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

Glossary term · Security

UEA2

UMTS Encryption Algorithm 2

Security →

UEA2 is the UMTS Encryption Algorithm 2, a 3GPP ciphering mechanism that uses AES in counter mode to protect user and signaling data confidentiality in UMTS systems.

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

Description

UEA2, or UMTS Encryption Algorithm 2, is a 3GPP ciphering algorithm for UMTS networks that provides confidentiality protection for signaling and user data. It is specified in TS 33.102 and TS 35.215 and was introduced in Release 7. UEA2 uses the Advanced Encryption Standard in counter mode, commonly AES-128-CTR. Like other UMTS ciphering algorithms, it operates after authentication and key agreement, when the UE and network have established a shared security context containing a cipher key, usually called CK. The network selects UEA2 during security mode procedures if the UE supports it and the operator policy allows AES-based ciphering. UEA2 is used to protect the content of messages or user-plane data so that an eavesdropper cannot recover plaintext. It does not provide integrity protection; integrity algorithms such as UIA1 or UIA2 are used for authentication and tamper detection.

Technically, UEA2 generates a keystream by encrypting counter blocks with AES-128. The input to the algorithm includes the cipher key CK and a set of security parameters, typically a message counter, direction indicator, length, and the message itself. In counter mode, the algorithm forms a sequence of counter values from the security parameters and encrypts each counter block with AES. The resulting output blocks are concatenated to form a keystream of the required length. The plaintext message is then XORed with this keystream to produce ciphertext. Decryption is symmetric: the receiver reconstructs the same counter sequence, generates the same keystream, and XORs the ciphertext to recover the plaintext. The counter value ensures that the keystream changes for each message or packet, preventing reuse of the same keystream. The direction indicator prevents uplink and downlink messages from being protected with identical keystream values, and the length field helps prevent truncation or extension of the encrypted payload.

Within the UMTS architecture, UEA2 is invoked by protocol layers that require confidentiality. This includes RRC signaling and user-plane data carried over radio bearers. The security context contains CK and the current counter values for each direction and bearer. When a message or packet must be encrypted, the relevant layer supplies the plaintext and the security parameters to the ciphering function. The UEA2 implementation defined in TS 35.215 performs AES-128 in counter mode and returns the ciphertext. The receiver performs the inverse operation using the same key and parameters. Because the algorithm is based on AES, it can benefit from widely available hardware acceleration and optimized software implementations. This made UEA2 attractive as a modern replacement for earlier UMTS ciphering options, particularly UEA1, which is based on KASUMI.

UEA2 plays an important role in the evolution of 3G security. Earlier UMTS ciphering algorithms were based on KASUMI, a block cipher designed specifically for mobile networks. While KASUMI was efficient, later analysis and industry preference for standardized, well-studied algorithms motivated the addition of AES. UEA2 provides confidentiality using AES-128 in counter mode, aligning UMTS with the cryptographic foundations used in later 3GPP systems such as LTE and 5G. It also complements UIA2, which provides integrity using AES-CMAC. Together, UEA2 and UIA2 offer a consistent AES-based security suite for UMTS networks. It is important to note that ciphering alone cannot detect message modification. If an attacker flips bits in ciphertext, the receiver may produce corrupted plaintext without knowing that tampering occurred. Therefore, UEA2 is typically used together with an integrity algorithm for signaling messages, while user-plane protection may rely on ciphering and higher-layer security depending on the deployment.

Purpose & Motivation

UEA2 exists to provide a stronger, more modern confidentiality option for UMTS networks. The original UMTS ciphering framework included UEA0, which is a null algorithm, and UEA1, which uses KASUMI. UEA1 was designed to be efficient for mobile devices and base stations, but over time the telecommunications industry moved toward AES as the preferred symmetric cipher. AES had undergone extensive public scrutiny, was widely implemented in hardware, and was already used in many security standards. UEA2 was introduced to give UMTS networks an AES-based encryption algorithm while preserving the existing key hierarchy and security-mode procedures.

The motivation was also practical. KASUMI had attracted cryptanalytic attention, and reliance on a proprietary or less widely studied cipher posed long-term risk. By adding UEA2, 3GPP allowed operators to migrate toward AES without redesigning the entire UMTS security architecture. The algorithm uses the same cipher key CK and similar input parameters as earlier ciphering algorithms, so it can be selected as an alternative during security mode command. This reduces implementation complexity and supports backward compatibility. UEA2 also addresses the limitation of UEA0, which provides no encryption at all, and the limitation of UEA1, which does not align with modern cryptographic preferences.

UEA2 solves the confidentiality problem for signaling and user data, but it does not solve integrity. That separation is intentional: ciphering and integrity are distinct security services. UEA2 ensures that an eavesdropper cannot recover plaintext, while UIA1 or UIA2 ensures that signaling messages are not altered or replayed. The introduction of UEA2 in Release 7 therefore strengthened UMTS security by adding a well-vetted AES-based encryption option and helped align 3G security with later 3GPP systems that rely heavily on AES.

What changed in its specifications

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

TS 33.102Rel-8 → Rel-9

Added 128-bit encryption for GSM and GPRS with Kc128 derived from CK and IK. Added IMS emergency call support over GPRS and EPS.

Full comparison in TS 33.102 →

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
  • UEA2 reused as 128-EEA1
    “128-EEA1 is based on SNOW 3G and is identical to UEA2 as specified in [14].” TS 33.401

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

UEA2 (SNOW 3G based) is specified for the first time in Rel-7, with TS 35.215 defining the algorithm and TS 33.102 adding UE support requirements and an algorithm identifier.

Rel-9 specification text

TS 33.102 gains a new text item on support of the UIA2 and UEA2 algorithms, adding a requirement that UMTS systems support UEA2.

Defining Specifications

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

SpecificationTitleRelease
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 35.215 vj00 3GPP UEA2 & UIA2 Confidentiality & Integrity Algorithms Rel-19 read