Description
GPRS Integrity Algorithm 4 (GIA4) is a core component of the security architecture for General Packet Radio Service (GPRS) and later 2G/3G packet-switched networks. It operates within the GPRS Encryption Algorithm (GEA) framework but is specifically dedicated to ensuring data integrity, as opposed to confidentiality. The algorithm is implemented in the network elements that handle the Gb interface, primarily the Serving GPRS Support Node (SGSN) and the Base Station Subsystem (BSS), which includes the Base Station Controller (BSC). Its primary role is to generate and verify Integrity Check Values (ICVs) or Message Authentication Codes (MACs) for data packets traversing this interface.
Technically, GIA4 functions by taking input parameters such as a secret cipher key (Kc), a time-variant input like a frame number, the direction of transmission (uplink/downlink), and the user data itself. It processes these inputs through a standardized cryptographic function to produce a fixed-length integrity tag. This tag is appended to the data packet. The receiving entity independently computes the expected tag using the same inputs and the shared secret key. If the computed tag matches the received tag, the data's integrity is verified, confirming it has not been altered in transit. A mismatch indicates a potential integrity violation, leading to the rejection of the packet.
Architecturally, GIA4 is part of the GPRS security protocols defined for the Gb interface layer. It works in conjunction with confidentiality algorithms like GEA4. The algorithm's specifications, including its detailed logical functions and test data, are meticulously documented in 3GPP technical specifications to ensure interoperability between equipment from different vendors. Its deployment strengthens the trust in the packet data service by protecting against data manipulation, replay attacks, and certain forms of signaling fraud, thereby forming a critical, albeit often transparent, layer of the overall network security posture for 2G and 3G mobile data.
Purpose & Motivation
GIA4 was created to address the evolving security requirements of GPRS and UMTS packet-switched domains. Early GPRS security mechanisms, primarily focused on encryption (GEA1-GEA3), lacked robust, standardized integrity protection dedicated to the Gb interface. This gap posed a risk, as data or signaling messages could be tampered with during transmission without detection. The introduction of dedicated integrity algorithms like GIA4 in Release 13 was part of a broader effort to bolster the security of legacy network interfaces, ensuring they met more contemporary security standards even as the industry transitioned towards 4G and 5G.
The motivation stemmed from the need for a comprehensive security suite. While encryption protects confidentiality, integrity protection is essential for ensuring data authenticity and preventing malicious modifications. GIA4, alongside GIA5, provided network operators with stronger, algorithmically distinct options for integrity protection. This was particularly important for maintaining secure services on networks that continued to support 2G and 3G devices and for ensuring backward-compatible security could be enhanced without requiring a full network overhaul. It addressed limitations of previous approaches where integrity might have been an afterthought or provided by weaker, non-standardized mechanisms.
What changed in its specifications
The latest release-to-release comparison of specifications that define GIA4. Each summary describes the whole specification, not only this term.
Rel-14 brings only minor changes to TS 55.241: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 55.241 →Rel-15 brings only minor changes to TS 43.020: 1 clause changed, with no change attributed to a release feature.
Full comparison in TS 43.020 →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.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented 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.
The GIA4 integrity algorithm, a KASUMI-based 32-bit MAC algorithm, is specified for the first time in TS 55.241 and added to the GPRS security requirements in TS 43.020.
- “The present document defines the technical details of the 3GPP integrity algorithm GIA4.” TS 55.241 v13.0.1
- “The integrity algorithm GIA4 computes a 32-bit MAC (Message Authentication Code) of a given input message using integrity key KI128.” TS 55.241 v13.0.1
- “The MS shall support integrity algorithms GIA4 and GIA5.” TS 43.020 v13.9.0
Defining Specifications
3GPP specifications that define or reference GIA4, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 55.241 vj00 | 3GPP Integrity Algorithm GIA4 Specification | Rel-19 read |
| TS 43.020 vj00 | Security Procedures for GSM | Rel-19 read |