Description
The Authentication and Key Agreement (AKA) protocol is a challenge-response mechanism that provides mutual authentication and cryptographic key derivation in 3GPP networks. It operates between the User Equipment (UE) and the network's Authentication Centre (AuC), which resides within the Home Subscriber Server (HSS) in 4G/5G or the Home Location Register (HLR) in 3G. The core of AKA is a shared secret key (K), which is securely stored in both the UE's Universal Subscriber Identity Module (USIM) and the AuC. This long-term key is never transmitted over the air.
The protocol execution begins when the serving network requests authentication vectors from the HSS/AuC. The AuC generates one or more authentication vectors using the subscriber's key K and a sequence number (SQN). Each vector contains a random challenge (RAND), an expected response (XRES), a cipher key (CK), an integrity key (IK), and an authentication token (AUTN). The AUTN itself contains the SQN and a Message Authentication Code (MAC), which allows the UE to verify the network's authenticity. The serving network (e.g., via the MME in 4G or AMF in 5G) sends the RAND and AUTN to the UE.
Upon receipt, the USIM in the UE uses its stored key K and the received RAND to compute its own version of the expected response (RES), cipher key (CK), integrity key (IK), and the MAC. It first verifies the AUTN by checking the MAC to ensure the challenge originated from a genuine network and by checking the SQN to ensure it is fresh and not a replay of an old authentication. If successful, the UE sends the RES back to the network. The network compares the received RES with the XRES; a match completes mutual authentication. The derived CK and IK are then used by the UE and the network's access stratum to enable confidentiality and integrity protection for all subsequent signaling and user data traffic.
AKA's design is robust, providing key separation—different keys are derived for different purposes (ciphering, integrity) and different network domains (access stratum, non-access stratum). It also supports synchronization mechanisms to handle cases where the sequence numbers in the UE and AuC become mismatched. In 5G, AKA was enhanced to 5G AKA, which includes improved home network control, the derivation of a anchor key (KAUSF) for better key hierarchy, and the inclusion of the serving network name in key derivation to bind keys to a specific network, mitigating certain attack vectors. The protocol's execution is transparent to the user but is triggered during initial network attachment, handovers between different core network types, or periodically for re-authentication.
Purpose & Motivation
AKA was created to address critical security shortcomings in predecessor cellular systems, most notably the weak and one-way authentication in GSM. In GSM, only the network authenticated the user, leaving it vulnerable to fake base station (IMSI catcher) attacks. Furthermore, GSM's encryption algorithms and key lengths were eventually found to be cryptographically weak. The primary purpose of AKA, introduced with 3G (UMTS), was to establish strong, mutual authentication and to generate robust, session-specific cryptographic keys to ensure both confidentiality and integrity of communications.
The protocol solves the problem of securely bootstrapping a trusted session in a hostile radio environment. It ensures that a user is connecting to a legitimate, authorized network and not a malicious impersonator, while simultaneously proving to the network that the user is a valid subscriber. This mutual trust is foundational for all other security services. By deriving fresh, ephemeral cipher and integrity keys (CK/IK) from a long-term secret for every authentication instance, AKA limits the impact of a potential key compromise and provides forward secrecy for user data within a session.
Historically, the development of AKA was motivated by the need for a standardized, future-proof security foundation that could evolve with network generations. Its design incorporated lessons from GSM and fixed-line authentication protocols. The use of a sequence number (SQN) mechanism, while introducing complexity for synchronization, was a deliberate choice to provide replay protection and enable the home network to maintain state. AKA's purpose has expanded from 3G to form the bedrock of the 3GPP security architecture, being adapted and enhanced in each subsequent generation (EPS-AKA for 4G, 5G AKA for 5G) to address new threats like linkability of subscribers and to support new architectural paradigms like network slicing and separation of the control and user planes.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Explore further
Broader topics and technologies where AKA plays a role.
Defining Specifications
3GPP specifications that define or reference AKA, 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 |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 |
| TS 23.804 v1710 | SMS/MMS over IP Access Networks | Rel-7 |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 |
| TS 24.234 vc20 | 3GPP-WLAN Interworking Network Selection | Rel-12 |
| TS 24.301 vk00 | 3GPP TS 24301 vk00: NAS Protocols for EPS | Rel-20 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 24.501 vk00 | 5G System (5GS) Non-Access Stratum (NAS) Protocol | Rel-20 |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 |
| TS 29.109 vj00 | GAA Bootstrapping Interfaces (Zh, Dz, Zn, Zpn) | Rel-19 |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 |
| TS 31.103 vj00 | ISIM Application Specification | Rel-19 |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 |
| TS 32.181 vj00 | User Data Convergence Management Framework | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 |
| TS 33.127 vj70 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.141 vj00 | Security for Presence Service (Ut reference point) | Rel-19 |
| TS 33.203 vk00 | IMS Security Features and Mechanisms | Rel-20 |
| TS 33.220 vj10 | Generic Authentication Architecture (GAA) Security | Rel-19 |
| TS 33.221 vj00 | Subscriber Certificate Distribution via GBA | Rel-19 |
| TS 33.234 vj00 | 3GPP-WLAN Interworking Security | Rel-19 |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 |
| TS 33.402 vj00 | Security for non-3GPP access to EPS | Rel-19 |
| TS 33.501 vk20 | 5G Security Architecture and Procedures | Rel-20 |
| TS 33.514 vk10 | 3GPP TS 33514 vk10: UDM Network Product Security Requirements | Rel-20 |
| TS 33.545 vk00 | Security Architecture for NR Femto Subsystem | Rel-20 |
| TS 33.804 vc00 | Non-UICC SSO using SIP Digest credentials | Rel-12 |
| TS 33.820 v1830 | Home NodeB/eNodeB Security Architecture | Rel-8 |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 |
| TR 33.841 vg10 | Security aspects; Study on 256-bit algorithms for 5G | Rel-16 |
| TS 33.843 vf10 | Security Study for ProSe UE-to-Network Relay | Rel-15 |
| TS 33.859 vb10 | UTRAN Key Hierarchy Enhancement Study | Rel-11 |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 |
| TR 33.919 vj00 | GAA Overview TR | Rel-19 |
| TR 33.924 vj00 | GBA-OpenID Interworking Specification | Rel-19 |
| TS 34.229 vj30 | IP Multimedia Call Control Protocol | Rel-19 |
| TS 35.235 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 |
| TS 35.236 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 |
| TS 35.249 vj10 | f5** Algorithm for MILENAGE and Tuak | Rel-19 |
| TR 35.937 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 |
| TS 38.300 vj30 | NR and NG-RAN Overall Description | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |