Description
The 5G Mobility Management (5GMM) protocol is a non-access stratum (NAS) protocol defined in 3GPP specifications, primarily in TS 24.501. It operates between the User Equipment (UE) and the Access and Mobility Management Function (AMF) in the 5G Core Network (5GC). 5GMM is responsible for managing the mobility and registration context of the UE, ensuring it can securely and efficiently access network services. It establishes and maintains the NAS signaling connection, which is essential for all control-plane communications between the UE and the core network, independent of the underlying radio access technology (e.g., NG-RAN, non-3GPP access).
5GMM operates based on specific states that define the UE's registration status with the network. The two primary states are 5GMM-REGISTERED and 5GMM-DEREGISTERED. In the REGISTERED state, the UE has successfully performed registration with the AMF, and a NAS signaling connection is established, allowing the UE to initiate service requests, receive paging, and maintain its mobility context. In the DEREGISTERED state, the UE is not registered, and the network does not maintain a context for it, though the UE may still perform initial registration procedures. 5GMM also manages substates like 5GMM-IDLE and 5GMM-CONNECTED, which reflect the connectivity status of the NAS signaling link.
Key procedures managed by 5GMM include initial registration, periodic registration update, mobility registration update (e.g., when the UE moves to a new tracking area), deregistration (initiated by the UE or network), and service request. The service request procedure is crucial as it transitions the UE from 5GMM-IDLE to 5GMM-CONNECTED mode to establish user-plane resources for data transfer. 5GMM also handles authentication and security by interacting with the Authentication Server Function (AUSF) and Security Anchor Function (SEAF) to ensure secure NAS signaling, including integrity protection and encryption of NAS messages.
5GMM is tightly integrated with other 5G core network functions. It works in conjunction with the Session Management Function (SMF) via the AMF to manage Protocol Data Unit (PDU) sessions. While 5GMM handles mobility and registration, session-specific parameters are managed by the 5G Session Management (5GSM) protocol. This separation allows for more flexible and scalable network architectures, supporting features like network slicing and edge computing. 5GMM also supports enhanced mobility scenarios, including handovers between 3GPP and non-3GPP access networks, and interworking with EPS (Evolved Packet System) for fallback scenarios.
Purpose & Motivation
5GMM was created as part of the 5G system architecture to address the limitations of the Evolved Packet System (EPS) Mobility Management (EMM) protocol used in 4G LTE. With the introduction of 5G, there was a need for a more flexible, scalable, and efficient mobility management protocol to support diverse use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). EMM, while effective for 4G, was not designed to handle the increased complexity, network slicing, and heterogeneous access integration required for 5G.
The primary problems 5GMM solves include simplifying signaling procedures to reduce latency, supporting seamless mobility across multiple access types (e.g., 3GPP NG-RAN, Wi-Fi, fixed networks), and enabling efficient network resource utilization. It introduces a service-based architecture (SBA) in the core network, where the AMF acts as a single entry point for NAS signaling, decoupling mobility management from session management. This separation allows for independent scaling and optimization of functions, which is critical for deploying network slices tailored to specific service requirements.
Historically, mobility management in previous generations (e.g., 4G EMM) was tightly coupled with session management, leading to less flexibility. 5GMM addresses this by defining clear state models and procedures that reduce signaling overhead and improve power efficiency for devices, especially IoT sensors. It also enhances security by incorporating new authentication frameworks and supporting concurrent multiple registrations for different network slices. The creation of 5GMM was motivated by the need to support a wider range of deployment scenarios, from dense urban areas to industrial IoT, while maintaining backward compatibility and interworking with 4G networks through procedures like handover and fallback.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (22 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- 5GMM parameter handling for TAU rejected with EMM cause #9 TS 24.301CR3047
- 5GMM context handling TS 24.301CR3063
- Correct 5GMM reference used in the handling of the emergency numbers procedures TS 24.301CR3088
- Update of handling of 5GMM parameters in EPS TS 24.301CR3115
- 5GMM parameters handling for 5GC interworking TS 24.301CR3131
- Definitions of 5GMM-IDLE mode and 5GMM-mode in TS 24.301 TS 24.301CR3214
- EMM causes handled as 5GMM causes received over 3GPP access TS 24.301CR3228
- Handling of 5GMM parameters for non-integrity protected reject messages in EPS TS 24.301CR3237
- 5GMM parameters handling for 4G ony causes TS 24.301CR3249
- Handing of 5GMM parameters during certain mobility registration failures TS 24.301CR3278
- Listing of 5GMM parameters to be handled for EMM cause #12 TS 24.301CR3315
- Use of Equivalent PLMN list in 5GMM TS 24.301CR3458
- 5GMM registration attempt counter reset for EMM reject causes TS 24.301CR3488
- Add 5GMM SR procedure for non-integrity protected reject message TS 24.301CR3524
- Handling of 5GMM parameters when EPS authentication is not accepted by the network TS 24.301CR3551
- 5GMM parameter handling in case of cause codes #13, #15 and #31 TS 24.301CR3562
- 5GMM parameter handling in service request procedure receiving with cause code #13, #15 TS 24.301CR3719
+ 1 more changes
Explore further
Broader topics and technologies where 5GMM plays a role.
Defining Specifications
3GPP specifications that define or reference 5GMM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.301 vk00 | 3GPP TS 24301 vk00: NAS Protocols for EPS | Rel-20 |
| TS 24.501 vk00 | 5G System (5GS) Non-Access Stratum (NAS) Protocol | Rel-20 |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 |
| TS 29.214 vj30 | Rx Reference Point Stage 3 Specification | Rel-19 |
| TS 38.508 vj31 | 5G NR UE ICS Proforma | Rel-19 |