AM

Access and Mobility Management

Core Network →
Introduced in Rel-4 Also in: Services, Core Network

AM is a core network function responsible for managing user equipment access, authenticating users, authorizing network access, and handling mobility procedures like location tracking and handovers.

Category
Core Network
Introduced
Rel-4
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
19 specs
AM Description Purpose Related Classification Specifications

Description

Access and Mobility Management (AM) is a fundamental functional entity within the 3GPP network architecture, specifically part of the Access and Mobility Management Function (AMF) in 5G systems. It serves as the primary termination point for Non-Access Stratum (NAS) signaling from the User Equipment (UE), handling all procedures related to initial registration, connection management, and mobility. The AM function is responsible for establishing and maintaining the UE's registration state with the network, which is the foundation for all subsequent communication services.

Architecturally, AM operates within the control plane of the core network, interacting with other network functions through service-based interfaces. In 5G, the AMF (which hosts the AM functionality) communicates with the Session Management Function (SMF) for PDU session establishment, the Authentication Server Function (AUSF) for security procedures, and the Unified Data Management (UDM) for subscriber data. It also connects to the Radio Access Network (RAN) via the N2 interface, receiving initial access requests and managing handover signaling. The AM function maintains the UE context, which includes the UE's registration status, security context, location information, and subscription data.

How AM works involves several key procedures. During initial access, the UE sends a Registration Request to the AMF via the RAN. The AM function authenticates the UE using credentials stored in the UDM and establishes a security context. It then authorizes the UE's access based on subscription profiles and network policies. For mobility management, AM tracks the UE's location at the granularity of a Registration Area (a group of tracking areas) and manages procedures like Registration Area Updates and handovers between different AMF serving areas. The AM function also handles connection management, transitioning the UE between CM-IDLE and CM-CONNECTED states, which controls whether the UE has a signaling connection with the AMF.

The role of AM in the network is critical for several reasons. First, it ensures that only authorized devices can access network resources, providing the first line of security. Second, it enables seamless mobility by managing location tracking and handovers without interrupting active sessions. Third, it optimizes network resource usage by controlling when UEs establish signaling connections. Finally, AM provides the foundation for other network services by maintaining the UE's registration state and context, which is essential for session management, policy enforcement, and charging.

Purpose & Motivation

The Access and Mobility Management function exists to provide a centralized, efficient mechanism for controlling how user devices connect to and move through mobile networks. Before the formalization of AM in 3GPP standards, access control and mobility management were often handled through proprietary or less integrated solutions that led to interoperability issues, inefficient handovers, and security vulnerabilities. The creation of AM addressed the need for a standardized approach that could scale with growing subscriber numbers and support increasingly complex mobility scenarios.

Historically, as mobile networks evolved from 2G to 3G and beyond, the challenges of managing user mobility became more pronounced. Early systems had limited handover capabilities and basic authentication mechanisms. The introduction of AM in 3GPP Release 4 provided a comprehensive framework that separated access and mobility management from session management, allowing for more flexible network architectures. This separation became particularly important with the transition to all-IP networks and the need to support multiple access technologies (like 2G, 3G, LTE, and non-3GPP access).

The AM function solves several key problems: it provides a single point of control for UE registration and authentication across different access types; it enables efficient tracking of UE location without excessive signaling overhead; it supports seamless mobility between cells and between different radio access technologies; and it provides the security foundation for all subsequent network interactions. By addressing these problems, AM enables the reliable, secure, and efficient operation of modern mobile networks that support billions of connected devices with diverse mobility patterns.

Classification

Part ofNAS
Specific typesAMF

Evolution Across Releases

Rel-4 Initial

Introduced the Access and Mobility Management function as part of the UMTS core network architecture. Established initial procedures for UE registration, authentication, and basic mobility management between RNS (Radio Network Subsystems). Defined the separation of mobility management from call control in the circuit-switched domain and from session management in the packet-switched domain.

Explore further

Broader topics and technologies where AM plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 22.815 ve00 Study on Multimedia Broadcast Supplement for PWS Rel-14
TS 25.322 vj00 RLC Protocol Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TR 26.937 vj00 3GPP PSS Characterization Rel-19
TS 29.519 vj40 UDR Usage for Policy & Exposure Data Rel-19
TS 29.521 vj40 5G Binding Support Management Service Stage 3 Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 32.859 vc10 Alarm Management Quality Improvement Study Rel-12
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 38.322 vj00 NR Radio Link Control (RLC) Protocol Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol 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.