8.1.4 Handover

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

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-K_gNB key based on the K_eNB key and using the received sk-Counter value, as specified in TS 33.401 [30];

3> derive the K_RRCenc and K_UPenc keys as specified in TS 33.401 [30];

3> derive the K_RRCint and K_UPint 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 K_gNB key based on the K_AMF key, as specified in TS 33.501 [11];

2> else:

3> derive or update the K_gNB key based on the current K_gNB 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 K_gNB key as follows:

3> if the securityAlgorithmConfig is included in SecurityConfig:

4> derive the K_RRCenc and K_UPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];

4> derive the K_RRCint and K_UPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];

3> else:

4> derive the K_RRCenc and K_UPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501 [11];

4> derive the K_RRCint and K_UPint 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

Procedure

Message Sequence

Verdict

U – S

Message

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 K_AMF has been calculated by the network
TSC	‘0’B	native security context (for KSI_AMF)
Key set identifier in 5G	KSI_AMFthat 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 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 K_gNB key based on the K_AMF key, as specified in TS 33.501 [11];

2> else:

3> derive or update the K_gNB key based on the current K_gNB 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 K_gNB key as follows:

3> if the securityAlgorithmConfig is included in SecurityConfig:

4> derive the K_RRCenc and K_UPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];

4> derive the K_RRCint and K_UPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];

3> else:

4> derive the K_RRCenc and K_UPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501 [11];

4> derive the K_RRCint and K_UPint 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 K_gNB key based on the current K_gNB key or the NH, using the stored nextHopChainingCount value, as specified in TS 33.501 [11];

1> derive the K_RRCenc and K_UPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501 [11];

1> derive the K_RRCint and K_UPint 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 K_RRCint 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 K_RRCint 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 K_RRCenc 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

SS/PBCH

SSS EPRE

dBm/SCS

-88

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

SS/PBCH

SSS EPRE

dBm/SCS

FFS

SS/PBCH

SSS EPRE

dBm/SCS

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.