Section: 5.4.5.2.4 UE-initiated NAS transport of messages not accepted by the network
Content: 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[ System architecture for the 5G System (5GS) ]  [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 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 does not support S-NSSAI location validity information; b) the S-NSSAI is subject to NS-AoS; and c) the AMF determines that the UE is not in the NS-AoS, the AMF may send back to the UE the message which was not forwarded as specified in subclause 5.4.5.3.1 case h6), include the 5GMM cause #69 "insufficient resources for specific slice", and include a back-off timer. 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[ System architecture for the 5G System (5GS) ]  [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", "LTE Positioning Protocol (LPP) message container" or "UPP-CMI container" or "SLPP 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.