9.1.5 Registration

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

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

9.1.5.1 Initial registration

9.1.5.1.1 Initial registration / Success / 5G-GUTI reallocation, last visited TAI

9.1.5.1.1.1 Test Purpose (TP)

(1)

with { the UE is 5GMM-REGISTERED state with no valid 5G-GUTI but available SUCI }

ensure that {

when { the UE is switched off and switched on }

then { the UE sends a REGISTRATION REQUEST message including the SUCI in the 5GS mobile identity IE }

}

(2)

with { the UE is 5GMM-REGISTERED state with a cell belong to a non-equivalent PLMN with assigned 5G-GUTI and last visited registered TAI }

ensure that {

when { the UE is switched off and switched on with a cell belong to another PLMN }

then { the UE sends a REGISTRATION REQUEST message including the 5G-GUTI assigned by the last PLMN in the 5GS mobile identity IE and the last visited registered TAI }

}

(3)

with { the UE is 5GMM-REGISTERED state with a cell belong to an equivalent PLMN with assigned 5G-GUTI }

ensure that {

when { the UE is switched off and switched on with a cell belong to another PLMN }

then { the UE sends a REGISTRATION REQUEST message including the 5G-GUTI assigned by the equivalent PLMN in the 5GS mobile identity IE }

}

(4)

with { the UE is 5GMM-REGISTERED state with an assigned 5G-GUTI }

ensure that {

when { the UE is switched off and switched on with a cell belong to the same PLMN }

then { the UE sends a REGISTRATION REQUEST message including the 5G-GUTI assigned by the last registered PLMN in the 5GS mobile identity IE }

}

9.1.5.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501 clauses 5.5.1.2.2 and 5.5.1.2.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.2]

The UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511.

During initial registration the UE handles the 5GS mobile identity IE in the following order:

b) if the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by the same PLMN with which the UE is performing the registration, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE;

c) if the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by an equivalent PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE;

d) if the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP, by any other PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE;

e) if a SUCI is available the UE shall include the SUCI in the 5GS mobile identity IE; and

…

If the SUCI is included in the 5GS mobile identity IE and the timer T3519 is not running, the UE shall start timer T3519 and store the value of the SUCI sent in the REGISTRATION REQUEST message. The UE shall include the stored SUCI in the REGISTRATION REQUEST message while timer T3519 is running.

…

If the last visited registered TAI is available, the UE shall include the last visited registered TAI in the REGISTRATION REQUEST message.

9.1.5.1.1.3 Test description

9.1.5.1.1.3.1 Pre-test conditions

System Simulator:

– NGC Cell A, NGC Cell C and NGC Cell H are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4].

UE:

– None.

Preamble:

– The UE is in test state 0N-B according to TS 38.508-1 [4].

9.1.5.1.1.3.2 Test procedure sequence

Table 9.1.5.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell A as the "Serving cell". – NGC Cell H and NGC Cell C as the "Non-Suitable "off" cell".	–	–	–	–
2	The UE is switched on.	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise.	–	–	–	–
3-5	The UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–	–	–	–
6	SS transmits an REGISTRATION REJECT message with the 5GMM cause IE setting as “Illegal UE”. NOTE1: 5G-GUTI-1 should be deleted, then UE has no valid 5G-GUTI but available SUCI now.	<–	REGISTRATION REJECT	–	–
7	The generic test procedure in TS 38.508-1 Table 4.9.6.4-1 of Switch off procedure in State DEREGISTERED are performed.
8	The UE is brought back to operation or the USIM is inserted.
9-11	The UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–	–	–	–
12	Check: Does the UE transmit an REGISTRATION REQUEST message including the SUCI in the 5GS mobile identity IE?	–>	REGISTRATION REQUEST	1	P
13-21	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
22	SS transmits an REGISTRATION ACCEPT message with a new assigned 5G-GUTI-2.	<–	REGISTRATION ACCEPT	–	–
23-27a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed with ‘connected without release’.	–	–	–	–
28	The generic test procedure in TS 38.508-1 Table 4.9.6.3-1 of Switch off procedure in RRC_CONNECTED are performed.	–	–	–	–
29	The SS configures: – NGC Cell H as the "Serving cell". – NGC Cell A and NGC Cell C as a "Non-Suitable "off" cell".	–	–	–	–
30	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
–	The following messages are to be observed on NGC Cell H unless explicitly stated otherwise.	–	–	–	–
31-33	The UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–	–	–	–
34	Check: Does the UE transmit an REGISTRATION REQUEST message including the 5G-GUTI-2 assigned by the last PLMN in the 5GS mobile identity IE and the last visited registered TAI?	–>	REGISTRATION REQUEST	2	P
35-43	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
44	SS transmits an REGISTRATION ACCEPT message with a new assigned 5G-GUTI-3 and the PLMN of NGC Cell A as Equivalent PLMNs.	<–	REGISTRATION ACCEPT	–	–
45-49a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed with ‘connected without release’.	–	–	–	–
50	The generic test procedure in TS 38.508-1 Table 4.9.6.3-1 of Switch off procedure in RRC_CONNECTED is performed.	–	–	–	–
51	The SS configures: – NGC Cell A as the "Serving cell". – NGC Cell H and NGC Cell C as a "Non-Suitable "off" cell".	–	–	–	–
52	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise.	–	–	–	–
53-55	The UE establishes an RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–	–	–	–
56	Check: Does the UE transmit an REGISTRATION REQUEST message including the 5G-GUTI-3 assigned by the equivalent PLMN in the 5GS mobile identity IE?	–>	REGISTRATION REQUEST	3	P
57-65	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
66	SS transmits an REGISTRATION ACCEPT message with a new assigned 5G-GUTI-4.	<–	REGISTRATION ACCEPT	–	–
67-71a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed with ‘connected without release’.	–	–	–	–
72	The generic test procedure in TS 38.508-1 Table 4.9.6.3-1 of Switch off procedure in RRC_CONNECTED is performed.	–	–	–	–
73	The SS configures: – NGC Cell C as the "Serving cell". – NGC Cell A and NGC Cell H as a "Non-Suitable off cell".	–	–	–	–
74	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
–	The following messages are to be observed on NGC Cell C unless explicitly stated otherwise.	–	–	–	–
75-77	The UE establishes an RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–	–	–	–
78	Check: Does the UE transmit an REGISTRATION REQUEST message including the 5G-GUTI-4 assigned by last registered PLMN in the 5GS mobile identity IE?	–>	REGISTRATION REQUEST	4	P
79-94	Steps 5-20 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.1.3.3 Specific message contents

Table 9.1.5.1.1.3.3-1: Message REGISTRATION REJECT (step 6, Table 9.1.5.1.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-9
Information Element	Value/Remark	Comment	Condition
5GMM cause	‘0000 0011’B	Illegal UE

Table 9.1.5.1.1.3.3-2: Message REGISTRATION REQUEST (step 12, Table 9.1.5.1.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
5GS mobile identity	SUCI	The SUCI of UE

Table 9.1.5.1.1.3.3-3: Message REGISTRATION ACCEPT (step 22, Table 9.1.5.1.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
5G-GUTI	5G-GUTI-2

Table 9.1.5.1.1.3.3-4: Message REGISTRATION REQUEST (step 34, Table9.1.5.1.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
5GS mobile identity	5G-GUTI-2
Last visited registered TAI	TAI-1	TAI of NGC Cell A

Table 9.1.5.1.1.3.3-5: Message REGISTRATION ACCEPT (step 44, Table 9.1.5.1.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
5G-GUTI	5G-GUTI-3
Equivalent PLMNs	The PLMN ID of NGC Cell A

Table 9.1.5.1.1.3.3-6: Message REGISTRATION REQUEST (step 56, Table 9.1.5.1.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
5GS mobile identity	5G-GUTI-3
Last visited registered TAI	TAI-8	TAI of NGC Cell H

Table 9.1.5.1.1.3.3-7: Message REGISTRATION ACCEPT (step 66, Table 9.1.5.1.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
5G-GUTI	5G-GUTI-4

Table 9.1.5.1.1.3.3-8: Message REGISTRATION REQUEST (step 78, Table 9.1.5.1.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
5GS mobile identity	5G-GUTI-4
Last visited registered TAI	TAI-1	TAI of NGC Cell A

9.1.5.1.2 Initial registration / 5GS services / Equivalent PLMN list handling

9.1.5.1.2.1 Test Purpose (TP)

(1)

with { The UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { UE receives a REGISTRATION ACCEPT with a new set of Equivalent PLMNs, then after Switch OFF and Switch ON }

then { The UE deletes the old equivalent PLMN list and uses the new equivalent PLMN list }

}

(2)

with { The UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { UE receives a REGISTRATION ACCEPT that does not include Equivalent PLMNs, then after Switch OFF and Switch ON }

then { UE deletes the old equivalent PLMN list }

}

(3)

with { The UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { the UE receives a REGISTRATION ACCEPT that includes equivalent PLMN list, and the UE detects that an entry in the equivalent PLMN list is also present in forbidden PLMN list }

then { UE deletes the entry in equivalent PLMN list that is also present in forbidden PLMN list }

}

9.1.5.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.5.1.2.4 and 5.5.1.3.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.4]

…

The AMF may also include a list of equivalent PLMNs in the REGISTRATION ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if the initial registration procedure is not for emergency services, the UE shall remove from the list any PLMN code that is already in the list of "forbidden PLMNs". In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list.

…

[TS 24.501, clause 5.5.1.3.4]

…

The AMF may also include a list of equivalent PLMNs in the REGISTRATION ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if there is no emergency PDU session established, the UE shall remove from the list any PLMN code that is already in the list of "forbidden PLMNs". If the UE is not registered for emergency services and there is an emergency PDU session established, the UE shall remove from the list of equivalent PLMNs any PLMN code present in the "forbidden PLMNs list" when the emergency PDU session is released. In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list.

…

9.1.5.1.2.3 Test description

9.1.5.1.2.3.1 Pre-test conditions

System Simulator:

– NGC Cell A and NGC Cell E and NGC Cell F are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [4].

– NGC Cell F is configured with NR frequency NRf3.

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

UE:

None.

Preamble:

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

9.1.5.1.2.3.2 Test procedure sequence

Table 9.1.5.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell F as the "Serving cell". – NGC Cell E as the "Non-Suitable "off" cell". – NGC Cell A as the “Non-Suitable “off" cell".	–	–	–	–
2	The UE is Switched ON		–
–	The following messages are to be observed on NGC Cell F unless explicitly stated otherwise		–
3-14	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	SS transmits a REGISTRATION ACCEPT message with PLMN ID of NGC Cell A included in the Equivalent PLMNs IE	<–	REGISTRATION ACCEPT	–	–
16-20a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
21	The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4]	–	–	–	–
22	The UE is Switched ON	–	–	–	–
23-34	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
35	SS transmits a REGISTRATION ACCEPT message with PLMN ID of NGC Cell E included in the Equivalent PLMNs IE	<–	REGISTRATION ACCEPT	–	–
36-40a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
41	The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4].	–	–	–	–
42	The SS configures: – NGC CelFl as the "Non-Suitable "off" cell". – NGC Cell E as the "Suitable neighbour cell". – NGC Cell A as the "Serving cell".	–	–	–	–
43	The UE is Switched ON.	–	–	–	–
–	The following messages are to be observed on NGC Cell E unless explicitly stated otherwise	–	–	–	–
44-62a1	Steps 2-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	1	P
63	The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4].	–	–	–	–
63A	The SS configures: – NGC Cell F as the "Serving cell". – NGC Cell E as the "Non-Suitable "off" cell". – NGC Cell A as the "Suitable neighbour cell".	–	–	–	–
64	The UE is Switched ON	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise	–	–	–	–
64A	Steps 2-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	2	P
64B	The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4].	–	–	–	–
64C	The SS configures: – NGC Cell A as the "Non-Suitable "off" cell".	–	–	–	–
64D	The UE is Switched ON.	–	–	–	–
65-76	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	2	P
76A	Void.	–	–	–	–
77	SS transmits a REGISTRATION REJECT with cause #11 (PLMN not allowed)	<–	REGISTRATION REJECT	–	–
78	The SS releases the RRC connection	–	–
79	The SS configures: – NGC Cell A as the "Serving cell". – NGC Cell E as the “Non-Suitable "off" cell ".. – NGC Cell F as the “Non-Suitable "off" cell ".	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise	–	–	–	–
80-93	Steps 2-13 of Table 4.5.5.2.2- 2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
94	SS transmits a REGISTRATION ACCEPT message with PLMN ID of NGC Cell E and NGC Cell F included in the Equivalent PLMNs IE	<–	REGISTRATION ACCEPT	–	–
95-99a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
100	The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4].	–	–	–	–
101	The SS configures: – NGC Cell A as the “Non-Suitable "off" cell ". – NGC Cell E as the "Suitable neighbour cell". – NGC Cell F as the “Serving cell".	–	–	–	–
–	The following messages are to be observed on NGC Cell E unless explicitly stated otherwise	–	–	–	–
102	The UE is Switched ON	–	–	–	–
103-121a1	Steps 2-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	3	P
122	The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4].	–	–	–	–
123	The SS configures: – NGC Cell A as the “Non-Suitable "off" cell ". – NGC Cell E as the "Non-Suitable "off" cell ". – NGC Cell F as the “Serving cell".	–	–	–	–
124	The UE is Switched ON	–	–	–	–
–	The user is prompted to manually select PLMN of NGC Cell F	–	–	–	–
–	The following messages are to be observed on NGC Cell F unless explicitly stated otherwise	–	–	–	–
125-143a1	Steps 2-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
144	The user sets the UE in Automatic PLMN selection mode.	–	–	–	–
145	Wait for 300s to allow the UE to switch to automatic PLMN selection mode.	–	–	–	–

9.1.5.1.2.3.3 Specific message contents

Table 9.1.5.1.2.3.3-1: REGISTRATION ACCEPT (step 15 Table 9.1.5.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
Equivalent PLMNs	MCC/MNC=MCC/MNC in USIM	PLMN ID of NGC Cell A

Table 9.1.5.1.2.3.3-2: REGISTRATION ACCEPT (step 35 Table 9.1.5.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
Equivalent PLMNs	MCC=002, MNC=101	PLMN ID of NGC Cell E

Table 9.1.5.1.2.3.3-3: REGISTRATION ACCEPT (step 94 Table 9.1.5.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
Equivalent PLMNs	MCC=003, MNC=101 and MCC=002, MNC=101	PLMN ID of NGC Cell F and PLMN ID of NGC Cell E

Table 9.1.5.1.2.3.3-4: REGISTRATION REJECT (step 77 Table 9.1.5.1.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM Cause	‘0000 1011’B	PLMN not allowed

9.1.5.1.3 Initial registration / 5GS services / NSSAI handling

9.1.5.1.3.1 Test Purpose (TP)

(1)

with { UE has sent a REGISTRATION REQUEST message including Requested NSSAI}

ensure that {

when { UE receives REGISTRATION ACCEPT message with Allowed NSSAI }

then { UE shall replace any stored allowed NSSAI for the current PLMN with new allowed NSSAI for the current PLMN }

}

(2)

with { UE has sent a REGISTRATION REQUEST message including Requested NSSAI}

ensure that {

when { UE receives REGISTRATION ACCEPT message with Rejected NSSAI with reject cause “S-NSSAI not available in the current PLMN” }

then { UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN and not attempt to use the Rejected NSSAI in the current PLMN until switching off the UE or the UICC containing the USIM is removed }

}

(3)

with { UE receives REGISTRATION ACCEPT message with Rejected NSSAI with reject cause “S-NSSAI not available in the current PLMN” }

ensure that {

when { UE has been switched off, then switched on }

then { UE shall delete the stored Rejected NSAAI and shall send the NSSAI in Requested NSSAI IE of the REGISTRATION REQUEST message as per the configured and Allowed NSSAI for current PLMN }

}

(4)

with { UE has sent a REGISTRATION REQUEST message including Requested NSSAI}

ensure that {

when { UE receives REGISTRATION ACCEPT message with Rejected NSSAI with reject cause “S-NSSAI not available in the current registration area” }

then { UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN and registration area combination and not attempt to use the Rejected NSSAI in the current registration area until switching off the UE, the UE moving out of the current registration area or the UICC containing the USIM is removed }

}

(5)

with { UE receives REGISTRATION ACCEPT message with Rejected NSSAI with reject cause “S-NSSAI not available in the current registration area” }

ensure that {

when { UE has been moved out of the current registration area }

then { UE shall delete the stored Rejected NSAAI for the current PLMN as well as registration area combination and shall send the NSSAI in Requested NSSAI IE of the REGISTRATION REQUEST message as per the configured and Allowed NSSAI for current PLMN }

}

9.1.5.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], clause 5.5.1.2.2 and 5.5.1.2.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501 clause 5.5.1.2.2]

The UE shall include the requested NSSAI containing the S-NSSAI(s) corresponding to the slice(s) to which the UE intendsto register and shall include themapped S-NSSAI(s) for the requested NSSAI, if available, in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI for the current PLMN, the requested NSSAI shall be either:

a) the configured NSSAI for the current PLMN, or a subset thereof as described below, if the UE has no allowed NSSAI for the current PLMN;

b) the allowed NSSAI for the current PLMN, or a subset thereof as described below, if the UE has an allowed NSSAI for the current PLMN; or

c) the allowed NSSAI for the current PLMN, or a subset thereof as described below, plus one or more S-NSSAIs from the configured NSSAI for which no corresponding S-NSSAI is present in the allowed NSSAI and those are neither in the rejected NSSAI for the current PLMN nor in the rejected NSSAI for the current area.

If the UE has neither allowed NSSAI for the current PLMN nor configured NSSAI for the current PLMN and has a default configured NSSAI, the UE shall:

a) include the S-NSSAI(s) in the Requested NSSAI IE of the REGISTRATION REQUEST message using the default configured NSSAI; and

b) include the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" in the REGISTRATION REQUEST message.

If the UE has no allowed NSSAI for the current PLMN, no configured NSSAI for the current PLMN, and no default configured NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION message.

The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to the current PLMN, if the S-NSSAI is neither in the rejected NSSAI for the current PLMN nor in the rejected NSSAI for the current PLMN and registration area combination.

The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for the current PLMN.

NOTE 3: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation specific. The UE can take preferences indicated by the upper layers(e.g. policies,application) into account.

NOTE 4: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight.

[TS 24.501 clause 5.5.1.2.4]

The AMF shall include the allowed NSSAI for the current PLMN and shall include the mapped S-NSSAI for the allowed NSSAI containedfrom the UE if available, in the REGISTRATION ACCEPT message if the UE included the requested NSSAI in the REGISTRATION REQUEST message and the AMF allows one or more S-NSSAIs in the requested NSSAI. The AMF may also include rejected NSSAI in the REGISTRATION ACCEPT message. Rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s).

The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message if:

a) the REGISTRATION REQUEST message did not include the requested NSSAI;

b) the REGISTRATION REQUEST message included the requested NSSAI containing an S-NSSAI that is not valid in the serving PLMN; or

c) the REGISTRATION REQUEST message included the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI".

If a new configured NSSAI for the current PLMN is included in the REGISTRATION ACCEPT message, the AMF shall also include the mapped NSSAI(s) for the configured NSSAI for the current PLMN if available in the REGISTRATION ACCEPT message. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3.

The AMF shall include the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed" in the REGISTRATION ACCEPT message if the UDM has indicated that the subscription data for network slicing has changed. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3.

The UE receiving the rejected NSSAI in the REGISTRATION ACCEPT message takes the following actions based on the rejection cause in the rejected NSSAI:

"S-NSSAI not available in the current PLMN"

The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN as specified in subclause 4.6.2.2 and not attempt to use this S-NSSAI in the current PLMN until switching off the UE or the UICC containing the USIM is removed.

"S-NSSAI not available in the current registration area"

The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and not attempt to use this S-NSSAI in the current registration area until switching off the UE, the UE moving out of the current registration area or the UICC containing the USIM is removed.

If the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the requested NSSAI are present in the subscribed S-NSSAIs, and one or more subscribed S-NSSAIs (containing one or more S-NSSAIs each of which may be associated with a new S-NSSAI) marked as default are available, the AMF shall put the subscribed S-NSSAIs marked as default in the allowed NSSAI of the REGISTRATION ACCEPT message. The AMF shall determine a registration area such that all S-NSSAIs of the allowed NSSAI are available in the registration area.

9.1.5.1.3.3 Test description

9.1.5.1.3.3.1 Pre-test conditions

System Simulator:

– NGC Cell A belongs to Home PLMN and TAI-1 and set as serving cell;

– NGC Cell B belongs to Home PLMN and TAI-2 and set as Non-Suitable “Off” cell.

– NGC Cell C belongs to Home PLMN and TAI-3 and set as Non-Suitable “Off” cell.

UE:

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

– Empty URSP Configuration.

Preamble:

– The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4].

9.1.5.1.3.3.2 Test procedure sequence

Table 9.1.5.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Check: Does UE transmit a REGISTRATION REQUEST message?	–>	REGISTRATION REQUEST	–	–
3-11	Steps 5 to 13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
12	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI and Configured NSSAI.	<–	REGISTRATION ACCEPT	–	–
13-18	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
19	Switch off procedure in RRC_IDLE specified in TS 38.508-1 subclause 4.9.6.1 is performed.	–	–	–	–
20	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
21	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI?	–>	REGISTRATION REQUEST	1	P
22-30	Steps 5 to 13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
31	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI and Rejected NSSAI.	<–	REGISTRATION ACCEPT	–	–
32-37	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
38	The SS configures NGC Cell A as a “Non-suitable “Off” cell” and NGC Cell C as the “Serving cell”.	–	–	–	–
39	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI on NGC Cell C?	–>	REGISTRATION REQUEST	2	P
40-48	Void.	–	–	–	–
49	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI.	<–	REGISTRATION ACCEPT	–	–
50	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
51	The SS transmits an RRCRelease message.	–	–	–	–
52	Check: Is S-NSSAI=2 in the Rejected NSSAI list with cause “S-NSSAI not available in the current PLMN” associated with current PLMN using AT/MMI?	–	–	2	P
53	Switch off procedure in RRC_IDLE specified in TS 38.508-1 subclause 4.9.6.1 is performed.	–	–	–	–
54	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
55	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI?	–>	REGISTRATION REQUEST	3	P
56-64	Steps 5 to13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
65	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI and Rejected NSSAI.	<–	REGISTRATION ACCEPT	–	–
66-71a1	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2 are performed.	–	–	–	–
–	EXCEPTION: Step 71Aa1 describes behaviour depending on UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.	–	–	–	–
71Aa1	If pc_noOf_PDUsNewConnection > 0 THEN generic procedure for NR RRC_IDLE Extension specified in TS 38.508-1 subclause Table 4.5.2.2-4 are performed.	–	–	–	–
72	Check: Is S-NSSAI=2 removed from the Rejected NSSAI list associated with current PLMN?	–	–	3	P
72A	Check: Is S-NSSAI=1 in the Rejected NSSAI list with cause “S-NSSAI not available in the current registration area” associated with current PLMN and registration area combination using AT/MMI?	–	–	4	P
73	The SS configures NGC Cell C as the "Non-suitable “Off” cell" and NGC Cell B as the "Serving cell".	–	–	–	–
74	Wait for 34s for FR1 or 130s for FR2 to allow UE to recognise the change, then the generic test procedure in TS 38.508-1 Table 4.9.4.2.2-1 is performed to indicate that UE camp on Cell B. (Note 1).	–	–	–	–
75-86	Void	–	–	–	–
87	Check: Is S-NSSAI=1 in the Rejected NSSAI list with cause “S-NSSAI not available in the current registration area” associated with current PLMN and registration area combination using AT/MMI?	–	–	4	P
88	The SS configures NGC Cell B as the "Non-suitable “Off” cell" and NGC Cell A as the "Serving cell".	–	–	–	–
89	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI?	–>	REGISTRATION REQUEST	5	P
90-98	Void	–	–	–	–
99	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI.	<–	REGISTRATION ACCEPT	–	–
100	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
101	The SS transmits an RRCRelease message.	–	–	–	–
102	Check: Is S-NSSAI=1 removed from the Rejected NSSAI list associated with current PLMN and registration area combination?	–	–	5	P
Note 1: The wait time for reselection to a newly detected intra frequency cell is selected to cover T_{detect,NR_Intra} (251280ms=32s for FR1 and 254*1280ms=128s for FR2) + T_SI-NR (1.28s for FR1 and FR2) = 33.28s rounded up to 34s for FR1 and 129.28s rounded up to 130s for FR2.

