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

Glossary term · Security

A5/3

Encryption Algorithm A5/3

Security →

A5/3 is a GERAN radio encryption algorithm based on KASUMI, introduced in 3GPP R99 to provide stronger confidentiality than legacy A5/1 and A5/2 on the GSM air interface.

Introduced
R99
Where
Security
Specifications
2 specs
A5/3 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

A5/3 is a GERAN radio encryption algorithm standardized in 3GPP R99 to provide confidentiality for GSM and GPRS traffic over the air interface. It is based on KASUMI, a 64-bit block cipher with a 128-bit key that was designed for 3GPP use in UMTS and later adapted for GERAN ciphering. A5/3 is used in the encryption mode of KASUMI, commonly referred to as f8, which transforms the block cipher into a keystream generator suitable for encrypting radio blocks. The algorithm is selected by the network during ciphering mode setting and applied by the UE and base station subsystem to protect user data and signalling that requires confidentiality.

The operation of A5/3 begins with a ciphering key and an initialization value derived from the radio frame context, including parameters such as a random value, frame number, direction, and bearer or logical channel information. These inputs initialize the KASUMI f8 mode, which repeatedly encrypts counter or block values to produce a keystream. The keystream is then XORed with the plaintext bits of the radio block to produce ciphertext, and the reverse operation is performed at the receiver. Because the algorithm is synchronous and depends on the frame context, both transmitter and receiver must maintain the same key and state. If the key or frame parameters are mismatched, decryption will fail and the receiver will typically discard or report the block as invalid.

A5/3 was introduced to address weaknesses in earlier GSM encryption algorithms. A5/1 had known cryptanalytic weaknesses and was vulnerable to time-memory trade-off and related attacks, while A5/2 was deliberately weakened for export restrictions. As GSM evolved into GPRS and EDGE, the need for stronger radio confidentiality became more important, especially for packet-switched services and roaming scenarios. KASUMI provided a modern block cipher foundation, and A5/3 allowed GERAN to adopt a stronger algorithm without replacing the entire GSM radio architecture. It became part of the GERAN security toolkit for networks that needed improved ciphering while continuing to support legacy GSM devices and infrastructure.

In the network, A5/3 operates primarily at the link and radio interface level. It does not define authentication or key establishment; those functions are handled by the SIM/USIM, authentication vectors, and security mode procedures. It also does not provide integrity protection for GERAN signalling. Its role is limited to confidentiality: ensuring that an eavesdropper on the radio interface cannot easily recover the transmitted voice or data payload. A5/3 can be negotiated when both the UE and network support it, and its use depends on the selected ciphering mode, subscriber capabilities, and operator policy.

A5/3 remains important historically as a bridge between classic GSM security and 3G-era cryptographic design. It illustrates how 3GPP strengthened legacy radio access networks by introducing algorithms derived from UMTS security primitives. While later networks and algorithms have moved toward stronger and more efficient ciphers, A5/3 represents a significant upgrade over legacy GSM encryption and a step toward modern cellular security.

From a deployment perspective, A5/3 was relevant for operators that wanted to improve 2G confidentiality without immediately replacing the radio access network. It could be introduced through software and configuration changes in compatible network elements and terminals. This made it useful during the transition from pure GSM to GPRS, EDGE, and multi-mode devices that also supported UMTS security algorithms.

Purpose & Motivation

A5/3 exists to strengthen the confidentiality of the GSM radio interface as mobile networks evolved from circuit-switched voice to packet data services. The original GSM ciphering algorithms were designed in a different security era. A5/1 was based on a relatively small state and had structural weaknesses that became increasingly concerning as computational resources grew. A5/2 was intentionally weakened to satisfy export restrictions, making it unsuitable for high-assurance commercial use. As GPRS and EDGE introduced higher data rates and more sensitive applications, operators needed an encryption algorithm that could protect user traffic over the air with a stronger cryptographic foundation.

The creation of KASUMI for UMTS provided an opportunity to reuse a modern 3GPP block cipher in GERAN. A5/3 was introduced in R99 to apply KASUMI-based confidentiality to GSM radio blocks. This allowed legacy GSM networks to adopt a stronger cipher while preserving the existing radio interface and authentication framework. It also supported roaming and multi-mode devices by providing a common algorithm family across 2G and 3G security contexts.

A5/3 addresses the limitation that GSM traffic was vulnerable to passive and active attacks when weak ciphers were used. It does not solve all security problems, because it lacks integrity protection and depends on key management, but it significantly raises the cost of eavesdropping and cryptanalysis compared with A5/1 and A5/2. Its purpose is therefore to provide a standardized, stronger GERAN encryption option during the transition from classic GSM to modern cellular security.

What changed in its specifications

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

TS 43.020Rel-14 → Rel-15

Rel-15 brings only minor changes to TS 43.020: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 43.020 →

Technology family

Ciphering and integrity algorithms · Security

  1. Phase 1 A5/1, A5/2, A8
  2. R97 GEA
  3. R98 B1, B2
  4. R99 A5/3, GEA3, KASUMI, UEA1, UIA1
  5. Rel-7 SNOW 3G, UEA2, UIA2
  6. Rel-8 128-EEA1, 128-EEA2, 128-EIA1, 128-EIA2, EEA0, EIA0
  7. Rel-9 A5/4, GEA4
  8. Rel-11 128-EEA3, 128-EIA3, ZUC
  9. Rel-13 GEA5, GIA4, GIA5
  10. Rel-15 128-NEA1, 128-NEA2, 128-NEA3, 128-NIA1, 128-NIA2, 128-NIA3, NEA0, NIA0
  • A5/3 extended by A5/4
    “The only essential change is the change of external key length input from 64 bits to 128 bits.” TS 55.226
  • A5/3 coexists with A5/1
    “It is mandatory for A5/1, A5/3, A5/4 and non encrypted mode to be implemented in mobile stations.” TS 43.020

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

TS 55.216 first appears in this release and specifies the A5/3 (and GEA3) encryption algorithm specification.

  • “The present document specifies the A5/3 and GEA3 specification.” TS 55.216 v3.0.0
Rel-4 specification text

Rel-4 TS 43.020 adds requirements on A5/3 support: implementing A5/3 in mobile stations is recommended, alongside mandatory A5/1, prohibited A5/2, and only standardised A5 algorithms allowed.

  • “It is recommended to implement A5/3 in mobile stations.” TS 43.020 v4.5.0
  • “Recommendation to support A5/3 and explicit prohibition of non-standard A5 algorithms in MS” TS 43.020 v4.5.0
Rel-6 specification text

A5/3 support in mobile stations changed from recommended to mandatory, alongside A5/1 and non-encrypted mode, and a usage note for A5/3 was added.

  • “It is mandatory for A5/1, A5/3 and non encrypted mode to be implemented in mobile stations.” TS 43.020 v6.5.1
  • “It is recommended to implement A5/3 in mobile stations.” TS 43.020 v6.5.1
Rel-11 specification text

A5/4 support becomes mandatory in mobile stations (previously optional) and in the BSS, alongside A5/3.

  • “It is mandatory for A5/1, A5/3, A5/4 and non encrypted mode to be implemented in mobile stations.” TS 43.020 v11.6.0
  • “It is mandatory for A5/3 and A5/4 to be implemented in the BSS.” TS 43.020 v11.6.0
Rel-14 specification text

The MS must disable use of A5/1, A5/3 or A5/4 on a visited network when instructed by an EF 'Disabled Algorithms' file in the SIM/USIM application.

  • “The use of non encrypted mode, A5/1, A5/3 or A5/4 in the MS shall be disabled on a particular visited network” TS 43.020 v14.6.0
  • “If the EF ‘Disabled Algorithms’ is present and active, then the algorithms marked as disabled shall not be used by the MS” TS 43.020 v14.6.0

Defining Specifications

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

SpecificationTitleRelease
TS 55.216 vj00 A5/3 and GEA3 Encryption Algorithms Specification Rel-19 read
TS 43.020 vj00 Security Procedures for GSM Rel-19 read