8.1.4 Handover
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
8.1.4.1 Intra NR handover
8.1.4.1.1 Void
8.1.4.1.2 Intra NR handover / Success / Inter-frequency
8.1.4.1.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having performed the inter-frequency measurements for the neighbour cell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync with rach-ConfigDedicated }
then { UE performs handover to the target cell and transmits an RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_CONNECTED state and having performed the inter-frequency measurements for the neighbour cell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync without rach-ConfigDedicated }
then { UE performs handover to the target cell and transmits an RRCReconfigurationComplete message }
}
(3)
with { UE in NR RRC_CONNECTED state}
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSIB1-Delivery containing SIB1 information with a change of trackingAreaCode }
then { UE reads the updated SIB1 information and sends an RRCReconfigurationComplete message followed by registration on the new tracking area }
}
(4)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync and keySetChangeIndicator set to ‘true’ in MasterKeyUpdate for handover to the target cell }
then { UE performs handover to the target cell with security key update and transmits an RRCReconfigurationComplete message }
}
8.1.4.1.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.2, 5.5.4.4, 5.2.2.4.2 and 5.3.5.7. 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:
…
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform security key update procedure as specified in 5.3.5.7;
…
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
…
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
…1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
…
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 CQI 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;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if T390 is running:
4> stop timer T390 for all access categories;
4> perform the actions as specified in 5.3.14.4.
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
2> the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.1]
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;
…
1> if the CellGroupConfig contains the mac-CellGroupConfig:
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;
…
1> if the CellGroupConfig contains the spCellConfig:
2> configure the SpCell as specified in 5.3.5.5.7;
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.5.4.4]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;
1> use the SpCell for Mp, Ofp and Ocp.
NOTE The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.
Inequality A3-1 (Entering condition)
Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off
Inequality A3-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off
The variables in the formula are defined as follows:
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Mp is the measurement result of the SpCell, not taking into account any offsets.
Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).
Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).
Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.
[TS 38.331, clause 5.2.2.4.2]
Upon receiving the SIB1 the UE shall:
1> store the acquired SIB1;
1> if the cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN:
2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, and cellIdentity for the cell as received in the corresponding PLMN-IdentityInfo containing the selected PLMN;
1> if in RRC_CONNECTED while T311 is not running:
2> disregard the frequencyBandList, if received, while in RRC_CONNECTED;
2> forward the cellIdentity to upper layers;
2> forward the trackingAreaCode to upper layers;
2> apply the configuration included in the servingCellConfigCommonSIB;
[TS 38.331, clause 5.3.5.7]
The UE shall:
1> if UE is connected to E-UTRA/EPC:
2> upon reception of sk-Counter as specified in TS 36.331 [10]:
3> update the S-KgNB key based on the KeNB key and using the received sk-Counter value, as specified in TS 33.401 [30];
3> derive the KRRCenc and KUPenc keys as specified in TS 33.401 [30];
3> derive the KRRCint and KUPint keys as specified in TS 33.401 [30].
1> else:
2> if the nas-Container is included in the received masterKeyUpdate:
3> forward the nas-Container to the upper layers;
2> if the keySetChangeIndicator is set to true:
3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501 [11];
2> else:
3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount value indicated in the received masterKeyUpdate, as specified in TS 33.501 [11];
2> store the nextHopChainingCount value;
2> derive the keys associated with the KgNB key as follows:
3> if the securityAlgorithmConfig is included in SecurityConfig:
4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
3> else:
4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in TS 33.501 [11].
NOTE: Ciphering and integrity protection are optional to configure for the DRBs.
8.1.4.1.2.3 Test description
8.1.4.1.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the serving cell and NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.
– 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:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.1.2.3.2 Test procedure sequence
Tables 8.1.4.1.2.3.2-1 and 8.1.4.1.2.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and NR Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table 8.1.4.1.2.3.2-3.
Table 8.1.4.1.2.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-91 |
Power levels are such that entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-79 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 3 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-79 |
-85 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-88 |
-78 |
Table 8.1.4.1.2.3.2-2: Power levels in FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 3 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
Table 8.1.4.1.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig to setup intra NR measurement and reporting for inter-frequency event A3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
4 |
Check: Does the UE transmit a MeasurementReport message to report event A3 with the measured RSRP value for NR Cell 3? |
–> |
NR RRC: MeasurementReport |
– |
– |
5 |
The SS transmits an RRCReconfiguration message including reconfigurationWithSync with rach-ConfigDedicated,keySetChangeIndicator set to true and including nas-Container IE to order the UE to perform inter-frequency handover to NR Cell 3 |
<– |
NR RRC: RRCReconfiguration |
– |
– |
6 |
Check: Does the UE transmit RRCReconfigurationComplete message in NR Cell 3? |
–> |
NR RRC: RRCReconfigurationComplete |
1, 4 |
P |
6A |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
1,4 |
– |
7 |
The SS transmits an RRCReconfiguration message including MeasConfig to setup intra NR measurement and reporting for inter-frequency event A3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
8 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
9 |
SS adjusts the cell-specific reference signal level according to row "T2". |
– |
– |
– |
– |
10 |
Check: Does the UE transmit a MeasurementReport message to report event A3 with the measured RSRP value for NR Cell 1? |
–> |
NR RRC: MeasurementReport |
– |
– |
11 |
The SS transmits an RRCReconfiguration message including reconfigurationWithSync without rach-ConfigDedicated, keySetChangeIndicator set to true and including nas-Container IE to order the UE to perform inter-frequency handover to NR Cell 1 |
<– |
NR RRC: RRCReconfiguration |
– |
– |
12 |
Check: Does the UE transmit RRCReconfigurationComplete message in NR Cell 1? |
–> |
NR RRC: RRCReconfigurationComplete |
2, 4 |
P |
12A |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 1? |
– |
– |
2,4 |
– |
13 |
SS adjusts the cell-specific reference signal level according to row "T3". |
– |
– |
– |
– |
14 |
The SS transmits an RRCReconfiguration including dedicatedSIB1-Delivery containing SIB1 of NR Cell 3 to order the UE to perform handover to NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
15 |
Check: Does the UE transmit an RRCReconfigurationComplete message on NR Cell 3? |
–> |
NR RRC: RRCReconfigurationComplete |
3 |
P |
16 |
Check: Does UE transmit a REGISTRATION REQUEST message to update the registration of the actual tracking area? |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION REQUEST |
3 |
P |
– |
EXCEPTION: In parallel to the events described in steps 16A to 19, the steps specified in Table 8.1.4.1.2.3.2-4 may take place. |
– |
– |
– |
– |
16A |
SS transmits SIB1 with TAC=2 on NR Cell 3 |
– |
– |
– |
– |
17 |
SS responds with REGISTRATION ACCEPT message with TAC=2 in Tracking Area Identity List IE. |
<– |
NR RRC: DLInformationTransfer 5GMM: REGISTRATION ACCEPT |
– |
– |
18 |
The UE sends a REGISTRATION COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION COMPLETE |
– |
– |
19 |
Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on NR Cell 3? |
– |
– |
3 |
– |
Table 8.1.4.1.2.3.2-4: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE sends REGISTRATION REQUEST NOTE: This request may be to register for TAC=1 or TAC=2 depending upon when UE reads the SIB1 after step 16 |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION REQUEST |
– |
– |
8.1.4.1.2.3.3 Specific message contents
Table 8.1.4.1.2.3.3-1: RRCReconfiguration (step 1, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition MEAS |
Table 8.1.4.1.2.3.3-2: MeasConfig (Table 8.1.4.1.2.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
2 entries |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 3 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
measObjectId |
2 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 1 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-EventA3 |
||
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
measGapConfig |
MeasGapConfig |
||
} |
Table 8.1.4.1.2.3.3-3: ReportConfigNR-EventA3 (Table 8.1.4.1.2.3.3-2 and Table 8.1.4.1.2.3.3-8)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
eventTriggered SEQUENCE { |
|||
eventId CHOICE { |
|||
eventA3 SEQUENCE { |
EVENT_A3 |
||
a3-Offset CHOICE { |
|||
rsrp |
6 |
3dB |
FR1 |
FFS |
FR2 |
||
} |
|||
hysteresis |
0 |
0 dB |
|
timeToTrigger |
ms640 |
||
} |
|||
} |
|||
reportAmount |
r1 |
||
reportQuantityCell SEQUENCE { |
|||
rsrp |
true |
||
rsrq |
false |
||
sinr |
false |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-4: MeasurementReport (step 4, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-5A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasurementReport ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
measurementReport SEQUENCE { |
|||
measResults SEQUENCE { |
|||
measId |
1 |
||
measResultServingMOList SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO { |
1 entry |
||
MeasResultServMO[1] SEQUENCE { |
entry 1 |
||
servCellId |
Cell index corresponding to NR Cell 1 |
||
measResultServingCell SEQUENCE { |
|||
physCellId |
Physical layer cell identity of NR Cell 1 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
(0..127) |
||
sinr |
Not present |
||
Not checked |
pc_ss_SINR_Meas |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
measResultNeighCells CHOICE { |
|||
measResultListNR SEQUENCE (SIZE (1.. maxCellReport)) OF MeasResultNR { |
1 entry |
||
MeasResultNR[1] SEQUENCE { |
entry 1 |
||
physCellId |
Physical layer cell identity of NR Cell 3 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
Not present |
||
sinr |
Not present |
||
} |
|||
resultsCSI-RS-Cell |
Not present |
||
} |
|||
rsIndexResults |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-5: RRCReconfiguration (step 5, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
|||
measConfig SEQUENCE { |
|||
measObjectToRemoveList SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId { |
2 entries |
||
measObjectId[1] |
1 |
entry 1 |
|
measObjectId[2] |
2 |
entry 2 |
|
} |
|||
measIdToRemoveList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId { |
1 entry |
||
measId[1] |
1 |
entry 1 |
|
} |
|||
} |
|||
masterCellGroup |
OCTET STRING (CONTAINING CellGroupConfig) |
||
masterKeyUpdate SEQUENCE { |
|||
keySetChangeIndicator |
True |
||
nextHopChainingCount |
0 |
||
nas-Container |
NASContainer |
Intra N1 mode NAS transparent container |
|
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-6: CellGroupConfig (Table 8.1.4.1.2.3.3-5)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
Same as default ServingCellConfigCommon |
||
physCellId |
Physical cell Id of NR Cell 3 |
||
} |
|||
rach-ConfigDedicated CHOICE { |
|||
Uplink |
RACH-ConfigDedicated |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-6A: NASContainer (Table 8.1.4.1.2.3.3-5, Table 8.1.4.1.2.3.3-10)
Derivation Path: TS 24.501, table 9.11.2.6 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Message authentication code |
The calculated value of MAC-I for this message. |
The value of MAC-I is calculated by SS using COUNT = 0xFFFFFFFF( as per TS 33.501[20], 6.9.2.3.3) |
|
Type of ciphering algorithm |
Set according to PIXIT px_NAS_5GC_CipheringAlgorithm for default ciphering algorithm |
||
Type of integrity protection algorithm |
Set according to PIXIT px_NAS_5GC_IntegrityAlgorithm for default integrity protection algorithm |
This value should not be equal to the null integrity algorithm. |
|
KACF |
‘1’B |
a new KAMF has been calculated by the network |
|
TSC |
‘0’B |
native security context (for KSIAMF) |
|
Key set identifier in 5G |
KSIAMF that was created when the UE last registered to 5GCN |
||
Sequence number |
The internal counter of the SS |
eight least significant bits of the downlink NAS COUNT |
Table 8.1.4.1.2.3.3-7: RRCReconfiguration (step 7, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition MEAS |
Table 8.1.4.1.2.3.3-8: MeasConfig (Table 8.1.4.1.2.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
2 entries |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 1 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
} |
|||
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
measObjectId |
2 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 3 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-EventA3 |
||
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-9: MeasurementReport (step 10, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-5A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasurementReport ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
measurementReport SEQUENCE { |
|||
measResults SEQUENCE { |
|||
measId |
1 |
||
measResultServingMOList SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO { |
1 entry |
||
MeasResultServMO[1] SEQUENCE { |
entry 1 |
||
servCellId |
Cell index corresponding to NR Cell 3 |
||
measResultServingCell SEQUENCE { |
|||
physCellId |
Physical layer cell identity of NR Cell 3 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
(0..127) |
||
sinr |
Not present |
||
Not checked |
pc_ss_SINR_Meas |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
measResultNeighCells CHOICE { |
|||
measResultListNR SEQUENCE (SIZE (1.. maxCellReport)) OF MeasResultNR { |
1 entry |
||
MeasResultNR[1] SEQUENCE { |
entry 1 |
||
physCellId |
Physical layer cell identity of NR Cell 1 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
Not present |
||
sinr |
Not present |
||
} |
|||
resultsCSI-RS-Cell |
Not present |
||
} |
|||
rsIndexResults |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-10: RRCReconfiguration (step 11, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
|||
measConfig SEQUENCE { |
|||
measObjectToRemoveList SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId { |
2 entries |
||
measObjectId[1] |
1 |
entry 1 |
|
measObjectId[2] |
2 |
entry 2 |
|
} |
|||
measIdToRemoveList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId { |
1 entry |
||
measId[1] |
1 |
entry 1 |
|
} |
|||
} |
|||
masterCellGroup |
OCTET STRING (CONTAINING CellGroupConfig) |
||
masterKeyUpdate SEQUENCE { |
|||
keySetChangeIndicator |
True |
||
nextHopChainingCount |
0 |
||
nas-Container |
NASContainer |
Intra N1 mode NAS transparent container |
|
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-11: CellGroupConfig (Table 8.1.4.1.2.3.3-10)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
Same as default ServingCellConfigCommon |
||
physCellId |
Physical cell Id of NR Cell 1 |
||
} |
|||
rach-ConfigDedicated |
Not Present |
||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-12: RRCReconfiguration (step 14 Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_NoKeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
|||
dedicatedSIB1-Delivery |
SIB1 |
OCTET STRING (CONTAINING SIB1) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-13: SIB1 (Table 8.1.4.1.2.3.3-12)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity { |
1 entry |
||
plmn-Identity[1] |
entry 1 |
||
trackingAreaCode |
2 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-14: REGISTRATION REQUEST (step 16 Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-6 with condition MOBILITY |
|||
Information Element |
Value/remark |
Comment |
Condition |
Last visited registered TAI |
|||
tac |
1 |
Table 8.1.4.1.2.3.3-15: SIB1 (step 16A, Table 8.1.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity { |
1 entry |
||
plmn-Identity[1] |
entry 1 |
||
trackingAreaCode |
2 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.2.3.3-16: REGISTRATION ACCEPT (step 17, Table 8.1.4.1.2.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
|||
Information Element |
Value/remark |
Comment |
Condition |
TAI list |
|||
TAC 1 |
2 |
Table 8.1.4.1.2.3.3-17: REGISTRATION REQUEST (step 1, Table 8.1.4.1.2.3.2-4)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-6 with condition MOBILITY |
|||
Information Element |
Value/remark |
Comment |
Condition |
Last visited registered TAI |
|||
tac |
Not Checked |
The value may be 1 or 2, please check note for step 1 in Table 8.1.4.1.2.3.2-4 |
8.1.4.1.3 Void
8.1.4.1.4 Void
8.1.4.1.5 Intra NR handover / Failure / Re-establishment successful
8.1.4.1.5.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the target cell }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
then { UE performs an RRCReestablishment procedure on the source cell }
}
(2)
with { UE detects handover failure and having transmitted an RRCReestablishmentRequest message }
ensure that {
when { UE receives an RRCReestablishment message with a nextHopChainingCount which is different from the NCC associated with the currently active KgNB }
then { UE derives new KgNB from the nextHopChainingCount and completes RRCReestablishment procedure on the source cell }
}
(3)
with { UE detects handover failure and having transmitted an RRCReestablishmentRequest message }
ensure that {
when { UE receives an RRCReestablishment message with a nextHopChainingCount which is same as the NCC associated with the currently active KgNB }
then { UE derives new KgNB from the currently active KgNB and completes RRCReestablishment procedure on the source cell }
}
8.1.4.1.5.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.5.2, 5.3.5.7, 5.3.5.8.3 and 5.3.7.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.7]
The UE shall:
…
1> else:
2> if the nas-Container is included in the received masterKeyUpdate:
3> forward the nas-Container to the upper layers;
2> if the keySetChangeIndicator is set to true:
3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501 [11];
2> else:
3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount value indicated in the received masterKeyUpdate, as specified in TS 33.501 [11];
2> store the nextHopChainingCount value;
2> derive the keys associated with the KgNB key as follows:
3> if the securityAlgorithmConfig is included in SecurityConfig:
4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
3> else:
4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in TS 33.501 [11].
NOTE: Ciphering and integrity protection are optional to configure for the DRBs.
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
1> if T304 of the MCG expires:
2> release dedicated preambles provided in rach-ConfigDedicated if configured;
2> revert back to the UE configuration used in the source PCell;
2> initiate the connection re-establishment procedure as specified in subclause 5.3.7.
NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer.
1> else if T304 of a secondary cell group expires:
2> release dedicated preambles provided in rach-ConfigDedicated, if configured;
2> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends;
1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2> reset MAC;
2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> consider the current cell to be the PCell;
1> store the nextHopChainingCount value indicated in the RRCReestablishment message;
1> update the KgNB key based on the current KgNB key or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [11];
1> derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501 [11];
1> derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified in TS 33.501 [11].
1> request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously configured algorithm and the KRRCint key;
1> if the integrity protection check of the RRCReestablishment message fails:
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’, upon which the procedure ends;
1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> release the measurement gap configuration indicated by the measGapConfig, if configured;
1> submit the RRCReestablishmentComplete message to lower layers for transmission;
1> the procedure ends.
8.1.4.1.5.3 Test Description
8.1.4.1.5.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the Serving cell.
– NR Cell 2 is the Suitable neighbour intra-frequency cell.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for both NR Cells.
UE:
– None.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
8.1.4.1.5.3.2 Test procedure sequence
Table 8.1.4.1.5.3.2-1 and Table 8.1.4.1.5.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.4.1.5.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-94 |
Table 8.1.4.1.5.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
Table 8.1.4.1.5.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes the power level setting according to the row "T1". |
– |
– |
– |
– |
2 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to order the UE to perform handover to NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 3 the steps specified in Table 8.1.4.1.5.3.2-4 should take place. |
– |
– |
– |
– |
3 |
The SS changes the power level setting according to the row "T2". |
– |
– |
– |
– |
4 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentRequest |
1 |
P |
5 |
The SS transmits an RRCReestablishment message to resume SRB1 operation and re-activate security on NR Cell 1. |
<– |
NR RRC: RRCReestablishment |
– |
– |
6 |
Does the UE transmit an RRCReestablishmentComplete message using the security key derived from the nextHopChainingCount on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentComplete |
2 |
P |
6A |
The SS transmits an RRCReconfiguration message to resume existing radio bearers on NR Cell 1. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
6B |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
7 |
The SS changes the power level setting according to the row "T1". |
– |
– |
– |
– |
8 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to order the UE to perform handover to NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 9 the steps specified in Table 8.1.4.1.5.3.2-4 should take place. |
– |
– |
– |
– |
9 |
The SS changes the power level setting according to the row "T2". |
– |
– |
– |
– |
10 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentRequest |
– |
– |
11 |
The SS transmits an RRCReestablishment message to resume SRB1 operation and re-activate security on NR Cell 1. |
<– |
NR RRC: RRCReestablishment |
– |
– |
12 |
Does the UE transmit an RRCReestablishmentComplete message using the security key derived from the nextHopChainingCount on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentComplete |
3 |
P |
12A |
The SS transmits an RRCReconfiguration message to resume existing radio bearers on NR Cell 1. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
12B |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
13 |
The SS transmits an RRCRelease message on NR Cell 1. |
<– |
NR RRC: RRCRelease |
– |
– |
Table 8.1.4.1.5.3.2-4: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
– |
EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304. |
– |
– |
– |
– |
1 |
The UE attempts to perform the handover using MAC Random Access Preamble on NR Cell 2. |
– |
– |
– |
– |
2 |
The SS does not respond. |
– |
– |
– |
– |
8.1.4.1.5.3.3 Specific message contents
Table 8.1.4.1.5.3.3-1: SIB1 for NR Cell 1 and NR Cell 2 (preamble and all steps, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.3-130 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigGeneric ::= SEQUENCE { |
|||
preambleTransMax |
n50 |
||
} |
Table 8.1.4.1.5.3.3-2: RRCReconfiguration-HO (steps 2, 8, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
Table 8.1.4.1.5.3.3-3: RRCReestablishmentRequest (step 4, 10, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-12 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishmentRequest ::= SEQUENCE { |
|||
ue-Identity SEQUENCE { |
|||
c-RNTI |
the value of the C-RNTI of the UE |
||
physCellId |
PhysicalCellIdentity of NR Cell 1 |
||
shortMAC-I |
The same value as the 16 least significant bits of the MAC-I value calculated by SS. |
||
} |
|||
reestablishmentCause |
handoverFailure |
||
} |
Table 8.1.4.1.5.3.3-4: RRCReestablishment (step 5, 11, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-10 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishment ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReestablishment SEQUENCE { |
|||
nextHopChainingCount |
2 |
||
} |
|||
} |
|||
} |
Table 8.1.4.1.5.3.3-5: Void
Table 8.1.4.1.5.3.3-6: Void
Table 8.1.4.1.5.3.3-7: RRCReconfiguration (step 6A and 12A, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition REEST |
8.1.4.1.6 Intra NR handover / Failure / Re-establishment failure
8.1.4.1.6.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the target cell }
ensure that {
when { UE detects handover failure and fails an RRCReestablishment procedure }
then { UE enters NR RRC_IDLE state }
}
8.1.4.1.6.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.5.2, 5.3.5.8.3 and 5.3.7.5 and TS 24.501, clause 5.5.1.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
1> if T304 of the MCG expires:
2> release dedicated preambles provided in rach-ConfigDedicated if configured;
2> revert back to the UE configuration used in the source PCell;
2> initiate the connection re-establishment procedure as specified in subclause 5.3.7.
NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer.
1> else if T304 of a secondary cell group expires:
2> release dedicated preambles provided in rach-ConfigDedicated, if configured;
2> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends;
1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2> reset MAC;
2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> consider the current cell to be the PCell;
1> store the nextHopChainingCount value indicated in the RRCReestablishment message;
1> update the KgNB key based on the current KgNB key or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [11];
1> derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501 [11];
1> derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified in TS 33.501 [11].
1> request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously configured algorithm and the KRRCint key;
1> if the integrity protection check of the RRCReestablishment message fails:
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’, upon which the procedure ends;
1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> release the measurement gap configuration indicated by the measGapConfig, if configured;
1> submit the RRCReestablishmentComplete message to lower layers for transmission;
1> the procedure ends.
[TS 24.501, clause 5.5.1.3.2]
The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF,
…
f) when the UE receives an indication of "RRC Connection failure" from the lower layers and does not have signalling pending (i.e. when the lower layer requests NAS signalling connection recovery) except for the case specified in subclause 5.3.1.4;
8.1.4.1.6.3 Test Description
8.1.4.1.6.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the Serving cell.
– NR Cell 2 is the Suitable neighbour intra-frequency cell.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for both NR Cells.
UE:
– None.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
8.1.4.1.6.3.2 Test procedure sequence
Table 8.1.4.1.6.3.2-1 and Table 8.1.4.1.6.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.4.1.6.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-94 |
Table 8.1.4.1.6.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
Table 8.1.4.1.6.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes the power level setting according to the row "T1". |
– |
– |
– |
– |
2 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to order the UE to perform handover to NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 3 the steps specified in Table 8.1.4.1.6.3.2-4 should take place. |
– |
– |
– |
– |
3 |
The SS changes the power level setting according to the row "T2". |
– |
– |
– |
– |
4 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentRequest |
1 |
P |
5 |
The SS transmits an RRCReestablishment message to resume SRB1 operation and re-activate security on NR Cell 1. Note: RRCReestablishment includes a wrong nextHopChainingCount value causing an integrity check failure. |
<– |
NR RRC: RRCReestablishment |
– |
– |
6 |
Check: Does the test result of test procedure in TS 38.508-1 [4] subclause 4.9.5 indicate that the UE has performed mobility registration on NR cell 1 started in NR RRC_IDLE? |
– |
– |
1 |
– |
Table 8.1.4.1.6.3.2-4: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
– |
EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304. |
– |
– |
– |
– |
1 |
The UE attempts to perform the handover using MAC Random Access Preamble on NR Cell 2. |
– |
– |
– |
– |
2 |
The SS does not respond. |
– |
– |
– |
– |
8.1.4.1.6.3.3 Specific message contents
Table 8.1.4.1.6.3.3-1: SIB1 for NR Cell 1 and NR Cell 2 (preamble and all steps, Table 8.1.4.1.6.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.3-130 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigGeneric ::= SEQUENCE { |
|||
preambleTransMax |
n50 |
||
} |
Table 8.1.4.1.6.3.3-2: RRCReconfiguration-HO (step 2, Table 8.1.4.1.6.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
Table 8.1.4.1.6.3.3-3: RRCReestablishmentRequest (step 4, Table 8.1.4.1.6.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-12 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishmentRequest ::= SEQUENCE { |
|||
ue-Identity SEQUENCE { |
|||
c-RNTI |
the value of the C-RNTI of the UE |
||
physCellId |
PhysicalCellIdentity of NR Cell 1 |
||
shortMAC-I |
The same value as the 16 least significant bits of the MAC-I value calculated by SS. |
||
} |
|||
reestablishmentCause |
handoverFailure |
||
} |
Table 8.1.4.1.6.3.3-4: RRCReestablishment (step 5, Table 8.1.4.1.6.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-10 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishment ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReestablishment SEQUENCE { |
|||
nextHopChainingCount |
7 |
||
} |
|||
} |
|||
} |
8.1.4.1.7 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release
8.1.4.1.7.1 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Intra-band Contiguous CA
8.1.4.1.7.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and configured an SCell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for handover to one of the SCell and sCellToAddModList for an SCell addition }
then { UE transmits an RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for PCell change and including sCellToReleaseList with an sCellIndex set to the configured Scell }
then { UE sends an RRCReconfigurationComplete message }
}
8.1.4.1.7.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.5.2, clauses 5.3.5.5.9 and clauses 5.3.5.5.8. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
8.1.4.1.7.1.3 Test description
8.1.4.1.7.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell, NR Cell 3 is the configured SCell and target PCell. NR Cell 2 is the active target SCell. NR Cell 12 is the target intra-frequency Cell of NR Cell 3, and also the target PCell.
– NR Cell 1 and NR Cell 3 are Intra-band Contiguous. NR Cell 2 and NR Cell 12 are Intra-band Contiguous.
– NR Cell 12 belongs to the same PLMN and TAI with NR Cell 1.
– 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:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.1.7.1.3.2 Test procedure sequence
Table 8.1.4.1.7.1.3.2-1 and Table 8.1.4.1.7.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR Cell 3, NR Cell 2 and NR Cell 12 at various time instants of the test execution. Row marked “T0” denotes the conditions after the preamble, while rows marked “T1” are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.4.1.7.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
NR Cell 12 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
-88 |
“Off” |
NR Cell 1, NR Cell 2 and NR Cell 3 are available. NR Cell 12 is not available. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-88 |
-88 |
-82 |
NR Cell 3, NR Cell 2 and NR Cell 12 are available. NR Cell 1 is not available. |
Table 8.1.4.1.7.1.3.2-2: Time instances of cell power level and parameter changes for OTA test environment
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
NR Cell 12 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
“Off” |
NR Cell 1, NR Cell 2 and NR Cell 3 are available. NR Cell 12 is not available. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“ff” |
FFS |
FFS |
FFS |
NR Cell 3, NR Cell 2 and NR Cell 12 are available. NR Cell 1 is not available. |
Table 8.1.4.1.7.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes Cell parameters according to the row “T0” in table 8.1.4.1.7.1.3.2-1/2. |
– |
– |
– |
– |
2 |
The SS transmits an RRCReconfiguration message including a sCellToAddModList to add NR Cell 3 as a SCell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
3 |
The UE transmits the RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
4 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync for handover to NR Cell 3 and sCellToAddModList to add NR Cell 2 as a SCell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
5 |
Check: Does UE transmit the RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
5A |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on Cell 2? |
– |
– |
1 |
– |
6 |
The SS changes Cell parameters according to the row “T1” in table 8.1.4.1.7.1.3.2-1/2. |
– |
– |
– |
– |
7 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync to change PCell to NR Cell 12 and including sCellToReleaseList with a sCellIndex of NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
8 |
Check: Does the UE transmit the RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
2 |
P |
9 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB #n associated with the first PDU session on Cell 12? |
– |
– |
2 |
– |
8.1.4.1.7.1.3.3 Specific message contents
Table 8.1.4.1.7.1.3.3-1: RRCReconfiguration (step 2, Table 8.1.4.1.7.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.7.1.3.3-2: CellGroupConfig (Table 8.1.4.1.7.1.3.3-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 3 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.7.1.3.3-3: RRCReconfiguration-HO (step 4, Table 8.1.4.1.7.1.3.2-3)
Derivation Path: TS 38.508-1 [4] 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.7.1.3.3-4: CellGroupConfig (Table 8.1.4.1.7.1.3.3-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 3 |
||
} |
|||
} |
|||
} |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 2 |
||
} |
|||
} |
|||
} |
|||
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
SCellIndex[1] |
1 |
entry 1 SCell release for NR Cell 3 |
|
} |
|||
} |
Table 8.1.4.1.7.1.3.3-5: RRCReconfiguration-HO (step 7, Table 8.1.4.1.7.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_KeyChange |
Table 8.1.4.1.7.1.3.3-6: CellGroupConfig (Table 8.1.4.1.7.1.3.3-5)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with conditions PCell_change |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 12 |
||
} |
|||
} |
|||
} |
|||
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
SCellIndex[1] |
1 |
entry 1 SCell release for NR Cell 2 |
|
} |
|||
} |
8.1.4.1.7.2 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Inter-band CA
8.1.4.1.7.2.1 Test Purpose (TP)
Same as TC 8.1.4.1.7.1 but applied to Inter-band CA case.
8.1.4.1.7.2.2 Conformance requirements
Same as TC 8.1.4.1.7.1 but applied to Inter-band CA case.
8.1.4.1.7.2.3 Test description
8.1.4.1.7.2.3.1 Pre-test conditions
Same as test case 8.1.4.1.7.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12.
– NR Cell 30 belongs to the same PLMN and TAI with NR Cell 1.
8.1.4.1.7.2.3.2 Test procedure sequence
Same as TC 8.1.4.1.7.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
8.1.4.1.7.2.3.3 Specific message contents
Same as TC 8.1.4.1.7.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
– Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12.
Table 8.1.4.1.7.2.3.3-1: SIB3 of NR Cell 10 (step 6, Table 8.1.4.1.7.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB3 ::= SEQUENCE { |
|||
intraFreqNeighCellList SEQUENCE (SIZE (1.. maxCellIntra)) OF IntraFreqNeighCellInfo { |
1 entry |
||
IntraFreqNeighCellInfo [1] SEQUENCE { |
entry 1 |
||
physCellId |
Physical Cell Identity of NR Cell 30 |
||
} |
|||
} |
|||
} |
8.1.4.1.7.3 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release / Intra-band non-contiguous CA
8.1.4.1.7.3.1 Test Purpose (TP)
Same as TC 8.1.4.1.7.1 but applied to Intra-band non-Contiguous CA.
8.1.4.1.7.3.2 Conformance requirements
Same as TC 8.1.4.1.7.1 but applied to Intra-band non-Contiguous CA.
8.1.4.1.7.3.3 Test description
8.1.4.1.7.3.3.1 Pre-test conditions
Same as test case 8.1.4.1.7.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
8.1.4.1.7.3.3.2 Test procedure sequence
Same as TC 8.1.4.1.7.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.1.4.1.7.3.3.3 Specific message contents
Same as TC 8.1.4.1.7.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.1.4.1.8 NR CA / Intra NR handover / Success / PCell Change / SCell no Change
8.1.4.1.8.1 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band Contiguous CA
8.1.4.1.8.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and configured an SCell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for PCell change and sCellToAddModList with an SCell same from configured Scell }
then { UE transmits an RRCReconfigurationComplete message }
}
8.1.4.1.8.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.5.2, clauses 5.3.5.5.9. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
8.1.4.1.8.1.3 Test description
8.1.4.1.8.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell, NR Cell 3 is the configured active SCell. NR Cell 2 is the target intra-frequency Cell of NR Cell 1, and also the target PCell.
– NR Cell 1 and NR Cell 3 are Intra-band Contiguous.
– 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:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.1.8.1.3.2 Test procedure sequence
Table 8.1.4.1.8.1.3.2-1 and Table 8.1.4.1.8.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR Cell 3 and NR Cell 2 at various time instants of the test execution. Row marked “T0” denotes the conditions after the preamble, while rows marked “T1” are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.4.1.8.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-99 |
“Off” |
NR Cell 1, NR Cell 3 are available. NR Cell 2 is not available. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-99 |
-88 |
NR Cell 1, NR Cell 3 and NR Cell 2 are available. |
Table 8.1.4.1.8.1.3.2-2: Time instances of cell power level and parameter changes for OTA test environment
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 2 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
“Off” |
NR Cell 1, NR Cell 3 are available. NR Cell 2 is not available. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
NR Cell 1, NR Cell 3 and NR Cell 2 are available. |
Table 8.1.4.1.8.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes Cell parameters according to the row “T0” in table 8.1.4.1.8.1.3.2-1/2. |
– |
– |
– |
– |
2 |
The SS transmits an RRCReconfiguration message including a sCellToAddModList to add NR Cell 3 as a SCell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
3 |
The UE transmits the RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3A |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 3? |
– |
– |
1 |
– |
4 |
The SS changes Cell parameters according to the row “T1” in table 8.1.4.1.8.1.3.2-1/2. |
– |
– |
– |
– |
5 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync to change PCell to NR Cell 2 and sCellToAddModList to add NR Cell 3 as the Scell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
6 |
Check: Does the UE transmit the RRCReconfigurationComplete message? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
7 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1A indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 3? |
– |
– |
1 |
– |
8 |
The SS transmits an RRCReconfiguration message containing an sCellToReleaseList with SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
9 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
8.1.4.1.8.1.3.3 Specific message contents
Table 8.1.4.1.8.1.3.3-1: RRCReconfiguration (step 2, Table 8.1.4.1.8.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.8.1.3.3-2: CellGroupConfig (Table 8.1.4.1.8.1.3.3-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellIndex |
1 |
||
sCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 3 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.8.1.3.3-3: RRCReconfiguration-HO (step 5, Table 8.1.4.1.8.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_KeyChange |
Table 8.1.4.1.8.1.3.3-4: CellGroupConfig (Table 8.1.4.1.8.1.3.3-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 2 |
||
} |
|||
} |
|||
} |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellIndex |
1 |
||
sCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 3 |
||
} |
|||
} |
|||
} |
|||
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
SCellIndex[1] |
1 |
entry 1 SCell release for NR Cell 3 |
|
} |
|||
} |
Table 8.1.4.1.8.1.3.3-5: RRCReconfiguration (step 8, Table 8.1.4.1.8.1.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.1.1.3.3-6: CellGroupConfig (Table 8.1.4.1.8.1.3.3-5)`
Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 with condition SCell_add |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
sCellToAddModList |
Not present |
||
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
||
SCellIndex[1] |
1 |
entry 1 |
|
} |
|||
} |
8.1.4.1.8.2 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Inter-band CA
8.1.4.1.8.2.1 Test Purpose (TP)
Same as TC 8.1.4.1.8.1 but applied to Inter-band CA case.
8.1.4.1.8.2.2 Conformance requirements
Same as TC 8.1.4.1.8.1 but applied to Inter-band CA case.
8.1.4.1.8.2.3 Test description
8.1.4.1.8.2.3.1 Pre-test conditions
Same as test case 8.1.4.1.8.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.1.4.1.8.2.3.2 Test procedure sequence
Same as TC 8.1.4.1.8.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA
8.1.4.1.8.2.3.3 Specific message contents
Same as TC 8.1.4.1.8.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.1.4.1.8.3 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band non-contiguous CA
8.1.4.1.8.3.1 Test Purpose (TP)
Same as TC 8.1.4.1.8.1 but applied to Intra-band non-Contiguous CA.
8.1.4.1.8.3.2 Conformance requirements
Same as TC 8.1.4.1.8.1 but applied to Intra-band non-Contiguous CA.
8.1.4.1.8.3.3 Test description
8.1.4.1.8.3.3.1 Pre-test conditions
Same as test case 8.1.4.1.8.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
8.1.4.1.8.3.3.2 Test procedure sequence
Same as TC 8.1.4.1.8.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.1.4.1.8.3.3.3 Specific message contents
Same as TC 8.1.4.1.8.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
8.1.4.1.9 NR CA / Intra NR handover / Failure / Re-establishment successful
8.1.4.1.9.1 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band Contiguous CA
8.1.4.1.9.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for PCell change and including sCellToReleaseList with an sCellIndex set to the configured Scell }
ensure that {
when { UE detects handover failure and the source PCell is selectable}
then { UE successfully performs an RRCReestablishment procedure on source Pcell}
}
(2)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for PCell change and including sCellToReleaseList with an sCellIndex set to the configured SCell }
ensure that {
when { UE detects handover failure and the initial SCell is selectable}
then { UE successfully performs an RRCReestablishment procedure on original SCell and the original SCell becomes the PCell}
}
8.1.4.1.9.1.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clause 5.3.5.5.2, 5.3.5.5.9, 5.3.5.5.8 and 5.3.7.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> consider the current cell to be the PCell;
1> store the nextHopChainingCount value indicated in the RRCReestablishment message;
1> update the KgNB key based on the current KgNB key or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [11];
1> derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501 [11];
1> derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified in TS 33.501 [11].
1> request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously configured algorithm and the KRRCint key;
1> if the integrity protection check of the RRCReestablishment message fails:
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’, upon which the procedure ends;
1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> release the measurement gap configuration indicated by the measGapConfig, if configured;
1> submit the RRCReestablishmentComplete message to lower layers for transmission;
1> the procedure ends.
8.1.4.1.9.1.3 Test Description
8.1.4.1.9.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the PCell and NR Cell 3 is the configured SCell and target PCell.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in all NR cells.
UE:
– None.
Preamble:
– The UE is in 5GS state 3N-A as defined in TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 on NR Cell 1.
8.1.4.1.9.1.3.2 Test procedure sequence
Table 8.1.4.1.9.1.3.2-1 and Table 8.1.4.1.9.1.3.2-1A illustrates the downlink power levels to be applied for NR Cell 1 and NR Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 8.1.4.1.9.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-85 |
-91 |
Power levels are such that entry condition for event A3 is not satisfied Mn + Ofn + Ocn – Hys < Mp + Ofp + Ocp + Off |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-85 |
-79 |
Power levels are such that entry condition for event A3 is satisfied Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-85 |
“Off” |
Power levels are assigned to satisfy SrxLevCell3 < 0 such that selecting Cell 1 is guaranteed |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
-85 |
-79 |
Power levels are such that entry condition for event A3 is satisfied Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off |
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-79 |
Power levels are assigned to satisfy SrxLevCell1 < 0 such that selecting Cell 3 is guaranteed |
Table 8.1.4.1.9.1.3.2-1A: TOTA test environment ime instances of cell power level and parameter changes for
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
[FFS] |
[FFS] |
Power levels are such that entry condition for event A3 is not satisfied Mn + Ofn + Ocn – Hys < Mp + Ofp + Ocp + Off |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
[FFS] |
[FFS] |
Power levels are such that entry condition for event A3 is satisfied Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
[FFS] |
“Off” |
Power levels are assigned to satisfy SrxLevCell3 < 0 such that selecting Cell 1 is guaranteed |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
[FFS] |
[FFS] |
Power levels are such that entry condition for event A3 is satisfied Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off |
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
[FFS] |
Power levels are assigned to satisfy SrxLevCell1 < 0 such that selecting Cell 3 is guaranteed |
Table 8.1.4.1.9.1.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to configure NR Cell 3 as an SCell |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to setup event A3 reporting configuration. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
4 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
5 |
The SS changes NR Cell 1 and NR Cell 3 parameters according to the row "T1" in table 8.1.4.1.9.1.3.2-1/1A |
– |
– |
– |
– |
6 |
The UE transmits a MeasurementReport message on NR Cell 1 to report event A3 with the measured RSRP, RSRQ value for NR Cell 3. |
–> |
NR RRC: MeasurementReport |
– |
– |
7 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to order the UE to perform inter frequency handover to NR Cell 3 and to release SCell NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 8 the steps specified in Table 8.1.4.1.9.1.3.2-3 should take place. |
– |
– |
– |
– |
8 |
The SS changes NR Cell 1 and NR Cell 3 parameters according to the row "T2" in table 8.1.4.1.9.1.3.2-1/1A |
– |
– |
– |
– |
9 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1? |
–> |
NR RRC: RRCReestablishmentRequest |
1 |
P |
10 |
The SS transmits an RRCReestablishment message to resume SRB1 operation and re-activate security on NR Cell 1. |
<– |
NR RRC: RRCReestablishment |
– |
– |
11 |
The UE transmits an RRCReestablishmentComplete message |
–> |
NR RRC: RRCReestablishmentComplete |
– |
– |
11A |
Void |
– |
– |
– |
– |
12 |
The SS transmits an RRCReconfiguration message to resume existing radio bearer on NR Cell 1 |
<– |
NR RRC: RRCReconfiguration |
– |
– |
13 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1 |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
13A |
The SS changes NR Cell 1 and NR Cell 3 parameters according to the row "T3" in table 8.1.4.1.9.1.3.2-1/1A |
– |
– |
– |
– |
13B |
The SS transmits an RRCReconfiguration message to configure NR Cell 3 as an SCell |
<– |
NR RRC: RRCReconfiguration |
– |
– |
13C |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1 |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
14 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to setup event A3 reporting configuration. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
15 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
16 |
Void |
– |
– |
– |
– |
17 |
The UE transmits a MeasurementReport message on NR Cell 1 to report event A3 with the measured RSRP, RSRQ value for NR Cell 3. |
–> |
NR RRC: MeasurementReport |
– |
– |
18 |
The SS transmits an RRCReconfiguration message on NR Cell 1 to order the UE to perform handover to NR Cell 3 and to release SCell NR Cell3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 19 the steps specified in Table 8.1.4.1.9.1.3.2-3 should take place. |
– |
– |
– |
– |
19 |
The SS changes NR Cell 1 and NR Cell 3 parameters according to the row "T4" in table 8.1.4.1.9.1.3.2-1/1A |
– |
– |
– |
– |
20 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 3? |
–> |
NR RRC: RRCReestablishmentRequest |
2 |
P |
21 |
The SS transmits an RRCReestablishment message to resume SRB1 operation and re-activate security on NR Cell 3. |
<– |
NR RRC: RRCReestablishment |
– |
– |
22 |
The UE transmits an RRCReestablishmentComplete message |
–> |
NR RRC: RRCReestablishmentComplete |
– |
– |
23 |
The SS transmits an RRCReconfiguration message to resume existing radio bearer on NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
24 |
The UE transmits an RRCReconfigurationComplete message on NR Cell 3. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
Table 8.1.4.1.9.1.3.2-3: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
– |
EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304. |
– |
– |
– |
– |
1 |
The UE attempts to perform the inter frequency handover using MAC Random Access Preamble on NR Cell 3. |
– |
– |
– |
– |
2 |
The SS does not respond. |
– |
– |
– |
– |
8.1.4.1.9.1.3.3 Specific message contents
Table 8.1.4.1.9.1.3.3-1: SIB1 for NR Cell 1 and NR Cell 3 (Preamble and all the steps in Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4] table 4.6.1-28 |
||||
Information Element |
Value/Remark |
Comment |
Condition |
|
SIB1 ::= SEQUENCE { |
||||
servingCellConfigCommon SEQUENCE { |
||||
uplinkConfigCommon SEQUENCE { |
||||
initialUplinkBWP SEQUENCE { |
||||
rach-ConfigCommon SEQUENCE { |
||||
rach-ConfigGeneric SEQUENCE { |
||||
preambleTransMax |
n50 |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.1.9.1.3.3-2: RRCReconfiguration (step 1 and 13B, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
masterCellGroup |
CellGroupConfig |
||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-3: CellGroupConfig (Table 8.1.4.1.9.1.3.3-2)
Derivation path: TS 38.508-1 [4], table 4.6.3-19 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellIndex |
1 |
||
sCellConfigCommon |
ServingCellConfigCommon |
||
sCellConfigDedicated |
ServingCellConfig |
||
} |
|||
} |
|||
sCellToReleaseList |
Not present |
||
} |
Table 8.1.4.1.9.1.3.3-4: ServingCellConfigCommon (Table 8.1.4.1.9.1.3.3-3)
Derivation Path: TS 38.508-1 [4], table 4.6.3-168 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ServingCellConfigCommon ::= SEQUENCE { |
|||
physCellId |
Physical layer cell identity of NR Cell 3 |
||
} |
Table 8.1.4.1.9.1.3.3-5: RRCReconfiguration (steps 3 and 14, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 and condition NR_MEAS |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
measConfig |
MeasConfig |
Table 8.1.4.1.9.1.3.3-6 |
|
nonCriticalExtension SEQUENCE { |
|||
masterCellGroup |
CellGroupConfig |
Table 8.1.4.1.9.1.3.3-9A |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-6: MeasConfig (Table 8.1.4.1.9.1.3.3-5)
Derivation path: TS 38.508-1[4], table 4.6.3-69 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
measConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
2 entries |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR-f1 |
NR Cell 1 |
|
} |
|||
} |
|||
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
measObjectId |
2 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR-f2 |
NR Cell 3 |
|
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId[1] |
1 |
||
reportConfig[1] CHOICE { |
|||
reportConfigNR |
ReportConfigNR-A3 |
||
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
2 |
||
reportConfigId |
1 |
||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-7: MeasObjectNR-f1 (Table 8.1.4.1.9.1.3.3-6)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
Downlink ARFCN of NR Cell 1 SSB |
||
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.1.9.1.3.3-8: MeasObjectNR-f2 (Table 8.1.4.1.9.1.3.3-6)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
Downlink ARFCN of NR Cell 3 SSB |
||
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.1.9.1.3.3-9: ReportConfigNR-A3 (Table 8.1.4.1.9.1.3.3-6)
Derivation Path: TS 38.508-1 [4], table 4.6.3-142 with condition EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR::= SEQUENCE { |
|||
reportType CHOICE { |
|||
eventTriggered SEQUENCE { |
|||
eventId CHOICE { |
|||
eventA3 SEQUENCE { |
|||
a3-Offset CHOICE { |
|||
rsrp |
2 |
1 dB (2*0.5 dB) |
FR1 |
FFS |
FR2 |
||
} |
|||
timeToTrigger |
ms2560 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-9A: CellGroupConfig (Table 8.1.4.1.9.1.3.3-5)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition MEAS |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig { |
1 entry |
||
SCellConfig[1] SEQUENCE { |
entry 1 |
||
sCellIndex |
SCellIndex of Cell 3 |
||
sCellConfigDedicated |
ServingCellConfig |
Table 8.1.4.1.9.1.3.3-9B |
|
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-9B: ServingCellConfig (Table 8.1.4.1.9.1.3.3-9A)
Derivation Path: TS 38.331 [6], Table 4.6.3-167 with condition MEAS |
|||
Information Element |
Value/remark |
Comment |
Condition |
ServingCellConfig ::= SEQUENCE { |
|||
servingCellMO |
2 |
||
} |
Table 8.1.4.1.9.1.3.3-10: MeasurementReport (steps 6 and 17, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-5A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasurementReport ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
measurementReport SEQUENCE { |
|||
measResults SEQUENCE { |
|||
measResultServingMOList |
Not checked |
||
measResultNeighCells CHOICE { |
1 entry |
||
measResultListNR SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultNR { |
|||
MeasResultNR[1] SEQUENCE { |
entry 1 |
||
physCellId |
PhysCellId of NR Cell 3 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrp |
(0..127) |
||
sinr |
(0..127) |
||
} |
|||
resultsCSI-RS-Cell |
Not present |
||
} |
|||
rsIndexResults |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-11: RRCReconfiguration (steps 7 and 18, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition NR |
|||
Information Element |
Value/Remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
|||
masterCellGroup |
CellGroupConfig |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-12: CellGroupConfig (Table 8.1.4.1.9.1.3.3-11)
Derivation path: TS 38.508-1 [4] table 4.6.3-19 with condition PCell_Change |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
CellGroupConfig ::= SEQUENCE { |
||||
spCellConfig SEQUENCE { |
||||
reconfigurationWithSync SEQUENCE { |
||||
spCellConfigCommon SEQUENCE { |
||||
physCellId |
PhysCellId of NR Cell 3 |
|||
downlinkConfigCommon SEQUENCE { |
||||
frequencyInfoDL SEQUENCE { |
||||
absoluteFrequencySSB |
Downlink ARFCN of NR Cell 3 SSB |
|||
} |
||||
} |
||||
} |
||||
rach-ConfigDedicated CHOICE { |
||||
uplink SEQUENCE { |
||||
cfra SEQUENCE { |
||||
resources CHOICE { |
||||
ssb SEQUENCE { |
||||
ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource { |
1 entry |
|||
CFRA-SSB-Resource[1] SEQUENCE { |
entry 1 |
|||
ra-PreambleIndex |
63 |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex { |
1 entry |
|||
SCellIndex[1] |
1 |
entry 1 SCellIndex of NR Cell 3 |
||
} |
||||
} |
Table 8.1.4.1.9.1.3.3-13: RRCReestablishmentRequest (steps 9 and 20, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-12 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishmentRequest ::= SEQUENCE { |
|||
ue-Identity SEQUENCE { |
|||
physCellId |
PhysCellId of NR Cell 1 |
||
} |
|||
reestablishmentCause |
handoverFailure |
||
} |
Table 8.1.4.1.9.1.3.3-14: RRCReestablishment (steps 10 and 21, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-10 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReestablishment ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReestablishment SEQUENCE { |
|||
nextHopChainingCount |
0 |
||
} |
|||
} |
|||
} |
Table 8.1.4.1.9.1.3.3-15: RRCReconfiguration (Steps 12 and 23, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition REEST |
8.1.4.1.9.2 NR CA / Intra NR handover / Failure / Re-establishment successful / Inter-band CA
8.1.4.1.9.2.1 Test Purpose (TP)
Same as TC 8.1.4.1.9.1 but applied to Inter-band CA case
8.1.4.1.9.2.2 Conformance requirements
Same as TC 8.1.4.1.9.1 but applied to Inter-band CA case
8.1.4.1.9.2.3 Test Description
8.1.4.1.9.2.3.1 Pre-test conditions
Same as test case 8.1.4.1.9.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: NR Cell 10 replaces NR Cell 3.
– NR Cell 10 is an Inactive SCell according to TS 38.508-1 [4] clause 6.3.1.
8.1.4.1.9.2.3.2 Test procedure sequence
Same as test case 8.1.4.1.9.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.1.4.1.9.2.3.3 Specific message contents
Same as TC 8.1.4.1.9.1 but applied to Inter-band CA case
8.1.4.1.9.3 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band non-contiguous CA
8.1.4.1.9.3.1 Test Purpose (TP)
Same as TC 8.1.4.1.9.1 but applied to Intra-band non-contiguous CA case
8.1.4.1.9.3.2 Conformance requirements
Same as TC 8.1.4.1.9.1 but applied to Intra-band non-contiguous CA case
8.1.4.1.9.3.3 Test Description
8.1.4.1.9.3.3.1 Pre-test conditions
Same as test case 8.1.4.1.9.1 with the following differences:
– CA configuration: Intra-band Contiguous CA replaces Intra-band non-contiguous CA.
8.1.4.1.9.3.3.2 Test procedure sequence
Same as test case 8.1.4.1.9.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
8.1.4.1.9.3.3.3 Specific message contents
Same as TC 8.1.4.1.9.1 but applied to Intra-band non-contiguous CA case
8.1.4.1.10 eCall Only mode / Intra NR handover / Success / Inter-frequency
8.1.4.1.10.1 Test Purpose (TP)
(1)
with { UE in eCall Only mode and an eCall over IMS is ongoing }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for handover }
then { UE performs handover to the target cell and transmits an RRCReconfigurationComplete message }
}
8.1.4.1.10.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.3.5.3, 5.3.5.5.1, 5.3.5.5.2, 5.5.4.4, 5.2.2.4.2 and 6.2.2.
[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 RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
…
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
…
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
…
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> stop timer T310 for source SpCell if running;
…
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;
…
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if T390 is running:
4> stop timer T390 for all access categories;
4> perform the actions as specified in 5.3.14.4.
3> if T350 is running:
4> stop timer T350;
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
…
2> the procedure ends.
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.1]
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended;
…
1> if the CellGroupConfig contains the rlc-BearerToAddModList:
2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;
1> if the CellGroupConfig contains the mac-CellGroupConfig:
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;
…
1> if the CellGroupConfig contains the spCellConfig:
2> configure the SpCell as specified in 5.3.5.5.7;
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> if no DAPS bearer is configured:
2> stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
1> stop timer T312 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
…
1> else:
2> reset the MAC entity of this cell group;
2> consider the SCell(s) of this cell group, if configured, that are not included in the SCellToAddModList in the RRCReconfiguration message, to be in deactivated state;
2> apply the value of the newUE-Identity as the C-RNTI for this cell group;
2> configure lower layers in accordance with the received spCellConfigCommon;
2> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.5.4.4]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;
1> use the SpCell for Mp, Ofp and Ocp.
NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.
Inequality A3-1 (Entering condition)
Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off
Inequality A3-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off
The variables in the formula are defined as follows:
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Mp is the measurement result of the SpCell, not taking into account any offsets.
Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).
Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).
Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.
NOTE 2: The definition of Event A3 also applies to CondEvent A3.
[TS 38.331, clause 5.2.2.4.2]
Upon receiving the SIB1 the UE shall:
1> store the acquired SIB1;
…
4> forward the eCallOverIMS-Support to upper layers, if present;
[TS 38.331, clause 6.2.2]
eCallOverIMS-Support
Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.
8.1.4.1.10.3 Test description
8.1.4.1.10.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the serving cell and NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.
– 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:
– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.
Preamble:
– An automatic eCall is established by following the test procedure as defined in TS 38.508-1 [4], subclause 4.9.29.
8.1.4.1.10.3.2 Test procedure sequence
Table 8.1.4.1.10.3.2-1 illustrate the downlink power levels to be applied for NR Cell 1 and NR Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.4.1.10.3.2-2.
Table 8.1.4.1.10.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-91 |
Power levels are such that entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-79 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 3 |
Editor’s Note: FR2 power levels are FFS
Table 8.1.4.1.10.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig to setup intra NR measurement and reporting for inter-frequency event A3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
4 |
The UE transmits a MeasurementReport message to report event A3 with the measured RSRP value for NR Cell 3. |
–> |
NR RRC: MeasurementReport |
– |
– |
5 |
The SS transmits an RRCReconfiguration message including reconfigurationWithSync to order the UE to perform inter-frequency handover to NR Cell 3. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
6 |
Check: Does the UE transmit RRCReconfigurationComplete message on NR Cell 3? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
7 |
Release eCall over IMS using the generic procedure described in TS 34.229-5 [41] subclause A.8. |
– |
– |
– |
– |
8.1.4.1.10.3.3 Specific message contents
Table 8.1.4.1.10.3.3-1: SIB1 for NR Cell 1, NR Cell 3 (All steps, Table 8.1.4.1.10.3.2-2)
Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR |
Table 8.1.4.1.10.3.3-2: RRCReconfiguration (step 1, Table 8.1.4.1.10.3.2-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition MEAS |
Table 8.1.4.1.10.3.3-3: MeasConfig (Table 8.1.4.1.10.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
2 entries |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 3 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
MeasObjectToAddMod[2] SEQUENCE { |
entry 2 |
||
measObjectId |
2 |
||
measObject CHOICE { |
|||
measObjectNR SEQUENCE { |
|||
ssbFrequency |
ssbFrequency IE equals the ARFCN for NR Cell 1 |
||
absThreshSS-BlocksConsolidation |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-EventA3 |
||
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
measGapConfig |
MeasGapConfig |
||
} |
Table 8.1.4.1.10.3.3-4: ReportConfigNR-EventA3 (Table 8.1.4.1.10.3.3-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
eventTriggered SEQUENCE { |
|||
eventId CHOICE { |
|||
eventA3 SEQUENCE { |
EVENT_A3 |
||
a3-Offset CHOICE { |
|||
rsrp |
6 |
3dB |
|
} |
|||
hysteresis |
0 |
0 dB |
|
timeToTrigger |
ms640 |
||
} |
|||
} |
|||
reportAmount |
r1 |
||
reportQuantityCell SEQUENCE { |
|||
rsrp |
true |
||
rsrq |
false |
||
sinr |
false |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.10.3.3-5: MeasurementReport (step 4, Table 8.1.4.1.10.3.2-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-5A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasurementReport ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
measurementReport SEQUENCE { |
|||
measResults SEQUENCE { |
|||
measId |
1 |
||
measResultServingMOList SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO { |
1 entry |
||
MeasResultServMO[1] SEQUENCE { |
entry 1 |
||
servCellId |
Cell index corresponding to NR Cell 1 |
||
measResultServingCell SEQUENCE { |
|||
physCellId |
Physical layer cell identity of NR Cell 1 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
(0..127) |
||
sinr |
Not present |
||
Not checked |
pc_ss_SINR_Meas |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
measResultNeighCells CHOICE { |
|||
measResultListNR SEQUENCE (SIZE (1.. maxCellReport)) OF MeasResultNR { |
1 entry |
||
MeasResultNR[1] SEQUENCE { |
entry 1 |
||
physCellId |
Physical layer cell identity of NR Cell 3 |
||
measResult SEQUENCE { |
|||
cellResults SEQUENCE { |
|||
resultsSSB-Cell SEQUENCE { |
|||
rsrp |
(0..127) |
||
rsrq |
Not present |
||
sinr |
Not present |
||
} |
|||
resultsCSI-RS-Cell |
Not present |
||
} |
|||
rsIndexResults |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.10.3.3-6: RRCReconfiguration (step 5, Table 8.1.4.1.10.3.2-2)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
|||
measConfig SEQUENCE { |
|||
measObjectToRemoveList SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId { |
2 entries |
||
measObjectId[1] |
1 |
entry 1 |
|
measObjectId[2] |
2 |
entry 2 |
|
} |
|||
measIdToRemoveList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId { |
1 entry |
||
measId[1] |
1 |
entry 1 |
|
} |
|||
} |
|||
masterCellGroup |
OCTET STRING (CONTAINING CellGroupConfig) |
||
masterKeyUpdate SEQUENCE { |
|||
keySetChangeIndicator |
True |
||
nextHopChainingCount |
0 |
||
nas-Container |
NASContainer |
Intra N1 mode NAS transparent container |
|
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.10.3.3-7: CellGroupConfig (Table 8.1.4.1.10.3.3-6)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
Same as default ServingCellConfigCommon |
||
physCellId |
Physical cell Id of NR Cell 3 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.1.10.3.3-8: NASContainer (Table 8.1.4.1.10.3.3-6)
Derivation Path: TS 24.501, table 9.11.2.6 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Message authentication code |
The calculated value of MAC-I for this message. |
The value of MAC-I is calculated by SS using COUNT = 0xFFFFFFFF( as per TS 33.501[20], 6.9.2.3.3) |
|
Type of ciphering algorithm |
Set according to PIXIT px_NAS_5GC_CipheringAlgorithm for default ciphering algorithm |
||
Type of integrity protection algorithm |
Set according to PIXIT px_NAS_5GC_IntegrityAlgorithm for default integrity protection algorithm |
This value should not be equal to the null integrity algorithm. |
|
KACF |
‘1’B |
a new KAMF has been calculated by the network |
|
TSC |
‘0’B |
native security context (for KSIAMF) |
|
Key set identifier in 5G |
KSIAMF that was created when the UE last registered to 5GCN |
||
Sequence number |
The internal counter of the SS |
eight least significant bits of the downlink NAS COUNT |
8.1.4.2 Inter-RAT handover
8.1.4.2.1 Inter-RAT handover from NR
8.1.4.2.1.1 Inter-RAT handover / From NR to E-UTRA / Success
8.1.4.2.1.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a MobilityFromNRCommand message }
then { UE transmits an RRCConnectionReconfigurationComplete message on the E-UTRA cell }
}
8.1.4.2.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.4.3.2, clause 5.4.3.3 and clause 5.4.3.4 and TS 36.331, clause 5.4.2.2 and clause 5.4.2.3.
[TS.38.331, clause 5.4.3.2]
The network initiates the mobility from NR procedure to a UE in RRC_CONNECTED, possibly in response to a MeasurementReport message, by sending a MobilityFromNRCommand message. The network applies the procedure as follows:
– the procedure is initiated only when AS-security has been activated, and SRB2 with at least one DRB are setup and not suspended.
[TS 38.331, clause 5.4.3.3]
The UE shall:
1> if the targetRAT-Type is set to eutra:
2> consider inter-RAT mobility as initiated towards E-UTRA;
2> forward the nas-SecurityParamFromNR to the upper layers, if included;
1> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT.
[TS.38.331, clause 5.4.3.4]
Upon successfully completing the handover, at the source side the UE shall:
1> reset MAC;
1> stop all timers that are running;
1> release ran-NotificationAreaInfo, if stored;
1> release the AS security context including the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if stored;
1> release all radio resources, including release of the RLC entity and the MAC configuration;
1> release the associated PDCP entity and SDAP entity for all established RBs;
NOTE : PDCP and SDAP configured by the source RAT prior to the handover that are reconfigured and re-used by target RAT when delta signalling (i.e., during inter-RAT intra-system handover when fullConfig is not present) is used, are not released as part of this procedure.
1> indicate the release of the RRC connection to upper layers together with the release cause ‘other’.
[TS 36.331, clause 5.4.2.2]
The RAN using another RAT or the E-UTRA connected to a different type of CN initiates the handover to E-UTRA procedure, in accordance with the specifications applicable for the other RAT or for the E-UTRA connected to a different type of CN, by sending the RRCConnectionReconfiguration message via the radio access technology from which the inter-RAT handover is performed.
E-UTRAN applies the procedure as follows:
– to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT or in the E-UTRA connected to a different type of CN;
– to establish SRB1, SRB2 and one or more DRBs, i.e. at least the DRB associated with the default EPS bearer is established if the target CN is EPC and at least one DRB is established if the target CN is 5GC.
[TS 36.331, clause 5.4.2.3]
If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE shall:
1> if the RRCConnectionReconfiguration message includes the fullConfig and the source RAT was E-UTRA(i.e., intra-RAT inter-system handover):
…
1> apply the default physical channel configuration as specified in 9.2.4;
1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;
1> apply the default MAC main configuration as specified in 9.2.2;
1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;
1> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;
1> start synchronising to the DL of the target PCell;
1> set the C-RNTI to the value of the newUE-Identity;
1> for the target PCell, apply the downlink bandwidth indicated by the dl-Bandwidth;
1> for the target PCell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;
1> configure lower layers in accordance with the received radioResourceConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;
1> perform the radio resource configuration procedure as specified in 5.3.10;
1> if the handoverType in securityConfigHO is set to fivegc-ToEPC:
2> indicate to higher layer that the CN has changed from 5GC to EPC;
2> derive the key KeNB based on the mapped KASME key as specified for interworking between EPS and 5GS in TS 33.501 [86];
2> store the nextHopChainingCount-r15 value;
1> else if the handoverType in securityConfigHO is set to intra5GC:
…
1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];
1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];
…
1> if the handoverType in securityConfigHO is set to fivegc-ToEPC or if the handoverType-v1530 is not present:
2> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint key immediately, i.e. the indicated integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
2> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc key immediately, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
…
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
…
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;
1> if the RRCConnectionReconfiguration message does not include rlf-TimersAndConstants set to setup:
2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;
1> if MAC successfully completes the random access procedure:
2> stop timer T304;
2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;
NOTE 1: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.
2> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;
8.1.4.2.1.1.3 Test description
8.1.4.2.1.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 and E-UTRA Cell 1.
– System information Combination NR-6 as defined in TS 38.508 [4] clause 4.4.3.1 is used in NR cells.
UE:
– None
Preamble:
– The UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.2.1.1.3.2 Test procedure sequence
Table 8.1.4.2.1.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits a MobilityFromNRCommand message on NR Cell 1. |
<– |
MobilityFromNRCommand |
– |
– |
2 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on E-UTRA Cell 1 using the security key derived from the new KeNB? |
–> |
RRCConnectionReconfigurationComplete |
1 |
P |
3 |
The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE REQUEST message. |
–> |
RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST |
– |
– |
4 |
The SS transmits a DLInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE ACCEPT message. |
<– |
RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT |
– |
– |
5 |
The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE COMPLETE message. |
–> |
RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE |
– |
– |
6 |
Void |
– |
– |
– |
– |
7 |
The SS sends one IP Packet to the UE on the default DRB associated with the first PDU session. |
– |
– |
– |
– |
8 |
The UE loop backs the IP packet received in step 7. |
– |
– |
1 |
P |
8.1.4.2.1.1.3.3 Specific message contents
Table 8.1.4.2.1.1.3.3-1: MobilityFromNRCommand (step 1, Table 8.1.4.2.1.1.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-8 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
MobilityFromNRCommand::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
|||
criticalExtensions CHOICE { |
||||
mobilityFromNRCommand SEQUENCE { |
||||
targetRAT-Type |
eutra |
|||
targetRAT-MessageContainer |
DL-DCCH message containing RRCConnectionReconfiguration |
|||
nas-SecurityParamFromNR |
8 LSB of the downlink NAS COUNT |
|||
} |
||||
} |
||||
} |
Table 8.1.4.2.1.1.3.3-2: RRCConnectionReconfiguration (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0) |
Table 8.1.4.2.1.1.3.3-3: MobilityControlInfo (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.5-1, condition HO-TO-EUTRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
MobilityControlInfo ::= SEQUENCE { |
|||
targetPhysCellId |
PhysicalCellIdentity of E-UTRA Cell 1 |
||
carrierFreq SEQUENCE { |
|||
dl-CarrierFreq |
Same downlink EARFCN as used for E-UTRA Cell 1 |
||
} |
|||
carrierFreq |
Not present |
Band > 64 |
|
carrierBandwidth SEQUENCE { |
|||
dl-Bandwidth |
Downlink system bandwidth under test. |
||
ul-Bandwidth |
Uplink Bandwidth under test. |
FDD |
|
ul-Bandwidth |
Not present |
TDD |
|
} |
|||
carrierFreq-v9e0 SEQUENCE { |
Band > 64 |
||
dl-CarrierFreq-v9e0 |
Same downlink EARFCN as used for E-UTRA Cell 1 |
||
} |
|||
} |
Condition |
Explanation |
FDD |
FDD cell environment |
TDD |
TDD cell environment |
Band > 64 |
If band > 64 is selected |
Table 8.1.4.2.1.1.3.3-4: SecurityConfigHO (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508, Table 4.6.4-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SecurityConfigHO-v1530 ::= SEQUENCE { |
|||
handoverType-v1530 CHOICE { |
|||
fivegc-ToEPC-r15 SEQUENCE { |
|||
securityAlgorithmConfig-r15 SEQUENCE { |
|||
cipheringAlgorithm |
Set according to PIXIT parameter for default ciphering algorithm |
||
integrityProtAlgorithm |
Set according to PIXIT parameter for default integrity protection algorithm |
||
} |
|||
nextHopChainingCount-r15 |
2 |
||
} |
|||
} |
|||
} |
Table 8.1.4.2.1.1.3.3-5: Void
Table 8.1.4.2.1.1.3.3-6: TRACKING AREA UPDATE REQUEST (step 3, Table 8.1.4.2.1.1.3.2-1)
Derivation Path: TS 38.508-1 table 4.9.7.2.3-1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
EPS update type |
||||
EPS update type Value |
‘000’B |
TA updating |
TA_only |
|
‘001’B |
Combined TA/LA updating |
combined_TA_LA_without_IMSI |
||
‘010’B |
Combined TA/LA updating with IMSI attach |
combined_TA_LA |
||
NAS key set identifier |
||||
NAS Key Set Identifier |
The value of ngKSI assigned in preamble |
|||
Type of security context flag |
‘1’B |
Mapped security context |
||
Non-current native NAS key set identifier |
Not present or any allowed value |
|||
Old GUTI |
Mapped 5G-GUTI |
|||
EPS bearer context status |
Not checked |
Condition |
Explanation |
TA_only |
The UE is configured to initiate EPS attach |
combined_TA_LA |
The UE is configured to initiate combined EPS/IMSI attach |
combined_TA_LA_without_IMSI |
The UE is configured to initiate combined attach |
Table 8.1.4.2.1.1.3.3-7: Void
8.1.4.2.1.2 Inter-RAT handover / From NR to EN-DC / Success
8.1.4.2.1.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives a MobilityFromNRCommand message with the embedded RRCConnectionReconfiguration message including nr-SecondaryCellGroupConfig }
then { UE transmits an RRCConnectionReconfigurationComplete message embedding an RRCReconfigurationComplete message on the E-UTRA cell }
}
8.1.4.2.1.2.2 Conformance requirements
Same as TC 8.1.4.2.1.1 with the addition of: Rel-16 TS 36.331, clause 5.3.5.4 and Rel-16 TS 37.340, clause 10.16.1.
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
1> if the RRCConnectionReconfiguration message includes the fullConfig:
…
1> if the received RRCConnectionReconfiguration includes the sk-Counter:
2> perform key update procedure as specified in in TS 38.331 [82], clause 5.3.5.7;
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> 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> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;
[TS 37.340, clause 10.16.1]
Inter-system HO from NR to E-UTRA with EN-DC configuration is supported in this version of the specification. N26 based inter-system HO will be executed between source RAN and gNB.
8.1.4.2.1.2.3 Test description
8.1.4.2.1.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the serving cell. System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR Cell 1.
– E-UTRA Cell 1 (PCell) and NR Cell 3 (PSCell) are the target cells. System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1 is used in the E-UTRA cell. Only NR MIB is broadcasted on NR Cell 3.
UE:
– None
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.2.1.2.3.2 Test procedure sequence
Table 8.1.4.2.1.2.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0A |
The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add DRB#a associated with a new QoS Flow. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
0B |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
0C |
The UE transmits a ULInformationTransfer message, an UL NAS TRANSPORT message and an PDU SESSION MODIFICATION COMPLETE message |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
– |
1 |
The SS transmits a MobilityFromNRCommand message on NR Cell 1,and embedded RRCConnectionReconfiguration message contains nr-SecondaryCellGroupConfig with the configuration of NR Cell 3 |
<– |
MobilityFromNRCommand (RRCConnectionReconfiguration) |
– |
– |
2 |
Check: Does the UE transmit an RRCConnectionReconfigurationComplete containing NR RRCReconfigurationComplete message on E-UTRA Cell 1 using the security key derived from the new KeNB and sk-Counter? |
–> |
RRCConnectionReconfigurationComplete (RRCReconfigurationComplete) |
1 |
P |
3 |
The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE REQUEST message. |
–> |
RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST |
– |
– |
4 |
The SS transmits a DLInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE ACCEPT message. |
<– |
RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT |
– |
– |
5 |
The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE COMPLETE message. |
–> |
RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE |
– |
– |
6 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on DRB#b associated with the default EPS bearer in E-UTRA Cell 1 |
– |
– |
1 |
P |
7 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.1 indicate that the UE is capable of exchanging IP data on the SCG DRB#a in NR Cell 3 |
– |
– |
1 |
P |
Tables 8.1.4.2.1.2.3.2-1a and 8.1.4.2.1.2.3.2-1b illustrate the downlink power levels to be applied for NR Cell 3, and E-UTRA Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble.
Table 8.1.4.2.1.2.3.2-1a: Time instances of cell power level and parameter changes for conducted test environment
Parameter |
Unit |
NR Cell 3 |
E-UTRA Cell 1 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
– |
|
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
Table 8.1.4.2.1.2.3.2-1b: Time instances of cell power level and parameter changes for OTA test environment
Parameter |
Unit |
NR Cell 3 |
E-UTRA Cell 1 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
– |
|
Cell-specific RS EPRE |
dBm/15kHz |
FFS |
8.1.4.2.1.2.3.3 Specific message contents
Table 8.1.4.2.1.2.3.3-0A: PDU SESSION MODIFICATION COMMAND (step 0A, Table 8.1.4.2.1.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 |
|||
Mapped EPS bearer contexts |
||||
Mapped EPS bearer context |
||||
EPS bearer identity |
(DRB#a + 4) |
|||
Operation code |
‘001’B |
Create new EPS bearer |
||
E bit |
‘1’B |
Parameters list is included |
||
Number of EPS parameters |
’0010’B |
2 parameters |
||
Mapped EPS QoS parameters |
EPC dedicated bearer context of the entry in TS 38.508-1 [4] Table 4.8.4-1 which has been determined by the DNN IE in the UL NAS TRANSPORT message which carried the corresponding PDU SESSION ESTABLISHMENT REQUEST or by pc_APN_Default_Configuration if the DNN IE was not present |
|||
TFT |
EPC dedicated bearer context of the entry in TS 38.508-1 [4] Table 4.8.4-1 which has been determined by the DNN IE in the UL NAS TRANSPORT message which carried the corresponding PDU SESSION ESTABLISHMENT REQUEST or by pc_APN_Default_Configuration if the DNN IE was not present. Reference dedicated EPS bearer context #1 as specified in TS 36.508 [10], Table 6.6.2-1. |
|||
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-1. |
QFI=5 |
||
Authorized QoS flow descriptions |
One entry |
|||
QoS flow [1] |
Dedicated QoS Flow |
QFI=5 |
||
NOTE: The mapped EPS bearer will become the Dedicated EPS Bearer after handover. |
Table 8.1.4.2.1.2.3.3-0B: Dedicated QoS Flow (step 0A, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 24.501, table 9.11.4.12 |
|||
Information Element |
Value/remark |
Comment |
Condition |
QoS flow descriptions |
|||
QoS flow description |
|||
QFI |
‘00 0101’B |
QFI 5 |
|
Operation code |
‘001’B |
Create new QoS flow description |
|
E bit |
‘1’B |
Parameters list is included |
|
Number of parameters |
’00 0010’B |
2 parameters |
|
5QI |
5QI 1 |
5QI 1 |
|
EPS bearer identity |
(DRB#a + 4) |
EBI related to NR DRB#a |
Table 8.1.4.2.1.2.3.3-0C: RRCReconfiguration (step 0A, Table8.1.4.2.1.2.3.2-1)
Derivation Path: TS xx?? Table 4.6.1-13 with condition NR. |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
radioBearerConfig |
RadioBearerConfig-HO-ENDC |
||
} |
|||
nonCriticalExtension SEQUENCE { |
|||
masterCellGroup |
CellGroupConfig-DRB(1,0) |
OCTET STRING (CONTAINING CellGroupConfig) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.2.1.2.3.3-0D: RadioBearerConfig-HO-ENDC (Table 8.1.4.2.1.2.3.3-0C)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 |
||||||||
Information Element |
Value/remark |
Comment |
Condition |
|||||
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
|||||||
DRB-ToAddMod[1] SEQUENCE { |
||||||||
cnAssociation CHOICE { |
||||||||
sdap-Config SEQUENCE { |
SDAP-Config |
|||||||
defaultDRB |
false |
|||||||
} |
||||||||
} |
||||||||
drb-Identity |
DRB-Identity using condition DRB#a |
|||||||
reestablishPDCP |
Not present |
|||||||
recoverPDCP |
Not present |
|||||||
pdcp-Config |
PDCP-Config |
|||||||
} |
||||||||
} |
||||||||
NOTE: DRB#a will become the Dedicated EPS Bearer and the SCG DRB on NR Cell 3 after Handover. |
Table 8.1.4.2.1.2.3.3-1: MobilityFromNRCommand (step 1, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-8 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
MobilityFromNRCommand::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
|||
criticalExtensions CHOICE { |
||||
mobilityFromNRCommand SEQUENCE { |
||||
targetRAT-Type |
eutra |
|||
targetRAT-MessageContainer |
DL-DCCH message containing RRCConnectionReconfiguration |
|||
nas-SecurityParamFromNR |
8 LSB of the downlink NAS COUNT |
|||
} |
||||
} |
||||
} |
Table 8.1.4.2.1.2.3.3-2: RRCConnectionReconfiguration (Table 8.1.4.2.1.2.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.1-8, condition HO-TO-EN-DC(x,0) |
|||||
Information Element |
Value/remark |
Comment |
Condition |
||
mobilityControlInfo |
MobilityControlInfo_EN-DC |
||||
nr-SecondaryCellGroupConfig-r15 |
OCTET STRING including the RRCReconfiguration message and CellGroupConfig_EN-DC |
||||
nr-RadioBearerConfig1-r15 |
OCTET STRING including RadioBearerConfig_EN-DC |
||||
NOTE: x is equal to the number of PDU sessions established on NR Cell 1. These are all included in the HO to E-UTRA. |
Table 8.1.4.2.1.2.3.3-2A: CellGroupConfig_EN-DC (Table 8.1.4.2.1.2.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC |
||||||||
Information Element |
Value/remark |
Comment |
Condition |
|||||
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
1 entry |
|||||||
RLC-BearerConfig[1] |
RLC-BearerConfig with conditions AM and DRB#a |
entry 1 |
||||||
} |
||||||||
} |
||||||||
NOTE: DRB#a is the SCG DRB on NR Cell 3 after Handover |
Table 8.1.4.2.1.2.3.3-2B: RadioBearerConfig_EN-DC (Table 8.1.4.2.1.2.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 |
||||||||
Information Element |
Value/remark |
Comment |
Condition |
|||||
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod { |
1 entry |
|||||||
DRB-ToAddMod[1] SEQUENCE { |
entry 1 |
|||||||
cnAssociation CHOICE { |
||||||||
eps-BearerIdentity |
(DRB#a + 4) |
|||||||
} |
||||||||
drb-Identity |
DRB-Identity using condition DRB#a |
|||||||
reestablishPDCP |
true |
|||||||
recoverPDCP |
Not present |
|||||||
pdcp-Config |
PDCP-Config |
|||||||
} |
||||||||
} |
||||||||
NOTE: DRB#a is the SCG DRB on NR Cell associated with the Dedicated EPS Bearer after handover. |
Table 8.1.4.2.1.2.3.3-3: MobilityControlInfo_EN-DC (Table 8.1.4.2.1.2.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.5-1, condition HO-TO-EN-DC |
|||
Information Element |
Value/remark |
Comment |
Condition |
MobilityControlInfo ::= SEQUENCE { |
|||
targetPhysCellId |
PhysicalCellIdentity of E-UTRA Cell 1 |
||
carrierFreq SEQUENCE { |
|||
dl-CarrierFreq |
Same downlink EARFCN as used for E-UTRA Cell 1 |
||
} |
|||
carrierFreq |
Not present |
Band > 64 |
|
carrierBandwidth SEQUENCE { |
|||
dl-Bandwidth |
Downlink system bandwidth under test. |
||
ul-Bandwidth |
Uplink Bandwidth under test. |
FDD |
|
ul-Bandwidth |
Not present |
TDD |
|
} |
|||
carrierFreq-v9e0 SEQUENCE { |
Band > 64 |
||
dl-CarrierFreq-v9e0 |
Same downlink EARFCN as used for E-UTRA Cell 1 |
||
} |
|||
} |
Condition |
Explanation |
FDD |
FDD cell environment |
TDD |
TDD cell environment |
Band > 64 |
If band > 64 is selected |
Table 8.1.4.2.1.2.3.3-4: SecurityConfigHO (Table 8.1.4.2.1.2.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.4-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SecurityConfigHO-v1530 ::= SEQUENCE { |
|||
handoverType-v1530 CHOICE { |
|||
fivegc-ToEPC-r15 SEQUENCE { |
|||
securityAlgorithmConfig-r15 SEQUENCE { |
|||
cipheringAlgorithm |
Set according to PIXIT parameter for default ciphering algorithm |
||
integrityProtAlgorithm |
Set according to PIXIT parameter for default integrity protection algorithm |
||
} |
|||
nextHopChainingCount-r15 |
2 |
||
} |
|||
} |
|||
} |
Table 8.1.4.2.1.2.3.3-5: Void
Table 8.1.4.2.1.2.3.3-6:RRCConnectionReconfigurationComplete (step 2, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 36.508 [7], Table 4.6.1-9, condition HO-TO-EN-DC(1,0) |
Table 8.1.4.2.1.2.3.3-7: TRACKING AREA UPDATE REQUEST (step 3, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 36.508 [7] clause 4.7.2-27 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
EPS update type |
||||
EPS update type Value |
‘000’B |
TA updating |
TA_only |
|
‘001’B |
Combined TA/LA updating |
combined_TA_LA_without_IMSI |
||
‘010’B |
Combined TA/LA updating with IMSI attach |
combined_TA_LA |
||
NAS key set identifier |
||||
NAS Key Set Identifier |
The value of ngKSI assigned in preamble |
|||
Type of security context flag |
‘1’B |
Mapped security context |
||
Non-current native NAS key set identifier |
Not present or any allowed value |
|||
Old GUTI |
Mapped 5G-GUTI |
|||
GUTI type |
Native |
|||
Additional GUTI |
Any value or not present |
|||
UE status |
UE is in 5GMM-REGISTERED state |
Condition |
Explanation |
TA_only |
The UE is configured to initiate EPS attach |
combined_TA_LA |
The UE is configured to initiate combined EPS/IMSI attach |
combined_TA_LA_without_IMSI |
The UE is configured to initiate combined attach |
8.1.4.2.2 Inter-RAT handover to NR
8.1.4.2.2.1 Inter-RAT handover / From E-UTRA to NR / Success
8.1.4.2.2.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives a MobilityFromEUTRACommand message }
then { UE transmits a RRCReconfigurationComplete message on the NR cell }
}
8.1.4.2.2.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.4.2.2, 5.4.2.3, TS 36.331, clause 5.4.3.2, 5.4.3.3, 5.4.3.4.Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.4.2.2]
The RAN using another RAT initiates the handover to NR procedure, in accordance with the specifications applicable for the other RAT, by sending the RRCReconfiguration message via the radio access technology from which the inter-RAT handover is performed.
The network applies the procedure as follows:
– to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT;
– to re-establish SRBs and one or more DRBs;
[TS 38.331, clause 5.4.2.3]
The UE shall:
1> perform RRC reconfiguration procedure as specified in 5.3.5;
NOTE: If the UE is connected to 5GC of the source E-UTRA cell, the delta configuration for PDCP and SDAP can be used for intra-system inter-RAT handover.
[TS 36.331, clause 5.4.3.2]
E-UTRAN initiates the mobility from E-UTRA procedure to a UE in RRC_CONNECTED, possibly in response to a MeasurementReport message or in response to reception of CS fallback indication for the UE from MME, by sending a MobilityFromEUTRACommand message. E-UTRAN applies the procedure as follows:
– the procedure is initiated only when AS-security has been activated, and SRB2 with at least one DRB are setup and not suspended;
[TS 36.331, clause 5.4.3.3]
The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> stop timer T310, if running;
1> stop timer T312, if running;
1> if T309 is running:
2> stop timer T309 for all access categories;
2> perform the actions as specified in 5.3.16.4.
1> if the MobilityFromEUTRACommand message includes the purpose set to handover:
…
2> else if the targetRAT-Type is set to nr:
3> consider inter-RAT mobility as initiated towards NR;
3> access the target cell indicated in the inter-RAT message in accordance with the specifications in TS 38.331 [82];
[TS 36.331, clause 5.4.3.4]
Upon successfully completing the handover, the cell change order or enhanced 1xRTT CS fallback, the UE shall:
…
1> else if the UE is connected to 5GC prior to the reception of the MobilityFromEUTRACommand and the targetRAT-Type in the received MobilityFromEUTRACommand is set to nr:
2> reset MAC;
2> stop all timers that are running;
2> release ran-NotificationAreaInfo, if stored;
2> release the AS security context including the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if stored;
2> release all radio resources, including release of the RLC entity and the MAC configuration and the associated PDCP entity and SDAP entity for all established RBs;
NOTE 1: PDCP and SDAP configured by the source configurations RAT prior to the handover that are reconfigured and re-used by target RAT when delta signalling (i.e., during inter-RAT intra-sytem handover when fullConfig is not present) is used, are not released as part of this procedure.
1> else:
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;
NOTE 2: If the UE performs enhanced 1xRTT CS fallback along with concurrent mobility to CDMA2000 HRPD and the connection to either CDMA2000 1xRTT or CDMA2000 HRPD succeeds, then the mobility from E-UTRA is considered successful.
8.1.4.2.2.1.3 Test description
8.1.4.2.2.1.3.1 Pre-test conditions
System Simulator:
– E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell".
– System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1 is used in the E-UTRA cell.
– System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in the NR cell.
UE:
– None.
Preamble:
– The UE isbrought to state RRC_CONNECTED using generic procedure parameters Connectivity (E-UTRA/EPC), Unrestricted nr PDN (On), Test Loop Function (On) with UE test loop mode B, on E-UTRA Cell 1 according to the procedure described in TS 38.508-1 [4], clause 4.5.4.
8.1.4.2.2.1.3.2 Test procedure sequence
Table 8.1.4.2.2.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0 |
The SS configures NR Cell 1 as the "Serving cell" and wait 5s. |
– |
– |
– |
– |
1 |
The SS transmits a MobilityFromEUTRACommand message on E-UTRA Cell 1. |
<– |
E-UTRA RRC: MobilityFromEUTRACommand |
– |
– |
2 |
Check: Does the UE transmit a RRCReconfigurationComplete message on NR Cell 1? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
3 |
The UE transmits a ULInformationTransfer message and a REGISTRATION REQUEST message indicating “mobility registration updating” is sent to update the registration of the actual tracking area. |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION REQUEST |
– |
– |
4 |
SS sends an DLInformationTransfer message and a REGISTRATION ACCEPT message containing a 5G-GUTI. |
<– |
NR RRC: DLInformationTransfer 5GMM: REGISTRATION ACCEPT |
– |
– |
5 |
The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION COMPLETE |
– |
– |
6 |
The procedure in table 4.5A.2C.2.2-1 in TS 38.508-1 [4] is performed. |
– |
– |
– |
– |
7 |
Void |
– |
– |
– |
– |
8 |
The SS sends one IP Packet to the UE on the default DRB associated with the first PDU session. |
– |
– |
– |
– |
9 |
The UE loop backs the IP packet received in step 8. |
– |
– |
– |
– |
Table 8.1.4.2.2.1.3.2-2: Void
8.1.4.2.2.1.3.3 Specific message contents
Table 8.1.4.2.2.1.3.3-1: MobilityFromEUTRACommand (step 1, Table 8.1.4.2.2.1.3.2-1)
Derivation Path: TS 36.508 [7] table 4.6.1-6 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MobilityFromEUTRACommand ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
mobilityFromEUTRACommand-r8 SEQUENCE { |
|||
purpose CHOICE { |
|||
handover SEQUENCE { |
|||
targetRAT-Type |
nr |
||
targetRAT-MessageContainer |
RRCReconfiguration |
||
nas-SecurityParamFromEUTRA |
Not present |
||
systemInformation |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.2.2.1.3.3-2: RRCReconfiguration (Table 8.1.4.2.2.1.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
radioBearerConfig |
RadioBearerConfig as per table 4.6.3-132 in TS 38.508-1 [4] with conditions SRB1,SRB2 and DRB1 |
|||
nonCriticalExtension SEQUENCE { |
||||
masterCellGroup |
CellGroupConfig with conditions SRB1,SRB2 and DRB1 |
OCTET STRING (CONTAINING CellGroupConfig) |
||
fullConfig |
true |
|||
masterKeyUpdate |
MasterKeyUpdate |
|||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.2.2.1.3.3-3: Void
Table 8.1.4.2.2.1.3.3-4: CellGroupConfig (Table 8.1.4.2.2.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-19 |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig { |
3 entries |
||
RLC-Bearer-Config[1] |
RLC-Bearer-Config with condition SRB1 |
entry 1 |
|
RLC-Bearer-Config[2] |
RLC-Bearer-Config with condition SRB2 |
entry 2 |
|
RLC-Bearer-Config[3] |
RLC-Bearer-Config with condition DRB1 |
entry 3 |
|
} |
|||
mac-CellGroupConfig |
MAC-CellGroupConfig |
||
physicalCellGroupConfig |
PhysicalCellGroupConfig |
||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon |
ServingCellConfigCommon |
||
newUE-Identity |
RNTI-Value |
||
t304 |
ms1000 |
||
rach-ConfigDedicated CHOICE { |
|||
uplink |
RACH-ConfigDedicated |
||
supplementaryUplink |
Not present |
||
} |
|||
} |
|||
rlf-TimersAndConstants CHOICE { |
|||
setup |
RLF-TimersAndConstants |
||
} |
|||
spCellConfigDedicated |
ServingCellConfig |
||
} |
|||
} |
Table 8.1.4.2.2.1.3.3-5: ServingCellConfigCommon (Table 8.1.4.2.2.1.3.3-4)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-168 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ServingCellConfigCommon ::= SEQUENCE { |
|||
physCellId |
Physical CellID of the NR Cell 1 |
||
} |
Table 8.1.4.2.2.1.3.3-6: MasterKeyUpdate (Table 8.1.4.2.2.1.3.3-2)
Derivation Path: TS 38.331 [12], clause 6.2.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterKeyUpdate ::= SEQUENCE { |
|||
keySetChangeIndicator |
True |
||
nextHopChainingCount |
NextHopChainingCount |
38.508-1 [4] Table 4.6.3-83 |
|
nas-Container |
Octets 1 to 4 are Message authentication code(MAC) IE using {NH, NCC=2} Bits 1 to 4 of octet 5 are set according to PIXIT parameter for default integrity protection algorithm. Bits 5 to 8 of octet 5 are set according to PIXIT parameter for default ciphering algorithm. Bits 1 to 3 of octet 6 contains the Key set identifier in 5G. Bit 4 of octet 6 contains the type of security context flag(TSC). Bits 5 to 7 of octet 6 contains the 3bit Next hop chaining counter. Bit 8 of octet 6 is Spare. Octets 7 and 8 are spare and shall be coded as zero. |
24.501 [22] 9.11.2.9 The value part of S1 mode to N1 mode NAS transparent container |
|
} |
8.1.4.3 DAPS handover
8.1.4.3.1 DAPS handover with key change / Success / Intra-frequency
8.1.4.3.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for handover with key change and dapsConfig is configured for a DRB } then { UE performs DAPS handover to the target cell and keeps DL/UL reception/transmission with the source gNB for the DRB configured with dapsConfig }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE has performed random access procedure to the target cell successfully } then { UE transmits an RRCReconfigurationComplete message to the target gNB }
}
(3)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE receives an RRCReconfiguration message including a daps-SourceRelease } then { UE releases the radio link with the source cell }
}
(4)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE has performed random access procedure to the target cell successfully }
then { UE continues the downlink user data reception from the source gNB until releasing the source cell }
}
8.1.4.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.1 and 9.2.3.2.1 and TS 38.331 clause 5.3.5.3 and 5.3.5.5.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.1]
Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility.
Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1:
Figure 9.2.3.1-1: Inter-gNB handover procedures
1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.
2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE.
3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the RRCReconfiguration message. The access information to the target cell may include beam specific information, if any.
4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete.
NOTE 1: User Data can also be sent in step 4 if the grant allows.
In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the source cell and continues the uplink user data transmission to the source gNB until successful random access procedure to the target gNB.
Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, NR sidelink configurations and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and are not configured by the target gNB until the DAPS handover has completed (i.e. at source cell release).
The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC, except for DAPS handover, where upon reception of the handover command, the UE:
– Creates a MAC entity for target;
– Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with DAPS;
– For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions for source and target and associates them with the RLC entities configured by source and target respectively;
– Retains the rest of the source configurations until release of the source.
NOTE 2: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.
NOTE 3: Void.
RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode and for SRBs, PDCP can either be re-established together with a security key change or remain as it is without a key change.
Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB.
Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure except in certain CHO or DAPS handover scenarios:
– When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and reports DAPS handover failure via the source without triggering RRC connection re-establishment if the source link has not been released.
– When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts CHO execution once, otherwise re-establishment is performed.
DAPS handover for FR2 to FR2 case is not supported in this release of the specification.
[TS 38.300, clause 9.2.3.2.1]
The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below depicts the basic handover scenario where neither the AMF nor the UPF changes:
Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover
0. The UE context within the source gNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update.
1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement configuration.
2. The source gNB decides to handover the UE, based on MeasurementReport and RRM information.
3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with necessary information to prepare the handover at the target side. The information includes at least the target cell ID, KgNB*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic AS-configuration including antenna Info and DL Carrier Frequency, the current QoS flow to DRB mapping rules applied to the UE, the SIB1 from source gNB, the UE capabilities for different RATs, PDU session related information, and can include the UE reported measurement information including beam-related information if available. The PDU session related information includes the slice information and QoS flow level QoS profile(s). The source gNB may also request a DAPS handover for one or more DRBs.
NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing Reflective QoS flow to DRB mapping.
4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the target gNB shall reject such PDU Sessions.
5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform the handover. The target gNB also indicates if a DAPS handover is accepted.
NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated.
NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data forwarding follows as defined in 9.2.3.2.3.
6. The source gNB triggers the Uu handover by sending an RRCReconfiguration message to the UE, containing the information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources, the association between RACH resources and SSB(s), the association between RACH resources and UE-specific CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc.
NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target gNB in step 8a.
NOTE 4a: CHO cannot be configured simultaneously with DAPS handover.
7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b.
7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a PDCP SN yet.
NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 8b instead of step 7.
NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already.
8. The UE synchronises to the target cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to target gNB. In case of DAPS handover, the UE does not detach from the source cell upon receiving the RRCReconfiguration message. The UE releases the source resources and configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node.
NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released.
8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the normal data forwarding follows as defined in 9.2.3.2.3.
NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS.
NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided.
NOTE 9: Void.
9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path towards the target gNB and to establish an NG-C interface instance towards the target gNB.
10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the source gNB.
11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.
12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.
…
Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane signalling transmission.
[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 RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection while timer T311 is running, as defined in 5.3.7.3:
2> remove all the entries within VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceRelease:
2> reset the source MAC and release the source MAC configuration;
2> for each DAPS bearer:
3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2> for each SRB:
3> release the PDCP entity for the source SpCell;
3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
…
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> stop timer T310 for source SpCell if running;
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;
2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5];
…
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message may not be similar to the original one.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> if no DAPS bearer is configured:
2> stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
1> stop timer T312 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell.
1> If any DAPS bearer is configured:
2> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group;
2> for each DAPS bearer:
3> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group;
3> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2.
2> for each SRB:
3> establish an RLC entity for the target cell group, with the same configurations as for the source cell group;
3> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
3> suspend SRBs for the source cell group;
NOTE 3: Void
2> apply the value of the newUE-Identity as the C-RNTI in the target cell group;
2> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon;
2> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
8.1.4.3.1.3 Test description
8.1.4.3.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the Serving cell and the power level is configured to ”Serving Cell” defined in TS 38.508-1 [4] Table 6.2.2.1-3.
– NR Cell 2 is the Suitable neighbour intra-frequency cell and the power level is configured to ” Suitable neighbour intra-frequency cell” defined in TS 38.508-1 [4] Table 6.2.2.1-3
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for both NR Cells
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.3.1.3.2 Test procedure sequence
Table 8.1.4.3.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message containing reconfigurationWithSync to order UE to perform DAPS handover to NR Cell 2. DRB#n of the first PDU session is configured as DAPS bearer. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel with step 2-3, parallel behaviour defined in table 8.1.4.3.1.3.2-2 is executed repeatedly. |
– |
– |
– |
– |
2 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB#n of the first PDU session on NR Cell 1? |
<– |
– |
1 |
P |
3 |
Void |
– |
– |
– |
– |
4 |
The SS transmits Random Access Response to respond to the latest preamble on NR Cell 2. |
<– |
Random Access Response |
– |
– |
5 |
Check: Does UE transmit an RRCReconfigurationComplete message in NR Cell 2? |
–> |
NR RRC: RRCReconfigurationComplete |
1,2 |
P |
5A |
The SS transmits one IP Packet to verify data path on DRB#n of the first PDU session on NR Cell 1 |
– |
– |
– |
– |
5B |
Check: Does the UE transmit HARQ feedback after step 5A? |
– |
– |
4 |
P |
6 |
The SS transmits an RRCReconfiguration message with condition DAPS_HO_ReleaseSource in NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
7 |
Check: Does the UE transmit an RRCReconfigurationComplete message in NR Cell 2? |
–> |
NR RRC: RRCReconfigurationComplete |
3 |
P |
8 |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB#n of the first PDU session on NR Cell 2? |
– |
– |
2 |
P |
9 |
The SS transmits one IP Packet to verify data path on DRB#n of the first PDU session on NR Cell 1. |
– |
– |
– |
– |
10 |
Check: Does UE send the IP Packet on DRB#n of the first PDU session in the uplink on NR Cell 1 within the next 1s? |
– |
– |
3 |
F |
Table 8.1.4.3.1.3.2-2: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE transmits preamble to NR Cell 2. |
-> |
(PRACH Preamble) |
– |
– |
8.1.4.3.1.3.3 Specific message contents
Table 8.1.4.3.1.3.3-1: RRCReconfiguration (step 1, Table 8.1.4.3.1.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
radioBearerConfig |
RadioBearerConfig with conditions SRB_NR_PDCP and (DRBn AND DAPS_PDCP) |
||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig) |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.3.1.3.3-2: CellGroupConfig (Table 8.1.4.3.1.3.3-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
3 entries |
||
RLC-BearerConfig[1] |
RLC-BearerConfig with conditions SRB1 |
entry 1 |
|
RLC-BearerConfig[2] |
RLC-BearerConfig with conditions SRB2 |
entry 2 |
|
RLC-BearerConfig[3] |
RLC-BearerConfig with conditions AM, DRBn |
entry 3 |
|
} |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 2 |
||
} |
|||
rach-ConfigDedicated CHOICE { |
|||
uplink |
RACH-ConfigDedicated |
Table 8.1.4.3.1.3.3-3 |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.3.1.3.3-3: RACH-ConfigDedicated (Table 8.1.4.3.1.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-129 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigDedicated ::= SEQUENCE { |
|||
cfra SEQUENCE { |
|||
occasions SEQUENCE { |
|||
rach-ConfigGeneric |
RACH-ConfigGeneric |
Table 8.1.4.3.1.3.3-4 |
|
} |
|||
} |
|||
} |
Table 8.1.4.3.1.3.3-4: RACH-ConfigGeneric (Table 8.1.4.3.1.3.3-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-130 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigGeneric ::= SEQUENCE { |
|||
preambleTransMax |
n200 |
||
} |
Table 8.1.4.3.1.3.3-5: RRCReconfiguration (step 6, Table 8.1.4.3.1.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-13 with Condition DAPS_HO_ReleaseSource |
8.1.4.3.2 DAPS handover / HO Failure and source link available / HO Success and RLF in source / Intra-frequency
8.1.4.3.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { T304 of the MCG expires and the source link has not been released }
then { UE falls back to source cell configuration, resumes the connection with source cell, and reports DAPS HO failure via the source without triggering RRC connection re-establishment }
}
(2)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { Radio link failure is detected for the source MCG }
then { UE suspends all DRBs in the source, releases the source connection and continues the handover procedure to target }
}
8.1.4.3.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.1 and 9.2.3.2.1 and TS 38.331 clause 5.3.5.3, 5.3.5.5.2, 5.3.5.5.6, 5.3.5.5.7, 5.3.5.8.3, 5.3.10.3 and 5.7.5.3. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.1]
Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility.
Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1:
Figure 9.2.3.1-1: Inter-gNB handover procedures
1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.
2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE.
3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the RRCReconfiguration message. The access information to the target cell may include beam specific information, if any.
4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete.
NOTE 1: User Data can also be sent in step 4 if the grant allows.
In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the source cell and continues the uplink user data transmission to the source gNB until successful random access procedure to the target gNB.
Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, NR sidelink configurations and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and are not configured by the target gNB until the DAPS handover has completed (i.e. at source cell release).
The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC, except for DAPS handover, where upon reception of the handover command, the UE:
– Creates a MAC entity for target;
– Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with DAPS;
– For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions for source and target and associates them with the RLC entities configured by source and target respectively;
– Retains the rest of the source configurations until release of the source.
NOTE 2: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.
NOTE 3: Void.
RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode and for SRBs, PDCP can either be re-established together with a security key change or remain as it is without a key change.
Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB.
Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure except in certain CHO or DAPS handover scenarios:
– When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and reports DAPS handover failure via the source without triggering RRC connection re-establishment if the source link has not been released.
– When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts CHO execution once, otherwise re-establishment is performed.
DAPS handover for FR2 to FR2 case is not supported in this release of the specification.
[TS 38.300, clause 9.2.3.2.1]
The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below depicts the basic handover scenario where neither the AMF nor the UPF changes:
Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover
0. The UE context within the source gNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update.
1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement configuration.
2. The source gNB decides to handover the UE, based on MeasurementReport and RRM information.
3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with necessary information to prepare the handover at the target side. The information includes at least the target cell ID, KgNB*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic AS-configuration including antenna Info and DL Carrier Frequency, the current QoS flow to DRB mapping rules applied to the UE, the SIB1 from source gNB, the UE capabilities for different RATs, PDU session related information, and can include the UE reported measurement information including beam-related information if available. The PDU session related information includes the slice information and QoS flow level QoS profile(s). The source gNB may also request a DAPS handover for one or more DRBs.
NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing Reflective QoS flow to DRB mapping.
4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the target gNB shall reject such PDU Sessions.
5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform the handover. The target gNB also indicates if a DAPS handover is accepted.
NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated.
NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data forwarding follows as defined in 9.2.3.2.3.
6. The source gNB triggers the Uu handover by sending an RRCReconfiguration message to the UE, containing the information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources, the association between RACH resources and SSB(s), the association between RACH resources and UE-specific CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc.
NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target gNB in step 8a.
NOTE 4a: CHO cannot be configured simultaneously with DAPS handover.
7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b.
7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a PDCP SN yet.
NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 8b instead of step 7.
NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already.
8. The UE synchronises to the target cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to target gNB. In case of DAPS handover, the UE does not detach from the source cell upon receiving the RRCReconfiguration message. The UE releases the source resources and configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node.
NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released.
8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the normal data forwarding follows as defined in 9.2.3.2.3.
NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS.
NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided.
NOTE 9: Void.
9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path towards the target gNB and to establish an NG-C interface instance towards the target gNB.
10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the source gNB.
11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.
12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.
…
Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane signalling transmission.
[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 RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection while timer T311 is running, as defined in 5.3.7.3:
2> remove all the entries within VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceRelease:
2> reset the source MAC and release the source MAC configuration;
2> for each DAPS bearer:
3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2> for each SRB:
3> release the PDCP entity for the source SpCell;
3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
…
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> stop timer T310 for source SpCell if running;
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;
2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5];
…
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message may not be similar to the original one.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> if no DAPS bearer is configured:
2> stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
1> stop timer T312 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell.
1> If any DAPS bearer is configured:
2> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group;
2> for each DAPS bearer:
3> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group;
3> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2.
2> for each SRB:
3> establish an RLC entity for the target cell group, with the same configurations as for the source cell group;
3> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
3> suspend SRBs for the source cell group;
NOTE 3: Void
2> apply the value of the newUE-Identity as the C-RNTI in the target cell group;
2> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon;
2> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
[TS 38.331, clause 5.3.5.5.6]
The UE shall:
1> if the received rlf-TimersAndConstants is set to release:
2> if any DAPS bearer is configured:
3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1;
2> else:
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
1> else:
2> if any DAPS bearer is configured:
3> configure the value of timers and constants for the target cell group in accordance with received rlf-TimersAndConstants;
2> else:
3> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;
3> stop timer T310 for this cell group, if running;
3> stop timer T312 for this cell group, if running;
3> reset the counters N310 and N311.
[TS 38.331, clause 5.3.5.5.7]
The UE shall:
1> if the SpCellConfig contains the rlf-TimersAndConstants:
2> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
1> else if rlf-TimersAndConstants is not configured for this cell group:
2> if any DAPS bearer is configured:
3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1;
2> else
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
…
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
1> if T304 of the MCG expires:
2> release dedicated preambles provided in rach-ConfigDedicated if configured;
2> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated if configured;
2> if any DAPS bearer is configured, and radio link failure is not detected in the source PCell, according to subclause 5.3.10.3:
3> reset MAC for the target PCell and release the MAC configuration for the target PCell;
3> for each DAPS bearer:
4> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell;
4> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
3> for each SRB:
4> if the masterKeyUpdate was not received:
5> configure the PDCP entity for the source PCell with state variables continuation as specified in TS 38.323 [5], the state variables as the PDCP entity for the target PCell;
4> release the PDCP entity for the target PCell;
4> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell;
4> trigger the PDCP entity for the source PCell to perform SDU discard as specified in TS 38.323 [5];
4> re-establish the RLC entity for the source PCell;
3> release the physical channel configuration for the target PCell;
3> revert back to the SDAP configuration used in the source PCell;
3> discard the keys used in target PCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
3> resume suspended SRBs in the source PCell;
3> for each non DAPS bearer:
4> revert back to the UE configuration used for the DRB in the source PCell, includes PDCP, RLC states variables, the security configuration and the data stored in transmission and reception buffers in PDCP and RLC entities ;
3> revert back to the UE measurement configuration used in the source PCell;
3> initiate the failure information procedure as specified in subclause 5.7.5 to report DAPS handover failure.
…
NOTE 2: In this clause, the term ‘handover failure’ has been used to refer to ‘reconfiguration with sync failure’.
[TS 38.331, clause 5.3.10.3]
The UE shall:
1> if any DAPS bearer is configured and T304 is running:
2> upon T310 expiry in source SpCell; or
2> upon random access problem indication from source MCG MAC; or
2> upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or
2> upon consistent uplink LBT failure indication from source MCG MAC:
3> consider radio link failure to be detected for the source MCG i.e. source RLF;
3> suspend the transmission and reception of all DRBs in the source MCG;
3> reset MAC for the source MCG;
3> release the source connection.
[TS 38.331, clause 5.7.5.3]
The UE shall:
…
1> if initiated to provide DAPS failure information, set FailureInfoDAPS as follows:
2> set the failureType as daps-failure;
1> if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information:
2> submit the FailureInformation message to lower layers for transmission via SRB1;
8.1.4.3.2.3 Test description
8.1.4.3.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1 is the Serving cell and NR Cell 2 is the Suitable neighbour intra-frequency cell.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR Cells
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.3.2.3.2 Test procedure sequence
Table 8.1.4.3.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the NR cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1", "T2" and "T3" are applied at the points indicated in the Main behaviour description in Table 8.1.4.3.2.3.2-2.
Table 8.1.4.3.2.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-94 |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
off |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
off |
-88 |
Table 8.1.4.3.2.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message containing reconfigurationWithSync to order UE to perform DAPS handover to NR Cell 2. DRB#n of the first PDU session is configured as DAPS bearer. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel with step 2, parallel behaviour defined in table 8.1.4.3.2.3.2-3 is executed repeatedly. |
– |
– |
– |
– |
2 |
The SS changes the power level setting according to the row "T1". |
– |
– |
– |
– |
3 |
Check: Does the UE transmit an RRCReestablishmentRequest message on NR Cell 1 within 5s? |
–> |
NR RRC: RRCReestablishmentRequest |
1 |
F |
4 |
Check: Does the UE transmit a FailureInformation message with failureType-r16 set to daps-failure on NR Cell 1 within 5s? |
–> |
NR RRC: FailureInformation |
1 |
P |
5 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE revert back to the configuration used in the source PCell on DRB#n of the first PDU session on NR Cell 1? |
– |
– |
1 |
P |
6 |
The SS changes the power level setting according to the row "T2". |
– |
– |
– |
– |
7 |
The SS transmits an RRCReconfiguration message containing reconfigurationWithSync to order UE to perform DAPS handover to NR Cell 2. DRB#n of the first PDU session is configured as DAPS bearer. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel with step 8, parallel behaviour defined in table 8.1.4.3.2.3.2-3 is executed repeatedly. |
– |
– |
– |
– |
8 |
The SS changes the power level setting according to the row "T3" and waits 300ms to ensure T310 expires in NR Cell 1. |
– |
– |
– |
– |
9 |
The SS transmits Random Access Response to respond to the latest preamble on NR Cell 2. |
<– |
Random Access Response |
– |
– |
10 |
Check: Does UE transmit an RRCReconfigurationComplete message in NR Cell 2? |
–> |
NR RRC: RRCReconfigurationComplete |
2 |
P |
11 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB#n of the first PDU session on NR Cell 2? |
– |
– |
2 |
P |
12 |
The SS transmits an RRCReconfiguration message with condition DAPS_HO_ReleaseSource in NR Cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
13 |
Check: Does the UE transmits an RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
Table 8.1.4.3.2.3.2-3: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE transmits preamble to NR Cell 2. |
-> |
(PRACH Preamble) |
– |
– |
2 |
The SS does not respond. |
– |
– |
– |
– |
8.1.4.3.2.3.3 Specific message contents
Table 8.1.5.6.1.3.3-1: SIB1 for NR Cell 1 (all steps)
Derivation Path: TS 38.508-1 [4] table 4.6.1-28 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
ue-TimersAndConstants SEQUENCE { |
|||
t310 |
ms0 |
0 ms |
|
} |
|||
} |
Table 8.1.4.3.2.3.3-2: RRCReconfiguration (step 1 and step 7, Table 8.1.4.3.2.3.2-2)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
radioBearerConfig |
RadioBearerConfig with conditions (SRB_NR_PDCP) and (DRBn AND DAPS_PDCP) |
||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig |
OCTET STRING (CONTAINING CellGroupConfig)Table 8.1.4.3.2.3.3-3 |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.3.2.3.3-3: CellGroupConfig (Table 8.1.4.3.2.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLCH)) OF RLC-BearerConfig { |
3 entries |
||
RLC-BearerConfig[1] |
RLC-BearerConfig with conditions SRB1 |
entry 1 |
|
RLC-BearerConfig[2] |
RLC-BearerConfig with conditions SRB2 |
entry 2 |
|
RLC-BearerConfig[3] |
RLC-BearerConfig with conditions AM, DRBn |
entry 3 |
|
} |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 2 |
||
} |
|||
rach-ConfigDedicated CHOICE { |
|||
uplink |
RACH-ConfigDedicated |
Table 8.1.4.3.2.3.3-4 |
|
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.3.2.3.3-4: RACH-ConfigDedicated (Table 8.1.4.3.2.3.3-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-129 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigDedicated ::= SEQUENCE { |
|||
cfra SEQUENCE { |
|||
occasions SEQUENCE { |
|||
rach-ConfigGeneric |
RACH-ConfigGeneric |
Table 8.1.4.3.2.3.3-5 |
|
} |
|||
} |
|||
} |
Table 8.1.4.3.2.3.3-5: RACH-ConfigGeneric (Table 8.1.4.3.2.3.3-4)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-130 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RACH-ConfigGeneric ::= SEQUENCE { |
|||
preambleTransMax |
n200 |
||
} |
Table 8.1.4.3.2.3.3-6: FailureInformation (step 4, Table 8.1.4.3.2.3.2-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-4 with Condition DAPS_HOF |
Table 8.1.4.3.2.3.3-7: RRCReconfiguration (step 12, Table 8.1.4.3.2.3.2-2)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-13 with Condition DAPS_HO_ReleaseSource |
8.1.4.3.3
8.1.4.3.4 DAPS handover with key change / Success / Inter-frequency
8.1.4.3.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for handover with key change and dapsConfig is configured for a DRB } then { UE performs DAPS handover to the target cell and keeps DL/UL reception/transmission with the source gNB for the DRB configured with dapsConfig }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE has performed random access procedure to the target cell successfully } then { UE transmits an RRCReconfigurationComplete message to the target gNB }
}
(3)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE receives an RRCReconfiguration message including a daps-SourceRelease } then { UE releases the radio link with the source cell }
}
(4)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for any DRB }
ensure that {
when { UE has performed random access procedure to the target cell successfully } then { UE continues the downlink user data reception from the source gNB until releasing the source cell }
}
8.1.4.3.4.2 Conformance requirements
Same as test case 8.1.4.3.1.
8.1.4.3.4.3 Test description
8.1.4.3.4.3.1 Pre-test conditions
Same as test case 8.1.4.3.1 with the following differences:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
– System information combination: NR-4 replaces NR-2.
8.1.4.3.4.3.2 Test procedure sequence
Same as test case 8.1.4.3.1 with the following differences:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
8.1.4.3.4.3.3 Specific message contents
Same as test case 8.1.4.3.1 with the following difference:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
8.1.4.3.5 DAPS handover / HO Failure and source link available / HO Success and RLF in source / Inter-frequency
8.1.4.3.5.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { T304 of the MCG expires and the source link has not been released }
then { UE falls back to source cell configuration, resumes the connection with source cell, and reports DAPS HO failure via the source without triggering RRC connection re-establishment }
}
(2)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { Radio link failure is detected for the source MCG }
then { UE suspends all DRBs in the source, releases the source connection and continues the handover procedure to target }
}
8.1.4.3.5.2 Conformance requirements
Same as test case 8.1.4.3.2.
8.1.4.3.5.3 Test description
8.1.4.3.5.3.1 Pre-test conditions
Same as test case 8.1.4.3.2 with the following differences:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
– System information combination: NR-4 replaces NR-2.
8.1.4.3.5.3.2 Test procedure sequence
Same as test case 8.1.4.3.2 with the following differences:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
8.1.4.3.5.3.3 Specific message contents
Same as test case 8.1.4.3.2 with the following differences:
– Cells configuration: NR Cell 3 replaces NR Cell 2.
8.1.4.4 Conditional handover
8.1.4.4.1 Conditional handover / Success / A3 / A5 / A3+A5
8.1.4.4.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving an RRCReconfiguration message including ConditionalReconfiguration }
ensure that {
when { any CHO execution condition is not satisfied } then { UE maintains connection with source gNB and starts evaluating the CHO execution conditions for the candidate cell(s) }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting conditional handover }
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and only event A3 is configured as conditional handover trigger event } then { UE starts evaluating the CHO execution condition A3 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }
}
(3)
with { UE in NR RRC_CONNECTED state and supporting conditional handover }
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and only event A5 is configured as conditional handover trigger event } then { UE starts evaluating the CHO execution condition A5 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }
}
(4)
with { UE in NR RRC_CONNECTED state and supporting conditional handover }
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and both event A3 and event A5 are configured as conditional handover trigger events } then { UE starts evaluating the CHO execution condition A3 and A5 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }
}
(5)
with { UE in NR RRC_CONNECTED state and supporting conditional handover }
ensure that {
when { UE perform conditional handover procedure successfully } then { UE releases stored CHO configurations }
}
8.1.4.4.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.4.1, and 9.2.3.4.2 and TS 38.331 clause 5.3.5.1, 5.3.5.13.1, 5.3.5.13.4 and 5.3.5.13.5. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.4.1]
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed (legacy handover or conditional handover execution).
The following principles apply to CHO:
– The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.
– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.
– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration.
– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.
CHO is not supported for NG-C based handover in this release of the specification.
[TS 38.300, clause 9.2.3.4.2]
As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes:
Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover
0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
2. The source gNB decides to use CHO.
3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A CHO request message is sent for each candidate cell.
4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell.
6. The source gNB sends an RRCReconfiguration message to the UE, containing the configuration of CHO candidate cell(s) and CHO execution condition(s).
NOTE 1: CHO configuration of candidate cells can be followed by other reconfiguration from the source gNB.
NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration.
7. The UE sends an RRCReconfigurationComplete message to the source gNB.
7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message.
8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to the target gNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure.
8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1.
NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS message.
8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other candidate target gNBs, if any, to cancel CHO for the UE.
[TS 38.331, clause 5.3.5.1]
Figure 5.3.5.1-1: RRC reconfiguration, successful
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
[TS 38.331, clause 5.3.5.13.1]
The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition. The network provides the configuration parameters for the target SpCell in the ConditionalReconfiguration IE.
The UE performs the following actions based on a received ConditionalReconfiguration IE:
1> if the ConditionalReconfiguration contains the condReconfigToRemoveList:
2> perform conditional reconfiguration removal procedure as specified in 5.3.5.13.2;
1> if the ConditionalReconfiguration contains the condReconfigToAddModList:
2> perform conditional reconfiguration addition/modification as specified in 5.3.5.13.3;
[TS 38.331, clause 5.3.5.13.4]
The UE shall:
1> for each condReconfigId within the VarConditionalReconfig:
2> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync in the received condRRCReconfig to be applicable cell;
2> for each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond associated to condReconfigId:
3> if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be fulfilled;
3> if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be not fulfilled;
2> if event(s) associated to all measId(s) within condTriggerConfig for a target candidate cell within the stored condRRCReconfig are fulfilled:
3> consider the target candidate cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell;
3> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5;
NOTE: Up to 2 MeasId can be configured for each condReconfigId. The conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
[TS 38.331, clause 5.3.5.13.5]
The UE shall:
1> if more than one triggered cell exists:
2> select one of the triggered cells as the selected cell for conditional reconfiguration execution;
1> for the selected cell of conditional reconfiguration execution:
2> apply the stored condRRCReconfig of the selected cell and perform the actions as specified in 5.3.5.3;
NOTE: If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for execution.
8.1.4.4.1.3 Test description
8.1.4.4.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2 and NR Cell 4.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR cells
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.4.1.3.2 Test procedure sequence
Tables 8.1.4.4.1.3.2-1 and 8.1.4.4.1.3.2-2 illustrate the downlink power levels to be applied for NR Cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table 8.1.4.4.1.3.2-3.
Table 8.1.4.4.1.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-82 |
-91 |
-91 |
Power levels are such that UE registered on NR Cell 1 and entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-79 |
-91 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-91 |
-79 |
Power levels are such that entry condition for event A5 is satisfied for NR Cell 4 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-79 |
-91 |
-91 |
Power levels are such that entry condition for event A3 and event A5 are satisfied for NR Cell 1 |
Table 8.1.4.4.1.3.2-2: Power levels in FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that UE registered on NR Cell 1 and entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A5 is satisfied for NR Cell 4 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 and event A5 are satisfied for NR Cell 1 |
Table 8.1.4.4.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 2 and NR Cell 4 as target candidate cells and configure event A3 as trigger event in NR cell 1. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message in NR cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
Check: Does the UE initiate a random access procedure transmitting Preamble in NR Cell 2 or in NR cell 4 within 10s? |
–> |
(PRACH Preamble) |
1 |
F |
4 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
5 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 2 within 10s? |
–> |
(PRACH Preamble) |
2 |
P |
6 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
7 |
The UE transmits RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
8 |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 2? |
– |
– |
2 |
P |
9 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 1 and NR Cell 4 as target candidate cells and configure event A5 as trigger event in NR cell 2. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
10 |
The UE transmits an RRCReconfigurationComplete message in NR cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
11 |
SS adjusts the cell-specific reference signal level according to row "T2". |
– |
– |
– |
– |
12 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 4 within 10s? |
–> |
(PRACH Preamble) |
3 |
P |
13 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
14 |
The UE transmits RRCReconfigurationComplete message in NR Cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
15 |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 4? |
– |
– |
3 |
P |
16 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration for intra -frequency event A3 and A5 in NR cell 4. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
17 |
The UE transmits an RRCReconfigurationComplete message in NR cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
18 |
SS adjusts the cell-specific reference signal level according to row "T3". |
– |
– |
– |
– |
19 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 1 within 10s? |
–> |
(PRACH Preamble) |
4 |
P |
20 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
21 |
The UE transmits RRCReconfigurationComplete message in NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
22 |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 1? |
– |
– |
4 |
P |
23 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
24 |
Check: Does the UE transmit RRCReconfigurationComplete message in NR Cell 2 within 10s? |
–> |
NR RRC: RRCReconfigurationComplete |
5 |
F |
8.1.4.4.1.3.3 Specific message contents
Table 8.1.4.4.1.3.3-1: RRCReconfiguration (Step 1, step 9 and step 16, Table 8.1.4.4.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS and CHO |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
measConfig |
MeasConfig |
Table 8.1.4.4.1.3.3-2 |
||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
conditionalReconfiguration-r16 |
ConditionalReconfiguration |
Table 8.1.4.4.1.3.3-6 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.4.1.3.3-2: MeasConfig (Table 8.1.4.4.1.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
1 entry |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR |
Table 8.1.4.4.1.3.3-3 |
|
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
2 entries |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-condEventA3 |
Table 8.1.4.4.1.3.3-4 |
|
} |
|||
} |
|||
ReportConfigToAddMod[2] SEQUENCE { |
entry 2 |
||
reportConfigId |
2 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-condEventA5 |
Table 8.1.4.4.1.3.3-5 |
|
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
Step 1, Step 9 |
|
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
Step 1 |
|
2 |
Step 9 |
||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
2 entries |
Step 16 |
|
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
MeasIdToAddMod[2] SEQUENCE { |
entry 2 |
||
measId |
2 |
||
measObjectId |
1 |
||
reportConfigId |
2 |
||
} |
|||
} |
|||
} |
Table 8.1.4.4.1.3.3-3: MeasObjectNR (Table 8.1.4.4.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
ARFCN-ValueNR for SSB of NR Cell 1 |
The SSB of NR cell 1, NR Cell 2 and NR cell 4 have the same ARFCN value as specified in TS 38.508-1 [4] clause 6.2.3 |
|
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.4.1.3.3-4: ReportConfigNR-condEventA3 (Table 8.1.4.4.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
condTriggerConfig SEQUENCE { |
|||
condEventId CHOICE { |
|||
condEventA3 SEQUENCE { |
|||
a3-Offset CHOICE { |
|||
rsrp |
2 |
1 dB (2*0.5 dB) |
FR1 |
FFS |
FR2 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.1.3.3-5: ReportConfigNR-condEventA5 (Table 8.1.4.4.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
condTriggerConfig SEQUENCE { |
|||
condEventId CHOICE { |
|||
condEventA5 SEQUENCE { |
|||
a5-Threshold1 CHOICE { |
|||
rsrp |
76 |
-80dBm |
FR1 |
FFS |
FR2 |
||
} |
|||
a5-Threshold2 CHOICE { |
|||
rsrp |
70 |
-86dBm |
FR1 |
FFS |
FR2 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.1.3.3-6: ConditionalReconfiguration (Table 8.1.4.4.1.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25D |
|||
Information Element |
Value/remark |
Comment |
Condition |
ConditionalReconfiguration-r16::= SEQUENCE { |
|||
condReconfigToRemoveList-r16 |
Not present |
||
condReconfigToAddModList-r16 |
CondReconfigToAddModList-r16 (Step 1 and step 9) |
Table 8.1.4.4.1.3.3-7 |
Step 1, Step 9 |
CondReconfigToAddModList-r16 (Step 16) |
Table 8.1.4.4.1.3.3-10 |
Step 16 |
|
} |
Table 8.1.4.4.1.3.3-7: CondReconfigToAddModList-r16 (Step 1 and step 9, Table 8.1.4.4.1.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
2 entries |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR cell 2 |
Table 8.1.4.4.1.3.3-8 |
Step 1 |
RRCReconfiguration-HO with condition HO_NR cell 1 |
Table 8.1.4.4.1.3.3-8 |
Step 9 |
|
} |
|||
CondReconfigToAddMod-r16[2] ::= SEQUENCE { |
entry 2 |
||
condReconfigId-r16 |
2 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR cell 4 |
Table 8.1.4.4.1.3.3-8 |
|
} |
|||
} |
Table 8.1.4.4.1.3.3-8: RRCReconfiguration-HO (Table 8.1.4.4.1.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig with condition PCI_NR cell 1 |
Table 8.1.4.4.1.3.3-9 |
HO_NR cell 1 |
CellGroupConfig with condition PCI_NR cell 2 |
Table 8.1.4.4.1.3.3-9 |
HO_NR cell 2 |
|
CellGroupConfig with condition PCI_NR cell 4 |
Table 8.1.4.4.1.3.3-9 |
HO_NR cell 4 |
|
} |
|||
} |
|||
} |
|||
} |
8.1.4.4.1.3.3-9: CellGroupConfig (Table 8.1.4.4.1.3.3-8)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 1 |
PCI_NR cell 1 |
|
Physical Cell Identity of NR Cell 2 |
PCI_NR Cell 2 |
||
Physical Cell Identity of NR Cell 4 |
PCI_NR Cell 4 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.1.3.3-10: CondReconfigToAddModList-r16 (Step 16, Table 8.1.4.4.1.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
2 entries |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
MeasId [2] |
2 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR cell 1 |
Table 8.1.4.4.1.3.3-8 |
|
} |
|||
CondReconfigToAddMod-r16[2] ::= SEQUENCE { |
entry 2 |
||
condReconfigId-r16 |
2 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR cell 2 |
Table 8.1.4.4.1.3.3-8 |
|
} |
|||
} |
8.1.4.4.2 Conditional handover / modify conditional handover configuration
8.1.4.4.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving an RRCReconfiguration message including a ConditionalReconfiguration }
ensure that {
when { UE received another RRCReconfiguration message with adding a new entry in the CondReconfigToAddModList before any CHO execution condition is satisfied } then { UE add the new entry within the VarConditionalReconfig and apply the latest conditional handover configurations}
}
(2)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving an RRCReconfiguration message including a ConditionalReconfiguration }
ensure that {
when { UE received another RRCReconfiguration message with modifying an existing entry in the CondReconfigToAddModList before any CHO execution condition is satisfied } then { UE replace the existing entry with the value received and apply the latest conditional handover configurations }
}
(3)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving an RRCReconfiguration message including a ConditionalReconfiguration }
ensure that {
when { UE received another RRCReconfiguration message with condConfigToRemoveList before any CHO execution condition is satisfied } then { UE removes the entry with the matching condConfigId included in the condConfigToRemoveList and apply the latest conditional handover configurations }
}
8.1.4.4.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.4.1, and 9.2.3.4.2 and TS 38.331 clause 5.3.5.1, 5.3.5.13.2 and 5.3.5.13.3. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.4.1]
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed (legacy handover or conditional handover execution).
The following principles apply to CHO:
– The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.
– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.
– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration.
– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.
CHO is not supported for NG-C based handover in this release of the specification.
[TS 38.300, clause 9.2.3.4.2]
As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes:
Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover
0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
2. The source gNB decides to use CHO.
3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A CHO request message is sent for each candidate cell.
4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell.
6. The source gNB sends an RRCReconfiguration message to the UE, containing the configuration of CHO candidate cell(s) and CHO execution condition(s).
NOTE 1: CHO configuration of candidate cells can be followed by other reconfiguration from the source gNB.
NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration.
7. The UE sends an RRCReconfigurationComplete message to the source gNB.
7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message.
8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to the target gNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure.
8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1.
NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS message.
8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other candidate target gNBs, if any, to cancel CHO for the UE.
[TS 38.331, clause 5.3.5.1]
Figure 5.3.5.1-1: RRC reconfiguration, successful
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
[TS 38.331, clause 5.3.5.13.2]
The UE shall:
1> for each condReconfigId value included in the condReconfigToRemoveList that is part of the current UE conditional reconfiguration in VarConditionalReconfig:
2> remove the entry with the matching condReconfigId from the VarConditionalReconfig;
NOTE: The UE does not consider the message as erroneous if the condReconfigToRemoveList includes any condReconfigId value that is not part of the current UE configuration.
[TS 38.331, clause 5.3.5.13.3]
For each condReconfigId received in the condReconfigToAddModList IE the UE shall:
1> if an entry with the matching condReconfigId exists in the condReconfigToAddModList within the VarConditionalReconfig:
2> if the entry in condReconfigToAddModList includes an condExecutionCond;
3> replace the entry with the value received for this condReconfigId;
2> if the entry in condReconfigToAddModList includes an condRRCReconfig;
2> replace the entry with the value received for this condReconfigId;
1> else:
2> add a new entry for this condReconfigId within the VarConditionalReconfig;
1> perform conditional reconfiguration evaluation as specified in 5.3.5.13.4;
8.1.4.4.2.3 Test description
8.1.4.4.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2 and NR Cell 4.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR cells
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.4.2.3.2 Test procedure sequence
Tables 8.1.4.4.2.3.2-1 and 8.1.4.4.2.3.2-2 illustrate the downlink power levels to be applied for NR cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table 8.1.4.4.2.3.2-3.
Table 8.1.4.4.2.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-82 |
-91 |
-91 |
Power levels are such that UE registered on NR Cell 1 and entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-79 |
-91 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-91 |
-79 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 4 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-91 |
-91 |
Power levels are such that entry condition for NR Cell 4 is not statified |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-91 |
-79 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 and NR Cell 4 |
Table 8.1.4.4.2.3.2-2: Power levels in FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that UE registered on NR Cell 1 and entry condition for event A3 is not satisfied |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 4 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for NR Cell 4 is not statified |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 and NR Cell 4 |
Table 8.1.4.4.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 4 as a target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
The SS transmits an RRCReconfiguration message including ConditionalReconfiguration to add NR Cell 2 as another target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
4 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
5 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
6 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 2 within 10s? |
–> |
(PRACH Preamble) |
1 |
P |
7 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
8 |
The UE transmits RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
9 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 2? |
– |
– |
1 |
P |
10 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 1 and NR Cell 4 as target candidate cells. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
11 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
12 |
The SS transmits an RRCReconfiguration message including ConditionalReconfiguration with condConfigToRemoveList to remove NR Cell 4 from the target candidate cell list. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
13 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
14 |
SS adjusts the cell-specific reference signal level according to row "T2". |
– |
– |
– |
– |
15 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 4 within 10s? |
–> |
(PRACH Preamble) |
3 |
F |
15A |
SS adjusts the cell-specific reference signal level according to row "T3". |
||||
16 |
The SS transmits an RRCReconfiguration message including ConditionalReconfiguration to replace NR Cell 1 with NR Cell 4 as the target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
16A |
The UE transmits RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
17 |
SS adjusts the cell-specific reference signal level according to row "T4". |
– |
– |
– |
– |
18 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 4 within 10s? |
–> |
(PRACH Preamble) |
3 |
P |
19 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
20 |
The UE transmits RRCReconfigurationComplete message in NR Cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
21 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 4? |
– |
– |
2 |
P |
8.1.4.4.2.3.3 Specific message contents
Table 8.1.4.4.2.3.3-1: RRCReconfiguration (Step 1, step 3, step 10, step 12 and step 16, Table 8.1.4.4.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS and CHO |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
measConfig |
Not present |
Step 3, Step 12, Step 16 |
||
MeasConfig |
Table 8.1.4.4.2.3.3-2 |
Step 1, Step 10 |
||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
conditionalReconfiguration-r16 |
ConditionalReconfiguration |
Table 8.1.4.4.2.3.3-5 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.4.2.3.3-2: MeasConfig (Table 8.1.4.4.2.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
1 entry |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR |
Table 8.1.4.4.2.3.3-3 |
|
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-condEventA3 |
Table 8.1.4.4.2.3.3-4 |
|
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
} |
Table 8.1.4.4.2.3.3-3: MeasObjectNR (Table 8.1.4.4.2.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
ARFCN-ValueNR for SSB of NR Cell 1 |
The SSB of NR Cell 1, NR Cell 2 and NR Cell 4 have the same ARFCN value as specified in TS 38.508-1 [4] clause 6.2.3 |
|
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.4.2.3.3-4: ReportConfigNR-condEventA3 (Table 8.1.4.4.2.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
condTriggerConfig SEQUENCE { |
|||
condEventId CHOICE { |
|||
condEventA3 SEQUENCE { |
|||
a3-Offset CHOICE { |
|||
rsrp |
2 |
1 dB (2*0.5 dB) |
FR1 |
FFS |
FR2 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.2.3.3-5: ConditionalReconfiguration (Table 8.1.4.4.2.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25D |
|||
Information Element |
Value/remark |
Comment |
Condition |
ConditionalReconfiguration-r16 ::= SEQUENCE { |
|||
condReconfigToRemoveList-r16 |
Not present |
||
condReconfigToRemoveList-r16 SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 { |
1 entry |
Step 12 |
|
condReconfigId-r16[1] |
2 |
entry 1 |
|
} |
|||
condReconfigToAddModList-r16 |
CondReconfigToAddModList-r16 (Step 1 and step 16) |
Table 8.1.4.4.2.3.3-6 |
Step 1, Step 16 |
CondReconfigToAddModList-r16 (Step 3) |
Table 8.1.4.4.2.3.3-9 |
Step 3 |
|
CondReconfigToAddModList-r16 (Step 10) |
Table 8.1.4.4.2.3.3-10 |
Step 10 |
|
} |
Table 8.1.4.4.2.3.3-6: CondReconfigToAddModList-r16 (Step 1 and step 16, Table 8.1.4.4.2.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
1 entry |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
OCTETSTRING (Containing RRCReconfiguration-HO with condition HO_NR Cell 4) |
Table 8.1.4.4.2.3.3-7 |
Step 1, Step 16 |
} |
|||
} |
Table 8.1.4.4.2.3.3-7: RRCReconfiguration-HO (Table 8.1.4.4.2.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig with condition PCI_NR Cell 1 |
Table 8.1.4.4.2.3.3-8 |
HO_NR Cell 1 |
CellGroupConfig with condition PCI_NR Cell 2 |
Table 8.1.4.4.2.3.3-8 |
HO_NR Cell 2 |
|
CellGroupConfig with condition PCI_NR Cell 4 |
Table 8.1.4.4.2.3.3-8 |
HO_NR Cell 4 |
|
} |
|||
} |
|||
} |
|||
} |
8.1.4.4.2.3.3-8: CellGroupConfig (Table 8.1.4.4.2.3.3-8)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 1 |
PCI_NR Cell 1 |
|
Physical Cell Identity of NR Cell 2 |
PCI_NR Cell 2 |
||
Physical Cell Identity of NR Cell 4 |
PCI_NR Cell 4 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.2.3.3-9: CondReconfigToAddModList-r16 (Step 3, Table 8.1.4.4.2.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
1 entry |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
2 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
OCTETSTRING (Containing RRCReconfiguration-HO with condition HO_NR Cell 2) |
Table 8.1.4.4.2.3.3-7 |
|
} |
|||
} |
Table 8.1.4.4.2.3.3-10: CondReconfigToAddModList-r16 (Step 10, Table 8.1.4.4.2.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
2 entries |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
OCTETSTRING (Containing RRCReconfiguration-HO with condition HO_NR Cell 1) |
Table 8.1.4.4.2.3.3-8 |
|
} |
|||
CondReconfigToAddMod-r16[2] ::= SEQUENCE { |
entry 2 |
||
condReconfigId-r16 |
2 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
OCTETSTRING (Containing RRCReconfiguration-HO with condition HO_NR Cell 4) |
Table 8.1.4.4.2.3.3-8 |
|
} |
|||
} |
8.1.4.4.3 Conditional handover / Failure
8.1.4.4.3.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving a RRCReconfiguration message including ConditionalReconfiguration }
ensure that {
when { UE detects conditional handover failure and finds a selectable cell which is the candidate cell included in ConditionalReconfiguration before T311 expires } then { UE applies the stored condRRCReconfig associated to the selected cell and perform conditional handover to the selected cell }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving a RRCReconfiguration message including ConditionalReconfiguration }
ensure that {
when { UE detects conditional handover failure and cannot find any selectable cell before T311 expires } then { UE goes to RRC_IDLE and release the stored conditional handover configurations }
}
8.1.4.4.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.4.1, and 9.2.3.4.2 and TS 38.331 clause 5.3.7.3, 5.3.7.6 and 5.3.11. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.4.1]
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed (legacy handover or conditional handover execution).
The following principles apply to CHO:
– The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.
– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.
– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration.
– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.
CHO is not supported for NG-C based handover in this release of the specification.
[TS 38.300, clause 9.2.3.4.2]
As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes:
Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover
0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
2. The source gNB decides to use CHO.
3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A CHO request message is sent for each candidate cell.
4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell.
6. The source gNB sends an RRCReconfiguration message to the UE, containing the configuration of CHO candidate cell(s) and CHO execution condition(s).
NOTE 1: CHO configuration of candidate cells can be followed by other reconfiguration from the source gNB.
NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration.
7. The UE sends an RRCReconfigurationComplete message to the source gNB.
7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message.
8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to the target gNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure.
8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1.
NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS message.
8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other candidate target gNBs, if any, to cancel CHO for the UE.
[TS 38.331, clause 5.3.7.3]
Upon selecting a suitable NR cell, the UE shall:
1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2;
1> stop timer T311;
…
1> if attemptCondReconfig is configured; and
1> if the selected cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in VarConditionalReconfig:
2> apply the stored condRRCReconfig associated to the selected cell and perform actions as specified in 5.3.5.3;
1> else:
2> if UE is configured with conditionalReconfiguration:
3> reset MAC;
3> release spCellConfig, if configured;
3> release the MCG SCell(s), if configured;
3> release delayBudgetReportingConfig, if configured and stop timer T342, if running;
3> release overheatingAssistanceConfig , if configured and stop timer T345, if running;
3> if MR-DC is configured:
4> perform MR-DC release, as specified in clause 5.3.5.10;
3> release idc-AssistanceConfig, if configured;
3> release btNameList, if configured;
3> release wlanNameList, if configured;
3> release sensorNameList, if configured;
3> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running;
3> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running;
3> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running;
3> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running;
3> release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e associated with the MCG, if running;
3> release releasePreferenceConfig, if configured and stop timer T346f, if running;
3> release onDemandSIB-Request if configured, and stop timer T350, if running;
3> suspend all RBs, except SRB0;
2> remove all the entries within VarConditionalReconfig, if any;
2> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
3> for the associated reportConfigId:
4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
3> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2> start timer T301;
2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;
2> apply the default MAC Cell Group configuration as specified in 9.2.2;
2> apply the CCCH configuration as specified in 9.1.1.2;
2> apply the timeAlignmentTimerCommon included in SIB1;
2> initiate transmission of the RRCReestablishmentRequest message in accordance with 5.3.7.4;
NOTE: This procedure applies also if the UE returns to the source PCell.
Upon selecting an inter-RAT cell, the UE shall:
1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’.
[TS 38.331, clause 5.3.7.6]
Upon T311 expiry, the UE shall:
1> if the procedure was initiated due to radio link failure or handover failure:
2> set the noSuitableCellFound in the VarRLF-Report to true;
1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’.
[TS 38.331, clause 5.3.11]
The UE shall:
1> reset MAC;
…
1> remove all the entries within VarConditionalReconfig, if any;
1> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
2> for the associated reportConfigId:
3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
3> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
1> discard the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if any;
1> release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the associated PDCP entity and SDAP for all established RBs;
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> except if going to RRC_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC_INACTIVE or RRC_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell for EPS fallback for IMS voice as specified in 5.4.3.5:
2> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20];
8.1.4.4.3.3 Test description
8.1.4.4.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2 and NR Cell 4.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR cells
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.4.3.3.2 Test procedure sequence
Tables 8.1.4.4.3.3.2-1 and 8.1.4.4.3.3.2-2 illustrate the downlink power levels to be applied for NR cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table 8.1.4.4.3.3.2-3.
Table 8.1.4.4.3.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-113 |
-113 |
Power levels are such that UE registered on NR Cell 1 |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-91 |
-79 |
-91 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-113 |
-113 |
-79 |
The power level is such that only SrxlevNR Cell 4 > 0 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-79 |
-91 |
-91 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-113 |
-113 |
-113 |
Power levels are such that all Srxlev NR Cell < 0 |
T5 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-113 |
-79 |
-113 |
The power level is such that only SrxlevNR Cell 2 > 0 |
Table 8.1.4.4.3.3.2-2: Power levels in FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that UE registered on NR Cell 1 |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
The power level is such that only SrxlevNR Cell 4 > 0 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 1 |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that all Srxlev NR Cell < 0 |
T5 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
The power level is such that only SrxlevNR Cell 2 > 0 |
Table 8.1.4.4.3.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 2 and NR Cell 4 as the target candidate cells. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
3 |
SS adjusts the cell-specific reference signal level according to row "T1". |
– |
– |
– |
– |
– |
EXCEPTION: The steps 4 and 5 below are repeated for the duration of T304. |
– |
– |
– |
– |
4 |
The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on NR Cell 2. |
– |
– |
– |
– |
5 |
The SS does not respond. |
– |
– |
– |
– |
6 |
SS adjusts the cell-specific reference signal level according to row "T2" right before T304 expire. |
– |
– |
– |
– |
7 |
Check: Does the UE initiate a random access procedure by transmitting Preamble in NR Cell 4 within 10s? |
–> |
(PRACH Preamble) |
1 |
P |
8 |
The SS transmits Random Access Response. |
<– |
Random Access Response |
– |
– |
9 |
The UE transmits RRCReconfigurationComplete message in NR Cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
10 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on DRB1 and NR Cell 4? |
– |
– |
1 |
P |
11 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 1 and NR Cell 2 as the target candidate cells. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
12 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
13 |
SS adjusts the cell-specific reference signal level according to row "T3". |
– |
– |
– |
– |
– |
EXCEPTION: The steps 14 and 15 below are repeated for the duration of T304. |
– |
– |
– |
– |
14 |
The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on NR Cell 1. |
– |
– |
– |
– |
15 |
The SS does not respond. |
– |
– |
– |
– |
16 |
SS adjusts the cell-specific reference signal level according to row "T4". |
– |
– |
– |
– |
17 |
Wait 5s to ensure that T304 and T311 expire. (Note 1) |
||||
18 |
SS adjusts the cell-specific reference signal level according to row "T5". |
– |
– |
– |
– |
19 |
Check: Is the generic mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 performed on NR Cell 2? |
– |
– |
2 |
P |
Note 1: The wait time is selected to cover T304 (1000ms) + T311 (1000ms) to ensure that UE goes to RRC_IDLE. |
8.1.4.4.3.3.3 Specific message contents
Table 8.1.4.4.3.3.3-1: SIB1 for NR Cell 2 (preamble and all steps, Table 8.1.4.4.3.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
PLMN-IdentityInfoList SEQUENCE { |
|||
trackingAreaCode |
2 |
||
} |
|||
} |
|||
} |
Table 8.1.4.4.3.3.3-2: RRCReconfiguration (Step1 and step 11, Table 8.1.4.4.3.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS and CHO |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
measConfig |
MeasConfig |
Table 8.1.4.4.3.3.3-3 |
||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
conditionalReconfiguration-r16 |
ConditionalReconfiguration |
Table 8.1.4.4.3.3.3-6 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.4.3.3.3-3: MeasConfig (Table 8.1.4.4.3.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
1 entry |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR |
Table 8.1.4.4.3.3.3-4 |
|
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-condEventA3 |
Table 8.1.4.4.3.3.3-5 |
|
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
} |
Table 8.1.4.4.3.3.3-4: MeasObjectNR (Table 8.1.4.4.3.3.3-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
ARFCN-ValueNR for SSB of NR Cell 1 |
The SSB of NR Cell 1, NR Cell 2 and NR Cell 4 have the same ARFCN value as specified in TS 38.508-1 [4] clause 6.2.3 |
|
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.4.3.3.3-5: ReportConfigNR-condEventA3 (Table 8.1.4.4.3.3.3-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
condTriggerConfig SEQUENCE { |
|||
condEventId CHOICE { |
|||
condEventA3 SEQUENCE { |
|||
a3-Offset CHOICE { |
|||
rsrp |
2 |
1 dB (2*0.5 dB) |
FR1 |
FFS |
FR2 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.3.3.3-6: ConditionalReconfiguration (Table 8.1.4.4.3.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25D |
|||
Information Element |
Value/remark |
Comment |
Condition |
ConditionalReconfiguration-r16::= SEQUENCE { |
|||
condReconfigToAddModList-r16 |
CondReconfigToAddModList-r16 |
Table 8.1.4.4.3.3.3-7 |
|
} |
Table 8.1.4.4.3.3.3-7: CondReconfigToAddModList-r16 (Table 8.1.4.4.3.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
2 entries |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR Cell 2 |
Table 8.1.4.4.3.3.3-8 |
Step 1 |
RRCReconfiguration-HO with condition HO_NR Cell 1 |
Table 8.1.4.4.3.3.3-8 |
Step 11 |
|
} |
|||
CondReconfigToAddMod-r16[2] ::= SEQUENCE { |
entry 2 |
||
condReconfigId-r16 |
2 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
RRCReconfiguration-HO with condition HO_NR Cell 4 |
Table 8.1.4.4.3.3.3-8 |
Step 1 |
RRCReconfiguration-HO with condition HO_NR Cell 2 |
Table 8.1.4.4.3.3.3-8 |
Step 11 |
|
} |
|||
} |
Table 8.1.4.4.3.3.3-8: RRCReconfiguration-HO (Table 8.1.4.4.3.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
CellGroupConfig with condition PCI_NR Cell 1 |
Table 8.1.4.4.3.3.3-9 |
HO_NR Cell 1 |
CellGroupConfig with condition PCI_NR Cell 2 |
Table 8.1.4.4.3.3.3-9 |
HO_NR Cell 2 |
|
CellGroupConfig with condition PCI_NR Cell 4 |
Table 8.1.4.4.3.3.3-9 |
HO_NR Cell 4 |
|
} |
|||
} |
|||
} |
|||
} |
8.1.4.4.3.3.3-9: CellGroupConfig (Table 8.1.4.4.3.3.3-8)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 1 |
PCI_NR Cell 1 |
|
Physical Cell Identity of NR Cell 2 |
PCI_NR Cell 2 |
||
Physical Cell Identity of NR Cell 4 |
PCI_NR Cell 4 |
||
} |
|||
} |
|||
} |
|||
} |
8.1.4.4.4 Conditional handover / legacy Handover / legacy Handover Failure
8.1.4.4.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and having received an RRCReconfiguration message including a ConditionalReconfiguration }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for legacy handover to a neighbour cell } then { UE performs handover procedure }
}
(2)
with { UE having stored ConditionalReconfiguration and having received another RRCReconfiguration message including a reconfigurationWithSync for legacy handover to a neighbour cell }
ensure that {
when { UE detects handover failure and find a selectable cell which is the candidate cell included in ConditionalReconfiguration before T311 expires } then { UE applies the stored condRRCReconfig associated to the selected cell and performs conditional handover to the selected cell }
}
(3)
with { UE having stored ConditionalReconfiguration and having received another RRCReconfiguration message including a reconfigurationWithSync for handover to a neighbour cell }
ensure that {
when { UE detects handover failure and can not find any selectable cell before T311 expires } then { UE goes to RRC_IDLE and releases the stored conditional handover configurations }
}
8.1.4.4.4.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.4.1 and 9.2.3.1 and 38.331 clause 5.3.7.3 and 5.3.11. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.4.1]
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed (legacy handover or conditional handover execution).
The following principles apply to CHO:
– The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.
– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.
– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration.
– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.
CHO is not supported for NG-C based handover in this release of the specification.
[TS 38.300, clause 9.2.3.1]
Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility.
Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1:
Figure 9.2.3.1-1: Inter-gNB handover procedures
1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.
2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE.
3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the RRCReconfiguration message. The access information to the target cell may include beam specific information, if any.
4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete.
NOTE 1: User Data can also be sent in step 4 if the grant allows.
…
NOTE 2: Void.
NOTE 3: Void.
RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode, PDCP can either be re-established together with a security key change or remain as it is without a key change. For SRBs, PDCP can either remain as it is, discard its stored PDCP PDUs/SDUs without a key change or be re-established together with a security key change.
Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB.
Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure except in certain CHO or DAPS handover scenarios:
– When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and reports DAPS handover failure via the source without triggering RRC connection re-establishment if the source link has not been released.
– When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts CHO execution once, otherwise re-establishment is performed.
DAPS handover for FR2 to FR2 case is not supported in this release of the specification.
The handover of the IAB-MT in SA mode follows the same procedure as described for the UE. After the backhaul has been established, the handover of the IAB-MT is part of the intra-CU topology adaptation procedure defined in TS 38.401 [4]. Modifications to the configuration of BAP sublayer and higher protocol layers above the BAP sublayer are described in TS 38.401 [4].
Beam Level Mobility does not require explicit RRC signalling to be triggered. The gNB provides via RRC signalling the UE with measurement configuration containing configurations of SSB/CSI resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. Beam Level Mobility is then dealt with at lower layers by means of physical layer and MAC layer control signalling, and RRC is not required to know which beam is being used at a given point in time.
SSB-based Beam Level Mobility is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, Beam Level Mobility can only be performed based on CSI-RS.
[TS 38.331, clause 5.3.7.3]
Upon selecting a suitable NR cell, the UE shall:
1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2;
1> stop timer T311;
…
1> if attemptCondReconfig is configured; and
1> if the selected cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in VarConditionalReconfig:
2> apply the stored condRRCReconfig associated to the selected cell and perform actions as specified in 5.3.5.3;
1> else:
2> if UE is configured with conditionalReconfiguration:
3> reset MAC;
3> release spCellConfig, if configured;
3> release the MCG SCell(s), if configured;
3> release delayBudgetReportingConfig, if configured and stop timer T342, if running;
3> release overheatingAssistanceConfig , if configured and stop timer T345, if running;
3> if MR-DC is configured:
4> perform MR-DC release, as specified in clause 5.3.5.10;
3> release idc-AssistanceConfig, if configured;
3> release btNameList, if configured;
3> release wlanNameList, if configured;
3> release sensorNameList, if configured;
3> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running;
3> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running;
3> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running;
3> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running;
3> release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e associated with the MCG, if running;
3> release releasePreferenceConfig, if configured and stop timer T346f, if running;
3> release onDemandSIB-Request if configured, and stop timer T350, if running;
3> suspend all RBs, except SRB0;
2> remove all the entries within VarConditionalReconfig, if any;
2> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
3> for the associated reportConfigId:
4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
3> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2> start timer T301;
2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;
2> apply the default MAC Cell Group configuration as specified in 9.2.2;
2> apply the CCCH configuration as specified in 9.1.1.2;
2> apply the timeAlignmentTimerCommon included in SIB1;
2> initiate transmission of the RRCReestablishmentRequest message in accordance with 5.3.7.4;
NOTE: This procedure applies also if the UE returns to the source PCell.
Upon selecting an inter-RAT cell, the UE shall:
1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’.
[TS 38.331, clause 5.3.11]
The UE shall:
1> reset MAC;
…
1> remove all the entries within VarConditionalReconfig, if any;
1> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
2> for the associated reportConfigId:
3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
3> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
1> discard the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if any;
1> release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the associated PDCP entity and SDAP for all established RBs;
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> except if going to RRC_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC_INACTIVE or RRC_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell for EPS fallback for IMS voice as specified in 5.4.3.5:
2> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20];
8.1.4.4.4.3 Test description
8.1.4.4.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2 and NR Cell 4.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR cells.
UE:
– None.
Preamble:
– If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
– Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
8.1.4.4.4.3.2 Test procedure sequence
Tables 8.1.4.4.4.3.2-1 and 8.1.4.4.4.3.2-2 illustrate the downlink power levels to be applied for NR cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", "T2", "T3", and "T4" are applied at the point indicated in the Main behaviour description in Table 8.1.4.4.4.3.2-3.
Table 8.1.4.4.4.3.2-1: Power levels in FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-79 |
-113 |
-85 |
Power levels are such that UE registered on NR Cell 1 |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-113 |
-79 |
Power levels are such that UE successfully handovers to NR Cell 4 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-85 |
-79 |
-113 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
– 113 |
-113 |
– 113 |
Power levels are such that all Srxlev NR Cell < 0 |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
-113 |
-113 |
-79 |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 4 |
Table 8.1.4.4.4.3.2-2: Power levels in FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that UE registered on NR Cell 1 |
T1 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that UE successfully handovers to NR Cell 4 |
T2 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 2 |
T3 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that all Srxlev NR Cell < 0 |
T4 |
SS/PBCH SSS EPRE |
dBm/ SCS |
FFS |
FFS |
FFS |
Power levels are such that entry condition for event A3 is satisfied for NR Cell 4 |
Table 8.1.4.4.4.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 2 as the target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
2 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 1. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
2A |
SS adjusts the cell-specific reference signal level according to row "T1". |
||||
3 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync for handover to NR Cell 4. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
4 |
Check: Does UE transmit the RRCReconfigurationComplete message in NR Cell 4 within 10s? |
–> |
NR RRC: RRCReconfigurationComplete |
1 |
P |
4A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on NR Cell 4? |
– |
– |
1 |
– |
– |
EXCEPTION: Steps 5-15 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if inactiveState is configured |
– |
– |
– |
– |
5 |
IF pc_condHandoverFailure-r16 THEN the SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 2 as the target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
6 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 4. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
7 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync for handover to NR Cell 1? |
<– |
NR RRC: RRCReconfiguration |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 8 the steps specified in Table 8.1.4.4.4.3.2-4 should take place. |
– |
– |
– |
– |
8 |
SS adjusts the cell-specific reference signal level according to row "T2". |
– |
– |
– |
– |
9 |
Check: Does UE transmit the RRCReconfigurationComplete message in NR Cell 2 within 10s? |
–> |
NR RRC: RRCReconfigurationComplete |
2 |
P |
9A |
Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.1-1 indicate that the UE is capable of exchanging IP data on NR Cell 2? |
– |
– |
2 |
– |
10 |
The SS transmits an RRCReconfiguration message including MeasConfig and ConditionalReconfiguration to set NR Cell 4 as the target candidate cell. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
11 |
The UE transmits an RRCReconfigurationComplete message in NR Cell 2. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
12 |
The SS transmits an RRCReconfiguration message including a reconfigurationWithSync for handover to NR Cell 1? |
<– |
NR RRC: RRCReconfiguration |
– |
– |
12A |
SS adjusts the cell-specific reference signal level according to row "T3". |
– |
– |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 13 the steps specified in Table 8.1.4.4.4.3.2-4 should take place until T304 expiry. |
– |
– |
– |
– |
13 |
SS waits 5s to make sure that the UE is in idle state. (Note 1) |
||||
14 |
SS adjusts the cell-specific reference signal level according to row "T4". |
– |
– |
– |
– |
15 |
Check: Is the generic mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 performed on NR Cell 4? |
– |
– |
3 |
-P |
Note 1: The wait time is selected to cover T304 (1000ms) + T311 (1000ms) to ensure that UE goes to RRC_IDLE. |
Table 8.1.4.4.4.3.2-4: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
– |
EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304. |
– |
– |
– |
– |
1 |
The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on NR Cell 1. |
– |
– |
– |
– |
2 |
The SS does not respond. |
– |
– |
– |
– |
8.1.4.4.4.3.3 Specific message contents
Table 8.1.4.4.4.3.3-1: RRCReconfiguration (Step1, step 5 and step 10, Table 8.1.4.4.4.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS and CHO |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
measConfig |
MeasConfig |
Table 8.1.4.4.4.3.3-2 |
||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
conditionalReconfiguration-r16 |
ConditionalReconfiguration |
Table 8.1.4.4.4.3.3-5 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 8.1.4.4.4.3.3-2: MeasConfig (Table 8.1.4.4.4.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-69 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasConfig ::= SEQUENCE { |
|||
measObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod { |
1 entry |
||
MeasObjectToAddMod[1] SEQUENCE { |
entry 1 |
||
measObjectId |
1 |
||
measObject CHOICE { |
|||
measObjectNR |
MeasObjectNR |
Table 8.1.4.4.4.3.3-3 |
|
} |
|||
} |
|||
} |
|||
reportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod { |
1 entry |
||
ReportConfigToAddMod[1] SEQUENCE { |
entry 1 |
||
reportConfigId |
1 |
||
reportConfig CHOICE { |
|||
reportConfigNR |
ReportConfigNR-condEventA3 |
Table 8.1.4.4.4.3.3-4 |
|
} |
|||
} |
|||
} |
|||
measIdToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod { |
1 entry |
||
MeasIdToAddMod[1] SEQUENCE { |
entry 1 |
||
measId |
1 |
||
measObjectId |
1 |
||
reportConfigId |
1 |
||
} |
|||
} |
|||
} |
Table 8.1.4.4.4.3.3-3: MeasObjectNR (Table 8.1.4.4.4.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-76 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasObjectNR::= SEQUENCE { |
|||
ssbFrequency |
ARFCN-ValueNR for SSB of NR Cell 1 |
The SSB of NR Cell 1, NR Cell 2 and NR Cell 4 have the same ARFCN value as specified in TS 38.508-1 [4] clause 6.2.3 |
|
absThreshSS-BlocksConsolidation |
Not present |
||
nrofSS-BlocksToAverage |
Not present |
||
} |
Table 8.1.4.4.4.3.3-4: ReportConfigNR-condEventA3 (Table 8.1.4.4.4.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ReportConfigNR ::= SEQUENCE { |
|||
reportType CHOICE { |
|||
condTriggerConfig SEQUENCE { |
|||
condEventId CHOICE { |
|||
condEventA3 SEQUENCE { |
|||
a3-Offset CHOICE { |
|||
rsrp |
2 |
1 dB (2*0.5 dB) |
FR1 |
FFS |
FR2 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.4.3.3-5: ConditionalReconfiguration (Table 8.1.4.4.4.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25D |
|||
Information Element |
Value/remark |
Comment |
Condition |
ConditionalReconfiguration-r16::= SEQUENCE { |
|||
condReconfigToAddModList-r16 |
CondReconfigToAddModList-r16 |
Table 8.1.4.4.4.3.3-6 |
|
} |
Table 8.1.4.4.4.3.3-6: CondReconfigToAddModList-r16 (Table 8.1.4.4.4.3.3-5)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C |
|||
Information Element |
Value/remark |
Comment |
Condition |
CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 { |
1 entry |
||
CondReconfigToAddMod-r16[1] ::= SEQUENCE { |
entry 1 |
||
condReconfigId-r16 |
1 |
||
condExecutionCond-r16::= SEQUENCE { |
|||
MeasId [1] |
1 |
||
} |
|||
condRRCReconfig-r16 |
OCTET STRING (CONTAINING RRCReconfiguration-HO with condition HO_NR Cell 2) |
Table 8.1.4.4.4.3.3-7 |
Step 1, Step 5 |
OCTET STRING (CONTAINING RRCReconfiguration-HO with condition HO_NR Cell 4) |
Table 8.1.4.4.4.3.3-7 |
Step 10 |
|
} |
|||
} |
Table 8.1.4.4.4.3.3-7: RRCReconfiguration-HO (Table 8.1.4.4.4.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
OCTET STRING (CONTAINING CellGroupConfig with condition PCI_NR Cell 2) |
Table 8.1.4.4.4.3.3-8 |
HO_NR Cell 2 |
OCTET STRING (CONTAINING CellGroupConfig with condition PCI_NR Cell 4) |
Table 8.1.4.4.4.3.3-8 |
HO_NR Cell 4 |
|
} |
|||
} |
|||
} |
|||
} |
8.1.4.4.4.3.3-8: CellGroupConfig (Table 8.1.4.4.4.3.3-7)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and CFRA |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfig SEQUENCE { |
|||
reconfigurationWithSync SEQUENCE { |
|||
spCellConfigCommon SEQUENCE { |
|||
physCellId |
Physical Cell Identity of NR Cell 2 |
PCI_NR Cell 2 |
|
Physical Cell Identity of NR Cell 4 |
PCI_NR Cell 4 |
||
} |
|||
} |
|||
} |
|||
} |
Table 8.1.4.4.4.3.3-9: RRCReconfiguration-HO (Step 3, step 7 and step 12, Table 8.1.4.4.4.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcReconfiguration SEQUENCE { |
|||
nonCriticalExtension SEQUENCE{ |
|||
masterCellGroup |
OCTET STRING (CONTAINING CellGroupConfig with condition PCI_NR Cell 4) |
Table 8.1.4.4.4.3.3-8 |
Step 3 |
OCTET STRING (CONTAINING CellGroupConfig with condition PCI_NR Cell 1) |
Table 8.1.4.4.4.3.3-8 |
Step 7, Step 12 |
|
} |
|||
} |
|||
} |
|||
} |