Content for TS 24.501 Word version: 18.4.0

1… 3… 4… 4.4… 4.4.3… 4.5… 4.5.3… 4.6… 4.7… 4.9… 4.15… 5… 5.2… 5.3… 5.3.2… 5.3.7… 5.3.19… 5.4… 5.4.1.3… 5.4.2… 5.4.4… 5.4.5… 5.4.6… 5.5… 5.5.1.2.4 5.5.1.2.5… 5.5.1.3… 5.5.1.3.4 5.5.1.3.5… 5.5.2… 5.6… 5.6.2… 6… 6.1.4… 6.2… 6.3… 6.3.2… 6.3.3… 6.4… 6.4.1.4… 6.4.2… 6.5… 7… 8… 8.2.9… 8.3… 9… 9.11.2… 9.11.2.10… 9.11.3… 9.11.3.4… 9.11.3.8… 9.11.3.14… 9.11.3.18C… 9.11.3.29… 9.11.3.33… 9.11.3.39… 9.11.3.45… 9.11.3.50… 9.11.3.53A… 9.11.3.68… 9.11.3.75… 9.11.4… 9.11.4.10… 9.11.4.13… 9.11.4.16… 9.11.4.30… 9.12 10… A… B… C… D… D.6… D.6.3… D.6.8 D.7…

8.1 Overview 8.2 5GS mobility management messages 8.2.1 Authentication request 8.2.2 Authentication response 8.2.3 Authentication result 8.2.4 Authentication failure 8.2.5 Authentication reject 8.2.6 Registration request 8.2.7 Registration accept 8.2.8 Registration complete
...

8 Message functional definitions and contents p. 719

8.1 Overview p. 719

This clause defines the structure of the messages of the Layer 3 (L3) protocols defined in the present document. These are standard L3 messages as defined in TS 24.007.

Each definition given in the present clause includes:

a brief description of the message direction and use, including whether the message has:
1. Local significance, i.e. relevant only on the originating or terminating access;
2. Access significance, i.e. relevant in the originating and terminating access, but not in the network;
3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or
4. Global significance, i.e. relevant in the originating and terminating access and in the network.
a table listing the Information Elements (IE) known in the message and the order of their appearance in the message. All IEs that may be repeated are explicitly indicated (The V, LV and LV-E formatted IEs, which compose the imperative part of the message, occur before the T, TV, TLV and TLV-E formatted IEs which compose the non-imperative part of the message, see TS 24.007). In a (maximal) sequence of consecutive IEs with half octet length, the first IE with half octet length occupies bits 1 to 4 of octet N, the second IE bits 5 to 8 of octet N, the third IE bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements.
For each information element the table indicates:
1. The Information Element Identifier (IEI), in hexadecimal notation, if the IE has format T, TV, TLV or TLV-E. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-).
  
  NOTE 1:
  The same IEI can be used for different information element types in different messages of the same protocol.
  
  NOTE 2:
  If a message includes a Type 6 IE container information element, then the same IEI can be used for different information element types in the Type 6 IE container information element and in other parts of the same message.
2. The name of the information element (which may give an idea of the semantics of the element). The name of the information element followed by "IE" or "information element" is used in this technical report as reference to the information element within a message.
3. The name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 9 of the present document describing the value part of the information element.
4. The presence requirement indication (M, C, or O) for the IE as defined in TS 24.007.
5. The format of the information element (T, V, TV, LV, TLV, LV-E or TLV-E) as defined in TS 24.007.
6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol. This indication is non-normative.
subclauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the static conditions for presence or non-presence of the IEs or for both cases (see TS 24.007).

8.2 5GS mobility management messages p. 720

8.2.1 Authentication request p. 720

8.2.1.1 Message definition p. 720

The AUTHENTICATION REQUEST message is sent by the AMF to the UE to initiate authentication of the UE identity. See Table 8.2.1.1.1.

Message type:

AUTHENTICATION REQUEST

Significance:

dual

Direction:

network to UE

Table 8.2.1.1.1: AUTHENTICATION REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Authentication request message identity	Message type 9.7	M	V	1
	ngKSI	NAS key set identifier 9.11.3.32	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	ABBA	ABBA 9.11.3.10	M	LV	3-n
21	Authentication parameter RAND (5G authentication challenge)	Authentication parameter RAND 9.11.3.16	O	TV	17
20	Authentication parameter AUTN (5G authentication challenge)	Authentication parameter AUTN 9.11.3.15	O	TLV	18
78	EAP message	EAP message 9.11.2.2	O	TLV-E	7-1503

8.2.1.2 Authentication parameter RAND p. 721

Authentication parameter RAND IE is included if the AUTHENTICATION REQUEST message is used in a 5G AKA authentication procedure.

8.2.1.3 Authentication parameter AUTN p. 721

Authentication parameter AUTN IE is included if the AUTHENTICATION REQUEST message is used in a 5G AKA authentication procedure.

8.2.1.5 EAP message p. 721

EAP message IE is included if the AUTHENTICATION REQUEST message is used in an EAP based primary authentication and key agreement procedure.

8.2.2 Authentication response p. 721

8.2.2.1 Message definition p. 721

The AUTHENTICATION RESPONSE message is sent by the UE to the AMF to deliver a calculated authentication response to the network. See Table 8.2.2.1.1.

Message type:

AUTHENTICATION RESPONSE

Significance:

dual

Direction:

UE to network

Table 8.2.2.1.1: AUTHENTICATION RESPONSE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Authentication response message identity	Message type 9.7	M	V	1
2D	Authentication response parameter	Authentication response parameter 9.11.3.17	O	TLV	18
78	EAP message	EAP message 9.11.2.2	O	TLV-E	7-1503

8.2.2.2 Authentication response parameter p. 722

This IE is included if the message is sent in a 5G AKA based primary authentication and key agreement procedure.

8.2.2.3 EAP message p. 722

EAP message IE is included if the EAP message received in a related AUTHENTICATION REQUEST message was an EAP-request.

8.2.3 Authentication result p. 722

8.2.3.1 Message definition p. 722

The AUTHENTICATION RESULT message is sent by the AMF to the UE to provide result of EAP authentication of the UE identity. See Table 8.2.3.1.1.

Message type:

AUTHENTICATION RESULT

Significance:

dual

Direction:

network to UE

Table 8.2.3.1.1: AUTHENTICATION RESULT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Authentication result message identity	Message type 9.7	M	V	1
	ngKSI	NAS key set identifier 9.11.3.32	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	EAP message	EAP message 9.11.2.2	M	LV-E	6-1502
38	ABBA	ABBA 9.11.3.10	O	TLV	4-n
55	Master session key	Master session key 9.11.3.107	O	TLV	66

8.2.3.2 ABBA p. 723

This IE shall be included if the message contains an EAP message IE with an EAP-success message.

8.2.3.3 Master session key |R18| p. 723

This IE shall be included when the AUTHENTICATION RESULT message is provided to a 5G-RG that is acting on behalf of an AUN3 device if the EAP message IE is set to an EAP-success message.

8.2.4 Authentication failure p. 723

8.2.4.1 Message definition p. 723

The AUTHENTICATION FAILURE message is sent by the UE to the AMF to indicate that authentication of the network has failed. See Table 8.2.4.1.1.

Message type:

AUTHENTICATION FAILURE

Significance:

dual

Direction:

UE to network

Table 8.2.4.1.1: AUTHENTICATION FAILURE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Authentication failure message identity	Message type 9.7	M	V	1
	5GMM cause	5GMM cause 9.11.3.2	M	V	1
30	Authentication failure parameter	Authentication failure parameter 9.11.3.14	O	TLV	16

8.2.4.2 Authentication failure parameter p. 723

This IE shall be included in a 5G AKA based primary authentication and key agreement procedure if and only if the 5GMM cause was #21 "synch failure". It shall include the response to the authentication challenge from the USIM, which is made up of the AUTS parameter (see TS 33.501).

8.2.5 Authentication reject p. 723

8.2.5.1 Message definition p. 723

The AUTHENTICATION REJECT message is sent by the AMF to the UE to indicate that the authentication procedure has failed and that the UE shall abort all activities. See Table 8.2.5.1.1.

Message type:

AUTHENTICATION REJECT

Significance:

dual

Direction:

network to UE

Table 8.2.5.1.1: AUTHENTICATION REJECT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Authentication reject message identity	Message type 9.7	M	V	1
78	EAP message	EAP message 9.11.2.2	O	TLV-E	7-1503

8.2.5.2 EAP message p. 724

EAP message IE is included if the AUTHENTICATION REJECT message is used to convey EAP-failure message.

8.2.6 Registration request p. 724

8.2.6.1 Message definition p. 724

The REGISTRATION REQUEST message is sent by the UE to the AMF. See Table 8.2.6.1.1.

Message type:

REGISTRATION REQUEST

Significance:

dual

Direction:

UE to network

Table 8.2.6.1.1: REGISTRATION REQUEST message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended Protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Registration request message identity	Message type 9.7	M	V	1
	5GS registration type	5GS registration type 9.11.3.7	M	V	1/2
	ngKSI	NAS key set identifier 9.11.3.32	M	V	1/2
	5GS mobile identity	5GS mobile identity 9.11.3.4	M	LV-E	6-n
C-	Non-current native NAS key set identifier	NAS key set identifier 9.11.3.32	O	TV	1
10	5GMM capability	5GMM capability 9.11.3.1	O	TLV	3-15
2E	UE security capability	UE security capability 9.11.3.54	O	TLV	4-10
2F	Requested NSSAI	NSSAI 9.11.3.37	O	TLV	4-74
52	Last visited registered TAI	5GS tracking area identity 9.11.3.8	O	TV	7
17	S1 UE network capability	S1 UE network capability 9.11.3.48	O	TLV	4-15
40	Uplink data status	Uplink data status 9.11.3.57	O	TLV	4-34
50	PDU session status	PDU session status 9.11.3.44	O	TLV	4-34
B-	MICO indication	MICO indication 9.11.3.31	O	TV	1
2B	UE status	UE status 9.11.3.56	O	TLV	3
77	Additional GUTI	5GS mobile identity 9.11.3.4	O	TLV-E	14
25	Allowed PDU session status	Allowed PDU session status 9.11.3.13	O	TLV	4-34
18	UE's usage setting	UE's usage setting 9.11.3.55	O	TLV	3
51	Requested DRX parameters	5GS DRX parameters 9.11.3.2A	O	TLV	3
70	EPS NAS message container	EPS NAS message container 9.11.3.24	O	TLV-E	4-n
74	LADN indication	LADN indication 9.11.3.29	O	TLV-E	3-811
8-	Payload container type	Payload container type 9.11.3.40	O	TV	1
7B	Payload container	Payload container 9.11.3.39	O	TLV-E	4-65538
9-	Network slicing indication	Network slicing indication 9.11.3.36	O	TV	1
53	5GS update type	5GS update type 9.11.3.9A	O	TLV	3
41	Mobile station classmark 2	Mobile station classmark 2 9.11.3.31C	O	TLV	5
42	Supported codecs	Supported codec list 9.11.3.51A	O	TLV	5-n
71	NAS message container	NAS message container 9.11.3.33	O	TLV-E	4-n
60	EPS bearer context status	EPS bearer context status 9.11.3.23A	O	TLV	4
6E	Requested extended DRX parameters	Extended DRX parameters 9.11.3.26A	O	TLV	3-4
6A	T3324 value	GPRS timer 3 9.11.2.5	O	TLV	3
67	UE radio capability ID	UE radio capability ID 9.11.3.68	O	TLV	3-n
35	Requested mapped NSSAI	Mapped NSSAI 9.11.3.31B	O	TLV	3-42
48	Additional information requested	Additional information requested 9.11.3.12A	O	TLV	3
1A	Requested WUS assistance information	WUS assistance information 9.11.3.71	O	TLV	3-n
A-	N5GC indication	N5GC indication 9.11.3.72	O	TV	1
30	Requested NB-N1 mode DRX parameters	NB-N1 mode DRX parameters 9.11.3.73	O	TLV	3
29	UE request type	UE request type 9.11.3.76	O	TLV	3
28	Paging restriction	Paging restriction 9.11.3.77	O	TLV	3-35
72	Service-level-AA container	Service-level-AA container 9.11.2.10	O	TLV-E	6-n
32	NID	NID 9.11.3.79	O	TLV	8
16	MS determined PLMN with disaster condition	PLMN identity 9.11.3.85	O	TLV	5
2A	Requested PEIPS assistance information	PEIPS assistance information 9.11.3.80	O	TLV	3-n
3B	Requested T3512 value	GPRS timer 3 9.11.2.5	O	TLV	3
3C	Unavailability period duration	Time duration 9.11.2.19	O	TLV	5
3F	Non-3GPP path switching information	Non-3GPP path switching information 9.11.3.102	O	TLV	3
56	AUN3 indication	AUN3 indication 9.11.3.104	O	TLV	3

8.2.6.2 Non-current native NAS key set identifier p. 727

The UE shall include this IE if the UE has a valid non-current native 5G NAS security context when the UE performs an inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode and the UE uses a mapped 5G NAS security context to protect the REGISTRATION REQUEST message.

8.2.6.3 5GMM capability p. 727

The UE shall include this IE, unless the UE performs a periodic registration updating procedure.

8.2.6.4 UE security capability p. 727

The UE shall include this IE, unless the UE performs a periodic registration updating procedure.

8.2.6.5 Requested NSSAI p. 727

This IE shall be included by the UE when performing the registration procedure if the 5GS registration type IE indicates:

"initial registration", according to the conditions specified in subclause 5.5.1.2.2; or
"mobility registration updating", according to the conditions specified in subclause 5.5.1.3.2.

8.2.6.6 Last visited registered TAI p. 727

This IE shall be included if the UE holds a valid last visited registered TAI.

8.2.6.7 S1 UE network capability p. 728

A UE supporting S1 mode shall include this IE, unless the UE performs a periodic registration updating procedure.

8.2.6.8 Uplink data status p. 728

This IE shall be included if the UE has uplink user data pending to be sent or the UE has active multicast MBS session(s), unless the UE performs a periodic registration updating procedure.

8.2.6.9 PDU session status p. 728

This IE shall be included when the UE needs to indicate the PDU sessions that are associated with the access type that the message is sent over, that are active within the UE.

8.2.6.10 MICO indication p. 728

The UE may include this IE to request the use of MICO mode.

8.2.6.11 UE status p. 728

This IE shall be included if the UE in single-registration mode performs the registration procedure due to inter-system change from S1 mode to N1 mode or if the UE in dual-registration mode and EMM state EMM-REGISTERED performs initial registration.

8.2.6.12 Additional GUTI p. 728

This IE shall be included:

if the UE performs the registration procedure due to inter-system change from S1 mode to N1 mode, the UE operates in single-registration mode and the UE has a valid 5G-GUTI; or
the UE holds two valid native 5G-GUTIs and one of the valid native 5G-GUTI was assigned by the PLMN with which the UE is performing the registration.

8.2.6.13 Allowed PDU session status p. 728

This IE shall be included if the REGISTRATION REQUEST message is sent as a response to paging with the access type indicating non-3GPP access.

8.2.6.14 UE's usage setting p. 728

This IE shall be included if the UE supports IMS voice.

8.2.6.15 Requested DRX parameters p. 728

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

8.2.6.16 EPS NAS message container p. 728

The UE operating in the single-registration mode shall include this information element as specified in subclause 5.5.1.3.2 if the UE performs mobility from S1 mode to N1 mode in 5GMM-IDLE mode. The content of this message container is the complete integrity protected TRACKING AREA UPATE REQUEST message, using EPS security context.

The UE performing initial registration shall include this information element if

the UE:
1. was previously registered in S1 mode before entering state EMM-DEREGISTERED; and
2. has received an "interworking without N26 interface not supported" indication from the network; and
EPS security context and a valid 4G-GUTI are available.

The content of this message container is the complete integrity protected ATTACH REQUEST message, using EPS security context.

8.2.6.17 LADN indication p. 729

The UE shall include this information element when the UE needs to request LADN information for specific LADN DNN(s) or to indicate a request for LADN information.

8.2.6.17A Payload container type p. 729

This IE shall be included if the UE includes the Payload container IE.

8.2.6.18 Payload container p. 729

Within a PLMN, this IE shall be included if:

the UE has one or more stored UE policy sections identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN for the registration procedure for mobility and periodic registration update due to inter-system change from S1 mode to N1 mode of a UE operating in the single-registration mode or for the registration procedure for initial registration; or
the UE does not have any stored UE policy section identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN for the registration procedure for mobility and periodic registration update due to inter-system change from S1 mode to N1 mode of a UE operating in the single-registration mode or for the registration procedure for initial registration and the UE needs to send a UE policy container to the network.

Within an SNPN, this IE shall be included if:

the UE has one or more stored UE policy sections for the selected SNPN for the registration procedure for initial registration; or
the UE does not have any UE policy section for the selected SNPN for the registration procedure for initial registration and the UE needs to send a UE policy container to the network.

8.2.6.19 Network slicing indication p. 729

This IE shall be included when a requested NSSAI is included in the REGISTRATION REQUEST message and the requested NSSAI is created from the default configured NSSAI.

8.2.6.20 5GS update type p. 729

