8.1.1 RRC connection management procedures

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

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

8.1.1.1 Paging

8.1.1.1.1 RRC / Paging for connection / Multiple paging records

8.1.1.1.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state }

ensure that {

when { UE receives a Paging message including only unmatched identities }

then { UE does not establish any RRC connection }

}

(2)

with { UE in NR RRC_IDLE state }

ensure that {

when { UE receives a Paging message including a matched identity ng-5G-S-TMSI }

then { UE successfully establishes the RRC connection }

}

(3)

with { UE in NR RRC_INACTIVE state }

ensure that {

when { UE receives a Paging message including only unmatched identities }

then { UE does not resume RRC connection }

}

(4)

with { UE in NR RRC_INACTIVE state }

ensure that {

when { UE receives a Paging message including a matched identity fullI-RNTI }

then { UE successfully resumes the RRC connection }

}

8.1.1.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.2.3.

[TS 38.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:

3> forward the ue-Identity and accessType (if present) to the upper layers;

1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the UE’s stored fullI-RNTI:

3> if the UE is configured by upper layers with Access Identity 1:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mps-PriorityAccess;

3> else if the UE is configured by upper layers with Access Identity 2:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mcs-PriorityAccess;

3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to highPriorityAccess;

3> else:

4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-Access;

2> else if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:

3> forward the ue-Identity to upper layers and accessType (if present) to the upper layers;

3> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘other’.

8.1.1.1.1.3 Test Description

8.1.1.1.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in 5GS state 1N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.

8.1.1.1.1.3.2 Test procedure sequence

Table 8.1.1.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including only unmatched identities (incorrect ng-5G-S-TMSI).	<–	NR RRC: Paging	–	–
2	Check: Does the UE transmit an RRCSetupRequest message within 10s?	–>	NR RRC: RRCSetupRequest	1	F
3	The SS transmits a Paging message including two unmatched identities (incorrect ng-5G-S-TMSI) and a matched identity (correct ng-5G-S-TMSI).	<–	NR RRC: Paging	–	–
4	Check: Does the UE transmit an RRCSetupRequest message?	–>	NR RRC: RRCSetupRequest	2	P
5	The SS transmits an RRCSetup message.	<–	NR RRC: RRCSetup	–	–
6	The UE transmit an RRCSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment.	–>	NR RRC: RRCSetupComplete 5GMM: SERVICE REQUEST	–	–
7-10	Steps 5 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 Table 4.5.4.2-3 are executed to successfully complete the service request procedure.	–	–	–	–
–	EXCEPTION: Steps 11a1-11a7 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if inactiveState is configured	–	–	–	–
11 a1	IF pc_inactiveState THEN the SS transmits an RRCRelease message including suspendConfig.	<–	NR RRC: RRCRelease	–	–
11a2	The SS transmits a Paging message including only unmatched identities (incorrect fullI-RNTI).	<–	NR RRC: Paging	–	–
11a3	Check: Does the UE transmit an RRCResumeRequest message within 10s?	–>	NR RRC: RRCResumeRequest	3	F
11a4	The SS transmits a Paging message including two unmatched identities (incorrect fullI-RNTI) and a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
11a5	Check: Does the UE transmit an RRCResumeRequest message?	–>	NR RRC: RRCResumeRequest	4	P
11a6	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
11a7	The UE transmits an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–
12-17	Void	–	–	–	–

8.1.1.1.1.3.3 Specific message contents

Table 8.1.1.1.1.3.3-1: Paging (step 1, Table 8.1.1.1.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord {	3 entries
PagingRecord[1] SEQUENCE {		entry 1
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the different value from the NG-5G-S-TMSI of the UE
}
}
PagingRecord[2] SEQUENCE {		entry 2
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the different value from the NG-5G-S-TMSI of the UE
}
}
PagingRecord[3] SEQUENCE {		entry 3
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the different value from the NG-5G-S-TMSI of the UE
}
}
}
}

Table 8.1.1.1.1.3.3-2: Paging (step 3, Table 8.1.1.1.1.3.2-1)

Derivation Path: TS 38.508-1[4], Table 4.6.1-9
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord {	3 entries
PagingRecord[1] SEQUENCE {		entry 1
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the different value from the NG-5G-S-TMSI of the UE
}
}
PagingRecord[2] SEQUENCE {		entry 2
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the different value from the NG-5G-S-TMSI of the UE
}
}
PagingRecord[3] SEQUENCE {		entry 3
ue-Identity CHOICE {
ng-5G-S-TMSI	Set to the value of the NG-5G-S-TMSI of the UE
}
}
}
}

Table 8.1.1.1.1.3.3-3: RRCSetupRequest (step 4, Table 8.1.1.1.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-23
Information Element	Value/remark	Comment	Condition
RRCSetupRequest ::= SEQUENCE {
rrcSetupRequest SEQUENCE {
establishmentCause	mt-Access
}
}

Table 8.1.1.1.1.3.3-4: Paging (step 11a2, Table 8.1.1.1.1.3.2-1)

Derivation Path: TS 38.508-1 Table 4.6.1-9
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord {	3 entries
PagingRecord[1] SEQUENCE {		entry 1
ue-Identity CHOICE {
fullI-RNTI	Set to the different value from the I-RNTI-Value of the UE
}
}
PagingRecord[2] SEQUENCE {		entry 2
ue-Identity CHOICE {
fullI-RNTI	Set to the different value from the I-RNTI-Value of the UE
}
}
PagingRecord[3] SEQUENCE {		entry 3
ue-Identity CHOICE {
fullI-RNTI	Set to the different value from the I-RNTI-Value of the UE
}
}
}
}

Table 8.1.1.1.1.3.3-5: Paging (step 11a4, Table 8.1.1.1.1.3.2-1)

Derivation Path: TS 38.508-1 Table 4.6.1-9
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord {	3 entries
PagingRecord[1] SEQUENCE {		entry 1
ue-Identity CHOICE {
fullI-RNTI	Set to the different value from the I-RNTI-Value of the UE
}
}
PagingRecord[2] SEQUENCE {		entry 2
ue-Identity CHOICE {
fullI-RNTI	Set to the different value from the I-RNTI-Value of the UE
}
}
PagingRecord[3] SEQUENCE {		entry 3
ue-Identity CHOICE {
fullI-RNTI	Set to the value of the I-RNTI-Value of the UE
}
}
}
}

8.1.1.1.2 RRC / Paging for connection / Shared network environment

8.1.1.1.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state having been registered in the TA of the current cell which has broadcasted a SIB1 message including multiple PLMN identities }

ensure that {

when { UE receives a Paging message including an IE ue-Identity set to the ng-5G-S-TMSI which was allocated to the UE during the UE registration procedure }

then { UE initiates RRCSetupRequest with ue-Identity set to ng-5G-S-TMSI-Part1 }

}

(2)

with { UE having sent RRCSetupRequest with ue-Identity set to ng-5G-S-TMSI-Part1 }

ensure that {

when { the UE receives RRCSetup message }

then { UE will set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2 in RRCSetupComplete message }

}

(3)

with { UE in NR RRC_INACTIVE state having been registered in the TA of the current cell which has broadcasted a SIB1 message including multiple PLMN identities }

ensure that {

when { UE receives a Paging message including an IE ue-Identity set to the ng-5G-S-TMSI which was allocated to the UE during the UE registration procedure }

then { UE releases RRC connection with release cause ‘other’ and goes to NR RRC_IDLE state }

}

8.1.1.1.2.2 Conformance requirements

Editor’s note: conformance requirements will be updated according to latest core specification.

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.2.3,5.3.3.3 5.3.3.4 and 5.3.11, TS 24.501, clause 5.3.1.4 and 5.6.1.1 . Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:

3> forward the ue-Identity and accessType (if present) to the upper layers;

1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the UE’s stored fullI-RNTI:

…

2> else if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:

3> forward the ue-Identity to upper layers and accessType (if present) to the upper layers;

3> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘other’.

[TS 38.331, clause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an 5G-S-TMSI:

3> set the ue-Identity to ng-5G-S-TMSI-Part1;

2> else:

3> draw a 39-bit random value in the range 0..2³⁹-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the 5G-S-TMSI if the UE is registered in the TA of the current cell.

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.6.

[TS 38.331, clause 5.3.3.4]

The UE shall perform the following actions upon reception of the RRCSetup:

…

1> set the content of RRCSetupComplete message as follows:

2> if upper layers provide an 5G-S-TMSI:

3> if the RRCSetup is received in response to an RRCSetupRequest:

4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2;

3> else:

4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI;

…

1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends

[TS 38.331, clause 5.3.11]

UE shall:

1> reset MAC;

1> if T302 is running:

2> stop timer T302;

2> perform the actions as specified in 5.3.14.4;

1> stop all timers that are running except T320 and T325;

1> discard the UE Inactive AS context;

1> set the variable pendingRnaUpdate to false, if that is set to true;

1> discard the K_gNB, the K_RRCenc key, the K_RRCint, the K_UPint key and the K_UPenc key, if any;

1> release all radio resources, including release of the RLC 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> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20], except if going to RRC_IDLE was triggered by selecting an inter-RAT cell while T311 was running;

1> if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime:

2> start timer T302 with the value set to the waitTime;

2> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’.

[TS 24.501, clause 5.3.1.4]

…

Upon receiving AMF paging indication from the lower layers, the UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access and handle the AMF paging same as the paging request received in the 5GMM-IDLE mode over 3GPP access as specified in clause 5.6.1.

[TS 24.501, clause 5.6.1.1]

…

The UE shall invoke the service request procedure when:

a) the UE, in 5GMM-IDLE mode over 3GPP access, receives a paging request from the network;

8.1.1.1.2.3 Test description

8.1.1.1.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1.

UE:

– None.

Preamble:

– The UE is in state 1N-A as defined in TS 38.508-1 [4], clause 4.4A on NR Cell 1 and 5G-GUTI is allocated in REGISTRATION ACCEPT.

8.1.1.1.2.3.2 Test procedure sequence

Table 8.1.1.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched ng-5G-S-TMSI.	<–	NR RRC: Paging	–	–
2	Check: Does the UE transmit an RRCSetupRequest message with ue-Identity set to ng-5G-S-TMSI-Part1?	–>	NR RRC: RRCSetupRequest	1	P
3	The SS transmits an RRCSetup message.	<–	NR RRC: RRCSetup	–	–
4	Check: Does the UE transmit an RRCSetupComplete message including ng-5G-S-TMSI-Part2 and a SERVICE REQUEST message and an IE selectedPLMN-Identity corresponding to the PLMN on which the UE has been registered to confirm the successful completion of the connection establishment?	–>	NR RRC: RRCSetupComplete	2	P
5-8	Steps 5 to 8 of the generic radio bearer establishment procedure (TS 38.508-1 [4] Table 4.5.4.2-3) are executed to successfully complete the service request procedure.	–	–	–	–
–	EXCEPTION: Steps 9a1-9b1 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if inactiveState is configured	–	–	–	–
9 a1	IF pc_inactiveState THEN the SS transmits an RRCRelease message with suspendConfig to suspend RRC connection and move to RRC_INACTIVE state.	<–	NR RRC: RRCRelease	–	–
9a2	Wait 5s and the SS transmits a Paging message including a matched ng-5G-S-TMSI.	<–	NR RRC: Paging	–	–
9a3	Check: Does the UE transmit an RRCSetupRequest message on the cell specified in the test case?	–>	NR RRC: RRCSetupRequest	3	P
9a49a10-	Steps 3-9 of Generic procedure for checking UE is in state 5GC RRC_IDLE on a certain cell as specified in Table 4.9.4.2.2-1 of TS 38.508-1 [4] are performed.	–	–	–	–
9b1	ELSE the SS transmits an RRCRelease message	<–	NR RRC: RRCRelease	–	–
10-18	Void	–	–	–	–

8.1.1.1.2.3.3 Specific message contents

Table 8.1.1.1.2.3.3-1: SIB1 (preamble and all steps, Table 8.1.1.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
CellAccessRelatedInfo SEQUENCE {
plmn-IdentityList	PLMN-IdentityInfoList
}
}

Table 8.1.1.1.2.3.3-2: PLMN-IdentityInfoList (Table 8.1.1.1.2.3.3-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-108
Information Element	Value/remark	Comment	Condition
PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo {	1 entry
PLMN-IdentityInfo[1] SEQUENCE {		entry 1
plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity {	2 entries
plmn-Identity[1] SEQUENCE {		entry 1
mcc	See Table 8.1.1.1.2.3.3-2A	PLMN1
mnc	See Table 8.1.1.1.2.3.3-2A	PLMN1
}
plmn-Identity[2] SEQUENCE {		entry 2
mcc	See Table 8.1.1.1.2.3.3-2A	PLMN2
mnc	See Table 8.1.1.1.2.3.3-2A	PLMN2
}
}
}
}

The PLMN Identity list broadcasted on the BCCH in NR Cell 1 shall be configured as defined in the table below.

Table 8.1.1.1.2.3.3-2A: PLMN Identity List broadcasted for NR Cell 1

Cell	PLMN Identity [1]		PLMN Identity [2]
Cell	MCC digits	MNC digits	MCC digits	MNC digits
1	PLMN 1	PLMN 1	PLMN 2	PLMN 2

The definition of each PLMN code is found in table below:

Table 8.1.1.1.2.3.3-2B: definition of each PLMN code

PLMN	MCC digit			MNC digit
	1	2	3	1	2	3
1	(NOTE 2)			(NOTE 2)
2	(NOTE 3)			0	2	–

NOTE 1: "–" (dash) denotes "not present"

NOTE 2: Set to the same Mobile Country Code and Mobile Network Code stored in EF_IMSI on the test USIM card for PLMN 1.

NOTE 3: Set to the same Mobile Country Code stored in EF_IMSI on the test USIM card for PLMN 2.

Table 8.1.1.1.2.3.3-3: RRCSetupRequest (step 2, 9a3, Table 8.1.1.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-23
Information Element	Value/remark	Comment	Condition
RRCSetupRequest ::= SEQUENCE {
rrcSetupRequest SEQUENCE {
ue-Identity CHOICE {
ng-5G-S-TMSI-Part1	ng-5G-S-TMSI-Part1	ng-5G-S-TMSI-Part1 is rightmost 39 bits of 5G-S-TMSI. 5G-S-TMSI is derived from 5G-GUTI in REGISTRATION ACCEPT according to TS 23.003 [34]
}
establishmentCause	mt-Access
}
}

Table 8.1.1.1.2.3.3-4: RRCSetupComplete (step 4, Table 8.1.1.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-22
Information Element	Value/remark	Comment	Condition
RRCSetupComplete::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcSetupComplete SEQUENCE {
ng-5G-S-TMSI-Value	ng-5G-S-TMSI-Part2	ng-5G-S-TMSI-Part2 is the leftmost 9 bits of 5G-S-TMSI. 5G-S-TMSI is derived from 5G-GUTI in REGISTRATION ACCEPT according to TS 23.003 [34]
selectedPLMN-Identity	1 or 2	PLMN1 or PLMN2 Note1
}
}
}
Note1: If RPLMN is PLMN1, UE will select PLMN1; if RPLMN is PLMN2, UE will select PLMN2

Table 8.1.1.1.2.3.3-5: RRCRelease (step 9a1, Table 8.1.1.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
suspendConfig SEQUENCE {
fullI-RNTI	I-RNTI-Value	38.508-1[4] Table 4.6.3-64
shortI-RNTI	ShortI-RNTI-Value	38.508-1[4] Table 4.6.3-170
ran-PagingCycle	rf256
ran-NotificationAreaInfo CHOICE {
cellList SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell {	2 entries
PLMN-RAN-AreaCellList[1] SEQUENCE {		entry 1
plmn-Identity	PLMN1
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity {	1 entry
CellIdentity[1]	CellIdentity of NR Cell 1	entry 1
}
}
PLMN-RAN-AreaCellList[2] SEQUENCE {		entry 2
plmn-Identity	PLMN2
ran-AreaCells SEQUENCE (SIZE (1..32)) OF CellIdentity {	1 entry
CellIdentity[1]	CellIdentity of NR Cell 1	entry 1
}
}
}
}
t380	Not Present
nextHopChainingCount	NextHopChainingCount	38.508-1[4] Table 4.6.3-83
}
}
}
}

8.1.1.2 RRC connection establishment

8.1.1.2.1 RRC connection establishment / Return to idle state after T300 expiry / connEstFailOffsetValidity / T300 expired

8.1.1.2.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state having sent an RRCSetupRequest message }

ensure that {

when { the SS does not answer to the UE during T300 }

then { UE goes to RRC_IDLE state }

}

(2)

with { UE in NR RRC_IDLE state }

ensure that {

when { T300 has expired a consecutive connEstFailCount times on the same cell for which connEstFailureControl is included in SIB1 for a period as indicated by connEstFailOffsetValidity }

then { UE uses connEstFailOffset for the parameter Qoffsettemp when performing cell reselection }

}

(3)

with { UE in NR RRC_IDLE state }

ensure that {

when { connEstFailOffsetValidity has expired }

then { UE stops using the parameter Qoffsettemp when performing cell reselection }

}

(4)

with { UE in NR RRC_IDLE state }

ensure that {

when { UE receives a short message transmitted on PDCCH using P-RNTI indicating a systemInfoModification }

then {UE re-acquires and applies the new system information }

}

8.1.1.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.3.7. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.3.7]

The UE shall:

1> if timer T300 expires:

2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

2> if the T300 has expired a consecutive connEstFailCount times on the same cell for which connEstFailureControl is included in SIB1:

3> for a period as indicated by connEstFailOffsetValidity:

4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell selection and reselection according to TS 38.304 [20] and TS 36.304 [27];

NOTE: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during connEstFailOffsetValidity for the concerned cell.

2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends;

8.1.1.2.1.3 Test description

8.1.1.2.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 and NR Cell 3.

– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.

UE:

– None.

Preamble:

– The UE is in state 1N-A as defined in TS 38.508-1 [4], clause 4.4A on NR Cell 1 and 5G-GUTI is allocated in REGISTRATION ACCEPT.

8.1.1.2.1.3.2 Test procedure sequence

Table 8.1.1.2.1.3.2-1/2 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 configuration marked "T1" is applied at the points indicated in the Main behaviour description in Table 8.1.1.2.1.3.2-3.

Table 8.1.1.2.1.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-78	Off
T1	SS/PBCH SSS EPRE	dBm/SCS	-78	-88
Note: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.

Table 8.1.1.2.1.3.2-2: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-82	Off
	Qrxlevmin	dBm	-91+Delta(NRf1)	–
T1	SS/PBCH SSS EPRE	dBm/SCS	-82	-91
	Qrxlevmin	dBm	-91+Delta(NRf1)	-100+Delta(NRf2)

Table 8.1.1.2.1.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched ng-5G-S-TMSI.	<–	NR RRC: Paging	–	–
2	The UE transmits an RRCSetupRequest message.	–>	NR RRC: RRCSetupRequest	–	–
3	The SS waits for 2s (T300 expire).	–	–	–	–
4	Check: Does UE send RRCSetupRequest in 5 second?	–>	NR RRC: RRCSetupRequest	1	F
5	Check: Does the test result of generic test procedure step 1-8 in TS 38.508-1 [4] Table 4.9.4.2.2-1 indicate that the UE is in RRC_IDLE?	–	–	1	–
6	SS transmits an RRCRelease message to release RRC connection and move the UE to RRC_IDLE	<–	NR RRC: RRCRelease	–	–
7	The SS remove connEstFailOffset in SIB1.	–	–	–	–
8	The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification.	–	PDCCH (DCI 1_0): Short Message	–	–
8A	Wait for 2.1* modification period to allow the new system information to take effect.	–	–	–	–
9	Void	–	–	–	–
10	The SS transmits a Paging message including a matched ng-5G-S-TMSI.	<–	NR RRC: Paging	–	–
11	The UE transmits an RRCSetupRequest message.	–>	NR RRC: RRCSetupRequest	–	–
12	The SS waits for 2s to let T300 expire.	–	–	–	–
12A	The SS re-adjusts the SS levels according to row "T1" in table 8.1.1.2.1.3.2-1/2 and waits for 35s to allow UE to perform cell reselection.	–	–	–	–
13	The SS transmits a Paging message including a matched ng-5G-S-TMSI on NR Cell 1.	<–	NR RRC: Paging	–	–
14	Check: Does UE send RRCSetupRequest in 5 second?	–>	NR RRC: RRCSetupRequest	2	F
15	Void	–	–	–	–
16	After expiry of connEstFailOffsetValidity, the SS waits 35s to allow UE to perform cell reselection.	–	–	–	–
17	Check: Does the test result of generic test procedure step 1-9a1 in TS 38.508-1 [4] Table 4.9.4.2.2-1 indicate that the UE is in RRC_IDLE on NR Cell 1?	–	–	3	–
18	The SS changes NR Cell 3 to high priority in SIB4 and the ValueTag of SIB4 in the SI-SchedulingInfo of SIB1 is increased on NR Cell 1.	–	–	–	–
18A	The SS changes NR cell reselection priority of NR Cell 3 in the SIB2 of NR Cell 3 and the ValueTag of SIB2 in the SI-SchedulingInfo of SIB1 is increased on NR Cell 3.	–	–	–	–
19	The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification.	–	PDCCH (DCI 1_0): Short Message	–	–
20	Wait for 2.1* modification period to allow the new system information to take effect.	–	–	–	–
21	Check: Does the test result of generic test procedure step 1-9a1 in TS 38.508-1 [4] Table 4.9.4.2.2-1 indicate that the UE is in RRC_IDLE on NR Cell 3?	–	–	4	–

8.1.1.2.1.3.3 Specific message contents

Table 8.1.1.2.1.3.3-1: RRCSetupRequest (steps 2 and 11, Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-23
Information Element	Value/remark	Comment	Condition
RRCSetupRequest ::= SEQUENCE {
rrcSetupRequest SEQUENCE {
establishmentCause	mt-Access
}
}

Table 8.1.1.2.1.3.3-2: SIB1 (step 7, Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
connEstFailureControl	ConnEstFailureControl	Table 8.1.1.2.1.3.3-3
}

Table 8.1.1.2.1.3.3-3: ConnEstFailureControl (Table 8.1.1.2.1.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-27
Information Element	Value/remark	Comment	Condition
ConnEstFailureControl ::= SEQUENCE {
connEstFailOffsetValidity	s60
connEstFailOffset	Not present	Value of infinity shall be used for Qoffset_temp
}

Table 8.1.1.2.1.3.3-4: SIB4 of NR Cell 1 (steps 18, Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.2-3
Information Element	Value/remark	Comment	Condition
SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo {	1 entry
InterFreqCarrierFreqInfo[1] SEQUENCE {		entry 1 The entry corresponding to the carrier of NR Cell 3
cellReselectionPriority	7	Higer priority than NR Cell 1
}
}
}

Table 8.1.1.2.1.3.3-5: SIB2 of NR Cell 3 (steps 18A, Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-1
Information Element	Value/remark	Comment	Condition
SIB2::= SEQUENCE {
cellReselectionServingFreqInfo SEQUENCE{
cellReselectionPriority	7	Higer priority than NR Cell 1
}
}

Table 8.1.1.2.1.3.3-6: SIB1 of NR Cell 1 (Step 18), Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
si-SchedulingInfo	SI-SchedulingInfo
}

Table 8.1.1.2.1.3.3-7: SI-SchedulingInfo (si-SchedulingInfo in Table 8.1.1.2.1.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-173
Information Element	Value/remark	Comment	Condition
SI-SchedulingInfo ::= SEQUENCE {
schedulingInfoList SEQUENCE (SIZE(1..maxSI-Message)) OF SchedulingInfo {	1 entry
SchedulingInfo[1] SEQUENCE {		entry 1
sib-MappingInfo SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo {	2 entries
SIB-TypeInfo[1] SEQUENCE {		entry 1
Type[1]	sibType2
valueTag[1]	0
}
SIB-TypeInfo[1] SEQUENCE {		entry 2
Type[1]	sibType4
valueTag[1]	1
}
}
}
}
}

Table 8.1.1.2.1.3.3-8: SIB1 of NR Cell 3 (Step 18A), Table 8.1.1.2.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
si-SchedulingInfo	SI-SchedulingInfo
}

Table 8.1.1.2.1.3.3-9: SI-SchedulingInfo (si-SchedulingInfo in Table 8.1.1.2.1.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-173
Information Element	Value/remark	Comment	Condition
SI-SchedulingInfo ::= SEQUENCE {
schedulingInfoList SEQUENCE (SIZE(1..maxSI-Message)) OF SchedulingInfo {	1 entry
SchedulingInfo[1] SEQUENCE {		entry 1
sib-MappingInfo SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo {	2 entries
SIB-TypeInfo[1] SEQUENCE {		entry 1
Type[1]	sibType2
valueTag[1]	1
}
SIB-TypeInfo[1] SEQUENCE {		entry 2
Type[1]	sibType4
valueTag[1]	0
}
}
}
}
}

8.1.1.2.2 Void

8.1.1.2.3 RRC connection establishment / RRC Reject with wait time

8.1.1.2.3.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state and has sent an RRCSetupRequest message }

ensure that {

when { UE receives an RRCReject message including an IE waitTime }

then { UE doesn’t re-send RRCSetupRequest message before the waitTime is expired }

}

8.1.1.2.3.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.15.2.

[TS 38.331, clause 5.3.15.2]

The UE shall:

1> stop timer T300, if running;

1> stop timer T319, if running;

1> stop timer T302, if running;

1> reset MAC and release the default MAC Cell Group configuration;

1> if waitTime is configured in the RRCReject:

2> start timer T302, with the timer value set to the waitTime;

1> if RRCReject is received in response to a request from upper layers:

2> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’;

1> if RRCReject is received in response to an RRCSetupRequest:

2> inform upper layers about the failure to setup the RRC connection, upon which the procedure ends;

1> else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1:

2> if resume is triggered by upper layers:

3> inform upper layers about the failure to resume the RRC connection;

2> if resume is triggered due to an RNA update:

3> set the variable pendingRnaUpdate to true;

2> discard the current K_gNB key, the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key derived in accordance with 5.3.13.3;

2> suspend SRB1, upon which the procedure ends;

The RRC_INACTIVE UE shall continue to monitor paging while the timer T302 is running.

8.1.1.2.3.3 Test Description

8.1.1.2.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 and Test Loop Function (On) with UE test loop mode B is established.

8.1.1.2.3.3.2 Test procedure sequence

Table 8.1.1.2.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the first PDU session on NR Cell 1.	–	–	–	–
2	Wait for 1 second after the IP packet has been transmitted in step 1. (Note 1)	–	–	–	–
3	The SS transmits an RRCRelease message on NR Cell 1.	<–	NR RRC: RRCRelease	–	–
4-4A	Steps 1-2 of the NR RRC_CONNECTED procedure in table 4.5.4.2-3 in TS 38.508-1[4] are performed.	–	–	–	–
5	The SS responds with RRCReject message with IE waitTime set to 10s.	<–	NR RRC: RRCReject	–	–
6	Check: Does the UE transmit an RRCSetupRequest message while timer T302 is running?	–>	NR RRC: RRCSetupRequest	1	F
6A	The SS starts timer Timer_1 = 10 s	–	–	–	–
–	EXCEPTION: Steps 15a1 to 15b1 describe a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens. (Note 3)	–	–	–	–
7-14	Void	–	–	–	–
15a1	Check: Does UE transmit RRCSetupRequest message for sending the IP packet received in step 1 after timer T302 expires?	–	NR RRC: RRCSetupRequest	1	P
15a2-15a6	Steps 3 to 7 of the NR RRC_CONNECTED procedure in TS 38.508-1 [4] Table 4.5.4.2-3 are executed.	–	–	–	–
–	EXCEPTION: Steps 15a7 and 15a8 can occur in any order.	–	–	–	–
15a7	The UE transmits an RRCReconfigurationComplete message on Cell 1.	–>	NR RRC: RRCReconfigurationComplete	–	–
15a8	The UE loop backs the IP packet received in step 1 on the DRB associated with the first PDU session on NR Cell 1.	–	–	–	–
15a9	The SS transmits an RRCRelease message on NR Cell 1.	<–	NR RRC: RRCRelease	–	–
15b1	The SS waits for Timer_1 expiry	–	–	–	–
Note 1: The 1 second delay is used to secure that the UE has received and forwarded the IP Packet transmitted by the SS in step 1 to the UE test loop function before the RRCRelease message is sent by the SS in step 3. Note 2: Void

8.1.1.2.3.3.3 Specific message contents

Table 8.1.1.2.3.3.3-1: RRCReject (step 5, table 8.1.1.2.3.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCReject ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReject SEQUENCE {
waitTime	10	10 seconds
}
}
}

Table 8.1.1.2.3.3.3-2: CLOSE UE TEST LOOP (Preamble, Table 8.1.1.2.3.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	‘0000 0101’B	5 seconds

Table 8.1.1.2.3.3.3-3: SERVICE REQUEST (Step 15a3, Table 8.1.1.2.3.3.2-1)

Derivation Path: TS 38.508-1[4], Table 4.7.1-16
Information Element	Value/remark	Comment	Condition
Service type	‘0001’B	data

8.1.1.2.4 RRC connection establishment / Extended and spare fields in SI

8.1.1.2.4.1 Test Purpose (TP)

(1)

with { UE is powered on and receives system information }

ensure that {

when { UE receives an optional spare or extended field in system information that it does not comprehend }

then { UE treats system information as if the spare or extended field were absent and system information is not ignored, and UE establishes an RRC connection }

}

8.1.1.2.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.3.1, 10.1 and 10.3. Unless otherwise stated, these are Rel-15 requirements.

[TS 38.331, clause 5.2.2.3.1]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

1> if the UE is in RRC_CONNECTED while T311 is running:

2> acquire the MIB, which is scheduled as specified in TS 38.213 [13];

2> if the UE is unable to acquire the MIB;

3> perform the actions as specified in clause 5.2.2.5;

2> else:

3> perform the actions specified in clause 5.2.2.4.1.

1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

1> if the UE is in RRC_CONNECTED while T311 is running:

2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]) and if SIB1 acquisition is required for the UE:

3> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];

3> if the UE is unable to acquire the SIB1:

4> perform the actions as specified in clause 5.2.2.5;

3> else:

4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2.

2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled in the cell:

3> perform the actions as specified in clause 5.2.2.5.

NOTE: The UE in RRC_CONNECTED 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 10.1]

The generic error handling defined in the subsequent clauses applies unless explicitly specified otherwise e.g. within the procedure specific error handling.

The UE shall consider a value as not comprehended when it is set:

– to an extended value that is not defined in the version of the transfer syntax supported by the UE;

– to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved value.

The UE shall consider a field as not comprehended when it is defined:

– as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved field.

[TS 38.331 clause 10.3]

The UE shall, when receiving an RRC message on any logical channel:

1> if the message includes a field that has a value that the UE does not comprehend:

2> if a default value is defined for this field:

3> treat the message while using the default value defined for this field;

2> else if the concerned field is optional:

3> treat the message as if the field were absent and in accordance with the need code for absence of the concerned field;

2> else:

3> treat the message as if the field were absent and in accordance with sub-clause 10.4.

8.1.1.2.4.3 Test description

8.1.1.2.4.3.1 Pre-test conditions

System Simulator:

– NR Cell 1.

UE:

None.

Preamble:

– The UE is switched off

8.1.1.2.4.3.2 Test procedure sequence

Table 8.1.1.2.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	System information that includes extended and spare fields that the UE does not comprehend is broadcasted on BCCH. (Note 1)	<–	RRC: SYSTEM INFORMATION (BCCH)	–	–
2	The UE is switched on.	–	–	–	–
3	Does the UE transmit an RRCSetupRequest message on NR Cell 1?	–>	RRCSetupRequest	1	P
4	The SS transmits an RRCSetup message on Cell 1.	<–	RRCSetup	–	–
5	Check: Does the UE transmit an RRCSetupComplete message to confirm the successful completion of the connection establishment and initiates the registration procedure by including the REGISTRATION REQUEST message?	–>	RRCSetupComplete 5GMM: REGISTRATION REQUEST	1	P
6-21a1	Steps 5 to 20a1 of the registration procedure described in TS 38.508 Table 4.5.2.2-2 are performed on NR Cell 1.	–	–	–	–
Note 1 The NR-19 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used

8.1.1.2.4.3.3 Specific message contents

Table 8.1.1.2.4.3.3-1: MIB (step 1, Table 8.1.1.2.4.3.2-1)

Derivation Path: TS 38.508-1 Table 4.6.1-6
Information Element	Value/remark	Comment	Condition
MIB ::= SEQUENCE {
spare	‘1’B	In Rel-15, the lowest bit is considered a spare according to TS 38.331 [12].	For Rel-15
}

Table 8.1.1.2.4.3.3-2: SystemInformation (step 1, Table 8.1.1.2.4.3.2-1)

Derivation Path: TS 38.508-1, Table 4.6.1-29
Information Element	Value/remark	Comment	Condition
SystemInformation ::= SEQUENCE {
criticalExtensions CHOICE {
systemInformation SEQUENCE {
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) OF CHOICE {
SIB2
SIB11-r16		In Rel-15, SIB11 is considered an extended field according to TS 38.331 [12].
}
lateNonCriticalExtension	Not present
nonCriticalExtension	Not present
}
}
}

Table 8.1.1.2.4.3.3-3: SIB11 (Table 8.1.1.2.4.3.3-2)

Derivation Path: TS 38.508-1, Table 4.6.2-13
Information Element	Value/remark	Comment	Condition
SIB11-r16 ::= SEQUENCE {
measIdleConfigSIB-r16	Not Present
lateNonCriticalExtension	Not Present
}

8.1.1.3 RRC release

8.1.1.3.1 RRC connection release / Redirection to another NR frequency

8.1.1.3.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCRelease message including an IE redirectedCarrierInfo with nr and carrierFreq different from the frequency UE was on in RRC_CONNECTED state }

then { UE enters RRC_IDLE state on new frequency included in IE redirectedCarrierInfo }

}

8.1.1.3.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3, TS 38.304, clause 5.2.4.1.Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.8.3]

The UE shall:

1> delay the following actions defined in this clause 60ms from the moment the RRCRelease message was received or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully acknowledged, whichever is earlier;

1> stop timer T320, if running;

1> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:

2> if cnType is included:

3> the received cnType is provided to upper layers;

NOTE: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation.

1> if the RRCRelease message includes the cellReselectionPriorities:

2> store the cell reselection priority information provided by the cellReselectionPriorities;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

…

[TS 38.304, clause 5.2.4.1]

…

The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

…

[TS 38.304, clause 5.2.6]

On transition from RRC_CONNECTED to RRC_IDLE state or RRC_INACTIVE state, UE shall attempt to camp on a suitable cell according to redirectedCarrierInfo if included in the RRCRelease message used for this transition. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on.

When returning to RRC_IDLE state after UE moved to RRC_CONNECTED state from camped on any cell state, UE shall attempt to camp on an acceptable cell according to redirectedCarrierInfo, if included in the RRCRelease message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the RRCRelease message does not contain redirectedCarrierInfo UE shall attempt to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE shall continue to search for an acceptable cell of any PLMN in state any cell selection.

8.1.1.3.1.3 Test description

8.1.1.3.1.3.1 Pre-test conditions

System Simulator:

– 2 cells on different NR frequencies and different tracking areas:

– NR Cell 1 (TAI-1) serving cell

– NR Cell 23 (TAI-2) suitable neighbour inter-frequency cell

– Cell power levels are selected according to 38.508-1 [4] Table 6.2.2.1-3 for FR1 or Table 6.2.2.2-2 for FR2. NR Cell 23 is switched on after UE has registered on 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.1.3.1.3.2 Test procedure sequence

Table 8.1.1.3.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCRelease message (IE redirectedCarrierInfo including NR Cell 23).	<–	NR RRC:RRCRelease	–	–
2A	Check: Does the UE transmits an RRCSetupRequest message?	–>	NR RRC: RRCSetupRequest	1	P
2B	SS transmit an RRCSetup message on on the NGC Cell 23.	<–	NR RRC: RRCSetup	–	–
2C	Check: Does the UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of the actual tracking area?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	1	–
3	The SS transmits a SecurityModeCommand message.	<–	NR RRC: SecurityModeCommand	–	–
4	The UE transmits a SecurityModeComplete message.	–>	NR RRC: SecurityModeComplete	–	–
5-6	Steps 4-5 of TS 38.508-1 [4] Table 4.9.5.2.2-1 of the generic procedure are performed.	–	–	–	–
7	The SS transmits an RRCReconfiguration message to establish SRB2 and DRB.	<–	NR RRC: RRCReconfiguration	–	–
8	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete	–	–
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?	–	–	1	P

8.1.1.3.1.3.3 Specific message contents

Table 8.1.1.3.1.3.3-1: SIB4 for NR cells 1 and 23 (preamble and all steps, Table 8.1.1.3.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.2-3
Information Element	Value/remark	Comment	Condition
SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo {	1 entry
InterFreqCarrierFreqInfo[1] SEQUENCE {		entry 1
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 23		NR Cell 1
	Same downlink NR ARFCN as used for NR Cell 1		NR Cell 23
cellReselectionPriority	Not present
}
}
}

Table 8.1.1.3.1.3.3-2: RRCRelease message (step 1, Table 8.1.1.3.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
redirectedCarrierInfo CHOICE {
nr SEQUENCE {
carrierFreq	ARFCN-ValueNR for NR Cell 23 frequency
ssbSubcarrierSpacing	Subcarrier spacing of SSB for NR Cell 23
smtc	SSB-MTC	38.508-1 [4] Table 4.6.3-185
}
}
}
}
}

Table 8.1.1.3.1.3.3-3: RRCReconfiguration message (step 6, Table 8.1.1.3.1.3.2-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-SRB2-DRB (n, m)	38.508-1 [4] Table 4.8.1-4
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig-SRB2-DRB(n, m)	38.508-1 [4] Table 4.8.1-2B
}
}
}
}

8.1.1.3.2 RRC connection release / Redirection from NR to E-UTRA

8.1.1.3.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCRelease message including an IE redirectionInformation with E-UTRA frequency }

then { UE enters RRC_IDLE state on E-UTRA frequency included in IE redirectionInformation }

}

8.1.1.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.8.3, TS 38.304, clause 5.2.6.

[TS 38.331, clause 5.3.8.3]

The UE shall:

1> stop timer T320, if running;

1> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:

2> if cnType is included:

3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers;

NOTE: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation.

[TS 38.304, clause 5.2.6]

At reception of RRCRelease message to transition the UE to RRC_IDLE or RRC_INACTIVE, UE shall attempt to camp on a suitable cell according to redirectedCarrierInfo if included in the RRCRelease message used for this transition. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on.

8.1.1.3.2.3 Test description

8.1.1.3.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

– E-UTRA Cell 1 is a suitable neighbour cell. System information combination 31 as defined in TS 38.508 [7], subclause 4.4.3.1.1

– The parameters settings and power levels for NR Cell 1, E-UTRA Cell 1 are selected to ensure that camping on NR Cell 1 is guaranteed and no cell re-selection to E-UTRA Cell 1 can take place (E -UTRA Cell 1 priority is lower than serving NR Cell 1).

UE:

– None

Preamble:

– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell", the UE is brought to state 1E-A, RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On), in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2.

– the UE is switched-off

– With E-UTRA Cell 1 and NR Cell 1 power levels set according to T0, the UE is brought to state 3N-A as defined in TS 38.508-1 [4], clause 4.4A.2.

8.1.1.3.2.3.2 Test procedure sequence

Tables 8.1.1.3.2.3.2-1/ 8.1.1.3.2.3.2-1A illustrates the downlink power levels to be applied for NR Cell 1, E-UTRA Cell 1 for the test execution.

Table 8.1.1.3.2.3.2-1: Time instances of cell power level and parameter changes for conducted test environment

Parameter

Unit

NR Cell 1

E-UTRA Cell 1

Remark

Cell-specific RS EPRE

dBm/15kHz

“Off”

SS/PBCH

SSS EPRE

dBm/SCS

-85

–

Cell-specific RS EPRE

dBm/15kHz

-91

The power levels are such that camping on NR Cell 1 is guaranteed.

SS/PBCH

SSS EPRE

dBm/SCS

-85

–

Cell-specific RS EPRE

dBm/15kHz

-91

The power levels are such that UE performs deregistration on E-UTRA cell and does not reselect NR Cell

SS/PBCH

SSS EPRE

dBm/SCS

-110

–

Table 8.1.1.3.2.3.2-1/1A: Time instances of cell power level and parameter changes for OTA test environment

	Parameter	Unit	NR Cell 1	E-UTRA Cell 1	Remark
T0	Cell-specific RS EPRE	dBm/15kHz		“Off”
T0	SS/PBCH SSS EPRE	dBm/SCS	-82	–
T1	Cell-specific RS EPRE	dBm/15kHz		-96	The power levels are such that camping on NR Cell 1 is guaranteed.
T1	SS/PBCH SSS EPRE	dBm/SCS	-82	–
T2	Cell-specific RS EPRE	dBm/15kHz		-96	The power levels are such that UE performs deregistration on E-UTRA cell and does not reselect NR Cell
T2	SS/PBCH SSS EPRE	dBm/SCS	-139	–

Table 8.1.1.3.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS changes NR Cell 1 and E-UTRA Cell 1 level according to the row "T1" in Table 8.1.1.3.2.3.2-1/1A	–	–	–	–
1	SS transmits an RRCRelease message (IE redirectionInformation including ARFCN-ValueEUTRA of E-UTRA Cell 1).	<–	NR RRC: RRCRelease	–	–
2	Check: Does the test result of generic test procedure in TS 38.508-1 Table 4.9.7.2.2-1 is performed and the UE is camped on E-UTRAN Cell 1, with connected without release‘’?	–	–	1	–
2A	SS changes NR Cell 1 SSS levels according to the row "T2" in Table 8.1.1.3.2.3.2-1/1A.	–	–	–	–
3	At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2_T3440) according to TS 36.508 [7].	–	–	–	–

8.1.1.3.2.3.3 Specific message contents

Table 8.1.1.3.2.3.3-1 RRCRelease (step 1, Table 8.1.1.3.2.3.2-2)

Derivation Path: TS 38.508-1 table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
redirectedCarrierInfo CHOICE {
eutra SEQUENCE {
eutraFrequency	EARFCN of E-UTRA Cell 1
cnType	epc
}
}
}
}
}

8.1.1.3.3 RRC connection release / Success / With priority information / T320 expiry

8.1.1.3.3.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListNR with higher priority frequency }

ensure that {

when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority frequency }

then { UE reselects the cell which belongs to the higher priority frequency }

}

(2)

with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListNR with higher priority frequency and timer T320 }

ensure that {

when { T320 timer expires }

then { UE discards the cell reselection priority information provided by the cellReselectionPriorities and apply the cell reselection priority information broadcast in the system information to perform reselection to another NR cell }

}

8.1.1.3.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3 and TS38.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.8.3]

The UE shall:

1> delay the following actions defined in this sub-clause 60 ms from the moment the RRCRelease message was received or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully acknowledged, whichever is earlier;

1> stop timer T380, if running;

1> stop timer T320, if running;

1> stop timer T390, if running;

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> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:

2> if cnType is included:

3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers;

NOTE: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation.

1> if the RRCRelease message includes the cellReselectionPriorities:

2> store the cell reselection priority information provided by the cellReselectionPriorities;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> if deprioritisationReq is included:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

1> if the RRCRelease includes suspendConfig:

2> apply the received suspendConfig;

2> reset MAC and release the default MAC Cell Group configuration, if any;

2> re-establish RLC entities for SRB1;

2> if the RRCRelease message with suspendConfig was received in response to an RRCResumeRequest or an RRCResumeRequest1:

3> stop the timer T319 if running;

3> in the stored UE Inactive AS context:

4> replace the K_gNB and K_RRCint keys with the current K_gNB and K_RRCint keys;

4> replace the C-RNTI with the temporary C-RNTI in the cell the UE has received the RRCRelease message;

4> replace the cellIdentity with the cellIdentity of the cell the UE has received the RRCRelease message;

4> replace the physical cell identity with the physical cell identity of the cell the UE has received the RRCRelease message;

4> replace the suspendConfig with the current suspendConfig;

2> else:

3> store in the UE Inactive AS Context the received suspendConfig, all current parameters configured with RRCReconfiguration or RRCResume, the current K_gNB and K_RRCintkeys, the ROHC state, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell;

2> suspend all SRB(s) and DRB(s), except SRB0;

2> indicate PDCP suspend to lower layers of all DRBs;

2> if the t380 is included:

3> start timer T380, with the timer value set to t380;

2> if the RRCRelease message is including the waitTime:

3> start timer T302 with the value set to the waitTime;

3> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’;

2> indicate the suspension of the RRC connection to upper layers;

2> enter RRC_INACTIVE and perform cell selection as specified in TS 38.304 [20];

1> else

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with the release cause ‘other’.

[TS 38.331, clause 5.3.8.4]

The UE shall:

1> if T320 expires:

2> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT;

2> apply the cell reselection priority information broadcast in the system information.

[TS 38.304, clause 5.2.4.1]

Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCRelease unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values).

The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

In case UE receives RRCRelease with deprioritisationReq, UE shall consider current frequency and stored frequencies due to the previously received RRCRelease with deprioritisationReq or all the frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection is performed on request by NAS (TS 23.122 [9]).

NOTE: UE should search for a higher priority layer for cell reselection as soon as possible after the change of priority. The minimum related performance requirements specified in TS 38.133 [8] are still applicable.

The UE shall delete priorities provided by dedicated signalling when:

– the UE enters a different RRC state; or

– the optional validity time of dedicated priorities (T320) expires; or

– a PLMN selection is performed on request by NAS (TS 23.122 [9]).

NOTE 2: Equal priorities between RATs are not supported.

The UE shall not consider any black listed cells as candidate for cell reselection.

The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection.

NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.

[TS 38.304, clause 5.2.4.1]

The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

The UE shall delete priorities provided by dedicated signalling when:

– the UE enters a different RRC state; or

– the optional validity time of dedicated priorities (T320) expires; or

– a PLMN selection is performed on request by NAS (TS 23.122 [9]).

NOTE 2: Equal priorities between RATs are not supported.

The UE shall not consider any black listed cells as candidate for cell reselection.

The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection.

NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.

[TS 38.304, clause 5.2.4.2]

Following rules are used by the UE to limit needed measurements:

– If the serving cell fulfils Srxlev> S_IntraSearchP and Squal > S_IntraSearchQ, the UE may choose not to perform intra-frequency measurements.

– Otherwise, the UE shall perform intra-frequency measurements.

– The UE shall apply the following rules for NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:

– For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133 [8].

– For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency:

– If the serving cell fulfils Srxlev > S_{nonIntraSearchP} and Squal > S_{nonIntraSearchQ}, the UE may choose not to perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority;

– Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority according to TS 38.133 [8].

[TS 38.304, clause 5.2.4.5]

If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > Thresh_{X, HighQ} during a time interval Treselection_RAT

Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– A cell of a higher priority RAT/ frequency fulfils Srxlev > Thresh_{X, HighP} during a time interval Treselection_RAT; and

– More than 1 second has elapsed since the UE camped on the current serving cell.

Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection as defined in sub-clause 5.2.4.6.

If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– The serving cell fulfils Squal < Thresh_{Serving, LowQ} and a cell of a lower priority NR or E-UTRAN RAT/ frequency fulfils Squal > Thresh_{X, LowQ} during a time interval Treselection_RAT.

Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– The serving cell fulfils Srxlev < Thresh_{Serving, LowP} and a cell of a lower priority RAT/ frequency fulfils Srxlev > Thresh_{X, LowP} during a time interval Treselection_RAT; and

– More than 1 second has elapsed since the UE camped on the current serving cell.

Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria.

If more than one cell meets the above criteria, the UE shall reselect a cell as follows:

– If the highest-priority frequency is an NR frequency, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria according to clause 5.2.4.6;

– If the highest-priority frequency is from another RAT, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.

[TS 38.304, clause 5.2.4.6]

The cell-ranking criterion R_s for serving cell and R_n for neighbouring cells is defined by:

R_s = Q_meas,s +Q_hyst – Qoffset_temp

R_n = Q_meas,n -Qoffset – Qoffset_temp

where:

Q_meas

RSRP measurement quantity used in cell reselections.

Qoffset

For intra-frequency: Equals to Qoffset_s,n, if Qoffset_s,n is valid, otherwise this equals to zero.

For inter-frequency: Equals to Qoffset_s,n plus Qoffset_frequency, if Qoffset_s,n is valid, otherwise this equals to Qoffset_frequency.

Qoffset_temp

Offset temporarily applied to a cell as specified in TS 38.331 [3].

The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.

The cells shall be ranked according to the R criteria specified above by deriving Q_meas,nand Q_meas,sand calculating the R values using averaged RSRP results.

If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4.

If rangeToBestCell is configured, then the UE shall perform cell reselection to the cell with the highest number of beams above the threshold (i.e. absThreshSS-BlocksConsolidation) among the cells whose R value is within rangeToBestCell of the R value of the highest ranked cell. If there are multiple such cells, the UE shall perform cell reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4.

In all cases, the UE shall reselect the new cell, only if the following conditions are met:

– the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval Treselection_RAT;

– more than 1 second has elapsed since the UE camped on the current serving cell.

NOTE: If rangeToBestCell is configured but absThreshSS-BlocksConsolidation is not configured on an NR frequency, the UE considers that there is one beam above the threshold for each cell on that frequency.

8.1.1.3.3.3 Test description

8.1.1.3.3.3.1 Pre-test conditions

System Simulator:

– NR Cell 1, NR Cell 3 and NR Cell6.

– NR Cell 1 (TAI-1) serving cell.

– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cells.

NOTE: For Cell 3 and 6 TAI is set to TAI-2

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.1.3.3.3.2 Test procedure sequence

Table 8.1.1.3.3.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is 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.1.3.3.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	NR Cell 3	NR Cell 6	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-88	Off	Off	The power level values are assigned to satisfy Srxlev_{Cell 1}> S_intrasearch. (NOTE 1)
T1	SS/PBCH SSS EPRE	dBm/SCS	-88	-94	-88	The power level values are assigned to satisfy both Thresh_{x, high} < Srxlev_{Cell 3} and Thresh_{x, low} <Srxlev_{Cell 6}.
T2	SS/PBCH SSS EPRE	dBm/SCS	-88	Off	-88	The power level values are assigned to satisfy Thresh_{x, high} < Srxlev_{Cell 6}.
NOTE 1: Power level “Off” is defined in TS38.508 Table 6.2.2.1-3.

Table 8.1.1.3.3.3.2-2 Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	NR Cell 3	NR Cell 6	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-82	Off	Off	The power level values are assigned to satisfy Srxlev_{Cell 1}> S_intrasearch. (NOTE 1)
T1	SS/PBCH SSS EPRE	dBm/SCS	-82	-91	-82	The power level values are assigned to satisfy both Thresh_{x, high} < Srxlev_{Cell 3} and Thresh_{x, low} <Srxlev_{Cell 6}.
T2	SS/PBCH SSS EPRE	dBm/SCS	-82	Off	-82	The power level values are assigned to satisfy Thresh_{x, high} < Srxlev_{Cell 6}.
NOTE 1: Power level “Off” is defined in TS38.508 Table 6.2.2.1-3.

Table 8.1.1.3.3.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes NR Cell 1, NR Cell 3 and NR Cell 6 power level according to the row "T1" in table 8.1.1.3.3.3.2-1/2.	–	–	–	–
2	The SS transmits an RRCRelease message including the freqPriorityListNR on NR Cell 1.	<–	NR RRC: RRCRelease	–	–
2A	Check: Does the UE transmits an RRCSetupRequest message on NR Cell3?	–>	NR RRC: RRCSetupRequest	1	P
2B	SS transmit an RRCSetup message on NR Cell3.	<–	NR RRC: RRCSetup	–	–
2C	Check: Does the UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of the actual tracking area?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	1	P
3	Void
3A	The SS transmits a SecurityModeCommand message.	<–	NR RRC: SecurityModeCommand
3B	The UE transmits a SecurityModeComplete message.	–>	NR RRC: SecurityModeComplete
3C-3D	Steps 4-5 of TS 38.508-1 [4] Table 4.9.5.2.2-1 of the generic procedure are performed.	–	–	–	–
3E	The SS transmits an RRCReconfiguration message to establish SRB2 and DRB.	<–	NR RRC: RRCReconfiguration	–	–
3F	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete	–	–
3G	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 NR Cell 3?	–	–	1	–
3H	The SS releases RRC connection.	–	–	–	–
4	The SS changes NR Cell 1, NR Cell 3 and NR Cell 6 power level according to the row "T0" in table 8.1.1.3.3.3.2-1/2.	–	–	–	–
5-5B	Steps 1-3 in TS 38.508-1 [4] Table 4.9.5.2.2-1 are peformed on NR Cell 1.	–	–	–	–
5C	The SS transmits a SecurityModeCommand message.	<–	NR RRC: SecurityModeCommand	–	–
5D	The UE transmits a SecurityModeComplete message.	–>	NR RRC: SecurityModeComplete	–	–
5E-5F	Steps 4-5 in TS 38.508-1 [4] Table 4.9.5.2.2-1 are peformed.			–	–
6	The SS transmits an RRCRelease message containing IE freqPriorityListNR to update the cell reselection priority of NR Cell 6 and the timer T320.	<–	NR RRC: RRCRelease	–	–
7	The SS changes NR Cell 1, NR Cell 3 and NR Cell 6 power level according to the row "T2" in table 8.1.1.3.3.3.2-1/2.	–	–	–	–
8	Check: Does the UE transmit an RRCSetupRequest message within T320 running?	–>	NR RRC: RRCSetupRequest	2	F
9	Check: After timer T320 expiry, does the UE perform the Registration procedure for mobility registration update as described in steps 1-3 of Table 4.9.5.2.2-1 on NR Cell 6?	–	–	2	–
10	The SS transmits a SecurityModeCommand message.	<–	NR RRC: SecurityModeCommand	–	–
11	The UE transmits a SecurityModeComplete message.	–>	NR RRC: SecurityModeComplete	–	–
12-13	Steps 4-5 of Table 4.9.5.2.2-1 of the generic procedure are performed.	–	–	–	–
14	The SS transmits an RRCReconfiguration message to establish SRB2 and DRB.	<–	NR RRC: RRCReconfiguration	–	–
15	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete	–	–
16	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 6?	–	–	2	–

