Description
The AMF Region is a fundamental architectural concept in the 5G Core Network (5GC), defined in 3GPP TS 23.501 and referenced in management specifications TS 28.540 and TS 28.802. The Access and Mobility Management Function (AMF) is the control-plane entry point for UEs, handling registration, connection management, mobility, and NAS signaling. Because a single AMF cannot serve an entire operator network at scale, the 5GC organizes AMFs into hierarchical groupings: AMF Sets and AMF Regions.
An AMF Set is a group of AMFs that serve a common set of Tracking Areas (TAs) and share a common AMF Set ID. Within an AMF Set, AMFs are functionally equivalent and can serve any UE in the set's coverage. This enables load balancing and redundancy: if one AMF fails, another in the same set can take over. An AMF Region, as defined, consists of one or multiple AMF Sets. It represents a larger administrative and operational domain — typically corresponding to a geographic area, a regional deployment, or an operator's network partition.
The AMF Region concept supports several key functions. First, it defines the scope for AMF selection: when a UE registers, the RAN (gNB) selects an AMF based on the UE's 5G-GUTI (which encodes the AMF Set ID and AMF pointer) or, for initial registration, based on the requested NSSAI and local configuration. The AMF Region provides the boundary within which this selection is valid. Second, it enables mobility: when a UE moves between AMF Sets within the same region, the source AMF can redirect the UE to a target AMF in the new set, or the UE may re-register. Third, it supports failover and disaster recovery: if an entire AMF Set becomes unavailable, the region's other sets can potentially absorb the load, subject to capacity and configuration.
Management aspects are covered in TS 28.540 (5G NRF/AMF management) and TS 28.802 (5G management concepts). These specify how AMF Regions are provisioned, monitored, and reconfigured. The AMF Region is also relevant to network slicing: different slices may have different AMF deployments, and the region concept helps define which AMFs serve which slices. In roaming scenarios, the AMF Region of the visited network interacts with the home network's slice and policy configurations.
The AMF Region is not directly visible to the UE; the UE interacts with an AMF via NAS, and the network handles region-level routing internally. However, the region structure influences the 5G-GUTI format, the behavior of the NRF (Network Repository Function) in discovering AMF instances, and the procedures for AMF relocation during mobility. In summary, the AMF Region is a scalability and resilience construct that organizes AMFs into manageable, fault-tolerant domains within the 5G Core.
Purpose & Motivation
The AMF is a critical control-plane function in 5GC, and a single AMF cannot handle the signaling load of a large network or provide sufficient redundancy. The AMF Region concept was created to structure AMF deployments into hierarchical, fault-tolerant domains. By grouping AMF Sets into regions, operators can scale horizontally, isolate failures, and manage mobility across large geographic areas without a flat, unmanageable AMF topology.
Before this hierarchical approach, early designs might have relied on simpler pools, but 5G's requirements for ultra-reliable, low-latency, and massive-scale services demanded a more structured approach. The AMF Region provides a clear boundary for AMF selection, load balancing, and failover. It also simplifies management: operators can provision and monitor regions rather than individual AMFs, and can apply policies at the region level.
The concept also supports network slicing and multi-tenancy. Different slices or tenants may have dedicated AMF Sets within a region, and the region structure allows the network to route UEs to the appropriate AMF based on slice and subscription. This flexibility is essential for 5G's diverse service landscape. Overall, the AMF Region exists to make 5G access and mobility management scalable, resilient, and operationally manageable.
What changed in its specifications
The latest release-to-release comparison of specifications that define AMF Region. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds management clauses for Ambient IoT, IAB nodes, and regenerative NTN with UE-Satellite-UE communication. It also shifts NTN responsibility from 5GC to 3GPP.
Full comparison in TS 28.540 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference AMF Region, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |