5.4.5 NAS transport procedure(s)

24.5013GPPNon-Access-Stratum (NAS) protocol for 5G System (5GS)Release 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.4.5.1 General

The purpose of the NAS transport procedures is to provide a transport of payload between the UE and the AMF. The type of the payload is identified by the Payload container type IE and includes one of the following:

a) a single 5GSM message;

b) SMS;

c) an LPP message (see 3GPP TS 37.355 [26]);

d) an SOR transparent container;

e) a UE policy container;

f) a UE parameters update transparent container;

g) a location services message (see 3GPP TS 24.080 [13A]);

h) a CIoT user data container;

i) a Service-level-AA container; or

j) Multiple payloads.

For payload type a) to e), g) and h), along with the payload, the NAS transport procedure may transport the associated information (e.g. PDU session information for 5GSM message payload).

For payload type j), the Payload container IE consists a list of payload container entries, where each of payload container entry contains the payload and optional associated information (e.g. PDU session information for 5GSM message payload).

NOTE: Payload type can be set to "Multiple payloads" if there are more than one payloads to be transported using the NAS transport procedures.

5.4.5.2 UE-initiated NAS transport procedure

5.4.5.2.1 General

The purpose of the UE-initiated NAS transport procedure is to provide a transport of:

a) a single 5GSM message as defined in subclause 8.3;

b) SMS (see 3GPP TS 24.011 [13]);

c) an LPP message;

d) an SOR transparent container;

e) a UE policy container; or

f) a UE parameters update transparent container;

g) a location services message;

h) a CIoT user data container;

i) a Service-level-AA container; or

j) multiple of the above types.

and:

– for a) to e), g) and h), optional associated payload routing information from the UE to the AMF in a 5GMM message; and

– for j), the Payload container IE consists a list of payload container entries, where each of the payload container entry contains the payload and optional associated payload routing information (e.g. PDU session information for 5GSM message payload).

5.4.5.2.2 UE-initiated NAS transport procedure initiation

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), 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 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 [13B].

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 [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 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 set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME" in the Payload container IE carrying the acknowledgement (see 3GPP TS 23.122 [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 [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; and

– set the Additional information IE to the routing information, if provided by the upper layer location services application.

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 "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 i) 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 i) above, and

iii) set the optional IE fields, if any, to the optional associated payload routing information as specified in cases a) to i) above.

Figure 5.4.5.2.2.1: UE-initiated NAS transport procedure

5.4.5.2.3 UE-initiated NAS transport of messages accepted by the network

Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to:

a) "N1 SM information", the AMF looks up a PDU session routing context for:

1) the UE and the PDU session ID IE in case the Old PDU session ID IE is not included, and:

NOTE 1: If the Old PDU session ID IE is not included in the UL NAS TRANSPORT message and the AMF has received a reallocation requested indication from the SMF, the AMF needs to ignore the reallocation requested indication.

i) if the AMF has a PDU session routing context for the PDU session ID and the UE, and the Request type IE is either not included or is included but set to other value than "initial request", "existing PDU session", "initial emergency request", "existing emergency PDU session" or "MA PDU request", the AMF shall send the 5GSM message, and the PDU session ID IE towards the SMF identified by the SMF ID of the PDU session routing context;

ii) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, the Request type IE is included and is set to "existing PDU session" or "MA PDU request", and the S-NSSAI associated with the PDU session identified by the PDU session ID is allowed for the target access type, the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN (if received) and the request type towards the SMF identified by the SMF ID of the PDU session routing context;

iii) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, and the Request type IE is included and is set to "initial request" or "MA PDU request":

A) the AMF shall select an SMF with following handlings in case the UE is not registered for onboarding services in SNPN:

If the S-NSSAI IE is not included and the allowed NSSAI contains:

– one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI;

– two or more S-NSSAIs and the user’s subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI that matches the default S-NSSAI as the S-NSSAI; or

– two or more S-NSSAIs and the user’s subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI.

If the DNN IE is included, the AMF shall use the UE requested DNN as the DNN determined by the AMF; and

If the DNN IE is not included, and the user’s subscription context obtained from UDM:

– contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN determined by the AMF; and

– does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN determined by the AMF;

A1) the AMF shall select an SMF with following handlings in case the UE is registered for onboarding services in SNPN:

– if the AMF onboarding configuration data does not contain a configured SMF used for onboarding services in SNPN and contains the S-NSSAI used for onboarding services in SNPN, the AMF shall use the S-NSSAI used for onboarding services in SNPN as the S-NSSAI;

– if the AMF onboarding configuration data does not contain a configured SMF used for onboarding services in SNPN and contains the DNN used for onboarding services in SNPN, the AMF shall use the DNN used for onboarding services in SNPN as the DNN;

– if the AMF onboarding configuration data does not contain the S-NSSAI used for onboarding services in SNPN, does not contain the DNN used for onboarding services in SNPN, and contains a configured SMF used for onboarding services in SNPN, the AMF shall select the configured SMF used for onboarding services in SNPN;

– if the AMF onboarding configuration data contains the S-NSSAI used for onboarding services in SNPN, the DNN used for onboarding services in SNPN, or both, and contains a configured SMF used for onboarding services in SNPN, the AMF shall use the S-NSSAI used for onboarding services in SNPN, if any, as the S-NSSAI, and use the DNN used for onboarding services in SNPN, if any, as the DNN or shall select the configured SMF used for onboarding services in SNPN, according to local policy; and

– if the AMF onboarding configuration data contains none of the S-NSSAI used for onboarding services in SNPN, the DNN used for onboarding services in SNPN and a configured SMF used for onboarding services in SNPN, the AMF handling is implementation specific; and

NOTE 2: The AMF can e.g. use a locally configured DNN used for onboarding services in SNPN as the DNN determined by the AMF.

NOTE 3: SMF selection is outside the scope of the present document.

NOTE 4: As part of SMF selection, the PCF can provide the AMF with a DNN selected by the network different from the DNN determined by the AMF.

B) if the SMF selection is successful:

– if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area;

– the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the SMF ID corresponding to the DNN in the user’s subscription context obtained from the UDM; and

– the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN determined by the AMF, DNN selected by the network (if different from DNN determined by the AMF), the request type, the MA PDU session information, UE presence in LADN service area (if DNN received corresponds to an LADN DNN, and the onboarding indication (if the UE is registered for onboarding services in SNPN) towards the SMF identified by the SMF ID of the PDU session routing context;

NOTE 5: The MA PDU session information is not sent towards the SMF if the DNN received corresponds to an LADN DNN.

iv) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "existing PDU session" or "MA PDU request", and the AMF retrieves an SMF ID associated with:

A) the PDU session ID matching the PDU session ID received from the UE, if any; or

B) the DNN matching the DNN received from the UE, otherwise;

such that the SMF ID includes a PLMN identity corresponding to the UE’s HPLMN or the current PLMN, then:

A) the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the retrieved SMF ID; and

B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN (if received) and the request type towards the SMF identified by the SMF ID of the PDU session routing context;

v) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial emergency request", and the AMF does not have a PDU session routing context for another PDU session ID of the UE indicating that the PDU session is an emergency PDU session:

A) the AMF shall select an SMF. The AMF shall use the emergency DNN from the AMF emergency configuration data as the DNN, if configured. The AMF shall derive the SMF from the emergency DNN or use the statically configured SMF from the AMF emergency configuration data, if configured; and

B) if the SMF selection is successful:

– the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the SMF ID of the selected SMF, and shall store an indication that the PDU session is an emergency PDU session in the stored PDU session routing context; and

– the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; and

vi) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial emergency request", and the AMF has a PDU session routing context indicating that the PDU session is an emergency PDU session for another PDU session ID of the UE:

A) the AMF shall store a PDU session routing context for the PDU session ID and the UE and shall set the SMF ID in the stored PDU session routing context to the SMF ID of the PDU session routing context for the other PDU session ID of the UE; and

B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data) and the request type towards the SMF identified by the SMF ID of the PDU session routing context; or

vii) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, and the Request type IE is included and is set to "existing emergency PDU session", the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; and

viii) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "existing emergency PDU session", and the AMF retrieves an SMF ID associated with emergency services such that the SMF ID includes a PLMN identity corresponding to the current PLMN, then:

A) the AMF shall store a PDU session routing context for the PDU session ID and the UE, shall set the SMF ID in the stored PDU session routing context to the retrieved SMF ID; and

B) the AMF shall send the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; or

2) the UE and the Old PDU session ID IE in case the Old PDU session ID IE is included, and:

i) the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial request", and the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reused, the AMF shall store a PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the SMF ID of the PDU session routing context for the old PDU session ID and the UE. If the DNN is a LADN DNN, the AMF shall determine the UE presence in LADN service area. The AMF shall send the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI (if received), the mapped S-NSSAI (in roaming scenarios), the DNN, the request type and UE presence in LADN service area (if DNN received corresponds to an LADN DNN) towards the SMF identified by the SMF ID of the PDU session routing context;

ii) the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is included and is set to "initial request", and the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reallocated:

A) the AMF shall select an SMF with the following handling;

If the S-NSSAI IE is not included and the allowed NSSAI contains:

– one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI;

If the DNN is a LADN DNN, the AMF shall determine the UE presence in LADN service area.

B) if the SMF selection is successful:

– the AMF shall store a PDU session routing context for the PDU session ID and the UE and set the SMF ID of the PDU session routing context to the SMF ID of the selected SMF; and

– the AMF shall send the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN, the request type, the MA PDU session information and UE presence in LADN service area (if DNN received corresponds to an LADN DNN) towards the SMF identified by the SMF ID of the PDU session routing context for the PDU session ID and the UE;

NOTE 6: The MA PDU session information is not sent towards the SMF if the DNN received corresponds to an LADN DNN.

b) "SMS", the AMF shall send the content of the Payload container IE to the SMSF associated with the UE;

c) "LTE Positioning Protocol (LPP) message container", the AMF shall send the Payload container type and the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE of the UL NAS TRANSPORT message;

d) "SOR transparent container", the AMF shall send the content of the Payload container IE to the UDM (see 3GPP TS 29.503 [20AB]);

e) "UE policy container", the AMF shall send the content of the Payload container IE to the PCF.

f) "UE parameters update transparent container", the AMF shall send the content of the Payload container IE to the UDM.

g) "Location services message container":

1) if the Additional information IE is not included in the UL NAS TRANSPORT message, the AMF shall provide the Payload container type and the content of the Payload container IE to the location services application; and

2) if the Additional information IE is included in the UL NAS TRANSPORT message, the AMF shall send the Payload container type and the content of the Payload container IE to an LMF associated with routing information included in the Additional information IE of the UL NAS TRANSPORT message.

h) "CIoT user data container", the AMF shall look up a PDU session routing context for the UE and the PDU session ID, and

1) send the content of the Payload container IE towards the SMF identified by the SMF ID of the PDU session routing context; and

2) initiate the release of the N1 NAS signalling connection:

i) if the Release assistance indication IE is included in the UL NAS TRANSPORT message and the DDX field of the Release assistance indication IE indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" and if there is no downlink signalling or downlink data for the UE; or

ii) upon subsequent delivery of the next received downlink data transmission to the UE if the Release assistance indication IE is included in the UL NAS TRANSPORT message and the DDX field of the Release assistance indication IE indicates "Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected" and if there is no additional downlink signalling or downlink data for the UE.

i) "Service-level-AA container" and the Service-level-AA container is included in the Payload container IE of the UL NAS TRANSPORT message, and the Service-level device ID included in the Service-level-AA container is set to a CAA-level UAV ID, the AMF shall send the content of the Payload container IE to the UAS-NF corresponding to the CAA-level UAV ID. If the Service-level device ID is not included in the Service-level-AA container and a CAA-level UAV ID is included in the 5GMM context of the UE, then the AMF shall send the content of the Payload container IE to the UAS-NF corresponding to the CAA-level UAV ID included in the 5GMM context of the UE.

j) "Multiple payloads", the AMF shall first decode the content of the Payload container IE (see subclause 9.11.3.39) to obtain the number of payload container entries and for each payload container entry, the AMF shall:

i) decode the payload container type field;

ii) decode the optional IE fields and the payload container contents field in the payload container entry; and

iii) handle the content of each payload container entry the same as the content of the Payload container IE and the associated optional IEs as specified in bullets a) to i) above according to the payload container type field.

5.4.5.2.4 UE-initiated NAS transport of messages not accepted by the network

Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information" and the UE is not configured for high priority access in selected PLMN or SNPN, and:

a) if the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request";

1) DNN based congestion control is activated for the DNN included in the UL NAS TRANSPORT message, or DNN based congestion control is activated for the selected DNN in case of no DNN included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #22 "congestion" as specified in subclause 5.4.5.3.1 case f);

2) S-NSSAI and DNN based congestion control is activated for the S-NSSAI and DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the S-NSSAI included in the UL NAS TRANSPORT message and the selected DNN in case of no DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI in case of no S-NSSAI included in the UL NAS TRANSPORT message and the DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI and the selected DNN in case of no S-NSSAI and no DNN included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #67 "insufficient resources for specific slice and DNN" as specified in subclause 5.4.5.3.1 case f);

3) S-NSSAI only based congestion control is activated for the S-NSSAI included in the UL NAS TRANSPORT message, or S-NSSAI based congestion control is activated for the selected S-NSSAI in case of no S-NSSAI included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #69 "insufficient resources for specific slice" as specified in subclause 5.4.5.3.1 case f);

b) void;

c) if the Request type IE is set to "modification request" and the PDU session is not an emergency PDU session;

1) DNN based congestion control is activated for the stored DNN, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #22 "congestion" as specified in subclause 5.4.5.3.1 case f);

2) S-NSSAI and DNN based congestion control is activated for the stored S-NSSAI and DNN, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #67 "insufficient resources for specific slice and DNN" as specified in subclause 5.4.5.3.1 case f);

3) S-NSSAI only based congestion control is activated for the stored S-NSSAI, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #69 "insufficient resources for specific slice" as specified in subclause 5.4.5.3.1 case f); or

d) the timer T3447 is running and the UE does not support service gap control:

1) the Request type IE:

i) is set to "initial request";

ii) is set to "existing PDU session"; or

iii) is set to "modification request" and the PDU session being modified is a non-emergency PDU session;

2) the current NAS signalling connection was not triggered by paging; and

3) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection,

the AMF shall send back to the UE the message which was not forwarded, send the 5GMM cause #22 "Congestion", and may include a back-off timer set to the remaining time of the timer T3447 as specified in subclause 5.4.5.3.1 case f).

Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request", and the AMF determines that the PLMN’s maximum number of PDU sessions has already been reached for the UE, the AMF shall send back to the UE the 5GSM message which was not forwarded and 5GMM cause #65 "maximum number of PDU sessions reached" as specified in subclause 5.4.5.3.1 case h).

Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", and

a) the UE is in NB-N1 mode;

b) the UE has indicated preference for user plane CIoT 5GS optimization;

c) the network accepted the use of user plane CIoT 5GS optimization; and

d) the AMF determines that there are user-plane resources established for a number of PDU sessions that is equal to the UE’ s maximum number of supported user-plane resources (see 3GPP TS 23.501 [8]),

the AMF shall either:

a) send back to the UE the message which was not forwarded as specified in in subclause 5.4.5.3.1 case h1); or

b) proceed with the PDU session establishment and include the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF.

Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "CIoT user data container", the UE is not configured for high priority access in selected PLMN, and:

a) the timer T3447 is running and the UE does not support service gap control;

b) the current NAS signalling connection was not triggered by paging; and

c) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection;

the AMF shall send back to the UE the CIoT user data which was not forwarded, send the 5GMM cause #22 "Congestion", and include a back-off timer set to the remaining time of the timer T3447 as specified in subclause 5.4.5.3.1 case l2).

Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "existing PDU session", and

a) the UE is in NB-N1 mode;

b) the UE has indicated preference for user plane CIoT 5GS optimization;

c) the network accepted the use of user plane CIoT 5GS optimization; and

d) the AMF determines that there are user-plane resources established for a number of PDU sessions that equals to the UE’s maximum number of supported user-plane resources (see 3GPP TS 23.501 [8]),

the AMF shall send back to the UE the message which was not forwarded as specified in in subclause 5.4.5.3.1 case h1).

Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request" or "modification request", the associated S-NSSAI that the AMF determined through the S-NSSAI IE or the PDU session ID IE is an S-NSSAI for which the AMF is performing NSSAA, and the AMF determines to not forward the 5GSM message to the SMF based on local policy, the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case h2).

Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "SMS" or "LTE Positioning Protocol (LPP) message container", the UE is not configured for high priority access in selected PLMN, and:

a) the timer T3447 is running and the UE does not support service gap control;

b) the current NAS signalling connection was not triggered by paging; and

c) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection;

the AMF shall abort the procedure.

NOTE 1: In this state the NAS signalling connection can be released by the network.

Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", and:

a) the determined DNN, S-NSSAI or both DNN and S-NSSAI are identified for UAS services; and

b) the UE is marked in the UE’s 5GMM context that it is not allowed to request UAS services;

the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case h4).

NOTE 2: The UE marked in the UE’s 5GMM context as not allowed to request UAS services happens in the case that the UUAA-MM procedure needs to be performed during the registration procedure according to operator policy.

5.4.5.2.5 Abnormal cases on the network side

The following abnormal cases in AMF are identified:

a) If the Payload container type IE is set to "N1 SM information" and:

1) if the Old PDU session ID IE is not included in the UL NAS TRANSPORT message, the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request" or "MA PDU request", and the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

2) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reallocated, and the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

3) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "existing PDU session" or "MA PDU request", and the user’s subscription context obtained from the UDM does not contain an SMF ID for the PDU session ID matching the PDU session ID received from the UE or for the DNN matching the DNN received from the UE such that the SMF ID includes a PLMN identity corresponding to the UE’s HPLMN or the current PLMN or the PLMN ID part of the current SNPN, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f).

4) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, and the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request" and the AMF has not received a reallocation requested indication, the AMF should select an SMF with following handlings:

i) if the S-NSSAI IE is not included and the allowed NSSAI contains:

A) one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI;

B) two or more S-NSSAIs and the user’s subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI; or

C) two or more S-NSSAIs and the user’s subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI;

ii) if the DNN IE is not included, and the user’s subscription context obtained from UDM:

A) contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN; and

B) does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN;

iii) if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area;

iv) if the SMF selection is successful, the AMF should store a PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the selected SMF ID, and forward the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN determined by the AMF, DNN selected by the network (if different from DNN determined by the AMF), the request type and UE presence in LADN service area (if DNN selected by the network corresponds to an LADN DNN) towards the SMF ID of the PDU session routing context; and

v) if the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

5) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, the Request type IE is set to "initial emergency request", the AMF should forward the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data) and the request type towards the SMF ID of the PDU session routing context;

6) if the Request type IE is set to "initial emergency request" and the S-NSSAI or the DNN is received, the AMF ignores the received S-NSSAI or the DNN and uses the emergency DNN from the AMF emergency configuration data, if any;

7) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, and the Request type IE of the UL NAS TRANSPORT message is either not provided or is provided but set to other value than "initial request", "existing PDU session", "initial emergency request", "existing emergency PDU session" and "MA PDU request", then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

8) if the AMF unsuccessfully attempted to forward the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN and the request type (if received) towards a SMF ID, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f).

9) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, the AMF does not have a PDU session routing context for the old PDU session ID and the UE, the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", the AMF should select an SMF with following handlings:

i) if the S-NSSAI IE is not included and the allowed NSSAI contains:

A) one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI;

B) two or more S-NSSAIs and the user’s subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the default S-NSSAI in the allowed NSSAI as the S-NSSAI; or

ii) if the DNN IE is not included, and the user’s subscription context obtained from UDM:

A) contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN; and

B) does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN;

iii) if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area;

v) if the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

10) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, and the Request type IE is included and is set to "existing emergency PDU session", the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

11) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, and the Request type IE is included and is set to "existing PDU session", the AMF may forward the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context;

12) if the AMF has a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", then the AMF shall perform a local release of the PDU session identified by the PDU session ID and shall request the SMF to perform a local release of the PDU session, and proceed as specified in subclause 5.4.5.2.3;

13) if the Request type IE is set to "initial request" or "modification request", and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e), case f) or h4);

14) if the Request type IE is set to "existing PDU session", the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, and the S-NSSAI associated with the PDU session identified by the PDU session ID is not allowed for the target access type, the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e), case f) or h4);

15) if the Request type IE is set to "initial request", "existing PDU session", "modification request" or "MA PDU request", the UE is not configured for high priority access in selected PLMN or SNPN, and the UE is in non-allowed area or is not in allowed area, the AMF shall send back to the UE the 5GSM message which was not forwarded, and 5GMM cause #28 "Restricted service area" as specified in subclause 5.4.5.3.1 case i);

15a) if the Request type IE is set to "initial request" or "initial emergency request" and the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case i1); and

16) if the Request type IE is set to "initial request" or "MA PDU request", the AMF is pending the receipt of a REGISTRATION REQUEST message indicating "mobility registration updating" in the 5GS registration type IE, and an emergency PDU session exists for the UE (see subclause 5.4.4.3), the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

17) if the timer T3447 is running and the UE supports service gap control and:

i) the Request type IE:

A) is set to "initial request";

B) is set to "existing PDU session"; or

C is set to "modification request" and the PDU session being modified is a non-emergency PDU session;

ii) the UE is not configured for high priority access in selected PLMN;

iii) the current NAS signalling connection was not triggered by paging; and

iv) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection,

then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

18) if the AMF has a PDU session routing context for the PDU session ID and the UE, the Request type IE is not included, the UE is not configured for high priority access in selected PLMN or SNPN, and the PDU session is not an emergency PDU session, then the AMF shall forward the 5GSM message, and the PDU session ID IE towards the SMF identified by the SMF ID of the PDU session routing context with:

i) an exemptionInd attribute indicating "message was exempted from the DNN based congestion activated in the AMF" as specified in 3GPP TS 29.502 [20A], if DNN based congestion control is activated for the selected DNN;

ii) an exemptionInd attribute indicating "message was exempted from the S-NSSAI and DNN based congestion activated in the AMF" as specified in 3GPP TS 29.502 [20A], if S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI and the selected DNN; or

iii) an exemptionInd attribute indicating "message was exempted from the S-NSSAI only based congestion activated in the AMF" as specified in 3GPP TS 29.502 [20A], if S-NSSAI only based congestion control is activated for the selected S-NSSAI;

19) if the Request type IE is set to "MA PDU request" and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network on neither access, then the AMF shall send to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f);

20) if the Request type IE is set to "initial request" and the UE is registered for emergency services over the current access, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); and

21) if the Request type IE is set to "existing PDU session", the UE is attempting to transfer a PDU session from 3GPP access to non-3GPP access, and the PDU session is associated with control plane only indication then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e).

22) if the Request type IE is set to "MA PDU request" and the UE requested DNN corresponds to an LADN DNN, the AMF shall send back to the UE the 5GSM message which was not forwarded and 5GMM cause #90 "payload was not forwarded" as specified in subclause 5.4.5.3.1 case hx).

23) if the Request type IE is set to "initial request", the UE requested DNN corresponds to an LADN DNN, and the MA PDU session information IE is included, the AMF shall not forward the MA PDU session information towards the SMF.

24) if the Request type IE is set to "modification request", the DNN associated with the PDU session corresponds to an LADN DNN, and MA PDU session information IE is included, the AMF shall not forward the MA PDU session information towards the SMF.

b) If the Payload container type IE is set to "SMS" and:

1) the AMF does not have an SMSF address associated with the UE;

2) the AMF cannot forward the content of the Payload container IE to the SMSF associated with the SMSF address available in the AMF; or

3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location;

then the AMF shall abort the procedure.

c) If the Payload container type IE is set to "LTE Positioning Protocol (LPP) message container" and:

1) if the Additional information IE is not included in the UL NAS TRANSPORT message;

2) the AMF cannot forward the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE; or

3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location;

then the AMF shall abort the procedure.

d) If the Payload container type IE is set to "UE policy container" and:

1) the AMF does not have a PCF address associated with the UE;

2) the AMF cannot forward the content of the Payload container IE to the PCF associated with the PCF address available in the AMF; or

3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location;

then the AMF shall abort the procedure.

e) If the Payload container type IE is set to "Location services message container" and:

1) if the Additional information IE is included in the UL NAS TRANSPORT message and the AMF cannot forward the content of the Payload container IE to an LMF associated with the routing information included in the Additional information IE;or

2) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location;

then the AMF shall abort the procedure.

f) If the Payload container type IE is set to "SMS" or "LTE Positioning Protocol (LPP) message container":

1) the timer T3447 is running and the UE supports service gap control;

2) the UE is not configured for high priority access in selected PLMN;

3) the current NAS signalling connection was not triggered by paging; and

4) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection,

the AMF shall abort the procedure.

NOTE: In this state the N1 NAS signalling connection can be released by the network.

g) If the Payload container type IE is set to "CIoT user data container" and:

1) if the AMF does not have a PDU session routing context for the PDU session ID and the UE; or

2) if the AMF unsuccessfully attempted to forward the user data container and the PDU session ID,

then the AMF may send back to the UE the CIoT user data container which was not forwarded as specified in subclause 5.4.5.3.1 case l1).

h) If the Payload container type IE is set to "CIoT user data container":

1) if the timer T3447 is running and the UE supports service gap control;

2) the UE is not configured for high priority access in selected PLMN;

3) the current N1 NAS signalling connection was not triggered by paging; and

4) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection,

then the AMF shall send back to the UE the CIoT user data container which was not forwarded as specified in subclause 5.4.5.3.1 case l1).

i) If the Payload container type IE is set to "SOR transparent container", "UE prameters update transparent container", or "Service-level-AA container", and the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, then the AMF shall abort the procedure.

5.4.5.2.6 Abnormal cases in the UE

The following abnormal cases can be identified:

a) The lower layers indicate that the access attempt is barred.

The UE shall not start the UE-initiated NAS transport procedure. The UE stays in the current serving cell and applies the normal cell reselection process.

If the access category for the access attempt is 6 due to a request from upper layers to send a mobile originated SMS over NAS and the UE is registered to the network via both 3GPP access and non-3GPP access, the UE may transmit the UL NAS TRANSPORT message via non-3GPP access, if available.

Otherwise, the UE-initiated NAS transport procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated.

aa) The lower layers indicate that:

1) access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or

2) access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0.

The UE shall proceed as specified for case a. For additional UE requirements see subclause 4.5.5.

b) If the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request" or "MA PDU request" and registration procedure for mobility and periodic registration update is pending due to receipt by the UE of new network slicing information via the generic UE configuration update procedure with re-registration request; and an emergency PDU session exists then:

1) The UE shall not send the UL NAS TRANSPORT message; and

2) The UL NAS TRANSPORT message can be sent, if still necessary, after a successful procedure for mobility and periodic registration update.

c) Transmission failure of the UL NAS TRANSPORT message with change in the current TAI.

If the current TAI is not in the TAI list, the UE-initiated NAS transport procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated. The UL NAS TRANSPORT message can be sent, if still necessary, after a successful procedure for mobility and periodic registration update.

If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the UE-initiated NAS transport procedure.

d) Transmission failure of the UL NAS TRANSPORT message indication without change in the current TAI.

It is up to the UE implementation how to re-run the ongoing procedure that triggered the UE-initiated NAS transport procedure.

e) Void.

f) Timer T3447 is running.

The UE shall not send the UL NAS TRANSPORT message unless:

1) the Payload container type IE is set to "N1 SM information" and:

i) the Request type IE is set to:

A) "initial emergency request";

B) "existing emergency PDU session"; or

C) "modification request" and the PDU session being modified is an emergency PDU session (see error cases described in subclause 6.4.1.3 and subclause 6.3.2.3); or

ii) the Request type IE is not included and the PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session;

2) the UE is a UE configured for high priority access in selected PLMN;

3) a paging request triggered the establishment of the current NAS signalling connection; or

4) the UE in 5GMM-CONNECTED mode receives mobile terminated signalling or downlink data over the user-plane.

The UL NAS TRANSPORT message can be sent, if still necessary, when timer T3447 expires or timer T3447 is stopped.

g) The lower layers indicate that the RRC connection has been suspended.

The UE shall abort the UE-initiated NAS transport procedure.

h) Timer T3346 is running.

The UE shall not send the UL NAS TRANSPORT message unless:

1) the Payload container type IE is set to "N1 SM information" and:

i) the Request type IE is set to:

A) "initial emergency request";

B) "existing emergency PDU session"; or

C) "modification request" and the PDU session being modified is an emergency PDU session; or

ii) the Request type IE is not included and the PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session; or

2) the UE is a UE configured for high priority access in selected PLMN or SNPN.

The UL NAS TRANSPORT message can be sent, if still necessary, when timer T3346 expires.

i) NAS MAC calculation indication from lower layers.

If lower layers indicate to calculate an NAS MAC, the UE shall calculate an NAS MAC as specified in 3GPP TS 33.501 [24] and then provide the calculated NAS MAC and 5 least significant bits of the uplink NAS COUNT used to calculate the NAS MAC to lower layers (see 3GPP TS 36.331 [25A]). The UE shall increase the uplink NAS COUNT by one after the calculation of the NAS MAC.

5.4.5.3 Network-initiated NAS transport procedure

5.4.5.3.1 General

The purpose of the network-initiated NAS transport procedure is to provide a transport of:

a) a single 5GSM message;

b) SMS;

c) an LPP message;

d) an SOR transparent container;

e) a single uplink 5GSM message which was not forwarded due to routing failure;

f) a single uplink 5GSM message which was not forwarded due to congestion control;

g) a UE policy container;

h) a single uplink 5GSM message which was not forwarded, because the PLMN’s maximum number of PDU sessions has been reached;

h1) a single uplink 5GSM message which was not forwarded, because the maximum number of PDU sessions with active user-plane resources has been reached;

h2) a single uplink 5GSM message which was not forwarded, because of ongoing network slice-specific authentication and authorization procedure for the S-NSSAI that is requested;

h3) a single uplink 5GSM message which was not forwarded, because the UE requested to establish an MA PDU session for LADN DNN;

h4) a single uplink 5GSM message which was not forwarded, because the maximum number of UEs for a network slice has been reached;

h5) a single uplink 5GSM message which was not forwarded because the UE is marked in the UE’s 5GMM context that it is not allowed to request UAS services;

i) a single uplink 5GSM message which was not forwarded due to service area restrictions;

i1) a single uplink 5GSM message which was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location;

j) a UE parameters update transparent container;

k) a location services message;

