Description
The Access and Mobility Management Function (AMF) is a fundamental control plane network function (NF) within the 5G Core (5GC) architecture, defined by 3GPP from Release 15 onwards. It serves as the primary termination point for Non-Access Stratum (NAS) signaling, which is the protocol layer between the User Equipment (UE) and the core network, independent of the underlying radio access technology (e.g., NG-RAN, non-3GPP access). The AMF is responsible for a suite of procedures related to UE access and mobility, including initial registration, connection management (establishing and releasing the signaling connection), reachability management (including idle mode mobility and paging), and mobility management (tracking area updates, handovers). It authenticates the UE and authorizes its access to the network, acting as a security anchor by interacting with the Authentication Server Function (AUSF) and the Security Anchor Function (SEAF). A key architectural principle in 5G is the separation of the control plane functions for access/mobility (AMF) and session management (SMF). This decoupling allows the AMF to be selected based on UE location and mobility requirements, while a different SMF can be selected based on the data session's service requirements, enabling greater flexibility, scalability, and support for network slicing.
From a procedural standpoint, when a UE initiates registration with the 5G network, the Radio Access Network (RAN) routes the initial NAS message to an AMF instance. The AMF then orchestrates the UE authentication process. Upon successful authentication and registration, the AMF maintains the UE's context, which includes its identity (SUPI/SUCI), registration status, assigned temporary identifier (5G-GUTI), security context, and the serving SMF(s) for its active Protocol Data Unit (PDU) Sessions. For mobility, the AMF manages the UE's mobility within the 5G system, handling procedures like handovers (with the assistance of other functions) and tracking area updates. It also plays a central role in network slicing by being part of the slice selection process, ensuring the UE is served by the appropriate network slice instance based on its subscription and requested service.
The AMF interfaces with numerous other 5GC NFs. Its key interfaces include N1 (to the UE via the RAN), N2 (to the NG-RAN for control plane signaling), and N11 (to the SMF). It also communicates with the AUSF (N12), Unified Data Management (UDM) (N8), Network Slice Selection Function (NSSF) (N22), and Network Exposure Function (NEF) (N29), among others. This web of interfaces allows the AMF to act as a central hub, coordinating between the UE, the RAN, and other core network functions to manage the UE's access lifecycle. Its stateless design principle, where the UE context can be stored externally in a Unified Data Repository (UDR), enhances reliability and allows for efficient load balancing and redundancy across multiple AMF instances.
Purpose & Motivation
The AMF was created as part of the 5G Core's Service-Based Architecture (SBA) to address the limitations of previous core network architectures, specifically the 4G Evolved Packet Core (EPC). In the EPC, the Mobility Management Entity (MME) combined access, mobility, and session management signaling. This monolithic design limited flexibility, made network function scaling inefficient, and hindered the deployment of diverse services with different requirements on a shared infrastructure. The primary purpose of the AMF is to decouple access and mobility management from session management, a separation that is foundational to 5G's goals of network flexibility, service-based design, and support for network slicing.
By isolating the mobility and connection state management in the AMF, the 5GC can independently scale the AMF and the SMF based on different network loads (e.g., a massive number of idle IoT devices versus high-bandwidth data sessions). This separation directly enables efficient network slicing, as different slices can share a common AMF pool for basic connectivity while utilizing dedicated SMF instances tailored for specific slice performance characteristics (e.g., ultra-low latency, massive IoT). Furthermore, the AMF's design as a stateless function (with context stored externally) improves network resilience, simplifies disaster recovery, and enables more agile load balancing compared to the stateful MME. Its creation was motivated by the need for a core network that could support a vastly wider range of use cases—from enhanced mobile broadband to mission-critical communications and massive IoT—with the required agility, scalability, and efficiency that the previous generation's architecture could not provide.
What changed in its specifications
The latest release-to-release comparison of specifications that define AMF. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →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 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → AMF (Packet Controller)
- Mobile Network → NG-RAN → AMF (5G Core (context))
Evolution Lineage
- Evolved from: MME (4G→5G)
- Network evolution overview →
Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
- AMF counterpart in another generation: MME
“At inter-system handover, the AMF selects target MME based on 2 octet TAC format used in the Target ID as specified in TS 38.413 [34].” TS 23.501
Security functions and anchors · Security
- Phase 1 AuC
- R99 HLR/AuC
- Rel-5 HSS
- Rel-6 3GPP AAA Server, BSF
- Rel-8 ASME, MME
- Rel-9 HSS-FE
- Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
- Rel-16 AAnF
- AMF counterpart in another generation: MME
“When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, the AMF selects the target MME based on the source AMF Region ID, AMF Set ID and target location information.” TS 23.501
- AMF used together with SEAF
“The SEAF shall derive the KAMF from KSEAF and send it to the AMF which is used by the AMF to derive NAS security keys.” TS 33.501
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 sourcesDocumented changes in 6 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.
The AMF is specified for the first time in Rel-15, including registration, NAS security, mobility and UE context transfer between old and new AMF, and the Namf_Communication service.
- “The AMF shall enter CM-CONNECTED state for the UE whenever an N2 connection is established for this UE between the AN and the AMF.” TS 23.501 v15.13.0
- “When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE.” TS 23.501 v15.13.0
- “The UEContextTransfer service operation is invoked by a NF Service Consumer, e.g. a target AMF, towards the AMF (acting as source AMF)” TS 29.518 v15.13.0
In Rel-16 the AMF gained new behaviours: determining LTE-M and NR-unlicensed RAT types, rejecting incompatible Preferred Network Behaviour, RACS handling, and mapped security context handling for N26 interworking.
- “the AMF shall reject the Registration Request with an appropriate cause value (e.g. one that avoids retries on this PLMN).” TS 23.502 v16.19.0
- “the AMF shall use the PEI of the UE to obtain the IMEI/TAC for the purpose of RACS operation.” TS 23.502 v16.19.0
- “The AMF may determine the RAT Type to be LTE-M as defined in clause 5.31.20; or” TS 23.501 v16.20.0
In Rel-17 the AMF gained new behaviours, including satellite access location verification, Disaster Roaming handling, analytics subscription transfer between AMFs, and MINT support indication signalling to the UDM.
- “For NR satellite access, the AMF may verify the UE location and determine whether the PLMN is allowed to operate at the UE location” TS 23.502 v17.15.0
- “the old AMF includes information about active analytics subscriptions, i.e. the Subscription Correlation ID, NWDAF identifier” TS 23.502 v17.15.0
- “The AMF may determine the RAT Type to be one of the RAT types for satellite access” TS 23.501 v17.15.0
In Rel-18 the AMF gained new behaviours, including Partially Allowed NSSAI handling in Registration Accept, Slice Usage Policy, and an unavailability period for satellite access.
- “the AMF may include Partially Allowed NSSAI in the Registration Accept with the related TAI List for S-NSSAIs in Partially allowed NSSAI” TS 23.502 v18.14.0
- “the AMF may include Slice Usage Policies for the slices in the Configured NSSAI” TS 23.502 v18.14.0
- “If the UE indicates an Unavailability Period Duration, then AMF shall consider the UE as unreachable during the unreachability period” TS 23.501 v18.12.0
AMF behaviour was extended in Rel-19, e.g. LP-WUS disabling and paging subgroup assistance information, MINT-EPS support indication to UDM, and AMF-initiated UE configuration update for network slice replacement.
- “If LP-WUS has been disabled for a UE, the AMF shall indicate in the Paging message to the gNB that LP-WUS is disabled” TS 23.501 v19.9.0
- “The AMF provides MINT, MINT-EPS or both support indication via Nudm_UECM_Registration towards UDM” TS 23.502 v19.9.0
- AMF initiation of UCU procedure for network slice replacement TS 24.501CR7074
AMF behaviour changed in Rel-20: it supports Indirect Network Sharing for Disaster Condition, handles Network Identity provisioning and a new AIoT service operation, and retransmits NAS messages after intra-AMF handover.
- “when the AMF of the hosting operator's network identifies that the UE is accessing via Indirect Network Sharing, then the AMF provides the PLMN ID” TS 23.502 v20.3.0
- “When the Network Identity is changed, the AMF provides the updated Network Identity to the UE via UE Configuration Update procedure.” TS 23.501 v20.3.0
- New AMF AIoT service operation TS 29.518CR1366
Defining Specifications
3GPP specifications that define or reference AMF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.822 vg00 | Satellite Access in 5G Study | Rel-16 read |
| TS 23.003 vk10 | Numbering, Addressing and Identification | Rel-20 read |
| TS 23.222 vk10 | Common API Framework (CAPIF) | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.527 vk00 | 5G Restoration Procedures for N4 Interface | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TR 23.958 vj00 | EDGEAPP alignment with ETSI MEC and GSMA OP | Rel-19 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.502 vk00 | Non-3GPP Access Network Discovery and Selection | Rel-20 read |
| TS 24.571 vj50 | 5G NAS Location Services (LCS) | Rel-19 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 26.501 vk00 | 5G Media Streaming Architecture | Rel-20 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 read |
| TR 26.919 vj00 | Study on 5G Conversational Media Handling | Rel-19 read |
| TS 26.942 vk00 | Sustainable Media Metrics and Architectural Impacts for 5G | Rel-20 read |
| TS 28.204 vi11 | Charging management | Rel-18 read |
| TS 28.531 vk10 | 5G Network Slice Provisioning Management | Rel-20 read |
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TS 28.561 vk20 | Network Digital Twin Management | Rel-20 read |
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |
| TR 28.816 vh00 | Charging for 5G Cellular IoT | Rel-17 read |
| TR 28.833 vi01 | Technical Report on 5G LAN-type Service Management | Rel-18 read |
| TR 28.840 vi10 | Technical Report | Rel-18 read |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 read |
| TS 28.874 vj10 | Study on Management Aspects of NTN Phase 2 | Rel-19 read |
| TS 28.879 vj10 | OAM for Service Management Exposure Study | Rel-19 read |
| TS 29.222 vk10 | CAPIF Northbound API Protocol | Rel-20 read |
| TS 29.503 vk10 | UDM Service Based Interface | Rel-20 read |
| TS 29.505 vk00 | UDR Services for Subscription Data | Rel-20 read |
| TS 29.507 vk10 | Access and Mobility Policy Control | Rel-20 read |
| TS 29.508 vk10 | Session Management Event Exposure Service | Rel-20 read |
| TS 29.509 vk00 | 3GPP TS 29509: Nausf Service Based Interface | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.515 vk10 | Ngmlc Location Services API | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.523 vk10 | Policy Control Event Exposure Service | Rel-20 read |
| TS 29.524 vk00 | 5GC to NAS Cause Mapping Specification | Rel-20 read |
| TS 29.525 vk10 | UE Policy Control Service | Rel-20 read |
| TS 29.532 vk00 | Nmbsmf Service Based Interface Specification | Rel-20 read |
| TS 29.534 vk00 | 5G Access and Mobility Policy Authorization | Rel-20 read |
| TS 29.536 vk10 | Nnsacf Network Slice Admission Control | Rel-20 read |
| TS 29.540 vk10 | Nsmsf Service-Based Interface for SMSF | Rel-20 read |
| TS 29.542 vk00 | Nsmf NIDD Service API (TS 29.542) | Rel-20 read |
| TS 29.552 vk10 | 5G Network Data Analytics Procedures | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |
| TS 29.574 vk10 | DCCF Service Based Interface | Rel-20 read |
| TS 29.575 vk10 | ADRF Service Based Interface | Rel-20 read |
| TS 29.576 vk10 | MFAF Service Based Interface | Rel-20 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 31.102 vk00 | USIM Application Specification | Rel-20 read |
| TS 31.103 vj10 | IM Services Identity Module Specification | Rel-19 read |
| TS 32.181 vj00 | User Data Convergence Management Framework | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | Rel-20 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.273 vj00 | MBMS Charging Management | Rel-19 read |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 read |
| TS 32.279 vj00 | 5G MBS Session Converged Charging | Rel-19 read |
| TS 32.290 vk00 | 5G Charging Service-Based Architecture | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TR 32.847 vi00 | Technical Report | Rel-18 read |
| TS 32.899 vf10 | 5G Charging Architecture Study | Rel-15 read |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.511 vk10 | 5G gNB Security Assurance Specification | Rel-20 read |
| TS 33.514 vk20 | UDM Security Assurance Specification | Rel-20 read |
| TS 33.535 vj00 | 5G AKMA: Authentication and Key Management for Apps | Rel-19 read |
| TS 33.701 vj00 | Study on mitigations against bidding down attacks | Rel-19 read |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TR 33.741 vi01 | Home Network Triggered Authentication | Rel-18 read |
| TS 33.794 vj10 | Study on Zero Trust Security Enablers for 5G | Rel-19 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TS 33.836 vg10 | Security Study for Advanced V2X Services | Rel-16 read |
| TR 33.847 vh10 | 5G Proximity Services Security Study | Rel-17 read |
| TS 33.856 vg10 | Security for 5G to 3G Voice Continuity | Rel-16 read |
| TS 33.861 vg10 | CIoT Security Evolution for 5G System | Rel-16 read |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 read |
| TS 33.897 vd10 | Security for Isolated E-UTRAN Operation | Rel-13 read |
| TS 35.205 vj00 | MILENAGE Algorithm Set: General Overview | Rel-19 read |
| TR 35.909 vj00 | 3GPP MILENAGE Algorithm Design Report | Rel-19 read |
| TR 35.934 vj00 | Tuak algorithm set for 3GPP auth & key gen | Rel-19 read |
| TS 37.473 vj00 | W1 Application Protocol (W1AP) Specification | Rel-19 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.410 vj20 | NG-RAN; NG General Aspects and Principles | Rel-19 read |
| TS 38.412 vj00 | NG Signalling Transport | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.414 vj00 | NG Interface User Plane Protocol | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 read |