Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

5GMM

5G Mobility Management

Protocol →

5GMM is the 5G control-plane protocol that manages the mobility, registration, and connectivity of a UE to enable network access and service continuity.

Introduced
Rel-15
Where
Core Network › Evolved Packet Core
Specifications
5 specs
5GMM Description Purpose What changed Neighbours Detected Changes Specifications

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.

TS 24.301Rel-18 → Rel-19

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 →
TS 24.501Rel-18 → Rel-19

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 Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (214 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 32 changes
  • 5GMM parameter handling for TAU rejected with EMM cause #9 TS 24.301CR3047
  • 5GMM context handling TS 24.301CR3063
  • Introduction of 5GMM cause #15 TS 24.501CR0158
  • 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

+ 26 more changes

Rel-16 72 changes
  • 5GMM capability for SRVCC from NG-RAN to UTRAN TS 24.501CR1187
  • Abnormal case handling for receipt of 5GMM cause value #11 from a PLMN TS 24.501CR1229
  • 5GMM cause value for CAG TS 24.501CR1057
  • 5GMM capability update for eNS TS 24.501CR1316
  • Addition of LCS indication in 5GMM capability and 5GS NW capability TS 24.501CR1335
  • Ethernet header compression for CP CIoT – 5GMM aspects TS 24.501CR2165

+ 66 more changes

Rel-17 59 changes
  • New 5GMM cause for satellite access TS 24.501CR3101
  • MCC list for 5GMM message TS 24.501CR3100
  • 5GMM procedures for satellite access for reject cause on UE location - alternative handling TS 24.501CR3217
  • Support NSAG in 5GMM capability TS 24.501CR4295
  • Storage of 5GMM information for UEs in SNPN access operation mode TS 24.501CR3262
  • The handling of 5GMM#79 TS 24.501CR3947

+ 53 more changes

Rel-18 41 changes
  • Equivalent SNPNs usage in 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR4839
  • Equivalent SNPNs: NSSAIs, network-assigned UE radio capability ID, maximum number of established PDU sessions and 5GMM parameters in annex C stored per selected entry TS 24.501CR5027
  • 5GMM procedure updates for LADN per DNN & S-NSSAI TS 24.501CR5012
  • 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
  • Indicating Uplink data status IE considering multicast MBS session reception in 5GMM-CONNECTED mode with RRC inactive indication TS 24.501CR5321

+ 35 more changes

Rel-19 8 changes
  • Update 5GMM capability for 5G ProSe multi-hop relays TS 24.501CR6692
  • Update 5GMM capability for IM relay TS 24.501CR6937
  • Handling 5GMM parameters due to eCall inactivity procedure TS 24.301CR4272
  • Correction to the handling of the 5GMM parameters in eCALL-INACTIVE state. TS 24.301CR4514
  • 5GMM handling upon cause #83 TS 24.301CR4578
  • FTAI list handling for extended 5GMM cause with cause #15 TS 24.501CR6728

+ 2 more changes

Rel-20 2 changes
  • Clarification on the "Satellite Access Disabling for 5GMM cause #15" configuration TS 24.501CR7153
  • Correction of 5G ProSe-l2end in 5GMM capability IE TS 24.501CR7213

Defining Specifications

3GPP specifications that define or reference 5GMM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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