Description
The P-TMSI is a cornerstone identity in the 2G GPRS and 3G UMTS packet-switched core network. It is a 32-bit temporary identifier locally assigned by the Serving GPRS Support Node (SGSN) to a UE upon successful attachment to the packet-switched domain or during a routing area update. The primary purpose of the P-TMSI is to serve as a substitute for the permanent International Mobile Subscriber Identity (IMSI) in most signaling messages between the UE and the network, thereby minimizing the exposure of the sensitive IMSI. The P-TMSI is structured to include the identity of the SGSN that allocated it (often via a Network Resource Identifier - NRI part) and a local sequence number. When a UE initiates a signaling procedure like a Routing Area Update (RAU) or Service Request, it typically uses the P-TMSI along with a P-TMSI Signature (a 3-byte authentication token) to identify itself to the network. The receiving SGSN uses the P-TMSI to look up the UE's context in its database. If the context is not found (e.g., because the UE has moved to a new SGSN area), the network may initiate an identity request procedure to retrieve the UE's IMSI. The P-TMSI is reallocated periodically or during specific mobility events to enhance privacy. Its scope is limited to a Routing Area (RA), and it must be updated when the UE moves to a new RA served by a different SGSN. The P-TMSI is tightly linked with the GPRS attach and routing area update procedures and is a key parameter in the security context establishment between the UE and the SGSN.
Purpose & Motivation
The P-TMSI was introduced to address critical security and privacy vulnerabilities associated with transmitting the permanent IMSI over the radio interface. Sending the IMSI in clear text (which was more common in early systems) would allow eavesdroppers to track a subscriber's location and identity. The P-TMSI provides identity confidentiality by ensuring the IMSI is sent very infrequently. It solves the problem of subscriber traceability and reduces the risk of IMSI-catcher attacks. Furthermore, it improves signaling efficiency; using a shorter, locally significant temporary identity is more efficient than transmitting the full IMSI in every message. Its creation was motivated by the development of the packet-switched core for GPRS, which required its own mobility and session management identities separate from the circuit-switched TMSI. The P-TMSI, along with its signature, also provides a mechanism for the network to quickly validate the UE's claim of identity without full authentication every time, speeding up mobility procedures. It addressed the limitations of the earlier systems that lacked robust temporary identity mechanisms for data services.
What changed in its specifications
The latest release-to-release comparison of specifications that define P-TMSI. 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-16 added SR-VCC handover from NR to UTRAN, integrity protection activation, and key set storage. These were the largest feature overviews for TS 25.331.
Full comparison in TS 25.331 →Technology family
Subscriber and device identifiers · User Equipment
- Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
- Phase 2 IMEISV
- R96 TLLI
- R97 P-TMSI
- R98 CTSMSI
- Rel-5 IMPI, IMPU, Temporary Public User Identity
- Rel-8 GUTI, M-TMSI
- Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
- Rel-16 GCI, GLI, Truncated 5G-S-TMSI
- P-TMSI counterpart in another generation: GUTI
“the MME needs to map the RAI, P-TMSI (or TLLI) and the P-TMSI Signature (sent by the SGSN) to create the GUTI and compare it with the stored GUTI.” TS 23.003
- P-TMSI extended by TLLI
“The TLLI to use is built by the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI).” TS 23.003
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 13 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.
Introduced in R97 (release dating of the term; no individual change cited).
P-TMSI handling is specified for the first time in R99: MS and network use of old and new P-TMSI during attach, routing area update and reallocation, plus P-TMSI structure and TLLI derivation.
- “the MS shall use this P-TMSI as new temporary identity for GPRS services and shall store the new P-TMSI.” TS 24.008 v3.20.0
- “P-TMSI can also be implicitly reallocated in the attach or routing area updating procedures.” TS 24.008 v3.20.0
- “A local TLLI is built by a MS which has a valid P-TMSI as follows:” TS 23.003 v3.15.0
P-TMSI handling was extended: the SGSN now allocates the P-TMSI when ATTACH REQUEST includes the IMSI, and P-TMSI storage now covers SIM/USIM and deletion on rejection.
- “When the ATTACH REQUEST includes the IMSI, the SGSN shall allocate the P-TMSI.” TS 24.008 v5.16.0
- “If the new SGSN is not able to extract the NRI from the old P-TMSI, it shall retrieve the address of the default SGSN” TS 23.003 v5.11.0
The MS is now prohibited from issuing another Service request while it is in state GMM-SERVICE-REQUEST-INITIATED.
- “The MS shall not issue another Service request when the MS is in state GMM-SERVICE-REQUEST-INITIATED” TS 24.008 v7.15.0
Rel-8 adds P-TMSI handling for EPS interworking: TIN-based selection and GUTI-to-P-TMSI mapping with NRI bit allocation, plus P-TMSI IE use in GTPv2 context messages and security handling.
- “if the TIN indicates "GUTI" and the MS holds a valid GUTI, the MS NAS shall provide the lower layers with the P-TMSI mapped from the GUTI” TS 24.008 v8.20.0
- “The NRI field is of variable length and shall be mapped into the P‑TMSI starting at bit 23 and down to bit 14.” TS 23.003 v8.21.0
- “If the sending/new node is an SGSN, it shall include RAI IE, P-TMSI IE and P-TMSI Signature IE in the Context Request message.” TS 29.274 v8.12.0
In Rel-9 the UE attaching to an SGSN may map a GUTI into the old P-TMSI IE, with a truncated NAS token in the P-TMSI signature, and the SGSN and MME handle it.
- “it shall include a truncated NAS-token, as defined in subclause 9.1.1, into the P-TMSI signature IE of the Attach Request.” TS 33.401 v9.9.0
- “the MS shall indicate the P-TMSI in the Mobile Identity IE and the RAI in the Old routing area identification IE.” TS 24.008 v9.13.0
- “the NRI length is limited to a maximum of 8 bits to be compatible for the mapping to MME Code within GUTI” TS 23.003 v9.15.0
TS 24.008 adds native and mapped P-TMSI types, and the MS must now include a P-TMSI type IE in the ATTACH REQUEST so the network can tell them apart.
- “the MS shall include P-TMSI type IE with P-TMSI type set to "native P-TMSI".” TS 24.008 v10.16.0
- “Native P-TMSI: a P-TMSI previously allocated by an SGSN.” TS 24.008 v10.16.0
- “the network shall use the P-TMSI type IE to determine whether the mobile identity included in the Mobile identity IE is a native P‑TMSI or a mapped P‑TMSI.” TS 24.008 v10.16.0
P-TMSI handling changed: the MS now sets P-TMSI type to native or mapped in the IDENTITY RESPONSE, and the TS 23.003 mapping and P-TMSI signature filling rules were refined.
- “In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "mapped P-TMSI".” TS 24.008 v11.17.1
- “In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI".” TS 24.008 v11.17.1
- “The UE shall fill the remaining 2 octets of the <P-TMSI signature> according to subclauses 9.1.1, 9.4.1, 10.2.1, or 10.5.1” TS 23.003 v11.9.0
The old P-TMSI is also considered valid until the GMM context marked as detached is released, and the TIN is set to P-TMSI with T3412 stopped after a DRX parameter change.
- “or the GMM context which has been marked as detached in the network is released, and shall not resent the message ATTACH ACCEPT” TS 24.008 v12.15.0
- “the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 if running” TS 24.008 v12.15.0
Paging handling with P-TMSI changed: the MS now responds only if T3346 is running, in ATTEMPTING-TO-UPDATE and with the RAI equal to the stored RAI, and the network now treats old and new P-TMSI as valid after reallocation.
- “upon reception of a paging indication, using P-TMSI, if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE” TS 24.008 v13.13.0
- “upon reception of a paging indication, using P-TMSI, even if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE;” TS 24.008 v13.13.0
The P-TMSI REALLOCATION COMMAND can now carry an optional DCN-ID alongside the new P-TMSI, and the MS stores the DCN-ID with the PLMN code in a non-volatile DCN-ID list.
- “optionally a P-TMSI signature or a DCN-ID or both allocated by the network.” TS 24.008 v14.9.0
- “This message is sent by the network to the MS to reallocate a P-TMSI and optionally assign a DCN-ID.” TS 24.008 v14.9.0
- DCN-ID in P-TMSI Reallocation Command Message TS 24.008CR3009
Paging response service type is now tied to a paging request using P-TMSI, and the GMM state after the reject handling is stated as GMM-DEREGISTERED.
- “the MS receives a paging request using P-TMSI for PS domain from the network in PMM-IDLE mode” TS 24.008 v15.9.0
TS 24.008 now specifies that the MS maps a valid GUTI allocated by an MME into a P-TMSI, clarifying which GUTI is used for the mapped P-TMSI in attach, RAU and lower-layer procedures.
- “If the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS shall map the GUTI into a P-TMSI” TS 24.008 v17.9.0
- “the MS NAS shall provide the lower layers with the P-TMSI mapped from the GUTI” TS 24.008 v17.9.0
- Clarification on GUTI used to map P-TMSI TS 24.008CR3290
Defining Specifications
3GPP specifications that define or reference P-TMSI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 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 33.401 vj20 | EPS Security Architecture | 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.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 |