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.
What changed in its specifications
The latest release-to-release comparison of specifications that define 5GMM. Each summary describes the whole specification, not only this term.
Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.
Full comparison in TS 24.301 →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 →Technology family
NAS mobility and session protocols · User Equipment › Protocol Layers (NAS)
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
5GMM behaviour was specified for access attempts: it initiates NAS transport or service request procedures for upper-layer requests, and handles barring and alleviation indications from lower layers.
- “5GMM shall initiate the NAS transport procedure as specified in subclause 5.4.5 to send the SMS in an UL NAS TRANSPORT message;” TS 24.501 v15.7.0
- “5GMM shall initiate the service request procedure as specified in subclause 5.6.1; and” TS 24.501 v15.7.0
- Introduction of 5GMM cause #15 TS 24.501CR0158
5GMM behaviour in 24.501 changed: access-attempt triggers now include MO IMS registration signalling, location requests and UE policy container transactions, with new NAS transport handling and barring rules.
- “if the event which triggered the access attempt was a request from upper layers to send a mobile originated location request, 5GMM shall initiate the NAS transport procedure” TS 24.501 v16.15.0
- Handling 5GMM cause #5 "PEI not accepted" TS 24.501CR0983
- Addition of LCS indication in 5GMM capability and 5GS NW capability TS 24.501CR1335
5GMM procedures and requirements were changed in TS 24.501, for example by extending NAS security protection to NAS IEs between UE and UDM and by adding 5GMM cause handling such as #76 and #78 for reject messages.
- “the procedures used for the protection of NAS IEs between the UE and the UDM. Security protection involves integrity protection and ciphering of the 5GMM messages.” TS 24.501 v17.18.1
- “e) REGISTRATION REJECT (if the 5GMM cause is not #76 or #78);” TS 24.501 v17.18.1
- Handling of a reject message including 5GMM cause value #78 without integrity protection TS 24.501CR3510
5GMM procedures changed in Rel-18: it now handles RAN timing synchronization status change by transitioning the UE from RRC-inactive to connected mode, plus new 5GMM cause handling and state coordination.
- “5GMM receives an indication from lower layers of the RAN timing synchronization status change, and decides to transition the UE from 5GMM-CONNECTED mode with RRC inactive indication” TS 24.501 v18.14.0
- Indication of support for reconnection to the network due to RAN timing synchronization status change via the 5GMM capability IE TS 24.501CR5056
- 5GMM state for unavailability period TS 24.501CR5458
5GMM behaviour was changed in TS 24.501: policy container transport now covers more services (A2XP, RSLPP), cause #78 handling gained location info, and 5GMM capability was updated for ProSe multi-hop relays and IM relay.
- “NAS signalling connection recovery during an ongoing UE-requested policy provisioning procedure for V2XP, ProSeP, A2XP, RSLPP or any combination of them” TS 24.501 v19.8.0
- Update 5GMM capability for 5G ProSe multi-hop relays TS 24.501CR6692
- “geographical location, if known by the UE, where the 5GMM cause value #78 was received over the satellite NG-RAN access technology” TS 24.501 v19.8.0
In Rel-20, the 5GMM protocol gained new UE capability bits (NSSAA-EPC, AIoTUR) in the 5GMM capability IE, and revised handling of 5GMM causes such as #27 and #28.
- “If the UE supports NSSAA over EPC, the UE shall set the NSSAA-EPC bit to "NSSAA over EPC supported" in the 5GMM capability IE” TS 24.501 v20.1.0
- “the UE may enable the N1 mode capability for the current PLMN after the ongoing NAS signalling connection is released.” TS 24.501 v20.1.0
- “the UE shall set the AIoTUR bit to "Operating as an AIoT UE reader supported" in the 5GMM capability IE” TS 24.501 v20.1.0
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 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| 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 |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 38.508 vj31 | 5G NR UE ICS Proforma | Rel-19 read |