13.1.1 Activation and deactivation of additional data radio bearer in E-UTRA
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
13.1.1.1 Test Purpose (TP)
(1)
with { UE has a default EPS bearer context and dedicated EPS bearer context active and the associated DRBs are established }
ensure that {
when { UE receives downlink data on the radio bearer associated with the default or the dedicated EPS bearer context }
then { UE delivers the downlink data to upper layers }
}
(2)
with { UE has a default EPS bearer context and dedicated EPS bearer context active and the associated DRBs are established }
ensure that {
when { uplink data are submitted for transmission }
then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context or the dedicated EPS bearer context according to configured TFT}
}
(3)
with { UE has a default EPS bearer context and the dedicated EPS bearer context was deactivated }
ensure that {
when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }
then { UE delivers the downlink data to upper layers }
}
(4)
with { UE has a default EPS bearer context and the dedicated EPS bearer context was deactivated }
ensure that {
when { uplink data are submitted for transmission }
then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }
}
13.1.1.2 Conformance requirements
Same Conformance requirements as in clause 8.2.1.3, 8.2.3.1, 10.2.1 and 10.4.1
13.1.1.3 Test description
13.1.1.3.1 Pre-test conditions
System Simulator:
– Cell 1.
UE:
None.
Preamble:
– The UE is in state Generic RB Established, UE test mode activated (state 3A) according to [18] using the UE TEST LOOP MODE B.
13.1.1.3.2 Test procedure sequence
Table 13.1.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS transmits an RRCConnectionReconfiguration message to establish a data radio bearer. The SS transmits a ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message activating a new EPS bearer context. The NAS message is included in a RRCConnectionReconfiguration message. |
<– |
RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
– |
– |
2 |
The UE transmits a RRCConnectionReconfigurationComplete message to confirm the establishment of data radio bearer. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
3 |
The UE transmits an ACTIVATE DEDICATE EPS BEARER CONTEXT ACCEPT message. |
–> |
ULInformationTransfer NAS: ACTIVATE DEDICATE EPS BEARER CONTEXT ACCEPT |
– |
– |
4 |
The SS closes the UE test loop mode. |
– |
– |
– |
– |
5 |
The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context. |
<– |
IP packet |
– |
– |
6 |
Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context? |
–> |
IP packet |
1,2 |
P |
7 |
The SS transmits one IP packet to the UE on the DRB associated with the dedicated EPS bearer context. |
<– |
IP packet |
– |
– |
8 |
Check: Does the UE loop back the IP packet on the DRB associated with the dedicated EPS bearer context? |
–> |
IP packet |
1,2 |
P |
9 |
SS transmits an RRCConnectionReconfiguration message to release a data radio bearer. The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the dedicated EPS bearer. The NAS message is included in a RRCConnectionReconfiguration message. |
<– |
RRCConnectionReconfiguration NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST |
– |
– |
10 |
The UE transmits an RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
11 |
The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT. |
–> |
ULInformationTransfer NAS:DEACTIVATE EPS BEARER CONTEXT ACCEPT |
– |
– |
12 |
The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context. |
<– |
IP packet |
– |
– |
13 |
Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context? |
–> |
IP packet |
3, 4 |
P |
13.1.1.3.3 Specific message contents
Table 13.1.1.3.3-1: Message RRCConnectionReconfiguration (step 1, Table 13.1.1.3.2-1)
Derivation Path: 36.508 table 4.6.1-8, condition DRB(1,0) |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE{ |
||||
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF |
1 entry |
|||
dedicatedInfoNAS [1] |
octet string |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST according 36.508 table 4.7.3-3 |
||
} |
||||
} |
||||
} |
||||
} |
Table 13.1.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 1, Table 13.1.1.3.2-1)
Derivation path: 36.508 table 4.7.3-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EPS bearer identity |
EBId-1 |
SS defines a dedicated bearer Id different from default EBId and between 5 and 15. |
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
|
Linked EPS bearer identity |
Default EBId |
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] |
||
TFT |
According to reference dedicated EPS bearer context #1- see [18] |
Table 13.1.1.3.3-3: Message ACTIVATE DEDICATE EPS BEARER CONTEXT ACCEPT (step 3, Table 13.1.1.3.2-1)
Derivation path: 36.508 table 4.7.3-1 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EPS bearer identity |
EBId-1 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST |
|
Procedure transaction identity |
0 |
"No procedure transaction identity assigned" |
Table 13.1.1.3.3-4: Message RRCConnectionReconfiguration (step 9, Table 13.1.1.3.2-1)
Derivation Path: 36.508 table 4.6.1-8 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE{ |
||||
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF SEQUENCE { |
||||
DedicatedInfoNAS[1] |
DEACTIVATE EPS BEARER CONTEXT REQUEST |
|||
} |
||||
radioResourceConfigDedicated |
RadioResourceConfigDedicated-DRB-RELEASE |
|||
} |
||||
} |
||||
} |
||||
} |
Table 13.1.1.3.3-5: Message RadioResourceConfigDedicated-DRB-RELEASE (step 9, Table 13.1.1.3.2-1)
Derivation Path: 36.331 clause 6.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RadioResourceConfigDedicated ::= SEQUENCE { |
|||
srb-ToAddModList |
Not present |
||
drb-ToAddModList |
Not present |
||
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE { |
1 entry |
||
drb-Identity[1] |
2 |
||
} |
|||
mac-MainConfig CHOICE { } |
Not present |
||
sps-Config |
Not present |
||
physicalConfigDedicated |
Not present |
||
} |
Table 13.1.1.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 9, Table 13.1.1.3.2-1)
Derivation path: 36.508 table 4.7.3-12 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EPS bearer identity |
EBId-1 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST of step 1 |
|
Procedure transaction identity |
0 |
No procedure transaction identity assigned |
|
ESM cause |
00100100 |
“Regular deactivation” |
|
Protocol configuration options |
Not present |
Table 13.1.1.3.3-7: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 11, Table 13.1.1.3.2-1)
Derivation path: 36.508 table 4.7.3-11 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EPS bearer identity |
EBId-1 |
Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST of step 1 |
|
Procedure transaction identity |
0 |
No procedure transaction identity assigned |