10.2 Dedicated EPS bearer context activation
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
10.2.1 Dedicated EPS bearer context activation / Success
10.2.1.1 Test Purpose (TP)
(1)
with { UE is in EMM-REGISTERED state and a PDN address for an active default EPS bearer was received in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the existing default EPS bearer }
then { UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}
10.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.4.2.3.
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall first check the received TFT before taking it into use. Then the UE shall 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 PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, 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.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message 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.
The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains packet filters for the uplink direction.
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timerT3485 and enter the state BEARER CONTEXT ACTIVE.
10.2.1.3 Test description
10.2.1.3.1 Pre-test conditions
System Simulator:
– Cell A is configured according to Table 6.3.2.2-1 in [18].
UE:
None.
Preamble:
– The UE is in Registered, Ile Mode state (state 2) according to [18].
10.2.1.3.2 Test procedure sequence
Table 10.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS pages the UE in order to establish a dedicated EPS bearer context. |
– |
– |
– |
– |
|
2 |
The UE transmits a SERVICE REQUEST for downlink signalling. |
–> |
SERVICE REQUEST |
– |
– |
|
2A |
The SS establishes SRB2 and DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure). |
– |
– |
– |
– |
|
3 |
The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with particular settings using Reference dedicated EPS bearer context in Table 10.2.1.3.3-1. (See Note 1). Note: The SS implicitly reuses the PDN address defined in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. |
<– |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
4 |
Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified? |
–> |
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
1 |
P |
|
5 |
Check: Does the test result of CALL generic procedure indicate that the UE accepts a modification of the newly activated EPS bearer context (clause 6.4.2.6 in [18]) which uses reference packet filter according to Table 10.2.1.3.3-3? |
– |
– |
1 |
– |
|
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 |
|||||
10.2.1.3.3 Specific message contents
Table 10.2.1.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, Table 10.2.1.3.2-1)
|
Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition AM-DRB-ADD(2) |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
|
Linked EPS bearer identity |
5 |
SS re-uses the EPS bearer identity of the default EPS bearer context. |
|
|
EPS QoS |
According to reference dedicated EPS bearer context #1 – see [18] |
Non-IMS see Note1 |
|
|
EPS QoS |
According to reference dedicated EPS bearer context #4 – see [18] |
IMS |
|
|
TFT |
According to reference dedicated EPS bearer context #1- see [18] |
Non-IMS see Note1 |
|
|
TFT |
According to reference dedicated EPS bearer context #4 – see [18] |
IMS |
|
|
Note 1: Condition applies if TS 36-523-2 Table A.4.4.1/25 is false. Note 2: Condition applies if TS 36-523-2 Table A.4.4.1/25 is true. |
|||
Table 10.2.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 4, Table 10.2.1.3.2-1)
|
Derivation path: 36.508 table 4.7.3-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
|
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
Table 10.2.1.3.3-3: Reference packet filter (step 5, Table 10.2.1.3.2-1)
|
Derivation path: 36.508 table 6.6.2-5: |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Identifier |
0 0 1 1 0 0 1 1 |
Bidirectional,ID=3 |
|
|
Evaluation precedence |
(0 0 0 0 0 0 0 0) + EPS Bearer ID – 6 + 16 |
16 to 23 |
|
|
Component type 1 ID |
0 1 0 1 0 0 0 1 |
Remote port range type |
|
|
Component type 1 Value |
7062 |
.Note 1 |
|
|
7063 |
Note 1 |
||
|
Component type 2 ID |
0 0 1 1 0 0 0 0 |
Protocol identifier/Next header type |
|
|
Component type 2 Value |
17 |
UDP |
|
|
Note 1: The port values are different from the port values used for IMS signalling. |
|||
10.2.2 Dedicated EPS bearer context with QCI 66 activation / Success
10.2.2.1 Test Purpose (TP)
(1)
with { UE is in EMM-REGISTERED state and a PDN address for an active default EPS bearer was received in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the existing default EPS bearer }
then { UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}
(2)
with { UE is in EMM-REGISTERED state and a PDN address for an active default EPS bearer was received in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and a dedicated bearer linked to the EPS default bearer has been established}
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message using QCI 66 and linked to the existing default EPS bearer }
then { UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}
10.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.4.2.3.
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall first check the received TFT before taking it into use. Then the UE shall 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 PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, 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.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message 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.
The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains packet filters for the uplink direction.
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timerT3485 and enter the state BEARER CONTEXT ACTIVE.
10.2.2.3 Test description
10.2.2.3.1 Pre-test conditions
System Simulator:
– Cell A is configured according to Table 6.3.2.2-1 in [18].
UE:
None.
Preamble:
– The UE is in Registered, Idle Mode state (state 2) according to [18].
10.2.2.3.2 Test procedure sequence
Table 10.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS pages the UE in order to establish a dedicated EPS bearer context. |
– |
– |
– |
– |
|
2 |
The UE transmits a SERVICE REQUEST for downlink signalling. |
–> |
SERVICE REQUEST |
– |
– |
|
2A |
The SS establishes SRB2 and DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure). |
– |
– |
– |
– |
|
3 |
The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with particular settings using Reference dedicated EPS bearer context in Table 10.2.2.3.3-1. (See Note 1). Note: The SS implicitly reuses the PDN address defined in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. |
<– |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
|
4 |
Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified? |
–> |
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT |
1 |
P |
|
5 |
Check: Does the test result of CALL generic procedure indicate that the UE accepts a modification of the newly activated EPS bearer context (clause 6.4.2.6 in [18]) which uses reference packet filter according to Table 10.2.2.3.3-3? |
– |
– |
1 |
– |
|
6 |
Void |
– |
– |
– |
– |
|
7 |
The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST with particular settings using Reference dedicated EPS bearer context in Table 10.2.2.3.3-4 (see Note 1) Note: The SS implicitly reuses the PDN address defined in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. |
<– |
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 |
2 |
P |
|
9 |
Check: Does the test result of CALL generic procedure indicate that the UE accepts a modification of the newly activated EPS bearer context (clause 6.4.2.6 in [18]) which uses reference packet filter according to Table 10.2.2.3.3-6? |
– |
– |
2 |
– |
|
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 |
|||||
10.2.2.3.3 Specific message contents
Table 10.2.2.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition AM-DRB-ADD(2) |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
||
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
|
Linked EPS bearer identity |
5 |
SS re-uses the EPS bearer identity of the default EPS bearer context. |
|
|
EPS QoS |
According to reference dedicated EPS bearer context #4 – see [18] |
QCI 1 |
|
|
TFT |
According to reference dedicated EPS bearer context #4 – see [18] |
||
Table 10.2.2.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 4, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 4.7.3-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
6 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
|
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
Table 10.2.2.3.3-3: Reference packet filter (step 5, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 6.6.2-5: |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Identifier |
0 0 1 1 0 0 1 1 |
Bidirectional,ID=3 |
|
|
Evaluation precedence |
"16" |
||
|
Component type 1 ID |
0 1 0 1 0 0 0 1 |
Remote port range type |
|
|
Component type 1 Value |
7072 |
.Note 1 |
|
|
7073 |
Note 1 |
||
|
Component type 2 ID |
0 0 1 1 0 0 0 0 |
Protocol identifier/Next header type |
|
|
Component type 2 Value |
17 |
UDP |
|
|
Note 1: The port values are different from the port values used for IMS signalling. |
|||
Table 10.2.2.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 7, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition AM-DRB-ADD(2) |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
7 |
||
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
|
Linked EPS bearer identity |
5 |
SS re-uses the EPS bearer identity of the default EPS bearer context. |
|
|
EPS QoS |
According to reference dedicated EPS bearer context #8 – see [18] |
QCI 66 |
|
|
TFT |
According to reference dedicated EPS bearer context #8 see [18] |
||
Table 10.2.2.3.3-5: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 8, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 4.7.3-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS bearer identity |
7 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
|
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
Table 10.2.2.3.3-6: Reference packet filter (step 9, Table 10.2.2.3.2-1)
|
Derivation path: 36.508 table 6.6.2-10 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Identifier |
0 0 1 1 0 1 0 1 |
Bidirectional,ID=5 |
|
|
Evaluation precedence |
"17" |
||
|
Component type 1 ID |
0 1 0 1 0 0 0 1 |
Remote port range type |
|
|
Component type 1 Value |
7062 |
.Note 1 |
|
|
7063 |
Note 1 |
||
|
Component type 2 ID |
0 0 1 1 0 0 0 0 |
Protocol identifier/Next header type |
|
|
Component type 2 Value |
17 |
UDP |
|
|
Note 1: The port values are different from the port values used for IMS signalling. |
|||