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.
What changed in its specifications
The latest release-to-release comparison of specifications that define UICC. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.
Full comparison in TS 22.101 →Technology family
Subscriber identity modules · User Equipment › SIM/USIM
- Phase 1 IC card SIM, ID-1 SIM, Plug-in SIM, SIM
- R96 proactive SIM, SAT
- R99 UICC, USAT, USIM
- Rel-5 ISIM
- Rel-17 MUSIM
Also in this family (introduction release not pinned to a single defining specification): eSIM, eUICC
- UICC extended by eUICC
“NOTE 1: The UICC refers to either a physically distinct module, or to an embedded eUICC (e..g as defined in [62], [63]).” TS 22.101
- UICC extended by USIM
“The present document defines the Universal Subscriber Identity Module (USIM) application. This application resides on the UICC, an IC card specified in TS 31.101 [11].” TS 31.102
- UICC extended by ISIM
“The present document defines the IM Services Identity Module (ISIM) application. This application resides on the UICC, an IC card specified in TS 31.101 [3].” TS 31.103
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 17 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.
Release 99 specs first define the UICC as the card hosting USIM and its proactive/USAT interface with the ME, including data download, events, bearer independent protocol and conformance testing.
- “Proactive UICC gives a mechanism whereby the UICC can initiate actions to be taken by the ME.” TS 31.111 v3.14.0
- “A proactive UICC shall not send any command requests (status bytes SW1 SW2 = '91 XX') to a mobile that does not support the proactive UICC feature.” TS 31.111 v3.14.0
- “The present document provides the Conformance Test Specification for a Universal IC Card (UICC) defined in 3G TS 31.101 [2]” TS 31.122 v3.10.0
TS 31.111 v4h0 now defers generic UICC toolkit behaviour to ETSI TS 102 223 and adds USAT-specific rules for UICC responses to SMS download, call control, SEND SS/USSD and ME handling of UICC data.
- “The present document refers in its majority to the ETSI TS 102 223 [32], which describes the generic aspects of application toolkits within the UICC.” TS 31.111 v4.17.0
- “if the UICC responds with '93 00', the ME shall either retry the command or send back an RP-ERROR message” TS 31.111 v4.17.0
- “the content supplied by the UICC for onward transmission by the ME shall not be altered by the ME.” TS 31.111 v4.17.0
UICC call control behaviour was extended: the ME must follow UICC responses to ENVELOPE (CALL CONTROL) for PDP context activation, including modified requests beyond ME capabilities, and UICC-ME interface scope was updated.
- “if the PDP Context Activation data is changed by call control, then the ME shall activate the PDP context using the data given by the UICC” TS 31.111 v5.12.0
- “It is mandatory for the ME to perform the PDP Context Activation in accordance with the data from the UICC” TS 31.111 v5.12.0
UICC behaviour and ME-UICC interaction changed in Rel-6, including a new UICC terminal profile service, specified ME handling of UICC status codes for MMS/USSD, and a requirement for a higher UICC/terminal interface speed.
- “If the UICC indicates the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM Service Table, the ME shall handle the profile download procedure” TS 31.111 v6.15.0
- Requirement for higher UICC/Terminal interface speed TS 31.101CR0029
- “The UICC shall be targeted using the following application identifier: "uicc.3gpp.org".” TS 31.111 v6.15.0
TS 31.111 USAT changed UICC proactive behaviour, adding profile download after UICC activation, an I-WLAN parameter list and the application identifier "uicc.3gpp.org" to address the UICC.
- “If the UICC indicates the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM Service Table, the ME shall handle the profile download procedure” TS 31.111 v7.17.0
- “the UICC shall be targeted using the following application identifier: "uicc.3gpp.org".” TS 31.111 v7.17.0
- “The UICC provides to the ME a list of parameters necessary to activate a I-WLAN service.” TS 31.111 v7.17.0
UICC–terminal interface specs extended for E-UTRAN/EPS: UICC can now control EPS PDN connection activation, request geographical location, and presence detection tests were added for E-UTRAN/EPC.
- “It is mandatory for the ME to perform the EPS PDN Connection Activation in accordance with the data from the UICC, if it is within the ME's capabilities to do so.” TS 31.111 v8.15.0
- “allows the UICC to request and receive the current geographical location information from the ME when the ME is equipped with a positioning feature” TS 31.111 v8.15.0
- Definition of the UICC presence detection test when connected to E-UTRAN/EPC TS 31.121CR0131
Terminal-UICC behaviour was extended: ME must report CSG cell selection events and CSG ID lists to the UICC, and must not send call control ENVELOPE for emergency PDP/EPS PDN activations.
- “the ME shall inform the UICC that it has occurred, using ENVELOPE (EVENT DOWNLOAD – CSG Cell Selection) as defined below.” TS 31.111 v9.12.2
- “When the ME performs an emergency EPS PDN connection activation, the ME shall not send the ENVELOPE (CALL CONTROL) command to the UICC.” TS 31.111 v9.12.2
UICC gained new behaviour for IMS access in Rel-10: opening and closing BIP channels for IMS, handling failure responses, and controlling SIP INVITE through call control.
- “the UICC may attempt to open a channel to communicate with the IMS.” TS 31.111 v10.17.0
- “In case of OPEN CHANNEL for IMS, the UICC shall send a CLOSE CHANNEL command to close the BIP channel” TS 31.111 v10.17.0
- “The UICC sends an Open Channel for IMS proactive command upon reception of this ENVELOPE command.” TS 31.111 v10.17.0
TS 31.111 changed UICC-related behaviour: UICC must authenticate PoR senders, SMS-PP download RP-ACK handling for '6F XX'/'62 XX'/'63 XX' was revised, and H(e)NB IP address and macrocell terminal responses were added.
- “the UICC shall verify the authenticity of the sender. If the authentication of the sender fails, no further processing related to the Proof of Receipt shall take place.” TS 31.111 v11.14.0
- “if the UICC responds with '90 00' or '6F XX' or '62 XX' or '63 XX', the ME shall acknowledge the receipt of the short message” TS 31.111 v11.14.0
- “Where the UICC has requested the H(e)NB IP address, the TERMINAL RESPONSE shall contain the list of all IP addresses available” TS 31.111 v11.14.0
UICC behaviour changed: ProSe usage information reporting via BIP was added, with the UICC storing and transmitting reports to the ProSe Function CTF, and the UICC-related proactive command text was updated.
- “A UICC supporting the "ProSe usage information reporting" shall also support BIP.” TS 31.111 v12.12.0
- “The UICC shall store the received ProSe usage information until a USAGE_INFORMATION_REPORT_LIST_RESPONSE is received” TS 31.111 v12.12.0
- “the ME shall perform a GBA bootstrapping procedure (as defined in TS 31.102 [14] or TS 31.103 [62]).” TS 31.111 v12.12.0
UICC-related behaviour changed: new UICC interactions for IMS communication control, WLAN identifier reporting, URI truncation, plus polling interval aligned with eDRX cycle.
- “the ME shall first pass the corresponding IMS Request-URI contained in SIP INVITE message (see TS24.229 [52]) to the UICC” TS 31.111 v13.8.0
- “Where the UICC has requested the WLAN Identifier, the TERMINAL RESPONSE shall contain the SSID, the BSSID when available” TS 31.111 v13.8.0
- Alignment of UICC polling interval with eDRX cycle TS 31.101CR0083
Rel-14 adds UICC suspension (SUSPEND UICC command) so the ME may suspend the UICC in PSM and must resume it before leaving PSM, plus non-removable UICC usage and related test cases.
- “If the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC after entering the PSM.” TS 31.121 v14.6.0
- Introduction of SUSPEND UICC command TS 31.101CR0089
- Usage of non-removable UICC TS 31.101CR0088
Rel-15 changed UICC behaviour: the UICC can request modification of PDU session establishment parameters via call control, and routing indicator data in the UICC can be updated by the UDM.
- “the response data from the UICC shall indicate to the ME whether to send the PDU Session Establishment Request message as proposed” TS 31.111 v15.13.0
- Enable procedure for update of Routing ID data in the UICC, as triggered by the UDM. TS 31.111CR0706
- Introduction of UICC interface during MICO TS 31.102CR0839
Rel-16 UICC test specifications were corrected and extended: NG-RAN UICC definition corrected and separated from NG-RAN ISIM-UICC, and the default 5G-NR UICC non-IMSI SUPI type corrected.
- Separation of NG-RAN UICC and NG-RAN ISIM-UICC TS 31.124CR0695
- Correction of default 5G-NR UICC non-IMSI SUPI Type TS 31.121CR0497
- “Where the UICC has requested the list of slice(s) information, the TERMINAL RESPONSE shall contain the slices information data object” TS 31.111 v16.11.0
Rel-17 adds UICC support for 5G ProSe usage information reporting, with the UICC storing reports and sending them to the 5G DDNMF CTF (ADF) over BIP.
- “The UICC is responsible for communicating those reports to the 5G DDNMF CTF (ADF) using BIP mechanism.” TS 31.111 v17.14.0
- “The UICC shall store the received 5G ProSe usage information until a USAGE_INFORMATION_REPORT_LIST_RESPONSE is received” TS 31.111 v17.14.0
- Correction that UE needs to wait for UICC to reply to network TS 23.122CR0928
Rel-18 extends UICC/terminal behaviour: TERMINAL RESPONSE for PROVIDE LOCAL INFORMATION gains a 'More data' mechanism for slice information, and a new service is added for UICC 5G ProSe usage reporting.
- “UICC shall include More Data tag if ME indicates more data is available in the buffer in the prior TERMINAL RESPONSE.” TS 31.111 v18.12.0
- “In the event the UICC provides an incorrect data index, which is different from the value provided by the ME in the prior TERMINAL RESPONSE” TS 31.111 v18.12.0
- Adding service for UICC 5G ProSe direct communication usage information reporting TS 31.102CR1048
UICC-related requirements changed in Rel-19: the TERMINAL RESPONSE for slice information now carries associated DNN lists, and the UICC and ME gain new test conditions for UICC suspension and Bearer Independent Protocol timer handling.
- “Where the UICC has requested the list of slice(s) information, the TERMINAL RESPONSE shall contain the Serving PLMN served S-NSSAIs list and its associated DNN(s) list” TS 31.111 v19.4.0
- “if the UICC attempts to resend OPEN CHANNEL command before the expiration of timer T the ME shall reply again to the UICC” TS 31.111 v19.4.0
- Addition of default settings of UICC and USIM for UE-to-UE relay TS 38.508-1CR3818
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 read |
| TS 21.133 v410 | 3G Security: Threat Analysis & Requirements | Rel-4 read |
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.100 v370 | UMTS Service Requirements for Release '99 | R99 read |
| TS 22.101 vl00 | 3GPP Service Principles for PLMNs | Rel-21 read |
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 read |
| TS 22.800 v600 | IMS Subscription Scenarios Analysis | Rel-6 read |
| TR 22.944 vj00 | UE Functionality Split Scenarios and Requirements | Rel-19 read |
| TR 22.967 vj00 | eCall Emergency Data Transmission | Rel-19 read |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 read |
| TS 23.402 vj00 | EPC for Non-3GPP Access (PMIP) | Rel-19 read |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 read |
| TS 24.186 vk10 | IMS Data Channel and AR Communication | Rel-20 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 read |
| TS 24.234 vc20 | 3GPP-WLAN Interworking Procedures | Rel-12 read |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 read |
| TS 24.514 vj30 | Ranging & Sidelink Positioning in 5GS | Rel-19 read |
| TS 27.007 vk00 | AT Command Interface for Mobile Terminals | Rel-20 read |
| TS 31.122 vj00 | USIM UICC Conformance Test Specification | Rel-19 read |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 read |
| TS 32.140 vj00 | Subscription Management (SuM) requirements | Rel-19 read |
| TS 32.141 vj00 | Subscription Management (SuM) Architecture | Rel-19 read |
| TS 32.181 vj00 | User Data Convergence Management Framework | Rel-19 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 read |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.402 vj00 | Security for non-3GPP access to EPS | Rel-19 read |
| TS 33.701 vj00 | Study on mitigations against bidding down attacks | Rel-19 read |
| TS 33.820 v830 | H(e)NB Security Threats and Countermeasures | Rel-8 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TR 33.848 vi00 | Technical Report on Virtualisation Security | Rel-18 read |
| TS 33.859 vb10 | UTRAN Key Hierarchy Study | Rel-11 read |
| TS 34.109 vj00 | UE Conformance Test Functions for UMTS | Rel-19 read |
| TS 35.234 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TR 35.934 vj00 | Tuak algorithm set for 3GPP auth & key gen | Rel-19 read |
| TR 35.937 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |