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 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 |
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 |
7C | 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 | PLMN with disaster condition | PLMN identity
9.11.3.85 | O | TLV | 5 |
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.
The UE shall include this IE, unless the UE performs a periodic registration updating procedure.
The UE shall include this IE, unless the UE performs a periodic registration updating procedure.
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.
This IE shall be included if the UE holds a valid last visited registered TAI.
A UE supporting S1 mode shall include this IE, unless the UE performs a periodic registration updating procedure.
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.
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.
The UE may include this IE to request the use of MICO mode.
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.
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.
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.
This IE shall be included if the UE supports IMS voice.
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.
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:
-
was previously registered in S1 mode before entering state EMM-DEREGISTERED; and
-
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.
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.
This IE shall be included if the UE includes the Payload container IE.
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.
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.
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.
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.
The UE shall include this IE if the UE needs to use extended DRX or change the extended DRX parameters.
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.
The UE may include this IE during the registration update procedure if it requests to use MICO mode and use the active time timer.
This IE shall be included if the UE supports 5G-SRVCC from NG-RAN to UTRAN (see
TS 23.216).
This IE shall be included if the UE supports 5G-SRVCC from NG-RAN to UTRAN.
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.
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.
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.
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.
This IE shall be included in the REGISTRATION REQUEST message when the W-AGF is acting on behalf of an N5GC device.
The UE shall include this IE if the UE wants to use or change the UE specific DRX parameters for NB-N1 mode.
The UE shall include this IE if the UE supports MUSIM and requests the release of the NAS signalling connection.
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.
The UE may include this IE if the UE accesses to an SNPN using credentials from any other SNPN.
The UE shall include this IE when the UE needs to indicate the PLMN with disaster condition.
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 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-5 |
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 | 12-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 |
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 |
7C | 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 |
34 | 5GS additional request result | 5GS additional request result
9.11.3.81 | O | TLV | 3 |
35 | NSSRG information | NSSRG information
9.11.3.82 | O | TLV | TBD |
14 | Disaster roaming wait range | Registration wait range
9.11.3.84 | O | TLV | 4 |
15 | 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 |
This IE may be included to assign a 5G-GUTI to a UE.
This IE may be included in order to assign a new equivalent PLMNs list to a UE.
This IE may be included to assign a TAI list to a UE.
This IE shall be included:
-
if:
-
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;
-
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
-
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
-
the network not supporting NSSAA has one or more subscribed S-NSSAIs marked as default; or
-
the network has one or more subscribed S-NSSAIs marked as default which are not subject to network slice-specific authentication and authorization.
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.
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.
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.
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.
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.
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.
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.
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.
This IE shall be included if the user's network slicing subscription has changed in the UDM of a PLMN or an SNPN.
This IE may be included to assign new service area restrictions to the UE.
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".
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.
This IE may be included to indicate a value for timer T3502.
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.
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.
This IE may be sent by the network.
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.
This IE shall be included if required by operatory policy.
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.
The network shall include this IE if the Requested DRX parameters IE was included in the REGISTRATION REQUEST message.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This IE is included if the network needs to send ciphering key data to the UE for ciphered broadcast assistance data.
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.
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.
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.
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.
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.
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.
The network may include this IE to inform the UE about the result of additional request.
This IE may be included to provide NSSRG information associated with the configured NSSAI only if the configured NSSAI IE is included.
This IE may be included to assign a new disaster roaming wait range to the UE.
This IE may be included to assign a new disaster return wait range to the UE.
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.