注册和连接管理

参考TS23501 架构 version g60

5.3 Registration and Connection Management

5.3.1 General

The Registration Management is used to register or deregister a UE/user with the network, and establish the user context in the network. The Connection Management is used to establish and release the signalling connection between the UE and the AMF.

注册管理用于向网络注册或注销 UE/用户，并在网络中建立用户上下文。 Connection Management 用于建立和释放 UE 和 AMF 之间的信令连接。

5.3.2 Registration Management

5.3.2.1 General

A UE/user needs to register with the network to receive services that requires registration. Once registered and if applicable the UE updates its registration with the network (see TS 23.502 [3]):

• periodically, in order to remain reachable (Periodic Registration Update); or
• upon mobility (Mobility Registration Update); or
• to update its capabilities or re-negotiate protocol parameters (Mobility Registration Update).

UE/用户需要向网络注册才能接收需要注册的服务。注册后，如果适用，UE 更新其与网络的注册（参见 TS 23.502 [3]）：

• 定期，以保持可达（定期注册更新）；或者
• 移动时（移动注册更新）；或者
• 更新其能力或重新协商协议参数（移动注册更新）。

The Initial Registration procedure involves execution of Network Access Control functions as defined in clause 5.2 (i.e. user authentication and access authorization based on subscription profiles in UDM). As result of the Registration procedure, the identifier of the serving AMF serving the UE in the access through which the UE has registered will be registered in UDM.

初始注册程序涉及执行第 5.2 节中定义的网络访问控制功能（即基于 UDM 中的订阅配置文件的用户身份验证和访问授权）。作为注册过程的结果，在 UE 已经注册的接入中为 UE 服务的服务 AMF 的标识符将在 UDM 中注册。

The registration management procedures are applicable over both 3GPP access and Non-3GPP access. The 3GPP and Non-3GPP RM states are independent of each other, see clause 5.3.2.4.

注册管理程序适用于 3GPP 接入和非 3GPP 接入。 3GPP 和非 3GPP RM 状态相互独立，见第 5.3.2.4 节。

5.3.2.2 5GS Registration Management states

5.3.2.2.1 General

Two RM states are used in the UE and the AMF that reflect the registration status of the UE in the selected PLMN:

• RM-DEREGISTERED.
• RM-REGISTERED.

5.3.2.2.2 RM-DEREGISTERED state

In the RMDEREGISTERED state, the UE is not registered with the network. The UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF. However, some parts of UE context may still be stored in the UE and the AMF e.g. to avoid running an authentication procedure during every Registration procedure.

In the RM-DEREGISTERED state, the UE shall:

• attempt to register with the selected PLMN using the Initial Registration procedure if it needs to receive service that requires registration (see TS 23.502 [3] clause 4.2.2.2).
• remain in RM-DEREGISTERED state if receiving a Registration Reject upon Initial Registration (see TS 23.502 [3] clause 4.2.2.2).
• enter RM-REGISTERED state upon receiving a Registration Accept (see TS 23.502 [3] clause 4.2.2.2).

When the UE RM state in the AMF is RM-DEREGISTERED, the AMF shall:

• when applicable, accept the Initial Registration of a UE by sending a Registration Accept to this UE and enter RM-REGISTERED state for the UE (see TS 23.502 [3] clause 4.2.2.2); or
• when applicable, reject the Initial Registration of a UE by sending a Registration Reject to this UE (see TS 23.502 [3] clause 4.2.2.2).

5.3.2.2.3 RM-REGISTERED state

In the RMREGISTERED state, the UE is registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network.

In the RM-REGISTERED state, the UE shall:

• perform Mobility Registration Update procedure if the current TAI of the serving cell (see TS 37.340 [31]) is not in the list of TAIs that the UE has received from the network in order to maintain the registration and enable the AMF to page the UE;
• perform Periodic Registration Update procedure triggered by expiration of the periodic update timer to notify the network that the UE is still active.
• perform a Mobility Registration Update procedure to update its capability information or to re-negotiate protocol parameters with the network;
• perform Deregistration procedure (see TS 23.502 [3] clause 4.2.2.3.1), and enter RM-DEREGISTERED state, when the UE needs to be no longer registered with the PLMN. The UE may decide to deregister from the network at any time.
• enter RM-DEREGISTERED state when receiving a Registration Reject message or a Deregistration message. The actions of the UE depend upon the ‘cause value’ in the Registration Reject or Deregistration message. See TS 23.502 [3] clause 4.2.2.

When the UE RM state in the AMF is RM-REGISTERED, the AMF shall:

• perform Deregistration procedure (see TS 23.502 [3] clauses 4.2.2.3.2, 4.2.2.3.3), and enter RM-DEREGISTERED state for the UE, when the UE needs to be no longer registered with the PLMN. The network may decide to deregister the UE at any time;
• perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration;
• when applicable, accept or reject Registration Requests or Service Requests from the UE.

5.3.2.2.4 5GS Registration Management State models

Figure 5.3.2.2.4-1: RM state model in UE
Figure 5.3.2.2.4-2: RM state model in AMF

5.3.2.3 Registration Area management

Registration Area management comprises the functions to allocate and reallocate a Registration area to a UE. Registration area is managed per access type i.e., 3GPP access or Non-3GPP access.

When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE. When the AMF allocates registration area, i.e. the set of tracking areas in TAI List, to the UE it may take into account various information (e.g. Mobility Pattern and Allowed/Non-Allowed Area (refer to clause 5.3.4.1)). An AMF which has the whole PLMN as serving area may alternatively allocate the whole PLMN (“all PLMN”) as registration area to a UE in MICO mode (refer to clause 5.4.1.3).

The 5G System shall support allocating a Registration Area using a single TAI List which includes tracking areas of any NG-RAN nodes in the Registration Area for a UE.

A single TAI dedicated to Non-3GPP access, the N3GPP TAI, is defined in a PLMN and applies within the PLMN.

When a UE registers with the network over the Non-3GPP access, the AMF allocates a registration area that only includes the N3GPP TAI to the UE.

When generating the TAI list, the AMF shall include only TAIs that are applicable on the access type (i.e. 3GPP access or Non-3GPP access) where the TAI list is sent.

NOTE 1: To prevent extra signalling load resulting from Mobility Registration Update occurring at every RAT change, it is preferable to avoid generating a RAT-specific TAI list for a UE supporting more than one RAT.

For all 3GPP Access RATs in NG-RAN and for Non-3GPP Access, the 5G System supports the TAI format as specified in TS 23.003 [19] consisting of MCC, MNC and a 3-byte TAC only.

The additional aspects for registration management when a UE is registered over one access type while the UE is already registered over the other access type is further described in clause 5.3.2.4.

To ensure a UE initiates a Mobility Registration procedure when performing inter-RAT mobility to or from NB-IoT, a Tracking Area shall not contain both NB-IoT and other RATs cells (e.g. WB-E-UTRA, NR), and the AMF shall not allocate a TAI list that contains both NB-IoT and other RATs Tracking Areas.

For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs associated with the N2 interface and additionally the Tracking Area indicated by NG-RAN. When the UE is accessing NR using unlicensed bands, as defined in clause 5.4.8, an indication is provided in N2 interface as defined in TS 38.413 [34].

The AMF may also determine more precise RAT Type information based on further information received from NG-RAN:

• The AMF may determine the RAT Type to be LTE-M as defined in clause 5.31.20; or
• The AMF may determine the RAT Type to be NR using unlicensed bands, as defined in clause 5.4.8.

For Non-3GPP accesses the AMF determines the RAT type the UE is camping based on the 5G-AN node associated with N2 interface as follows:

• The RAT type is Untrusted Non-3GPP if the 5G-AN node has a Global N3IWF Node ID;
• The RAT type is Trusted Non-3GPP if the 5G-AN node has a Global TNGF Node ID or a Global TWIF Node ID; and
• The RAT type is Wireline -BBF if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline BBF Access Network. The RAT type is Wireline-Cable if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline Cable Access Network. If not possible to distinguish between the two, the RAT type is Wireline.

NOTE 2: How to differentiate between W-AGF supporting either Wireline BBF Access Network or the Wireline (e.g. different Global W-AGF Node ID IE or the Global W-AGF Node ID including a field to distinguish between them) is left to Stage 3 definition.

NOTE 3: If an operator supports only one kind of Wireline Access Network (either Wireline BBF Access Network or a Wireline Cable Access Network) the AMF may be configured to use RAT type Wireline or the specific one.

For Non-3GPP access the AMF may also use the User Location Information provided at N2 connection setup to determine a more precise RAT Type, e.g. identifying IEEE 802.11 access, Wireline-Cable access, Wireline-BBF access.

When the 5G-AN node has either a Global N3IWF Node ID, or a Global TNGF Node ID, or a Global TWIF Node ID, or a Global W-AGF Node ID, the Access Type is Non-3GPP Access.

5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access

This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to the 5G-RG.

For a given serving PLMN there is one RM context for a UE for each access, e.g. when the UE is consecutively or simultaneously served by a 3GPP access and by a non-3GPP access (i.e. via an N3IWF, TNGF and W-AGF) of the same PLMN. UDM manages separate/independent UE Registration procedures for each access.

When served by the same PLMN for 3GPP and non-3GPP accesses, an UE is served by the same AMF except in the temporary situation described in clause 5.17 i.e. after a mobility from EPS while the UE has PDU Sessions associated with non-3GPP access.

An AMF associates multiple access-specific RM contexts for an UE with:

• a 5G-GUTI that is common to both 3GPP and Non-3GPP accesses. This 5G-GUTI is globally unique.
• a Registration state per access type (3GPP / Non-3GPP)
• a Registration Area per access type: one Registration Area for 3GPP access and another Registration Area for non 3GPP access. Registration Areas for the 3GPP access and the Non-3GPP access are independent.
• timers for 3GPP access:
• a Periodic Registration timer; and
• a Mobile Reachable timer and an Implicit Deregistration timer.
• timers for non-3GPP access:
• a UE Non-3GPP Deregistration timer; and
• a Network Non-3GPP Implicit Deregistration timer.
  The AMF shall not provide a Periodic Registration Timer for the UE over a Non-3GPP access. Consequently, the UE need not perform Periodic Registration Update procedure over Non-3GPP access. Instead, during the Initial Registration procedure and Re-registration, the UE is provided by the network with a UE Non-3GPP Deregistration timer that starts when the UE enters non-3GPP CM-IDLE state.
  When the 3GPP access and the non-3GPP access for the same UE are served by the same PLMN, the AMF assigns the same 5G-GUTI for use over both accesses. Such a 5G-GUTI may be assigned or re-assigned over any of the 3GPP and Non-3GPP accesses. The 5G-GUTI is assigned upon a successful registration of the UE, and is valid over both 3GPP and Non-3GPP access to the same PLMN for the UE. Upon performing an initial access over the Non-3GPP access or over the 3GPP access while the UE is already registered with the 5G System over another access of the same PLMN, the UE provides the native 5G-GUTI for the other access. This enables the AN to select an AMF that maintains the UE context created at the previous Registration procedure via the GUAMI derived from the 5G-GUTI, and enables the AMF to correlate the UE request to the existing UE context via the 5G-GUTI.
  If the UE is performing registration over one access and intends to perform registration over the other access in the same PLMN (e.g. the 3GPP access and the selected N3IWF, TNGF or W-AGF are located in the same PLMN), the UE shall not initiate the registration over the other access until the Registration procedure over first access is completed.
  NOTE: To which access the UE performs registration first is up to UE implementation.
  When the UE is successfully registered to an access (3GPP access or Non-3GPP access respectively) and the UE registers via the other access:
• if the second access is located in the same PLMN (e.g. the UE is registered via a 3GPP access and selects a N3IWF, TNGF or W-AGF located in the same PLMN), the UE shall use for the registration to the PLMN associated with the new access the 5G-GUTI that the UE has been provided with at the previous registration or UE configuration update procedure for the first access in the same PLMN. Upon successful completion of the registration to the second access, if the network included a 5G-GUTI in the Registration Accept, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration.
• if the second access is located in a PLMN different from the registered PLMN of the first access (i.e. not the registered PLMN), (e.g. the UE is registered to a 3GPP access and selects a N3IWF, TNGF or W-AGF located in a PLMN different from the PLMN of the 3GPP access, or the UE is registered over Non-3GPP and registers to a 3GPP access in a PLMN different from the PLMN of the N3IWF, TNGF or W-AGF), the UE shall use for the registration to the PLMN associated with the new access a 5G-GUTI only if it has got one previously received from a PLMN that is not the same as the PLMN the UE is already registered with. If the UE does not include a 5G-GUTI, the SUCI shall be used for the new registration. Upon successful completion of the registration to the second access, the UE has the two 5G-GUTIs (one per PLMN).
  A UE supporting registration over both 3GPP and Non-3GPP access to two PLMNs shall be able to handle two separate registrations, including two 5G-GUTIs, one per PLMN, and two associated equivalent PLMN lists.
  When a UE 5G-GUTI assigned during a Registration procedure over 3GPP (e.g. the UE registers first over a 3GPP access) is location-dependent, the same UE 5G-GUTI can be re-used over the Non-3GPP access when the selected N3IWF, TNGF or W-AGF function is in the same PLMN as the 3GPP access. When an UE 5G-GUTI is assigned during a Registration procedure performed over a Non 3GPP access (e.g. the UE registers first over a non-3GPP access), the UE 5G-GUTI may not be location-dependent, so that the UE 5G-GUTI may not be valid for NAS procedures over the 3GPP access and, in this case, a new AMF is allocated during the Registration procedure over the 3GPP access.
  When the UE is registered first via 3GPP access, if the UE registers to the same PLMN via Non-3GPP access, the UE shall send the GUAMI obtained via 3GPP access to the N3IWF, TNGF or W-AGF, which uses the received GUAMI to select the same AMF as the 3GPP access.
  The Deregistration Request message indicates whether it applies to the 3GPP access the Non-3GPP access, or both.
  If the UE is registered on both 3GPP and Non-3GPP accesses and it is in CM-IDLE over Non-3GPP access, then the UE or AMF may initiate a Deregistration procedure over the 3GPP access to deregister the UE only on the Non-3GPP access, in which case all the PDU Sessions which are associated with the Non-3GPP access shall be released.
  If the UE is registered on both 3GPP and non-3GPP accesses and it is in CM-IDLE over 3GPP access and in CM-CONNECTED over non-3GPP access, then the UE may initiate a Deregistration procedure over the non-3GPP access to deregister the UE only on the 3GPP access, in which case all the PDU Sessions which are associated with the 3GPP access shall be released.
  Registration Management over Non-3GPP access is further defined in clause 5.5.1.

5.3.3 Connection Management

5.3.3.1 General

Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN (RRC Connection over 3GPP access or UE-N3IWF connection over untrusted N3GPP access or UE-TNGF connection over trusted N3GPP access) and the N2 connection for this UE between the AN and the AMF.

5.3.3.2 5GS Connection Management states

5.3.3.2.1 General

Two CM states are used to reflect the NAS signalling Connection of the UE with the AMF:

• CM-IDLE
• CM-CONNECTED
  The CM state for 3GPP access and Non-3GPP access are independent of each other, i.e. one can be in CM-IDLE state at the same time when the other is in CM-CONNECTED state.

5.3.3.2.2 CM-IDLE state

A UE in CM-IDLE state has no NAS signalling connection established with the AMF over N1. The UE performs cell selection/cell reselection according to TS 38.304 [50] and PLMN selection according to TS 23.122 [17].
There are no AN signalling connection, N2 connection and N3 connections for the UE in the CM-IDLE state.
If the UE is both in CM-IDLE state and in RM-REGISTERED state, the UE shall, unless otherwise specified in clause 5.3.4.1:

• Respond to paging by performing a Service Request procedure (see TS 23.502 [3] clause 4.2.3.2), unless the UE is in MICO mode (see clause 5.4.1.3);
• perform a Service Request procedure when the UE has uplink signalling or user data to be sent (see TS 23.502 [3] clause 4.2.3.2). Specific conditions apply for LADN, see clause 5.6.5.
  When the UE state in the AMF is RM-REGISTERED, UE information required for initiating communication with the UE shall be stored. The AMF shall be able to retrieve stored information required for initiating communication with the UE using the 5G-GUTI.
  NOTE: In 5GS there is no need for paging using the SUPI/SUCI of the UE.
  The UE provides 5G-S-TMSI as part of AN parameters during AN signalling connection establishment as specified in TS 38.331 [28] and TS 36.331 [51]. The UE shall enter CM-CONNECTED state whenever an AN signalling connection is established between the UE and the AN (entering RRC Connected state over 3GPP access, or at the establishment of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access). The transmission of an Initial NAS message (Registration Request, Service Request or Deregistration Request) initiates the transition from CM-IDLE to CM-CONNECTED state.
  When the UE states in the AMF are CM-IDLE and RM-REGISTERED, the AMF shall:
