8.2.6 MR-DC RRC others
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
8.2.6.1 Failure information / RLC failure / SCG
8.2.6.1.1 Failure information / RLC failure / SCG / EN-DC
8.2.6.1.1.1 Failure information / RLC failure / SCG / EN-DC / Intra-band Contiguous CA
8.2.6.1.1.1.1 Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG }
ensure that {
when { an indication from SCG RLC that the maximum number of retransmissions has been reached and when CA duplication is configured and activated and for the corresponding logical channel allowedServingCells only includes SCell(s) }
then { UE sends the FailureInformation message embedded in E-UTRA RRC message ULInformationTransferMRDC to report RLC failure }
}
(2)
with { UE in RRC_CONNECTED state with EN-DC, and, MCG(s) (E-UTRA PDCP) and SCG and SRB3 configured }
ensure that {
when { an indication from SCG RLC that the maximum number of retransmissions has been reached and when CA duplication is configured and activated and for the corresponding logical channel allowedServingCells only includes SCell(s) }
then { UE initiates the failure information procedure to report RLC failure via SRB3 }
}
8.2.6.1.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.5.3, TS 38.331, clauses 5.3.10.3, 5.7.5.2 and 5.7.5.3. Unless otherwise stated these are Rel-15 requirements.
[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:
…
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
…
1> else:
2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 38.331, clause 5.3.10.3]
The UE shall:
…
1> upon indication from SCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from SCG RLC and CA duplication is configured and activated; and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
…
[TS 38.331, clause 5.7.5.2]
A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1> upon detecting failure for an RLC bearer, in accordance with 5.3.10.3;
Upon initiating the procedure, the UE shall:
1> initiate transmission of the FailureInformation message as specified in 5.7.5.3;
[TS 38.331, clause 5.7.5.3]
The UE shall:
1> if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows:
2> set logicalChannelIdentity to the logical channel identity of the failing RLC bearer;
2> set cellGroupId to the cell group identity of the failing RLC bearer;
2> set the failureType as rlc-failure;
…
1> else if used to inform the network about a failure for an SCG RLC bearer:
2> if SRB3 is configured;
3> submit the FailureInformation message to lower layers for transmission via SRB3;
2> else;
3> if the UE is in (NG)EN-DC:
4> submit the FailureInformation message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].
…
8.2.6.1.1.1.3 Test description
8.2.6.1.1.1.3.1 Pre-test conditions
System Simulator:
– EUTRA Cell 1 is the PCell, NR Cell 1 is the PSCell, NR Cell 3 is the SCell.
UE:
– None.
Preamble:
– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (EN-DC), Bearers (MCG(s) and SCG) established according to TS 38.508-1 [4], clause 4.5.4, and with UE test loop mode A prepared, as defined in TS 38.508-1 [4], subclause 4.4A.
8.2.6.1.1.1.3.2 Test procedure sequence
Table 8.2.6.1.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionReconfiguration message to add SCell (NR Cell 3) and DRB #j for the UE. |
<– |
EUTRA RRC: RRCConnectionReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCConnectionReconfigurationComplete message |
–> |
EUTRA RRC: RRCConnectionReconfigurationComplete |
– |
– |
|
2A |
The SS transmits a SCell Activation/Deactivation MAC-CE to activate SCell (NR Cell 3). |
<– |
MAC PDU (SCell Activation/Deactivation MAC CE of one octet (C1=1)) |
– |
– |
|
3 |
The SS transmits a CLOSE UE TEST LOOP message |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
4 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
5 |
The SS stops sending SCG RLC acknowledgments for the next RLC PDU on PSCell (NR Cell 1) and SCell (NR Cell 3) |
– |
– |
– |
– |
|
6 |
The SS transmits one PDCP PDU to the UE on DRB #j. |
<– |
PDCP PDU |
– |
– |
|
– |
EXCEPTION: Steps 7-7A occur in any sequence. |
– |
– |
– |
– |
|
7 |
The UE loops back the PDCP PDU on PSCell (NR Cell 1) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
7A |
The UE loops back the PDCP PDU on SCell (NR Cell 3) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
8 |
Check: Does the UE transmit an ULInformationTransferMRDC message including FailureInformation with failureType set to ‘rlc-failure’? |
–> |
EUTRA RRC: ULInformationTransferMRDC (FailureInformation) |
1 |
P |
|
9 |
Void |
||||
|
10 |
The SS transmits an OPEN UE TEST LOOP message |
<– |
OPEN UE TEST LOOP |
– |
– |
|
11 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
12 |
The SS transmits an RRCConnectionReconfiguration message to add SRB3 and re-establish SCell RLC entity of DRB #j for the UE |
<– |
EUTRA RRC: RRCConnectionReconfiguration |
– |
– |
|
13 |
The UE transmits an RRCConnectionReconfigurationComplete message |
–> |
EUTRA RRC: RRCConnectionReconfigurationComplete |
– |
– |
|
14 |
The SS transmits a CLOSE UE TEST LOOP message |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
15 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
16 |
The SS stops sending SCG RLC acknowledgments for the next RLC PDU on PSCell (NR Cell 1) and SCell (NR Cell 3) |
– |
– |
– |
– |
|
17 |
The SS transmits one PDCP PDU to the UE on DRB #j. |
<– |
PDCP PDU |
– |
– |
|
– |
EXCEPTION: Steps 18-18A occur in any sequence. |
– |
– |
– |
– |
|
18 |
The UE loops back the PDCP PDU on PSCell (NR Cell 1)on DRB #j |
–> |
PDCP PDU |
– |
– |
|
18A |
The UE loops back the PDCP PDU on SCell (NR Cell 3) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
19 |
Check: Does the UE transmit a FailureInformation with failureType set to ‘rlc-failure’? |
–> |
NR RRC: FailureInformation |
2 |
P |
8.2.6.1.1.1.3.3 Specific message contents
Table 8.2.6.1.1.1.3.3-1: RRCConnectionReconfiguration (Step 1, Table 8.2.6.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7] Table 4.6.1-8 with Condition EN-DC_EmbedNR_RRCRecon and EN-DC_EmbedNR_RBConfig |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nr-Config-r15 CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including RRCReconfiguration |
Table 8.2.6.1.1.1.3.3-2 |
||
|
} |
||||
|
} |
||||
|
nr-RadioBearerConfig1-r15 |
OCTET STRING including RadioBearerConfig-DRB(1,0) |
Table 8.2.6.1.1.1.3.3-3 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-2: RRCReconfiguration (Table 8.2.6.1.1.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition EN-DC_SCell_add |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
secondaryCellGroup SEQUENCE { |
||||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
2 entries |
|||
|
RLC-BearerConfig[1] |
RLC-BearerConfig-1 |
entry 1 Table 8.2.6.1.1.1.3.3-5 Primary RLC |
||
|
RLC-BearerConfig[2] |
RLC-BearerConfig-2 |
entry 2 Table 8.2.6.1.1.1.3.3-6 Secondary RLC |
||
|
} |
||||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
|||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
|||
|
sCellIndex |
SCellIndex for NR Cell 3 |
|||
|
sCellConfigCommon |
ServingCellConfigCommon as per TS 38.508-1 [4] Table 4.6.3-168 |
|||
|
sCellConfigDedicated |
ServingCellConfig as per TS 38.508-1 [4] Table 4.6.3-167 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-3: RadioBearerConfig-DRB(1, 0) (Table 8.2.6.1.1.1.3.3-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.8.1-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
||
|
DRB-ToAddMod[1] SEQUENCE { |
entry 1 |
||
|
pdcp-Config |
PDCP-Config |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.1.1.3.3-4: PDCP-Config (Table 8.2.6.1.1.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCP-Config ::= SEQUENCE { |
|||
|
moreThanOneRLC SEQUENCE { |
|||
|
primaryPath SEQUENCE { |
|||
|
logicalChannel |
LogicalChannelIdentity with Condition DRB j |
j is the ID of the DRB added in Table 8.2.6.1.1.1.3.3-3, which is allocated according to internal TTCN mapping |
|
|
} |
|||
|
pdcp-Duplication |
True |
||
|
} |
|||
|
} |
|||
Table 8.2.6.1.1.1.3.3-5: RLC-BearerConfig-1 (Table 8.2.6.1.1.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j |
ID of primary logical channel |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t32 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.1.1.3.3-6: RLC-BearerConfig-2 (Table 8.2.6.1.1.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j+1 |
To ensure ID of secondary logical channel ID is different with existing logical channel and the primary logical channel |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t1 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 3 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.1.1.3.3-7: ULInformationTransferMRDC (Step 8, Table 8.2.6.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-27 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
ULInformationTransferMRDC-r15 ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
ulInformationTransferMRDC-r15 SEQUENCE { |
||||
|
ul-DCCH-MessageNR-r15 |
OCTET STRING including the FailureInformation. |
Table 8.2.6.1.1.1.3.3-7 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-8: FailureInformation (Table 8.2.6.1.1.1.3.3-7 and Step 19, Table 8.2.6.1.1.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
FailureInformation ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
failureInformation SEQUENCE { |
||||
|
failureInfoRLC-Bearer SEQUENCE { |
||||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 with condition EN-DC |
|||
|
failureType |
rlc-failure |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-9: RRCConnectionReconfiguration (Step 12, Table 8.2.6.1.1.1.3.2-1)
|
Derivation Path: TS 36.508 [7] Table 4.6.1-8 with Condition and EN-DC_EmbedNR_RBConfig |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nr-Config-r15 CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including RRCReconfiguration |
Table 8.2.6.1.1.1.3.3-10 |
||
|
} |
||||
|
} |
||||
|
nr-RadioBearerConfig1-r15 |
OCTET STRING including RadioBearerConfig according to 38.508 [4] Table 4.6.3-132 with Condition SRB3 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-10: RRCReconfiguration (Table 8.2.6.1.1.1.3.3-9)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition EN-DC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
secondaryCellGroup |
CellGroupConfig |
Table 8.2.6.1.1.1.3.3-11 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.1.1.3.3-11: CellGroupConfig (Table 8.2.6.1.1.1.3.3-10)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 with condition EN-DC |
||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
2 entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig with conditions SRB3 |
entry 1 |
|
|
RLC-BearerConfig[2] |
RLC-BearerConfig-Reest |
entry 2 |
|
|
} |
|||
|
mac-CellGroupConfig |
Not present |
||
|
physicalCellGroupConfig |
Not present |
||
|
spCellConfig |
Not present |
||
|
} |
|||
Table 8.2.6.1.1.1.3.3-12: RLC-BearerConfig-Reest (Table 8.2.6.1.1.1.3.3-11)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j+1 |
SCell RLC bearer of DRB #j |
|
|
servedRadioBearer |
Not present |
||
|
reestablishRLC |
true |
||
|
rlc-Config |
Not present |
||
|
mac-LogicalChannelConfig |
Not present |
||
|
} |
|||
8.2.6.1.1.2 Failure information / RLC failure / SCG / EN-DC / Inter-band CA
8.2.6.1.1.2.1 Test Purpose (TP)
Same as TC 8.2.6.1.1.1 but applied to Inter-band CA case.
8.2.6.1.1.2.2 Conformance requirements
Same as TC 8.2.6.1.1.1 but applied to Inter-band CA case.
8.2.6.1.1.2.3 Test description
8.2.6.1.1.2.3.1 Pre-test conditions
Same as test case 8.2.6.1.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 replaces NR Cell 3.
8.2.6.1.1.2.3.2 Test procedure sequence
Same as test case 8.2.6.1.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 replaces NR Cell 3.
8.2.6.1.1.2.3.3 Specific message contents
Same as test case 8.2.6.1.1.1 with the following differences.
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 replaces NR Cell 3.
8.2.6.1.1.3 Failure information / RLC failure / SCG / EN-DC / Intra-band non Contiguous CA
8.2.6.1.1.3.1 Test Purpose (TP)
Same as TC 8.2.6.1.1.1 but applied to Intra-band non Contiguous CA case.
8.2.6.1.1.3.2 Conformance requirements
Same as TC 8.2.6.1.1.1 but applied to Intra-band non Contiguous CA case.
8.2.6.1.1.3.3 Test description
8.2.6.1.1.3.3.1 Pre-test conditions
Same as test case 8.2.6.1.1.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.2.6.1.1.3.3.2 Test procedure sequence
Same as test case 8.2.6.1.1.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.2.6.1.1.3.3.3 Specific message contents
Same as test case 8.2.6.1.1.1 but applied to Intra-band non Contiguous CA case.
8.2.6.1.2 Failure information / RLC failure / SCG / NR-DC
8.2.6.1.2.1 Failure information / RLC failure / SCG / NR-DC / Intra-band Contiguous CA
8.2.6.1.2.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state with NR-DC, and SCG }
ensure that {
when { an indication from SCG RLC that the maximum number of retransmissions has been reached and when CA duplication is configured and activated and for the corresponding logical channel allowedServingCells only includes SCell(s) }
then { UE sends the FailureInformation message embedded in ULInformationTransferMRDC to report RLC failure for the SCG }
}
(2)
with { UE in NR RRC_CONNECTED state with NR-DC, and SRB3 configured }
ensure that {
when { an indication from SCG RLC that the maximum number of retransmissions has been reached and when CA duplication is configured and activated and for the corresponding logical channel allowedServingCells only includes SCell(s) }
then { UE sends the FailureInformation message over SRB3 to report RLC failure for the SCG }
}
8.2.6.1.2.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.5.3, TS 38.331, clauses 5.3.10.3, 5.7.5.2 and 5.7.5.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
…
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:
2> if the mrdc-SecondaryCellGroupConfig is set to setup:
3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:
4> perform MR-DC release as specified in clause 5.3.5.10;
3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:
4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;
…
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
…
1> set the content of the RRCReconfigurationComplete message as follows:
…
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
3> include in the nr-SCG-Response the RRCReconfigurationComplete message;
…
1> else if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration via SRB1):
2> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
2> else
3> the procedure ends;
NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):
2> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
1> else (RRCReconfiguration was received via SRB1):
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
…
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a Random Access procedure triggered above;
2> stop timer T304 for that cell group;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
…
[TS 38.331, clause 5.3.10.3]
The UE shall:
…
1> upon indication from SCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from SCG RLC and CA duplication is configured and activated; and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.5 to report RLC failure.
…
[TS 38.331, clause 5.7.5.2]
A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1> upon detecting failure for an RLC bearer, in accordance with 5.3.10.3;
Upon initiating the procedure, the UE shall:
1> initiate transmission of the FailureInformation message as specified in 5.7.5.3;
[TS 38.331, clause 5.7.5.3]
The UE shall:
1> if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows:
2> set logicalChannelIdentity to the logical channel identity of the failing RLC bearer;
2> set cellGroupId to the cell group identity of the failing RLC bearer;
2> set the failureType as rlc-failure;
…
1> else if used to inform the network about a failure for an SCG RLC bearer:
2> if SRB3 is configured;
3> submit the FailureInformation message to lower layers for transmission via SRB3;
2> else;
…
3> else if the UE is in NR-DC:
4> submit the FailureInformation message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
…
8.2.6.1.2.1.3 Test description
8.2.6.1.2.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell, NR Cell 10 is the PSCell, NR Cell 28 is the SCG SCell.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
– None.
Preamble:
– The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC) according to TS 38.508-1 [4], Table 4.5.1-1, and with UE test loop mode A prepared, as defined in TS 38.508-1 [4], subclause 4.4A.
8.2.6.1.2.1.3.2 Test procedure sequence
Table 8.2.6.1.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfiguration message to add SCG SCell (NR Cell 28) and reconfigure SCG DRB #j with PDCP duplication for the UE. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCReconfigurationComplete message |
–> |
RRCReconfigurationComplete |
– |
– |
|
3 |
The SS transmits a SCell Activation/Deactivation MAC-CE on PSCell (NR Cell 10) to activate SCG SCell (NR Cell 28). |
<– |
MAC PDU (SCell Activation/Deactivation MAC CE of one octet (C1=1)) |
– |
– |
|
4 |
The SS transmits a CLOSE UE TEST LOOP message |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
5 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
6 |
The SS stops sending SCG RLC acknowledgments for the next RLC PDU on PSCell (NR Cell 10) and SCell (NR Cell 28) |
– |
– |
– |
– |
|
7 |
The SS transmits one PDCP PDU to the UE on DRB #j. |
<– |
PDCP PDU |
– |
– |
|
– |
EXCEPTION: Steps 8-9 occur in any sequence. |
– |
– |
– |
– |
|
8 |
The UE loops back the PDCP PDU on PSCell (NR Cell 10) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
9 |
The UE loops back the PDCP PDU on SCell (NR Cell 28) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
10 |
Check: Does the UE transmit an ULInformationTransferMRDC message including FailureInformation with failureType set to ‘rlc-failure’? |
–> |
ULInformationTransferMRDC (FailureInformation) |
1 |
P |
|
11 |
The SS transmits an OPEN UE TEST LOOP message |
<– |
OPEN UE TEST LOOP |
– |
– |
|
12 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
13 |
The SS transmits an RRCReconfiguration message to establish SRB3 for the UE |
<– |
RRCReconfiguration |
– |
– |
|
14 |
The UE transmits an RRCReconfigurationComplete message |
–> |
RRCReconfigurationComplete |
– |
– |
|
15 |
The SS transmits a CLOSE UE TEST LOOP message |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
16 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
17 |
The SS stops sending SCG RLC acknowledgments for the next RLC PDU on PSCell (NR Cell 10) and SCell (NR Cell 28) |
– |
– |
– |
– |
|
18 |
The SS transmits one PDCP PDU to the UE on DRB #j. |
<– |
PDCP PDU |
– |
– |
|
– |
EXCEPTION: Steps 19-20 occur in any sequence. |
– |
– |
– |
– |
|
19 |
The UE loops back the PDCP PDU on PSCell (NR Cell 10)on DRB #j |
–> |
PDCP PDU |
– |
– |
|
20 |
The UE loops back the PDCP PDU on SCell (NR Cell 28) on DRB #j |
–> |
PDCP PDU |
– |
– |
|
21 |
Check: Does the UE transmit a FailureInformation with failureType set to ‘rlc-failure’? |
–> |
FailureInformation |
2 |
P |
8.2.6.1.2.1.3.3 Specific message contents
Table 8.2.6.1.2.1.3.3-1: RRCReconfiguration (Step 1, Table 8.2.6.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
mrdc-SecondaryCellGroupConfig CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
mrdc-SecondaryCellGroup CHOICE { |
||||
|
nr-SCG |
RRCReconfiguration-SCG |
OCTET STRING (CONTAINING RRCReconfiguration) Table 8.2.6.1.2.1.3.3-2 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
radioBearerConfig2 |
RadioBearerConfig-DRB(1, 0) |
OCTET STRING (CONTAINING RadioBearerConfig) Table 8.2.6.1.2.1.3.3-3 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-2: RRCReconfiguration-SCG (Table 8.2.6.1.2.1.3.3-1)
|
Derivation Path: TS 38.331 [6], clause 6.2.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig |
Not present |
|||
|
secondaryCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) Table 8.2.6.1.2.1.3.3-4 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-3: RadioBearerConfig-DRB(1, 0) (Table 8.2.6.1.2.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.8.1-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
||
|
DRB-ToAddMod[1] SEQUENCE { |
entry 1 |
||
|
pdcp-Config |
PDCP-Config |
Table 8.2.6.1.2.1.3.3-5 |
|
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.2.1.3.3-4: CellGroupConfig (Table 8.2.6.1.2.1.3.3-2)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition SCell_add |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 condition NR-DC_SCG |
||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..max LC-ID)) OF RLC-BearerConfig { |
2 entries |
||
|
RLC-BearerConfig[1] |
RLC-BearerConfig-1 |
entry 1 Table 8.2.6.1.2.1.3.3-6 Primary RLC |
|
|
RLC-BearerConfig[2] |
RLC-BearerConfig-2 |
entry 2 Table 8.2.6.1.2.1.3.3-7 Secondary RLC |
|
|
} |
|||
|
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
|
SCellConfig[1] SEQUENCE { |
entry 1 |
||
|
sCellIndex |
SCellIndex for NR Cell 28 |
||
|
sCellConfigCommon |
ServingCellConfigCommon as per TS 38.508-1 [4] Table 4.6.3-168 |
||
|
sCellConfigDedicated |
ServingCellConfig as per TS 38.508-1 [4] Table 4.6.3-167 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.2.1.3.3-5: PDCP-Config (Table 8.2.6.1.2.1.3.3-3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-99 with condition Split |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCP-Config ::= SEQUENCE { |
|||
|
moreThanOneRLC SEQUENCE { |
|||
|
primaryPath SEQUENCE { |
|||
|
cellGroup |
1 |
SCG Cell Group Id |
|
|
logicalChannel |
LogicalChannelIdentity with Condition DRB j |
j is the ID of the SCG DRB, which is allocated according to internal TTCN mapping |
|
|
} |
|||
|
pdcp-Duplication |
True |
||
|
} |
|||
|
} |
|||
Table 8.2.6.1.2.1.3.3-6: RLC-BearerConfig-1 (Table 8.2.6.1.2.1.3.3-4)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j |
ID of primary logical channel |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t32 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 10 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.2.1.3.3-7: RLC-BearerConfig-2 (Table 8.2.6.1.2.1.3.3-4)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-148 with Condition AM |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RLC-BearerConfig ::= SEQUENCE { |
|||
|
logicalChannelIdentity |
LogicalChannelIdentity with condition DRB j+1 |
To ensure ID of secondary logical channel ID is different with existing logical channel and the primary logical channel |
|
|
servedRadioBearer CHOICE { |
|||
|
drb-Identity |
DRB-Identity with condition DRB j |
||
|
} |
|||
|
rlc-Config CHOICE { |
|||
|
am SEQUENCE { |
|||
|
ul-AM-RLC SEQUENCE { |
|||
|
maxRetxThreshold |
t1 |
To ensure RLC failure happens before RLF |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
mac-LogicalChannelConfig SEQUENCE { |
|||
|
ul-SpecificParameters SEQUENCE { |
|||
|
allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex { |
1 entry |
||
|
ServCellIndex[1] |
ServCellIndex of NR Cell 28 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.1.2.1.3.3-8: ULInformationTransferMRDC (Step 10, Table 8.2.6.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-34 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
ULInformationTransferMRDC ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
ulInformationTransferMRDC SEQUENCE { |
||||
|
ul-DCCH-MessageNR |
OCTET STRING including the FailureInformation. |
Table 8.2.6.1.2.1.3.3-9 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-9: FailureInformation (Table 8.2.6.1.2.1.3.3-8 and Step 21, Table 8.2.6.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
FailureInformation ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
failureInformation SEQUENCE { |
||||
|
failureInfoRLC-Bearer SEQUENCE { |
||||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 with condition NR-DC_SCG |
|||
|
failureType |
rlc-failure |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-10: RRCReconfiguration (step 13, Table 8.2.6.1.2.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup |
Not present |
|||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
mrdc-SecondaryCellGroupConfig CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
mrdc-SecondaryCellGroup CHOICE { |
||||
|
nr-SCG |
RRCReconfiguration-SCG |
OCTET STRING (CONTAINING RRCReconfiguration) Table 8.2.6.1.2.1.3.3-11 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
radioBearerConfig2 |
RadioBearerConfig as per TS 38.508-1 [4] Table 4.6.3-132 with condition SRB3 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-11: RRCReconfiguration-SCG (Table 8.2.6.1.2.1.3.3-10)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig |
Not present |
|||
|
secondaryCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING RRCReconfiguration) Table 8.2.6.1.2.1.3.3-12 |
||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.1.2.1.3.3-12: CellGroupConfig (Table 8.2.6.1.2.1.3.3-12)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
|||
|
cellGroupId |
CellGroupId as per TS 38.508-1 [4] Table 4.6.3-20 condition NR-DC_SCG |
||
|
rlc-BearerToAddModList SEQUENCE (SIZE(1..max LC-ID)) OF RLC-BearerConfig { |
1 entry |
||
|
RLC-Bearer-Config[1] |
RLC-BearerConfig as per TS 38.508-1 [4] Table 4.6.3-148 with condition SRB3 |
entry 1 |
|
|
} |
|||
|
mac-CellGroupConfig |
Not Present |
||
|
physicalCellGroupConfig |
Not Present |
||
|
spCellConfig |
Not Present |
||
|
} |
|||
8.2.6.1.2.2 Failure information / RLC failure / SCG / NR-DC / Inter-band CA
8.2.6.1.2.2.1 Test Purpose (TP)
Same as TC 8.2.6.1.2.1 but applied to Inter-band CA case.
8.2.6.1.2.2.2 Conformance requirements
Same as TC 8.2.6.1.2.1 but applied to Inter-band CA case.
8.2.6.1.2.2.3 Test description
8.2.6.1.2.2.3.1 Pre-test conditions
Same as test case 8.2.6.1.2.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 and NR Cell 28 are in the different band.
8.2.6.1.2.2.3.2 Test procedure sequence
Same as test case 8.2.6.1.2.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 and NR Cell 28 are in the different band.
8.2.6.1.2.2.3.3 Specific message contents
Same as test case 8.2.6.1.2.1 with the following differences.
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 and NR Cell 28 are in the different band.
8.2.6.1.2.3 Failure information / RLC failure / SCG / NR-DC / Intra-band non Contiguous CA
8.2.6.1.2.3.1 Test Purpose (TP)
Same as TC 8.2.6.1.2.1 but applied to Intra-band non Contiguous CA case.
8.2.6.1.2.3.2 Conformance requirements
Same as TC 8.2.6.1.2.1 but applied to Intra-band non Contiguous CA case.
8.2.6.1.2.3.3 Test description
8.2.6.1.2.3.3.1 Pre-test conditions
Same as test case 8.2.6.1.2.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.2.6.1.2.3.3.2 Test procedure sequence
Same as test case 8.2.6.1.2.1 with the following differences:
– CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
8.2.6.1.2.3.3.3 Specific message contents
Same as test case 8.2.6.1.2.1 but applied to Intra-band non Contiguous CA case.
8.2.6.2 Processing delay
8.2.6.2.1 Processing delay / PSCell addition / SCG DRB / Success / Latency check / EN-DC
8.2.6.2.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an RRCConnectionReconfiguration message to add PSCell with SCG DRB and after 20 subframes receives an UL grant }
then { UE successfully configures the PSCell with SCG DRB and sends an RRCConnectionReconfigurationComplete message }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives an UECapabilityEnquiry message requesting eutra-nr capabilities and after 80 subframes receives an UL grant }
then { UE successfully transmits an UECapabilityInformation message }
}
8.2.6.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.3, , TS 38.331, clauses 5.3.10.3, 5.7.3.2, 5.7.3.3. Unless otherwise stated these are Rel-15 requirements.
[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:
…
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
…
1> set the content of RRCConnectionReconfigurationComplete message as follows:
…
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;
…
1> else:
2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;
[TS 36.331, clause 5.6.3.3]
The UE shall:
…
1> else, set the contents of UECapabilityInformation message as follows:
…
2> if the ue-CapabilityRequest includes eutra-nr and if the UE supports (NG)EN-DC or NE-DC:
3> include the UE radio access capabilities for EUTRA-NR within a ue-CapabilityRAT-Container, with the rat-Type set to eutra-nr;
3> include band combinations as specified in TS 38.331 [82], clause 5.6.1.4, considering the included requestedFreqBandsNR-MRDC, requestedCapabilityNR (if present) and requestedCapabilityCommon (if included);
1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 11.2]
The UE performance requirements for RRC procedures are specified in the following tables, by means of a value N:
N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation).
NOTE: No processing delay requirements are specified for RN-specific procedures.
Figure 11.2-1: Illustration of RRC procedure delay
Table 11.2-1: UE performance requirements for RRC procedures for UEs other than NB-IoT UEs
|
Procedure title |
E-UTRAN -> UE |
UE -> E-UTRAN |
N |
Notes |
|---|---|---|---|---|
|
RRC Connection Control Procedures |
||||
|
RRC connection reconfiguration (NR SCG establishment/ /modification/release) |
RRCConnectionReconfiguration |
RRCConnectionReconfigurationComplete |
20 |
|
|
Other procedures |
||||
|
UE capability transfer |
UECapabilityEnquiry |
UECapabilityInformation |
10/ 80 |
N = 80 applies in case the UE has to report at least one of the following UE capabilities. – MR-DC band combinations. – NR band combinations – EUTRA feature sets |
8.2.6.2.1.3 Test description
8.2.6.2.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 state RRC_CONNECTED using generic procedure parameter Connectivity (E-UTRA/EPC) established and Test Loop Function (On) with UE test loop mode B according to TS 38.508-1 [4], clause 4.5.4.
8.2.6.2.1.3.2 Test procedure sequence
Table 8.2.6.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionReconfiguration message to add PSCell with SCG DRB |
<– |
E-UTRA RRC: RRCConnectionReconfiguration |
– |
– |
|
2 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes after successful completion of step 1? (Note 2) |
–> |
E-UTRA RRC: RRCConnectionReconfigurationComplete |
1 |
P |
|
2A |
Void |
– |
– |
– |
– |
|
3 |
The SS sends E-UTRA RRC UECapabilityEnquiry message including RAT-Type eutra-nr. |
<– |
E-UTRA RRC: UECapabilityEnquiry |
||
|
4 |
Check: Does the UE transmit an E-UTRA RRC UECapabilityInformation message within 85 (FDD)/88 (TDD) subframes after successful completion of step 3? (Note 2) |
–> |
E-UTRA RRC: UECapabilityInformation |
2 |
P |
|
Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1. Note 2: 5 (FDD) / 8 (TDD) subframes is added on top of RRC processing delay requirement, because UL grant is allocated for the next subframe after RRC procedure delay and because of transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant. |
|||||
8.2.6.2.1.3.3 Specific message contents
Table 8.2.6.2.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.6.2.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-8 with Condition SCG-DRB(1,1) |
Table 8.2.6.2.1.3.3-2: UECapabilityEnquiry (step 3, Table 8.2.6.2.1.3.2-1)
|
Derivation Path: TS 36.508 [7], Table 4.6.1-22 with Condition EN-DC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
UECapabilityEnquiry ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
ueCapabilityEnquiry-r8 SEQUENCE { |
||||
|
ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF RAT-Type { |
1 entry |
|||
|
RAT-Type[1] |
eutra-nr |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
8.2.6.2.2 Processing delay / Latency check / NR-DC
8.2.6.2.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message with nr-SCG IE to add an SCG and after 16ms receives an UL grant }
then { UE successfully transmits RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_INACTIVE state and has sent an RRCResumeRequest message }
ensure that {
when { UE receives RRCResume message and after 10ms receives an UL grant }
then { UE successfully transmits RRCResumeComplete message }
}
8.2.6.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.5.3, 12. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO or CPC):
…
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> if the mrdc-SecondaryCellGroupConfig is set to setup:
1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:
2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;
…
3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:
4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;
1> set the content of the RRCReconfigurationComplete message as follows:
…
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
3> include in the nr-SCG-Response the RRCReconfigurationComplete message
…
1> else (RRCReconfiguration was received via SRB1):
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
[TS 38.331, clause 12]
The UE performance requirements for RRC procedures are specified in the following tables. The performance requirement is expressed as the time in [ms] from the end of reception of the network -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation). In case the RRC procedure triggers BWP switching, the RRC procedure delay is the value defined in the following table plus the BWP switching delay defined in TS 38.133 [14], clause 8.6.3.
Figure 12.1-1: Illustration of RRC procedure delay
Table 12.1-1: UE performance requirements for RRC procedures for UEs
|
Procedure title: |
Network -> UE |
UE -> Network |
Value [ms] |
Notes |
|---|---|---|---|---|
|
RRC Connection Control Procedures |
||||
|
RRC reconfiguration (SCG establishment/ modification/ release) |
RRCReconfiguration |
RRCReconfigurationComplete |
16 |
|
|
RRC resume |
RRCResume |
RRCResumeComplete |
6 or 10 |
Value=6 applies for a UE supporting reduced CP latency for the case of RRCResume message only including MAC and PHY configuration, reestablishPDCP and reestablishRLC for SRB2 and DRB(s), and no DRX, SPS, configured grant, CA or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRCResumeComplete and the data is transmitted over common search space with DCI format 0_0. In this scenario, the RRC procedure delay [ms] can extend beyond the reception of the UL grant, up to 7 ms. For other cases, Value = 10 applies. |
8.2.6.2.2.3 Test description
8.2.6.2.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell and NR Cell 10 is the PSCell.
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
– None.
Preamble:
– The UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR), according to TS 38.508-1 [4], clause 4.5.4.
8.2.6.2.2.3.2 Test procedure sequence
Table 8.2.6.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS stops default uplink grant transmission. |
– |
– |
– |
– |
|
2 |
The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add NR PSCell with SCG DRB. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT |
– |
– |
|
3 |
The SS starts transmitting a periodic DCI (16∙2μ+1+TDL) slots after step 2 to schedule PUSCH. (Note 1, Note 2) |
– |
– |
– |
– |
|
4 |
Check: Does the UE transmit an RRCReconfigurationComplete message within (16∙2μ+1+TDL+K2) slots after successful completion of step 2? (Note 1, Note 2, Note 3) |
–> |
RRCReconfigurationComplete |
1 |
P |
|
5 |
The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
– |
|
– |
EXCEPTION: Steps 6a1 to 6a7 describe behaviour that depends on UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported |
– |
– |
– |
– |
|
6a1 |
IF pc_inactiveState THEN the SS transmits an RRCRelease message with suspendConfig. |
<– |
NR RRC: RRCRelease |
– |
– |
|
6a2 |
Wait 1s to let UE enter RRC_INACTIVE state. |
– |
– |
– |
– |
|
6a3 |
The SS transmits a Paging message including a matched ng-5G-S-TMSI. |
<– |
NR RRC: Paging |
– |
– |
|
6a4 |
The UE transmits an RRCResumeRequest message. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
6a5 |
The SS transmits an RRCResume message for the UE |
<– |
NR RRC: RRCResume |
– |
– |
|
6a6 |
The SS starts transmitting a periodic DCI from (10∙2μ+1+TDL) slots after step 6a5 to schedule PUSCH. (Note 1, Note 2) |
||||
|
6a7 |
Check: Does the UE transmit an RRCResumeComplete message within (10∙2μ+1+TDL+K2) slots after successful completion of step 6a5? (Note 1, Note 2, Note 3) |
–> |
NR RRC: RRCResumeComplete |
2 |
P |
|
Note 1: TDL is the delay in slots to the next available DL slot suitable for the transmission of a DCI. Note 2: μ is the SCS index. μ = 0/1/2/3 for SCS = 15kHz/30kHz/60kHz/120kHz respectively. Note 3: K2 is the offset (in slots) between DCI and the PUSCH it scheduled. |
|||||
8.2.6.2.2.3.3 Specific message contents
Table 8.2.6.2.2.3.3-1: RRCReconfiguration (step 2, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR-DC |
Table 8.2.6.2.2.3.3-2: PDU SESSION MODIFICATION COMMAND (step 2, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.7.2-9. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST associated with the Internet PDU session if available or with the first PDU session |
|||
|
Authorized QoS rules |
One entry |
|||
|
QoS rule [1] |
Reference QoS rule #5 as defined in TS 38.508-1 [4], Table 4.8.2.1-5. |
QFI=5 |
||
|
Authorized QoS flow descriptions |
One entry |
|||
|
QoS flow [1] |
Reference QoS flow #5 as defined in TS 38.508-1 [4], Table 4.8.2.3-5. |
QFI=5 |
||
Table 8.2.6.2.2.3.3-3: RRCReconfigurationComplete (step 5, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508 [4], Table 4.6.1-14 with condition NR-DC |
Table 8.2.6.2.2.3.3-4: Paging (step 1, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME |
Table 8.2.6.2.2.3.3-5: RRCResume (step 6a5, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-17 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCResume ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
|||
|
criticalExtensions CHOICE { |
||||
|
rrcResume SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
radioBearerConfig2 |
RadioBearerConfig according to Table 8.2.6.3.2.3.3-7 |
|||
|
sk-Counter |
0 |
|||
|
nonCriticalExtension SEQUENCE{ |
||||
|
idleModeMeasurementReq-r16 |
Not Present |
|||
|
restoreMCG-SCells-r16 |
Not Present |
|||
|
restoreSCG-r16 |
True |
|||
|
mrdc-SecondaryCellGroup-r16 CHOICE{ |
||||
|
nr-SCG-r16 |
According to TS 38.508-1[4], Table 4.6.1-13 with condition NR-DC_SCG |
|||
|
eutra-SCG-r16 |
Not Present |
|||
|
} |
||||
|
needForGapsConfigNR-r16 |
Not Present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.3.2.3.3-6: RRCResumeComplete (step 6a7, Table 8.2.6.2.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-18 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCResumeComplete ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
|||
|
criticalExtensions CHOICE { |
||||
|
rrcResumeComplete SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
idleMeasAvailable-r16 |
Not Present |
|||
|
measResultIdleEUTRA-r16 |
Not Present |
|||
|
measResultIdleNR-r16 |
Not Present |
|||
|
scg-Response-r16 CHOICE{ |
||||
|
nr-SCG-Response |
RRCReconfigurationComplete defined as per TS 38.508-1[4] Table 4.6.1-14 with condition NR-DC |
|||
|
eutra-SCG-Response |
Not Present |
|||
|
} |
||||
|
ue-MeasurementsAvailable-r16 |
Not Present |
|||
|
mobilityHistoryAvail-r16 |
Not Present |
|||
|
mobilityState-r16 |
Not Present |
|||
|
needForGapsInfoNR-r16 |
Not Present |
|||
|
nonCriticalExtension |
Not Present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.2.6.3.2.3.3-7: RadioBearerConfig (Table 8.2.6.2.2.3.3-5)
|
Derivation Path: TS 38.508 [4], Table 4.6.3-132 with condition DRBn and SecondaryKeys |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
||
|
DRB-ToAddMod SEQUENCE { |
|||
|
cnAssociation |
Not present |
||
|
drb-Identity |
DRB-Identity using condition DRBn |
n set to the SCG DRB identity |
|
|
reestablishPDCP |
True |
||
|
recoverPDCP |
Not present |
||
|
pdcp-Config |
Not present |
||
|
daps-Config-r16 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
8.2.6.3 Idle/Inactive measurements
8.2.6.3.3 Idle/Inactive measurements / Inactive mode / NE-DC / SIB11 configuration
8.2.6.3.3.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 including measIdleCarrierListEUTRA }
then { UE enters RRC_INACTIVE state, performs measurements on E-UTRA cells and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, SIB11 including measIdleCarrierListEUTRA, T331 expires }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and suspendConfig, SIB11 does not include measIdleCarrierListEUTRA }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state due to missing configuration }
}
8.2.6.3.3.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clauses 5.3.8.3, 5.7.8.3, 5.7.8.1a and 5.7.8.2a. Unless otherwise stated, these are Rel-16 requirements.
[TS 38.331, clause 5.3.8.3]
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
3> if the measIdleConfig contains measIdleCarrierListEUTRA:
4> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;
[TS 38.331, clause 5.7.8.3]
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.8.1a]
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message:
2> if the UE supports idleInactiveEUTRA-MeasReport:
3> if the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA:
4> store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;
3> else:
4> remove the measIdleCarrierListEUTRA in VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListEUTRA and the SIB1 contains idleModeMeasurementsEUTRA:
3> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:
4> if UE supports NE-DC between the serving carrier and the carrier frequency indicated by carrierFreqEUTRA within the corresponding entry:
5> perform measurements in the carrier frequency and bandwidth indicated by carrierFreqEUTRA and allowedMeasBandwidth within the corresponding entry;
5> if the reportQuantitiesEUTRA is set to rsrq:
6> consider RSRQ as the sorting quantity;
5> else:
6> consider RSRP as the sorting quantity;
5> if the measCellListEUTRA is included:
6> consider cells identified by each entry within the measCellListEUTRA to be applicable for idle/inactive mode measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive measurement results for the measurement quantities indicated by reportQuantitiesEUTRA;
5> store the derived measurement results as indicated by reportQuantitiesEUTRA within the measReportIdleEUTRA in VarMeasIdleReport in decreasing order of the sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThresholdEUTRA is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThresholdEUTRA;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
8.2.6.3.3.3 Test Description
8.2.6.3.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, serving cell. System information combination NR-7 defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used together with SIB 11.
– E-UTRA Cell 1, suitable for inter-frequency measurements. System information combination 31 as defined in 36.508 [7] clause 4.4.3.1.1.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.2.6.3.3.3.2 Test procedure sequence
Table 8.2.6.3.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 66 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
3 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
4 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
5 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
6 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
7 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
8 |
Check: Does the UE transmit UEInformationResponse including measResultIdleEutra? |
–> |
NR RRC: UEInformationResponse |
1 |
P |
|
9 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
10 |
Wait for 130 s for UE to enter RRC_INACTIVE mode and T331 to expire. |
– |
– |
– |
– |
|
11 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
12 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
13 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
14 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
15 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
16 |
Check: Does the UE transmit UEInformationResponse without measResultIdleEUTRA? |
–> |
NR RRC: UEInformationResponse |
2 |
P |
|
17 |
The SS removes measIdleCarrierListEUTRA in SIB11. |
– |
– |
– |
– |
|
18 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
19 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
20 |
The SS transmits RRCRelease message including measIdleConfig and suspendConfig to the UE. |
<– |
NR RRC: RRCRelease |
– |
– |
|
21 |
Wait for 66 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
22 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
23 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
24 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
25 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
26 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<– |
NR RRC: UEInformationRequest |
– |
– |
|
27 |
Check: Does the UE transmit UEInformationResponse without measResultIdleEUTRA? |
–> |
NR RRC: UEInformationResponse |
3 |
P |
8.2.6.3.3.3.3 Specific message contents
Table 8.2.6.3.3.3.3-1: RRCRelease (steps 1, 13 and 28, Table 8.2.6.3.3.3.2-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-16 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCRelease ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
rrcRelease SEQUENCE { |
|||
|
suspendConfig |
SuspendConfig |
||
|
nonCriticalExtensions SEQUENCE { |
|||
|
nonCriticalExtensions SEQUENCE { |
|||
|
measIdleConfig-r16 SetupRelease { |
|||
|
setup |
MeasIdleConfigDedicated |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.3.3.3.3-2: SuspendConfig (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.331 [12], clause 6.2.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SuspendConfig ::= SEQUENCE { |
|||
|
fullI-RNTI |
I-RNTI-Value |
38.508-1[4] Table 4.6.3-64 |
|
|
shortI-RNTI |
ShortI-RNTI-Value |
38.508-1[4] Table 4.6.3-170 |
|
|
ran-PagingCycle |
rf32 |
||
|
ran-NotificationAreaInfo CHOICE { |
|||
|
cellList SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell { |
2 entries |
||
|
PLMN-RAN-AreaCell[1] SEQUENCE { |
entry 1 |
||
|
plmn-Identity |
PLMN1 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of NR Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
PLMN-RAN-AreaCell[2] SEQUENCE { |
entry 2 |
||
|
plmn-Identity |
PLMN2 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of E-UTRA Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
t380 |
Not Present |
||
|
nextHopChainingCount |
NextHopChainingCount |
38.508-1[4] Table 4.6.3-83 |
|
|
} |
|||
Table 8.2.6.3.3.3.3-3: MeasIdleConfigDedicated (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.331 [12], clause 6.3.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r16 ::= SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not Present |
||
|
measIdleCarrierListEUTRA-r16 |
Not Present |
||
|
measIdleDuration-r16 |
sec120 |
||
|
validityAreaList-r16 |
Not Present |
||
|
} |
|||
Table 8.2.6.3.3.3.3-4: RRCResumeRequest (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-19 |
Table 8.2.6.3.3.3.3-5: RRCResume (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-17 |
Table 8.2.6.3.3.3.3-6: RRCResumeComplete (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-18 |
Table 8.2.6.3.3.3.3-7: SIB11 (Table 8.2.6.3.3.3.3-1, steps 1 to 16)
|
Derivation Path: TS 38.331 [12], clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB11-r16 ::= SEQUENCE { |
|||
|
measIdleConfigSIB-r16 SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not Present |
||
|
measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 { |
1 entry |
||
|
MeasIdleCarrierEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
carrierFreqEUTRA-r16 |
ARFCN value corresponding to E-UTRA cell 1 |
||
|
allowedMeasBandwidth-r16 |
mbw50 |
||
|
measCellListEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange { |
1 entry |
||
|
EUTRA-PhysCellIdRange[1] SEQUENCE { |
entry 1 |
||
|
start |
EUTRA-PhysCellId corresponding to E-UTRA cell 1 |
||
|
} |
|||
|
} |
|||
|
reportQuatitiesEUTRA-r16 |
both |
||
|
qualityThresholdEUTRA-r16 |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.3.3.3.3-8: SIB11 (Table 8.2.6.3.3.3.3-1, steps 17 to 27)
|
Derivation Path: TS 38.331 [12], clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB11-r16 ::= SEQUENCE { |
|||
|
measIdleConfigSIB-r16 SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not Present |
||
|
measIdleCarrierListEUTRA-r16 |
Not Present |
||
|
} |
|||
|
} |
|||
Table 8.2.6.3.3.3.3-9: UEInformationRequest (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32A with condition IDLE |
Table 8.2.6.3.3.3.3-10: UEInformationResponse (Table 8.2.6.3.3.3.3-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32B |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UEInformationResponse-r16 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
ueInformationResponse-r16 SEQUENCE { |
|||
|
measResultIdleEUTRA-r16 SEQUENCE { |
|||
|
measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16 { |
1 entry |
||
|
MeasResultsPerCarrierIdleEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
carrierFreqEUTRA-r16 |
ARFCN value corresponding to E-UTRA cell 1 |
||
|
measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16 { |
1 entry |
||
|
MeasResultsPerCellIdleEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
eutra-PhysCellId-r16 |
EUTRA-PhysCellId corresponding to E-UTRA cell 1 |
||
|
measIdleResultEUTRA-r16 SEQUENCE { |
|||
|
rsrp-ResultEUTRA-r16 |
INTEGER (0..97) |
||
|
rsrq-ResultEUTRA-r16 |
INTEGER (0..34) |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.2.6.3.4 Idle/Inactive measurements / Inactive mode / NE-DC / RRCRelease configuration
8.2.6.3.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including suspendConfig and measIdleConfig with measIdleCarrierListEUTRA }
then { UE enters RRC_INACTIVE state, performs measurements on E-UTRA cells and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including suspendConfig and measIdleConfig with measIdleCarrierListEUTRA, T331 expires }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including suspendConfig and measIdleConfig without measIdleCarrierListEUTRA }
then { UE enters RRC_INACTIVE state, UE does not report measurement results in RRC_CONNECTED state due to missing configuration }
}
8.2.6.3.4.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clauses 5.3.8.3, 5.7.8.1, 5.7.8.1a, 5.7.8.2a, 5.7.8.3 and 5.7.10.3. Unless otherwise stated, these are Rel-16 requirements.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
3> if the measIdleConfig contains measIdleCarrierListEUTRA:
4> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if the VarMeasIdleConfig includes the measIdleCarrierListEUTRA and the SIB1 contains idleModeMeasurementsEUTRA:
3> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:
4> if UE supports NE-DC between the serving carrier and the carrier frequency indicated by carrierFreqEUTRA within the corresponding entry:
5> perform measurements in the carrier frequency and bandwidth indicated by carrierFreqEUTRA and allowedMeasBandwidth within the corresponding entry;
5> if the reportQuantitiesEUTRA is set to rsrq:
6> consider RSRQ as the sorting quantity;
5> else:
6> consider RSRP as the sorting quantity;
5> if the measCellListEUTRA is included:
6> consider cells identified by each entry within the measCellListEUTRA to be applicable for idle/inactive mode measurement reporting;
5> else:
6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;
5> for all cells applicable for idle/inactive measurement reporting, derive measurement results for the measurement quantities indicated by reportQuantitiesEUTRA;
5> store the derived measurement results as indicated by reportQuantitiesEUTRA within the measReportIdleEUTRA in VarMeasIdleReport in decreasing order of the sorting quantity, i.e. the best cell is included first, as follows:
6> if qualityThresholdEUTRA is configured:
7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThresholdEUTRA;
6> else:
7> include the measurement results from all cells applicable for idle/inactive measurement reporting;
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available;
2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;
8.2.6.3.4.3 Test Description
8.2.6.3.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, serving cell. System information combination NR-7 defined in TS 38.508-1 [4] clause 4.4.3.1.2.
– E-UTRA Cell 1, suitable for inter-frequency measurements. System information combination 31 as defined in 36.508 [7] clause 4.4.3.1.1.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.2.6.3.4.3.2 Test procedure sequence
Table 8.2.6.3.4.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including suspendConfig and measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 66 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
3 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
4 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
5 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
6 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
7 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
8 |
Check: Does the UE transmit UEInformationResponse including measResultIdleEUTRA? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
9 |
The SS transmits RRCRelease message including suspendConfig and measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
10 |
Wait for 130 s for UE to enter RRC_INACTIVE mode and T331 to expire. |
– |
– |
– |
– |
|
11 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
12 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
13 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
14 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
15 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
16 |
Check: Does the UE transmit UEInformationResponse without measResultIdleEUTRA? |
-> |
NR RRC: UEInformationResponse |
2 |
P |
|
17 |
The SS transmits RRCRelease message including suspendConfig and measIdleConfig without measIdleCarrierListEUTRA to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
18 |
Wait for 66 s for UE to enter RRC_INACTIVE mode and to perform measurements. |
– |
– |
– |
– |
|
19 |
SS transmits Paging message to UE. |
<– |
NR RRC: Paging |
– |
– |
|
20 |
UE transmits RRCResumeRequest message to SS. |
–> |
NR RRC: RRCResumeRequest |
– |
– |
|
21 |
SS transmits RRCResume message to UE. |
<– |
NR RRC: RRCResume |
– |
– |
|
22 |
UE transmits RRCResumeComplete message to SS. |
NR RRC: RRCResumeComplete |
– |
– |
|
|
23 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
24 |
Check: Does the UE transmit UEInformationResponse without measResultIdleEUTRA? |
-> |
NR RRC: UEInformationResponse |
3 |
P |
8.2.6.3.4.3.3 Specific message contents
Table 8.2.6.3.4.3.3-1: RRCRelease (steps 1, 13 and 28, Table 8.2.6.3.4.3.2-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-16 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCRelease ::= SEQUENCE { |
|||
|
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
||
|
criticalExtensions CHOICE { |
|||
|
rrcRelease SEQUENCE { |
|||
|
suspendConfig |
SuspendConfig |
||
|
nonCriticalExtensions SEQUENCE { |
|||
|
nonCriticalExtensions SEQUENCE { |
|||
|
measIdleConfig-r16 SetupRelease { |
|||
|
setup |
MeasIdleConfigDedicated |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 8.2.6.3.4.3.3-2: SuspendConfig (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.331 [12], clause 6.2.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SuspendConfig ::= SEQUENCE { |
|||
|
fullI-RNTI |
I-RNTI-Value |
38.508-1[4] Table 4.6.3-64 |
|
|
shortI-RNTI |
ShortI-RNTI-Value |
38.508-1[4] Table 4.6.3-170 |
|
|
ran-PagingCycle |
rf32 |
||
|
ran-NotificationAreaInfo CHOICE { |
|||
|
cellList SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell { |
2 entries |
||
|
PLMN-RAN-AreaCell[1] SEQUENCE { |
entry 1 |
||
|
plmn-Identity |
PLMN1 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of NR Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
PLMN-RAN-AreaCell[2] SEQUENCE { |
entry 2 |
||
|
plmn-Identity |
PLMN2 |
||
|
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity { |
1 entry |
||
|
CellIdentity[1] |
CellIdentity of E-UTRA Cell 1 |
entry 1 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
t380 |
Not Present |
||
|
nextHopChainingCount |
NextHopChainingCount |
38.508-1[4] Table 4.6.3-83 |
|
|
} |
|||
Table 8.2.6.3.4.3.3-3: MeasIdleConfigDedicated (Table 8.2.6.3.4.3.3-1, steps 1 and 9)
|
Derivation Path: TS 38.331 [12], clause 6.3.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r16 ::= SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not Present |
||
|
measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 { |
1 entry |
||
|
MeasIdleCarrierEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
carrierFreqEUTRA-r16 |
ARFCN value corresponding to E-UTRA cell 1 |
||
|
allowedMeasBandwidth-r16 |
mbw50 |
||
|
measCellListEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange { |
1 entry |
||
|
EUTRA-PhysCellIdRange[1] SEQUENCE { |
entry 1 |
||
|
start |
EUTRA-PhysCellId corresponding to E-UTRA cell 1 |
||
|
} |
|||
|
} |
|||
|
reportQuatitiesEUTRA-r16 |
both |
||
|
qualityThresholdEUTRA-r16 |
Not Present |
||
|
} |
|||
|
} |
|||
|
measIdleDuration-r16 |
sec120 |
||
|
validityAreaList-r16 |
Not Present |
||
|
} |
|||
Table 8.2.6.3.4.3.3-4: MeasIdleConfigDedicated (Table 8.2.6.3.4.3.3-1, step 17)
|
Derivation Path: TS 38.331 [12], clause 6.3.2 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
MeasIdleConfigDedicated-r16 ::= SEQUENCE { |
|||
|
measIdleCarrierListNR-r16 |
Not Present |
||
|
measIdleCarrierListEUTRA-r16 |
Not Present |
||
|
measIdleDuration-r16 |
sec120 |
||
|
validityAreaList-r16 |
Not Present |
||
|
} |
|||
Table 8.2.6.3.4.3.3-5: RRCResumeRequest (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-19 |
Table 8.2.6.3.4.3.3-6: RRCResume (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-17 |
Table 8.2.6.3.4.3.3-7: RRCResumeComplete (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.508 [4], clause 4.6.1 table 4.6.1-18 |
Table 8.2.6.3.4.3.3-8: UEInformationRequest (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32A with condition IDLE |
Table 8.2.6.3.4.3.3-9: UEInformationResponse (Table 8.2.6.3.4.3.3-1)
|
Derivation Path: TS 38.508-1 [4], clause 4.6.1 table 4.6.1-32B |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UEInformationResponse-r16 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
ueInformationResponse-r16 SEQUENCE { |
|||
|
measResultIdleEUTRA-r16 SEQUENCE { |
|||
|
measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16 { |
1 entry |
||
|
MeasResultsPerCarrierIdleEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
carrierFreqEUTRA-r16 |
ARFCN value corresponding to E-UTRA cell 1 |
||
|
measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16 { |
1 entry |
||
|
MeasResultsPerCellIdleEUTRA-r16[1] SEQUENCE { |
entry 1 |
||
|
eutra-PhysCellId-r16 |
EUTRA-PhysCellId corresponding to E-UTRA cell 1 |
||
|
measIdleResultEUTRA-r16 SEQUENCE { |
|||
|
rsrp-ResultEUTRA-r16 |
INTEGER (0..97) |
||
|
rsrq-ResultEUTRA-r16 |
INTEGER (0..34) |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.2.6.3.5 Idle/Inactive measurements / Idle mode / NE-DC / SIB11 configuration
8.2.6.3.5.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig and SIB11 including measIdleCarrierListEUTRA }
then { UE enters RRC_IDLE state, performs measurements on E-UTRA cells and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, SIB11 including measIdleCarrierListEUTRA, T331 expires }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig, SIB11 does not include measIdleCarrierListEUTRA }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state due to missing configuration }
}
8.2.6.3.5.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clauses 5.3.8.3, 5.7.8 and 5.7.10.3.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message:
2> if the UE supports idleInactiveEUTRA-MeasReport:
3> if the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA:
4> store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;
3> else:
4> remove the measIdleCarrierListEUTRA in VarMeasIdleConfig, if stored;
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
8.2.6.3.5.3 Test Description
8.2.6.3.5.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– E-UTRA Cell 1
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.2.6.3.5.3.2 Test procedure sequence
Table 8.2.6.3.5.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
3-10 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
11 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
12 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
13 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
14 |
Wait for 11 s for UE to enter RRC_IDLE mode and T331 to expire. |
– |
– |
– |
– |
|
15-22 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
23 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
24 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
2 |
F |
|
25 |
The SS removes measIdleCarrierListEUTRA in SIB11. |
– |
– |
– |
– |
|
26 |
The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification. |
– |
PDCCH (DCI 1_0): Short Message |
– |
– |
|
27 |
Wait for 2.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
|
28 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
29 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
30-37 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
38 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
39 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
3 |
F |
8.2.6.3.5.3.3 Specific message contents
TBD
8.2.6.3.6 Idle/Inactive measurements / Idle mode / NE-DC / RRCRelease configuration
8.2.6.3.6.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig with measIdleCarrierListEUTRA }
then { UE enters RRC_IDLE state, performs measurements on E-UTRA cells and reports measurement results in RRC_CONNECTED state }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig with measIdleCarrierListEUTRA, T331 expires }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state after T331 expiration }
}
(3)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a RRCRelease message including measIdleConfig without measIdleCarrierListEUTRA }
then { UE enters RRC_IDLE state, UE does not report measurement results in RRC_CONNECTED state due to missing configuration }
}
8.2.6.3.6.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clauses 5.3.8.3, 5.7.8 and 5.7.10.3.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the RRCRelease includes the measIdleConfig:
2> if T331 is running:
3> stop timer T331;
3> perform the actions as specified in 5.7.8.3;
2> if the measIdleConfig is set to setup:
3> store the received measIdleDuration in VarMeasIdleConfig;
3> start timer T331 with the value set to measIdleDuration;
3> if the measIdleConfig contains measIdleCarrierListEUTRA:
4> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;
[TS 38.331, clause 5.7.8.1]
This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.
[TS 38.331, clause 5.7.8.1a]
The purpose of this procedure is to update the idle/inactive measurement configuration.
The UE initiates this procedure while T331 is running and one of the following conditions is met:
1> upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or
1> upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform measurements according to 5.7.8.2a.
[TS 38.331, clause 5.7.8.2a]
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [9].
While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:
1> perform the measurements in accordance with the following:
2> if, as a result of the procedure in this subclause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:
3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signalling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
[TS 38.331, clause 5.7.8.3]
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
[TS 38.331, clause 5.7.10.3]
Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:
1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:
2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;
8.2.6.3.6.3 Test Description
8.2.6.3.6.3.1 Pre-test conditions
System Simulator:
– NR Cell 1
– E-UTRA Cell 1
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
8.2.6.3.6.3.2 Test procedure sequence
Table 8.2.6.3.6.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
2 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
3-10 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
11 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
12 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
1 |
P |
|
13 |
The SS transmits RRCRelease message including measIdleConfig to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
14 |
Wait for 11 s for UE to enter RRC_IDLE mode and T331 to expire. |
– |
– |
– |
– |
|
15-22 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
23 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
24 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
2 |
F |
|
25 |
The SS transmits RRCRelease message including measIdleConfig without measIdleCarrierListEUTRA to the UE. |
<- |
NR RRC: RRCRelease |
– |
– |
|
26 |
Wait for 5 s for UE to enter RRC_IDLE mode and to perform measurements. |
– |
– |
– |
– |
|
27-34 |
Steps 1 to 8 of procedure described in TS 38.508-1 table 4.5.4.2-3: NR RRC_CONNECTED are performed. |
– |
– |
– |
– |
|
35 |
The SS transmits UEInformationRequest message including idleModeMeasurementReq to the UE. |
<- |
NR RRC: UEInformationRequest |
– |
– |
|
36 |
Check: Does the UE transmit UEInformationResponse including measResultIdleNR? |
-> |
NR RRC: UEInformationResponse |
3 |
F |
8.2.6.3.6.3.3 Specific message contents
TBD