Description
MILENAGE is a set of cryptographic algorithms designed for use in 3GPP Authentication and Key Agreement (AKA) procedures. It was originally developed as an example algorithm set to demonstrate how the 3GPP authentication and key generation functions can be implemented. The MILENAGE algorithms are specified in 3GPP technical specifications 33.834 and 35.934. They are used in the Authentication Center (AuC) and the Universal Subscriber Identity Module (USIM) to perform mutual authentication between the network and the user equipment (UE), and to generate session keys for securing subsequent communications.
The MILENAGE algorithm set consists of a core function f1-f5 and f1*-f5*, which are based on the AES (Advanced Encryption Standard) block cipher. Specifically, it uses a 128-bit key and operates on 128-bit blocks. The algorithms include functions for generating authentication vectors (f1, f2, f3, f4, f5) and for re-synchronization (f1*, f5*). The f1 function computes a message authentication code (MAC) for authentication, f2 generates the response (RES) used for authentication, f3 generates the cipher key (CK), f4 generates the integrity key (IK), and f5 generates the anonymity key (AK). The f1* and f5* are used for re-synchronization procedures. The MILENAGE algorithms are designed to be secure and efficient, leveraging the widely deployed AES.
In the 3GPP AKA procedure, the AuC generates an authentication vector (AV) consisting of a random challenge (RAND), an authentication token (AUTN), an expected response (XRES), a cipher key (CK), and an integrity key (IK). The MILENAGE algorithms are used to compute these values. The USIM, upon receiving RAND and AUTN, uses the same algorithms to verify the AUTN and compute the response RES, which is sent back to the network. If the RES matches XRES, the UE is authenticated. The CK and IK are then used to derive keys for ciphering and integrity protection at the access stratum and non-access stratum.
MILENAGE is an example algorithm set, meaning that operators can choose to use it or define their own algorithms. However, MILENAGE is widely adopted because it is based on AES, which is well-studied and efficient. It is used in 3G, 4G, and 5G networks. The algorithms are implemented in both the USIM and the AuC, ensuring interoperability. The security of MILENAGE relies on the secrecy of the subscriber key (K) and the randomness of the RAND. The use of AES provides strong resistance against cryptanalysis.
Over the releases, the MILENAGE definition has remained essentially unchanged, indicating its stability and continued relevance. It is a cornerstone of 3GPP security, enabling secure authentication and key agreement for millions of subscribers worldwide.
Purpose & Motivation
MILENAGE was created to provide a standardized, secure, and efficient algorithm set for 3GPP authentication and key generation. Before its introduction, there was a need for a common example algorithm that could be used by equipment vendors and operators to ensure interoperability and security. The 3GPP AKA procedure requires cryptographic functions to authenticate the subscriber and generate keys, but the specifications did not mandate a specific algorithm, leaving it to operators. However, to facilitate implementation and testing, an example algorithm set was needed. MILENAGE fills this gap by offering a reference implementation based on AES.
The motivation for using AES was to leverage its widespread availability and proven security. AES is efficient in both hardware and software, making it suitable for resource-constrained devices like USIM cards. MILENAGE also addresses the need for re-synchronization mechanisms to handle sequence number mismatches, which are common in mobile networks. The algorithm set includes functions for generating authentication vectors and for re-synchronization, providing a complete solution.
Historically, earlier generations (2G) used algorithms like COMP128, which were proprietary and sometimes vulnerable. MILENAGE was designed to be more transparent and based on open standards, allowing for public scrutiny. It has been adopted in 3G, 4G, and 5G networks, demonstrating its longevity. The stability of the MILENAGE definition across releases reflects its maturity and the fact that it continues to meet the security requirements of 3GPP networks.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference MILENAGE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 33.834 vg10 | Long Term Key Update Procedures Study | Rel-16 read |
| TR 35.934 vj00 | Tuak algorithm set for 3GPP auth & key gen | Rel-19 read |