Two CM (Connection Management) statuses are used in the 5G (UE) system to reflect the NAS signaling connection between the terminal (UE) and the AMF. They are:
I. 5G Terminal (UE) Connection Status When the terminal accesses 3GPP and non-3GPP systems, its CM status is independent of each other. That is, one CM status can be in CM-IDLE state, while the other CM status can be in CM-CONNECTED state.
II. CM-IDLE State When in CM-IDLE:
2.1 The 5G terminal (UE)
2.2 When the UE state in the AMF is RM-REGISTERED, the terminal information required to initiate communication with the UE shall be stored. The AMF shall be able to retrieve the stored information required to initiate communication with the UE using 5G-GUTI. ---- In 5GS, paging is not required using the UE's SUPI/SUCI.
2.3 During AN signaling connection establishment, the UE shall provide 5G-S-TMSI as part of the AN parameters in accordance with TS 38.331[28] and TS 36.331[51]. When the UE establishes an AN signaling connection with the AN (entering the RRC_CONNECTED state via 3GPP access, establishing a UE-N3IWF connection via untrusted non-3GPP access, or establishing a UE-TNGF connection via trusted non-3GPP access), the UE shall enter the CM-CONNECTED state. Sending an initial NA message (registration request, service request, or deregistration request) initiates the transition from CM-IDLE to CM-CONNECTED state.
2.4 When the AMF is in the CM-IDLE or RM-REGISTERED state, the AMF should execute a network-triggered service request procedure when it needs to send signaling or mobile terminal data to the UE. This is done by sending a paging request to the UE (see Section 4.2.3.3 of TS 23.502[3]), provided that the UE is not unable to respond due to MICO mode or mobility restrictions. Among them:
III. CM-CONNECTED State The UE in the CM-CONNECTED state establishes a NAS signaling connection with the AMF through N1. NAS signaling connections utilize the RRC connection between the UE and the NG-RAN, and the NGAP UE association between the AN and the AMF, to achieve 3GPP access. The UE can be in the CM-CONNECTED state, but its NGAP UE association is not bound to any TNLA between the AN and the AMF.
For a UE in the CM-CONNECTED state, the AMF can decide to release the NAS signaling connection with the UE after the NAS signaling procedure is completed.
3.1 In the CM-CONNECTED state, the UE should:
3.2 When the UE's CM state in the AMF is CM-CONNECTED, the AMF shall:
--When the UE's logical NGAP signaling connection and N3 user plane connection are released after the AN release procedure specified in TS 23.502[3] is completed, the UE shall enter the CM-IDLE state.
--The AMF may maintain the UE's CM state in the CM-CONNECTED state until the UE is deregistered from the core network.
3.3 A UE in the CM-CONNECTED state may be in the RRC_INACTIVE state, see TS 38.300[27]. When the UE is in the RRC_INACTIVE state, the following rules apply: