5.3.1.4 5GMM-CONNECTED mode with RRC inactive indication

This clause is only applicable for UE's 5GMM mode over 3GPP access. The 5GMM-CONNECTED mode with RRC inactive indication is not supported when the UE is in NB-N1 mode.

The UE is in 5GMM-CONNECTED mode with RRC inactive indication when the UE is in:

• 5GMM-CONNECTED mode over 3GPP access at the NAS layer; and
• RRC_INACTIVE state at the AS layer (see 3GPP TS 38.300 [27]).

Unless stated otherwise, the UE behaviour in 5GMM-CONNECTED mode with RRC inactive indication follows the UE behaviour in 5GMM-CONNECTED over 3GPP access, except that:

• the UE shall apply the mobility restrictions; and
• the UE shall perform the PLMN selection procedures

as in 5GMM-IDLE mode over 3GPP access.

The UE shall transition from 5GMM-CONNECTED mode over 3GPP access to 5GMM-CONNECTED mode with RRC inactive indication upon receiving an indication from the lower layers that the RRC connection has been suspended.

NOTE 1: Any pending procedure or uplink data packet when receiving an indication from the lower layers that the RRC connection has been suspended, triggers a request to the lower layers to transition to RRC_CONNECTED state. This is also the case when the pending procedure or uplink data packet triggered a previous request to the lower layers to transition to RRC_CONNECTED state.

If the UE in 3GPP access is configured for eCall only mode as specified in 3GPP TS 31.102 [22] then:

• if the UE with the N1 NAS signalling connection established for eCall over IMS moved to 5GMM-CONNECTED mode with RRC inactive indication, the UE shall stop, reset, and start timer T3444 with its initial value; and
• if the UE with the N1 NAS signalling connection established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service moved to 5GMM-CONNECTED mode with RRC inactive indication, the UE shall stop, reset, and start timer T3445 with its initial value.

Upon:

• a trigger of a procedure which requires sending of a NAS message different from a REGISTRATION REQUEST message with the NG-RAN-RCU bit of the 5GS update type IE set to "UE radio capability update needed";
• an uplink user data packet to be sent for a PDU session with suspended user-plane resources;
• a trigger to request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5;
• a trigger to request resources for V2X communication over PC5 (see 3GPP TS 23.287 [6C]); or
• a trigger to request resources for A2X communication over PC5 (see 3GPP TS 23.256 [6AB]);

the UE in 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access shall request the lower layers to transition to RRC_CONNECTED state (see 3GPP TS 38.300 [27]).

For case a) above, if the trigger of the procedure is to request the establishment of a PDU session associated with an S-NSSAI included in the partially allowed NSSAI, the UE shall request the lower layers to transition to RRC_CONNECTED state only if the current TA is in the list of TAs where the S-NSSAI is allowed.

For case a) above, if the trigger of the procedure is to request the establishment of a PDU session associated with an S-NSSAI which has S-NSSAI location validity information, the UE shall request the lower layers to transition to RRC_CONNECTED state only if the current cell is in the NS-AoS of the S-NSSAI.

For case b) above, the UE which supports S-NSSAI location validity information, and which has received S-NSSAI location validity information from the AMF, shall request the lower layers to transition to RRC_CONNECTED state only if the UE is inside the NS-AoS with respect to the S-NSSAI which is associated with the PDU session with suspended user-plane resources.

For case b) above, if the PDU session is associated with an S-NSSAI included in the partially allowed NSSAI, the UE shall request the lower layers to transition to RRC_CONNECTED state only if the current TA is in the list of TAs where the S-NSSAI is allowed.

NOTE 2: If the UE supports Small Data Transmission (SDT) (see 3GPP TS 38.300 [27]), the following applies:

• if the UE due to pending uplink NAS messages or user data packets is requesting the lower layers to transition to RRC_CONNECTED state, but has not received a response from the lower layers, the UE can send the pending NAS messages or user data packets to the lower layers, and can receive multiple downlink NAS messages or multiple downlink user data packets from the lower layers while the UE remains in 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access (i.e. without transitioning to 5GMM-CONNECTED mode). When the NAS layer triggers the transmission of pending uplink NAS messages or user data packets, and if the SDT is ongoing, the NAS layer will receive the response from the lower layers only after the SDT session has completed or failed;
• the NAS layer is not aware of the classification of NAS messages or the user data packets as belonging to the SDT session at the lower layers; and
• the setting of access category and the RRC establishment cause indicated to the lower layers when sending the pending uplink user data packets while the UE remains in 5GMM-CONNECTED mode with RRC inactive indication, is left to implementation.

Upon a trigger to send a REGISTRATION REQUEST message with the NG-RAN-RCU bit of the 5GS update type IE set to "UE radio capability update needed", the UE in 5GMM-CONNECTED mode with RRC inactive indication shall move to 5GMM-IDLE mode over 3GPP access and proceed with the registration procedure for mobility and periodic registration update as specified in clause 5.5.1.3.2.

The UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-CONNECTED mode over 3GPP access upon receiving an indication from the lower layers that the UE has transitioned to RRC_CONNECTED state (see 3GPP TS 38.300 [27]).

NOTE 3: The AMF can be aware of the transition between 5GMM-CONNECTED mode and 5GMM-CONNECTED mode with RRC inactive indication for a UE (see 3GPP TS 23.502 [9]).

The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon selection of a PLMN or SNPN that is not an equivalent PLMN or SNPN to the registered PLMN or SNPN. The UE shall not trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon entering a new PLMN or SNPN which is in the list of equivalent PLMNs or SNPNs.

The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon receiving REFRESH command from the UICC as specified in clause 5.4.5.3.3.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the RRC connection has been suspended, the UE shall stay in 5GMM-CONNECTED mode with RRC inactive indication. The UE shall re-initiate any pending procedure that had triggered the request to the lower layers to transition to RRC_CONNECTED state, if still needed.

When the UE in 5GMM-CONNECTED mode with RRC inactive indication receives a fallback indication from lower layers, and the UE has no pending NAS procedure and no pending uplink user data for PDU session(s) with user-plane resources already established, the UE shall:

• enter 5GMM-IDLE mode; and
• initiate the registration procedure for mobility and periodic registration update and include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any as in clause 5.5.1.3.

If the UE requests the lower layers to transition to RRC_CONNECTED state at initiation of a registration procedure, a service request procedure or a de-registration procedure, upon fallback indication from lower layers, the UE shall:

• enter 5GMM-IDLE mode;
• proceed with the pending procedure; and
• if the pending procedure is a service request or registration request procedure and the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message or the REGISTRATION REQUEST message does not include UE request type IE with Request type value set to "NAS signalling connection release", the UE shall include the Uplink data status IE in the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message or in the REGISTRATION REQUEST message, indicating the PDU session(s) without active user-plane resources for which the UE has pending user data to be sent, if any, and the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see clauses 5.5.1.3 and 5.6.1 for further details).

If the UE requests the lower layers to transition to RRC_CONNECTED state for other reason than initiation of a registration procedure, or for other reason than a service request procedure, or for other reason than a de-registration procedure, upon fallback indication from lower layers, the UE shall:

• enter 5GMM-IDLE mode;
• initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see clause 5.6.1 for further details). If the procedure that triggered the request to the lower layers to transition to RRC_CONNECTED state is the UE-initiated NAS transport procedure and the UE had SMS, location services message, or CIoT user data to send, the UE shall also include the SMS, location services message, or CIoT user data in the CONTROL PLANE SERVICE REQUEST message as described in clause 5.6.1.2.2; and
• upon successful service request procedure completion, proceed with any pending procedure.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives a fallback indication from lower layers, and the UE has pending uplink user data for PDU session(s) with user-plane resources already established but no pending NAS procedure, the UE shall:

• enter 5GMM-IDLE mode; and
• initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication (see clause 5.6.1 for further details).

In the above cases when the UE receives a fallback indication from lower layers, if the UE is in non-allowed area or not in allowed area, the UE shall behave as specified in clause 5.3.5.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the resumption of the RRC connection has failed, and:

• if the lower layers indicate that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0, the UE shall:
• stay in 5GMM-CONNECTED mode with RRC inactive indication;
• else, the UE shall:
• enter 5GMM-IDLE mode; and
• if the UE:
• does not have pending uplink user data for PDU session(s) with user-plane resources already established, initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for N1 NAS signalling connection recovery as specified for case f) in clause 5.5.1.3.2; or
• has pending uplink user data for PDU session(s) with user-plane resources already established or has pending NAS procedure other than a registration, service request, or de-registration procedure, then initiate the service request procedure for N1 NAS signalling connection recovery as specified for case i) or j) in clause 5.6.1.1.

NOTE 4: An indication from the lower layer that the RRC connection has been released with cause "RRC resume failure" can be considered as an indication that the resumption of the RRC connection has failed.

The UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access upon receiving from the lower layers:

• indication of transition from RRC_INACTIVE state to RRC_IDLE state; or
• indication of cell selection to E-UTRAN or another RAT that the UE supports.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers about the cell (re-)selection to different RAT that the UE supports, the UE shall initiate the registration procedure for mobility or periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) as specified in clause 5.5.1.3.2.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers of a transition from RRC_INACTIVE state to RRC_IDLE state and 5GMM-REGISTERED.LIMITED-SERVICE is entered, the UE shall subsequently upon entering state 5GMM-REGISTERED.NORMAL-SERVICE and if there is no uplink user data or signalling pending, initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for N1 NAS signalling connection recovery as specified in clause 5.5.1.3.2.

If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers about RAN paging and the MUSIM UE decides not to initiate the service request procedure with service type set to "mobile terminated services" or control plane service type set to "mobile terminating request" to respond to the RAN paging, the UE may initiate the service request procedure and set request type to "NAS signalling connection release" in the UE request type IE and service type to "signalling" in the SERVICE REQUEST message or set request type to "NAS signalling connection release" in the UE request type IE and control plane service type set to "mobile originating request" in the CONTROL PLANE SERVICE REQUEST message to reject the RAN paging as specified in clause 5.6.1.2 for case o of clause 5.6.1.1. The UE may include its paging restriction preferences in the Paging restriction IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message as specified in clause 5.6.1.2 for case o of clause 5.6.1.1.

NOTE 5: The interworking between the NAS layer and the AS layer triggered by RAN paging is up to UE implementation.

NOTE 6: As an implementation option, the MUSIM UE is allowed to not respond to RAN paging based on the information available in the paging message, e.g. voice service indication.

Upon receiving AMF paging indication from the lower layers, the UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access and handle the AMF paging same as the paging request received in the 5GMM-IDLE mode over 3GPP access as specified in clause 5.6.1.

If the UE supporting the reconnection to the network due to RAN timing synchronization status change has been requested to reconnect to the network upon receiving an indication of a change in the RAN timing synchronization status (see clauses 5.4.4.2, 5.5.1.2.4, and 5.5.1.3.4) and the UE receives an indication of a change in the RAN timing synchronization status, the UE in 5GMM-CONNECTED mode with RRC inactive indication shall request the lower layers to transition to RRC_CONNECTED state.