Description
128-EIA2 is a cryptographic integrity algorithm defined by 3GPP for the Evolved Packet System (EPS) in 4G LTE. It is one of the EPS Integrity Algorithms (EIA) designed to provide data origin authentication and integrity protection for messages transmitted over the LTE radio link. The algorithm is based on the AES (Advanced Encryption Standard) block cipher, operating in CMAC (Cipher-based Message Authentication Code) mode. This mode allows it to generate a fixed-size tag that serves as a cryptographic seal for a message.
The algorithm functions within the PDCP (Packet Data Convergence Protocol) layer. To compute the integrity tag (called MAC-I), it takes several inputs: the integrity key (IK), a time-varying input (COUNT), the bearer identity (BEARER), the direction of transmission (uplink or downlink), and the message data itself. The AES-CMAC process uses these inputs, particularly the message data, to create a 32-bit Message Authentication Code. This MAC-I is appended to the message before transmission. Upon receipt, the receiving entity (UE or eNB) independently recalculates the MAC-I using the same inputs and the received message. If the calculated MAC-I matches the one received, the message's integrity is verified. A mismatch results in the message being discarded, signaling a potential integrity breach.
128-EIA2 is applied to protect RRC (Radio Resource Control) signaling messages and, optionally, user plane data packets. For user plane integrity, its use is less common than for control plane due to overhead, but the standard supports it. It does not protect NAS (Non-Access Stratum) signaling, which has its own end-to-end integrity mechanism between the UE and MME. During the Security Mode Command procedure, the network and UE negotiate which integrity algorithm to use from their supported sets (EIA1, EIA2, EIA3). Support for 128-EIA2 is mandatory for LTE devices and networks, ensuring a baseline of integrity protection and global interoperability.
Purpose & Motivation
128-EIA2 was developed alongside 128-EEA2 as part of the enhanced LTE security suite in 3GPP Release 8. LTE aimed to advance beyond 3G UMTS security by incorporating more robust and efficient cryptographic primitives. While 3G's primary integrity algorithm (128-EIA1) was based on the KASUMI block cipher, LTE introduced AES-based algorithms. AES was a globally recognized, highly scrutinized standard offering excellent security guarantees and efficient implementation.
The introduction of 128-EIA2 solved the need for a strong, modern integrity protection mechanism for the LTE control plane. It protected critical RRC signaling—which manages connection setup, handover, and bearer management—from tampering, forgery, and replay attacks. By providing an AES-CMAC-based alternative to the KASUMI-based 128-EIA1, it gave operators and device makers a choice based on performance, security analysis, and implementation preferences, while maintaining mandatory support for interoperability across the LTE ecosystem.
What changed in its specifications
The latest release-to-release comparison of specifications that define 128-EIA2. Each summary describes the whole specification, not only this term.
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
- 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
- 128-EIA2 reused as 128-NIA2
“128-NIA2 is based on 128-bit AES [15] in CMAC mode [17].” 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 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.
128-EIA2 is specified for the first time as an AES-CMAC based EPS integrity algorithm that UEs, eNBs and MMEs must implement for RRC and NAS signalling integrity protection.
- “128-EIA2 is based on 128-bit AES [15] in CMAC mode [17].” TS 33.401 v8.8.0
- “UEs and eNBs shall implement 128-EIA1 and 128-EIA2 for RRC signalling integrity protection.” TS 33.401 v8.8.0
- “UEs and MMEs shall implement 128-EIA1 and 128-EIA2 for NAS signalling integrity protection.” TS 33.401 v8.8.0
For EN-DC, the UE's 128-NIA2 support is mapped to its 128-EIA2 support, and 128-NIA2 (same as 128-EIA2) is specified for RRC integrity protection towards the SgNB.
- “128-NIA2 (which is the same as 128-EIA2) for RRC integrity protection.” TS 33.401 v15.12.0
- “128-NIA2 as 128-EIA2 and 128-NIA3 as 128-EIA3” TS 33.401 v15.12.0
128-EIA2 is now also specified for user plane integrity protection (UE shall, eNB may implement it), and 128-NIA2 (same as 128-EIA2) is applied to both RRC and UP integrity protection.
- “UEs shall and eNBs may implement 128-EIA1 and 128-EIA2 for the user plane integrity protection.” TS 33.401 v17.7.0
- “128-NIA2 (which is the same as 128-EIA2) for both RRC and UP integrity protection.” TS 33.401 v17.7.0
Defining Specifications
3GPP specifications that define or reference 128-EIA2, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |