Description
The Universal Integrated Circuit Card (UICC) is a tamper-resistant smart card used in mobile devices to securely store subscriber identity information and network access credentials. It is the foundational element for user authentication and authorization in 3GPP networks. The UICC typically contains one or more applications, with the Universal Subscriber Identity Module (USIM) being the most common for 3G/4G/5G networks. Other applications may include the IP Multimedia Services Identity Module (ISIM) for IMS services, the CDMA Subscriber Identity Module (CSIM), and payment or ticketing applications.
The UICC is a physical device that can be inserted and removed from the terminal equipment (e.g., a mobile phone) or embedded inside the terminal (e.g., eUICC or eSIM). It provides a secure execution environment for applications and stores sensitive data such as the International Mobile Subscriber Identity (IMSI), authentication keys (e.g., K), and network-specific parameters. The UICC interfaces with the terminal via a standardized electrical interface, and communication is governed by protocols defined in 3GPP specifications (e.g., TS 31.102 for USIM, TS 31.101 for UICC-terminal interface).
In operation, when a UE attaches to a network, the USIM application on the UICC participates in the authentication and key agreement (AKA) procedure. The network sends a random challenge (RAND) and an authentication token (AUTN) to the UE. The USIM computes a response (RES) and a cipher key (CK) and integrity key (IK) using the stored secret key K and the AKA algorithm. The network verifies the RES to authenticate the subscriber and uses CK/IK for subsequent ciphering and integrity protection. This ensures that only legitimate subscribers with a valid UICC can access the network.
The UICC also supports over-the-air (OTA) provisioning, allowing operators to update applications, parameters, and credentials remotely. This is managed via the Remote File Management (RFM) and Remote Application Management (RAM) procedures defined in 3GPP TS 31.116 and TS 31.115. The UICC can also host multiple profiles (e.g., for different operators) in the case of eUICC, enabling dynamic switching between subscriptions.
Security is paramount for the UICC. It employs hardware-based security measures to protect against physical and logical attacks. The card's operating system enforces access control policies, and cryptographic operations are performed within the secure element. The UICC also supports secure channels for OTA updates, ensuring that only authorized entities can modify its content. Overall, the UICC is a critical component for secure and reliable mobile communications, forming the root of trust for subscriber authentication and service access.
Purpose & Motivation
The UICC was created to provide a secure, portable, and standardized means of storing subscriber credentials and applications. Before the UICC, early mobile systems (e.g., 1G) used simple identity modules with limited security. The introduction of the UICC in 3GPP Release 2 (as part of GSM Phase 2) addressed the need for robust authentication, roaming, and value-added services. It allowed subscribers to easily move their identity between devices by simply swapping the card, and it enabled operators to remotely manage subscriptions.
The UICC solves several critical problems: it provides a tamper-resistant environment for cryptographic keys, preventing cloning and fraud; it enables global roaming by standardizing the interface and procedures; and it supports multiple applications, allowing a single card to serve various services (voice, data, IMS, etc.). The evolution to embedded UICC (eUICC) in later releases (e.g., Rel-13 and beyond) addressed the need for smaller devices (e.g., IoT) and remote provisioning, eliminating the need for a physical card slot.
Over time, the UICC has evolved to support new generations of networks (4G, 5G) and new services (e.g., 5G authentication with SUCI). It remains a cornerstone of mobile security and will continue to adapt to emerging requirements such as network slicing and IoT.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Solving ambiguities on whether to consider UEs without UICC TS 23.402CR2978
- Emergency ePDG selection for UE without UICC TS 23.402CR2986
- Emergency ePDG selection for UE without UICC TS 24.302CR0656
- Corrections of errors in emergency PDU session establishment by UE without valid UICC using SCM in TWAN TS 24.302CR0659
- No UE configuration parameters for connectivity to ePDG by UICC TS 24.302CR0675
Defining Specifications
3GPP specifications that define or reference UICC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 21.111 vj00 | USIM and UICC Requirements for 3G | Rel-19 |
| TS 21.133 v1410 | 3G Security: Threat Analysis & Requirements | Rel-5 |
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 |
| TS 22.100 v1370 | UMTS Service Requirements for Release '99 | Rel-4 |
| TS 22.101 vk00 | Service Principles for PLMNs | Rel-20 |
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 |
| TS 22.800 v1600 | IMS Subscription Scenarios Analysis | Rel-6 |
| TR 22.944 vj00 | UE Functionality Split Scenarios and Requirements | Rel-19 |
| TR 22.967 vj00 | eCall Emergency Data Transmission | Rel-19 |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 |
| TS 23.402 vj00 | EPC for Non-3GPP Access (PMIP) | Rel-19 |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 |
| TS 24.186 vk10 | IMS Data Channel and AR Communication | Rel-20 |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 |
| TS 24.234 vc20 | 3GPP-WLAN Interworking Network Selection | Rel-12 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 24.514 vj30 | Ranging & Sidelink Positioning in 5GS | Rel-19 |
| TS 27.007 vk00 | AT Command Interface for Mobile Terminals | Rel-20 |
| TS 31.122 vj00 | USIM UICC Conformance Test Specification | Rel-19 |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 |
| TS 32.140 vj00 | Subscription Management (SuM) requirements | Rel-19 |
| TS 32.141 vj00 | Subscription Management (SuM) Architecture | Rel-19 |
| TS 32.181 vj00 | User Data Convergence Management Framework | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 |
| TS 33.402 vj00 | Security for non-3GPP access to EPS | Rel-19 |
| TS 33.701 vj00 | Study on mitigations against bidding down attacks | Rel-19 |
| TS 33.820 v1830 | Home NodeB/eNodeB Security Architecture | Rel-8 |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 |
| TR 33.848 vi00 | Technical Report on Virtualisation Security | Rel-18 |
| TS 33.859 vb10 | UTRAN Key Hierarchy Enhancement Study | Rel-11 |
| TS 34.109 vj00 | UE Conformance Test Functions for UMTS | Rel-19 |
| TS 35.234 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 |
| TR 35.934 vj00 | Tuak algorithm set for 3GPP auth & key gen | Rel-19 |
| TR 35.937 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 |