8.1.1.3.3.3.3 Specific message contents

Table 8.1.1.3.3.3.3-1: RRCRelease (step 2, Table 8.1.1.3.3.3.2-3)

Derivation Path: TS 38.508 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
cellReselectionPriorities SEQUENCE {
freqPriorityListEUTRA	Not present
freqPriorityListNR SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR {	3 entries
FreqPriorityNR[1] SEQUENCE {		entry 1
carrierFreq	Same downlink ARFCN as used for NR Cell 1
cellReselectionPriority	4
cellReselectionSubPriority	Not present
}
FreqPriorityNR[2] SEQUENCE {		entry 2
carrierFreq	Same downlink ARFCN as used for NR Cell 3
cellReselectionPriority	5
cellReselectionSubPriority	Not present
}
FreqPriorityNR[3] SEQUENCE {		entry 3
carrierFreq	Same downlink ARFCN as used for NR Cell 6
cellReselectionPriority	1
cellReselectionSubPriority	Not present
}
}
}
}
}
}

Table 8.1.1.3.3.3.3-2: SIB4 for Cell 1 (preamble and all steps, Table 8.1.1.3.3.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo {	2 entries
InterFreqCarrierFreqInfo[1] SEQUENCE {		entry 1
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 3
cellReselectionPriority	1
}
InterFreqCarrierFreqInfo[2] SEQUENCE {		entry 2
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 6
cellReselectionPriority	5
}
}
}

Table 8.1.1.3.3.3.3-3: SIB4 for Cell 6 (all steps, Table 8.1.1.3.3.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo {	2 entries
InterFreqCarrierFreqInfo[1] SEQUENCE {		entry 1
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 1
cellReselectionPriority	4
}
InterFreqCarrierFreqInfo[2] SEQUENCE {		entry 2
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 3
cellReselectionPriority	1
}
}
}

Table 8.1.1.3.3.3.3-4: RRCRelease (step 6, Table 8.1.1.3.5.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
cellReselectionPriorities SEQUENCE {
freqPriorityListEUTRA	Not present
freqPriorityListNR SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR {	2 entries
FreqPriorityNR[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueNR of NR Cell 1
cellReselectionPriority	4
cellReselectionSubPriority	Not present
}
FreqPriorityNR[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueNR of NR Cell 6
cellReselectionPriority	3
cellReselectionSubPriority	Not present
}
}
t320	min5
}
}
}
}

Table 8.1.1.3.3.3.3-5: RRCReconfiguration message (step 3E and step 14, Table 8.1.1.3.1.3.2-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-SRB2-DRB (n, m)	38.508-1 [4] Table 4.8.1-4
nonCriticalExtension SEQUENCE {
masterCellGroup	CellGroupConfig-SRB2-DRB(n, m)	38.508-1 [4] Table 4.8.1-2B
}
}
}
}

Table 8.1.1.3.3.3.3-6: SIB4 for Cell 3 (all steps, Table 8.1.1.3.3.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo {	2 entries
InterFreqCarrierFreqInfo[1] SEQUENCE {		entry 1
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 1
t-ReselectionNR	1
}
InterFreqCarrierFreqInfo[2] SEQUENCE {		entry 2
dl-CarrierFreq	Same downlink NR ARFCN as used for NR Cell 3
}
}
}

8.1.1.3.4 RRC connection release / Success / With priority information / T320 expiry / E-UTRA

8.1.1.3.4.1 Test Purpose (TP)

(1)

with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListEUTRA with higher priority frequency }

ensure that {

when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority EUTRA frequency }

then { UE reselects the cell which belongs to the higher priority EUTRA frequency }

}

(2)

with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListEUTRA with higher priority frequency and timer T320 }

ensure that {

when { T320 timer expires }

}

8.1.1.3.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3 and T 38.304, clause 5.2.4.1. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.8.3]

The UE shall:

1> stop timer T380, if running;

1> stop timer T320, if running;

1> stop timer T390, if running;

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> if the RRCRelease message includes the cellReselectionPriorities:

2> store the cell reselection priority information provided by the cellReselectionPriorities;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

[TS 38.304, clause 5.2.4.1]

The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

The UE shall delete priorities provided by dedicated signalling when:

– the UE enters a different RRC state; or

– the optional validity time of dedicated priorities (T320) expires; or

– a PLMN selection is performed on request by NAS (TS 23.122 [9]).

NOTE 2: Equal priorities between RATs are not supported.

The UE shall not consider any black listed cells as candidate for cell reselection.

The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection.

NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.

[TS 38.331, clause 5.3.8.4]

The UE shall:

1> if T320 expires:

2> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT;

2> apply the cell reselection priority information broadcast in the system information.

[TS 38.304, clause 5.2.4.2]

Following rules are used by the UE to limit needed measurements:

– If the serving cell fulfils Srxlev> S_IntraSearchP and Squal > S_IntraSearchQ, the UE may choose not to perform intra-frequency measurements.

– Otherwise, the UE shall perform intra-frequency measurements.

– Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority according to TS 38.133 [8].

[TS 38.304, clause 5.2.4.5]

– A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > Thresh_{X, HighQ} during a time interval Treselection_RAT

Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– A cell of a higher priority RAT/ frequency fulfils Srxlev > Thresh_{X, HighP} during a time interval Treselection_RAT; and

– More than 1 second has elapsed since the UE camped on the current serving cell.

Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection as defined in sub-clause 5.2.4.6.

– The serving cell fulfils Squal < Thresh_{Serving, LowQ} and a cell of a lower priority NR or E-UTRAN RAT/ frequency fulfils Squal > Thresh_{X, LowQ} during a time interval Treselection_RAT.

Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

– The serving cell fulfils Srxlev < Thresh_{Serving, LowP} and a cell of a lower priority RAT/ frequency fulfils Srxlev > Thresh_{X, LowP}during a time interval Treselection_RAT; and

– More than 1 second has elapsed since the UE camped on the current serving cell.

Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria.

If more than one cell meets the above criteria, the UE shall reselect a cell as follows:

– If the highest-priority frequency is an NR frequency, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria according to clause 5.2.4.6;

– If the highest-priority frequency is from another RAT, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.

[TS 38.304, clause 5.2.4.6]

The cell-ranking criterion R_s for serving cell and R_n for neighbouring cells is defined by:

R_s = Q_meas,s +Q_hyst – Qoffset_temp

R_n = Q_meas,n -Qoffset – Qoffset_temp

where:

Q_meas

RSRP measurement quantity used in cell reselections.

Qoffset

For intra-frequency: Equals to Qoffset_s,n, if Qoffset_s,n is valid, otherwise this equals to zero.

For inter-frequency: Equals to Qoffset_s,n plus Qoffset_frequency, if Qoffset_s,n is valid, otherwise this equals to Qoffset_frequency.

Qoffset_temp

Offset temporarily applied to a cell as specified in TS 38.331 [3].

The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.

The cells shall be ranked according to the R criteria specified above by deriving Q_meas,nand Q_meas,sand calculating the R values using averaged RSRP results.

If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.

In all cases, the UE shall reselect the new cell, only if the following conditions are met:

– the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval Treselection_RAT;

– more than 1 second has elapsed since the UE camped on the current serving cell.

8.1.1.3.4.3 Test description

8.1.1.3.4.3.1 Pre-test conditions

System Simulator:

– NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3.

– NR Cell 1 is configured to operate in FR1 bands as defined in TS 38.508-1 [4] clause 6.2.3.

– System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell.

– System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

– With E-UTRA Cell 1 "Serving cell",E-UTRA Cell 3 "Non-suitable "Off" cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On), in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context established.

– the UE is switched-off.

– With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 3N-A, NR RRC_ CONNECTED, in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.2.2-2. 5G-GUTI and ngKSI are assigned and security context established.

– 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.1.3.4.3.2 Test procedure sequence

Table 8.1.1.3.4.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is 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.1.3.4.3.2-1: Time instances of cell power level and parameter changes in FR1

	Parameter	Unit	NR Cell 1	E-UTRA Cell 1	E-UTRA Cell 3	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	–	"off”	"off”
T0	SS/PBCH SSS EPRE	dBm/SCS	-88	–	–
T1	Cell-specific RS EPRE	dBm/15kHz	–	-73	-73	The power level values are assigned to satisfy both Thresh_{x, low} < Srxlev_{E-UTRACell 1} and Thresh_{x, high} <Srxlev_{E-UTRACell 3} but not to satisfy Srxlev_{NR Cell 1} < Thresh_{serving, low}
T1	SS/PBCH SSS EPRE	dBm/SCS	-88	–	–
T2	Cell-specific RS EPRE	dBm/15kHz	–	"off”	"off”	The power level values are assigned to satisfy Srxlev_{NR Cell 1}> S_{nonintrasearch}. (NOTE 1)
T2	SS/PBCH SSS EPRE	dBm/SCS	-88	–	–
T3	Cell-specific RS EPRE	dBm/15kHz	–	-73	"off”	The power level values are assigned to satisfy Thresh_{x, high} < Srxlev_{E-UTRA Cell 1}.
T3	SS/PBCH SSS EPRE	dBm/SCS	-88	–	–
NOTE 1: Power level “Off” is defined in TS36.508 [7] Table 6.2.2.1-3.

Table 8.1.1.3.4.3.2-2: Void

Table 8.1.1.3.4.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3 level according to the row "T1" in Table 8.1.1.3.4.3.2-1	–	–	–	–
2	The SS transmits an RRCRelease message including the freqPriorityListEUTRA on NR Cell 1.	<–	NR RRC: RRCRelease	–	–
2A	Check: Does the UE transmits an RRCConnectionRequest message on E-UTRA cell 3?	–>	RRC: RRCConnectionRequest	1	P
2B	SS transmits an RRCConnectionSetup message on E-UTRA cell 3.	<–	RRC: RRCConnectionSetup	–	–
2C	Check: Does the UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area?	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST	1	P
3	Void
3A	The SS transmits a SecurityModeCommand message.	<–	E-UTRA RRC: SecurityModeCommand	–	–
3B	The UE transmits a SecurityModeComplete message.	–>	E-UTRA RRC: SecurityModeComplete	–	–
3C-3D	Steps 5-6 of TS 38.508-1 [4] Table 4.9.7.2.2-1 of the generic procedure are performed.	–	–	–	–
3E	The SS transmits an RRCConnectionReconfiguration message to establish DRB #n	<–	E-UTRA RRC: RRCConnectionReconfiguration	–	–
3F	The UE transmits an RRCReconfigurationComplete message.	–>	E-UTRA RRC: RRCConnectionReconfigurationComplete	–	–
3G	Void	–	–	1	–
3GA	The SS sends one IP Packet to the UE on the default DRB associated with the first PDU session.	–	–	–	–
3GB	The UE loop backs the IP packet received in step 3GA.	–	–	1	P
3H	The SS transmits an RRConnectionRelease	<–	E-UTRA RRC: RRCConnectionRelease	–	–
4	The SS changes NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3 level according to the row "T2" in Table 8.1.1.3.4.3.2-1	–	–	–	–
5	UE perform on the NR Cell 1 the mobility and periodic registration update procedure in TS 38.508-1[4] subclause 4.9.9.2.2	–	–	–	–
5AA	The SS transmits an RRCReconfiguration message to establish SRB2 and DRB.	<–	NR RRC: RRCReconfiguration	–	–
5AB	The UE transmits an RRCReconfigurationComplete message.	–>	NR RRC: RRCReconfigurationComplete	–	–
5A	Void	–	–	1	–
5B	The SS sends one IP Packet to the UE on the default DRB associated with the first PDU session.	–	–	–	–
5C	The UE loop backs the IP packet received in step 5B.	–	–	1	P
6	The SS transmits an RRCRelease message containing IE freqPriorityListEUTRA to update the cell reselection priority of E-UTRA Cell 1 and the timer T320.	<–	NR RRC: RRCRelease	–	–
7	The SS changes power levels of NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3 according to row “T3” in Table 8.1.1.3.4.3.2-1.	–	–	–	–
8	Check: While timer T320 is running, does the UE transmit an RRCSetupRequest message?	–	–	2	F
9	Void	–	–	2	–
9A	Check: Does the UE transmits an RRCConnectionRequest message on E-UTRA cell 1?	–>	RRC: RRCConnectionRequest	2	P
9B	SS transmits an RRCConnectionSetup message on E-UTRA cell 1.	<–	RRC: RRCConnectionSetup	–	–
9C	Check: Does the UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area?	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST	2	P
10	The SS transmits a SecurityModeCommand message.	<–	E-UTRA RRC: SecurityModeCommand	–	–
11	The UE transmits a SecurityModeComplete message.	–>	E-UTRA RRC: SecurityModeComplete	–	–
12-13	Steps 5-6 of TS 38.508-1 [4] Table 4.9.7.2.2-1 of the generic procedure are performed.	–	–	–	–
14	The SS transmits an RRCConnectionReconfiguration message to establish DRB #n	<–	E-UTRA RRC: RRCConnectionReconfiguration	–	–
15	The UE transmits an RRCReconfigurationComplete message.	–>	E-UTRA RRC: RRCConnectionReconfigurationComplete	–	–
16	Void	–	–	2	–
16A	The SS sends one IP Packet to the UE on the default DRB associated with the first PDU session.	–	–	–	–
16B	The UE loop backs the IP packet received in step 16A.	–	–	2	P

8.1.1.3.4.3.3 Specific message contents

Table 8.1.1.3.4.3.3-1: RRCRelease (step 1, Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
cellReselectionPriorities SEQUENCE {
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA {	2 entries
freqPriorityListEUTRA[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueEUTRA for EUTRA Cell 1 frequency
cellReselectionPriority	3
cellReselectionSubPriority	Not present
}
freqPriorityListEUTRA[1] SEQUENCE {		entry 2
carrierFreq	ARFCN-ValueEUTRA for EUTRA Cell 3 frequency
cellReselectionPriority	5
cellReselectionSubPriority	Not present
}
}
freqPriorityListNR SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR {	1 entry
FreqPriorityNR[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueNR for NR Cell 1 frequency
cellReselectionPriority	4
cellReselectionSubPriority	Not present
}
}
t320	Not Present
}
}
}
}

Table 8.1.1.3.4.3.3-2: SIB5 for NR cell 1 (preamble and all steps, Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.2-4
Information Element	Value/remark	Comment	Condition
SIB5 ::= SEQUENCE {
carrierFreqListEUTRA SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA {	2 entries
CarrierFreqEUTRA[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueEUTRA for EUTRA Cell 1 frequency
cellReselectionPriority	5
}
CarrierFreqEUTRA[2] SEQUENCE {		entry 2
carrierFreq	ARFCN-ValueEUTRA for EUTRA Cell 3 frequency
cellReselectionPriority	3
}
}
}

Table 8.1.1.3.4.3.3-3: RRCRelease (step 6, Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
cellReselectionPriorities SEQUENCE {
freqPriorityListEUTRA SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA {	1 entry
freqPriorityListEUTRA[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueEUTRA of E-UTRA Cell 1
cellReselectionPriority	3
cellReselectionSubPriority	Not present
}
}
freqPriorityListNR SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR {	1 entry
FreqPriorityNR[1] SEQUENCE {		entry 1
carrierFreq	ARFCN-ValueNR for NR Cell 1 frequency
cellReselectionPriority	4
cellReselectionSubPriority	Not present
}
}
t320	min5
}
}
}
}

Table 8.1.1.3.4.3.3-4: RRCConnectionReconfiguration (steps 3E and 14 Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 36.508[7] Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-DRB(n, m)
}
}
}
}

Table 8.1.1.3.4.3.3-5: RRCReconfiguration-SRB2-DRB (n, m) (step 5AA, Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.8.1-1B

Table 8.1.1.3.4.3.3-6: REGISTRATION REQUEST (Step 5, Table 8.1.1.3.4.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6.
Information Element	Value/remark	Comment	Condition
EPS NAS message container	TRACKING AREA UPDATE REQUEST message	See Table 8.1.1.3.4.3.3-7

Table 8.1.1.3.4.3.3-7: TRACKING AREA UPDATE REQUEST (Table 8.1.1.3.4.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-2 with condition Mapped EPS security context

8.1.1.3.5 Void

8.1.1.3.6 Void

8.1.1.3.7 RRC connection release / Success / Deprioritisation / Frequency / T325 expiry

8.1.1.3.7.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCRelease message including IE deprioritisationReq with deprioritisationType indicating ‘frequency’ and a deprioritisationTimer }

then { UE considers the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running }

}

8.1.1.3.7.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3 and TS 38.304 clause 5.2.4.1.

[TS 38.331, clause 5.3.8.3]

…

The UE shall:

1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

[TS 38.304, clause 5.2.4.1]

…

8.1.1.3.7.3 Test Description

8.1.1.3.7.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 and NR Cell 3 have different tracking areas and equal priority.

– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.

UE:

– None.

Preamble:

– The UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

8.1.1.3.7.3.2 Test procedure sequence

Table 8.1.1.3.7.3.2-1 illustrates the downlink power levels to be applied for NR Cell 1, Cell 2 and Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1" and "T2" 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.1.3.7.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-88	Off
T1	SS/PBCH SSS EPRE	dBm/SCS	-85	-91	The power level values are set so that R_{NRCell 1} > R_{NRCell 3}.

Table 8.1.1.3.7.3.2-2: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS
T1	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS	The power level values are set so that R_{NRCell 1} > R_{NRCell 3}.

Table 8.1.1.3.7.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCRelease message on NR Cell 1 including IE deprioritisationReq.	<–	NR RRC: RRCRelease	–	–
2	SS starts timer T325.	–	–	–	–
2A	The SS adjusts the SS/PBCH EPRE levels according to row "T1" in table 8.1.1.3.7.2-1/2	–	–	–	–
3	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 indicate that the UE is camped on NR Cell 3?	–	–	1	P
4	SS waits for T325 expiry.	–	–	–	–
5	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 indicate that the UE is camped on NR Cell 1?	–	–	1	P

8.1.1.3.7.3.3 Specific message contents

Table 8.1.1.3.7.3.3-1: RRCRelease (step 1, Table 8.1.1.3.7.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
deprioritisationReq SEQUENCE {
deprioritisationType	frequency
deprioritisationTimer	min5
}
}
}
}

8.1.1.3.7a RRC connection release / Success / Deprioritisation / NR / T325 expiry

8.1.1.3.7a.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state }

ensure that {

when { UE receives an RRCRelease message including IE deprioritisationReq with deprioritisationType indicating ‘nr’ and a deprioritisationTimer }

then { UE considers all frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running }

}

8.1.1.3.7a.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3 and TS 38.304 clause 5.2.4.1.

[TS 38.331, clause 5.3.8.3]

…

The UE shall:

1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

[TS 38.304, clause 5.2.4.1]

…

8.1.1.3.7a.3 Test Description

8.1.1.3.7a.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 and NR Cell 3 have different tracking areas and equal priority.

– E-UTRA Cell 1 is a lower priority cell.

– System information combination NR-7 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.

– System information combination 31 as defined in TS 36.508-1 [18] clause 4.4.3.1 is used in E-UTRA Cell.

UE:

– None.

Preamble:

– 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.

8.1.1.3.7a.3.2 Test procedure sequence

Table 8.1.1.3.7a.3.2-1 illustrates the downlink power levels to be applied for NR Cell 1, 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, while rows marked "T1" and "T2" 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.1.3.7a.3.2-1: Time instances of cell power level and parameter changes for conducted test environment

	Parameter	Unit	NR Cell 1	NR Cell 3	E-UTRA Cell 1	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-88	Off	–
T0	Cell-specific RS EPRE	dBm/15kHz	–	–	Off
T1	SS/PBCH SSS EPRE	dBm/SCS	-85	-79	–	The power level values are assigned to satisfy Srxlev_{E-UTRA Cell 1}> Thresh_{x, high}
T1	Cell-specific RS EPRE	dBm/15kHz	–	–	-75

Table 8.1.1.3.7a.3.2-2: Time instances of cell power level and parameter changes for OTA test envoirnment

	Parameter	Unit	NR Cell 1	NR Cell 3	E-UTRA Cell 1	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS	–
T0	Cell-specific RS EPRE	dBm/15kHz	–	–	Off
T1	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS	–	The power level values are assigned to satisfy Srxlev_{E-UTRA Cell 1}> Thresh_{x, high}
T1	Cell-specific RS EPRE	dBm/15kHz	–	–	-75

Table 8.1.1.3.7a.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS adjusts the SS/PBCH EPRE levels according to row "T1" in table 8.1.1.3.7a.3.2-1/2	–	–	–	–
2	The SS transmits an RRCRelease message on NR Cell 1 including IE deprioritisationReq.	<–	NR RRC: RRCRelease	–	–
3	SS starts timer T325.	–	–	–	–
4	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.7.2.2-1 is performed and the UE is camped on E-UTRAN Cell 1?	–	–	1	P
5	SS waits for T325 expiry.	–	–	–	–
6	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.9.2.2-1 indicate that the UE is camped on NR Cell 3?	–>	NR RRC: RRCSetupRequest	1	P

8.1.1.3.7a.3.3 Specific message contents

Table 8.1.1.3.7a.3.3-1: RRCRelease (step 2, Table 8.1.1.3.7a.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
deprioritisationReq SEQUENCE {
deprioritisationType	nr
deprioritisationTimer	min5
}
}
}
}

8.1.1.3.7b RRC connection release / Success / Deprioritisation / Deletion of Stored deprioritisation request

8.1.1.3.7b.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state and T325 is running}

ensure that {

when { UE is requested to perform manual PLMN selection }

then { UE deletes the stored deprioritisation request(s) and proceeds with the PLMN selection }

}

8.1.1.3.7b.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3 and TS 38.304 clause 5.2.4.1.

[TS 38.331, clause 5.3.8.3]

…

The UE shall:

1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

[TS 38.304, clause 5.2.4.1]

…

8.1.1.3.7b.3 Test Description

8.1.1.3.7b.3.1 Pre-test conditions

System Simulator:

– 2 NR cells: NR Cells 1 and 3 as specified in TS 38.508-1 [4] table 6.3.2.2-1 are configured as shown in Table 8.1.1.3.7b.3.1–1. PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-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.

Table 8.1.1.3.7b.3.1-1: PLMN identifiers

NR Cell	PLMN identifiers

NR Cell 1	PLMN1
NR Cell 3	PLMN2

UE:

– None.

Preamble:

– 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.

8.1.1.3.7b.3.2 Test procedure sequence

Table 8.1.1.3.7b.3.2-1 illustrates the downlink power levels to be applied for NR Cell 1, Cell 2 and Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1" and "T2" 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.1.3.7b.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	-88	Off
T1	SS/PBCH SSS EPRE	dBm/SCS	-85	-91	The power level values are set so that R_{NRCell 1} > R_{NRCell 3}.

Table 8.1.1.3.7b.3.2-2: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	NR Cell 3	Remark
T0	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS
T1	SS/PBCH SSS EPRE	dBm/SCS	FFS	FFS

Table 8.1.1.3.7b.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS adjusts the SS/PBCH EPRE levels according to row "T1" in table 8.1.1.3.7b.2-1/2.	–	–	–	–
2	The SS transmits an RRCRelease message on NR Cell 1 including IE deprioritisationReq.	<–	NR RRC: RRCRelease	–	–
3	SS starts timer T325.	–	–	–	–
4	PLMN2 is manually selected.
5	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 indicate that the UE is camped on NR Cell 3?	–>	NR RRC: RRCSetupRequest	–	–
6	PLMN1 is manually selected before T325 expiry.	–	–	–	–
7	Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 indicate that the UE is camped on NR Cell 1 before T325 expiry?	–>	NR RRC: RRCSetupRequest	1	P

8.1.1.3.7b.3.3 Specific message contents

Table 8.1.1.3.7b.3.3-1: RRCRelease (step 2, Table 8.1.1.3.7b.3.2-3)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
deprioritisationReq SEQUENCE {
deprioritisationType	frequency
deprioritisationTimer	min5
}
}
}
}

8.1.1.4 RRC resume

8.1.1.4.1 RRC resume / Suspend-Resume / RNA update / Success / Short message for SI update

8.1.1.4.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_INACTIVE state, with stored shortI-RNTI and useFullResumeID is not signalled in SIB1 }

ensure that {

when { UE receives a Paging message to resume RRC connection }

then { UE sends RRCResumeRequest message by setting resumeIdentity to the stored shortI-RNTI value }

}

(2)

with { UE in NR RRC_INACTIVE state, with stored fullI-RNTI and useFullResumeID is signalled in SIB1 }

ensure that {

when { UE receives a Paging message to resume RRC connection }

then { UE sends RRCResumeRequest1 message by setting resumeIdentity to the stored fullI-RNTI value }

}

(3)

with { UE in NR RRC_INACTIVE state }

ensure that {

when { UE performs cell reselection and enters an RNA not belonging to the configured ran-NotificationAreaInfo }

then { UE shall initiate RRC connection resume procedure with cause value set to rna-Update }

}

(4)

with { UE in NR RRC_INACTIVE state }

ensure that {

when { UE receives a short message transmitted on PDCCH using P-RNTI indicating a systemInfoModification }

then { UE re-acquires and applies the new system information about the correct prach-ConfigurationIndex in random access to resume RRC connection }

}

8.1.1.4.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.2.2.2.2, 5.2.2.3.1, 5.2.2.4.2, 5.3.8.3, 5.3.13.2, 5.3.13.3, 5.3.13.8 and 6.5. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.2.2.2.2]

A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS and positioning assistance data) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period. SI change indication is not applicable for SI messages containing posSIBs.

UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for SI change indication in its own paging occasion every DRX cycle. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13.

…

If the UE receives a Short Message, the UE shall:

…

1> if the systemInfoModification bit of Short Message is set:

2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification period.

[TS 38.331, clause 5.2.2.3.1]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

1> if the UE is in RRC_CONNECTED while T311 is running:

2> acquire the MIB, which is scheduled as specified in TS 38.213 [13];

2> if the UE is unable to acquire the MIB;

3> perform the actions as specified in clause 5.2.2.5;

2> else:

3> perform the actions specified in clause 5.2.2.4.1.

…

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

1> if the UE is in RRC_CONNECTED while T311 is running:

2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]) and if SIB1 acquisition is required for the UE:

3> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];

3> if the UE is unable to acquire the SIB1:

4> perform the actions as specified in clause 5.2.2.5;

3> else:

4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2.

2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled in the cell:

3> perform the actions as specified in clause 5.2.2.5.

…

[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> else:

…

2> if the UE supports the bandwidth of the initial uplink BWP and of the initial downlink BWPs indicated in the locationAndBandwidth fields in uplinkConfigCommon:

3> select the first frequency band in the frequencyBandList which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;

3> forward the cellIdentity to upper layers;

3> if trackingAreaCode is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list:

4> consider the cell as barred in accordance with TS 38.304 [20];

4> if intraFreqReselection is set to notAllowed:

5> consider cell re-selection to other cells on the same frequency as the barred cell as not allowed, as specified in TS 38.304 [20];

4> else:

5> consider cell re-selection to other cells on the same frequency as the barred cell as allowed, as specified in TS 38.304 [20];

3> else:

4> forward the trackingAreaCode to upper layers;

3> forward the PLMN identity to upper layers;

3> if in RRC_INACTIVE and the forwarded information does not trigger message transmission by upper layers:

4> if the serving cell does not belong to the configured ran-NotificationAreaInfo:

5> initiate an RNA update as specified in 5.3.13.8;

[TS 38.331, clause 5.3.8.3]

The UE shall:

…

1> if the RRCRelease includes suspendConfig:

2> apply the received suspendConfig;

2> reset MAC and release the default MAC Cell Group configuration, if any;

2> re-establish RLC entities for SRB1;

2> if the RRCRelease message with suspendConfig was received in response to an RRCResumeRequest or an RRCResumeRequest1:

3> stop the timer T319 if running;

3> in the stored UE Inactive AS context:

4> replace the K_gNB and K_RRCint keys with the current K_gNB and K_RRCint keys;

4> replace the C-RNTI with the temporary C-RNTI in the cell the UE has received the RRCRelease message;

4> replace the cellIdentity with the cellIdentity of the cell the UE has received the RRCRelease message;

4> replace the physical cell identity with the physical cell identity of the cell the UE has received the RRCRelease message;

4> replace the suspendConfig with the current suspendConfig;

2> else:

3> store in the UE Inactive AS Context the configured suspendConfig, the current K_gNB and K_RRCintkeys, the ROHC state, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, and all other parameters configured except with ReconfigurationWithSync;

…

[TS 38.331, clause 5.3.13.2]

The UE initiates the procedure when upper layers or AS (when responding to RAN paging or upon triggering RNA updates while the UE is in RRC_INACTIVE) requests the resume of a suspended RRC connection.

The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.

Upon initiation of the procedure, the UE shall:

1> if the resumption of the RRC connection is triggered by response to NG-RAN paging:

2> select ‘0’ as the Access Category;

2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> else if the resumption of the RRC connection is triggered by upper layers:

2> if the upper layers provide an Access Category and one or more Access Identities:

3> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers;

4> if the access attempt is barred, the procedure ends;

2> set the resumeCause in accordance with the information received from upper layers;

1> else if the resumption of the RRC connection is triggered due to an RNA update as specified in 5.3.13.8:

2> if an emergency service is ongoing:

NOTE: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation.

3> select ‘2’ as the Access Category;

3> set the resumeCause to emergency;

2> else:

3> select ‘8’ as the Access Category;

2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501 [23];

3> if the access attempt is barred:

4> set the variable pendingRnaUpdate to true;

4> the procedure ends;

…

1> release the MCG SCell(s) from the UE Inactive AS context, if stored;

1> apply the default L1 parameter values as specified in corresponding physical layer specifications, except for the parameters for which values are provided in SIB1;

1> apply the default SRB1 configuration as specified in 9.2.1;

1> apply the default MAC Cell Group configuration as specified in 9.2.2;

1> release delayBudgetReportingConfig from the UE Inactive AS context, if stored;

1> stop timer T342, if running;

1> release overheatingAssistanceConfig from the UE Inactive AS context, if stored;

1> stop timer T345, if running;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SIB1;

1> start timer T319;

1> set the variable pendingRnaUpdate to false;

1> initiate transmission of the RRCResumeRequest message or RRCResumeRequest1 in accordance with 5.3.13.3.

[TS 38.331, clause 5.3.13.3]

The UE shall set the contents of RRCResumeRequest or RRCResumeRequest1 message as follows:

1> if field useFullResumeID is signalled in SIB1:

2> select RRCResumeRequest1 as the message to use;

2> set the resumeIdentity to the stored fullI-RNTI value;

1> else:

2> select RRCResumeRequest as the message to use;

2> set the resumeIdentity to the stored shortI-RNTI value;

…

1> submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to lower layers.

NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering.

…

[TS 38.331, clause 5.3.13.8]

In RRC_INACTIVE state, the UE shall:

1> if T380 expires; or

1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2:

2> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to rna-Update;

1> if barring is alleviated for Access Category ‘8’, as specified in 5.3.14.4:

2> if upper layers do not request RRC the resumption of an RRC connection, and

2> if the variable pendingRnaUpdate is set to true:

3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause value set to rna-Update.

If the UE in RRC_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited service as defined in TS 38.304 [20], the UE shall:

1> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘other’.

NOTE: It is left to UE implementation how to behave when T380 expires while the UE is camped neither on a suitable nor on an acceptable cell.

[TS 38.331, clause 6.5]

Short Messages can be transmitted on PDCCH using P-RNTI with or without associated Paging message using Short Message field in DCI format 1_0 (see TS 38.212 [17], clause 7.3.1.2.1).

Table 6.5-1 defines Short Messages. Bit 1 is the most significant bit.

Table 6.5-1: Short Messages

Bit	Short Message
1	*systemInfoModification* If set to 1: indication of a BCCH modification other than SIB6, SIB7 and SIB8.
2	*etwsAndCmasIndication* If set to 1: indication of an ETWS primary notification and/or an ETWS secondary notification and/or a CMAS notification.
3	*stopPagingMonitoring* This bit can be used for only operation with shared spectrum channel access and if nrofPDCCH-MonitoringOccasionPerSSB-InPO is present. If set to 1: indication that the UE may stop monitoring PDCCH occasion(s) for paging in this Paging Occasion as specified in TS 38.304 [20], clause 7.1.
4 – 8	Not used in this release of the specification, and shall be ignored by UE if received.

8.1.1.4.1.3 Test Description

8.1.1.4.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the serving cell and NR Cell 2 is a suitable neighbour intra-frequency cell.

– Cell power levels are selected according to 38.508-1 [4] Table 6.2.2.1-3 and NR Cell 2 is switched on after UE has registered on NR Cell 1.

– System information combination NR-2 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 2N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

– Else, the UE is in 5GS state 2N-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.1.4.1.3.2 Test procedure sequence

Table 8.1.1.4.1.3.2-1 for FR1 and table 8.1.1.4.1.3.2-2 for FR2 illustrate the downlink power levels to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently in the Main behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.1.1.4.1.3.2-1: Cell configuration changes over time for FR1

Parameter

Unit

NR Cell 1

NR Cell 2

Remarks

SS/PBCH

SSS EPRE

dBm/SCS

-88

-94

SS/PBCH

SSS EPRE

dBm/SCS

"Off"

-94

Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3

Table 8.1.1.4.1.3.2-2: Cell configuration changes over time for FR2

	Parameter	Unit	NR Cell 1	NR Cell 2	Remarks
T0	SS/PBCH SSS EPRE	dBm/SCS	-82	-91
T0	Qrxlevmin	dBm	-110+Delta(NRf1)	-110+Delta(NRf1)
T1	SS/PBCH SSS EPRE	dBm/SCS	"Off"	-91	Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2
T1	Qrxlevmin	dBm	–	-110+Delta(NRf1)

Table 8.1.1.4.1.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	The following messages are to be observed on NR Cell 1 unless explicitly stated otherwise	–	–	–	–
1	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
2	Check: Does the UE transmit an RRCResumeRequest message by setting resumeIdentity to the stored shortI-RNTI value?	–>	NR RRC: RRCResumeRequest	1	P
3	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
4	The UE transmits an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–
5	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 default Internet PDU session?	–	–	1	–
6	The SS transmits an RRCRelease message including both fullI-RNTI and shortI-RNTI in suspendConfig.	<–	NR RRC: RRCRelease	–	–
7	The SS changes the SIB1 of NR Cell 1 to set the useFullResumeID to True.	–	–	–	–
8	The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification.	<–	PDCCH (DCI 1_0): Short Message	–	–
9	Wait for 2.1* modification period second for the UE to receive new system information. (Note 1)	–	–	–	–
10	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
11	Check: Does the UE transmit an RRCResumeRequest1 message by setting resumeIdentity to the stored fullI-RNTI value?	–>	NR RRC: RRCResumeRequest1	2	P
12	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
13	The UE transmits an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–
14	The SS transmits an RRCRelease message including both fullI-RNTI and shortI-RNTI in suspendConfig.	<–	NR RRC: RRCRelease	–	–
15	The SS adjusts cell levels according to row T1 of table 8.1.1.4.1.3.2-1 for FR1 and table 8.1.1.4.1.3.2-2 for FR2.	–	–	–	–
–	The following messages are to be observed on NR Cell 2 unless explicitly stated otherwise.	–	–	–	–
16	Check: Does the UE transmit an RRCResumeRequest message with resumeCause set to rna-Update on NR Cell 2 within 60s?	–>	NR RRC: RRCResumeRequest	3	P
17	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
18	The UE transmit an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–
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 default Internet PDU session?	–	–	3	–
20	The SS transmits an RRCRelease message including both fullI-RNTI and shortI-RNTI in suspendConfig.	<–	NR RRC: RRCRelease	–	–
21-22	Void	–	–	–	–
22A	The SS changes the prach-ConfigurationIndex and ra-responseWindow in the system information.	–	–	–	–
22B	The SS transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification.	–	PDCCH (DCI 1_0): Short Message	–	–
23	Wait for 2.1* modification period second for the UE to receive new system information. (Note 1)	–	–	–	–
24	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	–	NR RRC: Paging	–	–
25	Check: Does the UE transmit a random access using prach-ConfigurationIndex given in step 22?	–	–	4	P
26	The UE transmits an RRCResumeRequest message.	–>	RRCResumeRequest	–	–
27	The SS transmits an RRCResume message.	<–	RRCResume	–	–
28	The UE transmits an RRCResumeComplete message.	–>	RRCResumeComplete	–	–
Note 1: The modification period, expressed in number of radio frames = modificationPeriodCoeff * defaultPagingCycle.

8.1.1.4.1.3.3 Specific message contents

Table 8.1.1.4.1.3.3-1: Paging (step 1, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME

Table 8.1.1.4.1.3.3-2: RRCRelease (step 6, 13, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-16 with condition NR_RRC_INACTIVE

Table 8.1.1.4.1.3.3-3: SIB1 (step 7, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
useFullResumeID	true
}

Table 8.1.1.4.1.3.3-4: Paging (step 10 and 24, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME

Table 8.1.1.4.1.3.3-5: RRCResumeRequest (step 16, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-19
Information Element	Value/remark	Comment	Condition
RRCResumeRequest ::= SEQUENCE {
rrcResumeRequest SEQUENCE {
resumeCause	rna-Update
}
}

Table 8.1.1.4.1.3.3-6: RRCResume (step 3, 12, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-17

Table 8.1.1.4.1.3.3-7: Void

Table 8.1.1.4.1.3.3-8: RRCResume (step 17, Table 8.1.1.4.1.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCResume ::= SEQUENCE {
criticalExtensions CHOICE {
rrcResume SEQUENCE {
masterCellGroup := SEQUENCE {	CellGroupConfig	Table 8.1.1.4.1.3.3-10
}
}
}

Table 8.1.1.4.1.3.3-9: Void

Table 8.1.1.4.1.3.3-10: CellGroupConfig (Table 8.1.1.4.1.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition RESUME
Information Element	Value/remark	Comment	Condition
CellGroupConfig ::= SEQUENCE {
spCellConfigDedicated	ServingCellConfig
}

Table 8.1.1.4.1.3.3-11: ServingCellConfig (Table 8.1.1.4.1.3.3-10: CellGroupConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 with condition RESUME
Information Element	Value/remark	Comment	Condition
ServingCellConfig ::= SEQUENCE {
initialDownlinkBWP	BWP-DownlinkDedicated
}

Table 8.1.1.4.1.3.3-12: BWP-DownlinkDedicated (Table 8.1.1.4.1.3.3-11: ServingCellConfig)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-11
Information Element	Value/remark	Comment	Condition
BWP-DownlinkDedicated ::= SEQUENCE {
pdcch-Config	Not present
pdsch-Config CHOICE {
setup	PDSCH-Config
}
}

Table 8.1.1.4.1.3.3-13: PDSCH-Config (Table 8.1.1.4.1.3.3-12: BWP-DownlinkDedicated)

Derivation Path: TS 38.508-1 [4], Table 4.6.3-100
Information Element	Value/remark	Comment	Condition
PDSCH-Config ::= SEQUENCE {
dmrs-DownlinkForPDSCH-MappingTypeA	Not present
tci-StatesToAddModList SEQUENCE(SIZE (1.. maxNrofTCI-States)) OF TCI-State {	1 entry
TCI-State[1] SEQUENCE {		entry 1
tci-StateId	0
qcl-type1 SEQUENCE {
referenceSignal CHOICE {
ssb	SSB index #n	SSB index of NR Cell 2
}
}
}
}
}

Table 8.1.1.4.1.3.3-14: SIB1 (step 22A, Table 8.1.1.4.1.3.2-3)

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 {
prach-ConfigurationIndex	91		FR1
prach-ConfigurationIndex	156		FR2
ra-ResponseWindow	sl20
}
}
}
}
}
}

Condition	Explanation
FR1	410 MHz – 7125 MHz
FR2	24250 MHz – 52600 MHz

8.1.1.4.2 RRC resume / Suspend-Resume / RRC setup / T319 expiry

8.1.1.4.2.1 Test Purpose (TP)

(1)

with { UE in NR RRC_INACTIVE state and sends RRCResumeRequest message to resume RRC Connection }

ensure that {

when { UE receives a RRCSetup message }

then { UE shall discards any stored UE Inactive AS context, suspendConfig and send RRCSetupComplete message with ng-5G-S-TMSI-Value set to ng-5G-S-TMSI }

}

(2)

with { UE in NR RRC_INACTIVE state and sends RRCResumeRequest message to resume RRC Connection }

ensure that {

when { T319 expires }

then { UE shall release RRC connection with release cause RRC Resume failure and go to NR RRC_IDLE state }

}

8.1.1.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.3.3.4, 5.3.11, 5.3.13.5 and 5.3.13.7 and TS 24.501 clause 5.3.1.4. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, clause 5.3.3.4]

The UE shall perform the following actions upon reception of the RRCSetup:

…

1> if the RRCSetup is received in response to an RRCResumeRequest or RRCResumeRequest1:

2> discard any stored UE Inactive AS context and suspendConfig;

2> discard any current AS security context including the K_RRCenc key, the K_RRCint key, the K_UPint key and the K_UPenc key;

2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the associated PDCP entities and of SDAP;

2> release the RRC configuration except for the default MAC Cell Group configuration and CCCH configuration;

2> indicate to upper layers fallback of the RRC connection;

2> stop timer T380, if running;

1> perform the cell group configuration procedure in accordance with the received masterCellGroup and as specified in 5.3.5.5;

1> perform the radio bearer configuration procedure in accordance with the received radioBearerConfig and as specified in 5.3.5.6;

1> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT;

1> stop timer T300, T301 or T319 if running;

1> if T390 is running:

2> stop timer T390 for all access categories;

2> perform the actions as specified in 5.3.14.4.

1> stop timer T302, if running;

1> stop timer T320, if running;

1> if the RRCSetup is received in response to an RRCResumeRequest, RRCResumeRequest1 or RRCSetupRequest:

2> enter RRC_CONNECTED;

2> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> set the content of RRCSetupComplete message as follows:

2> if upper layers provide an 5G-S-TMSI:

3> if the RRCSetup is received in response to an RRCSetupRequest:

4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2;

3> else:

4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI;

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (TS 24.501 [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1;

2> if upper layers provide the ‘Registered AMF’:

3> include and set the registeredAMF as follows:

4> if the PLMN identity of the ‘Registered AMF’ is different from the PLMN selected by the upper layers:

5> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the ‘Registered AMF’ received from upper layers;

4> set the amf-Identifier to the value received from upper layers;

3> include and set the guami-Type to the value provided by the upper layers;

2> if upper layers provide one or more S-NSSAI (see TS 23.003 [21]):

3> include the s-nssai-List and set the content to the values provided by the upper layers;

2> set the dedicatedNAS-Message to include the information received from upper layers;

1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends

[TS 38.331, clause 5.3.11]

UE shall:

1> reset MAC;

1> if T302 is running:

2> stop timer T302;

2> perform the actions as specified in 5.3.14.4;

1> stop all timers that are running except T320 and T325;

1> discard the UE Inactive AS context;

1> set the variable pendingRnaUpdate to false, if that is set to true;

1> discard the K_gNB, the K_RRCenc key, the K_RRCint, the K_UPint key and the K_UPenc key, if any;

1> release all radio resources, including release of the RLC 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> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20], except if going to RRC_IDLE was triggered by selecting an inter-RAT cell while T311 was running;

[TS 38.331, clause 5.3.13.5]

The UE shall:

1> if timer T319 expires or upon receiving Integrity check failure indication from lower layers while T319 is running:

2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ‘RRC Resume failure’.

[TS 38.331, clause 5.3.13.7]

The UE shall:

1> perform the RRC connection setup procedure as specified in 5.3.3.4.

[TS 24.501, clause 5.3.1.4]

…

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the resumption of the RRC connection has failed, and:

a) if the lower layers indicate that access barring is applicable for all access categories except categories 0 and 2, the UE shall:

1) stay in 5GMM-CONNECTED mode with RRC inactive indication;

b) else, the UE shall:

1) enter 5GMM-IDLE mode; and

2) initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for N1 NAS signalling connection recovery as specified in subclause 5.5.1.3.2.

NOTE 2: An indication from the lower layer that the RRC connection has been released with cause "RRC resume failure" can be considered as an indication that the resumption of the RRC connection has failed.

8.1.1.4.2.3 Test description

8.1.1.4.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the serving cell.

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in state 2N-A as defined in TS 38.508-1 [4], Table 4.4A.2-2 on NR Cell 1.

8.1.1.4.2.3.2 Test procedure sequence

Table 8.1.1.4.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
2	The UE transmit an RRCResumeRequest message to resume RRC Connection by setting resumeIdentity to the stored shortI-RNTI value?	–>	NR RRC: RRCResumeRequest	–	–
3	The SS transmits an RRCSetup message in response to RRCResumeRequest message.	<–	NR RRC: RRCSetup	–	–
4	Check: Does the UE transmits an RRCSetupComplete message and a REGISTRATION REQUEST message by discarding any stored UE Inactive AS context and suspendConfig, setting the ng-5G-S-TMSI-Value to ng-5G-S-TMSI?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	1	P
4A-4B	Steps 4-5 as defined in TS 38.508-1 [4] Table 4.9.5.2.2-1.	–	–	–	–
4C-4F	Steps 5-8 as defined in TS 38.508-1 [4] Table Table 4.5.4.2-3.	–	–	–	–
5	The SS transmits an RRCRelease message including both fullI-RNTI and shortI-RNTI in suspendConfig.	<–	NR RRC: RRCRelease	–	–
6	The SS transmits a Paging message including a matched identities (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
7	The UE transmits an RRCResumeRequest message to resume RRC Connection by setting resumeIdentity to the stored shortI-RNTI value?	–>	NR RRC: RRCResumeRequest	–	–
8	The SS waits for T319 expiry.	–	–	–	–
9	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?	–	–	2	–

8.1.1.4.2.3.3 Specific message contents

Table 8.1.1.4.2.3.3-1: RRCRelease (preamble and step 5 in Table 8.1.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease SEQUENCE {
suspendConfig SEQUENCE {			NR_RRC_INACTIVE
fullI-RNTI	I-RNTI-Value
shortI-RNTI	ShortI-RNTI-Value
}
}
}
}

Table 8.1.1.4.2.3.3-1a: Void

Table 8.1.1.4.2.3.3-2: RRCResumeRequest (step 2 and 7 Table 8.1.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-19
Information Element	Value/remark	Comment	Condition
RRCResumeRequest ::= SEQUENCE {
rrcResumeRequest SEQUENCE {
resumeCause	mt-Access
}
}

Table 8.1.1.4.2.3.3-3: RRCSetupComplete (step 4 in Table 8.1.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-22
Information Element	Value/remark	Comment	Condition
RRCSetupComplete::= SEQUENCE {
criticalExtensions CHOICE {
rrcSetupComplete SEQUENCE {
ng-5G-S-TMSI-Value	ng-5G-S-TMSI
}
}
}

Table 8.1.1.4.2.3.3-4: REGISTRATION REQUEST (step 4 in Table 8.1.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type
5GS registration type value	‘010’B	Mobility registration updating
Uplink data status	Present but contents not checked

Table 8.1.1.4.2.3.3-5: RRCReconfiguration (step 4E in Table 8.1.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 condition NR and SRB2
Information Element	Value/remark	Comment	Condition
RRCReconfiguration ::= SEQUENCE {
dedicatedNAS-MessageList	Not present
}

8.1.1.4.3 Void

8.1.1.4.4 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Intra-band Contiguous CA

8.1.1.4.4.1 Test Purpose (TP)

FFS

8.1.1.4.4.2 Conformance requirements

FFS

8.1.1.4.4.3 Test description

8.1.1.4.4.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell, NR Cell 3 is the SCell.

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell.

UE:

– None.

Preamble:

– The UE is in state 2N-A as defined in TS 38.508-1 [4], Table 4.4A.2-2 on NR Cell 1.

8.1.1.4.4.3.2 Test procedure sequence

Table 8.1.1.4.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
2	Check: Does the UE transmit an RRCResumeRequest message by setting resumeIdentity to the stored shortI-RNTI value?	–>	NR RRC: RRCResumeRequest	1	P
3	The SS transmits an RRCResume message.	<–	NR RRC: RRCResume	–	–
4	The UE transmits an RRCResumeComplete message.	–>	NR RRC: RRCResumeComplete	–	–

FFS

8.1.1.4.4.3.3 Specific message contents

Table 8.1.1.4.4.3.3-1: Paging (step 1, Table 8.1.1.4.4.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME

Table 8.1.1.4.4.3.3-2: RRCResume (step 3, Table 8.1.1.4.4.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCResume ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcResume SEQUENCE {
masterCellGroup	CellGroupConfig with condition RESUME and SCell_add
}
}
}

Table 8.1.1.4.4.3.3-3: CellGroupConfig (Table 8.1.1.4.4.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
sCellState-r16	activated
}
}
}

FFS

8.1.1.4.5 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Intra-band non-Contiguous CA

8.1.1.4.5.1 Test Purpose (TP)

Same as TC 8.1.1.4.4 but applied to Intra-band non-Contiguous CA.

8.1.1.4.5.2 Conformance requirements

Same as TC 8.1.1.4.4 but applied to Intra-band non-Contiguous CA.

8.1.1.4.5.3 Test description

8.1.1.4.5.3.1 Pre-test conditions

Same as TC 8.1.1.4.4 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

8.1.1.4.5.3.2 Test procedure sequence

Same as TC 8.1.1.4.4 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

8.1.1.4.6 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Inter-band CA

8.1.1.4.6.1 Test Purpose (TP)

Same as TC 8.1.1.4.4 but applied to Inter-band CA case.

8.1.1.4.6.2 Conformance requirements

Same as TC 8.1.1.4.4 but applied to Inter-band CA case.

8.1.1.4.6.3 Test description

8.1.1.4.6.3.1 Pre-test conditions

Same as TC 8.1.1.4.4 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.1.4.6.3.2 Test procedure sequence

Same as TC 8.1.1.4.4 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.1.4.7 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-band Contiguous CA

8.1.1.4.7.1 Test Purpose (TP)

FFS

8.1.1.4.7.2 Conformance requirements

FFS

8.1.1.4.7.3 Test description

8.1.1.4.7.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is the PCell, NR Cell 3 is the PSCell, NR Cell 12 is the SCell

– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.

UE:

– None.

Preamble:

– The UE is in state 2N-A as defined in TS 38.508-1 [4], Table 4.4A.2-2 on NR Cell 1.

8.1.1.4.7.3.2 Test procedure sequence

Table 8.1.1.4.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity (correct fullI-RNTI).	<–	NR RRC: Paging	–	–
2	The UE transmit an RRCResumeRequest message to resume RRC Connection by setting resumeIdentity to the stored shortI-RNTI value?	–>	NR RRC: RRCResumeRequest	–	–
3	The SS transmits an RRCSetup message in response to RRCResumeRequest message.	<–	NR RRC: RRCSetup	–	–
4	The UE transmits an RRCSetupComplete message and a REGISTRATION REQUEST message by discarding any stored UE Inactive AS context and suspendConfig, setting the ng-5G-S-TMSI-Value to ng-5G-S-TMSI?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	–	–
5-6	Steps 4-5 as defined in TS 38.508-1 [4] Table 4.9.5.2.2-1.	–	–	–	–
7-8	Steps 5-6 as defined in TS 38.508-1 [4] Table 4.5.4.2-3.	–	–	–	–
9	Step 7 as defined in TS 38.508-1 [4] Table 4.5.4.2-3 and FFS.	–	–	–	–
10	Step 8 as defined in TS 38.508-1 [4] Table 4.5.4.2-3.	–	–	–	–

FFS

8.1.1.4.7.3.3 Specific message contents

Table 8.1.1.4.7.3.3-1: Paging (step 1, Table 8.1.1.4.7.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME

Table 8.1.1.4.7.3.3-2: RRCSetup (step 3, Table 8.1.1.4.7.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-21
Information Element	Value/remark	Comment	Condition
RRCSetup ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
rrcSetup SEQUENCE {
radioBearerConfig	RadioBearerConfig with condition RESUME
masterCellGroup	CellGroupConfig with condition RESUME and SCell_add
}
}
}

Table 8.1.1.4.7.3.3-3: CellGroupConfig (Table 8.1.1.4.7.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
sCellState-r16	activated
}
}
}

8.1.1.4.8 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-band non-Contiguous CA

8.1.1.4.8.1 Test Purpose (TP)

Same as TC 8.1.1.4.7 but applied to Intra-band non-Contiguous CA.

8.1.1.4.8.2 Conformance requirements

Same as TC 8.1.1.4.7 but applied to Intra-band non-Contiguous CA.

8.1.1.4.8.3 Test description

8.1.1.4.8.3.1 Pre-test conditions

Same as TC 8.1.1.4.7 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

8.1.1.4.8.3.2 Test procedure sequence

Same as TC 8.1.1.4.7 with the following differences:

– CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

8.1.1.4.9 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Inter-band CA

8.1.1.4.9.1 Test Purpose (TP)

Same as TC 8.1.1.4.7 but applied to Inter-band CA case.

8.1.1.4.9.2 Conformance requirements

Same as TC 8.1.1.4.7 but applied to Inter-band CA case.

8.1.1.4.9.3 Test description

8.1.1.4.9.3.1 Pre-test conditions

Same as TC 8.1.1.4.7 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.1.4.9.3.2 Test procedure sequence

Same as TC 8.1.1.4.7 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: NR Cell 10 replaces NR Cell 3