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.
What changed in its specifications
The latest release-to-release comparison of specifications that define GUTI. Each summary describes the whole specification, not only this term.
Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.
Full comparison in TS 23.003 →Rel-19 brings only minor changes to TS 23.251: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.251 →Technology family
Subscriber and device identifiers · User Equipment
- Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
- Phase 2 IMEISV
- R96 TLLI
- R97 P-TMSI
- R98 CTSMSI
- Rel-5 IMPI, IMPU, Temporary Public User Identity
- Rel-8 GUTI, M-TMSI
- Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
- Rel-16 GCI, GLI, Truncated 5G-S-TMSI
- GUTI counterpart in another generation: 5G-GUTI
“For idle mode mobility from 5GS to EPS, the UE performs either TAU or Attach procedure with EPS GUTI mapped from 5G-GUTI sent as old Native GUTI” TS 23.501
- GUTI counterpart in another generation: P-TMSI
“the MME needs to map the RAI, P-TMSI (or TLLI) and the P-TMSI Signature (sent by the SGSN) to create the GUTI and compare it with the stored GUTI.” TS 23.003
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 12 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.
GUTI is specified for the first time for EPS: NAS procedures for allocating and reallocating it at attach and tracking area update, and its use as the UE's temporary identity.
- “If the message contains a GUTI, the UE shall use this GUTI as new temporary identity for EPS services and shall store the new GUTI.” TS 24.301 v8.10.0
- “If the MME assigns a new GUTI for the UE, a GUTI shall be included in the TRACKING AREA UPDATE ACCEPT message.” TS 24.301 v8.10.0
- “When the UE is camping on an E-UTRAN cell, the RAT-related TMSI is the GUTI” TS 24.301 v8.10.0
GUTI handling in EPS attach/TAU changed: the UE indicates its GUTI in the EPS mobile identity IE, and the MME allocates a new GUTI when the provided one is invalid or from another MME.
- “If the TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the UE shall indicate the GUTI in the EPS mobile identity IE.” TS 24.301 v9.11.0
- “the MME considers the GUTI provided by the UE is invalid, or the GUTI provided by the UE was assigned by another MME, the MME shall allocate a new GUTI” TS 24.301 v9.11.0
- “for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the TAI supplied by the eNodeB is different from that of the GUTI” TS 23.401 v9.16.0
Rel-10 adds native versus mapped GUTI definitions and an Old GUTI type indication that the UE sends in Attach and TAU Requests so the network can tell which kind of GUTI it received.
- “the network shall use the Old GUTI type IE to determine whether the mobile identity included in the EPS mobile identity IE is a native GUTI or a mapped GUTI” TS 24.301 v10.15.0
- “Native GUTI: A GUTI previously allocated by an MME.” TS 24.301 v10.15.0
- “The indication of mapped or native GUTI shall be signalled by the UE to the MME as an explicit indication in Attach Request and TAU Request messages.” TS 23.401 v10.13.0
If the GUTI/IMSI mapping was correct, the network now sends an AUTHENTICATION REJECT instead of just terminating; TIN is set to GUTI on usage setting or voice domain preference changes; a reject cause now sets EU2 and starts a timer.
- “the network should terminate the authentication procedure by sending an AUTHENTICATION REJECT message” TS 24.301 v11.14.0
- “The UE shall start an implementation specific timer, setting its value to 2 times the value of T” TS 24.301 v11.14.0
On lower layer failure before TRACKING AREA UPDATE COMPLETE, the network now also enters EMM-IDLE mode, and the UE stops timer T3312 when setting TIN to GUTI after a capability or DRX change.
- “the network shall abort the procedure, enter EMM-IDLE mode and shall consider both, the old and new GUTI as valid” TS 24.301 v12.13.0
- “the UE shall set the TIN to "GUTI" and shall stop the periodic routing area update timer T3312, if running;” TS 24.301 v12.13.0
GUTI handling changed: eDRX paging may use the S-TMSI of both old and new GUTI, the UE now also deletes the TAI list on rejection, and the GUTI reallocation procedure is used for DCN redirection.
- “may determine the next paging window from both old GUTI and new GUTI, and may first use the S-TMSI from the GUTI” TS 24.301 v13.12.0
- “shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs” TS 24.301 v13.12.0
- “the MME performs the GUTI reallocation procedure, includes the unchanged GUTI of the UE and a non-broadcast TAI” TS 23.401 v13.14.0
The GUTI reallocation procedure now lets the network optionally provide a new DCN-ID with the GUTI, and the UE stores it together with the PLMN code.
- “The GUTI REALLOCATION COMMAND message shall include a GUTI and may include a TAI list or a DCN-ID or both.” TS 24.301 v14.10.0
- “The purpose of the GUTI reallocation procedure is to allocate a GUTI and optionally to provide a new TAI list or a new DCN-ID or both” TS 24.301 v14.10.0
- DCN-ID in GUTI Reallocation Command Message TS 24.301CR2606
GUTI handling changed in Rel-15: a mapped GUTI is generated from the 5G-GUTI for 5GS interworking, and the UE's inclusion of GUTI in attach/TAU requests and eDRX handling with a new GUTI were specified.
- “the UE NAS shall provide the lower layers with the MME identifier part of the mapped GUTI, which is generated from the 5G-GUTI” TS 24.301 v15.8.0
- “if the UE holds a valid 5G-GUTI, the UE shall include a GUTI, mapped from 5G-GUTI into the EPS mobile identity IE” TS 24.301 v15.8.0
- Definition of 5G-GUTI and mapping between 5G-GUTI and EPS GUTI TS 23.003CR0480
The GUTI reallocation procedure was extended so the GUTI REALLOCATION COMMAND can carry or delete UE radio capability IDs (RACS) and several GUTI handling rules were clarified, including SNPN GUTI use.
- “The GUTI REALLOCATION COMMAND message shall include a GUTI and may include one or more of the following:” TS 24.301 v16.9.0
- “the MME may initiate the GUTI Reallocation procedure to provide the UE with the UE Radio Capability ID” TS 23.401 v16.14.0
- UE shall use the GUTI assigned by the same SNPN during registration TS 24.501CR2278
GUTI handling was changed in Rel-17: the mapped GUTI definition now covers a 5G-GUTI from an AMF, UE radio capability IDs are carried in GUTI REALLOCATION COMMAND, and the Additional GUTI IE is used for N1-to-S1 change.
- “Mapped GUTI: A GUTI which is mapped from a P-TMSI and an RAI allocated previously by an SGSN or a 5G-GUTI previously allocated by an AMF.” TS 24.301 v17.12.0
- 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
GUTI handling in EPS NAS procedures changed: the Old GUTI type value name was made consistent, the UE status in attach/TAU with a mapped GUTI changed, and T3402 starts only for a non-zero timer value.
- “include Old GUTI type IE with GUTI type set to "Native GUTI" and include the UE status IE with a 5GMM registration status set to "UE is not in 5GMM-REGISTERED state"” TS 24.301 v18.9.0
- Consistent value name for GUTI type TS 24.301CR3950
- Removing GUTI from Registration Reject TS 33.501CR1794
GUTI handling changed: GUTI REALLOCATION COMMAND can carry access technology utilization control, UE behaviour on GUTI deletion in EMM-REGISTERED was specified, and GUTI mapped from 5G-GUTI is used for disaster roaming.
- “if the UE detects that the GUTI is deleted (e.g. due to a REFRESH command from the UICC as specified in 3GPP TS 31.111 [17A])” TS 24.301 v19.8.0
- “If an Access technology utilization control IE was included in the GUTI REALLOCATION COMMAND message, the MME shall consider the new access technology utilization control information as valid” TS 24.301 v19.8.0
- UE actions upon GUTI deletion TS 24.301CR4442
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 vk10 | Numbering, Addressing and Identification | Rel-20 read |
| TS 23.251 vj00 | Network Sharing Stage 2 Specification | Rel-19 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 29.303 vk00 | DNS Procedures for EPS and 5G Interworking | Rel-20 read |
| TS 31.117 vj30 | USAT Tests for Non-Removable UICC | Rel-19 read |
| TS 31.127 vj00 | UE Application Behavioural Tests for Non-Removable UICC | Rel-19 read |
| TS 33.126 vj30 | Lawful Interception Requirements | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TS 33.843 vf10 | Security Study for ProSe UE-to-Network Relay | Rel-15 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |