AID

Application Identifier

Identifier →
Introduced in Rel-4 Also in: Services, User Equipment

AID is the Application Identifier, a standardized code used to uniquely identify and manage specific applications, like a USIM, on a UICC/SIM card, enabling multiple secure applications to coexist.

Category
Identifier
Introduced
Rel-4
Where
Testing
Also touches
2 segments
Specifications
12 specs
AID Description Purpose Related Classification Detected Changes Specifications

Description

The Application Identifier (AID) is a fundamental component in the UICC (Universal Integrated Circuit Card) and SIM card ecosystem, defined by ISO/IEC 7816-4 and adopted by 3GPP for telecommunications applications. An AID consists of two parts: a Registered Application Provider Identifier (RID) and a Proprietary Application Identifier Extension (PIX). The RID is a 5-byte value assigned by ISO to identify the application provider, while the PIX is up to 11 bytes defined by the provider to identify specific applications. This hierarchical structure ensures global uniqueness while allowing providers flexibility in organizing their applications.

In 3GPP systems, AIDs are primarily used to identify the USIM (Universal Subscriber Identity Module) application on UICC cards. The standard AID for USIM is defined as 'A0000000871002FF...' where 'A000000087' identifies the telecommunications industry, '10' indicates the application family (GSM/UMTS applications), and subsequent bytes specify the USIM application. When a mobile device initializes communication with a UICC, it sends a SELECT command with the AID to activate the specific application. The UICC responds with the application's capabilities and available files.

The AID mechanism enables multiple applications to coexist on a single UICC card, including USIM, ISIM (for IMS), and various value-added services. Each application maintains its own file system and security domain, isolated from others. During card personalization, the AID is used to create the application's dedicated file structure. During operation, the terminal uses AIDs to navigate between applications, with the currently selected AID determining which application's files and commands are accessible. This architecture supports the multi-application capability essential for modern UICCs.

Beyond basic identification, AIDs play a critical role in security and application management. They enable secure channel establishment between the terminal and specific applications, with cryptographic keys and security policies associated with each AID. In remote application management (OTA), AIDs are used to target specific applications for updates, enabling operators to modify or add services without physical card replacement. The standardized AID structure ensures interoperability across different card manufacturers, mobile devices, and network operators worldwide.

Purpose & Motivation

The AID was created to solve the fundamental problem of application identification and selection in multi-application smart cards, which became essential as UICC/SIM cards evolved from simple authentication modules to platforms hosting multiple services. Before standardized AIDs, application selection was proprietary and inconsistent, making interoperability between different card manufacturers and mobile devices difficult. The ISO/IEC 7816-4 standard, adopted by 3GPP, provided a universal addressing scheme that enabled the coexistence of telecommunications applications alongside other services on a single card.

As mobile networks evolved from GSM to UMTS and LTE, the need for multiple applications on UICC cards grew significantly. The USIM application for 3G/4G authentication, ISIM for IMS services, and various value-added applications all needed to reside on the same physical card. The AID system provided a standardized way to identify, select, and manage these applications without conflicts. This was particularly important for global roaming, where a subscriber's UICC must work with different network operators' equipment worldwide.

The hierarchical structure of AID (RID + PIX) addressed both global uniqueness requirements and provider flexibility needs. By having ISO manage the RID assignments, conflicts between different application providers were avoided. Meanwhile, the PIX allowed providers to organize their own application families and versions. This balanced approach enabled the explosive growth of UICC-based services while maintaining backward compatibility with existing systems and ensuring future extensibility for new applications.

Classification

Specific typesUSIMISIM
Related approachesOTA

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the specification update specifically concerned the Application Identifier (AID) for Intelligent Transport Systems. The change involved updating the normative reference for the ITS-AID (Intelligent Transport Systems Application Identifier).

  • Update reference for ITS-AID TS 23.285CR0049
Rel-16 1 change

In Release 16, a new, dedicated Application Identifier (AID) was introduced specifically for USIM applications that are based on a non-IMSI Subscription Permanent Identifier (SUPI). This change provided a distinct means to identify and select these particular USIM applications, differentiating them from traditional IMSI-based applications.

  • Dedicated AID for USIM Applications with non-IMSI based SUPI Types TS 31.102CR0897

Explore further

Broader topics and technologies where AID plays a role.

Defining Specifications

3GPP specifications that define or reference AID, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.285 vj00 V2X Architecture Enhancements for LTE Rel-19
TS 23.286 vj00 V2X Application Enabler Architecture Rel-19
TS 23.287 vj00 5G V2X Architecture Enhancements Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 31.103 vj00 ISIM Application Specification Rel-19
TS 31.105 vj10 Slice Subscriber Identity Module (SSIM) Application Rel-19
TS 31.213 vi30 Test specification for (U)SIM Rel-18
TR 31.822 vi10 Technical Report on GBA_U based APIs Rel-18
TS 31.829 vd00 ISIM Conformance Requirements Technical Report Rel-13
TS 34.131 vj00 SIM API C Language Test Specification Rel-19
TS 51.013 vj00 SIM API for Java Card Test Specification Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.