This IE shall be included when the UE is performing the registration procedure to indicate any of the following:

the UE requests the use of SMS over NAS or there is a change in the UE's requirements to use SMS over NAS;
a change in the UE's radio capability for NG-RAN; or
the UE requests CIoT 5GS optimizations.

8.2.6.21 NAS message container p. 730

This IE shall be included if the UE is sending a REGISTRATION REQUEST message as an initial NAS message, the UE has a valid 5G NAS security context and the UE needs to send non-cleartext IEs.

8.2.6.22 Requested extended DRX parameters p. 730

The UE shall include this IE if the UE needs to use extended DRX or change the extended DRX parameters.

8.2.6.23 EPS bearer context status |R16| p. 730

The UE shall include this IE if the UE operating in the single-registration mode performs inter-system change from S1 mode to N1 mode and the UE has locally deactivated EPS bearer context(s) for which interworking to 5GS is supported while the UE was in S1 mode without notifying the network.

8.2.6.24 T3324 value |R16| p. 730

The UE may include this IE during the registration update procedure if it requests to use MICO mode and use the active time timer.

8.2.6.25 Mobile station classmark 2 |R16| p. 730

This IE shall be included if the UE supports 5G-SRVCC from NG-RAN to UTRAN (see TS 23.216).

8.2.6.26 Supported codecs |R16| p. 730

This IE shall be included if the UE supports 5G-SRVCC from NG-RAN to UTRAN.

8.2.6.27 UE radio capability ID |R16| p. 730

This IE shall be included if the UE is not in NB-N1 mode, the UE supports RACS and the UE needs to signal a UE radio capability ID to the network.

8.2.6.28 Requested mapped NSSAI |R16| p. 730

This IE shall be included by the UE when the UE has a PDN connection or a PDU session to transfer to visited PLMN associated only with an S-NSSAI that is applicable in the HPLMN as specified in subclause 5.5.1.3.2.

8.2.6.29 Additional information requested |R16| p. 730

The UE shall include this IE if the UE supports ciphered broadcast assistance data and the UE needs to obtain new ciphering keys for ciphered broadcast assistance data.

8.2.6.30 Requested WUS assistance information |R16| p. 730

The UE may include this IE if:

the UE supports WUS assistance information;
the UE is not performing initial registration for emergency services; and
the UE does not have an active emergency PDU session.

8.2.6.31 Void

8.2.6.32 N5GC indication |R16| p. 731

This IE shall be included in the REGISTRATION REQUEST message when the W-AGF is acting on behalf of an N5GC device.

8.2.6.33 Requested NB-N1 mode DRX parameters |R16| p. 731

The UE shall include this IE if the UE wants to use or change the UE specific DRX parameters for NB-N1 mode.

8.2.6.34 UE request type |R17| p. 731

The UE shall include this IE if the MUSIM UE requests the release of the NAS signalling connection.

8.2.6.35 Paging restriction |R17| p. 731

The UE shall include this IE if the Request type is set to "NAS signalling connection release" in the UE request type IE and the UE requests the network to restrict paging.

8.2.6.35a Service-level-AA container |R17| p. 731

The UE shall include this IE if the UE supporting UAS services requests a registration for UAS services.

8.2.6.36 NID |R17| p. 731

The UE shall include this IE if the 5G-GUTI in the 5GS mobile identity IE was assigned by an SNPN other than the SNPN with which the UE is registering.

8.2.6.37 MS determined PLMN with disaster condition |R17| p. 731

The UE shall include this IE when the UE needs to indicate the MS determined PLMN with disaster condition determined as specified in TS 23.122.

8.2.6.38 Requested PEIPS assistance information |R17| p. 731

The UE may include this IE if the UE supports NR paging subgrouping, the UE is not performing initial registration for emergency services, is not registered for emergency services and does not have an active emergency PDU session.

8.2.6.39 Requested T3512 value |R17| p. 731

The UE may include this IE during the registration procedure if it requests to use MICO mode and T3324 IE is included, to request a particular T3512 timer value.

8.2.6.40 Unavailability period duration |R18| p. 731

This IE shall be included if an event is triggered in the UE that would make the UE unavailable for a certain period.

8.2.6.41 Non-3GPP path switching information |R18| p. 731

The UE may include this IE during the registration procedure for mobility registration update if it requests from the network to keep using the user plane resources of the old non-3GPP access during path switching to the new non-3GPP access.

8.2.6.42 AUN3 indication |R18| p. 732

This IE shall be included in the REGISTRATION REQUEST message when the 5G-RG is acting on behalf of an AUN3 device.

8.2.7 Registration accept p. 732

8.2.7.1 Message definition p. 732

The REGISTRATION ACCEPT message is sent by the AMF to the UE. See Table 8.2.7.1.1.

Message type:

REGISTRATION ACCEPT

Significance:

dual

Direction:

network to UE

Table 8.2.7.1.1: REGISTRATION ACCEPT message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Registration accept message identity	Message type 9.7	M	V	1
	5GS registration result	5GS registration result 9.11.3.6	M	LV	2