• perform a network triggered Service Request procedure when it has signalling or mobile-terminated data to be sent to this UE, by sending a Paging Request to this UE (see TS 23.502 [3] clause 4.2.3.3), if a UE is not prevented from responding e.g. due to MICO mode or Mobility Restrictions.
  The AMF shall enter CM-CONNECTED state for the UE whenever an N2 connection is established for this UE between the AN and the AMF. The reception of initial N2 message (e.g., N2 INITIAL UE MESSAGE) initiates the transition of AMF from CM-IDLE to CM-CONNECTED state.
  The UE and the AMF may optimize the power efficiency and signalling efficiency of the UE when in CM-IDLE state e.g. by activating MICO mode (see clause 5.4.1.3).
  5.3.3.2.3 CM-CONNECTED state
  A UE in CM-CONNECTED state has a NAS signalling connection with the AMF over N1. A NAS signalling connection uses an RRC Connection between the UE and the NG-RAN and an NGAP UE association between the AN and the AMF for 3GPP access. A UE can be in CM-CONNECTED state with an NGAP UE association that is not bound to any TNLA between the AN and the AMF. See clause 5.21.1.2 for details on the state of NGAP UE association for an UE in CM-CONNECTED state. Upon completion of a NAS signalling procedure, the AMF may decide to release the NAS signalling connection with the UE.
  In the CM-CONNECTED state, the UE shall:
• enter CM-IDLE state whenever the AN signalling connection is released (entering RRC Idle state over 3GPP access or when the release of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access is detected by the UE), see TS 38.331 [28] for 3GPP access.
  When the UE CM state in the AMF is CM-CONNECTED, the AMF shall:
• enter CM-IDLE state for the UE whenever the logical NGAP signalling connection and the N3 user plane connection for this UE are released upon completion of the AN Release procedure as specified in TS 23.502 [3].
  The AMF may keep a UE CM state in the AMF in CM-CONNECTED state until the UE de-registers from the core network.
  A UE in CM-CONNECTED state can be in RRC Inactive state, see TS 38.300 [27]. When the UE is in RRC Inactive state the following applies:
• UE reachability is managed by the RAN, with assistance information from core network;
• UE paging is managed by the RAN.
• UE monitors for paging with UE’s CN (5G S-TMSI) and RAN identifier.

5.3.3.2.4 5GS Connection Management State models

Figure 5.3.3.2.4-2: CM state transition in AMF

When a UE enters CM-IDLE state, the UP connection of the PDU Sessions that were active on this access are deactivated.
NOTE: The activation of UP connection of PDU Sessions is documented in clause 5.6.8.
5.3.3.2.5 CM-CONNECTED with RRC Inactive state
RRC Inactive state applies to NG-RAN. UE support for RRC Inactive state is defined in TS 38.306 [69] for NR and TS 36.306 [70] for E-UTRA connected to 5GC. RRC Inactive is not supported by NB-IoT connected to 5GC.
The AMF shall provide assistance information to the NG-RAN, to assist the NG-RAN’s decision whether the UE can be sent to RRC Inactive state except due to some exceptional cases such as:

• PLMN (or AMF set) does not support RRC Inactive;
• The UE needs to be kept in CM-CONNECTED State (e.g. for tracking).
  The “RRC Inactive Assistance Information” includes:
• UE specific DRX values;
• UE specific extended idle mode DRX values (cycle length and Paging Time Window length);
• The Registration Area provided to the UE;
• Periodic Registration Update timer;
• If the AMF has enabled MICO mode for the UE, an indication that the UE is in MICO mode;
• Information from the UE identifier, as defined in TS 38.304 [50] for NR and TS 36.304 [52] for E-UTRA connected to 5GC, that allows the RAN to calculate the UE’s RAN paging occasions.
  The RRC Inactive Assistance Information mentioned above is provided by the AMF during N2 activation with the (new) serving NG-RAN node (i.e. during Registration, Service Request, Handover) to assist the NG RAN’s decision whether the UE can be sent to RRC Inactive state. If the AMF allocates a new Registration Area to the UE, the AMF should update the NG-RAN with the new Registration Area by sending the RRC Inactive Assistance Information accordingly.
  RRC Inactive state is part of RRC state machine, and it is up to the RAN to determine the conditions to enter RRC Inactive state. If any of the parameters included in the RRC Inactive Assistance Information changes as the result of NAS procedure, the AMF shall update the RRC Inactive Assistance Information to the NG-RAN node.
  When the UE is in CM-CONNECTED state, if the AMF has provided RRC Inactive assistance information, the RAN node may decide to move a UE to CM-CONNECTED with RRC Inactive state.
  The state and “endpoints” (in the case of Dual Connectivity configuration) of the N2 and N3 reference points are not changed by the UE entering CM-CONNECTED with RRC Inactive state. A UE in RRC inactive state is aware of the RAN Notification area and periodic RAN Notification Area Update timer.
  The 5GC network is not aware of the UE transitions between CM-CONNECTED with RRC Connected and CM-CONNECTED with RRC Inactive state, unless the 5GC network is notified via N2 notification procedure in TS 23.502 [3] clause 4.8.3.
  At transition into CM-CONNECTED with RRC Inactive state, the NG-RAN configures the UE with a periodic RAN Notification Area Update timer taking into account the value of the Periodic Registration Update timer value indicated in the RRC Inactive Assistance Information, and uses a guard timer with a value longer than the RAN Notification Area Update timer value provided to the UE.
  If the periodic RAN Notification Area Update guard timer expires in NG-RAN, the NG-RAN shall initiate AN Release procedure as specified in TS 23.502 [3], clause 4.2.6.
  When the UE is in CM-CONNECTED with RRC Inactive state, the UE performs PLMN selection procedures as defined in TS 23.122 [17] and TS 24.501 [47].
  When the UE is CM-CONNECTED with RRC Inactive state, the UE may resume the RRC Connection due to:
• Uplink data pending;
• Mobile initiated NAS signalling procedure;
• As a response to RAN paging;
• Notifying the network that it has left the RAN Notification Area;
• Upon periodic RAN Notification Area Update timer expiration.
  If the UE resumes the connection in a different NG-RAN node within the same PLMN or equivalent PLMN, the UE AS context is retrieved from the old NG-RAN node and a procedure is triggered towards the CN (see TS 23.502 [3], clause 4.8.2).
  NOTE 1: With Dual Connectivity configuration if the UE resumes the RRC connection in the Master RAN node, the Secondary RAN node configuration is defined in TS 38.300 [27].
  If the RAN paging procedure, as defined in TS 38.300 [27], is not successful in establishing contact with the UE the procedure shall be handled by the network as follows:
• If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see TS 23.502 [3], clause 4.2.6,) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery.
• If NG RAN has only pending user plane data for transmission, the NG-RAN node may keep the N2 connection active or initiate the AN Release procedure (see TS 23.502 [3], clause 4.2.6) based on local configuration in NG-RAN.
  NOTE 2: The user plane data which triggers the RAN paging can be lost, e.g. in the case of RAN paging failure.
  If a UE in CM-CONNECTED with RRC Inactive state performs cell selection to GERAN/UTRAN/E-UTRAN, it shall follow idle mode procedures of the selected RAT as specified in clause 5.17.
  In addition, a UE in CM-CONNECTED state with RRC Inactive state shall enter CM-IDLE state and initiates the NAS signalling recovery (see TS 24.501 [47]) in the following cases:
• If RRC resume procedure fails,
  If the UE receives Core Network paging,
• If the periodic RAN Notification Area Update timer expires and the UE cannot successfully resume the RRC Connection,
• In any other failure scenario that cannot be resolved in RRC Inactive state and requires the UE to move to CM-IDLE state.
  When a UE is in CM-CONNECTED with RRC Inactive state, and a trigger to change the UE’s NG-RAN UE Radio Capability information happens, the UE shall move to CM-IDLE state and initiate the procedure for updating UE Radio Capability defined in clause 5.4.4.1.
  When UE is in CM-CONNECTED with RRC Inactive state, if RAN has received Location Reporting Control message from AMF with the Reporting Type indicating single stand-alone report, the RAN shall perform RAN paging before reporting the location to AMF.
  When UE is in CM-CONNECTED with RRC Inactive state, if RAN has received Location Reporting Control message from AMF with the Reporting Type indicating continuously reporting whenever the UE changes cell, the RAN shall send a Location Report message to AMF including UE’s last known location with time stamp.
  When the UE is CM-CONNECTED with RRC Inactive state. If the AMF receives Nudm_UEContextManagement_DeregistrationNotification from UDM, the AMF shall initiate AN Release procedure as specified in TS 23.502 [3], clause 4.2.6.
  When UE is in CM-CONNECTED with RRC Inactive state, if RAN has received Location Reporting Control message from AMF with the Reporting Type of the Area Of Interest based reporting, the RAN shall send a Location Report message to AMF including UE presence in the Area Of Interest (i.e., IN, OUT, or UNKNOWN) and the UE’s last known location with time stamp.
  When the UE is in CM-CONNECTED with RRC Inactive state, if the old NG-RAN node that sents the UE into RRC Inactive state receives the downlink N2 signalling, it initiates the RAN paging as defined in TS 38.300 [27]. If the UE resumes the RRC Connection towards a different NG-RAN node, the old NG-RAN node includes the “UE Context Transfer” indication into a response container to the NF (e.g. AMF or SMF) that generates such N2 downlink signalling. Then the NF shall reattempt the same procedure when the path switch from the old NG-RAN node to the new NG-RAN node is complete.