CKSN

Ciphering Key Sequence Number

Security →
Introduced in Rel-5

CKSN is a security parameter that identifies the active ciphering key between a UE and the network, enabling secure key synchronization during authentication and handover to prevent key mismatch breaches.

Category
Security
Introduced
Rel-5
Where
Security
Specifications
3 specs
CKSN Description Purpose Detected Changes Specifications

Description

The Ciphering Key Sequence Number (CKSN) is a fundamental security parameter in 3GPP networks that serves as an index or identifier for the currently active ciphering key (CK) used for encrypting user data and signaling between the User Equipment (UE) and the network. It operates as part of the authentication and key agreement (AKA) framework, specifically within the UMTS AKA and EPS AKA procedures. The CKSN is stored both in the UE's non-volatile memory and in the network's authentication center (AuC) or home subscriber server (HSS), ensuring both entities can reference the same cryptographic key without transmitting the key itself over the air interface.

Architecturally, CKSN is integrated into the security context management system. When a UE performs initial attach or periodic authentication, the network generates a new ciphering key (CK) along with an integrity key (IK) and assigns a CKSN value, typically ranging from 0 to 7. This CKSN is transmitted to the UE within authentication vectors (e.g., in UMTS) or as part of the NAS security context (in LTE/5G). The UE stores the CK and associates it with the received CKSN. During subsequent connections, the UE includes the CKSN in its attach or service request messages, allowing the network to retrieve the corresponding CK from its database without needing to perform full authentication each time.

The CKSN plays a critical role during mobility events such as handovers between different radio access technologies (e.g., UMTS to LTE) or between network nodes. When a UE moves to a new serving node, the target node requests the security context from the source node or HSS. The CKSN is included in this context transfer, enabling the target node to identify and apply the correct ciphering key without interrupting the encryption session. This mechanism ensures seamless security continuity and prevents data exposure during transitions. In 5G systems, while the concept evolves with the introduction of the Key Set Identifier (KSI), CKSN remains relevant in interworking scenarios with legacy networks.

Key components involved with CKSN include the UE's security module (USIM), the serving network's mobility management entity (MME) or serving GPRS support node (SGSN), and the home network's HSS/AuC. The CKSN is typically a 3-bit value, allowing up to eight distinct key sequences to be managed simultaneously. This limited range requires careful key lifecycle management, including periodic key updates via re-authentication to prevent exhaustion of sequence numbers. The CKSN is also used in conjunction with the Key Set Identifier (KSI) in EPS and 5GS to provide backward compatibility and support for ciphering key negotiation procedures.

Purpose & Motivation

CKSN was introduced to solve critical key management challenges in early 3G (UMTS) networks, where secure and efficient ciphering key synchronization between the UE and network was essential for maintaining confidentiality. Prior to CKSN, 2G systems like GSM used a simpler key derivation approach without explicit sequence numbering, which led to vulnerabilities during handovers and potential key mismatches. These mismatches could cause service interruptions or security gaps, as the network and UE might attempt to use different encryption keys, resulting in decryption failures or exposed data.

The primary motivation for CKSN was to enable robust security context management during mobility and reconnection scenarios. Without a key identifier, networks would need to perform full authentication and key agreement for every connection attempt, increasing signaling overhead and latency. CKSN allows the network to quickly identify and reuse previously established ciphering keys, reducing authentication frequency while maintaining security. This was particularly important for packet-switched services in UMTS, where devices frequently transition between idle and connected states.

Furthermore, CKSN addressed limitations in key lifecycle management by providing a mechanism to track key versions. This prevents the reuse of outdated or compromised keys and supports key refresh procedures. In inter-system handovers (e.g., between GSM and UMTS), CKSN facilitates smooth security context transfer, ensuring continuous protection without requiring user intervention. The design of CKSN as a small, efficient identifier reflects the need to minimize overhead in radio messages while providing reliable key indexing across diverse network architectures.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-5, normative work from Rel-16.

Rel-16 1 change

In Release 16, the specification introduced new general abbreviations, including a formal definition for "CKSN" (Ciphering Key Sequence Number) as part of a broader update to the document's terminology. This addition was made to ensure clarity and consistency within the technical standards. The change was documented via a Change Request, though the cover sheet initially displayed an incorrect CR number.

  • Add new general abbreviations MCC Note: CR cover sheet wrongly shows CR number as "1118". TS 21.905CR0118

Explore further

Broader topics and technologies where CKSN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 33.102 vj10 3G Security Architecture Specification Rel-19
TS 33.401 vj10 EPS Security Architecture Rel-19