9.1.5.1.3.3.3 Specific message contents

Table 9.1.5.1.3.3.3-1: REGISTRATION REQUEST (step 2, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1	Note
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Note: S-NSSAI =1 will be always included from the allowed NSSAI list associated with PLMN of NCG Cell A by the UE but may include other S-NSSAI from Configured NSSAI list associated with PLMN of NCG Cell A if configured in the UE. See TS 24.501 clause 5.5.1.2.1

Table 9.1.5.1.3.3.3-2: REGISTRATION ACCEPT (step 12, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Configured NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present

Table 9.1.5.1.3.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (step 14 , Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI
Length of S-NSSAI contents	‘0000 0001’B	SST
SST	‘0000 0010’B	SST value 2

Table 9.1.5.1.3.3.3-4: REGISTRATION REQUEST (step 21, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2	Note
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Note: S-NSSAI =2 will be always included by the UE from the allowed NSSAI list associated with PLMN of NCG Cell A but may include S-NSSAI =1 from Configured NSSAI list associated with PLMN of NCG Cell A. See TS 24.501 sub-clause 5.5.1.2.1

Table 9.1.5.1.3.3.3-5: REGISTRATION ACCEPT (step 31, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1	Note
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Rejected NSSAI
Rejected S-NSSAI-1		Rejected S-NSSAI value 1
Cause value	‘0000’B	S-NSSAI not available in the current PLMN
SST	‘00000010’B	SST value 2
SD	Not Present
Note: If UE has requested only S-NSSAI =2 in step 21 and S-NSSAI =2 is added in the Rejected NSSAI list by the SS then AMF/SS can include default subscribed S-NSSAIs in the allowed NSSAI of REGISTRATION ACCEPT message, see TS 24.501 sub-clause 5.5.1.2.4.

Table 9.1.5.1.3.3.3-6: REGISTRATION REQUEST (step 39, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘010’B	mobility registration updating
Requested NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present

Table 9.1.5.1.3.3.3-7: REGISTRATION ACCEPT (step 49, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present

Table 9.1.5.1.3.3.3-8: REGISTRATION REQUEST (step 55, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1	Note
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Note: S-NSSAI =1 will be always included by the UE from the allowed NSSAI list associated with PLMN of NCG Cell C but may include S-NSSAI =2 from Configured NSSAI list associated with PLMN of NCG Cell C. See TS 24.501 sub-clause 5.5.1.2.1

Table 9.1.5.1.3.3.3-9: REGISTRATION ACCEPT (step 65, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
TAI list
Type of list	‘01’B	list of TACs belonging to one PLMN, with consecutive TAC values
Number of elements	‘00001’B	2 Elements
TAC	PLMN =MCC/MNC stored in EFIMSI TAC 1 = 2	TAI-2, TAI-3
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Rejected NSSAI
Rejected S-NSSAI-1		Rejected S-NSSAI value 1
Cause value	‘0001’B	S-NSSAI not available in the current registration area
SST	‘00000001’B	SST value 1
SD	Not Present
Note: If UE has requested only S-NSSAI =1 in step 55 and S-NSSAI =1 is added in the Rejected NSSAI list by the SS then AMF/SS can include default subscribed S-NSSAIs in the allowed NSSAI of REGISTRATION ACCEPT message, see TS 24.501 sub-clause 5.5.1.2.4.

Table 9.1.5.1.3.3.3-10: PDU SESSION ESTABLISHMENT ACCEPT (step 67 , Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI
Length of S-NSSAI contents	‘0000 0001’B	SST
SST	‘0000 0010’B	SST value 2

Table 9.1.5.1.3.3.3-11: Void

Table 9.1.5.1.3.3.3-12: Void

Table 9.1.5.1.3.3.3-13: REGISTRATION REQUEST (step 89, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘010’B	mobility registration updating
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Note: S-NSSAI =2 will be always included by the UE from the allowed NSSAI list associated with PLMN of NCG Cell A but may include S-NSSAI =1 from Configured NSSAI list associated with PLMN of NCG Cell A. See TS 24.501 sub-clause 5.5.1.2.1

Table 9.1.5.1.3.3.3-14: REGISTRATION ACCEPT (step 99, Table 9.1.5.1.3.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	SST value 2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2	Note
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	SST value 1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Note: SS will send allowed NSSAIs based on the Requested NSSAIs sent by UE in step 89.

9.1.5.1.3a Initial registration / 5GS services / NSSAI handling / NSSAI storage

9.1.5.1.3a.1 Test Purpose (TP)

(1)

with { UE is switched off with a valid USIM inserted }

ensure that {

when { UE has configured NSSAI associated with HPLMN, configured NSSAI associated with a current PLMN with mapping to the Configured NSSAI for the HPLMN and UE is powered up or switched on }

then { UE transmits REGISTRATION REQUEST message with Requested NSSAI using the configured NSSAI associated with current PLMN and mapping of each S-NSSAI of the requested NSSAI to the S-NSSAIs of the configured NSSAI for the HPLMN }

}

(2)

with { UE is switched off with a valid USIM inserted }

ensure that {

when { UE has neither allowed NSSAI for the current PLMN nor configured NSSAI for the current PLMN and has a default configured NSSAI and UE is powered up or switched on }

then { UE transmits REGISTRATION REQUEST message with Requested NSSAI using the default configured NSSAI and also includes Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" }

}

(3)

with { UE is switched off with a valid USIM inserted }

ensure that {

when { UE has no allowed NSSAI for the current PLMN, no configured NSSAI for the current PLMN, and no configured NSSAI not associated with a PLMN and UE is powered up or switched on }

then { UE transmits REGISTRATION REQUEST message and does not include a Requested NSSAI }

}

9.1.5.1.3a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 5.5.1.2.2 and 5.5.1.2.4.

[TS 24.501 clause 5.5.1.2.2]

5.5.1.2.1 General

This procedure can be used by a UE for initial registration for 5GS services.

…

The UE shall include the requested NSSAI containing the S-NSSAI(s) corresponding to the slice(s) to which the UE wants to register and shall include the mapping of the requested NSSAI which is the mapping of each S-NSSAI of the requested NSSAI to the S-NSSAI(s) of the HPLMN, if available, in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI for the current PLMN, the requested NSSAI shall be either:

a) the configured NSSAI for the current PLMN, or a subset thereof as described below, if the UE has no allowed NSSAI for the current PLMN;

b) the allowed NSSAI for the current PLMN, or a subset thereof as described below, if the UE has an allowed NSSAI for the current PLMN; or

If the UE has neither allowed NSSAI for the current PLMN nor configured NSSAI for the current PLMN and has a default configured NSSAI, the UE shall:

a) include the S-NSSAI(s) in the Requested NSSAI IE of the REGISTRATION REQUEST message using the default configured NSSAI; and

b) include the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" in the REGISTRATION REQUEST message.

If the UE has no allowed NSSAI for the current PLMN, no configured NSSAI for the current PLMN, and no default configured NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION message.

The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for the current PLMN.

NOTE 3: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation.

NOTE 4: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight.

[TS 24.501 clause 5.5.1.2.4]

The AMF shall include the allowed NSSAI for the current PLMN and shall include the mapping of each S-NSSAI of the allowed NSSAI to the S-NSSAI(s) of the HPLMN contained in the requested NSSAI from the UE if available, in the REGISTRATION ACCEPT message if the UE included the requested NSSAI in the REGISTRATION REQUEST message and the AMF allows one or more S-NSSAIs in the requested NSSAI. The AMF may also include rejected NSSAI in the REGISTRATION ACCEPT message. Rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s).

The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message if:

a) the REGISTRATION REQUEST message did not include the requested NSSAI;

b) the REGISTRATION REQUEST message included the requested NSSAI containing an S-NSSAI that is not valid in the serving PLMN; or

c) the REGISTRATION REQUEST message included the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI".

If a new configured NSSAI for the current PLMN is included in the REGISTRATION ACCEPT message, the AMF shall also include the mapping of the configured NSSAI for the current PLMN the S-NSSAI(s) of the to HPLMN if available in the REGISTRATION ACCEPT message. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3.

The UE receiving the rejected NSSAI in the REGISTRATION ACCEPT message takes the following actions based on the rejection cause in the rejected NSSAI:

"S-NSSAI not available in the current PLMN"

"S-NSSAI not available in the current registration area"

The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN and registration area combination as specified in subclause 4.6.2.2 and not attempt to use this S-NSSAI in the current registration area until switching off the UE, the UE moving out of the current registration area or the UICC containing the USIM is removed.

9.1.5.1.3a.3 Test description

9.1.5.1.3a.3.1 Pre-test conditions

System Simulator:

– NGC Cell G is configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4] except that frequency NRf1 replaces NRf2.

– NGC Cell G belongs to VPLMN, TAI-7 and set as serving cell.

UE:

– None

Preamble:

– The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4] and camped on NGC Cell A HPLMN.

9.1.5.1.3a.3.2 Test procedure sequence

Table 9.1.5.1.3a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.			–	–
2	The UE transmits REGISTRATION REQUEST message on NGC Cell G.	–>	REGISTRATION REQUEST	–	–
3-11	Steps 5 to 13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed.	–	–	–	–
12	The SS transmits REGISTRATION ACCEPT message including Configured and Allowed NSSAI lists.	<–	REGISTRATION ACCEPT	–	–
13 -18	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed with ‘connected without release’.	–	–	–	–
19	The SS transmits NSSAI DELETE REQUEST message to delete the Allowed NSSAI list for all PLMNs (MCC-MNC =000-000) and for 3GPP access so UE has only configured NSSAI.	<–	NSSAI DELETE REQUEST	–	–
20	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
21	The SS transmits an RRCRelease message.	–	–	–	–
22	Switch off procedure in RRC_Idle specified in TS 38.508-1 subclause 4.9.6.1 is performed.	–	–	–	–
23	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
24	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI?	–>	REGISTRATION REQUEST	1	P
25-33	Steps 5 to13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed.	–	–	–	–
34	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI.	<–	REGISTRATION ACCEPT	–	–
35-40	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed with ‘connected without release’.	–	–	–	–
41	The SS transmits NSSAI DELETE REQUEST message to delete the Default Configured NSSAI list.	<–	NSSAI DELETE REQUEST	–	–
42	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
43	Use AT command and set Default Configured NSSAI to 1 & 2.	–	–	–	–
44	The SS transmits NSSAI DELETE REQUEST message to delete the Configured NSSAI list for all PLMNs (MCC-MNC =000-000).	<–	NSSAI DELETE REQUEST	–	–
45	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
46	The SS transmits NSSAI DELETE REQUEST message to delete the Allowed NSSAI list for all PLMNs (MCC-MNC =000-000).	<–	NSSAI DELETE REQUEST	–	–
47	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
48	The SS transmits an RRCRelease message.	–	–	–	–
49	Switch off procedure in RRC_Idle specified in TS 38.508-1 subclause 4.9.6.1 is performed	–	–	–	–
50	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
51	Check: Does UE transmit a REGISTRATION REQUEST message including Requested NSSAI?	–>	REGISTRATION REQUEST	2	P
52- 60	Steps 5 to 13 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed.	–	–	–	–
61	The SS transmits a REGISTRATION ACCEPT message including Allowed NSSAI.	<–	REGISTRATION ACCEPT	–	–
62-67	Steps 15 to 20a1 of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed with ‘connected without release’.	–	–	–	–
68	The SS transmits NSSAI DELETE REQUEST message to delete the Default Configured NSSAI list.	<–	NSSAI DELETE REQUEST	–	–
69	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
70	The SS transmits NSSAI DELETE REQUEST message to delete the Configured NSSAI list for all PLMNs (MCC-MNC =000-000).	<–	NSSAI DELETE REQUEST	–	–
71	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
72	The SS transmits NSSAI DELETE REQUEST message to delete the Allowed NSSAI list for all PLMNs (MCC-MNC =000-000).	<–	NSSAI DELETE REQUEST	–	–
73	UE transmits NSSAI DELETE RESPONSE message.	–>	NSSAI DELETE RESPONSE	–	–
74	The SS transmits an RRCRelease message.	–	–	–	–
75	Switch off procedure in RRC_Idle specified in TS 38.508-1 subclause 4.9.6.1 is performed.	–	–	–	–
76	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
77	Check: Does UE transmit a REGISTRATION REQUEST message not including Requested NSSAI?	–>	REGISTRATION REQUEST	3	P
78-93	Steps 5 to 20a1of the generic procedure for NR RRC_IDLE specified in TS 38.508-1 subclause 4.5.2.2-2 are performed.	–	–	–	–

9.1.5.1.3a.3.3 Specific message contents

Table 9.1.5.1.3a.3.3-1: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Configured NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present

Table 9.1.5.1.3a.3.3-2: REGISTRATION ACCEPT (step 12, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000100’B	4
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Configured NSSAI
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000100’B	4
SD	Not Present
Mapped configured SST	‘00000001’B	1
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000101’B	5
SD	Not Present
Mapped configured SST	‘00000010’B	2
Mapped configured SD	Not Present

Table 9.1.5.1.3a.3.3-2A: PDU SESSION ESTABLISHMENT ACCEPT (step 14 , Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI
Length of S-NSSAI contents	‘0000 0001’B	SST
SST	‘0000 0100’B	SST value 4

Table 9.1.5.1.3a.3.3-3: NSSAI DELETE REQUEST (step 19, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000010’	Delete Allowed NSSAI
Allowed NSSAI	000000	All PLMNs (3 Octets)
	00	3GPP access

Table 9.1.5.1.3a.3.3-4: NSSAI DELETE RESPONSE (step 20, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-5: REGISTRATION REQUEST (step 24, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000100’B	4
SD	Not Present
Mapped configured SST	‘00000001’B	1
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000101’B	5
SD	Not Present
Mapped configured SST	‘00000010’B	2
Mapped configured SD	Not Present
Note: UE may include S-NSSAI 4 or 5 or both 4 and 5 from the configured NSSAI list associated with NGC cell G.

Table 9.1.5.1.3a.3.3-6: REGISTRATION ACCEPT (step 34, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000100’B	4
SD	Not Present
Mapped configured SST	‘00000001’B	1
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000101’B	5
SD	Not Present
Mapped configured SST	‘00000010’B	2
Mapped configured SD	Not Present
Note: SS will send Allowed NSSAIs based on the Requested NSSAI sent by UE in step 24.

Table 9.1.5.1.3a.3.3-6A: PDU SESSION ESTABLISHMENT ACCEPT (step 36, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI
Length of S-NSSAI contents	‘0000 0010’B	SST
SST	‘0000 0100’B	SST value 4
Mapped configured SST	‘00000001’B	mapped configured SST value 1

Table 9.1.5.1.3a.3.3-7: NSSAI DELETE REQUEST (step 41, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000000’	Delete Default Configured NSSAI

Table 9.1.5.1.3a.3.3-8: NSSAI DELETE RESPONSE (step 42, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-9: NSSAI DELETE REQUEST (step 44, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator
Message type	‘10000110’
Delete NSSAI type	‘00000001’	Delete Configured NSSAI
Configured NSSAI	00000000	All PLMNs

Table 9.1.5.1.3a.3.3-10: NSSAI DELETE RESPONSE (step 45, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-11: NSSAI DELETE REQUEST (step 46, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000010’	Delete Allowed NSSAI
Allowed NSSAI	000000	All PLMNs (3 Octets)
	00	3GPP access

Table 9.1.5.1.3a.3.3-12: NSSAI DELETE RESPONSE (step 47, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-13: REGISTRATION REQUEST (step 51, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000001’B	1
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000001’B	SST
SST	‘00000010’B	2
SD	Not Present
Mapped configured SST	Not Present
Mapped configured SD	Not Present
Network slicing indication
Default configured NSSAI indication	1	Requested NSSAI created from default configured NSSAI
Note: UE may include either 1 or 2 or both 1 and 2 NSSAIs.

Table 9.1.5.1.3a.3.3-14: REGISTRATION ACCEPT (step 61, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
5GS registration result value	‘001’B	3GPP access
Allowed NSSAI		Note
S-NSSAI IEI		S-NSSAI value 1
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000001’B	1
SD	Not Present
Mapped configured SST	‘00000001’B
Mapped configured SD	Not Present
S-NSSAI IEI		S-NSSAI value 2
Length of S-NSSAI contents	‘00000010’B	SST and mapped configured SST
SST	‘00000010’B	2
SD	Not Present
Mapped configured SST	‘00000010’B
Mapped configured SD	Not Present
Note: SS will send Allowed NSSAIs based on the Requested NSSAI sent by UE in Step 51

Table 9.1.5.1.3a.3.3-15: NSSAI DELETE REQUEST (step 68, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000000’	Delete Default Configured NSSAI

Table 9.1.5.1.3a.3.3-16: NSSAI DELETE RESPONSE (step 69, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-17: NSSAI DELETE REQUEST (step 70, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000001’	Delete Configured NSSAI
Configured NSSAI	000000	All PLMNs (3 Octets)

Table 9.1.5.1.3a.3.3-18: NSSAI DELETE RESPONSE (step 71, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-19: NSSAI DELETE REQUEST (step 72, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10000110’
Delete NSSAI type	‘00000010’	Delete Allowed NSSAI
Allowed NSSAI	000000	All PLMNs (3 Octets)
	00	3GPP access

Table 9.1.5.1.3a.3.3-20: NSSAI DELETE RESPONSE (step 73, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.509 Table 6.7.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	1111
Skip indicator	0000
Message type	‘10100111’

Table 9.1.5.1.3a.3.3-21: REGISTRATION REQUEST (step 77, Table 9.1.5.1.3a.3.2-1)

Derivation path: TS 38.508-1 Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type value	‘001’B	Initial registration
Requested NSSAI	Not Present

9.1.5.1.4 Initial registration / 5GS services / MICO mode / TAI list handling

9.1.5.1.4.1 Test Purpose (TP)

(1)

with { The UE is in 5GMM-DEREGISTERED state and is switched off }

ensure that {

when { the UE supports MICO mode and requests the use of MICO mode}

then { the UE includes the MICO indication IE in the REGISTRATION REQUEST message }

}

(2)

with { The UE has received REGISTRATION ACCEPT message }

ensure that {

when { the REGISTRATION ACCEPT message included MICO indication IE indicating “all PLMN registration area allocated” }

then { the UE treats all TAIs in the current PLMN as a registration area and deletes its old TAI list }

}

(3)

with { The UE detecting a better NG cell in same PLMN }

ensure that {

when { the UE treats all TAIs in the current PLMN as a registration area and has deleted its old TAI list as a result of REGISTRATION ACCEPT message included MICO indication IE indicating “all PLMN registration area allocated” }

then { the UE does not perform the REGISTRATION procedure for mobility }

}

(4)

with { The UE detecting a better NG cell in a different PLMN }

ensure that {

when { the UE transmits the REGISTRATION REQUEST }

then { the UE sets the IE 5GS registration type to “mobility registration updating” and performs a REGISTRATION procedure for Mobility }

}

9.1.5.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 5.5.1.2.2 and 5.5.1.2.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.2]

…

If the UE supports MICO mode and requests the use of MICO mode, then the UE shall include the MICO indication IE in the REGISTRATION REQUEST message.

…

[TS 24.501, clause 5.5.1.2.4]

…

The AMF shall include the MICO indication IE in the REGISTRATION ACCEPT message only if the MICO indication IE was included in the REGISTRATION REQUEST message, the AMF supports and accepts the use of MICO mode. If the AMF supports and accepts the use of MICO mode, the AMF may indicate "all PLMN registration area allocated" in the MICO indication IE in the REGISTRATION ACCEPT message. If "all PLMN registration area allocated" is indicated in the MICO indication IE, the AMF shall not assign and include the TAI list in the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message included an MICO indication IE indicating "all PLMN registration area allocated", the UE shall treat all TAIs in the current PLMN as a registration area and delete its old TAI list.

…

9.1.5.1.4.3 Test description

9.1.5.1.4.3.1 Pre-test conditions

System Simulator:

– NGC Cell A, NGC Cell C and NGC Cell E are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [4].

UE:

None.

Preamble:

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

9.1.5.1.4.3.2 Test procedure sequence

Table 9.1.5.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS configures: – NGC Cell A as the "Non-suitable “Off” cell. – NGC Cell C as the "Non-suitable "Off" cell". – NGC Cell E as the "Non-suitable "Off" cell".
1	The UE is switched ON
2	The user requests enabling of MICO mode by MMI or AT command	–		–	–
3	The SS configures: – NGC Cell A as the "Serving cell". – NGC Cell C as the "Non-suitable "Off" cell". – NGC Cell E as the "Non-suitable "Off" cell".	–		–	–
4-6	The UE establishes an RRC connection by executing steps 2–4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–		–	–
7	Check: Does the UE transmit a REGISTRATION REQUEST message including IE MICO indication	–>	REGISTRATION REQUEST	1	P
8-16	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38508-1 [4] are performed	–		–	–
17	SS transmits a REGISTRATION ACCEPT message that includes IE MICO indication	<–	REGISTRATION ACCEPT	–	–
18	The SS releases the RRC Connection	–		–	–
19	The SS configures: – NGC Cell A as the "Non-suitable “Off” cell". – NGC Cell C as the "Serving cell". – NGC Cell E as the "Non-suitable “Off” cell".	–
20	Check: Does the UE transmit a RRCSetupRequest on NGC Cell C? This is checked for 60s	–>	NR RRC: RRCSetupRequest	2,3	F
21	The SS configures: – NGC Cell A as the "Non-suitable “Off” cell". – NGC Cell C as the "Non-suitable “Off” cell". – NGC Cell E as the "Serving cell".	–		–	–
	The following messages are to be observed on NGC Cell E unless explicitly stated otherwise
22-24	The UE establishes an RRC connection by executing steps 2–4 of Table 4.5.2.2-2 in TS38.508-1 [4].	–		–	–
25	Check: Does the UE transmit a REGISTRATION REQUEST message with IE 5GS registration type set to “mobility registration updating”	–>	REGISTRATION REQUEST	4	P
26-27	Steps 4–5 of Table 4.9.5.2.2-1 in TS38.508-1 [4] are performed

9.1.5.1.4.3.3 Specific message contents

Table 9.1.5.1.4.3.3-1: REGISTRATION REQUEST (step 6 Table 9.1.5.1.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
5GS registration type value	‘001’B	Initial registration	INITIAL
MICO indication	‘0000’B

Table 9.1.5.1.4.3.3-2: REGISTRATION ACCEPT (step 16 Table 9.1.5.1.4.3.2-1)

Derivation Path: TS 38.508 [4], Table 4.7.1-7
Information Element	Value/remark	Comment	Condition
MICO Indication	‘0001’B	All PLMN registration area allocated
TAI list	Not present

Table 9.1.5.1.4.3.3-3: REGISTRATION REQUEST (step 23 Table 9.1.5.1.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
5GS registration type value	‘010’B	Mobility registration updating	MOBILITY

9.1.5.1.5 Initial registration / Abnormal / Failure after 5 attempts

9.1.5.1.5.1 Test Purpose (TP)

(1)

with { The UE in 5GMM-REGISTERED-INITIATED state and T3510 timer expired }

ensure that {

when { T3511 timer expires and registration attempt counter is less than 5 }

then { UE restarts the initial registration procedure }

}

(2)

with { The UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { The NAS signalling connection is released before the REGISTRATION ACCEPT or REGISTRATION REJECT message is received }

then { UE restarts the initial registration procedure }

}

(3)

with { The UE has sent initial REGISTRAION REQUEST message }

ensure that {

when { UE receives a REGISTRATION REJECT message including 5GMM cause value #95 and the UE updates the registration counter to 5 }

then { UE deletes 5G-GUTI, last visited TAI and ngKSI, performs a PLMN selection after timer T3502 timeout }

}

9.1.5.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.5.1.1 5.5.1.2.7, and 10.2. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.1]

Additionally, the registration attempt counter shall be reset when the UE is in sub state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE, and:

– a new tracking area is entered;

– timer T3502 expires; or

– timer T3346 is started.

[TS 24.501, clause 5.5.1.2.7]

The following abnormal cases can be identified:

…

c) T3510 timeout.

The UE shall abort the registration procedure for initial registration and the NAS signalling connection, if any, shall be released locally if the initial registration request is not for emergency services. The UE shall proceed as described below.

d) REGISTRATION REJECT message, other 5GMM cause values than those treated in subclause 5.5.1.2.5, and cases of 5GMM cause value #22, if considered as abnormal cases according to subclause 5.5.1.2.5.

If the registration request is not an initial registration request for emergency services, upon reception of the 5GMM causes #95, #96, #97, #99 and #111 the UE should set the registration attempt counter to 5.

The UE shall proceed as described below.

e) Lower layer failure or release of the NAS signalling connection received from lower layers before the REGISTRATION ACCEPT or REGISTRATION REJECT message is received.

The UE shall abort the registration procedure for initial registration and proceed as described below.

…

For the cases c, d and e, the UE shall proceed as follows:

Timer T3510 shall be stopped if still running.

If the registration procedure is neither an initial registration for emergency services nor for establishing an emergency PDU session with registration type not set to "emergency registration", the registration attempt counter shall be incremented, unless it was already set to 5.

If the registration attempt counter is less than 5:

– if the initial registration request is not for emergency services, timer T3511 is started and the state is changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. When timer T3511 expires the registration procedure for initial registration shall be restarted, if still required.

If the registration attempt counter is equal to 5

– the UE shall delete 5G-GUTI, TAI list, last visited TAI, list of equivalent PLMNs and ngKSI, start timer T3502 and shall set the 5GS update status to 5U2 NOT UPDATED. The state is changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or optionally to 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5].

[TS 24.501, clause 10.2]

Table 10.2.1: Timers of 5GS mobility management – UE side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T3510

15s

5GMM-REGISTERED-INITIATED

Transmission of REGISTRATION REQUEST message

REGISTRATION ACCEPT message received or REGISTRATION REJECT message received

Start T3511 or T3502 as specified in subclause 5.5.1.2.7 if T3510 expired during registration procedure for initial registration.

Start T3511 or T3502 as specified in subclause 5.5.1.3.7 if T3510 expired during the registration procedure for mobility and periodic registration update

T3502

Default 12 min.

NOTE 1

5GMM-REGISTERED

At registration failure and the attempt counter is equal to 5

Transmission of REGISTRATION REQUEST message

Initiation of the registration procedure, if still required

T3511

10s

5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION

5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

5GMM-REGISTERED.NORMAL-SERVICE

At registration failure due to lower layer failure, T3510 timeout or registration rejected with other 5GMM cause values than those treated in subclause 5.5.1.2.5 for initial registration or subclause 5.5.1.3.5 for mobility and periodic registration

Transmission of REGISTRATION REQUEST message

5GMM-CONNECTED mode entered (NOTE 5)

Retransmission of the REGISTRATION REQUEST, if still required

9.1.5.1.5.3 Test description

9.1.5.1.5.3.1 Pre-test conditions

System Simulator:

– NGC Cell A is configured according to Table 6.3.2.2-1 in TS 38.508-1 [4].

UE:

None.

Preamble:

– The UE is in state 0-A according to TS 38.508-1 [4] Table 4.4A.2-0.

9.1.5.1.5.3.2 Test procedure sequence

Table 9.1.5.1.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell A as the "Serving cell".	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise.	–	–	–	–
2	The UE is switched on.	–	–	–	–
3-5	Steps 2-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed and the UE transmits a REGISTRATION REQUEST with IE 5GS registration type set to “initial registration”.	–>	REGISTRATION REQUEST	–	–
6	The SS waits 25 seconds (15 seconds T3510 and 10 seconds T3511). (UE’s registration attempt counter = 1)	–	–	–	–
7	Check: Does the UE transmit a REGISTRATION REQUEST message with IE 5GS registration type set to “initial registration”?	–>	REGISTRATION REQUEST	1	P
8	The SS releases the RRC connection.	–	–	–	–
8A	The SS waits 10 seconds (T3511). (UE’s registration attempt counter = 2)
9-11	Steps 2-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed. Check: Does the UE transmit a REGISTRATION REQUEST message with IE 5GS registration type set to “initial registration”?	–>	REGISTRATION REQUEST	2	P
12-16	Steps 5-9 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
17	The SS transmits a REGISTRATION REJECT with cause #95 (Semantically incorrect message). (UE’s registration attempt counter = 5)	<–	REGISTRATION REJECT	–	–
17A	The SS releases the RRC connection.	–	–	–	–
	EXCEPTION: Steps 17Aa1 and 17Ab1 describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported
17Aa1	IF the UE transmits a REGISTRATION REQUEST message with IE 5GS registration type set to “initial registration” 10s after step 17A.	–>	REGISTRATION REQUEST	–	–
17Ab1	ELSE Check: Does the UE transmit a REGISTRATION REQUEST message with IE 5GS registration type set to “initial registration” after 12 minutes after step 17A? (UE’s registration attempt counter has been reset to 0 after expiry of T3502)	–>	REGISTRATION REQUEST	3	P
18	Void	–	–	–	–
19-34	Steps 5-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.5.3.3 Specific message contents

Table 9.1.5.1.5.3.3-1: REGISTRATION REJECT (step 17, Table 9.1.5.1.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘01011111’B	Cause #95 (Semantically incorrect message)

Table 9.1.5.1.5.3.3-2: REGISTRATION REQUEST (step 18, Table 9.1.5.1.5.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	no key is available
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111"
5GS mobile identity	SUCI
Last visited registered TAI	Not present

Table 9.1.5.1.5.3.3-3: Void

9.1.5.1.6 Initial registration / Rejected / Illegal UE

9.1.5.1.6.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED-INITIATED state }

ensure that {
when { the SS sends a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value #3 (Illegal UE) }

then { the UE deletes the stored 5G-GUTI, last visited registered TAI and ngKSI, deletes the list of equivalent PLMNs and enter state 5GMM-DEREGISTERED, the USIM is considered invalid until switching off the UE }

}

9.1.5.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 clause 5.5.1.2.5.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

If the initial registration request is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a back-off timer T3346.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

#3 (Illegal UE); or

#6 (Illegal ME).

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall consider the USIM as invalid for 5GS services until switching off or the UICC containing the USIM is removed. The UE shall delete the list of equivalent PLMNs and enter the state 5GMM-DEREGISTERED.

If the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301 [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed.

If the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value.

9.1.5.1.6.3 Test description

9.1.5.1.6.3.1 Pre-test conditions

System Simulator:

– NGC Cell A is configured according to table 6.3.2.2-1 in TS 38.508-1 [4].

UE:

None.

Preamble:

– The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4].

9.1.5.1.6.3.2 Test procedure sequence

Table 9.1.5.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC cell A as the "Serving cell".	–	–	–	–
–	The following messages are to be observed on NGC Cell A unless explicitly stated otherwise.	–	–	–	–
2	The UE is switched on.	–	–	–	–
3-14	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	The SS transmits a REGISTRATION REJECT message with the 5GMM cause set to ‘Illegal UE’ as specified.	<–	5GMM: REGISTRATION REJECT	–	–
16	The SS releases the RRC connection.	–	–	–	–
17	Check: Does the UE transmit an REGISTRATION REQUEST message on NGC cell A in the next 30 seconds?	–>	5GMM: REGISTRATION REQUEST	1	F
18	The user initiates Registration Request by MMI or by AT command.	–	–	–	–
19	Check: Does the UE transmit the REGISTRATION REQUEST message in the next 30 seconds?	–>	5GMM: REGISTRATION REQUEST	1	F
20	If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
21	The UE is brought back to operation or the USIM is inserted. The UE is powered on or switched on.	–	–	–	–
22	Check: Does the UE transmit an REGISTRATION REQUEST message on NGC Cell A?	–>	5GMM: REGISTRATION REQUEST	1	P
23-38	Steps 5-20 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NGC Cell A.	–	–	–	–

9.1.5.1.6.3.3 Specific message contents

Table 9.1.5.1.6.3.3-1: REGISTRATION REJECT (step 15, Table 9.1.5.1.6.3.2-1)

Derivation Path: TS 38.508-1 Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘0000 0011’B	Illegal UE

Table 9.1.5.1.6.3.3-2: REGISTRATION REQUEST (step 22, Table 9.1.5.1.6.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	no key is available (UE to network)
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111"
5GS mobile identity	The valid SUCI	.
Last visited registered TAI	Not present

9.1.5.1.7 Void

9.1.5.1.8 Initial registration / Rejected / Serving network not authorized

9.1.5.1.8.1 Test Purpose (TP)

(1)

with { The UE has sent initial REGISTRATION REQUEST message }

ensure that {

when { the UE receives a REGISTRATION REJECT with cause #73 (Serving network not authorized) }

then { the UE stores the PLMN identity in the "forbidden PLMN list" and does not attempt to register on a cell belong to that PLMN }

}

9.1.5.1.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.5.1.2.5.

[TS 24.501, clause 5.5.1.2.5]

[Rel-15]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

#3 (Illegal UE); or

#6 (Illegal ME).

….

#73 (Serving network not authorized).

The UE shall set the 5GS update status to 5U2 NOT UPDATED, reset the registration attempt counter, store the PLMN identity in the "forbidden PLMN list" and enter state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5].

[Rel-16]

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

#3 (Illegal UE); or

#6 (Illegal ME).

…

#73 (Serving network not authorized).

This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, reset the registration attempt counter, store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A, and enter state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value.

If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.

9.1.5.1.8.3 Test description

9.1.5.1.8.3.1 Pre-test conditions

System Simulator:

– 3 NGC Cells NGC Cell E, NGC Cell I and NGC Cell A are configured as specified in TS 38.508-1 [4] table 6.3.2.2-1 and table 6.3.2.2-3.

UE:

– The UE is in Automatic PLMN selection mode.

Preamble:

– NGC Cell E is set to “Serving Cell”.

– NGC Cell I is set to “Non-suitable "Off" cell”.

– NGC Cell A is set to “Non-suitable "Off" cell”.

– The UE is in state 0N-B with a successful registration on NGC Cell E according to 38.508-1 [4].

9.1.5.1.8.3.2 Test procedure sequence

Table 9.1.5.1.8.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on	–	–	–	–
2-9	Steps 2-9 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed on NGC Cell E.	–	–	–	–
10	The SS transmits a REGISTRATION REJECT with cause #73 (Serving network not authorized).	<–	REGISTRATION REJECT	–	–
11	The SS releases the RRC connection	–	–	–	–
11A	The SS configures – NGC Cell I as “Suitable neighbour cell”	–	–	–	–
12	Check: Does the UE send in the next 30 sec a request for RRC connection establishment on Cell E or Cell I.	–>	NR RRC: RRCSetupRequest	1	F
13	The SS configures – NGC Cell A as “Serving Cell”	–	–	–	–
14	Check: Does the UE perform Registration procedure on NGC Cell A as specified in TS 38.508-1 [4] subclause 4.5.2? (Note 1)	–	–	1	P
14A	Switch off procedure in RRC_IDLE specified in TS 38.508-1 subclause 4.9.6.1 is performed.	–	–	–	–
15	The SS configures – NGC Cell A as “Non-suitable "Off" cell” – NGC Cell I as “Non-suitable "Off" cell”	–	–	–	–
15A	The UE is brought back to operation or the USIM is inserted. The UE is powered on or switched on.	–	–	–	–
16	Set the UE in manual PLMN selection mode or request a PLMN search.	–	–	–	–
17	The user selects the PLMN of NGC Cell E.	–	–	–	–
18	The UE performs Registration procedure on NGC Cell E as specified in TS 38.508-1 [4] subclause 4.5.2.	–	–	–	–
19	Set the UE in Automatic PLMN selection mode.	–	–	–	–
20	Wait for 300s to allow the UE to switch to automatic PLMN selection mode.	–	–	–	–
Note 1: For Rel-16 or later Releases UE, the REGISTRATION REQUEST message shall be sent without integrity protection.

9.1.5.1.8.3.3 Specific message contents

Table 9.1.5.1.8.3.3-1: REGISTRATION REJECT (step 10 Table 9.1.5.1.8.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘01001001’B	Cause #73 (Serving network not authorized)

9.1.5.1.9 Initial registration / Abnormal / Change of cell into a new tracking area

9.1.5.1.9.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED-INITIATED state }

ensure that {
when { the UE changes into a new tracking area before UE receives the REGISTRATION ACCEPT message }

then { the UE shall abort the registration procedure for initial registration and re-initiate it immediately }

}

9.1.5.1.9.2 Conformance requirements

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

[TS 24.501, clause 5.5.1.2.7]

The following abnormal cases can be identified:

…

h) Change of cell into a new tracking area.

If a cell change into a new tracking area occurs before the registration procedure for initial registration is completed, the registration procedure for initial registration shall be aborted and re-initiated immediately. If a tracking area border is crossed when the REGISTRATION ACCEPT message has been received but before a REGISTRATION COMPLETE message is sent, the registration procedure for initial registration shall be re-initiated. If a 5G-GUTI was allocated during the registration procedure, this 5G-GUTI shall be used in the registration procedure.

9.1.5.1.9.3 Test description

9.1.5.1.9.3.1 Pre-test conditions

System Simulator:

– NGC Cell A is configured according to Table 6.3.2.2-1 in TS 38.508-1 [4].

– The defaultPagingCycle in SIB1 of NGC Cell A shall be set as rf32.

UE:

– the UE is previously registered on NGC, and when on NGC, the UE is last authenticated and 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) according to TS 38.508-1 [4].

9.1.5.1.9.3.2 Test procedure sequence

Table 9.1.5.1.9.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Void.	–	–	–	–
2	The UE is switched on.	–	–	–	–
3-14	Steps 2–13 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed.	–	–	–	–
15	SS does not send REGISTRATION ACCEPT to the UE and update TAC value in SIB1.	–	–	–	–
15A	Void.	–	–	–	–
16	The SS notifies the UE of change of System Information on NGC Cell A by sending Short Message on PDCCH using P-RNTI.	<–	NR RRC: Paging	–	–
16A-28	Void.	–	–	–	–
29	Check: Does the UE transmit an REGISTRATION REQUEST message before the 15 second timer (T3510) started in step 5 expires?	–	5GMM: REGISTRATION REQUEST	1	P
29A1	The SS transmits a REGISTRATION ACCEPT message.	<–	REGISTRATION ACCEPT	–	–
29A2	The UE transmits a REGISTRATION COMPLETE message.	–>	REGISTRATION COMPLETE	–	–
30-32	Steps 19a1-19Aa2 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.9.3.3 Specific message contents

Table 9.1.5.1.9.3.3-0A: SIB1 of NGC Cell A (preamble)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
servingCellConfigCommon SEQUENCE {
pcch-Config SEQUENCE {
defaultPagingCycle	rf32
}
}
}

Table 9.1.5.1.9.3.3-0: SIB1 of NGC Cell A (step 15, Table 9.1.5.1.9.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-IdentityInfoList SEQUENCE {
trackingAreaCode	2
}
}
}

Table 9.1.5.1.9.3.3-1: Void

Table 9.1.5.1.9.3.3-1A: Void

Table 9.1.5.1.9.3.3-2: REGISTRATION REQUEST (step 29, Table 9.1.5.1.9.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	‘001’B	Initial registration

9.1.5.1.10 Initial registration / Rejected / PLMN not allowed

9.1.5.1.10.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { the SS sends a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value #11 (PLMN not allowed) }

then { the UE deletes any 5G-GUTI, last visited registered TAI and ngKSI, deletes the list of equivalent PLMNs, stores the PLMN identity in the "forbidden PLMN list" and performs a PLMN selection }

}

9.1.5.1.10.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501 clauses 5.5.1.2.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

…

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

…

#11 (PLMN not allowed).

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the "forbidden PLMN list". The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122 [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value.

9.1.5.1.10.3 Test description

9.1.5.1.10.3.1 Pre-test conditions

System Simulator:

– NGC cell G and NGC cell I.

– The NGC cells are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in 38.508-1 [4], except replacing NRf3 with NRf1;

UE:

– the UE is previously registered on NGC, and when on NGC, the UE is last authenticated and registered on NGC cell G using default message contents according to TS 38.508-1 [4];

Preamble:

– The UE is in state 0N-B according to TS 38.508-1 [4].

9.1.5.1.10.3.2 Test procedure sequence

Table 9.1.5.1.10.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell G as the "Serving cell". – NGC Cell I as a "Non-Suitable Off cell".	–	–	–	–
2	Void
	The following messages are to be observed on Cell G unless explicitly stated otherwise.	–	–	–	–
3	The UE is switched on.	–	–	–	–
4-11	Steps 2-9 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
12	The SS transmits an REGISTRATION REJECT message including an appropriate 5GMM cause value #11 (PLMN not allowed).	<–	5GMM: REGISTRATION REJECT	–	–
13	The SS releases the RRC connection.	–	–	–	–
14	Check: Does the UE transmit an REGISTRATION REQUEST message on NGC cell G in the next 90 seconds?	–>	5GMM: REGISTRATION REQUEST	1	F
15	The generic test procedure in TS 38.508-1 Table 4.9.6.4-1 of Switch off procedure in State DEREGISTERED are performed.	–	–	–	–
16	The UE is brought back to operation or the USIM is inserted. The UE is powered on or switched on.	–	–	–	–
17	Check: Does the UE transmit an REGISTRATION REQUEST message in the next 30 seconds?	–>	5GMM: REGISTRATION REQUEST	1	F
18	The SS configures: -NGC Cell G as the "Serving cell" -NGC Cell I as a "Suitable neighbour cell".	–	–	–	–
19	Void
–	The following messages are to be observed on NGC Cell I unless explicitly stated otherwise.	–	–	–	–
20-22	The UE establishes RRC connection by executing steps 2-4 of Table 4.5.2.2-2 in TS 38.508-1 [4].	–	–	–	–
23	Check: Does the UE transmit an REGISTRATION REQUEST message as specified?	–>	5GMM: REGISTRATION REQUEST	1	P
24-39a1	Steps 5-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
40	The generic test procedure in TS 38.508-1 Table 4.9.6.3-1 of Switch off procedure in RRC_CONNECTED are performed.	–	–	–	–
40A	The SS configures: -NGC Cell G as the "Serving cell" -NGC Cell I as a "Non-Suitable "off" cell ".
40B	The UE is brought back to operation or the USIM is inserted. The UE is powered on or switched on.	–	–	–	–
40C	The user sets the UE in manual PLMN selection mode or requests a PLMN search.	–	–	–	–
41	The user selects PLMN of NGC Cell I.	–	–	–	–
42-60a1	Steps 2 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2 are performed on NGC Cell G.	–	–	–	–
61	The user sets the UE in Automatic PLMN selection mode.	–	–	–	–
62	Wait for 300s to allow the UE to switch to automatic PLMN selection mode.	–	–	–	–

9.1.5.1.10.3.3 Specific message contents

Table 9.1.5.1.10.3.3-1: Message REGISTRATION REJECT (step 12, Table 9.1.5.1.10.3.2-1)

Derivation path: TS 38.508-1 [4],table 4.7.1-9
Information Element	Value/Remark	Comment	Condition
5GMM cause	‘00001011’B	#11 "PLMN not allowed"

Table 9.1.5.1.10.3.3-2: Message REGISTRATION REQUEST (step 23, Table 9.1.5.1.10.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	no key is available (UE to network)
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111"
5GS mobile identity	The valid SUCI	.
Last visited registered TAI	Not present

9.1.5.1.11 Initial registration / Rejected / Tracking area not allowed

9.1.5.1.11.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { the SS sends a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value #12 (Tracking area not allowed)}

then { the UE deletes any 5G-GUTI, last visited registered TAI and ngKSI, stores the current TAI in the list of "5GS forbidden tracking areas for regional provision of service". }

}

(2)

with { the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE state and the TAI of the current cell belongs to the list of "forbidden tracking areas for regional provision of service"}

ensure that {

when { the UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas for regional provision of service"}

then { the UE attempts to registration }

}

(3)

with { the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE state and the list of "forbidden tracking areas for regional provision of service" contains more than one TAI}

ensure that {

when { the UE selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas for regional provision of service" }

then { the UE does not attempt to registration }

}

(4)

with { the UE is switched off or the UICC containing the USIM is removed }

ensure that {

when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden tracking areas for regional provision of service" before the UE was switched off or the USIM is inserted again on that cell }

then { UE performs registration on that cell }

}

9.1.5.1.11.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501, clauses 5.5.1.2.5, 5.1.3.2.2.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

…

#12 (Tracking area not allowed).

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter.

The UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE.

[TS 24.501, clause 5.1.3.2.2]

In order to describe the detailed UE behaviour, the 5GS update (5U) status pertaining to a specific subscriber is defined.

If the UE is not SNPN enabled or the UE is not operating in SNPN access mode (see 3GPP TS 23.501 [8]), the 5GS update status is stored in a non-volatile memory in the USIM if the corresponding file is present in the USIM, else in the non-volatile memory in the ME, as described in annex C.

If the UE is operating in SNPN access mode, the 5GS update status for each SNPN whose SNPN identity is included in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122 [5]) is stored in the non-volatile memory in the ME as described in annex C.

The 5GS update status value is changed only after the execution of a registration, network-initiated de-registration, 5GS based primary authentication and key agreement, service request or paging procedure.

5U1: UPDATED

The last registration attempt was successful.

5U2: NOT UPDATED

The last registration attempt failed procedurally, e.g. no response or reject message was received from the AMF.

5U3: ROAMING NOT ALLOWED

The last registration, service request, or registration for mobility or periodic registration update attempt was correctly performed, but the answer from the AMF was negative (because of roaming or subscription restrictions).

[TS 24.501, clause 5.3.13]

The UE shall store a list of "5GS forbidden tracking areas for roaming", as well as a list of "5GS forbidden tracking areas for regional provision of service". Within the 5GS, these lists are managed independently per access type, i.e., 3GPP access or non-3GPP access. These lists shall be erased when

a) the UE is switched off or the UICC containing the USIM is removed or an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated; and

b) periodically (with a period in the range 12 to 24 hours).

Over 3GPP access, when the lists are erased, the UE performs cell selection according to 3GPP TS 38.304 [28]. A tracking area shall be removed from the list of "5GS forbidden tracking areas for roaming", as well as the list of "5GS forbidden tracking areas for regional provision of service", if the UE receives the tracking area in the TAI list or the Service area list of "allowed tracking areas" in REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. The UE shall not remove the tracking area from "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" if the UE is registered for emergency services.

In N1 mode, the UE shall update the suitable list whenever a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message is received with the 5GMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking area".

Each list shall accommodate 40 or more TAIs. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted.

9.1.5.1.11.3 Test description

9.1.5.1.11.3.1 Pre-test conditions

System Simulator:

– NGC Cell A (home PLMN) and NGC Cell B (home PLMN, another TA) are configured according to Table 6.3.2.2-1 in TS 38.508-1 [4].

– System information combination NR-2 in accordance with TS 38.508-1 [4] sub-clause 4.4.3.1.2 is used in NGC Cell A and NGC Cell B.

– The UE is last authenticated and registered on NGC Cell A.

Preamble:

– The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4].

9.1.5.1.11.3.2 Test procedure sequence

Table 9.1.5.1.11.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGC Cell A as the "Serving cell ". – NGC Cell B as “Non-suitable "Off" cell”.	–	–	–	–
2	The UE is switched on.	–	–	–	–
3-14	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	The SS transmits a REGISTRATION REJECT message, 5GMM cause value = #12 "Tracking area not allowed".	<–	REGISTRATION REJECT	–	–
16	The SS releases the RRC connection.	–	–	–	–
17	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell A in the next 30 seconds?	–>	REGISTRATION REQUEST	1	F
18	The SS reconfigures: – NGC cell B as the "Serving cell". – NGC cell A as a "Non-suitable "Off" cell".	–	–	–	–
19	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell B?	–>	REGISTRATION REQUEST	1,2	P
20-26	Steps 5 to 11 from procedure in TS 38.508-1 [4] Table 4.5.2.2-2 are performed.	–	–	–	–
27	The SS transmits a REGISTRATION REJECT message, 5GMM cause value = #12 " "Tracking area not allowed".	<–	REGISTRATION REJECT	–	–
28	The SS releases the RRC connection.	–	–	–	–
28A	The SS reconfigures: – NGC cell A as a "Suitable neighbour intra-frequency cell".	–	–	–	–
29	Check: Does the UE transmit the REGISTRATION REQUEST message in the next 30 seconds on NGC Cell A or NGC Cell B?	–>	REGISTRATION REQUEST	1,3	F
30	Switch off UE in State Deregistered as described in TS38.508-1 [4] subclause 4.9.6.4.	–	–	–	–
31	The SS reconfigures: – NGC cell A as the "Serving cell". – NGC cell B as “Non-suitable "Off" cell".	–	–	–	–
32	Switch on UE.	–	–	–	–
33	Check: Does the UE transmit a REGISTRATION REQUEST message on NGC Cell A?	–>	REGISTRATION REQUEST	4	P
34-49a1	Steps 5-20a1 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.11.3.3 Specific message contents

Table 9.1.5.1.11.3.3-1: REGISTRATION REJECT (step 15, step 27, Table 9.1.5.1.11.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘00001100’B	#12 “Tracking area not allowed”

Table 9.1.5.1.11.3.3-2: REGISTRATION REQUEST (step 19, step33, Table 9.1.5.1.11.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	no key is available
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111"
5GS mobile identity	The valid SUCI	Only SUCI is available.
Last visited registered TAI	Not present

9.1.5.1.12 Initial registration / Rejected / Roaming not allowed in this tracking area

9.1.5.1.12.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED-INITIATED state }

ensure that {

when { the SS sends a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value #13 (Roaming not allowed in this tracking area)

then { the UE deletes any 5G-GUTI, last visited registered TAI and ngKSI, deletes the list of equivalent PLMNs, stores the current TAI in the list of "5GS forbidden tracking areas for roaming" }

}

(2)

with { the initial registration request cannot be accepted by the network }

ensure that {

when { the SS sends a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value #13 (Roaming not allowed in this tracking area)}

then { The UE performs a PLMN selection }

}

(3)

with { the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH state and the TAI of the current cell belongs to the list of "forbidden tracking areas for roaming"}

ensure that {

when { the UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas for roaming"}

then { the UE attempts to registration }

}

(4)

with { the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH state and the list of "forbidden tracking areas for roaming" contains more than one TAI}

ensure that {

when { the UE selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas for roaming" }

then { the UE does not attempt to registration }

}

(5)

with { the UE is switched off or the UICC containing the USIM is removed }

ensure that {

when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden tracking areas for roaming" before the UE was switched off or the USIM is inserted again on that cell }

then { UE performs registration on that cell }

}

9.1.5.1.12.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.501 clauses 5.5.1.2.5, 5.1.3.2.1, 5.1.3.2.2, TS 23.122 clauses 3.1.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

…

#13 (Roaming not allowed in this tracking area).

The UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-DEREGISTERED.PLMN-SEARCH. The UE shall perform a PLMN selection according to 3GPP TS 23.122 [5].

…

[TS 24.501, clause 5.1.3.2.1.3.3]

The sub state 5GMM-DEREGISTERED.LIMITED-SERVICE is chosen in the UE, when it is known that a selected cell for 3GPP access or TA for non-3GPP access is unable to provide normal service (e.g. the selected cell over 3GPP access is in a forbidden PLMN or is in a forbidden tracking area or TA for non-3GPP access is forbidden).

[TS 24.501, clause 5.1.3.2.1.3.5]

The sub state 5GMM-DEREGISTERED.PLMN-SEARCH is chosen in the UE, if the UE is searching for PLMNs. This sub state is left either when a cell has been selected (the new sub state is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment (the new sub state is NO-CELL-AVAILABLE).

This sub state is not applicable to non-3GPP access.

[TS 24.501, clause 5.1.3.2.2]

In order to describe the detailed UE behaviour, the 5GS update (5U) status pertaining to a specific subscriber is defined.

5U1: UPDATED

The last registration attempt was successful.

5U2: NOT UPDATED

The last registration attempt failed procedurally, e.g. no response or reject message was received from the AMF.

5U3: ROAMING NOT ALLOWED

[TS 23.122, clause 3.1]

The tracking area is added to the list of "5GS forbidden tracking areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to a tracking area which is not in the "5GS forbidden tracking areas for roaming" list.

9.1.5.1.12.3 Test description

9.1.5.1.12.3.1 Pre-test conditions

System Simulator:

– NGC cell C (MCC/MNC=MCC/MNC in USIM), NGC cell E (visited PLMN, mcc=002, mnc=101) and NGC cell I (visited PLMN, mcc=002, mnc=101, another TA) are configured are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [4], except replacing NRf3 with NRf2.

UE:

– The UE is last authenticated and registered on NGC Cell E.

Preamble:

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

9.1.5.1.12.3.2 Test procedure sequence

Table 9.1.5.1.12.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NGCCell E as the "Serving cell". – Other NGC cells as "Non-suitable "Off" cell".	–	–	–	–
2	The UE is switched on.	–	–	–	–
3-14	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	The SS transmits a REGISTRATION REJECT message, 5GMM cause value = #13 " roaming not allowed in this tracking area ".	<–	REGISTRATION REJECT	–	–
16	The SS releases the RRC connection.	–	–	–	–
17	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell E in the next 30 seconds?	–>	REGISTRATION REQUEST	1	F
18	The SS reconfigures: – NGC cell I as the "Serving cell". – NGC cell E as a " Non-suitable "Off" cell", – NGC cell C as "Non-suitable "Off" cell".	–	–	–	–
19	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell I?	–>	REGISTRATION REQUEST	1,3	P
20-26	Steps 5 to 11 from procedure in TS 38.508-1 [4] Table 4.5.2.2-2 are performed.	–	–	–	–
27	The SS transmits a REGISTRATION REJECT message, 5GMM cause value = #13 " roaming not allowed in this tracking area ".	<–	REGISTRATION REJECT	–	–
28	The SS releases the RRC connection.	–	–	–	–
29	Check: Does the UE transmit the REGISTRATION REQUEST message in the next 30 seconds on NGC cell I?	–>	REGISTRATION REQUEST	4	F
30	Switch off UE in State Deregistered as described in TS38.508-1 [4] subclause 4.9.6.4.	–	–	–	–
31	The SS reconfigures: – NGC cell E as the "Serving cell". – Other NGC cells as "Non-suitable "Off" cell".	–	–	–	–
32	Switch on UE.	–	–	–	–
33	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell E?	–>	REGISTRATION REQUEST	5	P
34-42	Steps 5 to 13 from procedure in TS 38.508-1 [4] Table 4.5.2.2-2 are performed.	–	–	–	–
43	The SS transmits a REGISTRATION REJECT message, 5GMM cause value = #13 " roaming not allowed in this tracking area ".	<–	REGISTRATION REJECT	–	–
44	The SS releases the RRC connection.	–	–	–	–
45	The SS reconfigures: – NGC Cell C as the "Serving cell", – Other NGC cells as "Non-suitable "Off" cell".	–	–	–	–
46	Check: Does the UE transmit the REGISTRATION REQUEST message on NGC Cell C?	–>	REGISTRATION REQUEST	2	P
47-62a1	Steps 5–20a1 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.12.3.3 Specific message contents

Table 9.1.5.1.12.3.3-1: REGISTRATION REJECT (step 15, step 27, step 43, Table 9.1.5.1.12.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘00001101’B	#13 "roaming not allowed in this tracking area"

Table 9.1.5.1.12.3.3-2: REGISTRATION REQUEST (step 19, step 33, step 46, Table 9.1.5.1.12.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	no key is available
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111"
5GS mobile identity	The valid SUCI	Only SUCI is available.
Last visited registered TAI	Not present

9.1.5.1.13 Initial registration / Rejected / No suitable cells in tracking area

9.1.5.1.13.1 Test Purpose (TP)

(1)

with { the UE has sent initial REGISTRAION REQUEST message }

ensure that {

when { the UE receives a REGISTRATION REJECT with cause #15 (No suitable cells in tracking area)}

then { the UE sets the 5GS update status to 5U3 ROAMING NOT ALLOWED and delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI }

}

(2)

with { the UE is in 5GMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for roaming"}

ensure that {

when { the UE re-selects a cell that belongs to the TAI where UE was rejected }

then { the UE does not attempt to perform registration}

}

(3)

with { the UE has sent initial REGISTRAION REQUEST message }

ensure that {

when { the UE receives a REGISTRATION REJECT with cause #15 (No suitable cells in tracking area)}

then { the UE searches for a suitable cell in another tracking area }

}

9.1.5.1.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.5.1.2.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

#3 (Illegal UE); or

#6 (Illegal ME).

….

#15 (No suitable cells in tracking area);

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter.

The UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304 [15].

9.1.5.1.13.3 Test description

9.1.5.1.13.3.1 Pre-test conditions

System Simulator:

– 3 cells, NGC Cell A and NGC Cell B belonging to TAI-1, NGC Cell C is in TAI-2. All Cells in the same PLMN.

UE:

– None.

Preamble:

– The UE is switched OFF.

– NGC Cell A is set to “Serving Cell”.

– NGC Cell B is set to “Non-suitable "Off" cell”.

– NGC Cell C is set to “Non-suitable "Off" cell”.

9.1.5.1.13.3.2 Test procedure sequence

Table 9.1.5.1.13.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on	–	–	–	–
2-9	Steps 2-9 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed on NGC Cell A.	–	–	–	–
10	The SS transmits a REGISTRATION REJECT with cause #15 (No suitable cells in tracking area).	<–	REGISTRATION REJECT	–	–
11	The SS releases the RRC connection	–	–	–	–
12	Check: Does the UE transmit a REGISTRATION REQUEST message on NGC Cell A in the next 30 seconds?	–>	REGISTRATION REQUEST	1	F
12A	The SS configures – NGC Cell B as “Serving Cell” – NGC Cell A and Cell C as “Non-suitable "Off" cell”
12B	Check: Does the UE transmit a REGISTRATION REQUEST message on NGC Cell B in the next 30 seconds?	–>	REGISTRATION REQUEST	2	F
13	The SS configures – NGC Cell C as “Serving Cell” – NGC Cell A and Cell B as “Non-suitable "Off" cell”	–	–	–	–
14	Check: Does the UE transmit a REGISTRATION REQUEST message on NGC Cell C?	–>	REGISTRATION REQUEST	3	P
15-29	Steps 5-19a1 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed.	–	–	–	–

9.1.5.1.13.3.3 Specific message contents

Table 9.1.5.1.13.3.3-1: REGISTRATION REJECT (step 10 Table 9.1.5.1.13.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘00001111’B	Cause #15(No suitable cells in tracking area)

Table 9.1.5.1.13.3.3-2: REGISTRATION REQUEST (step 14 Table 9.1.5.1.13.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6
Information Element	Value/remark	Comment	Condition
ngKSI
NAS key set identifier	‘111’B	"No key is available"
5GS mobile identity
Type of identity	‘001’B	5GS mobile identity is SUCI, 5G-GUTI has been deleted after receiving REGISTRATION REJECT at step 10.
Last visited registered TAI	Not present	TAI has been deleted after receiving REGISTRATION REJECT at step 10.

Table 9.1.5.1.13.3.3-3: Void

9.1.5.1.14 Initial registration / Rejected / Congestion / Abnormal / T3346

9.1.5.1.14.1 Test Purpose (TP)

(1)

with { The UE has sent initial REGISTRAION REQUEST message }

ensure that {

when { UE receives a REGISTRATION REJECT with cause #22 (Congestion) with T3346 included and the UE is NOT configured for High Priority Access in the selected PLMN }

then { UE does not start the Initial registration until T3346 expires }

}

(2)

with { The UE has received initial REGISTRATION REJECT with T3346 included }

ensure that {

when { upon expiry of T3346 }

then { UE starts the Initial registration procedure }

}

(3)

Void

(4)

with { The UE has received initial REGISTRATION REJECT with T3346 included }

ensure that {

when { the timer T3346 is running and the UE detects a cell better than serving cell on a PLMN other than serving cells PLMN (S criterion for detected cell > S criterion for serving cell }

then { UE starts the Initial registration procedure on the detected cell }

}

(5)

with { The UE has received initial REGISTRATION REJECT with T3346 included }

ensure that {

when { the timer T3346 is running and the UE detects a cell better than serving cell on same PLMN as serving cell (S criterion for detected cell > S criterion for serving cell)}

then { UE starts the Initial registration procedure on the detected cell after T3346 expiry }

}

9.1.5.1.14.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 5.2.2.3.3, 5.5.1.2.5 and 5.5.1.2.7. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

#3 (Illegal UE);

#6 (Illegal ME); or

….

#22 (Congestion).

If the T3346 value IE is present in the REGISTRATION REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below; otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.2.7.

The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION.

The UE shall stop timer T3346 if it is running.

If the REGISTRATION REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE.

If the REGISTRATION REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008 [12].

The UE stays in the current serving cell and applies the normal cell reselection process. The initial registration procedure is started if still needed when timer T3346 expires or is stopped.

#27 (N1 mode not allowed).

The UE capable of S1 mode shall disable the N1 mode capability for both 3GPP access and non-3GPP access (see subclause 4.9).

Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in subclause 5.5.1.2.7.

[TS 24.501, clause 5.5.1.2.7]

The following abnormal cases can be identified:

a) Timer T3346 is running.

The UE shall not start the registration procedure for initial registration unless:

1) the UE is a UE configured for high priority access in selected PLMN; or

2) the UE needs to perform the registration procedure for initial registration for emergency services.

The UE stays in the current serving cell and applies the normal cell reselection process.

NOTE 1: It is considered an abnormal case if the UE needs to initiate a registration procedure for initial registration while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non-successful case.

[TS 24.501, clause 5.2.2.3.3]

The UE in 3GPP access:

a) …

b) …

c) shall initiate an initial registration procedure when entering a new PLMN, if timer T3346 is running and the new PLMN is not equivalent to the PLMN where the UE started timer T3346, the PLMN identity of the new cell is not in the forbidden PLMN lists and the tracking area is not in one of the lists of 5GS forbidden tracking areas;

9.1.5.1.14.3 Test description

9.1.5.1.14.3.1 Pre-test conditions

System Simulator:

– NGC Cell A, NGC Cell B and NGC Cell E are configured according to Table 6.3.2.2-1 and Table 6.3.2.2-3 in TS 38.508-1 [4].

– 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 Switched OFF (State 0-A) as per TS 38.508-1 [4] Table 4.4A.2-0.

9.1.5.1.14.3.2 Test procedure sequence

Table 9.1.5.1.14.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS configures: – NGC Cell A as the "Non-suitable “Off” cell". – NGC Cell B as the "Non-suitable "Off" cell". – NGC Cell E as the "Serving cell".	–		–
0A	The UE is Switched/Powerd ON	–	–	–	–
1-12	Steps 2-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–		–	–
13	SS transmits a REGISTRATION REJECT message with cause #22 (Congestion) and T3346 set to 3 minutes. (Note 1)	<–	REGISTRATION REJECT	–	–
14	The SS releases the RRC connection	–		–	–
15	Check: Does the UE transmit a RRCSetupRequest on NGC Cell E within T3346 of Step 13? (Note 1)	–>	NR RRC: RRCSetupRequest	1	F
16	Check: Does the UE transmit a REGISTRATION REQUEST on NGC Cell E	–>	5GMM: REGISTRATION REQUEST	2	P
17-25	Void
26	SS transmits a REGISTRATION REJECT message with cause #22 (Congestion) and T3346 set to 3 minutes. (Note 1)	<–	REGISTRATION REJECT	–	–
27	The SS releases the RRC connection	–
28	The SS configures: – NGC Cell A as the "Non-suitable "Off" cell". – NGC Cell B as the "Serving cell". – NGC Cell E as the "Non-suitable "Off" cell".
29	Check: Does the UE transmit a REGISTRATION REQUEST on NGC Cell B within T3346 of Step 26? (Note 1)	–>	5GMM: REGISTRATION REQUEST	4	P
30-31	Void	–	–	–	–
32-38	Steps 5-11 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.
39	SS transmits a REGISTRATION REJECT message with cause #22 (Congestion) and T3346 set to 3 minutes. (Note 1)	<–	REGISTRATION REJECT	–	–
40	The SS releases the RRC connection	–		–	–
41	The SS configures: – NGC Cell A as the "Serving cell". – NGC Cell B as the "Non-suitable "Off" cell". – NGC Cell E as the "Non-suitable "Off" cell".
42	Check: Does the UE transmit a RRCSetupRequest on NGC Cell A within T3346 of Step 39? (Note 1)	–>	NR RRC: RRCSetupRequest	5	F
43	Check: Does the UE transmit a REGISTRATION REQUEST on NGC Cell A	–>	5GMM: REGISTRATION REQUEST	5	P
44-74b1	Void	–	–	–	–
75-90a1	Steps 5-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
Note 1: T3346 is set to 3 minutes. This is checked for 3 minutes less tolerance.

9.1.5.1.14.3.3 Specific message contents

Table 9.1.5.1.14.3.3-1: REGISTRATION REJECT (steps 13, 26, 39 Table 9.1.5.1.14.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-9
Information Element	Value/remark	Comment	Condition
5GMM cause	‘00010110’B	Cause #22 (Congestion)
T3346 Value	‘00100011’B	3 minutes

Table 9.1.5.1.14.3.3-2: Void

9.1.5.1.15 Initial registration / Success / Extended and spare fields in CAG information list

9.1.5.1.15.1 Test Purpose (TP)

with { UE is powered on and has sent a REGISTRATION REQUEST message }

ensure that {

when { UE receives extended and spare fields in CAG information list IE in REGISTRATION ACCEPT that it does not comprehend }

then { the UE ignores the contents of these octets and transmits REGISTRATION COMPLETE }

}

9.1.5.1.15.2 Conformance requirements

References: the conformance requirements covered in the current TC are specified in TS 24.007 [40], clause 11.2.2.1, and TS 24.501 [22] clauses 5.5.1.2.2, 5.5.1.2.3, and 5.5.1.2.4. Unless otherwise stated these are Rel-15 requirements.

[TS 24.007, clause 11.2.2.1]

According to this description method, the IE is presented in its maximum format, i.e., T, TV, TLV or TLV-E, in a picture representing the bits in a table, each line representing an octet. Bits appear in the occidental order, i.e., from left of the page to right of the page, and from top of the page to bottom of the page.

Boxes so delimited contains typically the field name, possibly an indication of which bits in the field are in the box, and possibly a value (e.g., for spare bits).

A specific method can be used in the IE description to describe a branching structure, i.e., a structure variable according to the value of particular fields in the IE. This design is unusual outside type 4 and type 6 IEs, and as, a design rule, should be used only in type 4 and type 6 IEs.

a) The octet number of an octet within the IE is defined typically in the table. It consists of a positive integer, possibly of an additional letter, and possibly of an additional asterisk, see clause f). The positive integer identifies one octet or a group of octets.

b) Each octet group is a self-contained entity. The internal structure of an octet group may be defined in alternative ways.

…

f) Optional octets are marked with asterisks (*). As a design rule, the presence or absence of an optional octet should be determinable from information in the IE and preceding the optional octet. Care should be taken not to introduce ambiguities with optional octets.

g) At the end of the IE, additional octets may be added in later versions of the protocols also without using the mechanisms defined in c) and d). Equipment shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in the formal description of the messages and of the individual information elements only takes into account this version of the protocols.

[TS 24.501, clause 5.5.1.2.2]

The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF,

a) when the UE performs initial registration for 5GS services;

b) when the UE performs initial registration for emergency services;

c) when the UE performs initial registration for SMS over NAS; and

d) when the UE moves from GERAN to NG-RAN coverage or the UE moves from a UTRAN to NG-RAN coverage.

with the following clarifications to initial registration for emergency services:

a) the UE shall not initiate an initial registration for emergency services over the current access, if the UE is already registered for emergency services over the non-current access, unless the initial registration has to be initiated to perform handover of an existing emergency PDU session from the non-current access to the current access; and

NOTE 1: Transfer of an existing emergency PDU session between 3GPP access and non-3GPP access is needed e.g. if the UE determines that the current access is no longer available.

b) the UE can only initiate an initial registration for emergency services over non-3GPP access if it cannot register for emergency services over 3GPP access.

During initial registration the UE handles the 5GS mobile identity IE in the following order:

a) Void

c) if the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by an equivalent PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE;

d) if the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP, by any other PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE;

e) if a SUCI is available the UE shall include the SUCI in the 5GS mobile identity IE; and

f) if the UE does not hold a valid 5G-GUTI or SUCI, and is initiating the registration procedure for emergency services, the PEI shall be included in the 5GS mobile identity IE.

If the UE is operating in the dual-registration mode and it is in EMM state EMM-REGISTERED, the UE shall include the UE status IE with the EMM registration status set to "UE is in EMM-REGISTERED state".

NOTE 2: Inclusion of the UE status IE with this setting corresponds to the indication that the UE is "moving from EPC" as specified in 3GPP TS 23.502 [9].

If the last visited registered TAI is available, the UE shall include the last visited registered TAI in the REGISTRATION REQUEST message.

If the UE requests the use of SMS over NAS, the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS supported". When the 5GS update type IE is included in the REGISTRATION REQUEST for reasons other than requesting the use of SMS over NAS, and the UE does not need to register for SMS over NAS, the UE shall set the SMS requested bit of the 5GS update type IE to "SMS over NAS not supported" in the REGISTRATION REQUEST message.

If the UE supports MICO mode and requests the use of MICO mode, then the UE shall include the MICO indication IE in the REGISTRATION REQUEST message.

If the UE needs to use the UE specific DRX parameters, the UE shall include the Requested DRX parameters IE in the REGISTRATION REQUEST message.

If the UE needs to request LADN information for specific LADN DNN(s) or indicates a request for LADN information as specified in 3GPP TS 23.501 [8], the UE shall include the LADN indication IE in the REGISTRATION REQUEST message and:

– request specific LADN DNNs by including a LADN DNN value in the LADN indication IE for each LADN DNN for which the UE requests LADN information; or

– to indicate a request for LADN information by not including any LADN DNN value in the LADN indication IE.

The UE shall include the requested NSSAI containing the S-NSSAI(s) corresponding to the slice(s) to which the UE intends to register with and shall include the mapped S-NSSAI(s) for the requested NSSAI, if available, in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI for the current PLMN, the requested NSSAI shall be either: