10.2 EN-DC session management
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
10.2.1 Network initiated procedures
10.2.1.1 Default EPS bearer context activation
10.2.1.1.1 Test Purpose (TP)
(1)
with { UE has sent a PDN CONNECTIVITY REQUEST message }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE Procedure transaction identity matching the PDN CONNECTIVITY REQUEST message and including the Extended APN-AMBR IE }
then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enters BEARER CONTEXT ACTIVE state }
}
10.2.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.4.1.3, 8.3.6.17and 9.9.4.29. Unless otherwise stated these are Rel-15 requirements.
[TS 24.301, clause 6.4.1.3]
Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396 if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message was received in response to a request for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then send an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. When the default bearer is activated as part of the attach procedure, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message together with ATTACH COMPLETE message. When the default bearer is activated as the response to the stand-alone PDN CONNECTIVITY REQUEST message, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message alone.
If a WLAN offload indication information element is included in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the WLAN offload acceptability values for this PDN connection and use the E-UTRAN offload acceptability value to determine whether this PDN connection is offloadable to WLAN or not.
The UE checks the PTI in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to identify the UE requested PDN connectivity procedure to which the default bearer context activation is related (see subclause 6.5.1).
If the UE receives a serving PLMN rate control IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the serving PLMN rate control IE value and use the stored serving PLMN rate control value as the maximum allowed limit of uplink User data container IEs included in ESM DATA TRANSPORT messages for the corresponding PDN connection in accordance with 3GPP TS 23.401 [10].
If the UE receives an APN rate control parameters container in the protocol configuration options IE or extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the APN rate control parameters value and use the stored APN rate control parameters value as the maximum allowed limit of uplink user data related to the APN indicated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in accordance with 3GPP TS 23.401 [10]. If the UE has a previously stored APN rate control parameters value for this APN, the UE shall replace the stored APN rate control parameters value for this APN with the received APN rate control parameters value.
If the UE receives an additional APN rate control parameters for exception data container in the protocol configuration options IE or extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the APN indicated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in accordance with 3GPP TS 23.401 [10]. If the UE has a previously stored additional APN rate control parameters for exception data value for this APN, the UE shall replace the stored additional APN rate control parameters for exception data value for this APN with the received additional APN rate control parameters for exception data value.
If the UE receives non-IP Link MTU parameter or IPv4 Link MTU parameter of the protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall pass the received Non-IP Link MTU or IPv4 Link MTU to the upper layer.
NOTE: The Non-IP Link MTU and the IPv4 Link MTU size correspond to the maximum length of user data that can be sent either in the user data container in the ESM DATA TRANSPORT message or via S1-U interface.
If the UE receives a session-AMBR and QoS rule(s), which correspond to the default EPS bearer of the PDN connectivity being activated, in the protocol configuration options IE or the extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE stores the session-AMBR and QoS rule(s) for use during inter-system change from S1 mode to N1 mode.
Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message, the MME shall enter the state BEARER CONTEXT ACTIVE and stop the timer T3485, if the timer is running. If the PDN CONNECTIVITY REQUEST message included a low priority indicator set to "MS is configured for NAS signalling low priority", the MME shall store the NAS signalling low priority indication within the default EPS bearer context.
[TS 24.301, clause 8.3.6.17]
This IE shall be included in the message only if the network wishes to transmit the APN-AMBR values to the UE for possible uplink policy enforcement and at least one of the values to be transmitted exceeds the maximum value specified in the APN aggregate maximum bit rate information element in subclause 9.9.4.2.
[TS 24.301, clause 9.9.4.29]
The purpose of the extended APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR with a value higher than 65280 Mbps when the UE establishes a PDN connection or to indicate the new APN-AMBR with a value higher than 65280 Mbps if it is changed by the network.
The receiving entity shall ignore the bit rate values which are included in the extended APN aggregate maximum bit rate information element and not higher than 65280 Mbps.
The extended APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.29.1 and table 9.9.4.29.1.
The extended APN aggregate maximum bit rate is a type 4 information element with a length of 8 octets.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Extended APN aggregate maximum bit rate IEI |
octet 1 |
|||||||
|
Length of extended APN aggregate maximum bit rate contents |
octet 2 |
|||||||
|
Unit for extended APN-AMBR for downlink |
octet 3 |
|||||||
|
Extended APN-AMBR for downlink |
octet 4 |
|||||||
|
Extended APN-AMBR for downlink (continued) |
octet 5 |
|||||||
|
Unit for extended APN-AMBR for uplink |
octet 6 |
|||||||
|
Extended APN-AMBR for uplink |
octet 7 |
|||||||
|
Extended APN-AMBR for uplink (continued) |
octet 8 |
|||||||
Figure 9.9.4.29.1: Extended APN aggregate maximum bit rate information element
Table 9.9.4.29.1: Extended APN aggregate maximum bit rate information element
|
Unit for extended APN-AMBR for downlink (octet 3) 0 0 0 0 0 0 0 0 value is not used 0 0 0 0 0 0 0 1 value is not used 0 0 0 0 0 0 1 0 value is not used 0 0 0 0 0 0 1 1 value is incremented in multiples of 4 Mbps 0 0 0 0 0 1 0 0 value is incremented in multiples of 16 Mbps 0 0 0 0 0 1 0 1 value is incremented in multiples of 64 Mbps 0 0 0 0 0 1 1 0 value is incremented in multiples of 256 Mbps 0 0 0 0 0 1 1 1 value is incremented in multiples of 1 Gbps 0 0 0 0 1 0 0 0 value is incremented in multiples of 4 Gbps 0 0 0 0 1 0 0 1 value is incremented in multiples of 16 Gbps 0 0 0 0 1 0 1 0 value is incremented in multiples of 64 Gbps 0 0 0 0 1 0 1 1 value is incremented in multiples of 256 Gbps 0 0 0 0 1 1 0 0 value is incremented in multiples of 1 Tbps 0 0 0 0 1 1 0 1 value is incremented in multiples of 4 Tbps 0 0 0 0 1 1 1 0 value is incremented in multiples of 16 Tbps 0 0 0 0 1 1 1 1 value is incremented in multiples of 64 Tbps 0 0 0 1 0 0 0 0 value is incremented in multiples of 256 Tbps 0 0 0 1 0 0 0 1 value is incremented in multiples of 1 Pbps 0 0 0 1 0 0 1 0 value is incremented in multiples of 4 Pbps 0 0 0 1 0 0 1 1 value is incremented in multiples of 16 Pbps 0 0 0 1 0 1 0 0 value is incremented in multiples of 64 Pbps 0 0 0 1 0 1 0 1 value is incremented in multiples of 256 Pbps Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol. Extended APN-AMBR for downlink (octets 4 and 5) Octets 4 and 5 represent the binary coded value of extended APN-AMBR for downlink in units defined by octet 3 Unit for extended APN-AMBR for uplink (octet 6) The coding is identical to that of the unit for extended APN-AMBR for downlink (octet 3) Extended APN-AMBR for uplink (octets 7 and 8) Octets 7 and 8 represent the binary coded value of extended APN-AMBR for uplink in units defined by octet 6. |
10.2.1.1.3 Test description
10.2.1.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell.
UE:
None.
Preamble:
– The UE is in RRC_IDLE state on E-UTRA Cell 1 using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4].
10.2.1.1.3.2 Test procedure sequence
Table 10.2.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request connectivity to an additional PDN (see Note 1) |
– |
– |
– |
– |
|
2 |
UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by a SERVICE REQUEST message. |
–> |
SERVICE REQUEST |
– |
– |
|
3 |
The SS establishes SRB2 and DRB associated with default EPS bearer context (a first PDN obtained during the attach procedure). |
– |
– |
– |
– |
|
4 |
The UE transmit a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN. |
–> |
PDN CONNECTIVITY REQUEST |
– |
– |
|
5 |
The SS transmits an RRCConnectionReconfiguration message containing NR RRCReconfiguration message to add NR PSCell with SCG DRB. The RRCConnectionReconfiguration message contains ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message containing Extended APN-AMBR IE. |
<– |
RRC: RRCConnectionReconfiguration((RRCReconfiguration) NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST |
– |
– |
|
6 |
The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer. |
–> |
RRC: RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in step 7 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
– |
– |
|
7 |
The UE transmits ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message. |
–> |
RRC: ULInformationTransfer NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT |
1 |
P |
|
Note 1: The request of connectivity to an additional PDN may be performed by MMI or AT command. |
|||||
10.2.1.1.3.3 Specific message contents
Table 10.2.1.1.3.3-1: PDN CONNECTIVITY REQUEST (step 4, Table 10.2.1.1.3.2-1)
|
Derivation path: TS 36.508 [7], Table 4.7.3-20 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
ESM |
|||
|
EPS bearer identity |
0 |
No EPS bearer identity assigned |
||
|
Procedure transaction identity |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
||
|
Access point name |
APN-1(New PDN name) |
The requested PDN is different from default PDN |
||
Table 10.2.1.1.3.3-2: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 5, Table 10.2.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.7.3-6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
ESM |
|||
|
EPS bearer identity |
6 |
|||
|
Procedure transaction identity |
PTI-1 |
SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure. |
||
|
EPS QoS |
||||
|
QCI |
8 |
|||
|
Maximum bit rate for uplink |
384 kbps |
|||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
|||
|
Guaranteed bit rate for uplink |
128 kbps |
|||
|
Guaranteed bit rate for downlink |
128 kbps |
|||
|
Maximum bit rate for uplink (extended) |
0 |
|||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
|||
|
Guaranteed bit rate for uplink (extended) |
0 |
|||
|
Guaranteed bit rate for downlink (extended) |
0 |
|||
|
Maximum bit rate for uplink (extended-2) |
0 |
|||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
|||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
|||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
|||
|
APN-AMBR |
||||
|
APN-AMBR for downlink |
‘11111110’B (8640 kbps) |
|||
|
APN-AMBR for uplink |
‘11111110’B (8640 kbps) |
|||
|
APN-AMBR for downlink (extended) |
‘11111010’ B(256 Mbps) |
|||
|
APN-AMBR for uplink (extended) |
‘11111010’ B(256 Mbps) |
|||
|
APN-AMBR for downlink (extended-2) |
‘11111110’B (65280 Mbps) |
|||
|
APN-AMBR for uplink (extended-2) |
0 |
|||
|
Access point name |
APN-1 |
SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure |
||
|
Extended APN-AMBR |
||||
|
Unit for extended APN-AMBR for downlink |
‘00000111’B (value is incremented in multiples of 1 Gbps) |
|||
|
Extended APN-AMBR for downlink |
‘0000000010000000’ (128 Gbps) |
|||
|
Unit for extended APN-AMBR for uplink |
0 |
|||
|
Extended APN-AMBR for uplink |
0 |
|||
10.2.1.2 Dedicated EPS bearer context activation
10.2.1.2.1 Test Purpose (TP)
(1)
with { UE in EMM-REGISTERED state }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, including the Extended EPS QoS IE, linked to the existing default EPS bearer }
then { UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT }
}
(2)
with { the UE in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode }
ensure that {
when { the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message including the Extended EPS QoS and Extended APN-AMBR IEs }
then { UE transmits a MODIFY EPS BEARER CONTEXT ACCEPT }
}
10.2.1.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.4.2.3, 6.4.3.1, 6.4.3.2, 6.4.3.3, 8.3.3.11, 9.9.4.29 and 9.9.4.30. Unless otherwise stated these are Rel-15 requirements.
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396, if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then check the received TFT before taking it into use, send an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. The ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message shall include the EPS bearer identity.
The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked.
If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the dedicated bearer context activation is related.
[TS 24.301, clause 6.4.3.1]
The purpose of the EPS bearer context modification procedure is to modify an EPS bearer context with a specific QoS and TFT, or re-negotiate header compression configuration associated to an EPS bearer context. The EPS bearer context modification procedure is initiated by the network, but it may also be initiated as part of the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure.
The network may also initiate the EPS bearer context modification procedure to update the APN-AMBR of the UE, for instance after an inter-system handover. See 3GPP TS 23.401 [10] annex E.
[TS 24.301, clause 6.4.3.2]
The MME shall initiate the EPS bearer context modification procedure by sending a MODIFY EPS BEARER CONTEXT REQUEST message to the UE, starting the timer T3486, and entering the state BEARER CONTEXT MODIFY PENDING (see example in figure 6.4.3.2.1).
The MME shall include an EPS bearer identity that identifies the EPS bearer context to be modified in the MODIFY EPS BEARER CONTEXT REQUEST message.
[TS 24.301, clause 6.4.3.3]
Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396, if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the MODIFY EPS BEARER CONTEXT REQUEST message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then check the received TFT before taking it into use and send a MODIFY EPS BEARER CONTEXT ACCEPT message to the MME.
If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the EPS bearer context modification is related (see subclause 6.5.3 and subclause 6.5.4).
If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]) and the PTI is associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided.
…
Upon receipt of the MODIFY EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timer T3486 and enter the state BEARER CONTEXT ACTIVE.
[TS 24.301, clause 8.3.3.11]
This IE shall be included in the message only if the network wishes to transmit the maximum and guaranteed bit rate values to the UE and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in subclause 9.9.4.3
[TS 24.301, clause 9.9.4.29]
The purpose of the extended APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR with a value higher than 65280 Mbps when the UE establishes a PDN connection or to indicate the new APN-AMBR with a value higher than 65280 Mbps if it is changed by the network.
The receiving entity shall ignore the bit rate values which are included in the extended APN aggregate maximum bit rate information element and not higher than 65280 Mbps.
The extended APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.29.1 and table 9.9.4.29.1.
The extended APN aggregate maximum bit rate is a type 4 information element with a length of 8 octets
[TS 24.301, clause 9.9.4.30]
The purpose of the Extended EPS quality of service information element is to indicate for an EPS bearer context the maximum bit rates for uplink and downlink and the guaranteed bit rates for uplink and downlink, if at least one of the bit rates has a value higher than 10 Gbps.
The Extended EPS quality of service information element is coded as shown in figure 9.9.4.30.1 and table 9.9.4.30.1. For uplink and downlink, if sending entity only has to indicate one bit rate (i.e., with a value higher than 10 Gbps), it shall encode the other bit rate (i.e., with a value smaller or equal to 10 Gbps) as "00000000". The receiving entity shall ignore the bit rate which is included in the extended quality of service information element and has a value smaller or equal to 10 Gbps.
10.2.1.2.3 Test description
10.2.1.2.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 is the PCell and NR Cell 1 is the PSCell.
UE:
– None.
Preamble:
– The UE is in RRC_IDLE state on E-UTRA Cell 1 using generic procedure parameter Connectivity (E-UTRA/EPC) according to TS 38.508-1 [4].
10.2.1.2.3.2 Test procedure sequence
Table 10.2.1.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1-6 |
Steps 1 to 6 of generic procedure defined in clause 4.5.4 in TS 38.508-1 [4]. |
– |
– |
– |
– |
|
7 |
The SS configures a dedicated EPS bearer associated with the default EPS bearer context by sending ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST including the Extended QoS IE. (See Note 1 and Note 2). |
<– |
NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
8 |
Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified? |
–> |
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
1 |
P |
|
9 |
The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message with Extended EPS QoS and Extended APN-AMBR IEs. This message is included in a DLInformationTransfer message. |
<– |
MODIFY EPS BEARER CONTEXT REQUEST |
– |
– |
|
10 |
Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT ACCEPT message? |
–> |
MODIFY EPS BEARER CONTEXT ACCEPT |
2 |
P |
|
Note 1: The ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is included in a RRCConnectionReconfiguration message including a DRB setup for the same EPS bearer ID. Note 2: The RRCConnectionReconfiguration uses the condition for DC bearer MCG and SCG |
|||||
10.2.1.2.3.3 Specific message contents
Table 10.2.1.2.3.3-1: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 7, Table 10.2.1.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.5.4.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Protocol discriminator |
ESM |
||
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
‘0000 0000’B |
No procedure transaction identity assigned |
|
|
EPS QoS |
|||
|
QCI |
8 |
||
|
Maximum bit rate for uplink |
‘01101000’B (384) kbps |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
‘01001000’B (128 kbps) |
||
|
Guaranteed bit rate for downlink |
‘01001000’B (128 kbps) |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
‘00000111’ (value is incremented in multiples of 1 Gbps) |
||
|
Maximum bit rate for uplink |
‘0000000000000000’B |
||
|
Maximum bit rate for downlink |
‘0000000000001100’B (12 Gbps) |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
Table 10.2.1.2.3.3-2: MODIFY EPS BEARER CONTEXT REQUEST (step 9, Table 10.2.1.2.3.2-1)
|
Derivation path: TS 36.508 [7], Table 4.7.3-18 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
New EPS QoS |
|||
|
QCI |
8 |
||
|
Maximum bit rate for uplink |
‘01101000’B (384 kbps) |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
‘01001000’B (128 kbps) |
||
|
Guaranteed bit rate for downlink |
‘01001000’B (128 kbps) |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
APN-AMBR |
|||
|
APN-AMBR for downlink |
‘11111110’B (8640 kbps) |
||
|
APN-AMBR for uplink |
‘11111110’B (8640 kbps) |
||
|
APN-AMBR for downlink (extended) |
‘11111010’ B(256 Mbps) |
||
|
APN-AMBR for uplink (extended) |
‘11111010’ B(256 Mbps) |
||
|
APN-AMBR for downlink (extended-2) |
‘11111110’B (65280 Mbps) |
||
|
APN-AMBR for uplink (extended-2) |
0 |
||
|
Extended APN-AMBR |
|||
|
Unit for extended APN-AMBR for downlink |
‘00000111’B (value is incremented in multiples of 1 Gbps) |
||
|
Extended APN-AMBR for downlink |
‘0000000010000000’ (128 Gbps) |
||
|
Unit for extended APN-AMBR for uplink |
0 |
||
|
Extended APN-AMBR for uplink |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
‘00000111’ (value is incremented in multiples of 1 Gbps) |
||
|
Maximum bit rate for uplink |
‘0000000000000000’B |
||
|
Maximum bit rate for downlink |
‘0000000000001110’B |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
10.2.2 UE initiated procedures
10.2.2.1 EPS bearer resource allocation / modification
10.2.2.1.1 Test Purpose (TP)
(1)
with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-IDLE mode }
ensure that {
when { UE is requested to allocate bearer resource using Extended EPS QoS }
then { UE sends a BEARER RESOURCE ALLOCATION REQUEST including the Extended EPS QoS IE }
}
(2)
with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message }
then { UE sends an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}
(3)
with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-CONNECTED mode }
ensure that {
when { UE is requested to modify of bearer resource corresponding to the dedicated bearer using Extended EPS QoS }
then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message including the Extended EPS QoS IE }
}
(4)
with { UE having sent the BEARER RESOURCE MODIFICATION REQUEST message }
ensure that {
when { UE receives an MODIFY EPS BEARER CONTEXT REQUEST message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message }
then { UE sends a MODIFY EPS BEARER CONTEXT ACCEPT message }
}
10.2.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.4.2.3, 6.5.3.2, 6.5.3.3, 6.5.4.2, 6.5.4.3, 8.3.8, 8.3.10 and 9.9.4.30. Unless otherwise stated these are Rel-15 requirements.
[TS 24.301, clause 6.4.2.3]
The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked.
If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the dedicated bearer context activation is related.
[TS 24.301, clause 6.5.3.2]
In order to request the allocation of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE ALLOCATION REQUEST message to the MME, start timer T3480 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.3.2.1).
The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create new TFT". The packet filters in the Traffic flow aggregate IE shall include at least one packet filter applicable for the uplink direction. In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the additional GBR required for the traffic flow aggregate.
[TS 24.301, clause 6.5.3.3]
If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST message, the UE shall stop timer T3480 and enter the state PROCEDURE TRANSACTION INACTIVE. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see subclause 7.3.1).
If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is received, the UE shall verify that the EPS bearer identity given in the EPS bearer identity IE is not already used by any EPS bearer context. The UE shall then proceed as described in subclause 6.4.2.3 or subclause 6.4.2.4.
[TS 24.301, clause 6.5.4.2]
In order to request the modification of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE MODIFICATION REQUEST message to the MME, start timer T3481 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.4.2.1).
[TS 24.301, clause 6.5.4.3]
Upon receipt of the BEARER RESOURCE MODIFICATION REQUEST message, the MME checks whether the resources requested by the UE can be established, modified or released by verifying the EPS bearer identity given in the EPS bearer identity for packet filter IE.
If the bearer resource modification requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure, an EPS bearer context modification procedure or an EPS bearer context deactivation procedure.
…
Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481 and enter the state PROCEDURE TRANSACTION INACTIVE. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see subclause 7.3.1).
i) If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is received, the UE shall verify that the EPS bearer identity given in the EPS bearer identity IE is not already used by any EPS bearer context. The UE shall then proceed as described in subclause 6.4.2.3 or subclause 6.4.2.4.
[TS 24.301, clause 8.3.8]
This IE shall be included in the message only if the UE wishes to transmit the maximum and guaranteed bit rate values to the network and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in subclause 9.9.4.3.
[TS 24.301, clause 8.3.10]
This IE shall be included in the message only if the UE wishes to transmit the maximum and guaranteed bit rate values to the network and at least one of the values to be transmitted exceeds the maximum value specified in the EPS quality of service information element in subclause 9.9.4.3.
[TS 24.301, clause 9.9.4.30]
The purpose of the Extended quality of service information element is to indicate for an EPS bearer context the maximum bit rates for uplink and downlink and the guaranteed bit rates for uplink and downlink, if at least one of the bit rates has a value higher than 10 Gbps.
The Extended quality of service information element is coded as shown in figure 9.9.4.30.1 and table 9.9.4.30.1. For uplink and downlink, if the sending entity only has to indicate one bit rate (i.e., with a value higher than 10 Gbps), it shall encode the other bit rate (i.e., with a value smaller or equal to 10 Gbps) as "00000000". The receiving entity shall ignore a bit rate which is included in the extended quality of service information element and has a value smaller or equal to 10 Gbps.
The Extended quality of service is a type 4 information element with a length of 12 octets.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Extended quality of service IEI |
octet 1 |
|||||||
|
Length of Extended quality of service contents |
octet 2 |
|||||||
|
Unit for maximum bit rate |
octet 3 |
|||||||
|
Maximum bit rate for uplink |
octet 4 |
|||||||
|
Maximum bit rate for uplink (continued) |
octet 5 |
|||||||
|
Maximum bit rate for downlink |
octet 6 |
|||||||
|
Maximum bit rate for downlink (continued) |
octet 7 |
|||||||
|
Unit for guaranteed bit rate |
octet 8 |
|||||||
|
Guaranteed bit rate for uplink |
octet 9 |
|||||||
|
Guaranteed bit rate for uplink (continued) |
octet 10 |
|||||||
|
Guaranteed bit rate for downlink |
octet 11 |
|||||||
|
Guaranteed bit rate for downlink (continued) |
octet 12 |
|||||||
Figure 9.9.4.30.1: Extended quality of service information element
Table 9.9.4.30.1: Extended quality of service information element
|
Unit for maximum bit rate (octet 3) 0 0 0 0 0 0 0 0 value is not used 0 0 0 0 0 0 0 1 value is incremented in multiples of 200 kbps 0 0 0 0 0 0 1 0 value is incremented in multiples of 1 Mbps 0 0 0 0 0 0 1 1 value is incremented in multiples of 4 Mbps 0 0 0 0 0 1 0 0 value is incremented in multiples of 16 Mbps 0 0 0 0 0 1 0 1 value is incremented in multiples of 64 Mbps 0 0 0 0 0 1 1 0 value is incremented in multiples of 256 Mbps 0 0 0 0 0 1 1 1 value is incremented in multiples of 1 Gbps 0 0 0 0 1 0 0 0 value is incremented in multiples of 4 Gbps 0 0 0 0 1 0 0 1 value is incremented in multiples of 16 Gbps 0 0 0 0 1 0 1 0 value is incremented in multiples of 64 Gbps 0 0 0 0 1 0 1 1 value is incremented in multiples of 256 Gbps 0 0 0 0 1 1 0 0 value is incremented in multiples of 1 Tbps 0 0 0 0 1 1 0 1 value is incremented in multiples of 4 Tbps 0 0 0 0 1 1 1 0 value is incremented in multiples of 16 Tbps 0 0 0 0 1 1 1 1 value is incremented in multiples of 64 Tbps 0 0 0 1 0 0 0 0 value is incremented in multiples of 256 Tbps 0 0 0 1 0 0 0 1 value is incremented in multiples of 1 Pbps 0 0 0 1 0 0 1 0 value is incremented in multiples of 4 Pbps 0 0 0 1 0 0 1 1 value is incremented in multiples of 16 Pbps 0 0 0 1 0 1 0 0 value is incremented in multiples of 64 Pbps 0 0 0 1 0 1 0 1 value is incremented in multiples of 256 Pbps Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol. Maximum bit rate for uplink (octets 4 and 5) Octets 4 and 5 represent the binary coded value of maximum bit rate for uplink in units defined by octet 3. Maximum bit rate for downlink (octets 6 and 7) Octets 6 and 7 represent the binary coded value of maximum bit rate for downlink in units defined by octet 3. Unit for guaranteed bit rate (octet 8) The coding is identical to that of the unit for maximum bit rate (octet 3). Guaranteed bit rate for uplink (octets 9 and 10) Octets 9 and 10 represent the binary coded value of guaranteed bit rate for uplink in units defined by octet 8. Guaranteed bit rate for downlink (octets 11 and 12) Octets 11 and 12 represent the binary coded value of guaranteed bit rate for downlink in units defined by octet 8. |
10.2.2.1.3 Test description
10.2.2.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 and NR Cell 1.
UE:
– None.
Preamble:
– The UE is in state RRC_IDLE using generic procedure parameter Connectivity (E-UTRA/EPC) established according to TS 38.508-1 [4], clause 4.5.2.
10.2.2.1.3.2 Test procedure sequence
Table 10.2.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request bearer resource allocation of dedicated EPS bearer associated with non-IMS PDN connectivity if pc_MULTI_PDN=TRUE else first PDN connectivity. (Note 1). |
– |
– |
– |
– |
|
2 |
The UE transmits a SERVICE REQUEST message. |
–> |
SERVICE REQUEST |
– |
– |
|
3 |
The SS establishes SRB2 and the MCG DRBs associated with the default EPS bearer context activated during the preamble. |
– |
– |
– |
– |
|
4 |
Check: Does the UE transmit a BEARER RESOURCE ALLOCATION REQUEST message? |
–> |
BEARER RESOURCE ALLOCATION REQUEST |
1 |
P |
|
5 |
The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message and establishes a RLC-AM SCG DRB bearer using MCG_and_SCG condition. |
<– |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
6 |
Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message? |
–> |
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
2 |
P |
|
7 |
Cause the UE to request bearer resource modification of dedicated EPS bearer associated with non-IMS PDN connectivity if pc_MULTI_PDN=TRUE else first PDN connectivity. (Note 2). |
– |
– |
– |
– |
|
8 |
Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message? |
–> |
BEARER RESOURCE MODIFICATION REQUEST |
3 |
P |
|
9 |
The SS transmits an MODIFY EPS BEARER CONTEXT REQUEST message. |
<– |
MODIFY EPS BEARER CONTEXT REQUEST |
– |
– |
|
10 |
Check: Does the UE transmit an MODIFY EPS BEARER CONTEXT ACCEPT message? |
–> |
MODIFY EPS BEARER CONTEXT ACCEPT |
4 |
P |
|
Note 1: The request is assumed to be triggered by AT command +CGDSCONT, and +CGACT (activated). Note 2: The request is assumed to be triggered by AT command +CGCMOD. |
|||||
10.2.2.1.3.3 Specific message contents
Table 10.2.2.1.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 4, Table 10.2.2.1.3.2-1)
|
Derivation path: TS 36.508 [7], Table 4.7.3-6B |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Linked EPS bearer identity |
12 |
||
|
5 |
IMS_PDN_ONLY |
||
|
EPS QoS |
|||
|
QCI |
1 |
||
|
Maximum bit rate for uplink |
384 kbps |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
128 kbps |
||
|
Guaranteed bit rate for downlink |
128 kbps |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
Any value(Note1) |
||
|
Maximum bit rate for uplink |
‘00000000’B |
||
|
Maximum bit rate for downlink |
Any value(Note1) |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
|
Note1: The product of Unit for maximum bit rate and maximum bit rate for downlink should be 12Gbps. |
|||
|
Condition |
Explanation |
|
IMS_PDN_ONLY |
IMS_PDN only available |
Table 10.2.2.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 5, Table 10.2.2.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.5.4.3-1 , condition UE-INITIATED |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
EPS QoS |
|||
|
QCI |
1 |
||
|
Maximum bit rate for uplink |
384 kbps |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
128 kbps |
||
|
Guaranteed bit rate for downlink |
128 kbps |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
‘00000111’ (value is incremented in multiples of 1 Gbps) |
||
|
Maximum bit rate for uplink |
‘00000000’B |
||
|
Maximum bit rate for downlink |
‘0000000000001100’ B (12 Gbps) |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
Table 10.2.2.1.3.3-3: Message BEARER RESOURCE MODIFICATION REQUEST (step 8, Table 10.2.2.1.3.2-1)
|
Derivation path: TS 36.508 [7], Table 4.7.3-8 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity for packet filter |
6 |
||
|
Required traffic flow QoS |
|||
|
QCI |
1 |
||
|
Maximum bit rate for uplink |
384 kbps |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
128 kbps |
||
|
Guaranteed bit rate for downlink |
128 kbps |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
Any value (Note1) |
||
|
Maximum bit rate for uplink |
‘00000000’B |
||
|
Maximum bit rate for downlink |
Any value (Note1) |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
|
Note1: The product of Unit for maximum bit rate and maximum bit rate for downlink should be 16Gbps. |
|||
Table 10.2.2.1.3.3-4: Message MODIFY EPS BEARER CONTEXT REQUEST (step 7, Table 10.2.2.1.3.2-1)
|
Derivation path: TS 36.508 [7], Table 4.7.3-18, condition UE-INITIATED |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Linked EPS bearer identity |
12 |
||
|
5 |
IMS_PDN_ONLY |
||
|
New EPS QoS |
|||
|
QCI |
1 |
||
|
Maximum bit rate for uplink |
384 kbps |
||
|
Maximum bit rate for downlink |
‘11111110’B (8640 kbps) |
||
|
Guaranteed bit rate for uplink |
128 kbps |
||
|
Guaranteed bit rate for downlink |
128 kbps |
||
|
Maximum bit rate for uplink (extended) |
0 |
||
|
Maximum bit rate for downlink (extended) |
‘11111010’B (256 Mbps) |
||
|
Guaranteed bit rate for uplink (extended) |
0 |
||
|
Guaranteed bit rate for downlink (extended) |
0 |
||
|
Maximum bit rate for uplink (extended-2) |
0 |
||
|
Maximum bit rate for downlink (extended-2) |
‘11110110’B (10 Gbps) |
||
|
Guaranteed bit rate for uplink (extended-2) |
0 |
||
|
Guaranteed bit rate for downlink (extended-2) |
0 |
||
|
APN-AMBR |
|||
|
APN-AMBR for downlink |
‘11111110’B (8640 kbps) |
||
|
APN-AMBR for uplink |
‘11111110’B (8640 kbps) |
||
|
APN-AMBR for downlink (extended) |
‘11111010’ B(256 Mbps) |
||
|
APN-AMBR for uplink (extended) |
‘11111010’ B(256 Mbps) |
||
|
APN-AMBR for downlink (extended-2) |
‘11111110’B (65280 Mbps) |
||
|
APN-AMBR for uplink (extended-2) |
0 |
||
|
Extended APN-AMBR |
|||
|
Unit for extended APN-AMBR for downlink |
‘00000111’B (value is incremented in multiples of 1 Gbps) |
||
|
Extended APN-AMBR for downlink |
‘0000000010000000’ (128 Gbps) |
||
|
Unit for extended APN-AMBR for uplink |
0 |
||
|
Extended APN-AMBR for uplink |
0 |
||
|
Extended EPS QoS |
|||
|
Unit for maximum bit rate |
‘00000111’ (value is incremented in multiples of 1 Gbps) |
||
|
Maximum bit rate for uplink |
‘00000000’B |
||
|
Maximum bit rate for downlink |
‘0000000000010000’ B (16 Gbps) |
||
|
Unit for guaranteed bit rate |
‘00000000’B |
||
|
Guaranteed bit rate for uplink |
‘00000000’B |
||
|
Guaranteed bit rate for downlink |
‘00000000’B |
||
|
Condition |
Explanation |
|
IMS_PDN_ONLY |
IMS_PDN only available |