• Precedence Class: This attribute indicates the packet transfer priority under abnormal conditions, for example during a network congestion load.
• Reliability Class: This attribute indicates the transmission characteristics. It defines the probability of data loss, data delivered out of sequence, duplicate data delivery, and corrupted data. This parameter enables the configuration of layer "2" protocols in acknowledged or unacknowledged modes.
• Peak Throughput Class: This attribute indicates the expected maximum data transfer rate across the network for a specific access to an external packet switching network (from 8 Kbps up to 2,048 Kbps).
• Mean Throughput Class: This attribute indicates the average data transfer rate across the network during the remaining lifetime of a specific access to an external packet switching network (best effort, from 0.22 bps up to 111 Kbps).
• Delay Class: This attribute defines the end-to-end transfer delay for the transmission of Service Data Units (SDUs) through the GPRS network. The SDU represents the data unit accepted by the upper layer of GPRS and conveyed through the GPRS network.

• Traffic Class: Indicates the application type (conversational, streaming, interactive, background). Four classes of traffic have been defined for QoS:
  • Conversational Class: These services are dedicated to bi-directional communication in real time (for example, voice over IP and video conferencing).
  • Streaming Class: These services are dedicated to uni-directional data transfer in real time (for example, audio streaming and one-way video).
  • Interactive Class: These services are dedicated to the transport of human or machine interaction with remote equipment (for example, Web browsing, access to a server and access to a database).
  • Background Class: These services are dedicated to machine-to-machine communication; this class of traffic is not delay sensitive (for example, e-mail and SMS).
• Delivery Order: Indicates the presence of an in-sequence SDU delivery (if any).
• Delivery of Erroneous SDUs: Indicates if erroneous SDUs are delivered or discarded.
• SDU Format Information: Indicates the possible exact sizes of SDUs.
• SDU Error Ratio: Indicates the maximum allowed fraction of SDUs lost or detected as erroneous.
• Maximum SDU Size: Indicates the maximum allowed SDU size (from "10" octets up to "1,520" octets).
• Maximum Bit Rate for Uplink: Indicates the maximum number of bits delivered to the network within a period of time (from "0" up to "8,640" Kbps).
• Maximum Bit Rate for Downlink: Indicates the maximum number of bits delivered by the network within a period of time (from "0" up to "8,640" Kbps).
• Residual Bit Error Ratio: Indicates the undetected bit error ratio for each sub-flow in the delivered SDUs.
• Transfer Delay: Indicates the maximum time of SDU transfer for 95th percentile of the distribution of delay for all delivered SDUs.
• Traffic-Handling Priority: Indicates the relative importance of all SDUs belonging to a specific GPRS bearer compared with all SDUs of other GPRS bearers.
• Allocation/Retention Priority: Indicates the relative importance of resource allocation and resource retention for the data flow related to a specific GPRS bearer compared with the data flows of other GPRS bearers (this attribute is useful when resources are scarce).
• Guaranteed Bit Rate for Uplink: Indicates the guaranteed number of bits delivered to the network within a period of time (from "0" up to "8,640" Kbps).
• Guaranteed Bit Rate for Downlink: Indicates the guaranteed number of bits delivered to the network within a period of time (from "0" up to "8,640" Kbps).
• Maximum Bit Rate for Uplink (extended, octet 17): This field is an extension of the Maximum bit rate for uplink in octet "8". The coding is identical to that of the Maximum bit rate for downlink (extended). It is used to signal extended Maximum bit rates in uplink (up to "256" Mbps)
• Maximum Bit Rate for Downlink (extended, octet 15): Used to signal extended bit rates for downlink delivered by the network (up to "256" Mbps). This attribute is supported in 3GPP Release 6 and beyond.
• Guaranteed Bit Rate for Uplink (extended, octet 18): This field is an extension of the Guaranteed bit rate for uplink in octet "12". The coding is identical to that of the guaranteed bit rate for downlink (extended). Used to signal extended Guaranteed bit rates in uplink (up to "256" Mbps)
• Guaranteed Bit Rate for Downlink (extended, octet 16): Used to signal extended Guaranteed bit rates in downlink (up to "256" MBps). This attribute is supported in 3GPP Release 6 and beyond.

• Subscribed QoS
• Local QoS capping limit (if configured)
• QoS sent by GGSN in tunnel management messages
• QoS sent by RNC in RAB assignment messages (UMTS only)

• Maximum Bitrate (MBR) DL is capped to "472" kbps.
• Maximum Bitrate (MBR) UL is capped to "472" kbps.
• Peak Throughput (PR) is capped to "6" ("32000" octets/sec).
• Reliability class (RC) of "0x2", "Unacknowledged GTP; Acknowledged LLC and RLC, Protected data" is not supported. In such cases, RC is over-ridden as "0x3", "Unacknowledged GTP and LLC; Acknowledged RLC, Protected data"

• For Reliability Class "0x3", the SDU error ratio is capped to "4" (1x10^-4) if it exceeds a value of "4", a value greater than "4" represents stringent error ratios.
• For Reliability Class greater than "0x3", the SDU error ratio capped to "3" (1x10^-3) if the value provided exceeds "4".

• User action (The user may subscribe for a more premium service)
• Service provider action (The QoS is restricted on reaching download limits)

• An External Trigger (PCRF)
• Current load or capability of the GGSN
• If the "No Qos negotiation" flag is set in the previous Tunnel Management Request from SGSN.

• While sending Update PDP Context request during activation (Direct tunnel).
• During a service request for data with direct tunnel enabled for the subscriber, a UPCQ is initiated to inform the GGSN with the teid and the address of the RNC. This Update PDP context request has no negotiation bit set.
• Update PDP context request sent during preservation procedures.
• UPCQ sent to indicate establishment / removal of direct tunnel.
• Intra SGSN SRNS.
• Downlink data for the subscriber without active RABs and direct tunnel enabled for the subscriber, UPCQ is initiated to inform the GGSN of the teid and the address of the RNC. This Update PDP context request has "No QoS Negotiation" flag set.
• In all modification procedures (HLR, RNC, MS) if any other node other than the modifying entity has downgraded the QoS. For example, consider a HLR Initiated Modification procedure where the SGSN does the following signaling:
  • Initiates a UPCQ to inform the GGSN of the QOS change, GGSN sends a UPCR with same QOS as UPCQ.
  • Modify PDP context Request to MS, the MS sends a Modify PDP Accept.
  • RAB establishment request to the RNC, the RNC downgrades the QoS in the RAB assignment response.
  • The SGSN initiates a UPCQ to inform the GGSN of the new QoS sent in the previous step. This UPCQ will have no QoS negotiation bit set.
• If loss of Radio connectivity feature is enabled, then the Update PDP Context initiated to inform the GGSN that the MS is back in Radio Coverage will have the "No Qos Negotiation" bit set.

• QoS Class Identifier (QCI): The QCI is scalar that is used as a reference to node specific parameters that control packet forwarding treatment (for example, scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration and so on.) and that have been pre-configured by the operator owning the node (for example, eNodeB). The standardized characters associated with a standard QCI are listed below:

  • Resource Type (GBR or Non-GBR)
  • Priority
  • Packet Delay Budget
  • Packet Error Loss Rate

  

• APN AMBR: The APN-AMBR limits the aggregate bit rate that can be provided across all Non- GBR PDP contexts of the same APN (for example, excess traffic may get discarded by a rate shaping function). Each of those Non-GBR PDP contexts can potentially utilize the entire APN AMBR (for example, when the other Non-GBR PDP contexts do not carry any traffic). The GBR PDP contexts are outside the scope of APN AMBR. The PGW enforces the APN AMBR in downlink. Enforcement of APN AMBR in uplink may be done in the UE and additionally in the PGW.

• UE AMBR: The UE AMBR limits the aggregate bit rate that can be provided across all Non-GBR PDP contexts of a UE (for example, excess traffic may get discarded by a rate shaping function). Each of the Non-GBR PDP contexts can potentially use the entire UE AMBR (for example, when the other Non-GBR PDP contexts do not carry any traffic). The GBR (real-time) PDP contexts are outside the scope of UE AMBR. The RAN enforces the UE AMBR in uplink and downlink.

• E-ARP: The EPC uses Evolved ARP, which has priority level ranging from "1" up to "15". Additionally, evolved ARP comprises of pre-emption capability and pre-emption vulnerability. The preemption capability information defines whether a bearer with a lower priority level should be dropped to free up the required resources. The pre-emption vulnerability information indicates whether a bearer is applicable for such dropping by a preemption capable bearer with a higher priority value.

  For handover between UTRAN/GERAN and E-UTRAN, refer to 3GPP TS 24.101 "Annexure-E". It defines the mapping rule between ARP and Evolved ARP during R99 QoS to EPS bearer QoS mapping and vice versa.

• MBR: Maximum Bit Rate indicates the maximum number of bits delivered to the network or by the network within a period of time. This parameter is as defined in GMM QoS Parameters. In EPC, these values are encoded as a "5" octet linear value but in GMM QoS it is a single octet or a two octet step wise value.

• GBR: Guaranteed Bit Rate indicates the guaranteed number of bits delivered to the network or by the network within a period of time. This parameter is as defined in GMM QoS Parameters. In EPC, these values are encoded as a "5" octet linear value but in GMM QoS it is a single octet or a two octet step wise value.

1. EPC Subscription: If a subscriber has an EPC subscription, the QoS in subscription data is sent in the EPC format.
2. GPRS Subscription: If the subscriber does not have an EPC subscription, the QoS in subscription data is sent in R99/R5/R7 format.

• APN-AMBR is mapped to MBR for non-GBR bearers.
• Per bearer MBR and GBR is mapped to MBR and GBR towards UE for GBR bearers.
• For information on other mapping values refer to, 3GPP TS 23.203, table 6.1.7.

• During Activate Accept (EPC QoS to GMM QoS)
• During Activation initiated Create Session Request (if GPRS subscription is used GMM QoS to EPC QoS mapping)
• During S4-SGSN to Gn SGSN handover (EPC QoS to GMM QoS)
• During HLR / HSS initiated QoS modification (if GPRS subscription is used GMM to EPC QoS towards SGW/PGW; towards UE EPC to GMM QoS for both types of subscription)

1. Attach is received from an EPC capable UE.
2. The HLR subscription does not have EPS subscription data. Only GPRS subscription is present.
3. Activate a PDP context with all QoS parameters set to "subscribed".

Important

For this scenario, PDP context activation through Gn/Gp interface by default is not done. Instead a S4 election is done as the UE is EPC capable. However, if the local operator policy overrides this to select Gn/Gp, then Gn/Gp is preferred.

1. APN AMBR = Subscribed MBR

2. Bearer QoS PVI = Taken from local policy [use call-control-profile qos gn-gp config]

3. Bearer QoS PCI = Taken from local policy [use call-control-profile qos gn-gp config]

4. Bearer QoS PL = Taken from local policy [use call-control-profile qos gn-gp config]

5. Bearer QoS QCI = Mapped from subscribed traffic class

6. Bearer QoS MBR UL and DL = Mapped from subscribed MBR + MBR-Extended for UL and DL

7. Bearer QoS GBR UL and DL = Zero for interactive or background traffic. For streaming or conversational it is mapped from subscribed GBR + Ext.GBR UL / DL

1. Attach is received from an EPC capable UE.
2. The HLR subscription does not have EPS subscription data. Only GPRS subscription is present.
3. Activate a PDP context with all QoS parameters set to "subscribed".

Important

For this scenario, PDP context activation through Gn/Gp interface by default is not done. Instead a S4 election is done as the UE is EPC capable. However, if the local operator policy overrides this to select Gn/Gp, then Gn/Gp is preferred.

1. Traffic Class = Mapped from QCI based on Table E.3 in 3GPP TS 23.401.
2. Delivery Order = Taken from local configuration [apn-profile --> qos --> class [traffic class] --> sdu --> delivery order]
3. Delivery of erroneous SDU = Taken from local configuration [apn-profile --> qos --> class [traffic class] --> sdu --> erroneous]
4. Maximum SDU Size = [apn-profile --> qos --> class [traffic class] --> sdu --> max size]
5. MBR Uplink = APN-AMBR-UL (if traffic class = interactive /background) or Bearer MBR-UL (if TC = streaming / conversational)
6. MBR DL = APN-AMBR-DL (if traffic class = interactive /background) or Bearer MBR-DL (if TC = streaming / conversational)
7. Residual BER = Taken from local config [apn-profile-->qos-->class [tc] --> residual-bit-error-rate
8. SDU error ratio = Mapped based on Table 6.1.7 in 3GPP TS 23.203
9. Transfer delay = Mapped based on Table 6.1.7 in 3GPP TS 23.203
10. THP = Mapped from QCI based on Table E.3 in 3GPP TS 23.401
11. GBR UL = "0" for interactive or background class traffic. Mapped from Bearer QoS GBR UL for conversational or streaming traffic.
12. GBR DL = "0" for interactive or background class traffic. Mapped from Bearer QoS GBR DL for conversational or streaming traffic.
13. Signaling Indication = Mapped from QCI as per Table E.3 3GPP TS 23.401
14. Extended bit rates will be present if the mapped MBR / GBR exceeds "8640" Kbps

1. Attach is received from an EPC capable UE
2. The HLR subscription does not have EPS subscription data. Only GPRS subscription data is present.
3. A primary PDP context is activated with all QoS parameters set to some requested values.

1. Negotiate the requested QoS with subscribed QoS. Map the negotiated QoS as described in Scenario-1.
2. After receiving a Create Session Response, map the accepted EPS QoS to R99+ QoS as described in Scenario-2 and send the Activate accept.

1. Attach is received from an EPC capable UE
2. The HLR subscription has EPS subscription data.
3. A PDP context is activated with all QoS parameters set to "Subscribed" values or some requested values.

1. For every primary PDP context to an APN, the EPS subscribed QoS is used as is.
2. Once the EPS bearer is activated, the Activate PDP Accept is sent by mapping the accepted QoS value as described in Scenario-2.

1. Attach is received from an EPC capable UE
2. The HLR subscription has EPS subscription data.
3. A secondary PDP context is activated with all QoS parameters set to "Subscribed" values.

1. Linked EPS Bearer ID = EPS bearer ID of linked Primary PDP
2. PTI = Transaction ID received from the MS (In MME, the received PTI is used in the NAS message as the PTI towards S-GW. But for the SGSN PTI is not there in the NAS message. The 3GPP TS is not clear on what the SGSN should send as PTI, therefore TI is sent.

1. QCI = Mapped from requested Traffic Class, if TC= conversational / streaming
2. MBR UL = APN-AMBR last received from P-GW for primary PDP activation
3. MBR DL = APN-AMBR last received from P-GW for primary PDP activation
4. GBR UL = APN-AMBR last received from P-GW for primary PDP activation
5. GBR DL = APN-AMBR last received from P-GW for primary PDP activation
6. Else, the values will be MBR UL = "0", BR DL ="0", GBR UL = "0", GBR DL = "0"

Important

The value sent in the Flow QoS does not have any impact as it is the P-GW which decides the correct QoS value to be provided. If the requested QoS is set to "subscribed" then as a placeholder value the APN-AMBR value is sent as the MBR and GBR values.

1. Attach is received from an EPC capable UE
2. The HLR subscription has EPS subscription data.
3. A secondary PDP context is activated with all QoS parameters set to specified values.

1. Linked EPS Bearer ID = EPS bearer ID of linked Primary PDP
2. PTI = Transaction ID received from the MS (In MME, the received PTI is used in the NAS message as the PTI towards S-GW. But for the SGSN PTI is not there in the NAS message. The 3GPP TS is not clear on what the SGSN should send as PTI, therefore TI is sent.

1. QCI = Mapped from requested Traffic Class, if TC= conversational or streaming.
2. MBR UL = Requested MBR UL, MBR DL = Requested MBR DL
3. GBR UL = Requested GBR UL, GBR DL = Requested GBR DL or GBR UL = "0", GBR DL = "0"

Important

If the traffic class is conversational or streaming, the requested MBR or GBR values can be greater than the subscribed APN-AMBR.

1. Attach is received from an EPC capable UE
2. The HLR subscription does not have EPS subscription data.
3. A secondary PDP context is activated with all QoS parameters set to "Subscribed".

1. Linked EPS Bearer ID = EPS bearer ID of linked Primary PDP
2. PTI = Transaction ID received from the MS (In MME, the received PTI is used in the NAS message as the PTI towards S-GW. But for the SGSN PTI is not there in the NAS message. The 3GPP TS is not clear on what the SGSN should send as PTI, therefore TI is sent.

1. QCI = Mapped from requested Traffic Class, if TC= conversational or streaming
2. MBR UL = APN-AMBR-UL last obtained from P-GW for primary
3. MBR DL = APN-AMBR-DL last obtained from P-GW for primary
4. GBR UL = APN-AMBR-UL last obtained from P-GW for primary
5. GBR DL = APN-AMBR-UL last obtained from P-GW for primary
6. Else, MBR UL = "0", MBR DL = "0", GBR UL = "0", GBR DL = "0"

1. Attach is received from an EPC capable UE
2. The HLR subscription does not have EPS subscription data.
3. A secondary PDP context is activated with all QoS parameters set to valid requested values.

1. Linked EPS Bearer ID = EPS bearer ID of linked Primary PDP
2. PTI = Transaction ID received from the MS (In MME, the received PTI is used in the NAS message as the PTI towards S-GW. But for the SGSN PTI is not there in the NAS message. The 3GPP TS is not clear on what the SGSN should send as PTI, therefore TI is sent.

1. QCI = Mapped from requested Traffic Class, if TC= conversational or streaming
2. MBR UL = MBR-UL negotiated
3. MBR DL = MBR-DL negotiated
4. GBR UL = GBR-UL negotiated
5. GBR DL = GBR-DL negotiated
6. Else, MBR UL = "0", MBR DL = "0", GBR UL = "0", GBR DL = "0"

1. APN-AMBR-UL = Subscribed MBR-UL
2. APN-AMBR-DL = Subscribed MBR-DL
3. Bearer QoS MBR = Negotiated MBR received from peer SGSN Bearer QoS GBR = "0", for Interactive or Background traffic classes and it is Negotiated GBR value for Conversational or Streaming traffic classes.
4. Bearer QoS - PVI = Use from Local Policy (use call-control-profile qos gn-gp configuration)
5. Bearer QoS - PCI = Use from Local Policy (use call-control-profile qos gn-gp configuration)
6. Bearer QoS - PL = Use from Local Policy (use call-control-profile qos gn-gp configuration), based on the negotiated ARP received.
7. Bearer QoS - QCI = Mapped from negotiated traffic class.

1. Subscribed QoS = Mapped from subscribed EPS QoS
2. Requested QoS = Return the MS requested value
3. Negotiated QoS = Mapped from the current EPS QoS
4. The mapping of EPS QoS to pre- release "8" QoS is as described in scenario-2.
5. When mapping subscribed EPS QoS to pre-release "8" MBR and GBR the following rules are applied:
   • MBR-UL = APN-AMBR-UL
   • MBR-DL = APN-AMBR-DL
   • GBR-UL / DL = "0" (for TC = interactive / background)
   • GBR-UL / DL = APN-AMBR-UL / DL (for TC = interactive / background)

• The MS sends a Modify PDP Context Request (TI, QoS Requested, TFT, and Protocol Configuration Options) message to the SGSN. Either QoS Requested or TFT or both may be included. The QoS Requested indicates the desired QoS profile, while the TFT indicates the TFT that is to be added or modified or deleted from the PDP context. Protocol Configuration Options may be used to transfer optional PDP parameters and/or requests to the PGW.
• The SGSN identifies the bearer modification scenario that applies and sends the Bearer Resource Command (TEID, LBI, PTI, EPS Bearer QoS (excluding ARP), TFT, EBI, RAT type, Protocol Configuration Options, serving network identity, CGI/SAI, User CSG Information, MS Info Change Reporting support indication, DL TEID and DL Address, DTI) message to the selected Serving GW.
  • An S4-based SGSN applies the BCM 'MS/NW' whenever the S4 is selected for a certain MS. The following table list the details of MS-initiated EPS bearer modification, MS/NW mode:

    Table 1. MS-initiated EPS bearer modification, MS/NW mode

    Sl No.	PDP context modification use case	Information provided by SGSN at S4 signaling
    1.	Add TFT filters and increase QoS	QoS related to EPS Bearer, TFT filters added, TEID, EPS Bearer ID
    2.	Increase of QoS related to one or more TFT filter(s)	QoS related to EPS Bearer filters, Impacted TFT filters, TEID, EPS Bearer ID
    3.	Increase of QoS, TFT filters not specified	Not allowed in MS/NW mode
    4.	Add/remove TFT filters, no QoS change	TFT filters added/removed, TEID, EPS Bearer ID
    5.	Decrease QoS related to one or more TFT filter(s)	QoS related to EPS Bearer filters, Impacted TFT filters, TEID, EPS Bearer ID
    6.	Remove TFT filters and decrease QoS	QoS related to EPS Bearer, TFT filters removed, TEID, EPS Bearer ID
    7.	Decrease of QoS, TFT filters not specified	Not allowed in MS/NW mode
    Note: Only the modified QCI and/or GBR parameters are forwarded by the SGSN.

• The S4-SGSN may assume that the BCM mode of a bearer is MS/NW there are instances where the BCM mode negotiated between UE and PGW can be "UE only". In such cases, a UE sends a Modify PDP Request to the SGSN without a TFT. But SGSN cannot honor it in a R9 capable network since TAD is mandatory in BRC. In a R10 network, TAD is conditional optional on the S4 interface. Once the EGTP stack is upgraded to R10 compliance, the S4-SGSN honors PDP modification without TFT. For release 14.0, the SGSN rejects such PDP modifications.
• If the PDP modification is for non-GBR bearer, the SGSN sets the MBR and GBR values in Bearer Resource Command to "0". If the PDP modification is for GBR bearer, then SGSN sets the MBR and GBR values in Bearer Resource Command to the requested values.
• The Serving GW Forwards the message to the PGW.
• If the request is accepted, the PGW Initiated Bearer Modification Procedure is invoked by the PGW to modify the EPS Bearer indicated by the TEID.
  • The PDN GW sends an Update Bearer Request (TEID, EPS Bearer Identity, PTI, EPS Bearer QoS, APN-AMBR, TFT, Protocol Configuration Options, Prohibit Payload Compression, MS Info Change Reporting Action, and CSG Information Reporting Action) message to the Serving GW. The Procedure Transaction Id (PTI) parameter is used to link this message to the Request Bearer Resource Modification message received from the Serving GW.
• The Serving GW sends an Update Bearer Request (PTI, EPS Bearer Identity, EPS Bearer QoS, TFT, APN AMBR, Protocol Configuration Options, Prohibit Payload Compression, MS Info Change Reporting Action, CSG Information Reporting Action) message to the SGSN.
• In Iu mode, radio access bearer modification may be performed by the RAB Assignment procedure. If the radio access bearer does not exist, the RAB setup is done by the RAB Assignment procedure.
• The SGSN acknowledges the bearer modification by sending an Update Bearer Response (TEID, EPS Bearer Identity, DL TEID and DL Address, DTI) message to the Serving GW.
• The Serving GW acknowledges the bearer modification by sending an Update Bearer Response (TEID, EPS Bearer Identity) message to the PDN GW.
• The SGSN selects Radio Priority and Packet Flow Id based on QoS Negotiated, and returns a Modify PDP Context Accept (TI, QoS Negotiated, Radio Priority, Packet Flow Id, and Protocol Configuration Options) message to the MS.

• The Home Subscriber Server (HSS) initiated PDP context modification procedure is used when the HSS decides to modify the subscribed QoS, where typically QoS related parameters are changed. The parameters that may be modified are UE-AMBR, APN-AMBR QCI and Allocation/Retention Policy.
• The HSS initiates the modification by sending an Insert Subscriber Data (IMSI, Subscription Data) message to the SGSN. The Subscription Data includes EPS subscribed QoS (QCI, ARP) and the subscribed UE-AMBR and APN AMBR.
• The S4-SGSN then updates the stored Subscription Data and acknowledges the Insert Subscriber Data message by returning an Insert Subscriber Data Ack (IMSI) message to the HSS and sends the Modify Bearer Command (EPS Bearer Identity, EPS Bearer QoS, APN AMBR) message to the S-GW. The S-GW forwards the Modify Bearer Command (EPS Bearer Identity, EPS Bearer QoS, APN AMBR) message to the P-GW. Note that the EPS Bearer QoS sent in the Modify Bearer Command does not modify the per bearer bit-rate. It is sent to carry only a change in the ARP / QCI received from subscription. Also, the Modify Bearer Command can be sent only for the default bearer (primary PDP) in a PDN connection.
• The P-GW modifies the default bearer of each PDN connection corresponding to the APN for which subscribed QoS has been modified. If the subscribed ARP parameter has been changed, the P-GW shall also modify all dedicated EPS bearers having the previously subscribed ARP value unless superseded by PCRF decision. The P-GW then sends the Update Bearer Request (EPS Bearer Identity, EPS Bearer QoS [if QoS is changed], TFT, APN AMBR) message to the S-GW.
• The S-GW sends the Update Bearer Request (EPS Bearer Identity, EPS Bearer QoS (if QoS is changed) APN-AMBR, TFT) message to the SGSN. On completion of modification S4-SGSN acknowledges the bearer modification by sending the "Update Bearer Response (EPS Bearer Identity)" message to P-GW via S-GW. If the bearer modification fails, the P-GW deletes the concerned EPS Bearer.

• The P-GW sends the Update Bearer Request (TEID, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Prohibit Payload Compression, MS Info Change Reporting Action, CSG Information Reporting Action, TFT, and Protocol Configuration Options) message to the S-GW.
  • The TFT is optional and included in order to add, modify or delete the TFT related to the PDP Context. Protocol Configuration Options is optional.
• The S- GW sends the Update Bearer Request (TEID, EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, Prohibit Payload Compression, MS Info Change Reporting Action, CSG Information Reporting Action, TFT, and Protocol Configuration Options) message to the SGSN.
• In Iu mode, radio access bearer modification may be performed by the RAB Assignment procedure.
• The SGSN selects Radio Priority and Packet Flow Id based on the QoS Negotiated, and sends a Modify PDP Context Request (TI, PDP Address, QoS Negotiated, Radio Priority, Packet Flow Id, TFT, and PCO) message to the MS. The TFT is included only if it was received from the P-GW in the Update Bearer Request message. Protocol Configuration Options are sent transparently through the SGSN.
• The MS should accept the PDP context modification requested by the network if it is capable of supporting any modified QoS Negotiated as well as any modified TFT. For a successful modification the MS acknowledges by returning a Modify PDP Context Accept message. If the MS is incapable of accepting a new QoS Negotiated or TFT it shall instead de-activate the PDP context with the PDP Context Deactivation Initiated by MS procedure.
• On receiving the Modify PDP Context Accept message, or on completion of the RAB modification procedure, the SGSN returns an Update PDP Context Response (TEID, QoS Negotiated) message to the S-GW.
• The S-GW acknowledges the bearer modification to the P- GW by sending an Update Bearer Response (EPS Bearer Identity) message.

• Subscribed Evolved ARP if P-GW does not send any evolved ARP in Create Session Response.

• Evolved ARP supplied by the P-GW.

• Evolved ARP derived from the GPRS subscription using CLIs displayed below, when the P-GW does not send any Evolved ARP in Create Session Response:

• Evolved ARP supplied by the P-GW.

• PRE-EMPTION_CAPABILITY_ENABLED (0)

  This value indicates that the service data flow or bearer which is allowed to get resources that were already assigned to another service data flow or bearer with a lower priority level.

• PRE-EMPTION_CAPABILITY_DISABLED (1)

  This value indicates that the service data flow or bearer which is not allowed to get resources that were already assigned to another service data flow or bearer with a lower priority level. This is the default value applicable if this AVP is not supplied.

• PRE-EMPTION_VULNERABILITY_ENABLED (0)

  This value indicates that the resources assigned to the service data flow or bearer which can be pre-empted and allocated to a service data flow or bearer with a higher priority level. This is the default value applicable if this AVP is not supplied.

• PRE-EMPTION_VULNERABILITY_DISABLED (1)

  This value indicates that the resources assigned to the service data flow or bearer which shall not be pre-empted and allocated to a service data flow or bearer with a higher priority level.

• Default ARP high-priority value = 5.
• Default ARP medium-priority value = 10.
• Default pre-emption capability = shall-not-trigger-pre-emption.
• .Default pre-emption vulnerability = not pre-emptable

configure 
    sgsn-global 
         qos-arp-rp-map-profile  arp_profile_name 
         no qos-arp-rp-map-profile  arp_profile_name 
         end 

• arp_profile_name - Enter a string of 1 to 64 alphanumeric characters to identify the mapping profile and moves into the ARP-RP mapping profile configuration mode.
• no qos-arp-rp-map-profile - Removes the profile definition from the configuration.

configure 
    sgsn-global 
         qos-arp-rp-map-profile  arp_profile_name 
              arparp_value radio-priority  rp_value 
              end 

• arp_value - Defines the allocation retention priority. Enter an integer from 1 to 3.
• rp_value - Defines the radio priority. Enter an integer from 1 to 4.
• Default ARP-RP mapping would be
  • ARP1 RP4
  • ARP2 RP4
  • ARP3 RP4
• Use the show sgsn-mode command to display the ARP-RP profile and configuration.

configure 
    context  context_name 
         gprs-service  service_name 
              sm radio-priority from-arp arp_profile_name 
              no sm radio-priority from-arp arp_profile_name 
              end 

• This example illustrates the GPRS Service configuration mode, but either GPRS or SGSN Service configuration modes could be entered. The command sequent would have to be repeated, once for each type of service, to associate the ARP-RP profile with both types of services.
• no sm radio-priority from-arp - This command will remove the association from the configuration.
• Use the show configuration command to display the association.