77	5G-GUTI	5GS mobile identity 9.11.3.4	O	TLV-E	14
4A	Equivalent PLMNs	PLMN list 9.11.3.45	O	TLV	5-47
54	TAI list	5GS tracking area identity list 9.11.3.9	O	TLV	9-114
15	Allowed NSSAI	NSSAI 9.11.3.37	O	TLV	4-74
11	Rejected NSSAI	Rejected NSSAI 9.11.3.46	O	TLV	4-42
31	Configured NSSAI	NSSAI 9.11.3.37	O	TLV	4-146
21	5GS network feature support	5GS network feature support 9.11.3.5	O	TLV	3-6
50	PDU session status	PDU session status 9.11.3.44	O	TLV	4-34
26	PDU session reactivation result	PDU session reactivation result 9.11.3.42	O	TLV	4-34
72	PDU session reactivation result error cause	PDU session reactivation result error cause 9.11.3.43	O	TLV-E	5-515
79	LADN information	LADN information 9.11.3.30	O	TLV-E	13-1715
B-	MICO indication	MICO indication 9.11.3.31	O	TV	1
9-	Network slicing indication	Network slicing indication 9.11.3.36	O	TV	1
27	Service area list	Service area list 9.11.3.49	O	TLV	6-114
5E	T3512 value	GPRS timer 3 9.11.2.5	O	TLV	3
5D	Non-3GPP de-registration timer value	GPRS timer 2 9.11.2.4	O	TLV	3
16	T3502 value	GPRS timer 2 9.11.2.4	O	TLV	3
34	Emergency number list	Emergency number list 9.11.3.23	O	TLV	5-50
7A	Extended emergency number list	Extended emergency number list 9.11.3.26	O	TLV-E	7-65538
73	SOR transparent container	SOR transparent container 9.11.3.51	O	TLV-E	20-n
78	EAP message	EAP message 9.11.2.2	O	TLV-E	7-1503
A-	NSSAI inclusion mode	NSSAI inclusion mode 9.11.3.37A	O	TV	1
76	Operator-defined access category definitions	Operator-defined access category definitions 9.11.3.38	O	TLV-E	3-8323
51	Negotiated DRX parameters	5GS DRX parameters 9.11.3.2A	O	TLV	3
D-	Non-3GPP NW policies	Non-3GPP NW provided policies 9.11.3.36A	O	TV	1
60	EPS bearer context status	EPS bearer context status 9.11.3.23A	O	TLV	4
6E	Negotiated extended DRX parameters	Extended DRX parameters 9.11.3.26A	O	TLV	3-4
6C	T3447 value	GPRS timer 3 9.11.2.5	O	TLV	3
6B	T3448 value	GPRS timer 2 9.11.2.4	O	TLV	3
6A	T3324 value	GPRS timer 3 9.11.2.5	O	TLV	3
67	UE radio capability ID	UE radio capability ID 9.11.3.68	O	TLV	3-n
E-	UE radio capability ID deletion indication	UE radio capability ID deletion indication 9.11.3.69	O	TV	1
39	Pending NSSAI	NSSAI 9.11.3.37	O	TLV	4-146
74	Ciphering key data	Ciphering key data 9.11.3.18C	O	TLV-E	34-n
75	CAG information list	CAG information list 9.11.3.18A	O	TLV-E	3-n
1B	Truncated 5G-S-TMSI configuration	Truncated 5G-S-TMSI configuration 9.11.3.70	O	TLV	3
1C	Negotiated WUS assistance information	WUS assistance information 9.11.3.71	O	TLV	3-n
29	Negotiated NB-N1 mode DRX parameters	NB-N1 mode DRX parameters 9.11.3.73	O	TLV	3
68	Extended rejected NSSAI	Extended rejected NSSAI 9.11.3.75	O	TLV	5-90
7B	Service-level-AA container	Service-level-AA container 9.11.2.10	O	TLV-E	6-n
33	Negotiated PEIPS assistance information	PEIPS assistance information 9.11.3.80	O	TLV	3-n
35	5GS additional request result	5GS additional request result 9.11.3.81	O	TLV	3
70	NSSRG information	NSSRG information 9.11.3.82	O	TLV-E	7-4099
14	Disaster roaming wait range	Registration wait range 9.11.3.84	O	TLV	4
2C	Disaster return wait range	Registration wait range 9.11.3.84	O	TLV	4
13	List of PLMNs to be used in disaster condition	List of PLMNs to be used in disaster condition 9.11.3.83	O	TLV	2-n
1D	Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming"	5GS tracking area identity list 9.11.3.9	O	TLV	9-114
1E	Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service"	5GS tracking area identity list 9.11.3.9	O	TLV	9-114
71	Extended CAG information list	Extended CAG information list 9.11.3.86	O	TLV-E	3-n
7C	NSAG information	NSAG information 9.11.3.87	O	TLV-E	9-3143
3D	Equivalent SNPNs	SNPN list 9.11.3.92	O	TLV	11-137
32	NID	NID 9.11.3.79	O	TLV	8
7D	Registration accept type 6 IE container	Type 6 IE container 9.11.3.98	O	TLV-E	6-65538
4B	RAN timing synchronization	RAN timing synchronization 9.11.3.95	O	TLV	3
4B	Alternative NSSAI	Alternative NSSAI 9.11.3.97	O	TLV	2-146
4F	Discontinuous coverage maximum time offset	GPRS timer 3 9.11.2.5	O	TLV	3
5B	S-NSSAI time validity information	S-NSSAI time validity information 9.11.3.101	O	TLV	23-257
3C	Unavailability period duration	Time duration 9.11.2.19	O	TLV	5
5C	Feature authorization indication	Feature authorization indication 9.11.3.105	O	TLV	3-257

8.2.7.2 5G-GUTI p. 736

This IE may be included to assign a 5G-GUTI to a UE.

8.2.7.3 Equivalent PLMNs p. 736

This IE may be included in order to assign an equivalent PLMNs list to a UE.

8.2.7.4 TAI list p. 736

This IE may be included to assign a TAI list to a UE.

8.2.7.5 Allowed NSSAI p. 736

This IE shall be included:

if:
1. one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message are allowed by the AMF for a network not supporting NSSAA;
2. one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or
3. the network slice-specific authentication and authorization has been successfully performed for one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message; or
if the initial registration request is not for onboarding services in SNPN or the UE is not registered for onboarding services in SNPN, the requested NSSAI was not included in the REGISTRATION REQUEST message or none of the requested NSSAI are allowed; and
1. the network does not support NSSAA; or
2. the network has one or more default S-NSSAIs which are not subject to network slice-specific authentication and authorization.

8.2.7.6 Rejected NSSAI p. 736

The network may include this IE to inform the UE of one or more S-NSSAIs that were included in the requested NSSAI in the REGISTRATION REQUEST message but were rejected by the network.

8.2.7.7 Configured NSSAI p. 736

The network may include this IE if the network needs to provide the UE with a new configured NSSAI for the current PLMN or SNPN and the UE is neither registering nor registered for onboarding services in SNPN.

8.2.7.8 5GS network feature support p. 736

The network may include this IE to inform the UE of the support of certain features. If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.

8.2.7.9 PDU session status p. 737

This IE shall be included when the network needs to indicate the PDU sessions that are associated with the access type the message is sent over, that are active in the network.

8.2.7.10 PDU session reactivation result p. 737

This IE shall be included:

if the Uplink data status IE is included in the REGISTRATION REQUEST message; or
if the Allowed PDU session status IE is included in the REGISTRATION REQUEST message and there is at least one PDU session indicated in the Allowed PDU session status IE for which the user-plane resources can be re-established over 3GPP access.

8.2.7.11 PDU session reactivation result error cause p. 737

This IE may be included, if the PDU session reactivation result IE is included and there exist one or more PDU sessions for which the user-plane resources cannot be re-established, to indicate the cause of failure to re-establish the user-plane resources.

8.2.7.12 LADN information p. 737

The network shall include this IE if there are valid LADN service area(s) for the subscribed DNN(s) of the UE in the current registration area.

8.2.7.13 MICO indication p. 737

The network shall include the MICO indication IE if:

the UE included the MICO indication IE in the REGISTRATION REQUEST message; and
the network supports and accepts the use of MICO mode.

8.2.7.14 Network slicing indication p. 737

This IE shall be included if the user's network slicing subscription has changed in the UDM of a PLMN or an SNPN.

8.2.7.15 Service area list p. 737

This IE may be included to assign new service area restrictions to the UE.

8.2.7.16 T3512 value p. 737

The AMF shall include this IE during a registration procedure over 3GPP access when the 5GS registration type IE does not indicate "periodic registration updating". The AMF may include this IE during the mobility and periodic registration update procedure over 3GPP access when the 5GS registration type IE indicates "periodic registration updating".

8.2.7.17 Non-3GPP de-registration timer value p. 737

This IE may be included if the network needs to indicate to the UE registered over non-3GPP access the value of a non-3GPP de-registration timer value.

8.2.7.18 T3502 value p. 737

This IE may be included to indicate a value for timer T3502.

8.2.7.19 Emergency number list p. 738

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid within the same country as in the PLMN from which this IE is received.

8.2.7.20 Extended emergency number list p. 738

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers (with URN information) valid within the same country as in the PLMN from which this IE is received or valid only in the PLMN or SNPN from which this IE is received.

8.2.7.21 SOR transparent container p. 738

This IE may be sent by the network.

8.2.7.22 EAP message p. 738

EAP message IE is included if the REGISTRATION ACCEPT message is sent as part of registration for emergency services and is used to convey EAP-failure message.

8.2.7.23 NSSAI inclusion mode p. 738

This IE shall be included if required by operatory policy.

8.2.7.24 Operator-defined access category definitions p. 738

This IE may be included to assign new operator-defined access category definitions to the UE or delete the operator-defined access category definitions at the UE side.

8.2.7.25 Negotiated DRX parameters p. 738

The network shall include this IE if the Requested DRX parameters IE was included in the REGISTRATION REQUEST message.

8.2.7.26 Non-3GPP NW policies p. 738

The AMF shall not include this IE during a registration procedure over non-3GPP access.

This IE is included if the network needs to indicate whether emergency numbers provided via non-3GPP access can be used to initiate UE detected emergency calls (see TS 24.302). If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero.

8.2.7.27 Negotiated extended DRX parameters p. 738

The network shall include the Negotiated extended DRX parameters IE if:

the UE included the Requested extended DRX parameters IE in the REGISTRATION REQUEST message; and
the network supports eDRX and accepts the use of eDRX.

8.2.7.28 T3447 value |R16| p. 738

The network may include T3447 value IE if:

the UE has indicated support for service gap control in the REGISTRATION REQUEST message; and
the 5GMM context contains a service gap time value.

8.2.7.29 T3448 value |R16| p. 739

The network may include this IE if the congestion control for transport of user data via the control plane is active and the UE supports the control plane CIoT 5GS optimizations.

8.2.7.30 T3324 value |R16| p. 739

The AMF shall include this IE if the UE has requested active time value in the REGISTRATION REQEUST message and the AMF decides to accept the use of MICO mode and the use of the active time.

8.2.7.31 EPS bearer context status |R16| p. 739

This IE shall be included when the network generated an EPS bearer context status information for the UE during the inter-system change from S1 mode to N1 mode and the network supports N26 interface.

8.2.7.32 UE radio capability ID |R16| p. 739

This IE may be included if the UE is not in NB-N1 mode, both the UE and the network support RACS and the network needs to assign a network-assigned UE radio capability ID to the UE.

8.2.7.33 UE radio capability ID deletion indication |R16| p. 739

This IE may be included if the UE is not in NB-N1 mode, both the UE and the network support RACS and the network needs to trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving PLMN or SNPN.

8.2.7.34 Pending NSSAI |R16| p. 739

The network may include this IE to inform the UE of one or more S-NSSAIs that are pending as the network slice-specific authentication and authorization procedure is not completed.

8.2.7.35 Ciphering key data |R16| p. 739

This IE is included if the network needs to send ciphering key data to the UE for ciphered broadcast assistance data.

8.2.7.36 CAG information list |R16| p. 739

This IE may be included to assign a new "CAG information list" to the UE or delete the "CAG information list" at the UE side.

8.2.7.37 Truncated 5G-S-TMSI configuration |R16| p. 739

The network shall include this IE if:

the UE is in NB-N1 mode;
the UE requests "control plane CIoT 5GS optimization" in the 5GS update type IE of REGISTRATION REQUEST message;
the AMF decides to accept the requested CIoT 5GS optimization; and
the network is configured to provide the truncated 5G-S-TMSI configuration for control plane CIoT 5GS optimizations.

8.2.7.38 Negotiated NB-N1 mode DRX parameters |R16| p. 740

The network shall include the Negotiated NB-N1 mode DRX parameters IE if the requested NB-N1 mode DRX parameters IE was included in the REGISTRATION REQUEST message.

8.2.7.39 Negotiated WUS assistance information |R16| p. 740

The network shall include the Negotiated WUS assistance information IE if:

the UE supports WUS assistance information;
the AMF supports and accepts the use of WUS assistance information;
the UE is not performing the initial registration for emergency services; and
the UE does not have an active emergency PDU session.

8.2.7.40 Extended rejected NSSAI |R17| p. 740

If the UE supports Extended rejected NSSAI, the network may include this IE to inform the UE of one or more S-NSSAIs that were included in the requested NSSAI in the REGISTRATION REQUEST message but were rejected by the network.

8.2.7.41 Service-level-AA container |R17| p. 740

The network shall include this IE if the UUAA procedure is triggered for the UE supporting UAS services. The network may include this IE if there is a valid successful UUAA result for the UE in the UE 5GMM context upon a registration for UAS services is requested from the UE.

8.2.7.42 Negotiated PEIPS assistance information |R17| p. 740

The network shall include the Negotiated PEIPS assistance information IE if:

the UE supports NR paging subgrouping;
the AMF supports and accepts the use of PEIPS assistance information for the UE; and
the UE is not performing initial registration for emergency services and does not have an active emergency PDU session.

8.2.7.43 5GS additional request result |R17| p. 740

The network may include this IE to inform the UE about the result of additional request.

8.2.7.44 NSSRG information |R17| p. 740

This IE may be included to provide NSSRG information associated with the configured NSSAI.

8.2.7.45 Disaster roaming wait range |R17| p. 740

This IE may be included to assign a new disaster roaming wait range to the UE.

8.2.7.46 Disaster return wait range |R17| p. 740

This IE may be included to assign a new disaster return wait range to the UE.

8.2.7.47 List of PLMNs to be used in disaster condition |R17| p. 741

This IE may be included by an allowed PLMN to assign a new "list of PLMN(s) to be used in disaster condition" associated with the serving PLMN to the UE.

8.2.7.48 Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" |R17| p. 741

This IE is included to indicate the forbidden TAI(s) to be stored in the list of "5GS forbidden tracking areas for roaming". This IE is included only if the message is sent via satellite NG-RAN access.

8.2.7.49 Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" |R17| p. 741

This IE is included to indicate the forbidden TAI(s) to be stored in the list of "5GS forbidden tracking areas for regional provision of service". This IE is included only if the message is sent via satellite NG-RAN access.

8.2.7.50 Extended CAG information list |R17| p. 741

If the UE supports Extended CAG information list, the network may include this IE to assign a new "CAG information list" to the UE or delete the "CAG information list" at the UE side.

8.2.7.51 NSAG information |R17| p. 741

If the UE has set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message over 3GPP access, the network may include this IE to provide NSAG information to the UE. Otherwise, the network shall not include this IE (see the 'comprehension required' scheme in subclause 11.2.5 of TS 24.007).

8.2.7.52 Equivalent SNPNs |R18| p. 741

This IE may be included in order to assign an equivalent SNPNs list to a UE, by an AMF of an SNPN.

8.2.7.53 NID |R18| p. 741

This IE shall be included if the UE supports equivalent SNPNs and the serving SNPN changes.

8.2.7.54 Registration accept type 6 IE container |R18| p. 741

8.2.7.54.1 General p. 741

This information element may be included only if the network knows that the UE will not treat this IE as unknown 'comprehension required' IE. Otherwise, the network shall not include this IE (see the 'comprehension required' scheme in subclause 11.2.5 of TS 24.007).

In this version of the specification, only the transfer of the information elements specified in Table 8.2.7.54.1.1 is supported in the Registration accept type 6 IE container information element in the present message. For the handling of an information element with an IEI not listed in Table 8.2.7.54.1.1, i.e., with an IEI unknown in the Registration accept type 6 IE container information element, see subclause 7.6.4.1.

Table 8.2.7.54.1.1: Information elements and IEIs for the Registration accept type 6 IE container

IEI	Information Element	Type/Reference	Presence	Format	Length
01	Extended LADN information	Extended LADN information 9.11.3.96	O	TLV-E	15-1787
TBD	S-NSSAI location validity information	S-NSSAI location validity information 9.11.3.100	O	TLV-E	TBD
04	Partially allowed NSSAI	Partial NSSAI 9.11.3.103	O	TLV-E	13-808
05	Partially rejected NSSAI	Partial NSSAI 9.11.3.103	O	TLV-E	13-808

8.2.7.54.2 Extended LADN information p. 742

The network shall include this IE if the UE supports LADN per DNN and S-NSSAI and there are valid LADN service area(s) for the subscribed DNN(s) of the UE and S-NSSAI associated with the LADN in the current registration area.

8.2.7.54.3 S-NSSAI location validity information p. 742

The network may include this IE to update the S-NSSAI location validity information.

8.2.7.54.4 Void

8.2.7.54.5 Partially allowed NSSAI p. 742

The network may include this IE to assign a partially allowed NSSAI to the UE.

8.2.7.54.6 Partially rejected NSSAI p. 742

The network may include this IE to assign a partially rejected NSSAI to the UE.

8.2.7.55 RAN timing synchronization |R18| p. 742

This IE may be included to provide information related to the RAN timing synchronization to a UE which has set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message.

8.2.7.56 Alternative NSSAI |R18| p. 742

The network may include this IE to provide the alternative NSSAI to the UE.

8.2.7.57 Discontinuous coverage maximum time offset |R18| p. 742

This IE may be included to provide the UE with a maximum wating time after return from discontinuous coverage.

8.2.7.58 S-NSSAI time validity information |R18| p. 742

If the UE supports S-NSSAI time validity information, the network may include this IE to update the S-NSSAI time validity information.

8.2.7.59 Unavailability period duration |R18| p. 742

The AMF should include this IE if the AMF needs to send the unavailability period duration to the UE.

8.2.7.60 Feature authorization indication |R18| p. 743

The network may include this IE to inform to the UE about the authorization status of the UE whether to operate as an MBSR or to operate not as an MBSR but to operate as a UE.

8.2.8 Registration complete p. 743

8.2.8.1 Message definition p. 743

The REGISTRATION COMPLETE message is sent by the UE to the AMF. See Table 8.2.8.1.1.

Message type:

REGISTRATION COMPLETE

Significance:

dual

Direction:

UE to network

Table 8.2.8.1.1: REGISTRATION COMPLETE message content

IEI	Information Element	Type/Reference	Presence	Format	Length
	Extended protocol discriminator	Extended protocol discriminator 9.2	M	V	1
	Security header type	Security header type 9.3	M	V	1/2
	Spare half octet	Spare half octet 9.5	M	V	1/2
	Registration complete message identity	Message type 9.7	M	V	1
73	SOR transparent container	SOR transparent container 9.11.3.51	O	TLV-E	20

8.2.8.2 SOR transparent container p. 743

This IE may be sent by the UE. If this IE is sent, the contents of this IE indicates the UE acknowledgement of successful reception of the SOR transparent container IE in the REGISTRATION ACCEPT message. This IE shall indicate the ME support of SOR-CMCI.

Content for TS 24.501 Word version: 18.4.0

8 Message functional definitions and contents p. 719

8.1 Overview p. 719

8.2 5GS mobility management messages p. 720

8.2.1 Authentication request p. 720

8.2.1.1 Message definition p. 720

8.2.1.2 Authentication parameter RAND p. 721

8.2.1.3 Authentication parameter AUTN p. 721

8.2.1.4 Void

8.2.1.5 EAP message p. 721

8.2.2 Authentication response p. 721

8.2.2.1 Message definition p. 721

8.2.2.2 Authentication response parameter p. 722

8.2.2.3 EAP message p. 722

8.2.3 Authentication result p. 722

8.2.3.1 Message definition p. 722

8.2.3.2 ABBA p. 723

8.2.3.3 Master session key |R18| p. 723

8.2.4 Authentication failure p. 723

8.2.4.1 Message definition p. 723

8.2.4.2 Authentication failure parameter p. 723

8.2.5 Authentication reject p. 723

8.2.5.1 Message definition p. 723

8.2.5.2 EAP message p. 724

8.2.6 Registration request p. 724

8.2.6.1 Message definition p. 724

8.2.6.2 Non-current native NAS key set identifier p. 727

8.2.6.3 5GMM capability p. 727

8.2.6.4 UE security capability p. 727

8.2.6.5 Requested NSSAI p. 727

8.2.6.6 Last visited registered TAI p. 727

8.2.6.7 S1 UE network capability p. 728

8.2.6.8 Uplink data status p. 728

8.2.6.9 PDU session status p. 728

8.2.6.10 MICO indication p. 728

8.2.6.11 UE status p. 728

8.2.6.12 Additional GUTI p. 728

8.2.6.13 Allowed PDU session status p. 728

8.2.6.14 UE's usage setting p. 728

8.2.6.15 Requested DRX parameters p. 728

8.2.6.16 EPS NAS message container p. 728

8.2.6.17 LADN indication p. 729

8.2.6.17A Payload container type p. 729

8.2.6.18 Payload container p. 729

8.2.6.19 Network slicing indication p. 729

8.2.6.20 5GS update type p. 729

8.2.6.21 NAS message container p. 730

8.2.6.22 Requested extended DRX parameters p. 730

8.2.6.23 EPS bearer context status |R16| p. 730

8.2.6.24 T3324 value |R16| p. 730

8.2.6.25 Mobile station classmark 2 |R16| p. 730

8.2.6.26 Supported codecs |R16| p. 730

8.2.6.27 UE radio capability ID |R16| p. 730

8.2.6.28 Requested mapped NSSAI |R16| p. 730

8.2.6.29 Additional information requested |R16| p. 730

8.2.6.30 Requested WUS assistance information |R16| p. 730

8.2.6.31 Void

8.2.6.32 N5GC indication |R16| p. 731

8.2.6.33 Requested NB-N1 mode DRX parameters |R16| p. 731

8.2.6.34 UE request type |R17| p. 731

8.2.6.35 Paging restriction |R17| p. 731

8.2.6.35a Service-level-AA container |R17| p. 731

8.2.6.36 NID |R17| p. 731

8.2.6.37 MS determined PLMN with disaster condition |R17| p. 731

8.2.6.38 Requested PEIPS assistance information |R17| p. 731

8.2.6.39 Requested T3512 value |R17| p. 731

8.2.6.40 Unavailability period duration |R18| p. 731

8.2.6.41 Non-3GPP path switching information |R18| p. 731

8.2.6.42 AUN3 indication |R18| p. 732

8.2.7 Registration accept p. 732

8.2.7.1 Message definition p. 732

8.2.7.2 5G-GUTI p. 736

8.2.7.3 Equivalent PLMNs p. 736

8.2.7.4 TAI list p. 736

8.2.7.5 Allowed NSSAI p. 736

8.2.7.6 Rejected NSSAI p. 736

8.2.7.7 Configured NSSAI p. 736

8.2.7.8 5GS network feature support p. 736

8.2.7.9 PDU session status p. 737

8.2.7.10 PDU session reactivation result p. 737