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

Glossary term · Identifier

5G-GUTI

5G Globally Unique Temporary Identifier

Identifier →

5G-GUTI is a temporary identifier assigned to a UE in 5G networks to protect the user's permanent subscription identity, used for network access, paging, and service requests.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
6 specs
5G-GUTI Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The 5G-GUTI is a fundamental identifier in 5G system architecture, designed to uniquely and temporarily identify a User Equipment (UE) within the network. It serves as a privacy-preserving alias for the permanent Subscription Permanent Identifier (SUPI), ensuring that the user's long-term identity is not exposed during radio communication, which mitigates tracking and eavesdropping risks. The identifier is structured to support efficient network operations, including registration, service requests, and mobility management, by allowing the network to correlate sessions and context without repeatedly querying the SUPI.

Architecturally, the 5G-GUTI is assigned by the Access and Mobility Management Function (AMF) during initial registration procedures. It consists of two main components: the GUAMI (Globally Unique AMF Identifier) and the 5G-TMSI (5G Temporary Mobile Subscriber Identity). The GUAMI uniquely identifies the AMF that allocated the 5G-GUTI, comprising a Mobile Country Code (MCC), Mobile Network Code (MNC), and an AMF Region ID, AMF Set ID, and AMF Pointer. The 5G-TMSI is a unique identifier within that AMF, used to distinguish the UE locally. This hierarchical structure allows for scalable routing and management, as the network can determine the serving AMF from the GUAMI and then use the 5G-TMSI to locate the specific UE context.

In operation, the UE includes the 5G-GUTI in signaling messages, such as Registration Requests or Service Requests, to identify itself to the network. The AMF validates the 5G-GUTI to retrieve the UE's security context and subscription data from its local storage or the Unified Data Management (UDM). If the 5G-GUTI is invalid or expired, the network may initiate a re-authentication procedure, potentially requesting the SUPI securely. The identifier can be reallocated or updated during mobility events, like handovers or inter-AMF transfers, to reflect changes in the serving network entity. This dynamic assignment supports seamless mobility across different AMFs and network slices.

The role of the 5G-GUTI extends beyond identity protection; it is integral to network efficiency and scalability. By using a temporary identifier, the network reduces signaling overhead, as the AMF can quickly resolve the UE context without extensive database queries. It also facilitates paging and notification procedures, where the 5G-TMSI is used to page the UE within a specific area. In scenarios involving network slicing, the 5G-GUTI helps associate the UE with the appropriate slice instance, ensuring that mobility and service continuity are maintained across slice boundaries. Overall, the 5G-GUTI is a cornerstone of 5G security and operational design, balancing privacy, performance, and flexibility.

Purpose & Motivation

The 5G-GUTI was created to address critical privacy and security vulnerabilities present in previous mobile generations, such as 4G/LTE, where temporary identifiers like the GUTI could still be linked to permanent identities over time, enabling potential tracking. In 5G, enhanced privacy is a core requirement, driven by regulations like GDPR and increased user awareness. The 5G-GUTI solves this by providing a robust mechanism to obscure the SUPI during radio transmissions, preventing passive attackers from correlating user activities or locations with their permanent identity. This separation ensures that even if temporary identifiers are intercepted, they cannot be easily mapped to the user's long-term subscription.

Historically, identifiers in 2G/3G/4G networks, such as the IMSI or 4G-GUTI, had limitations in privacy protection and scalability. The 4G-GUTI, for example, could be used to track users if not frequently refreshed, and its structure was less optimized for distributed architectures like 5G's service-based interface. The 5G-GUTI introduces a more hierarchical and globally unique design, aligning with 5G's cloud-native and sliced network environments. It supports efficient mobility management across diverse deployment scenarios, including non-public networks and edge computing, by enabling clear routing to the correct AMF instance.

Furthermore, the 5G-GUTI addresses operational challenges in large-scale networks by reducing dependency on central databases for every UE interaction. By allowing the AMF to manage temporary identifiers locally, it decreases latency and signaling load, which is crucial for 5G's low-latency use cases like URLLC. The identifier also facilitates network slicing by embedding AMF-specific information, ensuring that UE contexts are handled within the appropriate slice. Overall, the 5G-GUTI embodies 5G's principles of enhanced security, privacy by design, and scalable architecture, solving legacy issues while enabling future innovations.

What changed in its specifications

The latest release-to-release comparison of specifications that define 5G-GUTI. Each summary describes the whole specification, not only this term.

TS 23.003Rel-18 → Rel-19

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

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Technology family

Subscriber and device identifiers · User Equipment

  1. Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
  2. Phase 2 IMEISV
  3. R96 TLLI
  4. R97 P-TMSI
  5. R98 CTSMSI
  6. Rel-5 IMPI, IMPU, Temporary Public User Identity
  7. Rel-8 GUTI, M-TMSI
  8. Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
  9. Rel-16 GCI, GLI, Truncated 5G-S-TMSI
  • 5G-GUTI counterpart in another generation: 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
  • 5G-GUTI extended by 5G-S-TMSI
    “The 5G-S-TMSI is the shortened form of the 5G-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 sources

Documented changes in 5 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.

Rel-15 introduced

5G-GUTI is first defined and specified in Rel-15: NAS procedures for its assignment and validity, its use for routing, and its mapping to the 4G GUTI.

  • Definition of 5G-GUTI and mapping between 5G-GUTI and EPS GUTI TS 23.003CR0480
  • “This procedure shall be initiated by the network to assign a new 5G-GUTI to the UE after a successful service request procedure” TS 24.501 v15.7.0
  • “the AMF shall consider both the old and the new 5G-GUTIs as valid until the old 5G-GUTI can be considered as invalid by the AMF” TS 24.501 v15.7.0
Rel-16 1 CR

Rel-16 changes 5G-GUTI handling: it is unique only within an SNPN, an SNPN UE accepts only a 5G-GUTI from the same SNPN, and old and new 5G-GUTIs stay valid in abnormal registration cases.

  • “when registering or registered to an SNPN, the UE shall only consider a 5G-GUTI previously assigned by the same SNPN as a valid 5G-GUTI” TS 24.501 v16.15.0
  • 5G-GUTI not globally unique in an SNPN TS 24.501CR1458
  • “the AMF shall consider both the old and the new 5G-GUTI as valid until the old 5G-GUTI can be considered as invalid” TS 24.501 v16.15.0
Rel-17 1 CR

In Rel-17 the UE and network handling of 5G-GUTI changed: UE identity provided to lower layers per access type, 5G-GUTI reallocation corrections, and SNPN and eDRX handling with old and new 5G-GUTI.

  • “the UE NAS shall provide the lower layers with the 5G-GUTI, if available, otherwise shall provide the lower layers with the SUCI;” TS 24.501 v17.18.1
  • “the network shall use the stored UE specific DRX parameter, if available, with the old 5G-GUTI and use the eDRX provided by the network with the new 5G-GUTI” TS 24.501 v17.18.1
  • 5G-GUTI reallocation after resume from 5GMM-IDLE mode with suspend indication due to paging TS 24.501CR2645
Rel-18 1 CR

5G-GUTI handling was changed: the UE status in the mapped-GUTI Attach now indicates 'not in 5GMM-REGISTERED', 5G-GUTI selection is corrected for equivalent SNPNs, and GUAMI/5G-S-TMSI provision is revised.

  • Equivalent SNPNs: 5G-GUTI selection TS 24.501CR4997
  • “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
  • “For untrusted non-3GPP access, if the UE does not hold a 5G-GUTI and the UE does not hold a 4G-GUTI” TS 24.501 v18.14.0
Rel-19 1 CR

UE behaviour on 5G-GUTI deletion in 5GMM-REGISTERED was specified (5U2 NOT UPDATED, delete TAI/ngKSI, enter 5GMM-DEREGISTERED), and 5G-GUTI handling on registration and rejection was updated.

  • “if the UE detects that the 5G-GUTI is deleted (e.g. due to a REFRESH command from the UICC as specified in 3GPP TS 31.111 [22A])” TS 24.501 v19.8.0
  • UE actions upon 5G-GUTI deletion TS 24.501CR6943
  • “is a MUSIM UE and needs to request a new 5G-GUTI assignment as specified in clause 5.5.1.3.2;” TS 24.501 v19.8.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read
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.518 vk10 AMF Service Based Interface Rel-20 read