Description
User Identity Authentication (UIA) is the core procedure defined by 3GPP to ensure that a user or device is who it claims to be before granting access to cellular network services. It is a primary function of the Authentication and Key Agreement (AKA) protocol. The architecture involves several key network functions: the User Equipment (UE) containing a SIM or USIM, the serving network (e.g., VLR/SGSN/MME/AMF), and the home network's Authentication Centre (AuC) and Home Subscriber Server (HSS). The process begins when the serving network requests authentication vectors from the HSS/AuC. The AuC generates these vectors using a secret key (K) unique to the subscriber's identity (IMSI) 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 serving network sends the RAND and AUTN to the UE. The USIM in the UE, possessing the same secret key (K), processes the AUTN to verify it originated from a legitimate network (authentication of the network to the user) and checks the SQN for freshness to prevent replay attacks. It then computes a response (RES) using the RAND and K. The UE sends RES back to the serving network, which compares it to the XRES. A match authenticates the user. Successful UIA also results in the derivation of the same CK and IK in both the UE and network, enabling subsequent ciphering and integrity protection of communications. This mutual authentication (network authenticates user, user authenticates network) is a critical security feature.
Purpose & Motivation
UIA exists to establish secure, trusted access to mobile network resources, solving the fundamental security problem of impersonation and unauthorized use. Before standardized authentication, early mobile systems had weak or no authentication, making them vulnerable to cloning and fraud. The motivation for developing robust UIA in GSM (and its evolution through 3G, 4G, and 5G) was to protect network operators from revenue loss due to fraud and to protect user privacy and service integrity. It addresses the limitations of simple password-based systems by using a shared secret stored in a tamper-resistant module (SIM) and cryptographic challenge-response mechanisms that never transmit the secret key over the air. The creation of the AKA protocol, with UIA at its heart, was driven by the need for a scalable, efficient authentication method suitable for millions of devices, capable of supporting roaming between different operator networks, and providing a foundation for generating session keys for confidentiality and integrity. Its continuous evolution across releases addresses emerging threats, enhances key lengths and algorithms, and adapts to new network architectures (e.g., EPS AKA in LTE, 5G AKA in 5G SA) while maintaining backward compatibility and global interoperability.
Key Features
- Mutual authentication between user and network
- Based on a shared secret key (K) stored in USIM and AuC
- Uses challenge-response mechanism (RAND, RES/XRES)
- Generates cipher key (CK) and integrity key (IK) for session security
- Includes sequence number (SQN) to prevent replay attacks
- Foundation for the 3GPP Authentication and Key Agreement (AKA) protocol
Evolution Across Releases
Introduced the UMTS Authentication and Key Agreement (AKA) protocol as a significant enhancement over GSM authentication. UIA in Rel-4 provided mutual authentication, stronger cryptographic algorithms (MILENAGE), and the generation of separate ciphering and integrity keys (CK/IK), greatly improving security for 3G UMTS networks.
Maintained core UIA procedures while introducing the IP Multimedia Subsystem (IMS). Defined IMS-specific authentication (IMS AKA), which reuses the same UIA mechanism and credentials from the USIM but applies it for access to IMS services, enabling single sign-on for circuit-switched and packet-switched multimedia services.
Enhanced authentication for Generic Bootstrapping Architecture (GBA), which leverages UIA to bootstrap authentication for applications over HTTP. This allowed web services and IMS applications to reuse the strong cellular network authentication, simplifying security for value-added services.
Introduced EPS AKA for the Evolved Packet System (LTE/EPC) in later releases, but Rel-7 laid groundwork with continued enhancements to security architecture. Support for stronger encryption algorithms was ongoing.
Formally specified EPS AKA for LTE, which evolved UIA for the all-IP EPC architecture. EPS AKA maintained the core UIA principles but used keys derived from CK/IK (K_ASME) for access security in E-UTRAN, introducing key hierarchy specific to LTE.
Continuous strengthening of UIA. This included the introduction of 5G AKA in Rel-15 for 5G Standalone (SA) networks. 5G AKA enhanced privacy by concealing the subscriber's permanent identity (SUPI) using SUCI, and introduced enhanced home network control with authentication vector confirmation from the SEAF. The core UIA challenge-response mechanism remained intact but was embedded in a new key hierarchy and signaling flow for 5G.
Further evolution of authentication for 5G-Advanced, including support for integrated access and backhaul (IAB), non-3GPP access (e.g., wireline), and enhanced authentication for network slicing and edge computing. Work on post-quantum cryptography readiness may influence future UIA mechanisms, ensuring long-term security.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.111 | 3GPP TS 21.111 |
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 33.102 | 3GPP TR 33.102 |
| TS 33.401 | 3GPP TR 33.401 |
| TS 33.501 | 3GPP TR 33.501 |
| TS 33.700 | 3GPP TR 33.700 |
| TS 33.859 | 3GPP TR 33.859 |