9.1.9 RACS

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

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

9.1.9.1 RACS / Network assigned UE radio capability ID

9.1.9.1.1 Test Purpose (TP)

(1)

with { UE is switched on and the UE has an applicable UE radio capability ID for the current UE radio configuration for the selected network }

ensure that {

when { the UE performs an initial registration procedure }

then { the UE includes the UE radio capability ID in the REGISTRATION REQUEST message }

}

(2)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE mode and having assigned a new UE Radio Capability ID in the Registration Accept message }

ensure that {

when { UE enters a new tracking area that is not in the list of tracking areas that the UE previously registered in the AMF }

then { UE sends REGISTRATION REQUEST message including the new UE radio capability ID }

}

9.1.9.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 4.16, 5.4.4.1, 5.4.4.2, 5.4.4.3, 5.4.4.4, 5.5.1.3.2

[TS 24.501, clause 4.16]

UE radio capability signalling optimisation (RACS) is a feature that is optional at both the UE and the network and which aims to optimise the transmission of UE radio capability over the radio interface (see 3GPP TS 23.501 [8]). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called the UE radio capability ID. A UE radio capability ID can be either manufacturer-assigned or network-assigned. The UE radio capability ID is an alternative to the signalling of the radio capabilities container over the radio interface.

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

b) if the UE performs a registration procedure for initial registration and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message;

…

g) if the UE performs a registration procedure for mobility and periodic registration update due to entering a tracking area that is not in the list of tracking areas that the UE previously registered in the AMF and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message.

If the network supports RACS:

a) the network may assign a network-assigned UE radio capability ID to a UE which supports RACS by including a UE radio capability ID IE in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message;

[TS 24.501, clause 5.4.4.1]

The purpose of this procedure is to:

a) allow the AMF to update the UE configuration for access and mobility management-related parameters decided and provided by the AMF by providing new parameter information within the command; or

b) request the UE to perform a registration procedure for mobility and periodic registration update towards the network to update access and mobility management-related parameters decided and provided by the AMF (see subclause 5.5.1.3).

…

9.1.9.1.3 Test description

9.1.9.1.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

– NGC Cell B configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] and set as Non-Suitable “Off” cell.

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

UE:

– UE is previously registered on NGC Cell A using default message contents according to TS 38.508-1 [4];

Preamble:

– The UE is in state Switched OFF (State 0N-B) as per TS 38.508-1 [4] Table 4.4A.2-0.

9.1.9.1.3.2 Test procedure sequence

Table 9.1.9.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Check: Does the UE transmit REGISTRATION REQUEST message including the UE radio capability ID 1?	–>	REGISTRATION REQUEST	1	P
3-11	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
12	SS transmits a REGISTRATION ACCEPT message with a new UE radio capability ID 2.	<–	REGISTRATION ACCEPT	–	–
13-18	Steps 15-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
19	The SS configures NGC Cell A as the "Suitable Neighbour intra-frequency cell" and NGC Cell B as the "Serving cell".	–	–	–	–
20	Check: Does the UE perform on NGC Cell B the Registration procedure for mobility registration update by executing the Test procedure to check that UE is camped on a new cell belonging to a new TA as specified in TS 38.508-1 [4] subclause 4.9.5 including the new UE radio capability ID 2 in the REGISTRATION REQUEST message?	–	–	2	P

9.1.9.1.3.3 Specific message contents

Table 9.1.9.1.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.1.3.3-2: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000010’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 000000000001

Table 9.1.9.1.3.3-3: REGISTRATION REQUEST (Step 2, Table 9.1.9.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
UE radio capability ID	‘01000000000010’H	Type Field (TF): 1 Version ID: 00 Radio Configuration Identifier (RCI): 00000000001

Table 9.1.9.1.3.3-4: REGISTRATION ACCEPT (Step 12, Table 9.1.9.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000020’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 000000000002

Table 9.1.9.1.3.3-5: REGISTRATION REQUEST (Step 20, Table 9.1.9.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘00000010’B	mobility registration updating
UE radio capability ID	‘010000000020’H	Type Field (TF): 1 Radio Configuration Identifier (RCI): 000000000002

9.1.9.2 RACS / UE configuration update / UE radio capability ID

9.1.9.2.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED state and a UE Radio Capability ID assigned in REGISTRATION ACCEPT message }

ensure that {

when { UE receives CONFIGURATION UPDATE COMMAND with new UE Radio Capability ID and acknowledgement requested}

then { UE sends CONFIGURATION UPDATE COMPLETE message }

}

(2)

with { UE in state 5GMM-REGISTERED, and 5GMM-IDLE mode over 3GPP access and assigned a new UE Radio Capability ID in CONFIGURATION UPDATE COMMAND }

ensure that {

when { UE enters a new tracking area that is not in the list of tracking areas that the UE previously registered in the AMF }

then { UE sends REGISTRATION REQUEST message including the new UE radio capability ID }

}

9.1.9.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 4.16, 5.4.4.1, 5.4.4.2, 5.4.4.3, 5.4.4.4, 5.5.1.3.2

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

…

d) upon receiving a network-assigned UE radio capability ID in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall store the network-assigned UE radio capability ID and the PLMN ID or SNPN identity of the serving network along with a mapping to the current UE radio configuration in its non-volatile memory as specified in annex C. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs with the associated PLMN ID or SNPN identity and the mapping to the corresponding UE radio configuration;

…

If the network supports RACS:

[TS 24.501, clause 5.4.4.1]

The purpose of this procedure is to:

a) allow the AMF to update the UE configuration for access and mobility management-related parameters decided and provided by the AMF by providing new parameter information within the command; or

…

[TS 24.501, clause 5.4.4.2]

The AMF shall initiate the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message to the UE.

The AMF shall in the CONFIGURATION UPDATE COMMAND message either:

a) include one or more of the following parameters: 5G-GUTI, TAI list, allowed NSSAI that may include the mapped S-NSSAI(s), LADN information, service area list, MICO indication, NITZ information, configured NSSAI that may include the mapped S-NSSAI(s), rejected NSSAI, network slicing subscription change indication, operator-defined access category definitions, SMS indication, service gap time value, "CAG information list", UE radio capability ID, 5GS registration result, UE radio capability ID deletion indication or truncated 5G-S-TMSI configuration;

b) include the Configuration update indication IE with the Registration requested bit set to "registration requested"; or

c) include a combination of both a) and b).

If an acknowledgement from the UE is requested, the AMF shall indicate "acknowledgement requested" in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message and shall start timer T3555. Acknowledgement shall be requested for all parameters except when only NITZ is included.

[TS 24.501, clause 5.4.4.3]

Upon receiving the CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if running and use the contents to update appropriate information stored within the UE.

If "acknowledgement requested" is indicated in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message, the UE shall send a CONFIGURATION UPDATE COMPLETE message.

…

If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message includes:

b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C

9.1.9.2.3 Test description

9.1.9.2.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

– NGC Cell B configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] and set as Non-Suitable “Off” cell.

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

UE:

None

Preamble:

– The UE is in state 3N-A on NGC cell A according to TS 38.508-1 [4].

9.1.9.2.3.2 Test procedure sequence

Table 9.1.9.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits CONFIGURATION UPDATE COMMAND including a new UE Radio Capability ID	<–	CONFIGURATION UPDATE COMMAND	–	–
2	Check: Does UE transmit CONFIGURATION UPDATE COMPLETE	–>	CONFIGURATION UPDATE COMPLETE	1	P
3	The SS transmits an RRCRelease message.	–	–	–	–
4	The SS configures NGC Cell A as the "Non-suitable cell" and NGC Cell B as the "Serving cell".	–	–	–	–
5	Check: Does the UE perform on NGC Cell B the Registration procedure for mobility registration update by executing the Test procedure to check that UE is camped on a new cell belonging to a new TA as specified in TS 38.508-1 [4] subclause 4.9.5?	–	–	2	P

9.1.9.2.3.3 Specific message contents

Table 9.1.9.2.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.2.3.3-2: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000050’H

Type Field (TF): 1

Version ID: ‘00’H

Radio Configuration Identifier (RCI): 00000000005

Table 9.1.9.2.3.3-3: CONFIGURATION UPDATE COMMAND (step 1, Table 9.1.9.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-19
Information Element	Value/Remark	Comment	Condition
Configuration update indication	‘11010001’B	Acknowledgement Requested
UE radio capability ID	‘01000000000070’H	Type Field (TF): ‘1’H Version ID: ‘00’H Radio Configuration Identifier (RCI): ‘00000000007’H

Table 9.1.9.2.3.3-4: REGISTRATION REQUEST (step 5, Table 9.1.9.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	‘00000010’B	mobility registration updating
UE radio capability ID	‘01000000000070’H	Type Field (TF): ‘1’H Version ID: ‘00’H Radio Configuration Identifier (RCI): ‘00000000007’H

9.1.9.3 RACS / PLMN change within registration area / From NW assigned to Manufacturer assigned UE Radio Capability ID

9.1.9.3.1 Test Purpose (TP)

(1)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE mode and NW has not assigned a UE Radio Capability ID in the Registration Accept message }

ensure that {

when { UE enters a new tracking area that is not in the list of tracking areas that the UE previously registered in the AMF }

then { UE sends REGISTRATION REQUEST message including the manufacturer-assigned UE Radio Capability ID }

}

(2)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE mode and having assigned a new UE Radio Capability ID in the Registration Accept message }

ensure that {

when { UE moves to cell belong to another equivalent PLMN }

then { UE sends REGISTRATION REQUEST message including the manufacturer-assigned UE Radio Capability ID }

}

9.1.9.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 4.16, 5.5.1.3

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

…

e) the UE shall not use a network-assigned UE radio capability ID assigned by a PLMN in PLMNs equivalent to the PLMN which assigned it;

f) upon receiving a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall delete all network-assigned UE radio capability IDs stored at the UE for the serving network, initiate a registration procedure for mobility and periodic registration update and include an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, if available at the UE, in the UE radio capability ID IE of the REGISTRATION REQUEST message; and

If the network supports RACS:

[TS 24.501, clause 5.5.1.3]

When the UE is not in NB-N1 mode, if the UE supports RACS, the UE shall:

a) set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

b) if the UE has an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN, include the applicable network-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message; and

c) if the UE:

1) does not have an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN; and

2) has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration,

include the applicable manufacturer-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message.

…

9.1.9.3.3 Test description

9.1.9.3.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

– NGC Cell B and NGC Cell E configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] and set as Non-Suitable “Off” cell.

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

UE:

– UE is previously registered on NGC Cell A using default message contents according to TS 38.508-1 [4];

Preamble:

– The UE is in test state (State 1N-A) as per TS 38.508-1 [4] Table 4.4A.2-0.

9.1.9.3.3.2 Test procedure sequence

Table 9.1.9.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell B as the "Serving cell". – NGC Cell A, and NGC Cell E as a "Non-suitable ‘Off’ cell".	–	–	–	–
–	The following messages are to be observed on NGC Cell B unless explicitly stated otherwise	–	–	–	–
2	Check: Does the UE transmit REGISTRATION REQUEST message including manufactured-assigned UE Radio Capability ID?	–>	REGISTRATION REQUEST	1	P
3	SS transmits a REGISTRATION ACCEPT message with a Network assigned UE radio capability ID and with PLMN ID of NGC Cell E included in the Equivalent PLMNs IE.	<–	REGISTRATION ACCEPT	–	–
4	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
5	The SS releases the RRC connection.	–	–	–	–
6	The SS configures: – NGC Cell E as the "Serving cell". – NGC Cell A, and NGC Cell B as a "Non-suitable ‘Off’ cell".	–	–	–	–
–	The following messages are to be observed on NGC Cell E unless explicitly stated otherwise	–	–	–	–
7	Check: Does the UE transmit REGISTRATION REQUEST message including manufactured-assigned UE Radio Capability ID?	–>	REGISTRATION REQUEST	2	P
8	SS transmits a REGISTRATION ACCEPT message with a Network assigned UE radio capability ID.	<–	REGISTRATION ACCEPT	–	–
9	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–

9.1.9.3.3.3 Specific message contents

Table 9.1.9.3.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.3.3.3-2: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
UE radio capability ID	Not Present	Network Radio capability ID is not assigned

Table 9.1.9.3.3.3-3: REGISTRATION REQUEST (Step 2, Table 9.1.9.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0010’B	mobility registration updating
UE radio capability ID	‘X0XXXXXXX XXXXXXXXXXX’H	Type Field (TF): 0 Vendor ID: XXXXXXXX(Note) Radio Configuration Identifier (RCI): XXXXXXXXXXX
Note: Vendor ID is assigned by Internet Assigned Numbers Authority as per TS 23.003 [34], cl.29.2.The value is not checked.

Table 9.1.9.3.3.3-4: REGISTRATION ACCEPT (Step 3, Table 9.1.9.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
UE radio capability ID	‘01000000000010’H	Type Field (TF): 1Version ID: 00 Radio Configuration Identifier (RCI): 000000000001
Equivalent PLMNs	MCC=002, MNC=101	PLMN ID of NGC Cell E

Table 9.1.9.3.3.3-5: REGISTRATION REQUEST (Step 7, Table 9.1.9.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0010’B	mobility registration updating
UE radio capability ID	‘X0XXXXXXX XXXXXXXXXXX’H	Type Field (TF): 0 Vendor ID: XXXXXXXX(Note) Radio Configuration Identifier (RCI): XXXXXXXXXXX
Note: Vendor ID is assigned by Internet Assigned Numbers Authority as per TS 23.003 [34], cl.29.2.The value is not checked.

Table 9.1.9.1.3.3-6: REGISTRATION ACCEPT (Step 8, Table 9.1.9.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
UE radio capability ID	‘01000000000010’H	Type Field (TF): 1 Version ID: 00 Radio Configuration Identifier (RCI): 000000000001

9.1.9.4 RACS / USIM change / Handling of URCID

9.1.9.4.1 Test Purpose (TP)

(1)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE mode and having assigned a UE Radio Capability ID in the REGISTRATION ACCEPT message }

ensure that {

when { UE is powered on or switched on with USIM having different SUPI }

then { UE does not include the UE radio capability ID in the REGISTRATION REQUEST message }

}

9.1.9.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 4.16, Annex C.

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

If the network supports RACS:

[TS 24.501, Annex C]

The following 5GMM parameters shall be stored in a non-volatile memory in the ME together with the SUPI from the USIM:

– configured NSSAI(s);

– NSSRG information;

– NSSAI inclusion mode(s);

– MPS indicator;

– MCS indicator;

– operator-defined access category definitions;

– network-assigned UE radio capability IDs;

…

Each network-assigned UE radio capability ID is stored together with a PLMN identity of the PLMN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that PLMN. A network-assigned UE radio capability ID can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the network-assigned UE radio capability ID.

9.1.9.4.3 Test description

9.1.9.4.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

UE:

– The UE is equipped with a USIM containing default values (as per 38.508-1 [4])

Preamble:

– The UE is in test state 1N-A as defined in 38.508-1 [4], subclause 4.4A.2 on NGC Cell A.

9.1.9.4.3.2 Test procedure sequence

Table 9.1.9.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The generic test procedure in TS 38.508-1 [4] Table 4.9.6.1-1 of Switch off procedure in RRC_IDLE are performed.	–	–	–	–
2	The UE is brought back to operation with USIM configuration 25 as defined in TS 38.508-1 [4] Table 6.4.1-25.	–	–	–	–
3	Check: Does the UE transmit an REGISTRATION REQUEST message without including UE radio capability ID?	–>	REGISTRATION REQUEST	1	P
4-19a1	Steps 5-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–

9.1.9.4.3.3 Specific message contents

Table 9.1.9.4.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.4.3.3-2: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000010’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 000000000001

Table 9.1.9.4.3.3-3: REGISTRATION REQUEST (step 3, Table 9.1.9.4.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘00000001’B	Initial registration
UE radio capability ID	Not present

9.1.9.5 RACS / Handling of delete indication for NW assigned UE radio capability ID

9.1.9.5.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED state and a UE Radio Capability ID assigned in REGISTRATION ACCEPT message }

ensure that {

when { UE receives CONFIGURATION UPDATE COMMAND with UE radio capability ID deletion indication and indicating “registration requested” }

then { UE deletes any stored Network-assigned UE radio capability IDs and then releases the existing N1 NAS signalling connection, starts a mobility registration procedure and does not include any Network-assigned UE radio capability IDs in the REGISTRATION REQUEST message }

}

(2)

with { UE in state 5GMM-REGISTERED, and 5GMM-IDLE mode over 3GPP access and assigned a new UE Radio Capability ID, enters a new tracking area that is not in the list of tracking areas that the UE previously registered in the AMF }

ensure that {

when { UE receives REGISTRATRATION ACCEPT message with UE radio capability ID deletion indication }

then { UE deletes the stored Network-assigned UE radio capability ID and initiate a registration procedure for mobility and periodic registration update over the existing N1 NAS signalling connection}

}

9.1.9.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 4.16, 5.4.4.1, 5.4.4.2, 5.4.4.3, 5.5.1.2.4. Unless otherwise stated these are Rel-16 requirements.

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

…

f) upon receiving a UE radio capability ID deletion indication IE set to "delete network-assigned UE radio capability IDs" in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall delete all network-assigned UE radio capability IDs stored at the UE for the serving network, initiate a registration procedure for mobility and periodic registration update and include an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, if available at the UE, in the UE radio capability ID IE of the REGISTRATION REQUEST message; and

If the network supports RACS:

[TS 24.501, clause 5.4.4.1]

The purpose of this procedure is to:

a) allow the AMF to update the UE configuration for access and mobility management-related parameters decided and provided by the AMF by providing new parameter information within the command; or

…

[TS 24.501, clause 5.4.4.2]

The AMF shall initiate the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message to the UE.

The AMF shall in the CONFIGURATION UPDATE COMMAND message either:

b) include the Configuration update indication IE with the Registration requested bit set to "registration requested"; or

c) include a combination of both a) and b).

…

If the AMF includes a UE radio capability ID deletion indication IE in the CONFIGURATION UPDATE COMMAND message, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE.

…

If the UE is not in NB-N1 mode and the UE supports RACS, the AMF may include either a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the CONFIGURATION UPDATE COMMAND message.

…

[TS 24.501, clause 5.4.4.3]

Upon receiving the CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if running and use the contents to update appropriate information stored within the UE.

…

If the CONFIGURATION UPDATE COMMAND message indicates "registration requested" in the Registration requested bit of the Configuration update indication IE and:

…

d) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" is included, and:

1) the UE is not in NB-N1 mode;

2) a new allowed NSSAI, a new configured NSSAI or a Network slicing subscription change indication is not included; and

3) the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message,

the UE shall, after the completion of the generic UE configuration update procedure, start a registration procedure for mobility and registration update as specified in subclause 5.5.1.3.

…

If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message includes:

b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C

[TS 24.501, clause 5.5.1.2.4]

If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message includes:

a) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the RPLMN or RSNPN stored at the UE, then the UE shall, after the completion of the ongoing registration procedure, initiate a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3.2 over the existing N1 NAS signalling connection; and

b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C.

9.1.9.5.3 Test description

9.1.9.5.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

– NGC Cell B configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] and set as Non-Suitable “Off” cell.

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

UE:

None

Preamble:

– The UE is in state 3N-A on NGC cell A according to TS 38.508-1 [4].

9.1.9.5.3.2 Test procedure sequence

Table 9.1.9.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits CONFIGURATION UPDATE COMMAND including UE radio capability ID deletion indication.	<–	CONFIGURATION UPDATE COMMAND	–	–
2	Check: Does UE transmit CONFIGURATION UPDATE COMPLETE	–>	CONFIGURATION UPDATE COMPLETE	–	–
3	SS releases the RRC connection.	–	–	–	–
4	Check: Does UE transmit a REGISTRATION REQUEST message and does not include any Network-assigned UE radio capability ID?	–>	REGISTRATION REQUEST	1	P
5	The SS transmits a REGISTRATION ACCEPT message including a UE radio capability ID.	<–	REGISTRATION ACCEPT	–	–
6	The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
7	The SS transmits an RRCRelease message.	–	–	–	–
8	The SS configures NGC Cell A as the "Non-suitable Off cell" and NGC Cell B as the "Serving cell".	–	–	–	–
9	The UE initiates a Registration procedure for mobility registration update by transmitting a REGISTRATION REQUEST message on NGC Cell B and includes the UE radio capability ID assigned at step 5.	–>	REGISTRATION REQUEST	–	–
10	The SS transmits REGISTRATION ACCEPT message including UE radio capability ID deletion indication.	<–	REGISTRATION ACCEPT	–	–
11	The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
12	Check: Does UE transmit a REGISTRATION REQUEST message and does not include any Network-assigned UE radio capability ID?	–>	REGISTRATION REQUEST	2	P
13	The SS transmits a REGISTRATION ACCEPT message.	<–	REGISTRATION ACCEPT	–	–
14	The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
15	The SS transmits an RRCRelease message.	–	–	–	–

9.1.9.5.3.3 Specific message contents

Table 9.1.9.5.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.5.3.3-2: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000010’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 00000000001

Table 9.1.9.5.3.3-3: CONFIGURATION UPDATE COMMAND (step 1, Table 9.1.9.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-19
Information Element	Value/Remark	Comment	Condition
Configuration update indication	‘11010011’B	Registration and Acknowledgement (ACK) requested
UE radio capability ID deletion indication	001	Network-assigned UE radio capability IDs deletion requested

Table 9.1.9.5.3.3-4: REGISTRATION REQUEST (step 4 and 12, Table 9.1.9.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	mobility registration updating
UE radio capability ID	Not present or ‘x0xxxxxxxxxxxxxxxxxx’H	Manufacturer assigned UE radio capability ID, If present

Table 9.1.9.5.3.3-5: REGISTRATION ACCEPT (step 5, Table 9.1.9.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000020’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 00000000002

Table 9.1.9.2.3.3-6: REGISTRATION REQUEST (step 9, Table 9.1.9.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	‘00000010’B	mobility registration updating
UE radio capability ID	‘01000000000020’H	Type Field (TF): ‘1’H Version ID: 00 Radio Configuration Identifier (RCI): ‘00000000002’H

Table 9.1.9.5.3.3-7: REGISTRATION ACCEPT (step 10, Table 9.1.9.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
UE radio capability ID deletion indication	001	Network-assigned UE radio capability IDs deletion requested

Table 9.1.9.5.3.3-8: REGISTRATION ACCEPT (step 13, Table 9.1.9.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
UE radio capability ID	Not Present

9.1.9.6 RACS / Change in radio capability / NW assigned URCID

9.1.9.6.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED state, and 5GMM-IDLE mode over 3GPP access and a UE Radio Capability ID assigned in REGISTRATION ACCEPT message }

ensure that {

when { radio configuration at the UE changes}

then { UE initiate a registration procedure for mobility and periodic registration update over the existing N1 NAS signalling connection, and includes the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed" and uses the network assigned ID }

}

9.1.9.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 4.16, 5.5.1.3.2

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

c) if the radio configuration at the UE changes (for instance because the UE has disabled a specific radio capability) then:

1) if the UE has an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update. The UE shall include the applicable UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message and shall include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed". If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message; and

2) if the UE does not have an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update and include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed";

NOTE: Performing the registration procedure for mobility and periodic registration update and including the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed" without a UE radio capability ID included in the REGISTRATION REQUEST message can trigger the network to assign a new UE radio capability ID to the UE.

…

If the network supports RACS:

[TS 24.501, clause 5.5.1.3.2]

m) when the UE needs to indicate PDU session status to the network after performing a local release of PDU session(s) as specified in subclauses 6.4.1.5 and 6.4.3.5;

n) when the UE in 5GMM-IDLE mode changes the radio capability for NG-RAN or E-UTRAN;

…

For case n), the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to " UE radio capability update needed". Additionally, if the UE is not in NB-N1 mode, the UE supports RACS and the UE has an applicable UE radio capability ID for the new UE radio configuration in the serving PLMN or SNPN, the UE shall include the applicable UE radio capability ID in the UE radio capability ID of the REGISTRATION REQUEST message.

…

If the UE is not in NB-N1 mode and the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message, the AMF may include either a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the REGISTRATION ACCEPT message. If the UE radio capability ID IE or the UE radio capability ID deletion indication IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3.

…

9.1.9.6.3 Test description

9.1.9.6.3.1 Pre-test conditions

System Simulator:

– NGC Cell A configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] belongs to Home PLMN and set as serving cell;

UE:

None

Preamble:

– The UE is in state 1N-A on NGC cell A according to TS 38.508-1 [4].

9.1.9.6.3.2 Test procedure sequence

Table 9.1.9.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to change the radio capability configuration. (Note 1)	–	–	–	–
2	Check: Does the UE transmit REGISTRATION REQUEST message including ‘NG-RAN-RCU’ bit and the UE radio capability ID#1 (assigned during preamble)?	–>	REGISTRATION REQUEST	1	P
3	SS transmits a REGISTRATION ACCEPT message with a UE radio capability ID 2.	<–	REGISTRATION ACCEPT	–	–
4	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
Note 1: The request to change radio capability configuration be performed by MMI or AT Command.

9.1.9.6.3.3 Specific message contents

Table 9.1.9.6.3.3-1: REGISTRATION REQUEST (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0001’B	Initial registration
5GMM capability
RACS	‘1’B	RACS supported

Table 9.1.9.6.3.3-2: REGISTRATION REQUEST (Step 2, Table 9.1.9.6.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘0000 0010’B	mobility registration updating
UE radio capability ID	‘01000000000010’H	Type Field (TF): 1 Version ID: 00 Radio Configuration Identifier (RCI): 00000000001
5GS update type
NG-RAN-RCU	UE radio capability update needed

Table 9.1.9.6.3.3-3: REGISTRATION ACCEPT (Step 3, Table 9.1.9.6.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000010’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 000000000001

9.1.9.7 RACS / Inter-system mobility registration update / Handling of UE radio capability ID

9.1.9.7.1 Test Purpose (TP)

(1)

with { UE in state EMM-REGISTERED and EMM-IDLE on an E-UTRA cell and has been previously registered on 5GC, UE supporting S1 and N1 and operating in single-registration mode, NWK supporting Single-registration mode with N26 interface and a UE Radio Capability ID assigned in the ATTACH ACCEPT message}

ensure that {

when { UE detects a suitable NGC cell after the serving E-UTRA cell becomes not suitable }

then { UE performs a Inter-system change from S1 mode to N1 mode by initiating and successfully completing a mobility and periodic registration update procedure, and includes the UE radio capability ID in the REGISTRATION REQUEST message }

}

(2)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE on a 5GC NR cell and has been previously registered on EPC as well, UE supporting S1 and N1 and operating in single-registration mode, NWK supporting Single-registration mode with N26 interface, having assigned a new UE Radio Capability ID in the Registration Accept message }

ensure that {

when { UE detects a suitable EPC E-UTRA cell after the serving NGC cell becomes not suitable }

then { UE performs a Inter-system change from N1 mode to S1 mode by initiating and successfully completing a TAU procedure, and the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. }

}

9.1.9.7.2 Conformance requirements

[TS 24.501, clause 4.16]

In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.

If the UE supports RACS:

a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;

…

If the network supports RACS:

[TS 24.501, clause 5.5.1.2.4]

If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message includes:

b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C.

c) if the UE:

1) does not have an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN; and

2) has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration,

include the applicable manufacturer-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message.

[TS 24.301, clause 5.3.20]

UE radio capability signalling optimisation (RACS) is a feature that is optional at both the UE and the network and which aims to optimise the transmission of UE radio capability over the radio interface (see 3GPP TS 23.401 [10]). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called the UE radio capability ID. A UE radio capability ID can be either manufacturer-assigned or network-assigned. The UE radio capability ID is an alternative to the signalling of the radio capabilities container over the radio interface.

In this release of the specification, RACS is not applicable to NB-S1 mode.

If the UE supports RACS:

– the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages;

– if the UE performs an attach procedure and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID availability IE in the ATTACH REQUEST message and set the IE to "UE radio capability ID available";

– if the UE performs a tracking area updating procedure and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID availability IE in the TRACKING AREA UPDATE REQUEST message and set the IE to "UE radio capability ID available";

– If the UE is requested to provide its UE radio capability ID by the network during a security mode control procedure, the UE shall include its UE radio capability ID in the UE radio capability ID IE of the SECURITY MODE COMPLETE message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE radio capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the SECURITY MODE COMPLETE message;

– if the radio configuration at the UE changes (for instance because the UE has disabled a specific radio capability) then:

a) if the UE has an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a tracking area updating procedure, include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message and include a UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the TRACKING AREA UPDATE REQUEST message; and

b) if the UE does not have an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a tracking area updating procedure and shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message;

NOTE: Performing the tracking area updating procedure with the UE radio capability information update needed IE included in the TRACKING AREA UPDATE REQUEST message and without the UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message as specified in b) above can trigger the network to assign a new UE radio capability ID to the UE.

….

[TS 24.301, clause 5.5.3.3.2]

The UE operating in CS/PS mode 1 or CS/PS mode 2, in state EMM-REGISTERED, shall initiate the combined tracking area updating procedure:

…

zf) in WB-S1 mode, when the applicable UE radio capability ID for the current UE radio configuration changes due to a reselection to a new PLMN or a revocation of the network-assigned UE radio capability IDs by the serving PLMN; or

…

For cases n, zc, ze and zf, the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message.

…

9.1.9.7.3 Test description

9.1.9.7.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NGC Cell A as defined in TS 38.508-1 [4] Table 6.3.2.2-1. System information combination NR-6 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2.

– E-UTRA Cell A as defined in TS 36.508 [7] Table 6.3.2.2-1. System information combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.

UE:

None.

Preamble:

– With NGC Cell A "Serving cell" and E-UTRA Cell A "Non-suitable "Off" cell", the UE is brought to state 0N-B as defined in 38.508-1 [4], subclause 4.4A on NGC Cell A.

– With E-UTRA Cell A "Serving cell" and NGC Cell A "Non-suitable "Off" cell", 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.

9.1.9.7.3.2 Test procedure sequence

Table 9.1.9.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell A as "Serving cell" – E-UTRA Cell A as "Non-suitable "off" cell".	–	–	–	–
2	Check: Does the UE perform test procedure for UE Tracking area updating for Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode as described in TS 38.508-1 [4], Table 4.9.9.2.2-1 on NGC Cell A?	–	–	1	–
3	The SS configures: – E-UTRA Cell A as "Serving cell" – NGC Cell A as "Non-suitable "off" cell".	–	–	–	–
4	Check: Does the UE perform Test procedure for UE Tracking area updating for Inter-system change from N1 mode to S1 mode in 5GMM/EMM-IDLE mode as described in TS 38.508-1 [4], Table 4.9.7.2.2-1, ‘connected without release‘ on E-UTRA Cell A?	–	–	2	–

9.1.9.7.3.3 Specific message contents

Table 9.1.9.7.3.3-1: ATTACH ACCEPT (Preamble)

Derivation path: TS 36.508, Table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000010’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 00000000001

Table 9.1.9.7.3.3-2: REGISTRATION REQUEST (step 2, Table 9.1.9.7.3.2-1; step 3, TS 38.508-1 [4], Table 4.9.9.2.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GS registration type	‘010’B	Mobility registration updating
5GMM capability
RACS	‘1’B	RACS supported
UE radio capability ID	‘01000000000010’H	Type Field (TF): 1 Version ID: 00 Radio Configuration Identifier (RCI): 00000000001

Table 9.1.9.7.3.3-3: REGISTRATION ACCEPT (step 2, Table 9.1.9.7.3.2-1; step 10, TS 38.508-1 [4], Table 4.9.9.2.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/Remark

Comment

Condition

UE radio capability ID

‘01000000000020’H

Type Field (TF): 1

Version ID: 00

Radio Configuration Identifier (RCI): 00000000002

Table 9.1.9.7.3.3-4: TRACKING AREA UPDATE REQUEST (step 4, Table 9.1.9.7.3.2-1; step 3, TS 38.508-1 [4], Table 4.9.7.2.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
UE radio capability information update needed	‘0001’B	UE radio capability information update needed