Browse Prior Art Database

PDN Connection Setup Prioritization Disclosure Number: IPCOM000246066D
Original Publication Date: 2016-May-02
Included in the Prior Art Database: 2016-May-02
Document File: 3 page(s) / 168K

Publishing Venue


Related People

Tjandra, Paula: INVENTOR [+1]


This disclosure proposed PDN Connection Setup Prioritization perform to allow higher priority PDN connection to be set up when number of bearer limit has been reached. The prior arts for admission/scheduling are done after the PDN Connection has been set up. Priority of PDN connections can be dynamically calculated based on associated application type and dynamically changing ARP of that application at any specific time of an incident. Application Priority can be dynamically determined by the network (for deployment where dynamic dedicated bearer is utilized). Application Priority can be determined by configuration within the device.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Method and System for Prioritizing PDN Connection Setup

Paula Tjandra, Brundaban Sahoo

Motorola Solutions, Inc


Packet Data Network Connectivity in 3GPP EPS architecture is composed of a “default” EPS bearer and optionally one or more “dedicated” EPS bearer.  The total number of EPS bearers (“default” and/or “dedicated”) associated with a UE is limited to 8 bearers.  If this limit is reached, then any request for PDN connection will be rejected regardless of its priority and network congestion status.

In this paper, we present a new method that allows a UE to dynamically prioritize PDN connectivity setup, to temporarily suspend lower priority PDN connection in order to setup a higher priority PDN connection and to automatically re-establish lower priority PDN connection when the higher priority PDN connection has been terminated.


The 3GPP EPS architecture limits the number of EPS bearer associated with a UE to 8 bearers.  LTE RRC specification [1] further defines the breakdown of the 8 bearers:

·         Option 1: 8 bearers consist of 8 non-GBR bearers.

·         Option 2: 8 bearers consist of 5 non-GBR bearers and 3 GBR bearers.

Depending on the above option, the maximum number of the PDN connections for each UE is limited to either 8 or 5 PDN connections. The actual number of the PDN connections for each UE will likely be lower if the access network had already set up dedicated bearer for prioritized applications. An example for typical bearer usage for commercial system is as follow:

·         Non-GBR bearer usage: 

1.       IMS APN default bearer

2.       Emergency IMS APN default bearer (on demand APN, only set up when end user invoke emergency calling)

3.       Default/Internet APN default bearer

4.       Management APN default bearer (on demand APN, only set up when device management related procedure is required)

5.       MMS default bearer

·         GBR bearer usage:

1.       IMS dedicated bearer for voice session (on demand dedicated bearer)

2.       IMS dedicated bearer for video session (on demand dedicated)

The commercial system example above illustrates how the typical usage is already almost exhausted the limit.

LTE adaptation for public safety introduces new issues related to additional QoS requirements. An example for typical additional bearer usage for public safety system is as follow:

·         Non-GBR bearer usage: 

1.       One or more high priority data application dedicated bearer

2.       Default bearer for APN associated with public safety applications such as PTT

·         GBR bearer usage:

1.       Dedicated bearer for Push-to-Talk application

2.       Dedicated bearer for high priority video application

As illustrated in the public safety system example above, it is possible that the 5 non-GBR bearer limit has been reached by the time a UE invoke emergency calling.

Additional bearer may be required to provide additional level of prioritization, utilizing the 3GPP Release 12 Mission Critical QoS Class Identifier [2].

There has been proposal [3] for improving infrastructure admission c...