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 Detected Changes 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

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-4, normative work from Rel-15.

Rel-15 10 changes

In Release 15, the AM function was enhanced with specific clarifications and corrections for mobility scenarios, including inter-RAT mobility and idle mode mobility between 5GS and EPS. The release introduced corrections for PDCP re-establishment on AM DRBs and clarifications on the handling of mapped GUMMEI/GUAMI identifiers. Furthermore, it provided updates for UE capabilities concerning mobility between E-UTRA and 5GC.

  • AM policy data resource definition TS 29.519CR0010
  • Corrections on AM Policy and UE Policy data TS 29.519CR0056
  • Correction on SN size for RLC AM TS 36.322CR0141
  • CR for T312 on LTE HetNet mobility TS 36.331CR3506
  • TS36.331 CR on UE capabilities for mobility and E-UTRA/5GC TS 36.331CR3589
  • [E201] CR to 36.331 on handling of mapped GUMMEI/GUAMI at idle mode mobility between 5GS and EPS TS 36.331CR3592

+ 4 more changes

Rel-16 30 changes

In Release 16, the AM function introduced significant mobility enhancements for both LTE (E-UTRAN) and NR, including the specific feature of "Even further mobility enhancement in E-UTRAN." The release also defined new capabilities for mobility to NR operating with shared spectrum access and introduced procedures like Conditional Handover (CHO), as indicated by corrections to its event descriptions. These updates focused on improving handover robustness and performance across the radio access network.

  • Support of BDT reference Id within Session Management data TS 29.519CR0149
  • Introduction of even further mobility enhancement in E-UTRAN TS 36.300CR1270
  • Baseline CR for introducing Rel-16 LTE further mobility enhancements TS 36.300CR1296
  • Introduction of Even further Mobility enhancement in E-UTRAN TS 36.331CR4205
  • Introduction of NR Mobility enhancements TS 36.331CR4234
  • Mobility to NR operating with shared spectrum access TS 36.331CR4263

+ 24 more changes

Rel-17 10 changes

In Release 17, key enhancements for the Access and Mobility Management (AM) function included the introduction of mobility-state-based cell reselection for NR HSDN to improve connection management. Furthermore, the release introduced and refined procedures for handling "AM Influence Data," including new query capabilities for any UE and updates to the associated data models and resource handling.

  • AM Influence UDR models for DCAMP TS 29.519CR0260
  • AM Influence data model updates TS 29.519CR0282
  • Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] TS 36.331CR4730
  • Introduction of mobility-state-based cell reselection for NR HSDN [NR_HSDN] TS 38.331CR2846
  • AM Influence Data: alignment with naming convention TS 29.519CR0278
  • Updates of AM Influence Data resource TS 29.519CR0312

+ 4 more changes

Rel-18 15 changes

In Release 18, the AM function was enhanced to support operator-specific AM policy data, including subscriber spending limits information, and to provide AM Influence Data containing a list of PLMN IDs for inbound roaming UEs. These updates improve policy control and roaming management for the Access and Mobility Management function.

  • Adding list of PLMN ID(s) for inbound roaming UEs in AM Influence Data. TS 29.519CR0410
  • Support for AM policy data in the operator specific data resource TS 29.519CR0425
  • Support of subscriber spending limits information modify in AM policy data TS 29.519CR0505
  • Introduction of Enhancement on NR QoE management and optimizations for diverse services TS 38.331CR4446
  • Introduction of further NR mobility enhancements TS 38.331CR4458
  • Correction to subscription to notification of changes of AF influence on AM Policies TS 29.519CR0464

+ 9 more changes

Rel-19 15 changes

In Release 19, key enhancements to the AM function included mobility enhancements for Uncrewed Aerial Vehicles (UAVs) and the introduction of idle mode mobility from LTE terrestrial networks to NR Non-Terrestrial Networks. Furthermore, the release optimized the subscription mechanism for changes to AM influence data and introduced reporting of the Mobility State for UEs in RRC_CONNECTED to support mobility management. These updates were accompanied by various corrections across the specified mobility procedures.

  • Optimization of the subscription to changes of AM influence data TS 29.519CR0532
  • Optimization of the subscription to changes of AM influence data TS 29.519CR0533
  • Introduction of LTE TN to NR NTN idle mode mobility TS 36.300CR1412
  • Introduction of LTE TN to NR NTN IDLE mode mobility TS 36.331CR5065
  • Introduction of UAV mobility enhancements [UAV_Mobility] TS 38.331CR5399
  • Introduction of RRC changes for mobility enhancements phase 4 TS 38.331CR5443

+ 9 more changes

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