Description
GEA3 is a 3GPP confidentiality algorithm for GPRS packet data in GERAN. It is specified in TS 55.216 and referenced in TS 43.020, which defines the family of GSM/GPRS encryption algorithms. GEA3 is used when a mobile station and SGSN select an optional stronger cipher for the logical link control (LLC) layer. The LLC layer sits above the SNDCP packet transfer layer and below the RLC/MAC radio link layer, so GEA3 protects LLC frames carried between the MS and SGSN, not necessarily every lower-layer radio frame. Its primary role is to keep user-plane packet payloads confidential against eavesdropping on the radio interface. The algorithm is selected through security capability exchange, and the network chooses an encryption algorithm supported by both endpoints.
The algorithm is based on KASUMI, a block cipher standardized by 3GPP for UMTS security. KASUMI operates on 64-bit blocks with a 128-bit key and uses an eight-round Feistel-like structure with FL, FLi, and FO functions. GEA3 uses KASUMI as a keystream generator, generally by encrypting a sequence of counter blocks and XORing the resulting keystream with the LLC payload. Because KASUMI is a block cipher, GEA3 does not directly encrypt a whole frame in one pass; it generates a mask of the required length. The counter block construction allows parallel generation of keystream words and makes the algorithm suitable for packet-oriented traffic. The counter is initialized from security parameters such as the cipher key, a frame or packet count, a bearer or logical channel identifier, and the transmission direction. This construction avoids repeating the same keystream for different frames and allows receiver-side decryption without needing the plaintext.
In a GERAN network, the cipher key is established during authentication and key agreement, typically from the GSM-MAP authentication procedure. The key is not transmitted over the air; it is derived from authentication vectors and used locally by the MS and network. The network and mobile station then agree on an encryption algorithm, such as GEA1, GEA2, GEA3, or another supported algorithm. If GEA3 is selected, both endpoints apply the KASUMI-based construction to LLC frames. The algorithm provides confidentiality but not cryptographic integrity; error detection is still handled by LLC CRC and lower-layer mechanisms. Integrity protection, if required, is provided by separate mechanisms or higher-layer security.
GEA3 was introduced as an upgrade path from legacy GPRS ciphers. Early GEA algorithms were designed for 64-bit keys and simpler stream-cipher constructions, which became less attractive as computational resources and cryptanalytic techniques improved. GEA3 addressed this by using a stronger block-cipher primitive and larger key material. By reusing KASUMI, GEA3 aligned GERAN packet security with the block-cipher primitive used in UMTS, allowing shared implementation effort and stronger key material. It is optional, so operators could deploy it gradually on supported devices and network elements while older terminals continued to use legacy algorithms.
From an architecture perspective, GEA3 sits in the security plane of GERAN. It does not change routing, mobility, or radio resource management; it changes how LLC payloads are protected. Its importance lies in preserving confidentiality for packet data services such as GPRS and EDGE, where user data may be more sensitive than voice traffic. It also demonstrates 3GPP's approach of evolving legacy GSM security by adding modern primitives while maintaining backward compatibility. For engineers, GEA3 is a bridge between GSM-era packet security and UMTS-era cryptographic standards.
Purpose & Motivation
GEA3 exists to strengthen confidentiality for GPRS packet data. The original GSM and GPRS encryption algorithms were designed in an era when 64-bit keys and lightweight stream ciphers were considered adequate. As networks carried more sensitive data and attackers gained greater computational power, these legacy designs became less desirable. GEA3 addresses this by using KASUMI, a block cipher selected for UMTS, and a 128-bit key construction. This gives GERAN operators an optional, standards-based way to protect LLC frames with a stronger primitive.
Historically, GPRS security had to remain backward compatible with vast installed GSM infrastructure. A wholesale replacement of legacy ciphers was impractical, so 3GPP introduced additional algorithms that could be negotiated when both the mobile station and network supported them. GEA3 solved the problem of weak packet confidentiality without breaking older devices. It also reduced implementation cost by reusing KASUMI across GERAN and UTRAN. The motivation was therefore both security and migration: provide a stronger, interoperable option for packet data while allowing legacy networks to continue operating.
What changed in its specifications
The latest release-to-release comparison of specifications that define GEA3. Each summary describes the whole specification, not only this term.
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
- Phase 1 A5/1, A5/2, A8
- R97 GEA
- R98 B1, B2
- R99 A5/3, GEA3, KASUMI, UEA1, UIA1
- Rel-7 SNOW 3G, UEA2, UIA2
- Rel-8 128-EEA1, 128-EEA2, 128-EIA1, 128-EIA2, EEA0, EIA0
- Rel-9 A5/4, GEA4
- Rel-11 128-EEA3, 128-EIA3, ZUC
- Rel-13 GEA5, GIA4, GIA5
- Rel-15 128-NEA1, 128-NEA2, 128-NEA3, 128-NIA1, 128-NIA2, 128-NIA3, NEA0, NIA0
- GEA3 extended by GEA4
“GEA 4 is the same algorithms as GEA3 but with KLEN changed from 64 to 128 bits.” TS 55.226
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 sourcesDocumented changes in 3 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.
TS 55.216 first appears in Rel-99 and specifies the A5/3 and GEA3 encryption algorithms, defining GEA3 for the first time.
- “The present document specifies the A5/3 and GEA3 specification.” TS 55.216 v3.0.0
Rel-6 GERAN security spec 43.020 makes GEA3 implementation mandatory in mobile stations, alongside GEA1, GEA2 and unencrypted GEA0, and excludes other GPRS algorithms.
- “It is mandatory for GEA1, GEA2, GEA3 and non encrypted mode (i.e. GEA0) to be implemented in mobile stations.” TS 43.020 v6.5.1
Rel-8 changes the mobile station requirement: GEA3 and GEA0 are mandatory, while GEA1 and GEA2 become prohibited and must not be implemented, instead of all four being mandatory.
- “It is mandatory for GEA3 and non encrypted mode (i.e. GEA0) to be implemented in mobile stations.” TS 43.020 v8.2.0
- “It is mandatory for GEA1, GEA2, GEA3 and non encrypted mode (i.e. GEA0) to be implemented in mobile stations.” TS 43.020 v8.2.0
Defining Specifications
3GPP specifications that define or reference GEA3, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |