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

Glossary term · Security

128-EEA2

128-bit EPS Encryption Algorithm 2

Security →

128-EEA2 is a 128-bit standardized ciphering algorithm for 4G LTE/EPS that encrypts user data and control signaling between the UE and eNB over the air interface to prevent eavesdropping.

Introduced
Rel-8
Where
Security
Specifications
1 specs
128-EEA2 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

128-EEA2 is a cryptographic encryption (ciphering) algorithm standardized by 3GPP for the Evolved Packet System (EPS), which encompasses 4G LTE. It is one of the EPS Encryption Algorithms (EEA) designed to provide confidentiality protection for data transmitted over the LTE-Uu air interface between the User Equipment (UE) and the evolved NodeB (eNB). The algorithm itself is based on the AES (Advanced Encryption Standard) block cipher, specifically operating in Counter Mode (AES-CTR). This mode transforms the block cipher into a stream cipher, making it efficient for encrypting packet data of variable lengths typical in mobile communications.

The algorithm operates within the PDCP (Packet Data Convergence Protocol) layer. For encryption, it takes several inputs: the ciphering key (CK), a time-dependent counter (COUNT), the bearer identity (BEARER), the direction of the transmission (uplink or downlink), and the length of the keystream required. Using these inputs, the AES-CTR engine generates a pseudorandom keystream. This keystream is then XORed with the plaintext data (for user plane) or the plaintext PDCP PDU (for control plane) to produce the ciphertext. The receiving side performs the identical process using the same inputs and key to regenerate the keystream and decrypt the data by XORing the ciphertext with the keystream.

128-EEA2 protects both user plane traffic (the actual user data like web pages or voice packets) and RRC (Radio Resource Control) control plane signaling. It does not apply to NAS (Non-Access Stratum) signaling, which is encrypted end-to-end between the UE and the MME using different keys and algorithms. The selection of 128-EEA2, versus other EEAs like 128-EEA1 or 128-EEA3, is determined during the Security Mode Command procedure based on the capabilities supported by both the UE and the network. Its implementation is mandatory for all LTE-compliant devices and networks, ensuring a baseline of confidentiality across global LTE deployments.

Purpose & Motivation

128-EEA2 was developed as part of the LTE security specifications in 3GPP Release 8. A primary goal for LTE was to improve upon the security mechanisms of 3G UMTS. While 3G used the KASUMI block cipher (in f8 mode for confidentiality), LTE sought to adopt more modern, widely analyzed, and efficient cryptographic algorithms. The AES standard, chosen by 128-EEA2, represented a global cryptographic benchmark known for its strength and performance in hardware and software.

Its creation solved the critical need for strong over-the-air encryption in the new LTE system. It addressed the limitation of relying solely on the older KASUMI-based cipher (128-EEA1) by providing an AES-based alternative. This offered enhanced cryptographic assurance and efficiency. By standardizing multiple algorithms (EEA1, EEA2, EEA3), 3GPP also provided flexibility and a migration path, allowing networks to choose based on their security policies and performance requirements, while ensuring all devices supported a common set for interoperability.

What changed in its specifications

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

TS 33.401Rel-18 → Rel-19

Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.

Full comparison in TS 33.401 →

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
  • 128-EEA2 reused as 128-NEA2
    “128-NEA2 is based on 128-bit AES [15] in CTR mode [16].” TS 33.501

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 2 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-8 introduced

128-EEA2 is specified for the first time in TS 33.401 as an AES-based (CTR mode) EPS ciphering algorithm that UEs, eNBs and MMEs must implement for RRC, UP and NAS ciphering.

  • “UEs and eNBs shall implement EEA0, 128-EEA1 and 128-EEA2 for both RRC signalling ciphering and UP ciphering.” TS 33.401 v8.8.0
  • “128-EEA2 is based on 128-bit AES [15] in CTR mode [16]” TS 33.401 v8.8.0
  • “UEs and MMEs shall implement EEA0, 128-EEA1 and 128-EEA2 for NAS signalling ciphering.” TS 33.401 v8.8.0
Rel-15 specification text

For dual connectivity with an NR gNB, 128-EEA2 support is mapped to 128-NEA2, so the UE must support 128-NEA2 the same as 128-EEA2 for RRC and UP confidentiality.

  • “128-NEA2 (which is the same as 128-EEA2) for both RRC and UP confidentiality.” TS 33.401 v15.12.0
  • “the UE shall have the same support for 128-NEA1 as 128-EEA1, 128-NEA2 as 128-EEA2” TS 33.401 v15.12.0

Defining Specifications

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

SpecificationTitleRelease
TS 33.401 vj20 EPS Security Architecture Rel-19 read