Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

XRES

Expected Response

Security →

XRES is the expected authentication response value generated by the network to verify a user's SIM by comparing it against the user's computed response during 3G authentication.

Introduced
Rel-4
Where
Security
Specifications
9 specs
XRES Description Purpose What changed Neighbours Specifications

Description

The Expected Response (XRES) is a critical component within the 3GPP authentication and key agreement (AKA) framework, specifically for 3G (UMTS) networks. It is generated by the Home Location Register/Authentication Center (HLR/AuC) alongside other authentication vectors (AV), which include a random challenge (RAND), a network authentication token (AUTN), and ciphering/integrity keys (CK/IK). This vector is sent to the serving network node, such as the Visitor Location Register (VLR) or Serving GPRS Support Node (SGSN). The core function of XRES is to serve as the network's reference value for verifying the user's identity. When a user equipment (UE) attempts to attach to the network, the VLR/SGSN forwards the RAND and AUTN to the UE. The UE's Universal Subscriber Identity Module (USIM) uses the shared secret key (K) with the HLR/AuC to process these inputs. It independently computes a response value, called RES. The UE then sends this RES back to the VLR/SGSN. The network node performs a direct comparison: if the received RES matches the pre-stored XRES from the authentication vector, the user is authenticated. A mismatch indicates authentication failure, and access is denied. This process ensures that only a UE possessing the correct secret key K can generate the correct RES, thereby validating the subscriber's identity and protecting against impersonation attacks. The XRES is a temporary value, valid for a single authentication procedure, which enhances security by preventing replay attacks. Its generation and verification are central to the mutual authentication process in 3G, where the network authenticates the UE and the UE authenticates the network (via the AUTN).

Purpose & Motivation

XRES was introduced to address security weaknesses in the 2G (GSM) authentication system, which only provided one-way authentication (network to user). The primary purpose of XRES is to enable robust mutual authentication in 3G UMTS networks. It solves the problem of verifying that a user is who they claim to be, based on a cryptographically secure challenge-response mechanism. By having the network generate an expected value (XRES) derived from a secret key known only to the home network and the user's SIM, the system can definitively confirm a user's identity before granting network access. This was a significant evolution from GSM's use of the SRES (Signed Response), as part of a more comprehensive AKA procedure that also provided stronger encryption keys (CK/IK) and network authentication. The creation of XRES was motivated by the need for enhanced security in mobile communications to protect against fraud, eavesdropping, and unauthorized access, which became increasingly critical with the advent of mobile data services. It forms the verification cornerstone within the UMTS AKA protocol, a standard that has influenced all subsequent 3GPP security architectures.

What changed in its specifications

The latest release-to-release comparison of specifications that define XRES. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 24.109Rel-16 → Rel-17

Standalone security aspects update HTTP references and specify authentication algorithm values. AKMA adds TLS usage over Ua* with new definitions, and GBA updates authentication algorithm and TLS version details for 5GC bootstrapping.

Full comparison in TS 24.109 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-4 Initial

Introduced as a core component of the UMTS Authentication and Key Agreement (AKA) mechanism. Defined as part of the authentication vector generated by the HLR/AuC for 3G circuit-switched and packet-switched domains. Its comparison with the user's RES formed the basis for user authentication in the new 3G security architecture.

Defining Specifications

3GPP specifications that define or reference XRES, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 24.109 vj00 HTTP Digest AKA & GAA Stage 3 Rel-19 read
TS 29.109 vj00 GAA Bootstrapping Interfaces (Zh, Dz, Zn, Zpn) Rel-19 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TR 31.900 vj00 3GPP TS 31.900: Security Interworking Guidance Rel-19 read
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 33.105 vj00 3G Security: Cryptographic Algorithm Requirements Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TR 35.909 vj00 3GPP MILENAGE Algorithm Design Report Rel-19 read