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.
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.
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.
The AMF may include this IE when the 5GMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum time value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
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.
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.
This IE may be included by the network to indicate additional information associated with the 5GMM cause value #15 "no suitable cells in tracking area".
The UE shall include this IE if the UL NAS TRANSPORT message transports a PDU SESSION ESTABLISHMENT REQUEST message upon receiving the PDU SESSION MODIFICATION COMMAND message with the 5GSM cause IE set to #39 "reactivation requested" and the Payload container type IE is set to "N1 SM information".
The UE shall include this IE when the PDU session ID IE is included and the Payload container IE contains the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST which is not initiated to indicate a change of 3GPP PS data off UE status associated to a PDU session.
The UE may include this IE when the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request", the Payload container type IE is set to "N1 SM information" and the UE is not registered for onboarding services in SNPN.
The UE may include this IE when the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request", the Payload container type IE is set to "N1 SM information" and the UE is not registered for onboarding services in SNPN.
This IE is included when the Payload container type IE is set to "LTE Positioning Protocol (LPP) message container", "UPP-CMI container", "SLPP message container", or "Location services (LCS) message container".
The UE may include this IE if the Request type IE is included and is not set to "initial emergency request" or "existing emergency PDU session" in the UL NAS TRANSPORT message.
The UE may include this IE to inform the network whether:
no further uplink and no further downlink data transmission is expected; or
only a single downlink data transmission (e.g. acknowledgement or response to uplink data) and no further uplink data transmission subsequent to the uplink data transmission is expected.
The UE may include this IE when the Payload container type IE is set to "N1 SM information" to indicate whether the UE supports the non-3GPP access path switching for the PDU session.
This IE is included when the Payload container type IE is set to "LTE Positioning Protocol (LPP) message container", "UPP-CMI container", "SLPP message container", or "Location services (LCS) message container".
The AMF shall include this IE when the Payload container IE contains an uplink payload which was not forwarded and the Payload container type IE is not set to "Multiple payloads".
The AMF may include this IE to indicate the back-off timer value when the Payload container IE is included and the Payload container type IE is not set to "Multiple payloads".
The AMF may include this IE when the 5GMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum time value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
The UE may include this IE when an event is triggered in the UE that would make the UE unavailable for a certain period and the use of unavailability period is not due to NR satellite access discontinuous coverage.
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.
The AMF may include this IE when the 5GMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum time value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
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.
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.
The SERVICE REQUEST message is sent by the UE to the AMF in order to request the establishment of an N1 NAS signalling connection, to request the establishment of user-plane resources for PDU sessions which are established without user-plane resources, or both. See Table 8.2.16.1.1.
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.
This IE shall be included if the SERVICE REQUEST message is sent as a response to paging with the access type indicating non-3GPP access or notification via 3GPP access for PDU session(s) associated with non-3GPP access.
The UE shall include this IE if the Request type is set to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE and the UE requests the network to restrict paging.
This IE shall be included when the network needs to indicate the PDU sessions that are associated with the access type that the message is sent over that are active within the network.
if the Uplink data status IE is included in the SERVICE REQUEST message; or
if the Allowed PDU session status IE is included in the SERVICE REQUEST message and there is at least one PDU session indicated in the Allowed PDU session status IE for which 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 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.
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.
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.
This IE shall be included when the network needs to indicate the PDU sessions that are associated with the access type that the message is sent over, that are active within the network.
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.
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.
The AMF may include this IE when the 5GMM cause is set to #78 "PLMN not allowed to operate at the present UE location", to provide a minimum time value for an entry added to the list of "PLMNs not allowed to operate at the present UE location".
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.
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.
The AMF shall include this IE when the AMF 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 one or more S-NSSAIs that were previously sent to the UE in the allowed NSSAI or the pending NSSAI, but are now considered rejected by the network.
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.
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 serving SNPN.
This IE may be included to provide a new truncated 5G-S-TMSI configuration to the UE in NB-N1 mode if the network is configured to provide the truncated 5G-S-TMSI configuration for control plane CIoT 5GS optimizations.
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 previously sent to the UE in the allowed NSSAI or the pending NSSAI, but are now considered rejected by the network.
The network shall include this IE when the AMF receives the Service-level-AA payload or the UUAA-MM result from the UAS-NF during the UUAA-MM procedure or the UUAA revocation procedure. The network shall also include this IE if the AMF receives from the UAS-NF, the CAA-Level UAV ID as part of the UUAA-MM procedure.
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.
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.
The AMF may include this IE if the UE supports NR paging subgrouping, the AMF supports and accepts the use of PEIPIS assistance information for the UE, the UE is not registered for emergency services, the UE does not have an active emergency PDU session, and the network needs to update PEIPS assistance information for the UE.
If the UE has set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message is sent over 3GPP access, the network may include this IE to provide NSAG information to the UE.
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.
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.
The NOTIFICATION RESPONSE message is sent by the UE to the AMF to notify the failure to initiate the service request procedure as a response of notification. See Table 8.2.24.1.1.
This information element shall be included when the UE needs to indicate over non-3GPP access the PDU sessions that are associated with the 3GPP access type that are active within the UE.
This IE shall be included if the AMF supports N26 interface, the UE set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, and the AMF needs to provide the selected EPS NAS security algorithms to the UE.
the network needs to provide the UE with horizontal derivation parameter; or
the applicable initial NAS message (i.e. REGISTRATION REQUEST, CONTROL PLANE SERVICE REQUEST or SERVICE REQUEST) does not successfully pass the integrity check at the AMF (see subclause 5.4.2.2).
This IE is included when the EAP Success message is sent as part of the EAP based primary authentication and key agreement procedure, as specified in subclause 5.4.1.2.
This IE shall be included when the SECURITY MODE COMMAND 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.
if during an ongoing registration procedure or service request procedure, the AMF included the Additional 5G security information with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message as described in TS 33.501; or
if during an ongoing registration procedure, the UE does not have a valid 5G NAS security context.
The 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall include this information element, if the IMEISV was requested within the corresponding SECURITY MODE COMMAND message, the IMEISV is not available but MAC address is available.
The UE shall include this information element, if the IMEISV was requested within the corresponding SECURITY MODE COMMAND message, the IMEISV is not available but EUI-64 is available.
The SECURITY MODE REJECT message is sent by the UE to the AMF to indicate that the corresponding security mode command has been rejected. See Table 8.2.27.1.1.
This message is sent by the UE or the network to transfer a plain 5GS NAS message as specified in subclause 8.2 together with the sequence number and the message authentication code protecting the message. See Table 8.2.28.1.1.
The CONTROL PLANE SERVICE REQUEST message is sent by the UE to the AMF when the UE is using 5GS services with control plane CIoT 5GS optimization. See Table 8.2.30.1.1.
This IE shall be included if the UE needs to send uplink small user data, SMS or location services message that is not more than 254 bytes, and there is no other optional IE to be sent.
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 inform the network whether:
no further uplink and no further downlink data transmission is expected; or
only a single downlink data transmission (e.g. acknowledgement or response to uplink data) and no further uplink data transmission subsequent to the uplink data transmission is expected.
This IE shall be included if the UE is sending a CONTROL PLANE SERVICE REQUEST message as an initial NAS message and the UE needs to send non-cleartext IEs.
This IE shall be included if the CONTROL PLANE SERVICE REQUEST message is sent as a response to paging with the access type indicating non-3GPP access or notification via 3GPP access for PDU session(s) associated with non-3GPP access.
The UE shall include this IE if the Request type is set to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE and the UE requests the network to restrict paging.
The NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message is sent by the AMF to the UE for authentication of the upper layers of the UE. See Table 8.2.31.1.1.
The NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message is sent by the UE to the AMF in response to the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and indicates acceptance of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. See Table 8.2.32.1.1.
The NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message is sent by the AMF to the UE for indicating the result of the network slice-specific authentication and authorization procedure. See Table 8.2.33.1.1.
The RELAY KEY REQUEST message is sent by the UE to the AMF for initiation of PC5 keys establishment with the 5G ProSe remote UE or the 5G ProSe end UE as specified in TS 33.503. See Table 8.2.34.1.
The RELAY AUTHENTICATION REQUEST message is sent by the network to the UE to initiate authentication of the 5G ProSe remote UE or the 5G ProSe end UE as specified in TS 33.503. See Table 8.2.37.1.
The RELAY AUTHENTICATION RESPONSE message is sent by the UE to the network to forward the authentication response from the 5G ProSe remote UE or the 5G ProSe end UE as specified in TS 33.503. See Table 8.2.38.1.