Description
128-NEA3 is a stream cipher-based encryption algorithm defined within the 3GPP security architecture for 5G System (5GS). It operates primarily within the Packet Data Convergence Protocol (PDCP) layer in the 5G NR radio protocol stack. The algorithm is responsible for encrypting user-plane data and control-plane signaling messages (RRC) to ensure confidentiality. It uses a 128-bit Ciphering Key (CK), a 32-bit COUNT (a hyperframe number and PDCP sequence number), a 5-bit BEARER identity, a 1-bit direction indicator (uplink/downlink), and the length of the keystream required.
The algorithm core is the ZUC stream cipher, the same foundational cipher used in 128-EIA3. For encryption, ZUC generates a pseudorandom keystream based on the input parameters. This keystream is then XORed with the plaintext data to produce the ciphertext. The process is symmetric, meaning the same algorithm and key are used for encryption at the sender and decryption at the receiver. The specific construction and usage within PDCP are detailed in 3GPP specifications to guarantee interoperability.
In the 5G architecture, the selection of 128-NEA3 is part of the security negotiation between the UE and the network. During the Initial Context Setup or Security Mode Command procedures, the network's Access and Mobility Management Function (AMF) informs the gNB and the UE of the selected encryption algorithm from the mutually supported list. The successful application of 128-NEA3 ensures that all data transmitted over the NR air interface is concealed from unauthorized parties, forming a critical layer of 5G privacy and security.
Purpose & Motivation
128-NEA3 was created as part of the new 5G security algorithm suite defined in 3GPP Release 15. The development of 5G NR necessitated a fresh set of cryptographic algorithms, separate from those used in EPS/LTE, to align with new security requirements and protocols. While 5G supports some LTE security algorithms for backward compatibility and interworking, the introduction of native NR algorithms like 128-NEA3 was driven by the desire for a clean-slate design optimized for 5G's enhanced mobile broadband, ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC) use cases.
The purpose extends beyond mere confidentiality. It contributes to the 5G security principle of cryptographic algorithm agility. By standardizing multiple strong algorithms (NEA1, NEA2, NEA3) based on different ciphers (Snow 3G, AES, ZUC), 3GPP ensures the 5G ecosystem is not dependent on a single cryptographic foundation. This mitigates systemic risk and allows for future evolution, including the potential deprecation of an algorithm should vulnerabilities be discovered. 128-NEA3, based on ZUC, also represents the integration of this cipher into the core of 5G security, continuing its role from 4G and supporting global cryptographic standards.
What changed in its specifications
The latest release-to-release comparison of specifications that define 128-NEA3. Each summary describes the whole specification, not only this term.
Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.
Full comparison in TS 33.501 →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-NEA3 reuses 128-EEA3
“128-NEA3 is based on 128-bit ZUC (see TS 35.221 [18]).” 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.
Detected Changes Across Releases
verified against 3GPP sourcesDocumented 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.
TS 33.501 first specifies 128-NEA3 as a 5G NR encryption algorithm based on 128-bit ZUC, identical to 128-EEA3, defined in Annex D.
- “128-NEA3 is based on 128-bit ZUC (see TS 35.221 [18]).” TS 33.501 v15.20.0
- “128-NEA3 is identical to 128-EEA3 as specified in Annex B of TS 33.401 [10].” TS 33.501 v15.20.0
- “"00112" 128-NEA3 128-bit ZUC based algorithm.” TS 33.501 v15.20.0
Defining Specifications
3GPP specifications that define or reference 128-NEA3, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |