Description
The Universal Subscriber Identity Module (USIM) is the cornerstone of subscriber security and identity management in 3GPP networks from UMTS (3G) onwards. It is not the physical card itself (that is the UICC) but a dedicated application that runs on the UICC's secure microprocessor. The USIM's primary functions are to securely store the subscriber's unique identity (IMSI), authenticate the subscriber to the network, generate session keys for encryption and integrity protection, and manage subscriber-related data like the phonebook and SMS.
Architecturally, the USIM interacts with the Mobile Equipment (ME) via a standardized interface (ETSI/3GPP TS 31.101). When a device powers on or enters a new network area, the ME requests the International Mobile Subscriber Identity (IMSI) from the USIM. This IMSI is sent to the network to initiate an authentication procedure. The network's Authentication Centre (AuC) generates an authentication vector containing a random challenge (RAND), an expected response (XRES), a ciphering key (CK), and an integrity key (IK). The RAND is sent to the USIM.
The USIM, using a secret key (K) stored securely within it and a cryptographic algorithm (MILENAGE for 3G/4G/5G), computes a response (RES) and the same CK and IK. The ME sends the RES back to the network for verification. If RES matches XRES, authentication is successful. The CK and IK are then used by the device and network to encrypt and integrity-protect all subsequent communications. This process, known as Authentication and Key Agreement (AKA), ensures that only a legitimate subscriber with the correct USIM can access the network and that the communication is secure.
Beyond core authentication, the USIM provides a secure storage area for subscriber data, network selection preferences, and service provider applications (like OTA provisioning). In 5G, the USIM's role evolves to support the 5G AKA protocol and store new identifiers like the Subscription Concealed Identifier (SUCI) for enhanced privacy. It acts as a root of trust, enabling secure bootstrapping for other services and acting as a secure element for mobile commerce and digital identity applications.
Purpose & Motivation
The USIM was introduced with 3G UMTS to address security weaknesses in the 2G SIM (Subscriber Identity Module). The 2G SIM used the COMP128 algorithm, which had known vulnerabilities, and the GSM authentication was one-way (network authenticates the subscriber) with weaker encryption algorithms. The move to 3G required a stronger, mutual authentication mechanism and enhanced cryptographic capabilities to protect new data and multimedia services.
The creation of the USIM provided a standardized, future-proof platform for subscriber identity. It separated the secure application (USIM) from the physical card (UICC), allowing multiple applications (like ISIM for IMS) to coexist. This modularity was crucial for the convergence of services. The USIM's secure execution environment and storage protect the long-term secret key (K) from extraction, forming an immutable root of trust for the entire mobile ecosystem.
Its ongoing evolution is driven by the need for stronger privacy (e.g., SUCI in 5G to protect the IMSI), support for new authentication frameworks (EAP-AKA', 5G AKA), and enabling new use cases like network slicing identification and secure services for IoT. The USIM solves the fundamental problem of securely and portably binding a subscriber identity to a subscription, enabling global roaming, secure service access, and trusted transaction capabilities.
What changed in its specifications
The latest release-to-release comparison of specifications that define USIM. 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-5 added USAT definitions, proactive key press indication, ISIM reference, and removed network-specific bearer and communication control restrictions.
Full comparison in TS 22.038 →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
- USIM counterpart in another generation: SIM
“If a USIM application is present on the UICC, a 3GPP ME shall only use the USIM application regardless of the radio access technology in use. In this case, a possibly existing SIM application shall never be used by a 3GPP ME.” TS 31.102
- USIM used together with ISIM
“If an ISIM is present on the UICC it shall be used to access the IMS.” TS 22.101
- USIM builds on UICC
“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
- USIM extended by MUSIM
“MUSIM UE: An ME with multiple USIMs.” TS 22.101
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 18 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.
The USIM application on the UICC is defined for the first time for 3G network operation, including its files, authentication functions and the UICC/ME application protocol.
- “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 v3.18.0
- “The present document defines the USIM application for 3G telecom network operation.” TS 31.102 v3.18.0
TS 31.102 USIM requirements changed: USIM must execute all TS 31.101 commands without jeopardising service, and new files and procedures (MMS notification, EFECC emergency number handling, MBDN) were added to the USIM.
- “The USIM shall execute all commands defined in TS 31.101 [11], if applicable for the USIM (see section 8.3 for optional commands)” TS 31.102 v4.15.0
- “If EFECC does not contain any valid number, the ME shall use the emergency numbers it stores for use in setting up an emergency call without a USIM.” TS 31.102 v4.15.0
- “If there is no available empty space in the USIM to store the MMS notification, it is up to ME implementation how the notification is handled.” TS 31.102 v4.15.0
TS 31.102 changed USIM application selection behaviour: a 3GPP ME uses only the USIM, the ME may try the GSM application if none is listed, and the 'last selected USIM application' is stored.
- “If a USIM application is present on the UICC, a 3GPP ME shall only use the USIM application regardless of the radio access technology in use.” TS 31.102 v5.15.0
- “This application is referred to as the last selected USIM application.” TS 31.102 v5.15.0
- “the ME may then try to select the GSM application as specified in TS 51.011 [18].” TS 31.102 v5.15.0
Rel-6 added USIM behaviour: new USIM commands for VGCS/VBS short term key derivation and GBA_U bootstrapping and NAF derivation, plus USAT test corrections including REFRESH USIM Application Reset.
- “The USIM computes the Short Term Key (VSTK) associated with a particular VGCS/VBS Group Identifier (Group_Id).” TS 31.102 v6.23.0
- “The USIM then derives and stores GBA_U bootstrapped key material from CK, IK values.” TS 31.102 v6.23.0
- Addition of REFRESH USIM Application Reset TS 31.124CR0058
USIM behaviour was specified for local key establishment: storing Ks_local, returning errors when Ks_int_NAF is missing or unauthorised, and overwriting local keys when memory is full.
- “The USIM uses the NAF_ID to identify the Ks_int_NAF associated to the NAF Key Centre.” TS 31.102 v7.17.0
- “the USIM shall overwrite a Local Key and its associated data in order to store the new one.” TS 31.102 v7.17.0
- Clarification of the USIM behavior when MSK key is not updated TS 31.102CR0322
Rel-8 USIM specification gained new capabilities: eCall numbers and service 89, EFNCP-IP connectivity parameters, call control on EPS PDN connection by USIM, and home (e)NodeB provisioning.
- “eCall support on the USIM is indicated in the service table when service '89' is "available".” TS 31.102 v8.22.0
- “The procedures and commands for Call control on EPS PDN connection by USIM are defined in TS 31.111 [12].” TS 31.102 v8.22.0
- USIM provisioning for home (e)NodeB TS 31.102CR0380
USIM-related test specifications were extended in Rel-9: a new USIM SMS reading test was introduced and test 8.2.1 for Class 2 SM storage on the USIM was split.
- “Introduction of ISIM and USIM related SMS reading test” TS 31.121 v9.6.0
- “Split of test 8.2.1 for independent verification of correct 'Class 2 SM storage on the USIM'” TS 31.121 v9.6.0
USIM gained new Rel-10 capabilities: Communication Control for IMS by USIM procedures, an IARI list in the USIM, and USIM-INI/USIM-RN applications for Relay Nodes.
- “The procedures and commands for Communication Control for IMS by USIM are defined in TS 31.111 [12].” TS 31.102 v10.15.0
- “The USIM applications USIM-INI and USIM-RN are not simultaneously active.” TS 31.102 v10.15.0
- Introduction of the IARI list in the USIM TS 31.102CR0472
USIM specification gained new PWS configuration by USIM and file/FID allocation for Relay Nodes, plus corrections to DFs at the USIM ADF level.
- “PWS configuration by USIM” TS 31.102 v11.12.0
- FID allocation and other corrections to USIM for Relay Nodes TS 31.102CR0512
- Corrections in the clause DFs at the USIM ADF level TS 31.102CR0504
The USIM application gained new Rel-12 capabilities: ProSe usage-reporting and group-communication files, USIM-ME pairing files (EFIWL, EFIPS) with OTA updates, and URI support in USIM services.
- “The use of a USIM can be restricted to specific MEs using the USAT Application Pairing procedure” TS 31.102 v12.13.0
- “The file EFIWL stores ranges of values of IMEI(SV) to which the USIM is authorized to be paired” TS 31.102 v12.13.0
- URI support for USIM Phonebook TS 31.102CR0569
TS 31.102 gained new USIM capabilities in Rel-13: a USIM application dedicated for IOPS, new service table entries and files, and USIM re-initialisation rules when the UICC is deactivated in PSM or extended DRX.
- “Annex M (normative): USIM application dedicated for IOPS” TS 31.102 v13.9.1
- “re-initialize the USIM (as specified in clause 5.1.1) and take appropriate steps to verify that the same USIM is used” TS 31.102 v13.9.1
- “DFACDC shall be present at the ADFUSIM level if service nº108 is "available" in EFUST” TS 31.102 v13.9.1
The USIM permanent key K may now be 128 or 256 bits, a V2X service table file (service n°119) is added, and eCall support allows URIs and Service n°112.
- “This key K has a length of 128 bits or 256 bits and is stored within the USIM” TS 31.102 v14.8.0
- “eCall support on the USIM is indicated in the service table when Service n° 89 or Service n° 112 is "available".” TS 31.102 v14.8.0
The USIM application was extended for 5G: SUCI calculation can be performed by the USIM, and the USIM Service Table gained PDU session call control support and 5GS files.
- “If Service n°124 and Service n°125 are declared "available", the "SUCI calculation is to be performed by the USIM".” TS 31.102 v15.13.0
- USIM Service Table update for PDU session call control support TS 31.102CR0786
- Updates to USIM management procedures for 5GS TS 31.102CR0806
Rel-16 adds a non-IMSI SUPI type USIM (Annex N, dedicated AID ranges, service n°130) and USIM support for URSP and trusted non-3GPP access network lists.
- “Non-IMSI based USIM is a USIM Application which is configured with a SUPI of type non-IMSI” TS 31.102 v16.17.0
- “Both USIM application types shall use different AID ranges as defined in Annex O of TS 31.101 [11].” TS 31.102 v16.17.0
- “Support for URSP by USIM” TS 31.102 v16.17.0
Rel-17 extended the USIM with new files and data for SOR-CMCI, disaster roaming, SNPN PWS configuration, eDRX parameters, 5G NSWO, 5G ProSe and IMEI pairing (EFIAL), plus new related test cases.
- “SOR-CMCI storage in USIM” TS 31.102 v17.18.0
- “Storage of disaster roaming information in USIM” TS 31.102 v17.18.0
- Introduce a USIM file to store pre-configured CAG information list TS 31.102CR0904
TS 31.102 now mandates that USIM Service n°133 be available whenever Service n°123 is available, and adds new USIM files (GBA_U access control, IMS data channel configuration).
- “When Service n°123 is declared "available" then Service n°133 shall also be declared "available".” TS 31.102 v18.11.0
- Add EF of Access Control to GBA_U_APIs to the USIM TS 31.102CR1007
- Add EF of IMS Data Channel configuration to the USIM TS 31.102CR1006
USIM behaviour changed in Rel-19: it is considered invalid until T3245 expires, new 5G ProSe multi-hop policy files were added, and backward compatibility for USIM without extended EF_5GAuthKeys storage was introduced.
- “the USIM shall be considered invalid until switching off the UE, the UICC containing the USIM is removed, or the timer T3245 expires” TS 24.501 v19.8.0
- “If service n°139 is "available" in the USIM Service Table and service n°9 is "available" in EF5G_PROSE_ST, this file shall be present.” TS 31.102 v19.6.0
- Backward compatibility handling of USIM without extended security parameter storage in EF_5GAuthKeys - Rel19 TS 31.102CR1074
Defining Specifications
3GPP specifications that define or reference USIM, 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.022 vj00 | ME Personalisation Features for GSM/3G | Rel-19 read |
| TS 22.038 vj00 | USIM Application Toolkit (USAT) Stage 1 | Rel-19 read |
| TS 22.057 vj00 | Mobile Execution Environment (MExE) Stage 1 | Rel-19 read |
| TS 22.066 vj00 | Mobile Number Portability Stage 1 | 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.105 vj00 | Telecommunication Services Framework | Rel-19 read |
| TS 22.112 v800 | USAT Interpreter for Secure Narrowband Channel | Rel-8 read |
| TS 22.121 v531 | Virtual Home Environment Service Requirements | Rel-5 read |
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 read |
| TR 22.907 v313 | UMTS IC Card and Terminal Concepts | R99 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.975 v310 | UMTS Numbering and Addressing Requirements | R99 read |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 read |
| TS 23.009 vj00 | Handover Procedures in PLMNs | Rel-19 read |
| TS 23.048 v590 | Secured Packets Structure for SMS and UICC Management | Rel-5 read |
| TS 23.050 | 3GPP TS 23.050 | R99 read |
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.101 vj00 | UMTS Architecture and Functional Separation | Rel-19 read |
| TS 23.110 vj00 | Access Stratum Services Specification | Rel-19 read |
| TS 23.127 v610 | Virtual Home Environment Stage 2 Specification | Rel-6 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.228 vk10 | IP Multimedia Core Network Subsystem | Rel-20 read |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 23.804 v710 | SMS/MMS over IP Access Networks | Rel-7 read |
| TS 23.851 v610 | Network Sharing Architecture for 3G Systems | Rel-6 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 read |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 read |
| TS 24.167 vj10 | 3GPP IMS Management Object | Rel-19 read |
| TS 24.186 vk10 | IMS Data Channel and AR Communication | Rel-20 read |
| TS 24.228 v590 | IP Multimedia Call Control Signaling Flows | Rel-5 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.526 vk00 | 5GS UE Policies | Rel-20 read |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 read |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TR 26.967 vj00 | eCall via CTM Suitability Analysis | Rel-19 read |
| TS 27.007 vk00 | AT Command Interface for Mobile Terminals | Rel-20 read |
| TS 29.198 v340 | OSA R99 API Stage 3 Specification | R99 read |
| TS 31.102 vk00 | USIM Application Specification | Rel-20 read |
| TS 31.111 vj40 | 3GPP TS 31111 vj40: USIM Application Toolkit | Rel-19 read |
| TS 31.112 v800 | USAT Interpreter System Architecture and Functionality | Rel-8 read |
| TS 31.113 v800 | USAT Interpreter Byte Codes Specification | Rel-8 read |
| TS 31.114 v800 | USAT Interpreter Transmission Protocol | Rel-8 read |
| TS 31.115 vj00 | Secured Packet Structure for UICC Applications | Rel-19 read |
| TS 31.121 vj00 | UICC Application Test Specification | Rel-19 read |
| TS 31.122 vj00 | USIM UICC Conformance Test Specification | Rel-19 read |
| TS 31.131 vj00 | C Language Binding for (U)SIM API | Rel-19 read |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 read |
| TR 31.901 ve00 | USIM/ISIM/USAT Feature Review Study | Rel-14 read |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | 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.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 read |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | 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.105 vj00 | 3G Security: Cryptographic Algorithm Requirements | 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.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | Rel-19 read |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 read |
| TS 33.820 v830 | H(e)NB Security Threats and Countermeasures | Rel-8 read |
| TS 33.822 v800 | Inter-Access Mobility Security Architecture | Rel-8 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 read |
| TS 34.131 vj00 | SIM API C Language Test Specification | Rel-19 read |
| TS 35.205 vj00 | MILENAGE Algorithm Set: General Overview | Rel-19 read |
| TS 35.234 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TS 35.235 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TR 35.909 vj00 | 3GPP MILENAGE Algorithm Design Report | 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.304 vj30 | LTE UE Idle Mode Procedures | Rel-19 read |