Description
The Globally Unique MME Identifier (GUMMEI) is a composite identifier that uniquely identifies a specific Mobility Management Entity (MME) node within the global network ecosystem of the Evolved Packet System (EPS) and 5G System (5GS). It is structured from three main components: the Public Land Mobile Network (PLMN) Identity (MCC and MNC), an MME Group ID (MMEGI), and an MME Code (MMEC). The PLMN Identity identifies the home network of the MME. The MMEGI identifies a group of MMEs within that PLMN, often used for load balancing and redundancy purposes. The MMEC is a code that uniquely identifies an MME within that specific MME Group. The concatenation of PLMN ID + MMEGI + MMEC guarantees global uniqueness. This structure is defined in technical specifications such as TS 23.003 and TS 36.413.
Architecturally, the GUMMEI is used extensively in signaling procedures between network entities. For instance, during the initial attach procedure or a Tracking Area Update (TAU), the eNodeB (in LTE) or gNB (in 5G NR) needs to select an MME for the UE. If the UE provides a previously assigned GUMMEI in its signaling (e.g., in the Globally Unique Temporary Identity, GUTI), the eNodeB can use the PLMN and MME Group ID parts to help route the message to the correct pool of MMEs. The network then uses the full GUMMEI to pinpoint the exact MME that holds the UE's context. The GUMMEI is also carried in messages between MMEs during inter-MME handovers (S10 interface) and between the MME and other core network functions like the Serving Gateway (SGW) and Home Subscriber Server (HSS).
Its role is critical for mobility management, session management, and network scalability. By providing a globally unique address for each MME, it prevents ambiguity in signaling routing, which is essential in interconnected networks involving roaming. The hierarchical structure (PLMN -> Group -> Node) supports efficient network planning. Operators can deploy pools of MMEs (sharing an MMEGI) for load distribution and resilience; if one MME fails, another in the same group can take over its UEs because the group-level identity is known. The GUMMEI is also a key component in deriving the GUTI, the temporary identifier assigned to the UE to protect its permanent subscriber identity (IMSI). The security and uniqueness of the GUMMEI underpin the integrity of this privacy mechanism. In 5GS, the equivalent concept for the Access and Mobility Management Function (AMF) is the GUAMI (Globally Unique AMF ID), which follows a similar structural principle, highlighting the foundational importance of this type of identifier in cellular core networks.
Purpose & Motivation
The GUMMEI was introduced in 3GPP Release 8 with the Evolved Packet Core (EPC) to solve the addressing and routing challenges inherent in a flat, all-IP core network architecture that replaced the hierarchical circuit-switched core of 2G/3G. In previous systems, node addressing was often more localized or tied to circuit-switching paradigms. EPC introduced a flatter architecture with a clear separation between the control plane (MME) and user plane (SGW/PGW), requiring a robust, scalable, and unambiguous way to identify control plane entities globally. The primary problem was ensuring that signaling messages for a mobile user, potentially roaming anywhere in the world, could be correctly routed to the specific MME currently managing that user's mobility context, even among many MMEs deployed in pools for high availability.
The creation of GUMMEI was motivated by several key requirements: First, global uniqueness to avoid conflicts in international roaming scenarios. Second, support for network pooling and load balancing, allowing multiple MMEs to serve a common geographic area. The Group ID component directly addresses this, enabling routing to a pool before selecting a specific node. Third, efficiency in signaling; the identifier is compact enough to be included in numerous messages without excessive overhead. Fourth, it enabled enhanced privacy through the GUTI. By having a unique MME identifier, the network could assign temporary identities that were traceable only by the network holding the mapping, protecting the user's IMSI from eavesdroppers. The GUMMEI solved these problems by providing a standardized, structured identifier that became a cornerstone for EPC and 5GC mobility management, facilitating the scalable deployment of LTE and 5G networks worldwide. Without it, managing mobility in large, distributed, multi-vendor networks would be significantly more complex and prone to errors.
Classification
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.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the GUMMEI function was extended to support interworking with 5G systems, specifically allowing a GUMMEI to be mapped from a 5G GUTI with an explicit indication during 5G interworking. This release also introduced procedures for using a 5G-GUTI in the creation of an ATTACH REQUEST message and included corrections for GUTI handling in single-registration mode. Furthermore, the release defined an extension of the GUMMEI Type itself.
- Clarification on eDRX handling with assigning a new GUTI TS 24.301CR2895
- Correction on inclusion of GUTI for UE in single-registration mode TS 24.301CR3119
- GUMMEI mapped from 5G GUTI with indication at 5G interworking TS 24.301CR3108
- Use of 5G-GUTI in creation of an ATTACH REQUEST message TS 24.301CR3152
- Extending GUMMEI Type TS 36.413CR1644
In Release 16, the enhancements to the GUMMEI function included the introduction of a Version Identifier within PLMN assigned identities and the new capability for UE radio capability ID assignment and deletion via the GUTI reallocation procedure. These changes provided a mechanism for versioning identifiers and integrated the management of radio capability identifiers with the existing temporary identifier reallocation process.
- UE radio capability ID assignment via GUTI reallocation procedure TS 24.301CR3328
- Temporary Identifier usage at interworking TS 36.413CR1643
- Inclusion of Version Identifier in PLMN assigned ID TS 23.401CR3561
- Deletion of UE Radio Capability ID using GUTI reallocation TS 23.401CR3587
- Alignment of the 5G ciphering and integrity algorithm identifiers TS 24.301CR3221
- Correction of connected en-gNB Identifier TS 36.300CR1289
In Release 17, the updates to the GUMMEI function focused on clarifying and correcting the handling of the mapped GUTI and Additional GUTI information element during inter-system mobility. Specifically, the release provided clarifications on the mapped GUTI terminology and defined the precise condition for including the Additional GUTI IE in a TAU Request message for an N1 mode to S1 mode change. Furthermore, it introduced the handling of UE radio capability IDs within the GUTI REALLOCATION COMMAND message.
- Include Additional GUTI IE in TAU request for N1 mode to S1 mode change TS 24.301CR3428
- Handling UE radio capability IDs in GUTI REALLOCATION COMMAND message TS 24.301CR3489
- Correction to definition of mapped GUTI TS 24.301CR3633
- Condition for inclusion of Additional GUTI IE in the TAU Request TS 24.301CR3681
- Clarifications on the mapped GUTI terminology TS 24.301CR3715
In Release 18, the GUMMEI function was updated to ensure identifier availability for Lawful Interception during Inter-MME and MME-5GS handover procedures. The release also provided clarification for the use of satellite identifiers within this context. Furthermore, adjustments were made to ensure a consistent value name for the GUTI type associated with the GUMMEI.
In Release 19, the enhancements to the GUMMEI function focused on refining procedures related to the GUTI. Specifically, the release introduced a mechanism for Radio Access Technology (RAT) utilization control during GUTI reallocation and defined new UE actions to be taken upon GUTI deletion. These updates provided more granular control over identifier management without altering the fundamental structure of the GUMMEI itself.
Explore further
Broader topics and technologies where GUMMEI plays a role.
Defining Specifications
3GPP specifications that define or reference GUMMEI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.401 vj50 | Evolved Packet System (EPS) Stage 2 Description | Rel-19 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 |
| TS 36.413 vj10 | S1 Application Protocol (S1AP) | Rel-19 |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 |