Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.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…

 

8  Message functional definitions and contentsWord‑p. 576

8.1  OverviewWord‑p. 576

8.2  5GS mobility management messagesWord‑p. 576

8.2.1  Authentication requestWord‑p. 576

8.2.1.1  Message definitionWord‑p. 576

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 RANDWord‑p. 576

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 AUTNWord‑p. 576

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 messageWord‑p. 577

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 responseWord‑p. 577

8.2.2.1  Message definitionWord‑p. 577

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 parameterWord‑p. 577

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 messageWord‑p. 577

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

8.2.3  Authentication resultWord‑p. 577

8.2.3.1  Message definitionWord‑p. 577

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
Up

8.2.3.2  ABBAWord‑p. 578

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

8.2.4  Authentication failureWord‑p. 578

8.2.4.1  Message definitionWord‑p. 578

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 parameterWord‑p. 578

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 rejectWord‑p. 579

8.2.5.1  Message definitionWord‑p. 579

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 messageWord‑p. 579

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

8.2.6  Registration requestWord‑p. 579

8.2.6.1  Message definitionWord‑p. 579

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
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
7CService-level-AA containerService-level-AA container
9.11.2.10
OTLV-E6-n
32NIDNID
9.11.3.79
OTLV8
16PLMN with disaster conditionPLMN identity
9.11.3.85
OTLV5
Up

8.2.6.2  Non-current native NAS key set identifierWord‑p. 582

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 capabilityWord‑p. 582

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

8.2.6.4  UE security capabilityWord‑p. 582

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

8.2.6.5  Requested NSSAIWord‑p. 582

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 TAIWord‑p. 582

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

8.2.6.7  S1 UE network capabilityWord‑p. 582

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

8.2.6.8  Uplink data statusWord‑p. 582

This IE shall be included if the UE has uplink user data pending to be sent, unless the UE performs a periodic registration updating procedure.

8.2.6.9  PDU session statusWord‑p. 583

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 indicationWord‑p. 583

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

8.2.6.11  UE statusWord‑p. 583

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 GUTIWord‑p. 583

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 statusWord‑p. 583

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 and the UE wants to indicate the user-plane resources of PDU session(s) associated with non-3GPP access allowed to be re-established over 3GPP access.

8.2.6.14  UE's usage settingWord‑p. 583

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

8.2.6.15  Requested DRX parametersWord‑p. 583

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 containerWord‑p. 583

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 indicationWord‑p. 584

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 typeWord‑p. 584

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

8.2.6.18  Payload containerWord‑p. 584

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

8.2.6.19  Network slicing indicationWord‑p. 584

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 typeWord‑p. 584

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 containerWord‑p. 584

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 parametersWord‑p. 584

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|Word‑p. 584

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|Word‑p. 584

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|Word‑p. 585

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|Word‑p. 585

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|Word‑p. 585

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|Word‑p. 585

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 clause 5.5.1.3.2.

8.2.6.29  Additional information requested |R16|Word‑p. 585

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|Word‑p. 585

The UE may include this IE if the UE supports WUS assistance information and the UE is not performing the initial registration for emergency services.

8.2.6.31Void

8.2.6.32  N5GC indication |R16|Word‑p. 585

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|Word‑p. 585

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|Word‑p. 585

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

8.2.6.35  Paging restriction |R17|Word‑p. 585

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|Word‑p. 585

8.2.6.36  NID |R17|Word‑p. 585

The UE may include this IE if the UE accesses to an SNPN using credentials from any other SNPN.

8.2.6.37  PLMN with disaster condition |R17|Word‑p. 586

The UE shall include this IE when the UE needs to indicate the PLMN with disaster condition.

8.2.7  Registration acceptWord‑p. 586

8.2.7.1  Message definitionWord‑p. 586

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-5
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-E12-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
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
7CService-level-AA containerService-level-AA container
9.11.2.10
OTLV-E6-n
33Negotiated PEIPS assistance informationPEIPS assistance information
9.11.3.80
OTLV3-n
345GS additional request result5GS additional request result
9.11.3.81
OTLV3
35NSSRG informationNSSRG information
9.11.3.82
OTLVTBD
14Disaster roaming wait rangeRegistration wait range
9.11.3.84
OTLV4
15Disaster 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
Up

8.2.7.2  5G-GUTIWord‑p. 589

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

8.2.7.3  Equivalent PLMNsWord‑p. 589

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

8.2.7.4  TAI listWord‑p. 589

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

8.2.7.5  Allowed NSSAIWord‑p. 589

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 not supporting NSSAA has one or more subscribed S-NSSAIs marked as default; or
    2. the network has one or more subscribed S-NSSAIs marked as default which are not subject to network slice-specific authentication and authorization.
Up

8.2.7.6  Rejected NSSAIWord‑p. 590

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 NSSAIWord‑p. 590

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 supportWord‑p. 590

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 statusWord‑p. 590

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 resultWord‑p. 590

This IE shall be included:
  • if the Uplink data status IE is included in the REGISTRATION REQUEST message;
  • 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 causeWord‑p. 590

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 informationWord‑p. 590

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 indicationWord‑p. 591

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 indicationWord‑p. 591

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 listWord‑p. 591

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

8.2.7.16  T3512 valueWord‑p. 591

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 valueWord‑p. 591

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 valueWord‑p. 591

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

8.2.7.19  Emergency number listWord‑p. 591

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 listWord‑p. 591

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 containerWord‑p. 591

This IE may be sent by the network.

8.2.7.22  EAP messageWord‑p. 591

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 modeWord‑p. 591

This IE shall be included if required by operatory policy.

8.2.7.24  Operator-defined access category definitionsWord‑p. 592

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 parametersWord‑p. 592

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 provided policiesWord‑p. 592

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 parametersWord‑p. 592

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|Word‑p. 592

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|Word‑p. 592

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|Word‑p. 592

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|Word‑p. 592

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|Word‑p. 592

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|Word‑p. 593

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|Word‑p. 593

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|Word‑p. 593

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|Word‑p. 593

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|Word‑p. 593

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|Word‑p. 593

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|Word‑p. 593

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; and
  • the UE is not performing the initial registration for emergency services.

8.2.7.40  Extended rejected NSSAI |R17|Word‑p. 593

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|Word‑p. 593

8.2.7.42  Negotiated PEIPS assistance information |R17|Word‑p. 594

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|Word‑p. 594

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

8.2.7.44  NSSRG information |R17|Word‑p. 594

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

8.2.7.45  Disaster roaming wait range |R17|Word‑p. 594

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|Word‑p. 594

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|Word‑p. 594

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.8  Registration completeWord‑p. 594

8.2.8.1  Message definitionWord‑p. 594

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 containerWord‑p. 595

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