l) a CIoT user data container;

l1) a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure;

l2) a single uplink CIoT user data container which was not forwarded due to congestion control;

m) a service-level-AA container;

m1) an event notification for upper layers; or

n) multiple of the above types.

from the AMF to the UE in a 5GMM message.

5.4.5.3.2 Network-initiated NAS transport procedure initiation

In 5GMM-CONNECTED mode, the AMF initiates the NAS transport procedure by sending the DL NAS TRANSPORT message, as shown in figure 5.4.5.3.2.1.

In case a) in subclause 5.4.5.3.1, i.e. upon reception from an SMF of a 5GSM message without an N1 SM delivery skip allowed indication for a UE or a 5GSM message with an N1 SM delivery skip allowed indication for a UE in the 5GMM-CONNECTED mode, the AMF shall:

a) include the PDU session information (PDU session ID) in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information"; and

c) set the Payload container IE to the 5GSM message.

In case b) in subclause 5.4.5.3.1, i.e. upon reception from an SMSF of an SMS payload, the AMF shall:

a) set the Payload container type IE to "SMS";

b) set the Payload container IE to the SMS payload; and

c) select the access type to deliver the DL NAS TRANSPORT message as follows in case the access type selection is required:

1) if the UE to receive the DL NAS TRANSPORT message is registered to the network via both 3GPP access and non-3GPP access, the 5GMM context of the UE indicates that SMS over NAS is allowed, the UE is in MICO mode, and the UE is in 5GMM-IDLE mode for 3GPP access and in 5GMM-CONNECTED mode for non-3GPP access, then the AMF selects non-3GPP access. Otherwise, the AMF selects either 3GPP access or non-3GPP access.

If the delivery of the DL NAS TRANSPORT message over 3GPP access has failed, the AMF may re-send the DL NAS TRANSPORT message over the non-3GPP access.

If the delivery of the DL NAS TRANSPORT message over non-3GPP access has failed, the AMF may re-send the DL NAS TRANSPORT message over the 3GPP access; and

2) otherwise, the AMF selects 3GPP access.

NOTE 1: The AMF selects an access type between 3GPP access and non-3GPP access based on operator policy.

In case c) in subclause 5.4.5.3.1 i.e. upon reception from an LMF of an LPP message payload, the AMF shall:

a) set the Payload container type IE to "LTE Positioning Protocol (LPP) message container";

b) set the Payload container IE to the LPP message payload received from the LMF;

c) set the Additional information IE to an LCS correlation identifier received from the LMF from which the LPP message was received.

NOTE 2: The LCS Correlation Identifier is assigned originally by the AMF except for LPP message transfer associated with event reporting for periodic or triggered location as described in subclause 6.3.1 of 3GPP TS 23.273 [6B], where the LMF assigns the correlation identifier. AMF and LMF assigned correlation identifiers can be distinguished by an implementation specific convention (e.g. use of a different number of octets) to enable an AMF to distinguish one from the other when received in the Additional Information IE in an UL NAS Transport message.

In case d) in subclause 5.4.5.3.1 i.e. upon reception of a steering of roaming information (see 3GPP TS 23.122 [5]) from the UDM to be forwarded to the UE, the AMF shall:

a) set the Payload container type IE to "SOR transparent container"; and

b) set the Payload container IE to the steering of roaming information received from the UDM (see 3GPP TS 29.503 [20AB]).

In case e) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to routing failure, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded;

d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded" or 5GMM cause #91 "DNN not supported or not subscribed in the slice".

The AMF sets the 5GMM cause IE to the 5GMM cause #91 "DNN not supported or not subscribed in the slice", if the 5GSM message could not be forwarded since SMF selection fails because:

1) the DNN is not supported in the slice identified by the S-NSSAI used by the AMF; or

2) neither the DNN provided by the UE nor the wildcard DNN are in the subscribed DNN list of the UE for the S-NSSAI used by the AMF.

Otherwise, the AMF sets the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded"; and

e) optionally include the Back-off timer value IE if the 5GMM cause IE is set to 5GMM cause #91 "DNN not supported or not subscribed in the slice" due to the DNN is not supported in the slice.

In case f) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to congestion control, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded;

d) set the 5GMM cause IE to the 5GMM cause #22 "Congestion", the 5GMM cause #67 "insufficient resources for specific slice and DNN" or the 5GMM cause #69 "insufficient resources for specific slice"; and

e) include the Back-off timer value IE.

In case g) in subclause 5.4.5.3.1, i.e. upon reception of a UE policy container from the PCF to be forwarded to the UE, the AMF shall:

a) set the Payload container type IE to "UE policy container"; and

b) set the Payload container IE to the UE policy container received from the PCF.

In case h) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the PLMN’s maximum number of PDU sessions has been reached, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #65 "maximum number of PDU sessions reached".

In case h1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the maximum number of PDU sessions with active user-plane resources has been reached, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #92 "insufficient user-plane resources for the PDU session".

In case h2) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE requested to establish a PDU session associated with an S-NSSAI or to modify a PDU session associated with an S-NSSAI for which:

a) the AMF is performing network slice-specific authentication and authorization and determined to reject the request based on local policy; or

b) the network slice-specific authentication and authorization has failed or the authorization has been revoked;

the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded".

In case h3) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE requested to establish an MA PDU session for LADN DNN, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded".

In case h4) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the maximum number of UEs for a network slice has been reached, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded;

d) set the 5GMM cause IE to the 5GMM cause #69 "insufficient resources for specific slice"; and

e) include the Back-off timer value IE.

For case h5) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE is marked in the UE’s 5GMM context that it is not allowed to request UAS services, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #79 "UAS services not allowed".

In case i) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to service area restrictions, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #28 "Restricted service area".

In case i1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "N1 SM information";

c) set the Payload container IE to the 5GSM message which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #78 "PLMN not allowed to operate at the present UE location".

In case j) in subclause 5.4.5.3.1 i.e. upon reception of UE parameters update data (see 3GPP TS 23.502 [9]) from the UDM to be forwarded to the UE, the AMF shall:

a) set the Payload container type IE to "UE parameters update transparent container"; and

b) set the contents of the Payload container IE to the UE parameters update data (see 3GPP TS 23.502 [9]) received from the UDM.

For case k) in subclause 5.4.5.3.1 upon reception from a location services application of a Location services message payload, the AMF shall:

a) set the Payload container type IE to "Location services message container"; and

b) set the Payload container IE to the Location services message payload.

For case k) in subclause 5.4.5.3.1 upon reception from an LMF of a Location services message payload, the AMF shall:

a) set the Payload container type IE to "Location services message container";

b) set the Payload container IE to the Location services message payload; and

c) set the Additional information IE to routing information associated with the LMF from which the Location services message payload was received.

NOTE 3: Case k) in subclause 5.4.5.3.1 supports transport of a Location services message container between a UE and an AMF and between a UE and an LMF. For transport between a UE and an LMF, the Additional information IE is included and provides routing information for the LMF. For transport between a UE and an AMF, the Additional information IE is not included.

In case l) in subclause 5.4.5.3.1, i.e. upon reception from an SMF of a user data container payload, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "CIoT user data container"; and

c) set the Payload container IE to the user data container.

For case l1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to "CIoT user data container";

c) set the Payload container IE to the CIoT user data container or control plane user data which was not forwarded; and

d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded".

NOTE 4: For case l1) in subclause 5.4.5.3.1, this is also applied for a single uplink CIoT user data container or control plane user data in the CONTROL PLANE SERVICE REQUEST message which was not forwarded due to routing failure.

For case l2) in subclause 5.4.5.3.1, i.e. upon sending a single uplink CIoT user data container which was not forwarded due to congestion control, the AMF shall:

a) include the PDU session ID in the PDU session ID IE;

b) set the Payload container type IE to " CIoT user data container";

c) set the Payload container IE to the CIoT user data container which was not forwarded;

In case m) in subclause 5.4.5.3.1, during UUAA-MM procedure, if the AMF receives the UUAA payload from the UAS-NF, the AMF shall:

a) include the service-level-AA payload with the value set to the payload; and

b) if a payload type associated with the payload is received, include the service-level-AA payload type with the value set to the payload type

In case m1) in subclause 5.4.5.3.1, i.e. if the AMF needs to send an event notification indicator for upper layers to the UE which set the "EventNotification" bit of the 5GMM capability IE in the last REGISTRATION REQUEST message to "Event notification supported", the AMF shall:

a) set the Payload container type IE to "Event notification"; and

b) set the Payload container IE to the event notification indicator.

In case n) in subclause 5.4.5.3.1, the AMF shall:

a) set the Payload container type IE to "Multiple payloads";

b) 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 for cases a) to m) 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 for cases a) to m) above;

iii) set the optional IE fields, if any, to the optional associated information as specified for cases a) to m) above.

Figure 5.4.5.3.2.1: Network-initiated NAS transport procedure

5.4.5.3.3 Network-initiated NAS transport of messages

Upon reception of a DL NAS TRANSPORT message, the UE shall stop the timer T3346 if running.

Upon reception of a DL NAS TRANSPORT message, if the Payload container type IE is set to:

a) "N1 SM information" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the 5GSM message in the Payload container IE and the PDU session ID are handled in the 5GSM procedures specified in clause 6;

b) "SMS", the UE shall forward the content of the Payload container IE to the SMS stack entity;

c) "LTE Positioning Protocol (LPP) message container", the UE shall forward the payload container type, the content of the Payload container IE and the routing information included in the Additional information IE to the upper layer location services application;

d) "SOR transparent container" and if the Payload container IE:

1) successfully passes the integrity check (see 3GPP TS 33.501 [24]), the ME shall store the received SOR counter as specified in annex C and proceed as follows:

i) If the Payload container IE indicates a list of preferred PLMN/access technology combinations is provided and the list type indicates "PLMN ID and access technology list", then the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME;

ii) If the list type indicates "secured packet", then the ME shall behave as if a SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of SOR transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040 [4A];

iii) If the Payload container IE includes SOR-SNPN-SI, the ME shall replace SOR-SNPN-SI of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription, as specified in 3GPP TS 23.122 [5] with the received SOR-SNPN-SI; and

iv) If the SOR-CMCI is present, in plain text, and the Store SOR-CMCI in ME indicator is set to "Store SOR-CMCI in ME" then the UE shall store or delete the SOR-CMCI in the non-volatile memory of the ME as described in annex C.1;

If the ACK bit of the SOR header for SOR data type in the SOR transparent container is set to "acknowledgement requested" and the list type indicates:

A) "PLMN ID and access technology list"; or

B) "secured packet" and the ME receives status bytes from the UICC indicating that the UICC has received the secured packet successfully;

then the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "SOR transparent container" as specified in subclause 5.4.5.2.2. In the Payload container IE carrying the acknowledgement, the UE shall set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is not operating in SNPN access operation mode, the UE may set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME".

The UE shall proceed with the behaviour as specified in 3GPP TS 23.122 [5] annex C; or

2) does not successfully pass the integrity check (see 3GPP TS 33.501 [24]) then the UE shall discard the content of the payload container IE and proceed with the behaviour as specified in 3GPP TS 23.122 [5] annex C.

e) Void;

f) Void;

g) "N1 SM information" and:

1) the 5GMM cause IE is set to the 5GMM cause #22 "Congestion", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to DNN based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

2) the 5GMM cause IE is set to the 5GMM cause #28 "Restricted service area", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to service area restrictions along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, enters the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE and, if the DL NAS TRANSPORT message is received over 3GPP access, performs the registration procedure for mobility and periodic registration update without waiting for the release of the N1 NAS signalling connection (see subclauses 5.3.5 and 5.5.1.3);

3) the 5GMM cause IE is set to the 5GMM cause #65 "maximum number of PDU sessions reached", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the PLMN’s maximum number of PDU sessions has been reached, along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message;

4) the 5GMM cause IE is set to the 5GMM cause #67 "insufficient resources for specific slice and DNN", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to S-NSSAI and DNN based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

5) the 5GMM cause IE is set to the 5GMM cause #69 "insufficient resources for specific slice", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

5a) the 5GMM cause IE is set to the 5GMM cause #78 "PLMN not allowed to operate at the present UE location", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message. Additionally, the UE shall not send the UL NAS TRANSPORT message to transport any of the data types listed in subclause 5.4.5.2.1;

6) the 5GMM cause IE is set to the 5GMM cause #90 "payload was not forwarded", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to routing failure along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message;

7) the 5GMM cause IE is set to the 5GMM cause #91 "DNN not supported or not subscribed in the slice", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the DNN is not supported or not subscribed in a slice along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE, if any;

8) the 5GMM cause IE is set to the 5GMM cause #92 "insufficient user-plane resources for the PDU session", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to insufficient user-plane resources along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message.

9) the 5GMM cause IE is set to the 5GMM cause #79 "UAS services not allowed", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the UE is marked in the UE’s 5GMM context that it is not allowed to request UAS services along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message.

h) "UE policy container", the UE policy container in the Payload container IE is handled in the UE policy delivery procedures specified in Annex D;

i) "UE parameters update transparent container" and if the Payload container IE

1) successfully passes the integrity check (see 3GPP TS 33.501 [24]), the ME shall store the received UE parameter update counter as specified in annex C and proceed as follows:

i) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data",

A) the ME shall behave as if an SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of UE parameters update transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040 [4A]; and

B) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the ME receives status bytes from the UICC indicating that the UICC has received the secured packet successfully, the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2; and

C) if the ME receives a REFRESH command from the UICC as specified in 3GPP TS 31.111 [22A] and if the REG bit of the UE parameters update header in the UE parameters update transparent container IE is set to "re-registration requested", and:

C1) the UE is registered over 3GPP access, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on non-3GPP access or the UE is not registered over non-3GPP access, or wait until the de-registration procedure over non-3GPP access specified in case C2) or C3) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on non-3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2;

C2) the UE is registered over non-3GPP access and does not have emergency services ongoing over non-3GPP access, then the UE shall locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on 3GPP access or the UE is not registered over 3GPP access, or wait until the de-registration procedure over 3GPP access specified in case C1) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on 3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; and

C3) the UE is registered over non-3GPP access and has an emergency services ongoing over non-3GPP access, then the UE shall wait until the emergency services are completed before locally releasing the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on 3GPP access or if the UE is not registered over 3GPP access, or wait until the de-registration procedure over 3GPP access specified in case C1) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on 3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2.

ii) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data",

A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2

B) the ME shall replace the stored default configured NSSAI with the default configured NSSAI included in the default configured NSSAI update data. In case of SNPN, the ME shall replace the stored default configured NSSAI associated with the selected entry of the "list of subscriber data" or the PLMN subscription with the default configured NSSAI included in the default configured NSSAI update data; and

C) if the REG bit of the UE parameters update header in the UE parameters update transparent container is set to "re-registration requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility registration update as specified in subclause 5.5.1.3.

if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE used the old default configured NSSAI to create the requested NSSAI in a REGISTRATION REQUEST message, the UE does not have a configured NSSAI for the current PLMN or SNPN and the UE has an allowed NSSAI for the current PLMN or SNPN which contains one or more S-NSSAIs that are not included in the new default configured NSSAI, the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; and

iii) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Disaster roaming information update data",

A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data" or a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2;

B) the UE shall delete the indication of whether disaster roaming is enabled in the UE stored in the ME, if any, and store the indication of whether disaster roaming is enabled in the UE included in the disaster roaming information update data in the ME;

C) the UE shall delete the indication of applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN’ stored in the ME, if any, and store the indication of ‘applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN’ included in the disaster roaming information update data in the ME; and

D) if the REG bit of the UE parameters update header in the UE parameters update transparent container is set to "re-registration requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility registration update as specified in subclause 5.5.1.3.

iv) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "ME routing indicator update data":

A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2;

B) the UE shall set or replace the routing indicator of the selected entry of the "list of subscriber data" with the routing indicator included in the ME routing indicator update data; and

C) if the REG bit of the UE parameters update header in the UE parameters update transparent container IE is set to "re-registration requested", and:

C1) the UE is registered over 3GPP access and is not registered over non-3GPP access, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication, perform a de-registration procedure, delete its 5G-GUTI, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2;

C2) the UE is registered over non-3GPP access and is not registered over 3GPP access, then the UE shall locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, delete its 5G-GUTI, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; or

C3) the UE is registered over 3GPP access and non-3GPP access to same SNPN, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, perform a de-registration procedure over 3GPP access, locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure over non-3GPP access, delete its 5G-GUTI and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2.

NOTE: The term "non-3GPP access" in an SNPN refers to the case where the UE is accessing SNPN services via a PLMN.

2) does not successfully pass the integrity check (see 3GPP TS 33.501 [24]) then the UE shall discard the content of the payload container IE;

j) "Location services message container" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the UE shall forward the payload container type, the content of the Payload container IE and the routing information in the Additional information IE if included to the upper layer location services application;

k) "CIoT user data container", the UE shall forward the content of the Payload container IE and the PDU session ID to the 5GSM sublayer;

l) "CIoT user data container" and:

1) the 5GMM cause IE is set to the 5GMM cause #22 "Congestion", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to DNN based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

2) the 5GMM cause IE is set to the 5GMM cause #67 "insufficient resources for specific slice and DNN", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to S-NSSAI and DNN based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

3) the 5GMM cause IE is set to the 5GMM cause #69 "insufficient resources for specific slice", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to S-NSSAI only based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE;

4) the 5GMM cause IE is set to the 5GMM cause #90 "payload was not forwarded", the UE passes to the 5GSM sublayer an indication that the user data container was not forwarded due to routing failure along with the user data container from the Payload container IE and the PDU session ID from the PDU session ID IE of the DL NAS TRANSPORT message.

m) "service-level-AA container", the UE shall forward the content of the Payload container IE to the upper layers;

m1) "Event notification", the UE shall forward the received event notification indicator(s) to the upper layers (see 3GPP TS 23.216 [6A] and 3GPP TS 24.237 [14AA] for the "SRVCC handover cancelled, IMS session re-establishment required" indicator); or

n) "Multiple payloads", the UE shall first decode the content of the Payload container IE (see subclause 9.11.3.39) to obtain the number of payload container entries and for each payload container entry, the UE shall:

1) decode the payload container type field;

2) decode the optional IE fields and the payload container contents field in the payload container entry; and

3) handle the content of each payload container entry the same as the content of the Payload container IE and the associated optional IEs as specified in bullets a) to m) above according to the payload container type field.