AMF (5G)

AMF (5G)
Name	AMF (5G)
Type	Network function
Developer	3GPP
Standard	3GPP TS 23.501
Introduced	5G System (5GS)
Role	Access and mobility management

AMF (5G) is the Access and Mobility Management Function defined for the 5G System by 3GPP. It coordinates registration, connection, reachability, mobility, and user plane anchor selection across entities such as gNB, UPF, SMF, and NSSF while interacting with components specified by ETSI, ITU, and regional operators.

Overview

The AMF implements control-plane responsibilities in the 5G Core specified in 3GPP releases and described in 3GPP TS 23.501, interoperating with entities from ETSI and recommendations from the International Telecommunication Union; it replaces or extends functions that in earlier generations were handled by nodes like the MME from 3GPP Release 8 and aligns with cloud-native initiatives from vendors such as Nokia, Ericsson, Huawei, and Samsung Electronics. Its remit spans authentication coordination with AUSF and UDM, policy interaction with PCF, session anchoring via SMF, and exposure for third-party services through interfaces framed by organizations like GSMA and IETF. The AMF's placement within operator architectures used by carriers such as Verizon Communications, AT&T, Deutsche Telekom, China Mobile, and Vodafone affects roaming interactions with entities governed by GSMA roaming guidelines and home/visited network agreements like those codified by 3GPP.

Architecture and Functions

AMF is a control-plane network function in the Service-Based Architecture specified by 3GPP; it exposes service-based interfaces to peer functions such as SMF, PCF, and UDM and supports legacy interworking with nodes referenced in 3GPP TS 23.501, enabling features demanded by operators like T-Mobile US and infrastructure vendors like Cisco Systems. Core responsibilities include registration management (authentication handshake with AUSF and subscription retrieval from UDM), connection management (NAS procedures handed to radio access elements like gNB), mobility management (handover preparation with gNB and session continuity via UPF), and reachability/UE context management for roaming scenarios involving entities such as GSMA-defined HPLMN and VPLMN. AMF also implements subscriber identifier handling including 5G-GUTI allocation and interaction with lawful interception frameworks used by agencies such as INTERPOL under national laws administered by ministries of communications.

Interfaces and Protocols

AMF exposes service-based interfaces (SBI) defined by 3GPP using RESTful principles and HTTP/2 over TLS, interoperating with IETF TLS and IETF HTTP/2 stacks commonly implemented by vendors like Red Hat and Google. Key reference points include N1 to the UE via NAS signaling over gNB, N2 to the RAN for signaling with gNB and ng-eNodeB, N11 to SMF for session management, and N8 to UDM for subscription data retrieval; these align with format and procedures specified in 3GPP TS 29.500 series and are often exposed through cloud platforms like OpenStack or Kubernetes for virtualization. Interworking for roaming leverages interfaces standardized by GSMA and 3GPP, and transport relies on network technologies from Juniper Networks or Arista Networks for backbone connectivity.

Procedures and Signalling

AMF manages NAS signaling procedures defined in 3GPP TS 24.501 including registration, deregistration, periodic registration update, PDU session establishment choreography with SMF, and mobility procedures for both intra- and inter-architecture handovers involving handover protocols specified by 3GPP. Authentication flows are coordinated via the AUSF using 5G AKA or EAP-based methods referencing credentials stored in UDM and subscriber databases common to operators such as NTT Docomo and Orange S.A.. AMF also handles UE reachability, paging triggers, and policy-driven interactions with PCF for authorized behavior, while generating events consumed by charging and monitoring systems like those from Amdocs and Oracle Corporation.

Deployment and Scalability

AMF is designed for flexible deployment models endorsed by 3GPP and adopted by cloud-native initiatives from Linux Foundation projects; operators deploy AMF as monolithic VM appliances or as microservices within Kubernetes clusters managed via orchestration tools from VMware or Red Hat OpenShift. Scalability strategies include stateless front-ends, distributed state stores implemented with technologies by Couchbase, Redis, or Apache Cassandra, and geo-distributed deployments to meet latency constraints in regional networks operated by BT Group or Telstra. High-availability topologies follow patterns from ETSI NFV and TM Forum operational frameworks with multi-site redundancy, AMF relocation support for roaming, and elastic scaling to accommodate load surges during events managed jointly by operators and vendors.

Security and Privacy

AMF participates in 5G security architecture defined by 3GPP, coordinating authentication via AUSF, subscriber credential protection with UDM, and integrity/confidentiality of NAS messages using 5G cryptographic algorithms standardized by 3GPP and evaluated by national bodies like NIST and ENISA. Privacy measures include management of subscription concealed identifiers and policies to limit exposure of IMSI-equivalent identifiers, aligning with regulatory frameworks such as those administered by European Commission and privacy guidance from organizations like GSMA. Security deployment practices involve mutual TLS for SBI, certificate management via PKI systems often provided by DigiCert or enterprise solutions from Entrust, and monitoring integrated with SIEM platforms from Splunk or IBM Security to detect anomalies and support incident response coordinated with national CERT teams like US-CERT.

Category:5G Core network functions