Description
GEA4 is a 3GPP GPRS encryption algorithm introduced in Rel-9 and specified in TS 55.226. It is part of the GERAN ciphering family described in TS 43.020 and is used to provide confidentiality for packet data carried over GPRS/EDGE radio access. Like other GEA algorithms, GEA4 operates at the LLC layer between the mobile station and the SGSN, protecting LLC frames that contain user-plane packet data. It is optional and negotiated between endpoints, allowing operators to upgrade security while retaining support for legacy algorithms. The mobile station advertises supported encryption algorithms, and the SGSN selects one that both sides can implement.
The core primitive of GEA4 is SNOW 3G, a synchronous stream cipher standardized by 3GPP for UMTS security. SNOW 3G uses a 128-bit key and 32-bit word operations, combining a linear feedback shift register with substitution boxes and mixing functions. GEA4 uses SNOW 3G to generate a keystream that is XORed with the LLC payload. The cipher is initialized with security parameters such as the session key, a frame or packet count, a bearer or logical channel identifier, and the direction of transmission. The count parameter ensures that the keystream changes over time, preventing reuse of the same mask for different packets. Because SNOW 3G is word-oriented, the construction can be efficient on general-purpose processors and on modern baseband chips.
In operation, the network and mobile station derive or agree on a cipher key during authentication and key agreement. The key is not transmitted over the air; it is established from authentication vectors and used locally. When GEA4 is selected, both sides instantiate the SNOW 3G-based algorithm with the same inputs. The sender encrypts each LLC frame by generating keystream words and XORing them with the plaintext payload. The receiver performs the same operation to recover the original data. Because SNOW 3G is a stream cipher, encryption and decryption are symmetric and efficient for variable-length packet payloads. GEA4 provides confidentiality, but integrity is not its primary function; LLC CRC and higher-layer mechanisms handle error detection and integrity as needed.
GEA4 was added to provide an alternative to KASUMI-based GEA3 and legacy GEA1/GEA2. SNOW 3G was already used in UTRAN for f8 confidentiality, so GEA4 extended that primitive to GERAN packet security. This alignment allowed vendors to implement one security library across GSM/GPRS and UMTS. It also offered performance advantages: SNOW 3G is word-oriented and can be efficient in software, while KASUMI is block-oriented and may be better suited to certain hardware implementations. Operators could choose GEA3 or GEA4 depending on device support, performance, and security policy. The algorithm was introduced during a period when mobile data traffic was growing and when stronger legacy-radio security was needed.
From a network architecture viewpoint, GEA4 does not alter GPRS routing, mobility, or bearer setup. It changes the security transformation applied to LLC frames. Its significance is that it strengthened GERAN packet confidentiality in a standards-compliant way during the transition toward more data-centric mobile services. It also reflected 3GPP's practice of introducing optional, stronger ciphering algorithms into legacy radio access networks without forcing immediate retirement of older equipment. For engineers, GEA4 is a practical example of reusing UMTS stream-cipher technology to improve GSM/GPRS packet security.
Purpose & Motivation
GEA4 exists to improve GERAN packet confidentiality by bringing SNOW 3G, already used in UMTS, to GPRS encryption. Earlier GEA algorithms relied on legacy stream-cipher designs with 64-bit keys or simpler constructions that became increasingly vulnerable to cryptanalysis and resource growth. GEA3 introduced KASUMI, but KASUMI's block-cipher structure can be less efficient in software on some platforms. GEA4 addressed this by using SNOW 3G, a 128-bit-key stream cipher optimized for word-based processing.
Historically, Rel-9 was a period when mobile networks carried more sensitive data and operators needed stronger security in legacy GERAN. However, a forced upgrade of all GSM/GPRS devices was impractical. GEA4 provided an optional algorithm that could be negotiated when both the MS and SGSN supported it. This allowed gradual deployment while maintaining backward compatibility. Its motivation was to strengthen packet-data confidentiality, align GERAN with UTRAN security primitives, and offer a performance-friendly alternative to KASUMI-based encryption.
What changed in its specifications
The latest release-to-release comparison of specifications that define GEA4. 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
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.
GEA4 is specified for the first time in Rel-9 as a 128-bit GPRS ciphering algorithm, optional in mobile stations, with SGSN selection tied to a UMTS security context.
- “In this document are specified three ciphering algorithms: A5/4 for GSM, A5/4 for ECSD, and GEA4 for GPRS (including EGPRS).” TS 55.226 v9.0.0
- “the SGSN shall not select GEA4 if the SGSN does not share a UMTS security context with the MS.” TS 43.020 v9.4.0
- “Introduction of A5/4 and GEA4” TS 43.020 v9.4.0
The requirement text for GEA4 in mobile stations was reworded: GEA4 remains optional, GEA1/GEA2 prohibited, and the sentence barring other GPRS encryption algorithms was dropped.
- “No other GPRS encryption algorithms shall be supported in mobile stations.” TS 43.020 v11.6.0
- “GEA4 may be implemented in the mobile stations.” TS 43.020 v11.6.0
TS 43.020 gained requirements for GEA4 in the enhanced GPRS security features: MS and eSGSN must support GEA4 (with GIA4), and its input parameters are specified.
- “The MS shall support ciphering algorithms GEA0, GEA4 and GEA5.” TS 43.020 v13.9.0
- “If encryption is supported by eSGSN, only GEA4 or GEA5 shall be used with GIA4 or GIA5.” TS 43.020 v13.9.0
- “The input parameters used in GEA4 and GEA5 are not identical.” TS 43.020 v13.9.0
Defining Specifications
3GPP specifications that define or reference GEA4, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 55.226 vj00 | A5/4 & GEA4 Encryption Algorithms Specification | Rel-19 read |
| TS 43.020 vj00 | Security Procedures for GSM | Rel-19 read |