Sequence Number

Description

The Sequence Number (SQN) is a fundamental security element in 3GPP systems, defined across multiple specifications such as 33.102 and 33.401, as part of the Authentication and Key Agreement (AKA) protocol. SQN is a counter or nonce value generated by the network's authentication center (AuC) or home subscriber server (HSS) to ensure the freshness of authentication vectors and prevent replay attacks. During the authentication process, SQN is included in the authentication token (AUTN) sent to the User Equipment (UE), which then verifies it against locally stored values to confirm that the authentication request is current and not a duplicate. This mechanism is essential for mutual authentication, where both the network and UE validate each other's legitimacy, and for deriving session keys (e.g., CK, IK) that secure subsequent communications.

Architecturally, SQN operates within the security layer of the core network and UE, interfacing with components like the AuC, HSS, and the UE's universal subscriber identity module (USIM). The SQN is typically a 48-bit value, structured to include sequence information and optionally an index for management. It works by being incremented or updated by the network for each authentication instance, ensuring uniqueness. When the UE receives an AUTN, it extracts the SQN, checks its freshness based on a window of acceptable values, and if valid, proceeds with key derivation. If the SQN is out of sync (e.g., due to network issues or attacks), the UE may trigger resynchronization procedures, as defined in specifications like 33.102, to restore security alignment without compromising service.

In operation, SQN is integral to the AKA process: the network generates an authentication vector containing RAND (random challenge), AUTN (which includes SQN masked with anonymity key AK), XRES (expected response), and session keys. The UE decrypts AUTN to retrieve SQN, verifies it using USIM-stored parameters, and computes a response (RES) for network validation. This ensures that each authentication session is unique and resistant to replay, protecting against eavesdropping and man-in-the-middle attacks. SQN's role extends from 2G (where it was simpler) to 5G, evolving to support enhanced privacy and security features, such as in 5G AKA where SQN handling is refined to address privacy concerns like subscriber traceability.

Purpose & Motivation

SQN was introduced to address security vulnerabilities in early mobile networks, particularly the lack of replay protection in authentication protocols. Prior to SQN, systems like GSM used simple challenge-response mechanisms without sequence tracking, making them susceptible to replay attacks where intercepted authentication messages could be reused to impersonate users. SQN solves this by adding freshness through a sequentially increasing number, ensuring that each authentication attempt is unique and time-sensitive. This enhancement was motivated by the need for stronger mutual authentication as networks evolved from 2G to 3G and beyond, supporting services like mobile banking and IoT that demand higher security.

Historically, SQN was standardized in 3GPP Rel-2 as part of the UMTS AKA protocol, building on lessons from GSM weaknesses. Its creation was driven by the requirement for robust key agreement and privacy in 3G networks, as outlined in specifications like 33.102. Over releases, SQN has been adapted to address new threats, such as in 4G EPS AKA (33.401) where it supports LTE security, and in 5G AKA (33.501) where its structure is optimized to prevent privacy leaks. By ensuring authentication freshness, SQN enables secure mobility, roaming, and service access across generations of mobile technology.

Key Features

• Ensures freshness in authentication vectors to prevent replay attacks
• 48-bit value generated by AuC/HSS and verified by UE USIM
• Integral part of AUTN in AKA protocols for mutual authentication
• Supports resynchronization procedures to handle out-of-sync scenarios
• Evolved across 2G to 5G with enhanced privacy and security refinements
• Critical for deriving session keys (CK, IK) and securing communications

Evolution Across Releases

Defining Specifications