Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  18.6.0

Top   Top   Up   Prev   Next
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  Message functional definitions and contentsp. 743

8.1  Overviewp. 743

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:
  1. 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.
  2. 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-).
    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.
  3. 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).
Up

8.2  5GS mobility management messagesp. 744

8.2.1  Authentication requestp. 744

8.2.1.1  Message definitionp. 744

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Authentication request message identityMessage type
9.7
MV1
ngKSI NAS key set identifier
9.11.3.32
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
ABBAABBA
9.11.3.10
MLV3-n
21Authentication parameter RAND (5G authentication challenge)Authentication parameter RAND
9.11.3.16
OTV17
20Authentication parameter AUTN (5G authentication challenge)Authentication parameter AUTN
9.11.3.15
OTLV18
78EAP messageEAP message
9.11.2.2
OTLV-E7-1503
Up

8.2.1.2  Authentication parameter RANDp. 745

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 AUTNp. 745

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

8.2.1.4Void

8.2.1.5  EAP messagep. 745

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 responsep. 745

8.2.2.1  Message definitionp. 745

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Authentication response message identityMessage type
9.7
MV1
2DAuthentication response parameterAuthentication response parameter
9.11.3.17
OTLV18
78EAP messageEAP message
9.11.2.2
OTLV-E7-1503
Up

8.2.2.2  Authentication response parameterp. 746

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 messagep. 746

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

8.2.3  Authentication resultp. 746

8.2.3.1  Message definitionp. 746

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Authentication result message identityMessage type
9.7
MV1
ngKSI NAS key set identifier
9.11.3.32
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
EAP messageEAP message
9.11.2.2
MLV-E6-1502
38ABBAABBA
9.11.3.10
OTLV4-n
55AUN3 device security keyAUN3 device security key
9.11.3.107
OTLV36-n
Up

8.2.3.2  ABBAp. 747

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

8.2.3.3  AUN3 device security key |R18|p. 747

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 failurep. 747

8.2.4.1  Message definitionp. 747

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Authentication failure message identityMessage type
9.7
MV1
5GMM cause5GMM cause
9.11.3.2
MV1
30Authentication failure parameterAuthentication failure parameter
9.11.3.14
OTLV16
Up

8.2.4.2  Authentication failure parameterp. 747

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 rejectp. 747

8.2.5.1  Message definitionp. 747

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Authentication reject message identityMessage type
9.7
MV1
78EAP messageEAP message
9.11.2.2
OTLV-E7-1503
Up

8.2.5.2  EAP messagep. 748

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

8.2.6  Registration requestp. 748

8.2.6.1  Message definitionp. 748

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended Protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Registration request message identityMessage type
9.7
MV1
5GS registration type5GS registration type
9.11.3.7
MV1/2
ngKSINAS key set identifier
9.11.3.32
MV1/2
5GS mobile identity5GS mobile identity
9.11.3.4
MLV-E6-n
C-Non-current native NAS key set identifierNAS key set identifier
9.11.3.32
OTV1
105GMM capability5GMM capability
9.11.3.1
OTLV3-15
2EUE security capabilityUE security capability
9.11.3.54
OTLV4-10
2FRequested NSSAINSSAI
9.11.3.37
OTLV4-74
52Last visited registered TAI5GS tracking area identity
9.11.3.8
OTV7
17S1 UE network capabilityS1 UE network capability
9.11.3.48
OTLV4-15
40Uplink data statusUplink data status
9.11.3.57
OTLV4-34
50PDU session statusPDU session status
9.11.3.44
OTLV4-34
B-MICO indicationMICO indication
9.11.3.31
OTV1
2BUE statusUE status
9.11.3.56
OTLV3
77Additional GUTI5GS mobile identity
9.11.3.4
OTLV-E14
25Allowed PDU session statusAllowed PDU session status
9.11.3.13
OTLV4-34
18UE's usage settingUE's usage setting
9.11.3.55
OTLV3
51Requested DRX parameters5GS DRX parameters
9.11.3.2A
OTLV3
70EPS NAS message containerEPS NAS message container
9.11.3.24
OTLV-E4-n
74LADN indicationLADN indication
9.11.3.29
OTLV-E3-811
8-Payload container typePayload container type
9.11.3.40
OTV1
7BPayload containerPayload container
9.11.3.39
OTLV-E4-65538
9-Network slicing indicationNetwork slicing indication
9.11.3.36
OTV1
535GS update type5GS update type
9.11.3.9A
OTLV3
41Mobile station classmark 2Mobile station classmark 2
9.11.3.31C
OTLV5
42Supported codecsSupported codec list
9.11.3.51A
OTLV5-n
71NAS message containerNAS message container
9.11.3.33
OTLV-E4-n
60EPS bearer context statusEPS bearer context status
9.11.3.23A
OTLV4
6ERequested extended DRX parametersExtended DRX parameters
9.11.3.26A
OTLV3-4
6AT3324 valueGPRS timer 3
9.11.2.5
OTLV3
67UE radio capability IDUE radio capability ID
9.11.3.68
OTLV3-n
35Requested mapped NSSAIMapped NSSAI
9.11.3.31B
OTLV3-42
48Additional information requestedAdditional information requested
9.11.3.12A
OTLV3
1ARequested WUS assistance informationWUS assistance information
9.11.3.71
OTLV3-n
A-N5GC indicationN5GC indication
9.11.3.72
OTV1
30Requested NB-N1 mode DRX parametersNB-N1 mode DRX parameters
9.11.3.73
OTLV3
29UE request typeUE request type
9.11.3.76
OTLV3
28Paging restrictionPaging restriction
9.11.3.77
OTLV3-35
72Service-level-AA containerService-level-AA container
9.11.2.10
OTLV-E4-65538
32NIDNID
9.11.3.79
OTLV8
16MS determined PLMN with disaster conditionPLMN identity
9.11.3.85
OTLV5
2ARequested PEIPS assistance informationPEIPS assistance information
9.11.3.80
OTLV3-n
3BRequested T3512 valueGPRS timer 3
9.11.2.5
OTLV3
3CUnavailability informationUnavailability information
9.11.2.20
OTLV3-9
3FNon-3GPP path switching informationNon-3GPP path switching information
9.11.3.102
OTLV3
56AUN3 indicationAUN3 indication
9.11.3.104
OTLV3
Up

8.2.6.2  Non-current native NAS key set identifierp. 751

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 capabilityp. 751

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

8.2.6.4  UE security capabilityp. 751

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

8.2.6.5  Requested NSSAIp. 751

This IE shall be included by the UE when performing the registration procedure if the 5GS registration type IE indicates:
  1. "initial registration", according to the conditions specified in subclause 5.5.1.2.2; or
  2. "mobility registration updating", according to the conditions specified in subclause 5.5.1.3.2.
Up

8.2.6.6  Last visited registered TAIp. 751

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

8.2.6.7  S1 UE network capabilityp. 752

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

8.2.6.8  Uplink data statusp. 752

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 statusp. 752

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 indicationp. 752

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

8.2.6.11  UE statusp. 752

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 GUTIp. 752

This IE shall be included:
  1. 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
  2. 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 statusp. 752

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 settingp. 752

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

8.2.6.15  Requested DRX parametersp. 752

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 containerp. 752

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
  1. 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
  2. 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.
Up

8.2.6.17  LADN indicationp. 753

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 typep. 753

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

8.2.6.18  Payload containerp. 753

Within a PLMN, this IE shall be included if:
  1. 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
  2. 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:
  1. the UE has one or more stored UE policy sections for the selected SNPN for the registration procedure for initial registration; or
  2. 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.
Up

8.2.6.19  Network slicing indicationp. 753

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 typep. 753

This IE shall be included when the UE is performing the registration procedure to indicate any of the following:
  1. the UE requests the use of SMS over NAS or there is a change in the UE's requirements to use SMS over NAS;
  2. a change in the UE's radio capability for NG-RAN; or
  3. the UE requests CIoT 5GS optimizations.

8.2.6.21  NAS message containerp. 754

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 parametersp. 754

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

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

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

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

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

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

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

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

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.31Void

8.2.6.32  N5GC indication |R16|p. 755

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

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

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

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

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

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

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

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

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 information |R18|p. 755

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

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

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 acceptp. 756

8.2.7.1  Message definitionp. 756

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Registration accept message identityMessage type
9.7
MV1
5GS registration result5GS registration result
9.11.3.6
MLV2
775G-GUTI5GS mobile identity
9.11.3.4
OTLV-E14
4AEquivalent PLMNsPLMN list
9.11.3.45
OTLV5-47
54TAI list5GS tracking area identity list
9.11.3.9
OTLV9-114
15Allowed NSSAINSSAI
9.11.3.37
OTLV4-74
11Rejected NSSAIRejected NSSAI
9.11.3.46
OTLV4-42
31Configured NSSAINSSAI
9.11.3.37
OTLV4-146
215GS network feature support5GS network feature support
9.11.3.5
OTLV3-6
50PDU session statusPDU session status
9.11.3.44
OTLV4-34
26PDU session reactivation resultPDU session reactivation result
9.11.3.42
OTLV4-34
72PDU session reactivation result error causePDU session reactivation result error cause
9.11.3.43
OTLV-E5-515
79LADN informationLADN information
9.11.3.30
OTLV-E13-1715
B-MICO indicationMICO indication
9.11.3.31
OTV1
9-Network slicing indicationNetwork slicing indication
9.11.3.36
OTV1
27Service area listService area list
9.11.3.49
OTLV6-114
5ET3512 valueGPRS timer 3
9.11.2.5
OTLV3
5DNon-3GPP de-registration timer valueGPRS timer 2
9.11.2.4
OTLV3
16T3502 valueGPRS timer 2
9.11.2.4
OTLV3
34Emergency number listEmergency number list
9.11.3.23
OTLV5-50
7AExtended emergency number listExtended emergency number list
9.11.3.26
OTLV-E7-65538
73SOR transparent containerSOR transparent container
9.11.3.51
OTLV-E20-n
78EAP messageEAP message
9.11.2.2
OTLV-E7-1503
A-NSSAI inclusion modeNSSAI inclusion mode
9.11.3.37A
OTV1
76Operator-defined access category definitionsOperator-defined access category definitions
9.11.3.38
OTLV-E3-8323
51Negotiated DRX parameters5GS DRX parameters
9.11.3.2A
OTLV3
D-Non-3GPP NW policiesNon-3GPP NW provided policies
9.11.3.36A
OTV1
60EPS bearer context statusEPS bearer context status
9.11.3.23A
OTLV4
6ENegotiated extended DRX parametersExtended DRX parameters
9.11.3.26A
OTLV3-4
6CT3447 valueGPRS timer 3
9.11.2.5
OTLV3
6BT3448 valueGPRS timer 2
9.11.2.4
OTLV3
6AT3324 valueGPRS timer 3
9.11.2.5
OTLV3
67UE radio capability IDUE radio capability ID
9.11.3.68
OTLV3-n
E-UE radio capability ID deletion indicationUE radio capability ID deletion indication
9.11.3.69
OTV1
39Pending NSSAINSSAI
9.11.3.37
OTLV4-146
74Ciphering key dataCiphering key data
9.11.3.18C
OTLV-E34-n
75CAG information listCAG information list
9.11.3.18A
OTLV-E3-n
1BTruncated 5G-S-TMSI configurationTruncated 5G-S-TMSI configuration
9.11.3.70
OTLV3
1CNegotiated WUS assistance informationWUS assistance information
9.11.3.71
OTLV3-n
29Negotiated NB-N1 mode DRX parametersNB-N1 mode DRX parameters
9.11.3.73
OTLV3
68Extended rejected NSSAIExtended rejected NSSAI
9.11.3.75
OTLV5-90
7BService-level-AA containerService-level-AA container
9.11.2.10
OTLV-E4-65538
33Negotiated PEIPS assistance informationPEIPS assistance information
9.11.3.80
OTLV3-n
355GS additional request result5GS additional request result
9.11.3.81
OTLV3
70NSSRG informationNSSRG information
9.11.3.82
OTLV-E7-4099
14Disaster roaming wait rangeRegistration wait range
9.11.3.84
OTLV4
2CDisaster return wait rangeRegistration wait range
9.11.3.84
OTLV4
13List of PLMNs to be used in disaster conditionList of PLMNs to be used in disaster condition
9.11.3.83
OTLV2-n
1D Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" 5GS tracking area identity list
9.11.3.9
OTLV9-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
OTLV9-114
71Extended CAG information listExtended CAG information list
9.11.3.86
OTLV-E3-n
7CNSAG informationNSAG information
9.11.3.87
OTLV-E9-3143
3DEquivalent SNPNsSNPN list
9.11.3.92
OTLV11-137
32NIDNID
9.11.3.79
OTLV8
7DRegistration accept type 6 IE containerType 6 IE container
9.11.3.98
OTLV-E6-65538
4BRAN timing synchronizationRAN timing synchronization
9.11.3.95
OTLV3
4BAlternative NSSAIAlternative NSSAI
9.11.3.97
OTLV2-146
4FMaximum time offsetGPRS timer 3
9.11.2.5
OTLV3
5BS-NSSAI time validity informationS-NSSAI time validity information
9.11.3.101
OTLV23-257
3CUnavailability configurationUnavailability configuration
9.11.2.21
OTLV3-6
5CFeature authorization indicationFeature authorization indication
9.11.3.105
OTLV3-257
61On-demand NSSAIOn-demand NSSAI
9.11.3.108
OTLV5-210
Up

8.2.7.2  5G-GUTIp. 760

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

8.2.7.3  Equivalent PLMNsp. 760

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

8.2.7.4  TAI listp. 760

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

8.2.7.5  Allowed NSSAIp. 760

This IE shall be included:
  1. 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
  2. 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.
Up

8.2.7.6  Rejected NSSAIp. 760

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 NSSAIp. 760

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 supportp. 760

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 statusp. 761

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 resultp. 761

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 causep. 761

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 informationp. 761

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 indicationp. 761

The network shall include the MICO indication IE if:
  1. the UE included the MICO indication IE in the REGISTRATION REQUEST message; and
  2. the network supports and accepts the use of MICO mode.

8.2.7.14  Network slicing indicationp. 761

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 listp. 761

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

8.2.7.16  T3512 valuep. 761

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 valuep. 761

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 valuep. 761

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

8.2.7.19  Emergency number listp. 762

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 listp. 762

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 containerp. 762

This IE may be sent by the network.

8.2.7.22  EAP messagep. 762

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 modep. 762

This IE shall be included if required by operatory policy.

8.2.7.24  Operator-defined access category definitionsp. 762

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 parametersp. 762

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 policiesp. 762

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

8.2.7.27  Negotiated extended DRX parametersp. 762

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

8.2.7.44  NSSRG information |R17|p. 764

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

8.2.7.45  Disaster roaming wait range |R17|p. 764

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

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

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

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

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

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

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

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

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

8.2.7.54.1  Generalp. 765
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.
IEI Information Element Type/Reference Presence Format Length
01Extended LADN informationExtended LADN information
9.11.3.96
OTLV-E15-1787
02S-NSSAI location validity informationS-NSSAI location validity information
9.11.3.100
OTLV-E25-19307
03Partially allowed NSSAIPartial NSSAI
9.11.3.103
OTLV-E3-808
04Partially rejected NSSAIPartial NSSAI
9.11.3.103
OTLV-E3-808
Up
8.2.7.54.2  Extended LADN informationp. 766
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 informationp. 766
The network may include this IE to update the S-NSSAI location validity information.
8.2.7.54.4Void
8.2.7.54.5  Partially allowed NSSAIp. 766
The network may include this IE to assign a partially allowed NSSAI to the UE.
8.2.7.54.6  Partially rejected NSSAIp. 766
The network may include this IE to assign a partially rejected NSSAI to the UE.

8.2.7.55  RAN timing synchronization |R18|p. 766

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

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

8.2.7.57  Maximum time offset |R18|p. 766

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

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

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 configuration |R18|p. 766

The network should include this IE if the network needs to provide parameters related to unavailability period to the UE.

8.2.7.60  Feature authorization indication |R18|p. 767

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.7.61  On-demand NSSAI |R18|p. 767

The network may include this IE to provide the on-demand NSSAI to the UE.

8.2.8  Registration completep. 767

8.2.8.1  Message definitionp. 767

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
IEI Information Element Type/Reference Presence Format Length
Extended protocol discriminatorExtended protocol discriminator
9.2
MV1
Security header typeSecurity header type
9.3
MV1/2
Spare half octetSpare half octet
9.5
MV1/2
Registration complete message identityMessage type
9.7
MV1
73SOR transparent containerSOR transparent container
9.11.3.51
OTLV-E20
Up

8.2.8.2  SOR transparent containerp. 767

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.

Up   Top   ToC