Description
The ASME Key is a 32-byte (256-bit) security key that is associated with the Authentication and Security Management Entity (ASME) in the 3GPP security architecture. The ASME is the entity in the core network — typically located in the MME for E-UTRAN or the AMF for 5G NR — that is responsible for authenticating the UE and deriving the security keys used to protect the air interface. The ASME Key represents the root key material held by this entity, from which the access security keys (such as KASME in LTE and KSEAF in 5G) are derived. In the 3GPP test specifications TS 31.121 (UICC terminal interface conformance testing for the USIM application) and TS 31.124 (UICC terminal interface conformance testing for the ISIM application), the ASME Key is defined as a test parameter used to verify the terminal's handling of security key material during authentication procedures.
The definition in the specifications states that the ASME Key is a '32 byte key, any value 'FF' (not available)'. This means that in the test context, the ASME Key is a 256-bit value, and the special value of all bytes set to 'FF' indicates that the key is not available or not applicable in a particular test scenario. This convention allows test cases to specify that no valid ASME key is present, which is used to verify the terminal's error handling and behavior when security key material is missing or invalid. The 32-byte length aligns with the 256-bit key sizes used in the 3GPP key hierarchy, where keys such as K, CK, IK, and the derived ASME keys are 128 or 256 bits long.
The ASME Key is part of the broader 3GPP security architecture defined in TS 33.401 (System Architecture Evolution security) and TS 33.501 (5G security). In this architecture, the long-term subscription key K is stored in the USIM and the AuC/HSS. During authentication, the UE and the network derive the cipher key CK and integrity key IK, from which the ASME derives the KASME (in LTE) or KSEAF (in 5G). The ASME Key in the test specifications represents the key material that the terminal must correctly handle when interacting with the USIM/ISIM and the network during authentication and key agreement procedures.
In the context of TS 31.121 and TS 31.124, the ASME Key is used in test cases that verify the terminal's conformance to the UICC terminal interface. These tests ensure that the terminal correctly processes the security parameters provided by the UICC during authentication, including the handling of the ASME key material. The 'FF' (not available) convention is a common pattern in 3GPP test specifications for indicating optional or absent parameters, and it allows the test suite to cover both the case where the ASME key is present and the case where it is absent.
The ASME Key is therefore a test-oriented representation of the security key material associated with the ASME, used to validate terminal behavior in conformance testing. It is not a key that is transmitted over the air interface; rather, it is a parameter used in the test environment to configure the UICC and verify the terminal's security procedures. Understanding the ASME Key is important for engineers working on UE conformance testing, USIM/ISIM application testing, and the 3GPP security architecture.
Purpose & Motivation
The ASME Key exists within 3GPP test specifications to provide a standardized representation of the security key material associated with the Authentication and Security Management Entity, enabling conformance testing of terminals that interact with USIM and ISIM applications. In the 3GPP security architecture, the ASME is the core network entity responsible for authentication and key derivation, and the terminal must correctly handle the key material provided by the UICC during authentication procedures. Test specifications need a well-defined parameter to represent this key material so that test cases can be written reproducibly and executed across different terminal implementations.
The 'FF' (not available) convention solves the problem of representing the absence of a valid key in a test scenario. Many conformance test cases need to verify how a terminal behaves when security parameters are missing, invalid, or not applicable. By defining a special all-FF value, the specifications provide a clear, unambiguous way to signal 'no key available' without requiring separate parameter definitions for each test case. This improves the consistency and maintainability of the test suite.
The ASME Key also supports the broader goal of 3GPP security standardization: ensuring that terminals from different vendors interoperate securely with UICCs and networks from different vendors. By defining the key length (32 bytes) and the representation of unavailable keys, the specifications ensure that all implementations interpret security parameters in the same way, which is essential for global roaming and interoperability.
What changed in its specifications
The latest release-to-release comparison of specifications that define ASME Key. Each summary describes the whole specification, not only this term.
Rel-19 added harmonized test definitions for FDN, charging, PLMN selection, CSG; RedCap access control tests across EPS, NB-IoT, 5G NR; slice selection conformance clauses; SOR-CMCI test clauses for PDU release; and PLMN selection priority test changes.
Full comparison in TS 31.121 →Rel-19 added test clauses for harmonized cross-RAT cases: DISPLAY TEXT, SMS-PP Data Download, CALL CONTROL, eCall, SMS-PP via DL NAS. Also added proactive UICC tests: SMS via IMS/SGs, Send SS, Open Channel for IMS/NG-RAN.
Full comparison in TS 31.124 →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.
The definition wording changed to '32 byte key, any value', removing the explicit '(not available)' annotation. The change cannot be fully assessed from the available wording, but it appears the specification no longer explicitly states the 'FF' value means 'not available', potentially reflecting a clarification or restructuring of how the key parameter is described.
Defining Specifications
3GPP specifications that define or reference ASME Key, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 31.121 vj00 | UICC Application Test Specification | Rel-19 read |
| TS 31.124 vj00 | USIM Application Toolkit Conformance Testing | Rel-19 read |