Section: 5.4.5.2.2 UE-initiated NAS transport procedure initiation
Content: In the connected mode, the UE initiates the NAS transport procedure by sending the UL NAS TRANSPORT message to the AMF, as shown in figure 5.4.5.2.2.1. In case a) in subclause 5.4.5.2.1, the UE shall: - include the PDU session information (PDU session ID, old PDU session ID, S-NSSAI, mapped S-NSSAI (if available in roaming scenarios), DNN, request type, alternative S-NSSAI, MA PDU session information), if available; - set the Payload container type IE to "N1 SM information"; and - set the Payload container IE to the 5GSM message. The UE shall set the PDU session ID IE to the PDU session ID. If an old PDU session ID is to be included, the UE shall set the Old PDU session ID IE to the old PDU session ID. If an alternative S-NSSAI is to be included, the UE shall set the Alternative S-NSSAI IE to the alternative S-NSSAI and shall set the S-NSSAI IE to the S-NSSAI to be replaced. If an S-NSSAI is to be included, the UE shall set the S-NSSAI IE to the S-NSSAI selected for the PDU session from the allowed NSSAI for the current PLMN or SNPN, associated with the mapped S-NSSAI (if available in roaming scenarios). If a DNN is to be included, the UE shall set the DNN IE to the DNN. 5GSM procedures specified in clause 6 describe conditions for inclusion of the S-NSSAI, mapped S-NSSAI (if available in roaming scenarios), and the DNN. If a request type is to be included, the UE shall set the Request type IE to the request type. The request type is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message and the PDU SESSION MODIFICATION REQUEST message. If an MA PDU session information is to be included, the UE shall set the MA PDU session information IE to the MA PDU session information. The MA PDU session information is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message and the PDU SESSION MODIFICATION REQUEST message as specified in 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ]  [13B]. If the UE supports the non-3GPP access path switching for the PDU session and the AMF has indicated its support for the non-3GPP access path switching, the UE shall include the Non-3GPP access path switching indication information element and set the NAPS bit to "non-3GPP access path switching supported". The non-3GPP access path switching indication is not provided along 5GSM messages other than the PDU SESSION ESTABLISHMENT REQUEST message. In case b) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SMS"; and - set the Payload container IE to the SMS payload. Based on the UE preferences regarding access selection for mobile originated (MO) transmission of SMS over NAS as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ]  [8]: - when SMS over NAS is preferred to be sent over 3GPP access: the UE attempts to deliver MO SMS over NAS via the 3GPP access if the UE is registered over both 3GPP access and non-3GPP access. If the delivery of SMS over NAS via the 3GPP access is not available, the UE attempts to deliver MO SMS over NAS via the non-3GPP access; and - when SMS over NAS is preferred to be sent over non-3GPP access: the UE attempts to deliver MO SMS over NAS via the non-3GPP access if the UE is registered over both 3GPP access and non-3GPP access. If the delivery of SMS over NAS via the non-3GPP access is not available, the UE attempts to deliver MO SMS over NAS via the 3GPP access. In case c) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "LTE Positioning Protocol (LPP) message container"; - set the Payload container IE to the LPP message payload; and - set the Additional information IE to the routing information provided by the upper layer location services application. In case c1) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SLPP message container"; - set the Payload container IE to the SLPP message payload; and - set the Additional information IE to the routing information provided by the upper layer location services application. In case d) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "SOR transparent container"; and - set the Payload container IE to the UE acknowledgement due to successful reception of steering of roaming information, and; i) set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME" ; ii) set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME"; and iii) set the ME support of SOR-SNPN-SI-LS indicator to "SOR-SNPN-SI-LS supported by the ME", - in the Payload container IE carrying the acknowledgement (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ]  [5]). In case e) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UE policy container"; and - set the contents of the Payload container IE as specified in Annex D. In case f) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UE parameters update transparent container"; and - set the contents of the Payload container IE to the UE acknowledgement due to successful reception of UE parameters update data (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ]  [9]). In case g) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Location services message container"; - set the Payload container IE to the Location services message payload; - set the Additional information IE to the routing information, if preconfigured or provided by AMF in a previous procedure or provided by the upper layer location services application; and - include the Payload container information IE with the PRU bit set to "Payload container related to PRU" if the location services message payload is related to PRU (see 3GPP TS 24.080[ Mobile radio interface layer 3 supplementary services specification; Formats and coding ]  [13A]). NOTE: The AMF may configure the routing information to the UE during the PRU association procedure or the PRU disassociation procedure as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ]  [6B]. For case h), when the UE is located outside the LADN service area, the UE shall not perform the UE-initiated NAS transport procedure to send CIoT user data via the control plane for a PDU session for LADN. In case h) in subclause 5.4.5.2.1, the UE shall: - include the PDU session ID, and Release assistance indication (if available); - set the Payload container type IE to "CIoT user data container"; and - set the Payload container IE to the user data container. In case i) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Service-level-AA container"; and - set the Payload container IE to the Service-level-AA container. In case j) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "UPP-CMI container"; and - set the Payload container IE to the UPP-CMI container. In case k) in subclause 5.4.5.2.1, the UE shall: - set the Payload container type IE to "Multiple payloads"; and - set each payload container entry of the Payload container IE (see subclause 9.11.3.39), as follows: i) set the payload container type field of the payload container entry to a payload container type value set in the Payload container type IE as specified in cases a) to j) above; ii) set the payload container entry contents field of the payload container entry to the payload container contents set in the Payload container IE as specified in cases a) to j) above, and iii) set the optional IE fields, if any, to the optional associated payload routing information as specified in cases a) to j) above. Figure 5.4.5.2.2.1: UE-initiated NAS transport procedure