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

Glossary term · Security

128-EIA3

128-bit EPS Integrity Algorithm 3

Security →

128-EIA3 is a 3GPP-standardized cryptographic integrity algorithm for the Evolved Packet System, introduced in Release 11 to provide message authentication and integrity protection for LTE signaling data between the UE and network against tampering during transmission.

Introduced
Rel-11
Where
Security
Specifications
2 specs
128-EIA3 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The 128-EIA3 is a stream cipher-based integrity algorithm defined within the 3GPP security architecture for EPS. It operates within the Packet Data Convergence Protocol (PDCP) layer in the radio protocol stack, specifically protecting Radio Resource Control (RRC) signaling messages and user-plane data integrity where required. The algorithm uses a 128-bit integrity key (IK), a 32-bit COUNT (a packet sequence number), a 5-bit BEARER identity, a 1-bit direction indicator (uplink/downlink), and the message length to generate a 32-bit Message Authentication Code (MAC-I) for the message. This MAC-I is appended to the data before transmission. The receiving entity independently calculates the expected MAC-I (XMAC-I) using the same inputs and compares it to the received MAC-I to verify integrity.

The algorithm's core is based on the ZUC stream cipher, a design developed in China and submitted to 3GPP. ZUC generates a keystream which is then used in a specific construction to produce the MAC. The design emphasizes efficiency and security, suitable for the high-speed, low-latency requirements of LTE. Its operation is standardized to ensure interoperability between user equipment and network equipment from different vendors globally.

Architecturally, 128-EIA3 is one of several EPS Integrity Algorithms (EIA). It is selected during the NAS Security Mode Command procedure and the AS Security Mode Command procedure, where the network indicates to the UE which algorithms are supported and preferred. The successful integrity verification is fundamental for establishing a secure radio bearer and maintaining trust in the control-plane signaling, which governs connection setup, handovers, and other critical mobility and session management functions.

Purpose & Motivation

128-EIA3 was introduced to diversify the cryptographic algorithm suite available for LTE network integrity protection. Prior to its introduction, EPS relied on algorithms like 128-EIA1 (based on Snow 3G) and 128-EIA2 (based on AES). The creation of 128-EIA3, based on the ZUC cipher, served multiple purposes. Firstly, it enhanced cryptographic agility by providing an additional, independently designed algorithm, reducing reliance on a single cryptographic design philosophy and mitigating risk if a weakness were discovered in the existing algorithms. Secondly, it addressed specific regional requirements and contributed to global cryptographic standards, incorporating Chinese cryptographic expertise into the international 3GPP framework.

The motivation stemmed from a desire to strengthen the overall security posture of mobile networks as they became more critical to infrastructure. By standardizing multiple strong algorithms, 3GPP ensured that operators could choose and combine algorithms based on their security policies, regulatory requirements, and to implement defense-in-depth strategies. This diversification protects against the potential compromise of any one algorithm and supports long-term network security as cryptographic techniques evolve.

What changed in its specifications

The latest release-to-release comparison of specifications that define 128-EIA3. 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-EIA3 reused as 128-NIA3
    “128-NIA3 is based on 128-bit ZUC (see TS 35.221 [18]).” TS 33.501
  • 128-EIA3 builds on ZUC
    “128-EIA3 is based on ZUC and specified in [33].” 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 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.

Rel-11 introduced

128-EIA3, a ZUC-based EPS integrity algorithm, is specified for the first time, with an algorithm identifier and optional UE/eNB/MME support for RRC and NAS integrity protection.

  • “128-EIA3 is based on ZUC and specified in [33].” TS 33.401 v11.9.0
  • “UEs and eNBs may implement 128-EIA3 for RRC signalling integrity protection.” TS 33.401 v11.9.0
  • “UEs and MMEs may implement 128-EIA3 for NAS signalling integrity protection.” TS 33.401 v11.9.0
Rel-15 specification text

For EN-DC in Rel-15, 128-EIA3 is mapped to NR's 128-NIA3, so UE support of 128-NIA3 must equal its 128-EIA3 support, including for RRC integrity protection.

  • “128-NIA3 (which is the same as 128-EIA3) for RRC integrity protection .” TS 33.401 v15.12.0
  • “the UE shall have the same support for 128-NEA1 as 128-EEA1” TS 33.401 v15.12.0
Rel-17 specification text

128-EIA3 (as 128-NIA3) is now also allowed for user plane integrity protection, whereas OLD covered only RRC and NAS signalling integrity.

  • “UEs and eNBs may implement 128-EIA3 for the user plane integrity protection.” TS 33.401 v17.7.0
  • “128-NIA3 (which is the same as 128-EIA3) for both RRC and UP integrity protection” TS 33.401 v17.7.0

Defining Specifications

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

SpecificationTitleRelease
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 35.221 vj00 3GPP Confidentiality & Integrity Algorithms EEA3/EIA3 Rel-19 read