Description
The International Mobile Subscriber Identity (IMSI) is a critical identifier in GSM, UMTS, LTE, and 5G systems. It is a 15-digit (or shorter) numeric code permanently associated with a subscriber and stored within the SIM (Subscriber Identity Module) or USIM (Universal SIM). Structurally, the IMSI is composed of three parts: the Mobile Country Code (MCC, 3 digits), the Mobile Network Code (MNC, 2 or 3 digits), and the Mobile Subscriber Identification Number (MSIN, 9-10 digits). The MCC and MNC together identify the home PLMN (Public Land Mobile Network) of the subscriber, while the MSIN uniquely identifies the subscriber within that network.
In network operations, the IMSI is used during the initial attach procedure when a mobile device connects to the network. The device sends the IMSI to the serving network element (e.g., MME in LTE, AMF in 5G), which then uses it to query the home network's HSS (Home Subscriber Server) or equivalent database (like AUC) for authentication vectors and subscriber profile data. The authentication process involves the network generating a challenge using a secret key (Ki) associated with the IMSI. For privacy reasons, the IMSI is not transmitted openly frequently; instead, a temporary identifier like TMSI (Temporary Mobile Subscriber Identity) or GUTI (Globally Unique Temporary Identity) is used after initial authentication to avoid IMSI exposure over the air interface.
The IMSI's role extends beyond mere identification. It is the primary key for subscriber data in network databases, linking to subscription details, service profiles, QoS parameters, and security credentials. In mobility management, it helps in tracking area updates and handovers between cells. In session management, it is used to correlate charging records (CDRs) with the correct subscriber account. Its standardized format enables international roaming, as a visited network can identify the subscriber's home network using the MCC/MNC and establish the appropriate roaming agreements and routing.
Purpose & Motivation
The IMSI was created to provide a standardized, globally unique, and permanent identifier for mobile subscribers, solving the problems of subscriber identification and roaming in early analog cellular systems. Before GSM, identifiers were often network-specific, hindering interoperability and international roaming. The IMSI, introduced with GSM, allowed any network worldwide to uniquely identify a subscriber and contact their home network for authentication and service profile retrieval, enabling seamless global mobility.
Its design addresses several key requirements: uniqueness (ensured by the MCC/MNC/MSIN structure), permanence (tied to the subscription, not the device), and security (stored securely on the SIM). The separation of the home network identifier (MCC/MNC) from the subscriber identifier (MSIN) simplifies routing of signaling messages for roaming subscribers. The IMSI is fundamental to the security architecture of cellular networks, as it is linked to the subscriber's secret authentication key (Ki). Without a robust, standardized permanent identity like the IMSI, functions like lawful interception, international roaming billing, and subscriber management would be extremely complex or impossible on a global scale.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the concept of a non-IMSI based SUPI (Subscription Permanent Identifier) was formally introduced, as indicated by the work item for a Dedicated AID for USIM Applications supporting such types. This allowed for subscriber identities that are not derived from the traditional IMSI, while the specification maintained the existing security requirement that any stored IMSI used for reactivation purposes must be kept secure and unreadable.
In Release 17, the specification introduced a procedure for transferring an Alternative IMSI between MMEs. Furthermore, a specific requirement for the removal of the IMSI was deleted from clause 5.2.33, while the core security principle that an IMSI retained in the Mobile Equipment for USIM reactivation must be stored securely and not be readable was maintained.
Explore further
Broader topics and technologies where IMSI plays a role.
Defining Specifications
3GPP specifications that define or reference IMSI, 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 |
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.022 vj00 | ME Personalisation Features for GSM/3G | Rel-19 |
| TS 22.240 vj00 | 3GPP Generic User Profile Requirements | Rel-19 |
| TR 22.944 vj00 | UE Functionality Split Scenarios and Requirements | Rel-19 |
| TR 22.975 v1310 | UMTS Numbering and Addressing Requirements | Rel-4 |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 |
| TS 23.125 v1700 | Flow Based Charging Architecture | Rel-7 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 23.280 vk10 | Common Architecture for Mission Critical Services | Rel-20 |
| TS 23.806 v1700 | Voice Call Continuity between CS and IMS | Rel-7 |
| TS 23.815 v1500 | IMS Charging Implications | Rel-5 |
| TS 23.851 v1600 | Network Sharing Architecture for 3G Systems | Rel-6 |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 25.304 vj00 | UTRA Idle Mode Procedures Specification | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.367 vj00 | Home NodeB Mobility Procedures | Rel-19 |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 25.705 vd00 | UMTS Small Data Transmission Enhancements Study | Rel-13 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TS 29.172 vj00 | EPC LCS Protocol (ELP) specification | Rel-19 |
| TS 29.274 vj50 | GTPv2-C Control Plane Protocol Specification | Rel-19 |
| TS 29.275 vj00 | PMIPv6 Mobility & Tunnelling Protocols Stage 3 | Rel-19 |
| TS 29.276 vj00 | EPS S101/S121/S103 Interfaces Stage 3 | Rel-19 |
| TS 29.277 vj00 | S102 Interface Protocol Specification | Rel-19 |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 |
| TS 31.102 vj40 | USIM Application Specification | Rel-19 |
| TS 31.117 vj10 | USIM Application Toolkit Test for Non-Removable UICC | Rel-19 |
| TS 31.121 vi50 | UICC-terminal interface test specification | Rel-18 |
| TR 31.900 vj00 | 3GPP TS 31.900: Security Interworking Guidance | Rel-19 |
| TS 32.182 vj00 | UDC Common Baseline Information Model (CBIM) | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.276 vj00 | VCS Online Charging from Proxy Function | Rel-19 |
| TS 32.277 vj20 | Charging Management for Proximity Services (ProSe) | Rel-19 |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.849 vd00 | IMS Roaming Charging Study | Rel-13 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |
| TS 33.102 vj10 | 3G Security Architecture Specification | Rel-19 |
| TS 33.105 vj00 | 3G Security: Cryptographic Algorithm Requirements | Rel-19 |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.320 vj00 | H(e)NB Subsystem Security Architecture | Rel-19 |
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 33.820 v1830 | Home NodeB/eNodeB Security Architecture | Rel-8 |
| TS 33.843 vf10 | Security Study for ProSe UE-to-Network Relay | Rel-15 |
| TS 36.304 vj00 | UE Idle Mode Procedures in E-UTRA | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 37.320 vj00 | Minimization of Drive Tests (MDT) Overview | Rel-19 |
| TS 38.304 vj00 | UE RRC_IDLE and RRC_INACTIVE Procedures | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 41.033 ve00 | GSM Lawful Interception Interface Requirements | Rel-14 |
| TS 43.020 vj00 | Security Procedures for GSM | Rel-19 |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |
| TS 51.010 vj00 | SIM Application Toolkit Conformance Testing | Rel-19 |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 |