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

Glossary term · Security

GEA5

GPRS Encryption Algorithm 5

Security →

GEA5 is the Rel-13 3GPP GPRS encryption algorithm based on AES that uses a 128-bit key to protect GERAN packet data.

Introduced
Rel-13
Where
Security
Specifications
2 specs
GEA5 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

GEA5 is a 3GPP GPRS encryption algorithm introduced in Rel-13 and specified in TS 55.251. It is part of the GERAN encryption algorithm family referenced in TS 43.020 and is intended to provide confidentiality for packet data in GSM/GPRS/EDGE networks. GEA5 is applied to LLC frames between the mobile station and the SGSN, protecting user-plane packet payloads carried over the radio interface. As with earlier GEA algorithms, it is optional and negotiated, allowing operators to deploy a stronger cipher on supported devices and network elements. Its introduction reflected the fact that GPRS was still used for coverage, fallback, and machine-to-machine services even as newer radio access technologies became dominant.

The underlying primitive of GEA5 is AES, the Advanced Encryption Standard block cipher. AES operates on 128-bit blocks and supports 128-bit, 192-bit, or 256-bit keys; GEA5 is defined for GERAN packet encryption using AES as the basis for a keystream construction, commonly in counter mode with a 128-bit key. In counter mode, the algorithm encrypts successive counter blocks with the session key, producing a pseudorandom keystream that is XORed with the LLC payload. The counter is initialized from security parameters such as the cipher key, packet or frame count, bearer or logical channel identifier, and direction, ensuring that each packet uses a distinct keystream. AES is widely analyzed, has strong security margins, and is commonly accelerated in hardware, which makes it suitable for constrained mobile devices and network equipment.

During operation, the cipher key is established through authentication and key agreement and is not transmitted over the air. If GEA5 is selected, both the mobile station and SGSN configure the AES-based algorithm with matching inputs. The sender generates keystream blocks by encrypting counters and XORs them with the plaintext LLC data. The receiver repeats the same process to decrypt. Because AES in CTR mode turns a block cipher into a stream-like construction, it can encrypt variable-length packet payloads efficiently. GEA5 provides confidentiality; cryptographic integrity is not its main purpose, and error detection remains handled by LLC and lower-layer mechanisms. Integrity protection, if required, is provided by separate security functions or higher-layer protocols.

GEA5 was introduced to modernize GERAN packet security with a widely deployed and extensively analyzed cipher. AES had become the dominant block cipher in LTE and later 3GPP security, with hardware acceleration common in mobile devices and network equipment. By adding AES-based GEA5, 3GPP gave GERAN an algorithm aligned with newer radio access technologies and with the security expectations of data services, IoT, and machine-to-machine communications that still used GPRS. It also offered operators an alternative to KASUMI-based GEA3 and SNOW 3G-based GEA4, allowing selection based on device capability, performance, and operational policy.

Architecturally, GEA5 changes only the confidentiality transformation for LLC frames. It does not redefine GPRS mobility, routing, or bearer management. Its value is in extending legacy packet networks with a contemporary cipher while preserving backward compatibility. For engineers, GEA5 illustrates how 3GPP evolves security incrementally: legacy GERAN can negotiate stronger algorithms without replacing the entire radio architecture, while implementations can reuse AES libraries and hardware support developed for newer standards.

Purpose & Motivation

GEA5 exists to bring AES-based confidentiality to GPRS packet data. By Rel-13, many networks still relied on GPRS/EDGE for coverage, fallback, and machine-to-machine services, but legacy GERAN ciphers such as GEA1 and GEA2 were no longer considered strong enough for sensitive data. GEA3 and GEA4 had improved security by introducing KASUMI and SNOW 3G, yet AES had become the mainstream cipher in LTE and in modern hardware. GEA5 addressed this by aligning GERAN packet encryption with AES, giving operators a widely trusted algorithm with broad implementation support.

Historically, 3GPP had to upgrade security without disrupting deployed devices. A mandatory replacement of GPRS ciphers would have been infeasible, so GEA5 was introduced as an optional negotiated algorithm. It solved the problem of providing modern cipher strength to legacy packet networks while allowing older devices to continue operating. Its motivation was also practical: AES hardware acceleration in chips made efficient encryption possible even on constrained devices, and using AES simplified security testing and implementation across radio access technologies.

What changed in its specifications

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

TS 55.251Rel-13 → Rel-14

Rel-14 brings only minor changes to TS 55.251: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 55.251 →
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
  • GEA5 used together with GIA5
    “GEA5/GIA5 for ciphering and integrity protection based on SNOW 3G.” TS 43.020
  • GEA5 builds on SNOW 3G
    “GEA5 is based on SNOW 3G, and is specified in TS 55.251 [25].” 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.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 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.

Rel-13 introduced

GEA5, a SNOW 3G-based stream cipher using a 128-bit key Kc128, is specified for the first time in TS 55.251 and added to TS 43.020 for GPRS ciphering.

  • “The confidentiality algorithm GEA5 is a stream cipher that is used to encrypt/decrypt blocks of data under a confidentiality key KC128.” TS 55.251 v13.0.1
  • “The input parameters to the GEA5 are the 128-bit ciphering key Kc128, the 32-bit INPUT, the 1-bit DIRECTION and the 32-bit CONSTANT-F.” TS 43.020 v13.9.0
  • Adding details for new cellular algorithms GIA4, GEA5 and GIA5 TS 43.020CR0041

Defining Specifications

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

SpecificationTitleRelease
TS 55.251 vj00 GEA5 and GIA5 Encryption Algorithm Specification Rel-19 read
TS 43.020 vj00 Security Procedures for GSM Rel-19 read