Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Identifier

TMSI

Temporary Mobile Subscriber Identifier

Identifier →

TMSI is a temporary, randomly assigned identifier that replaces the permanent IMSI on the radio interface to enhance subscriber privacy and security by preventing tracking and eavesdropping.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
29 specs
Also in
Core Network, Services, User Equipment, Testing, Management
TMSI Description Purpose What changed Neighbours Specifications

Description

The Temporary Mobile Subscriber Identity (TMSI) is a fundamental privacy and security mechanism in 2G (GSM), 3G (UMTS), and 4G (LTE) mobile networks. It is a temporary, locally significant identifier assigned by the Visited Mobile Switching Center (MSC) in circuit-switched (CS) domains or the Mobility Management Entity (MME) in the packet-switched (PS/EPS) domain to a mobile station or User Equipment (UE) within their area of jurisdiction. The primary purpose of the TMSI is to avoid frequent transmission of the permanent, globally unique International Mobile Subscriber Identity (IMSI) over the radio interface, which would make subscribers easily identifiable and trackable.

The TMSI lifecycle begins when a UE first attaches to a network or enters a new location area (LA) or tracking area (TA). During the initial location update or attach procedure, the UE may need to identify itself using its IMSI. Upon successful authentication, the network (MSC or MME) allocates a new TMSI and sends it to the UE in a secure message, typically encrypted using ciphering keys established during authentication. The UE stores this TMSI in its non-volatile memory. For all subsequent signaling interactions with the network within that area—such as responding to paging, performing periodic updates, or initiating a mobile-originated call—the UE uses the TMSI instead of the IMSI. The network maintains a mapping between the allocated TMSI and the subscriber's IMSI in its local database (VLR or MME context).

The TMSI is structured to be meaningful only within the area controlled by the assigning node and for a limited time. It can be re-assigned periodically (e.g., at each location update) or in specific scenarios like inter-MSC handovers. If a UE cannot present a valid TMSI (e.g., after losing coverage or if the network cannot decode it), the network will request the IMSI in an Identity Request procedure, triggering a new TMSI allocation. In 4G LTE, the concept is extended with the Globally Unique Temporary Identity (GUTI), which includes the MME identifier (GUMMEI) and a temporary identifier (M-TMSI), providing a broader scope. The TMSI mechanism is a cornerstone of mobile network security, working in tandem with authentication, ciphering, and location update procedures to protect subscriber identity confidentiality.

Purpose & Motivation

The TMSI was introduced in early GSM standards to address a critical privacy flaw: the permanent IMSI, which uniquely identifies a subscriber worldwide, was originally sent in clear text over the radio channel for identification. This allowed passive eavesdroppers to easily collect IMSIs, track individuals' movements, and clone subscriptions. The motivation was to provide a level of anonymity for mobile users, a concern that grew with the widespread adoption of cellular technology. TMSI created a essential layer of privacy by ensuring the permanent identity is exposed only during initial network entry or failure scenarios, not during routine communication.

Before TMSI, the lack of a temporary identifier made subscriber traffic easily correlatable and compromised user location privacy. The TMSI mechanism solved this by implementing identity confidentiality. Its design was driven by the need for a lightweight, efficient solution that could be integrated into existing signaling procedures without major overhead. The temporary, local nature of the TMSI means that even if it is intercepted, it cannot be used to identify the subscriber outside that specific network area and time window. This concept was so successful that it was carried forward and enhanced in UMTS and LTE/EPC, forming the basis for more advanced temporary identifiers like the P-TMSI in GPRS and the GUTI in EPS. It addresses the fundamental security requirement of identity protection, which is a prerequisite for trusted mobile communication services.

What changed in its specifications

The latest release-to-release comparison of specifications that define TMSI. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 23.221Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.221: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.221 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Inherited and solidified from GSM. In the UMTS context, TMSI continued as the primary temporary identifier for the circuit-switched domain, with allocation and management procedures defined for the MSC/VLR. Its usage was tightly coupled with authentication and ciphering procedures for secure delivery.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.022 vj00 ME Personalisation Features for GSM/3G Rel-19 read
TR 22.944 vj00 UE Functionality Split Scenarios and Requirements Rel-19 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 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 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.302 vj00 UTRA Physical Layer Services Rel-19 read
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 31.117 vj30 USAT Tests for Non-Removable UICC Rel-19 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.401 vj00 Performance Management Concept & Requirements 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 43.051 vj00 GERAN Stage 2 Service Description Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.901 vj00 Generic Access to A/Gb Interface Feasibility Study Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19 read
TS 44.160 vg00 GERAN Iu Mode RLC/MAC Protocol Specification Rel-16 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read
TS 52.402 vj00 GSM Performance Management Measurements Rel-19 read