Description
UIA1, or UMTS Integrity Algorithm 1, is a 3GPP security algorithm defined for UMTS networks to provide integrity protection and data origin authentication for signaling messages. It is specified in TS 33.102 and TS 35.201 and was introduced in Release 99 as part of the UMTS security framework. UIA1 is used after the authentication and key agreement procedure has established a shared security context between the user equipment and the network. In that context, the network and the UE derive an integrity key, commonly called IK, which is used as the secret input to the algorithm. UIA1 is selected by the network during security mode procedures, subject to the UE reported capabilities and the security policy of the operator. Its primary role is to protect control-plane signaling, especially RRC messages, and in some deployments NAS messages, from modification, replay, or injection by an attacker. It does not provide confidentiality; ciphering algorithms such as UEA1, UEA2, or UEA3 are used for that purpose.
Technically, UIA1 is based on the HMAC-SHA-1 construction. HMAC is a keyed hash mechanism that combines a cryptographic hash function, in this case SHA-1, with a secret key to produce a message authentication code. The algorithm takes as input the integrity key IK and a message that is formed from the actual signaling payload together with security parameters. These parameters typically include a message counter, often referred to as COUNT, a direction indicator, a length field, and a fresh value or other context-dependent input. The direction indicator prevents a message protected for the downlink from being accepted on the uplink, and the length field prevents truncation or extension attacks. The counter provides replay protection because each direction and bearer or security context maintains an incrementing sequence number. The sender computes a MAC over the input message and appends it to the signaling message. The receiver recomputes the MAC using the same key and parameters and compares it with the received value. If the values match, the receiver accepts the message as authentic and unmodified; if they do not match, the message is discarded and the security context may be reset or an error procedure may be triggered.
Within the UMTS architecture, UIA1 sits in the security layer that supports the radio resource control and, where applicable, the non-access stratum. The security context is established during initial attach or after handover and contains keys such as CK for ciphering and IK for integrity. When a signaling message must be protected, the relevant protocol layer invokes the integrity algorithm with the message and the current security parameters. In the case of UIA1, the implementation calls the HMAC-SHA-1 based function defined in TS 35.201. The resulting MAC is transmitted with the message, usually in a dedicated field or appended to the payload according to the protocol specification. On the receiving side, the same parameters are reconstructed and the MAC is verified before the message is processed by higher-layer logic. This verification step is important because many UMTS procedures, including security mode command, handover, and radio bearer setup, are sensitive to message manipulation. An attacker who could alter such messages might force weaker security, redirect traffic, or impersonate network elements.
UIA1 is therefore a foundational integrity mechanism for 3G systems. It gives the network and the UE a way to authenticate signaling messages even when the physical radio link is exposed to eavesdropping and tampering. The algorithm is relatively straightforward to implement because HMAC-SHA-1 was already widely deployed and supported by software libraries and hardware. However, it is also a legacy mechanism. SHA-1 has known weaknesses, and the UMTS security framework later introduced UIA2, which uses AES-CMAC, to provide a stronger and more modern integrity option. UIA1 is still referenced in standards and may remain available for backward compatibility, but operators and device vendors generally prefer UIA2 when supported. The relationship between UIA1 and ciphering algorithms is also important: integrity protection and encryption are complementary. Encryption hides content, while integrity protection proves that the content was not altered and came from the expected party. In UMTS, UIA1 provides the latter for signaling, helping to maintain the trustworthiness of control-plane procedures.
Purpose & Motivation
UIA1 exists to address a security gap in mobile radio systems: the need to protect signaling messages from modification and replay. In early mobile networks, authentication and ciphering were the main security services. Authentication proved the identity of the UE or network, and ciphering concealed user data and some signaling. However, neither mechanism by itself prevented an attacker from altering control messages or replaying old messages. If signaling could be changed, an attacker might downgrade security, redirect handovers, or inject fake commands. UIA1 was introduced in UMTS to provide data origin authentication and integrity protection for signaling, making such attacks detectable.
Before UIA1, GSM-era mechanisms had limited integrity support for radio signaling. UMTS designers recognized that the IP-based packet core and more flexible radio control procedures increased the attack surface. A stronger security architecture was needed, with keys derived from authentication and algorithms that could be negotiated between UE and network. UIA1 used HMAC-SHA-1 because it was a mature, well-understood construction at the time and could be implemented efficiently. It solved the immediate problem of protecting RRC signaling and other control messages without requiring a completely new cryptographic primitive. The algorithm also included parameters such as counter, direction, and length to prevent replay and message substitution.
UIA1 was motivated by the need for a practical first-generation integrity algorithm for UMTS. Its limitations later became apparent: SHA-1 security margins weakened over time, and AES-based algorithms became preferred for both encryption and integrity. This led to UIA2 in Release 7. Still, UIA1 remains historically important because it established the integrity-protection model used in later 3GPP systems and helped define the security context, key usage, and MAC verification procedures that are central to mobile network control-plane security.
What changed in its specifications
The latest release-to-release comparison of specifications that define UIA1. Each summary describes the whole specification, not only this term.
Added 128-bit encryption for GSM and GPRS with Kc128 derived from CK and IK. Added IMS emergency call support over GPRS and EPS.
Full comparison in TS 33.102 →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
- UIA1 used together with UEA1
“Within the security architecture of the 3GPP system there are two standardised algorithms: A confidentiality algorithm f8, and an integrity algorithm f9.” TS 35.201
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.
Introduced in R99 (release dating of the term; no individual change cited).
A requirement was added making it mandatory for UEs and RNCs to implement the UIA1 integrity algorithm.
- “It shall be mandatory for UEs and RNCs to implement UIA1.” TS 33.102 v6.5.0
The requirement changed from UEs and RNCs mandatorily implementing UIA1 alone to implementing both UIA1 and UIA2, with UIA2 positioned as a back-up algorithm to UIA1.
- “UEs and RNCs shall implement UIA1 and UIA2.” TS 33.102 v7.1.0
- “It shall be mandatory for UEs and RNCs to implement UIA1.” TS 33.102 v7.1.0
Defining Specifications
3GPP specifications that define or reference UIA1, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 read |
| TS 35.201 vj00 | 3GPP Confidentiality & Integrity Algorithms f8/f9 | Rel-19 read |