GUAMI

Globally Unique AMF Identifier

Identifier →
Introduced in Rel-15

GUAMI is a globally unique identifier for a 5G AMF instance, used to correctly route signaling messages for procedures like registration and handover.

Category
Identifier
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
17 specs
GUAMI Description Purpose Related Classification Detected Changes Specifications

Description

The Globally Unique AMF Identifier (GUAMI) is a structured identifier defined in 3GPP for the 5G System (5GS) that provides a globally unambiguous way to identify a specific instance of an Access and Mobility Management Function (AMF). An AMF is a core network function responsible for termination of NAS signaling, registration management, connection management, reachability management, and mobility management for User Equipment (UE). The GUAMI is constructed from three components: the Public Land Mobile Network (PLMN) Identifier (MCC and MNC), the AMF Region ID, the AMF Set ID, and the AMF Pointer. This hierarchical structure allows for efficient routing and scalability within and across PLMNs.

Architecturally, the GUAMI is assigned to each AMF instance by the network operator and is configured within the AMF's operational parameters. It is advertised by the AMF to other network functions, such as the Radio Access Network (RAN) nodes (gNBs) via the N2 interface and to other core functions like the Network Slice Selection Function (NSSF) via service-based interfaces. When a UE initiates registration to the 5G network, the RAN node uses the GUAMI, often derived from the Temporary Mobile Subscriber Identity (5G-S-TMSI) or provided in the initial NAS message, to select an appropriate AMF for the UE's request. The GUAMI enables the RAN to route the initial UE message to the correct AMF instance, even in deployments with multiple AMFs for load balancing and redundancy.

Operationally, the GUAMI plays a key role in several procedures. During registration, if the UE provides a GUAMI from a previous registration (within the 5G-GUTI), the network can use it to efficiently retrieve the UE's context. In mobility scenarios like handovers, the source AMF includes its GUAMI in the handover request to the target, ensuring the target system can identify and communicate with the correct AMF. For paging, the RAN uses the GUAMI to determine which AMF to contact when the network needs to reach an idle UE. The hierarchical nature of the GUAMI (Region ID, Set ID, Pointer) allows operators to organize AMFs into logical groups (Sets) within geographical regions, facilitating flexible deployment, disaster recovery, and efficient routing. The GUAMI is a fundamental element that underpins the stateless and service-based architecture of 5GC, enabling dynamic discovery and selection of AMF instances.

Purpose & Motivation

GUAMI was created to address the scalability, flexibility, and routing challenges inherent in the 5G Core's service-based architecture, which decouples software instances from hardware and allows for dynamic scaling of network functions. In previous generations like 4G EPS, the MME was identified by an MME Code and Group ID within a PLMN, but this lacked a globally unique scope and the granularity needed for cloud-native, distributed deployments. The motivation for GUAMI stemmed from the need to uniquely identify potentially thousands of AMF instances deployed across multiple data centers and geographical regions, supporting network slicing, edge computing, and high-availability requirements.

Historically, identifiers in mobile networks evolved from simple codes to more structured forms to support increasing network complexity. The introduction of 5G and its requirement for network slicing—where a single physical network hosts multiple logical networks—necessitated an identifier that could not only uniquely point to an AMF instance but also convey logical grouping information for efficient slice-aware routing. GUAMI solves this by incorporating PLMN ID, Region ID, Set ID, and Pointer, allowing operators to organize AMFs in a way that reflects their deployment topology and slice associations.

The technology solves critical problems in 5G operation: it enables the RAN to perform efficient AMF selection without requiring a central directory for every UE request, reducing signaling latency. It supports stateless operation, where an AMF instance can fail and another can take over, as the GUAMI provides a consistent handle for locating UE context. Furthermore, it facilitates inter-PLMN mobility and roaming by ensuring AMFs are globally addressable. By providing a structured, globally unique identifier, GUAMI is foundational to achieving the 5G vision of a flexible, scalable, and resilient core network that can support diverse services from massive IoT to ultra-reliable low-latency communications.

Classification

Part ofAMF
Specific typesFN-CRG
Related approaches5G-GUTI

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 4 changes

In Release 15, the GUAMI (Globally Unique AMF Identifier) was newly defined as a structured identifier, constructed from the MCC, MNC, and an AMF Identifier comprised of Region ID, Set ID, and Pointer. This introduction enabled its inclusion in RRC messages for key procedures and established its role in the 5G-GUTI construction, which also necessitated mechanisms for updating the GUAMI in case of an AMF change.

  • Including GUAMI in RRC message of related procedures TS 23.501CR0414
  • GUAMI Definition Correction TS 23.501CR0516
  • GUAMI update in case of AMF change TS 38.413CR0101
  • GUAMI TS 23.003CR0505
Rel-16 7 changes

In Release 16, the GUAMI function was enhanced to support EPS/5GS interworking and standalone non-public network allocation. New procedures were defined for its inclusion in N1/N2 Message Notification and the Update operation, and for signaling the Old GUAMI to a target AMF during AMF planned removal. These changes clarified the association between the GUAMI and its AMF instance.

  • The GUAMI and GUMMEI usage for EPS/5GS interworking TS 38.413CR0143
  • GUAMI allocation for standalone non-public network TS 23.501CR1608
  • GUAMI in N1/N2 Message Notification TS 29.518CR0345
  • Association between the GUAMI and AMF instance TS 23.501CR1176
  • GUAMI included in the Update operation TS 29.507CR0074
  • Signalling Old GUAMI to target AMF during the AMF planned removal procedure TS 29.518CR0200

+ 1 more changes

Rel-17 2 changes

In Release 17, the GUAMI function was enhanced in two specific areas. First, clarifications were provided regarding the use of the GUAMI list within the BackupAmfInfo data structure. Second, a new capability was introduced to return the GUAMI of the Serving AMF to the GMLC (Gateway Mobile Location Centre).

  • Clarification on GUAMI List in BackupAmfInfo TS 29.571CR0371
  • Return GUAMI of Serving AMF to GMLC TS 29.503CR0948
Rel-19 1 change

In Release 19, a change was specified regarding the use of the GUAMI in the procedure for UDM Initiated Notification to AMF. This modification addressed the handling of the "Old GUAMI" parameter within that specific notification mechanism.

  • Old GUAMI in UDM Initiated Notification to AMF TS 29.503CR1293

Explore further

Broader topics and technologies where GUAMI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vj50 Numbering, addressing and identification in 3GPP Rel-19
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16
TS 29.503 vj50 UDM Service Based Interface Stage 3 Rel-19
TS 29.507 vj40 5G Access & Mobility Policy Control Service Rel-19
TS 29.508 vj40 5G Session Management Event Exposure Service Rel-19
TS 29.512 vj40 5G Session Management Policy Control Service Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.525 vj40 5G UE Policy Control Service Stage 3 Rel-19
TS 29.571 vj50 Common Data Types for 5G Service Based Interfaces Rel-19
TS 32.255 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.256 vj40 5G Connection & Mobility Charging Spec Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.413 vj10 NG Application Protocol (NGAP) Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.