Description
SNOW 3G is a 3GPP stream cipher standardized in TS 35.216. It uses a 128-bit key and a 128-bit initialization vector, and it produces a continuous keystream that can be XORed with plaintext to obtain ciphertext, or used in integrity algorithms after appropriate construction. SNOW 3G was introduced in Release 7 and became important for LTE and later 5G security algorithms, where high-speed packet data required a cipher that could provide strong security with efficient hardware and software performance. Unlike a block cipher, SNOW 3G does not require padding and can operate naturally on byte or bit streams, which makes it well suited to IP-based radio bearers.
The cipher is built around a finite state machine and a linear feedback shift register. Its internal state consists of sixteen 32-bit registers. The LFSR portion provides linear mixing across the state, while the finite state machine adds nonlinear operations such as XOR, modular addition, and substitution through S-boxes. Each step of the cipher updates the registers and produces a 64-bit output word. The key and initialization vector are loaded into the internal state during initialization, and the cipher then runs for a number of discard steps so that the initial state is sufficiently mixed before any keystream is used. This setup phase is critical because it prevents weak initial states from being exposed to the attacker.
During normal operation, SNOW 3G generates keystream blocks that are combined with data. For confidentiality, the keystream is XORed with plaintext or ciphertext, depending on the direction. For integrity, the cipher can be used as part of a MAC construction, often with additional key mixing and finalization, so that the receiver can verify that the data has not been modified. The 3GPP algorithm specifications define how SNOW 3G interacts with keys, sequence numbers, bearer identifiers, and message lengths. These parameters provide freshness and bind the cryptographic output to a particular connection and direction, which is essential for preventing replay and forgery attacks.
SNOW 3G was designed to be faster and more secure than earlier 3GPP ciphers while remaining implementable in mobile devices and network equipment. Its 128-bit key and 128-bit IV align with the security expectations of LTE, where packet data rates and signalling volumes are much higher than in legacy 3G systems. The cipher's structure allows efficient parallelism in hardware and compact implementation in software. It also avoids some weaknesses associated with smaller block sizes or less modern constructions. In 3GPP, SNOW 3G became one of the core algorithms for ciphering and integrity protection, alongside AES-based and ZUC-based algorithms, giving operators options that balance security, performance, and compatibility.
The significance of SNOW 3G is that it represents the transition from legacy block-cipher security to stream-cipher security for packet-centric mobile networks. It supports the need for high-throughput encryption on shared radio bearers, while still providing cryptographic separation between ciphering and integrity keys. For engineers, understanding SNOW 3G requires looking at both the primitive itself and the 3GPP algorithms that use it. The cipher generates the raw keystream, but the security services are defined by the surrounding protocol logic, including key derivation, counters, padding, and MAC construction.
Purpose & Motivation
SNOW 3G exists to provide a modern, high-performance stream cipher for 3GPP security algorithms, particularly for LTE and later mobile systems. The main problem it addresses is the need to protect large volumes of packet data and signalling over radio interfaces efficiently. Legacy UMTS security relied heavily on KASUMI, a 64-bit block cipher that was well suited to the constraints of early 3G devices but less ideal for the high data rates and all-IP architecture of LTE. Block ciphers can introduce padding, require additional modes of operation, and may not be the most efficient choice for continuous packet streams.
SNOW 3G was motivated by the desire for stronger security margins and better throughput. A stream cipher can generate keystream on demand and XOR it with data, which is natural for IP packets and radio bearers. The 128-bit key and 128-bit initialization vector support the security expectations of fourth-generation networks, where attacks on keystreams and replay protection must be robust. SNOW 3G also fits the 3GPP model of having a small number of standardized primitives that can be used for both confidentiality and integrity through defined algorithms. By introducing SNOW 3G, 3GPP gave operators a practical way to upgrade security for LTE without requiring every device to implement a completely different cryptographic stack.
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
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.
Introduced in Rel-7 (release dating of the term; no individual change cited).
Defining Specifications
3GPP specifications that define or reference SNOW 3G, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 35.216 vj00 | 3GPP UEA2 & UIA2 Confidentiality & Integrity Algorithms | Rel-19 read |