8.2.3 Radio bearer release
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success
8.2.3.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a drb-ToReleaseList }
then { for each drb-Identity release the PDCP entity and RLC entity and DTCH logical channel
and indicate release of the DRB(s) to upper layers }
}
8.2.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.5.3 and 5.3.10.2.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
- if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:
…
1> else:
2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
3> perform the radio resource configuration procedure as specified in 5.3.10;
…
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 36.331, clause 5.3.10.2]
The UE shall:
1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration (DRB release):
2> release the PDCP entity;
2> release the RLC entity;
2> release the DTCH logical channel;
1> indicate the release of the DRB(s) and the eps-BearerIdentity of the released DRB(s) to upper layers;
8.2.3.1.3 Test description
8.2.3.1.3.1 Pre-test conditions
System Simulator:
– Cell 1
UE:
None.
Preamble:
– The UE is in state Generic RB Established (state 3) according to [18].
– The condition SRB2-DRB(2, 0) is used for step 8 in 4.5.3.3 according to [18].
8.2.3.1.3.2 Test procedure sequence
Table 8.2.3.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCConnectionReconfiguration message with a drb-ToReleaseList. |
<– |
RRCConnectionReconfiguration |
– |
– |
2 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete message? |
–> |
RRCConnectionReconfigurationComplete |
1 |
P |
2a |
The UE transmits an ULInformationTransfer message. |
–> |
ULInformationTransfer |
– |
– |
3 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1? |
– |
– |
1 |
– |
8.2.3.1.3.3 Specific message contents
Table 8.2.3.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.3.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 |
1 entry |
|||
DedicatedInfoNAS[1] |
DEACTIVATE EPS BEARER CONTEXT REQUEST with EPS bearer identity corresponding to drb-Identity 2 and ESM cause #36 |
According 36.508 table 4.7.3-12 and regular deactivation of a second DRB |
||
radioResourceConfigDedicated |
RadioResourceConfigDedicated-DRB-RELEASE |
Table 8.2.3.1.3.3-2 |
||
} |
||||
} |
||||
} |
||||
} |
Table 8.2.3.1.3.3-2: RadioResourceConfigDedicated-DRB-RELEASE (Table 8.2.3.1.3.3-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 |
1 entry |
||
drb-Identity[1] |
2 |
||
mac-MainConfig CHOICE { } |
Not present |
||
sps-Config |
Not present |
||
physicalConfigDedicated |
Not present |
||
} |