Description
The 5GMM-CONNECTED mode is one of the primary mobility management states defined in 3GPP TS 24.501 for the 5G System. It represents the state in which a User Equipment (UE) has an active NAS (Non-Access Stratum) signaling connection with the Access and Mobility Management Function (AMF) in the 5G core network. This state is fundamental to how the 5G system manages UE mobility, session management, and data transfer. The 5GMM-CONNECTED mode is distinct from the 5GMM-IDLE mode, where no NAS signaling connection exists and the UE is not actively communicating with the network at the NAS level.
In the 5GMM-CONNECTED mode, the UE can be connected over either 3GPP access (e.g., NR or LTE) or non-3GPP access (e.g., Wi-Fi or wireline). When the term is used standalone, as clarified in TS 24.501, it means the UE can be in 5GMM-CONNECTED mode over 3GPP access, over non-3GPP access, or potentially both simultaneously if the UE supports multi-access PDU sessions. This dual-access capability is a key feature of 5G, allowing seamless mobility and traffic steering across different access technologies. The AMF maintains the UE's connection management state and coordinates with the SMF (Session Management Function) for PDU session management.
The transition into 5GMM-CONNECTED mode occurs through a service request procedure or a registration procedure. When the UE has data to send or receives a paging message, it initiates a service request to establish the NAS signaling connection. The AMF, upon receiving the request, sets up the connection and moves the UE to 5GMM-CONNECTED mode. In this state, the UE can perform various procedures such as PDU session establishment, modification, and release, as well as mobility registration updates. The UE can also receive downlink data, as the network knows the UE's location at the cell level and can page or directly deliver data.
Mobility in 5GMM-CONNECTED mode is managed through handover procedures. When the UE moves and changes cells, the network performs a handover to maintain the connection. The AMF is informed of the new cell and may update the UE's location. For non-3GPP access, mobility is handled differently, often through the N3IWF (Non-3GPP Interworking Function) or TNGF (Trusted Non-3GPP Gateway Function), depending on whether the access is trusted or untrusted. The 5GMM-CONNECTED mode over non-3GPP access allows UEs to maintain connectivity through Wi-Fi or other technologies while still being managed by the 5G core network.
The 5GMM-CONNECTED mode also supports network slicing and QoS enforcement. When the UE is in this mode, the network can apply specific QoS policies to different PDU sessions and flows. The SMF and PCF work together to ensure that the UE's traffic is treated according to the subscribed QoS. Additionally, the 5GMM-CONNECTED mode enables features like reflective QoS, where the UE can derive QoS rules from received packets, and session continuity, where PDU sessions remain active during mobility events. The state is maintained until the UE or network initiates a release, or the UE becomes unreachable, at which point the UE transitions to 5GMM-IDLE mode.
Purpose & Motivation
The 5GMM-CONNECTED mode exists to provide a well-defined state in which the UE and the 5G core network can exchange signaling and user data efficiently. It solves the problem of managing UE connectivity in a dynamic network environment where UEs move, change access technologies, and require different levels of service. Before the introduction of 5GMM states, earlier systems like 4G had similar concepts (EMM-CONNECTED), but 5G introduced the need to handle multiple access types (3GPP and non-3GPP) and more complex session management. The 5GMM-CONNECTED mode allows the network to track the UE's location at the cell level, enabling fast paging and handover, and to maintain context for active sessions.
The concept was motivated by the need for seamless mobility and service continuity in 5G. In 5GMM-CONNECTED mode, the UE can perform handovers without dropping ongoing data sessions, which is critical for applications like voice calls, video streaming, and industrial control. The mode also supports the dual-access scenario, where a UE can be connected over both 3GPP and non-3GPP access simultaneously, allowing for features like access traffic steering, switching, and splitting (ATSSS). This flexibility is essential for operators who want to leverage both licensed and unlicensed spectrum.
Furthermore, the 5GMM-CONNECTED mode simplifies the network's handling of UE state. By clearly defining the connected state, the network can allocate resources, apply policies, and manage security contexts more efficiently. It also provides a basis for power saving features, as the UE can transition to idle mode when not actively communicating, reducing battery consumption. The standalone definition of 5GMM-CONNECTED mode, which encompasses both 3GPP and non-3GPP access, ensures that the term is used consistently across different access technologies and specifications.
What changed in its specifications
The latest release-to-release comparison of specifications that define 5GMM-CONNECTED mode. Each summary describes the whole specification, not only this term.
Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.
Full comparison in TS 24.501 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (17 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Updates to RRC fallback indication while in 5GMM-CONNECTED mode, or while in 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR0280
- Transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode triggered by radio capability update TS 24.501CR0454
- Stopping T3511 after transitioning to 5GMM-CONNECTED mode TS 24.501CR0635
- Initiation of Service Request after reception of Notification over non-3GPP while the UE is in 5GMM-CONNECTED mode with RRC inactive indication in the 3GPP access TS 24.501CR0720
- Registration upon change of UE radio capability during 5GMM-CONNECTED mode TS 24.501CR1586
- Correct parameters included by AMF during inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode TS 24.501CR2095
- Integrity check interworking in 5GMM-CONNECTED mode TS 24.501CR2215
- TA change during Authentication procedure in 5GMM-CONNECTED mode TS 24.501CR2092
- Consistency of terms "5GMM-IDLE mode over non-3GPP access" and "5GMM-CONNECTED mode over non-3GPP access" TS 24.501CR2828
- State transition from 5GMM-CONNECTED mode with RRC inactive indication to LIMITED-SERVICE TS 24.501CR2998
- Clarification of access control checks for specific procedures initiated in 5GMM-CONNECTED mode with RRC Inactive TS 24.501CR2913
- NAS connection release from 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR3623
- Resolve EN on SR for rejecting RAN paging in 5GMM-CONNECTED mode with RRC inactive TS 24.501CR3767
- UE performing deregistration procedure in 5GMM-CONNECTED mode TS 24.501CR3797
- Equivalent SNPNs usage in 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR4839
- Indicating Uplink data status IE considering multicast MBS session reception in 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR5321
- 5GSM message transfer in a TA with service area restrictions in 5GMM-CONNECTED mode TS 24.501CR5985
Defining Specifications
3GPP specifications that define or reference 5GMM-CONNECTED mode, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |