Description
The Globally Unique Temporary UE Identity (GUTI) is a fundamental privacy and efficiency mechanism in 3GPP's Evolved Packet System (EPS) and 5G System (5GS). Its primary role is to replace the use of the permanent, subscriber-sensitive Superscript Permanent Identifier (SUPI) – which in 4G is the IMSI – in most radio signaling messages. The GUTI is assigned by the core network's Mobility Management Entity (MME) in EPS or the Access and Mobility Management Function (AMF) in 5GS during initial registration or attachment procedures. Once assigned, the UE uses the GUTI to identify itself in subsequent signaling interactions, such as during service requests, tracking area updates, or handovers.
The structure of the GUTI is hierarchical and contains information that allows the network to efficiently route signaling and locate the node managing the UE's mobility context. In EPS, the GUTI is composed of a Globally Unique MME Identifier (GUMMEI) and an MME-Temporary Mobile Subscriber Identity (M-TMSI). The GUMMEI uniquely identifies the MME that allocated the GUTI, and the M-TMSI is a unique identifier for the UE within that MME. In 5GS, the equivalent structure comprises a Globally Unique AMF Identifier (GUAMI) and a 5G-TMSI. This structure means that when a network entity receives a message with a GUTI, it can immediately determine which MME/AMF is responsible for the UE's context.
The operational lifecycle of a GUTI involves assignment, re-assignment, and usage. It is assigned during initial registration. The network may re-assign a new GUTI during certain procedures, like inter-MME/AMF handovers or for periodic privacy refresh. The UE stores its assigned GUTI in non-volatile memory to use it after power cycles. A key procedure involving the GUTI is identification. If a network node (like a new MME during inter-MME handover) receives a GUTI it does not recognize, it uses the embedded GUMMEI/GUAMI to query the old MME/AMF for the UE's context and permanent identity (IMSI/SUPI). This mechanism allows for seamless mobility and context transfer while still shielding the permanent identity on the radio link.
Purpose & Motivation
The GUTI was introduced primarily to address critical user privacy concerns associated with the permanent IMSI. In earlier 2G/3G systems, the IMSI was frequently sent in clear text over the radio interface, making it vulnerable to interception and tracking by passive eavesdroppers. An attacker could collect IMSIs to profile user locations, movements, and habits—a significant privacy breach. The GUTI solves this by acting as a pseudonym; the sensitive IMSI/SUPI is transmitted only during exceptional, secured initial procedures, and is otherwise replaced by the temporary GUTI.
Beyond privacy, the GUTI serves important network efficiency and operational purposes. The hierarchical structure of the GUTI (GUMMEI/GUAMI + TMSI) provides built-in routing information. This allows other network nodes, such as eNodeBs/gNBs or other MMEs/AMFs, to quickly determine the 'anchor' core network node managing the UE's session without needing complex lookups or broadcasting queries. This speeds up signaling procedures like handovers and paging.
The design of GUTI also supports scalability and network architecture evolution. By decoupling the temporary identity from the permanent one, operators can re-assign GUTIs independently (e.g., after a UE moves to a new MME/AMF area). This flexibility is crucial for load balancing, network optimization, and the distributed nature of 5G core networks. In essence, the GUTI is a cornerstone for enabling secure, efficient, and scalable mobility management in modern 3GPP systems.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the 5G-GUTI was newly defined for the 5G System to identify the UE and the AMF, constructed from a GUAMI and a 32-bit 5G-TMSI. This release also specified the procedures for mapping between the 5G-GUTI and the EPS GUTI during inter-system mobility between 5GS and E-UTRAN. Furthermore, it introduced clarifications on the allocation of a new 5G-GUTI during procedures like the Mobile Originated service request.
- 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
- Clarification on the allocation of 5G-GUTI TS 33.501CR0529
- Allocating new 5G-GUTI during the MO service request procedure TS 33.501CR0547
+ 1 more changes
In Release 16, the GUTI reallocation procedure was enhanced to include the assignment and deletion of a UE Radio Capability ID. This allowed the network to manage the UE's stored radio capability information directly through the existing GUTI reallocation mechanism, adding a new function to this identity management procedure.
In Release 17, key enhancements for the GUTI included clarifications and corrections to the definition and terminology of the mapped GUTI used during inter-system mobility, such as between 5GS and E-UTRAN. The release also introduced the inclusion of an Additional GUTI Information Element in the Tracking Area Update Request message for specific mode changes and aligned GUTI allocation procedures to best practices for generating unpredictable identifiers.
- 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
- Align GUTI allocation to best practices of unpredictable identifier generation TS 33.401CR0702
+ 1 more changes
In Release 18, changes to the GUTI function included removing the GUTI from the Registration Reject message for enhanced security and ensuring a consistent value name for the GUTI type across specifications. These updates refined the procedures for identity confidentiality and inter-system mobility, such as the mapping between GUTI and P-TMSI during handovers between E-UTRAN and GERAN/UTRAN.
In Release 19, the GUTI function was enhanced with new UE actions upon GUTI deletion and the introduction of RAT utilization control in GUTI reallocation procedures. Furthermore, a correction was made to the terminology regarding the 4G-GUTI to ensure specification clarity. These updates refine the management and security of the temporary identity across different radio access technologies.
Explore further
Broader topics and technologies where GUTI plays a role.
Defining Specifications
3GPP specifications that define or reference GUTI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.003 vj50 | Numbering, addressing and identification in 3GPP | Rel-19 |
| TS 23.251 vj00 | Network Sharing Stage 2 Specification | 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 29.303 vj10 | DNS Procedures for Evolved Packet System | Rel-19 |
| TS 31.117 vj10 | USIM Application Toolkit Test for Non-Removable UICC | Rel-19 |
| TS 31.127 vi40 | UICC-terminal interaction testing specification | Rel-18 |
| TS 33.126 vj30 | Lawful Interception Requirements | Rel-19 |
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 |
| TS 33.843 vf10 | Security Study for ProSe UE-to-Network Relay | Rel-15 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |