Section: 5.3.1.3 Release of the N1 NAS signalling connection
Content: The signalling procedure for the release of the N1 NAS signalling connection is initiated by the network. In N1 mode, upon indication from lower layers that the access stratum connection has been released, the UE shall enter 5GMM-IDLE mode and consider the N1 NAS signalling connection released. If the UE in 3GPP access is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [22] then: - if the N1 NAS signalling connection that was released had been established for eCall over IMS was released, the UE shall start timer T3444; and - if the N1 NAS signalling connection that was released had been established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service was released, the UE shall start timer T3445. The UE shall start the timer T3447 if not already running when the N1 NAS signalling connection is released as specified in subclause 5.3.17. To allow the network to release the N1 NAS signalling connection, the UE: a) shall start the timer T3540 if the UE receives any of the 5GMM cause values #7, #11, #12, #13, #15, #27, #31, #62, #72, #73, #74, #75, #76, #78and the UE does not consider the received 5GMM cause value as abnormal case as specified in subclauses 5.5.1.2.7, 5.5.1.3.7 and 5.5.2.3.4; a1) shall start the timer T3540 if the UE receives a SERVICE REJECT, case i) in subclause 5.6.1.7 is applicable and the procedure was started from 5GMM-IDLE mode; b) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a REGISTRATION ACCEPT message which does not include a Pending NSSAI IE or UE radio capability ID deletion indication IE; 2) the UE has set the Follow-on request indicator to "No follow-on request pending" in the REGISTRATION REQUEST message; 3) the UE has not included the Uplink data status IE in the REGISTRATION REQUEST message, or the UE has included the Uplink data status IE in the REGISTRATION REQUEST message but the REGISTRATION ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; 4) the UE has not included the Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session(s) for which the UE allowed the user-plane resource to be re-established over 3GPP access in the REGISTRATION REQUEST message, or the UE has included the Allowed PDU session status IE in the REGISTRATION REQUEST message but the REGISTRATION ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established; 5) the registration procedure has been initiated in 5GMM-IDLE mode, or the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the REGISTRATION REQUEST message and the N1 NAS signalling connection release bit is set to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message; 6) the user-plane resources for PDU sessions have not been set up, except for the case the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the REGISTRATION REQUEST message and the N1 NAS signalling connection release bit is set to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message; 7) the UE need not request resources for V2X communication over PC5 reference point (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ]  [6C]); 8) the UE has included unavailability information and has not included the start of unavailability period in the REGISTRATION REQUEST message; 9) the UE need not request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ]  [6E]); and 10) the UE need not request resources for A2X communication over PC5 reference point (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ]  [6AB]); NOTE 1: The lower layers indicate when the user-plane resources for PDU sessions are successfully established or released. c) shall start the timer T3540 if the UE receives a REGISTRATION REJECT message indicating: the 5GMM cause value #9 or #10; d) shall start the timer T3540 if the UE receives a SERVICE REJECT message indicating: the 5GMM cause value #9, #10; or the 5GMM cause value #28 and with no emergency PDU session has been established; e) shall start the timer T3540 if: 1) the UE receives a CONFIGURATION UPDATE COMMAND message containing the Configuration update indication IE with the Registration bit set to "registration requested" and with: i) either new allowed NSSAI information or new configured NSSAI information or both included; ii) the network slicing subscription change indication; or iii) no other parameters; and 2) the user-plane resources for PDU sessions have not been set up; f) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a SERVICE ACCEPT message; 2) for the case that the UE sent the: i) SERVICE REQUEST message, the UE did not set the Service type IE to "signalling" or "high priority access", the UE has not included the Uplink data status IE in the SERVICE REQUEST message, or the UE has included the Uplink data status IE in the SERVICE REQUEST message but the SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; or ii) CONTROL PLANE SERVICE REQUEST message, the UE did not set the Control plane service type IE to "emergency services fallback", the UE has not included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; 3) the UE has not included the Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session(s) for which the UE allowed the user-plane resource to be re-established over 3GPP access in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Allowed PDU session status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established; 4) the service request procedure has been initiated in 5GMM-IDLE mode; 5) the user-plane resources for PDU sessions have not been set up; 6) the UE need not request resources for V2X communication over PC5 reference point (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ]  [6C]); 7) the UE need not request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ]  [6E]); and 8) the UE need not request resources for A2X communication over PC5 reference point (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ]  [6AB]); NOTE 2: The lower layers indicate when the user-plane resources for PDU sessions are successfully established or released. g) may start the timer T3540 if the UE receives any of the 5GMM cause values #3 or #6 or if it receives an AUTHENTICATION REJECT message; h) shall start the timer T3540 for a UE in 3GPP access upon completion of the configuration update procedure or the registration procedure if the UE does not have an emergency PDU session and: 1) the UE received a CONFIGURATION UPDATE COMMAND message or a REGISTRATION ACCEPT message while camping on a CAG cell and none of the CAG-ID(s) supported by the current CAG cell is authorized based on "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list"; 2) the UE received a CONFIGURATION UPDATE COMMAND message or a REGISTRATION ACCEPT message while camping on a non-CAG cell and the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells"; or 3) the UE received a CONFIGURATION UPDATE COMMAND message while camping on a CAG cell and the entry for the current PLMN in not included in the received "CAG information list"; or i) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a SERVICE ACCEPT message; and 2) the UE: - has set Request type to "NAS signalling connection release" in the UE request type IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message; or - has set Request type to "Rejection of paging" in the UE request type IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message and the UE receives a CONFIGURATION UPDATE COMMAND message; j) shall start the timer T3540 if: 1) the UE receives the 5GMM cause value #22 along with a T3346 value in the SERVICE REJECT message, the value indicates that the timer T3346 is neither zero nor deactivated and the service request procedure has been initiated in 5GMM-IDLE mode; or 2) the UE receives the 5GMM cause value #22 along with a T3346 value in the message different from the SERVICE REJECT message, and the value indicates that the timer T3346 is neither zero nor deactivated; or k) shall start the timer T3540 if the UE receives a DEREGISTRATION ACCEPT message. l) shall start the timer T3540 after the completion of the de-registration procedure, if the UE receives a DEREGISTRATION REQUEST message and the de-registration type indicates "re-registration required". Upon expiry of T3540, - in cases a), a1), b), f), g), h), i), j) and k) the UE shall locally release the established N1 NAS signalling connection; - in cases c) and d) the UE shall locally release the established N1 NAS signalling connection and the UE shall initiate the registration procedure as described in subclause 5.5.1.3 or 5.6.1.5; or - in case e), the UE shall locally release the established N1 NAS signalling connection and perform a new registration procedure as specified in subclause 5.5.1.3.2. - in case l), the UE shall locally release the established N1 NAS signalling connection and initiate the registration procedure as specified in subclause 5.5.1.2.2. In case a), - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. In case b) and f), - upon an indication from the lower layers that the user-plane resources for PDU sessions are set up, the UE shall stop timer T3540 and may send uplink signalling via the existing N1 NAS signalling connection or user data via user plane. If the uplink signalling is associated with emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and send the uplink signalling via the existing N1 NAS signalling connection; In case b), f) and i), - upon receipt of a DEREGISTRATION REQUEST message, the UE shall stop timer T3540 and respond to the network-initiated de-registration request via the existing N1 NAS signalling connection as specified in subclause 5.5.2.3; - upon receipt of a message of a network-initiated 5GMM common procedure , the UE shall stop timer T3540 and respond to the network-initiated 5GMM common procedure via the existing N1 NAS signalling connection as specified in subclause 5.4; - if there is no user-plane resources established for PDU sessions, upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.6.1; - if there is no user-plane resources established for PDU sessions, upon receiving a request from the upper layers to perform services other than emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall wait for the local release of the established N1 NAS signalling connection upon expiry of timer T3540 or wait for timer T3540 being stopped, before initiating NAS signalling; - upon receipt of a DL NAS TRANSPORT message, the UE shall stop timer T3540 and may send uplink signalling via the existing N1 NAS signalling connection; - upon reception of NOTIFICATION message as specified in subclause 5.6.3.1 case a), the UE shall stop timer T3540 and send uplink signalling via the existing N1 NAS signalling connection; or - upon initiation of registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.2.7 for cases h), i), j), subclause 5.5.1.3.7 for cases j), k) or subclause 5.5.1.3.2 for case a), the UE shall stop timer T3540. In case c) and d), - upon an indication from the lower layers that the access stratum connection has been released, the UE shall stop timer T3540 and perform a new registration procedure as specified in subclause 5.5.1.3.5 or 5.6.1.5. - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. In case e), - upon an indication from the lower layers that the access stratum connection has been released, the UE shall stop timer T3540 and perform a new registration procedure as specified in subclause 5.5.1.3.2. - upon an indication from the lower layers that the user-plane resources for PDU sessions are set up, the UE shall stop timer T3540 and may send user data via user plane. NOTE 3: In this case, the new registration procedure is performed when the UE moves to the 5GMM-IDLE mode. - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. If the UE had set the Follow-on request indicator to "Follow-on request pending" in the REGISTRATION REQUEST message due to pending uplink signalling but cannot send the pending signalling due to new service area restrictions received or due to network not supporting the feature as indicated in the REGISTRATION ACCEPT message (for example UE set the "Follow-on request pending" to send SMS over NAS but AMF notified "SMS over NAS not allowed") and if there is no further pending data or signalling and user plane resources have not been set up, the UE may locally release the established N1 NAS signalling connection upon completion of the registration procedure. NOTE 4: the UE is allowed to inform the lower layers that there is no 5GMM or 5GSM messages need to be sent over non-3GPP access if the UE receives a REGISTRATION REJECT message over non-3GPP access or a SERVICE REJECT message over non-3GPP access. If the timer T3540 is not running when the UE enters state 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH, the UE may locally release the N1 NAS signalling connection.