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

Glossary term · Identifier

MSISDN

Mobile Station International Subscriber Directory Number

Identifier →

MSISDN is the globally unique public telephone number, following the E.164 format, used to call a mobile subscriber and to route calls and SMS messages.

Introduced
Phase 1
Where
Services › IMS
Specifications
37 specs
Also in
Core Network, Management
MSISDN Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Mobile Station International Subscriber Directory Number (MSISDN) is the primary, internationally standardized identifier for a mobile subscriber within the Public Switched Telephone Network (PSTN) and the Integrated Services Digital Network (ISDN). It follows the ITU-T E.164 numbering plan, comprising a Country Code (CC), a National Destination Code (NDC) which often identifies the mobile network operator, and a Subscriber Number (SN). This number is not stored on the SIM card itself but is a key data element within the subscriber's profile in the Home Location Register (HLR) in GSM/UMTS networks or the Home Subscriber Server (HSS) in LTE/5G networks. The MSISDN is decoupled from the device's hardware identity (IMEI) and the SIM's identity (IMSI), allowing a subscriber to change devices while retaining their number and enabling number portability between operators.

In network operations, the MSISDN is the principal address used for routing mobile-terminated voice calls and SMS messages. When a call is placed to an MSISDN, the originating network queries the appropriate number portability database and then routes the call to the subscriber's home network. The home network's Gateway MSC (GMSC) uses the MSISDN to interrogate the HLR/HSS to obtain the current routing information, specifically the Mobile Station Roaming Number (MSRN) or the IP address of the serving MSC or SMSC. This process enables the call or message to be delivered to the subscriber's current location, whether in the home network or roaming.

The MSISDN's role extends beyond basic circuit-switched services. In the IP Multimedia Subsystem (IMS), the MSISDN can be used as a Public User Identity (IMPU) for SIP-based services like VoLTE and ViLTE, allowing interoperability with legacy PSTN/PLMN users. It is also a critical key for subscriber management, billing, and lawful interception. The separation of the MSISDN from the IMSI provides operational flexibility; for example, a single IMSI (and thus a single subscription) can be associated with multiple MSISDNs for services like voice and fax, or for corporate lines. Its standardized, globally routable format is foundational for global mobile telecommunications.

Purpose & Motivation

The MSISDN was created to provide a standardized, user-friendly, and globally unique addressing scheme for mobile subscribers, analogous to telephone numbers in the fixed network. Prior to cellular standardization, various incompatible radio systems used different identification methods, hindering interoperability and international roaming. The adoption of the E.164-based MSISDN within GSM and subsequent 3GPP technologies solved this by providing a consistent number that users could share and that networks could use for routing calls worldwide.

Its design separates the subscriber's public identity (MSISDN) from their private network identity (IMSI) and equipment identity (IMEI). This separation is crucial for security, privacy, and operational flexibility. It allows for subscriber mobility and number portability without changing the physical SIM card or device. The MSISDN enables the mobile network to interface seamlessly with the global PSTN/ISDN, making the mobile phone a true extension of the worldwide telephone system. It solved the fundamental problem of how to find and route a call to a mobile subscriber whose location is not fixed, by using it as a stable key to query dynamic routing information from the HLR.

What changed in its specifications

The latest release-to-release comparison of specifications that define MSISDN. 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.057Rel-4 → Rel-5

Rel-5 added MExE Classmark 4 for CLI Compact Profile devices, covering architecture, security, charging, and capability negotiation.

Full comparison in TS 23.057 →

Technology family

Subscriber and device identifiers · User Equipment

  1. Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
  2. Phase 2 IMEISV
  3. R96 TLLI
  4. R97 P-TMSI
  5. R98 CTSMSI
  6. Rel-5 IMPI, IMPU, Temporary Public User Identity
  7. Rel-8 GUTI, M-TMSI
  8. Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
  9. Rel-16 GCI, GLI, Truncated 5G-S-TMSI
  • MSISDN extended by GPSI (not stated verbatim in the specifications)

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 sources

Documented 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.

Phase 1 introduced

Introduced in Phase 1 (release dating of the term; no individual change cited).

R99 specification text

TS 23.066 (first appearing in this release) specifies Mobile Number Portability, defining how calls and non-call signalling are routed using the ported MSISDN, with HLR and Number Portability Database handling.

  • “Mobile Number Portability (MNP) is the ability for a UMTS or GSM mobile subscriber to change the subscription network within a portability domain whilst retaining her original MSISDN or MSISDNs.” TS 23.066 v3.3.0
  • “When GMSCB receives the ISUP IAM, it requests routeing information by submitting a MAP SRI to the HLRB including the MSISDN in the request.” TS 23.066 v3.3.0
  • “add an entry in the HLR; delete any entry related to the ported MSISDN in the Number Portability Database.” TS 23.066 v3.3.0
Rel-4 specification text

TS 23.271 first specifies MSISDN as the identifier of the target UE in LCS, used for addressing, routing, HLR lookup and access barring lists, and 33.107 extends MSISDN target identities to CS and GPRS interception.

  • “In the mobile terminated location request procedures in the PS domain (as well as in the CS domain), the target UE is always identified using MSISDN.” TS 23.271 v4.13.0
  • “It shall be possible to address and indicate the target UE using MSISDN.” TS 23.271 v4.13.0
  • “The target identities for 3GMS CS and GPRS interception at the SGSN, GGSN, 3G MSC Server and 3G GMSC Server can be at least on of the following: IMSI, MSISDN or IMEI.” TS 33.107 v4.3.0
Rel-5 1 CR

MSISDN gained new roles in Rel-5: used for MNP database queries and tariff decisions, as a possibly non-dialable callback number for SIM-less emergency calls, and added to downloadable data sets.

  • “In the case of a SIM-less UE making the emergency call, the MSISDN may be populated with a non-dialable callback number” TS 23.271 v5.13.0
  • Add MSISDN to set of Data that may be downloaded TS 29.329CR031
  • “The database query uses the MSISDN received at the application level in the ATI, rather than the CdPA of the SCCP level.” TS 23.066 v5.3.0
Rel-6 1 CR

MSISDN's role as a target identity changed: it can now be used with IMSI to address the target UE in LCS, via pseudonym/verinym and LIMS-IWF retrieval, and its interception use was clarified.

  • “the target UE is identified using either MSISDN or IMSI.” TS 23.271 v6.13.0
  • “The purpose of this interface is to retrieve the user's MSISDN.” TS 23.271 v6.13.0
  • MSISDN/IMEI clarification for GPRS interception TS 33.107CR0034
Rel-7 specification text

In Rel-7, 23.271 adds MSISDN-based emergency-call correlation for E.U. (ISUP/BICC IAM calling party number set to MSISDN), and 33.107 adds MSISDN interception caveats and I-WLAN target identity text.

  • “In E.U. it is provided through the ISUP/BICC IAM message with location number parameter set to MSC number and the calling party number parameter set to MSISDN.” TS 23.271 v7.10.0
  • “Some communication content during a mobility procedure may not be intercepted when interception is based on MSISDN (only PS interception) or IMEI.” TS 33.107 v7.7.0
Rel-8 specification text

Lawful interception requirements now allow MSISDN as a target identity at the EPC nodes (MME, HSS, S-GW, PDN-GW), with notes on its availability in those nodes.

  • “The target identities for interception at the MME, HSS, S-GW and PDN-GW are IMSI, MSISDN and ME (Mobile Equipment) Identity.” TS 33.107 v8.12.0
  • “MSISDN is a possible identity available in the EPC nodes, which may be provided by the HSS to the MME and then forwarded to the S-GW/PDN-GW.” TS 33.107 v8.12.0
  • “Interception in the PDN-GW shall be based on one or more of NAI, MSISDN, IMEI.” TS 33.107 v8.12.0
Rel-9 1 CR

LCS procedures in TS 23.271 now cover EPC: MSISDN or IMSI is used to identify the target UE, and the HLR/HSS returns the current MME alongside SGSN and VMSC/MSC server addresses.

  • “In this scenario, it is assumed that the target UE is identified using an MSISDN or IMSI.” TS 23.271 v9.8.0
  • “The MME shall send a Subscriber Location Report to the GMLC carrying the IMEI and if available the IMSI and MSISDN of the UE” TS 23.271 v9.8.0
  • Clarifications to MSISDN coding TS 29.274CR0417
Rel-10 1 CR

The Sh interface Sh-Update procedure was changed to handle MSISDN, so the MSISDN-related update behaviour of the Sh interface was altered or extended.

Rel-11 1 CR

MSISDN handling changed: the source SGSN/MME may send a Subscriber Location Report carrying the MSISDN after handover, and T4 triggering was addressed for PS-only IMS UEs without an MSISDN.

  • “send a Subscriber Location Report to the source GMLC carrying the UE identity (IMSI, MSISDN and/or IMEI)” TS 23.271 v11.3.0
  • T4 triggering for PS-only IMS UE without MSISDN TS 23.682CR0030
Rel-12 1 CR

SMS over generic 3GPP IP access gained handling for IMS UE to IMS UE messaging without an MSISDN, so the concept's role as the SMS routing identity changed.

  • SMS for IMS UE to IMS UE without MSISDN TS 23.204CR0096
Rel-13 1 CR

In TS 33.107, MSISDN handling as a target identity was extended: E.164 number for optional Non-Local ID was added, and MSISDN-based change reporting and additional MSISDN delivery to DF2 were specified.

  • “IMSI, MSISDN (or E.164 number for optional Non-Local ID) or IMEI.” TS 33.107 v13.8.0
  • “New Observed additional MSISDN (if available)” TS 33.107 v13.8.0
  • SMS w/o MSISDN with removal of Sh interaction TS 23.204CR0108
Rel-14 2 CRs

MSISDN handling changed: CRs add MSISDN to emergency IP-CAN session establishment and define its removal from the HSS subscription profile, and the 33.107 association-change event now carries the old MSISDN.

  • MSISDN as part of IP-CAN session establishment for emergency sessions TS 29.212CR1507
  • Handling of MSISDN removal from subscription profile TS 29.272CR0655
  • “Old MSISDN of the target before a change.” TS 33.107 v14.7.0
Rel-15 1 CR

Lawful interception specification TS 33.107 now lists MSISDN as a target identity at the HSS, SCEF, IWK-SCEF, MME and SGSN, and as a Change Type value in Subscriber Change Records.

  • “The target identities for interception at the HSS, SCEF and IWK-SCEF are IMSI, MSISDN, External Identifier and ME (Mobile Equipment) Identity.” TS 33.107 v15.6.0
  • “The target identities for interception at the MME and SGSN are IMSI, MSISDN, External Identifier.” TS 33.107 v15.6.0
  • Absence of MSISDN in S6n TS 29.336CR0146
Rel-16 2 CRs

Two approved Rel-16 corrections to TS 29.122 address how MSISDN is handled in the specification, a technical correction to the concept's behaviour.

Rel-17 2 CRs

Rel-17 includes CRs that change MSISDN handling: clarified MSISDN coding in the PCO IE (24.008) and removal of Monitoring Events when MSISDN is deleted (29.272).

  • Clarification of coding for MSISDN in the PCO IE TS 24.008CR3305
  • Removal of Monitoring Events when External ID or MSISDN is deleted TS 29.272CR0832
Rel-18 1 CR

A new NEF procedure lets an authorized AF retrieve the UE ID in MSISDN form via the get-msisdn custom operation, subject to authorization and user consent checks with the UDM.

  • “the AF shall send an HTTP POST request message to the NEF targeting the custom operation URI "{apiRoot}/3gpp-ueid/v1/get-msisdn"” TS 29.522 v18.13.0
  • “The NEF shall then respond to the AF with the MSISDN that was received from the UDM.” TS 29.522 v18.13.0
  • Exposing GSPI in MSISDN format based on User Consent TS 29.522CR1346
Rel-19 1 CR

Rel-19 adds MSISDN verification to the Nnef_UEId service and reworks MSISDN retrieval (GetMsisdn) with user consent and authorization handling, including GPSI form of MSISDN under the UEId_retrieval_Ext1 feature.

  • “4.4.32.5 Verify UE ID in the form of MSISDN” TS 29.522 v19.7.0
  • “This procedure may be used only when the operator policy and/or local regulations allow an authenticated and authorized AF to perform MSISDN verification.” TS 29.522 v19.7.0
  • Adding MSISDN verification operation support to Nnef_UEId Service TS 23.501CR5816

Defining Specifications

3GPP specifications that define or reference MSISDN, 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.066 vj00 Mobile Number Portability Stage 1 Rel-19 read
TS 22.085 vj00 Closed User Group (CUG) Supplementary Service Rel-19 read
TR 22.949 vj00 Privacy Requirements Study for 3GPP Services Rel-19 read
TS 23.039 v500 SMSC to SME Interface Protocols Rel-5 read
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19 read
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 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.863 vc00 MSISDN-less SMS over IMS Rel-12 read
TR 23.976 vj00 Push Service Requirements Analysis Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.333 vj00 ProSe Management Objects for UE Configuration Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 29.204 vj00 SS7 Security Gateway Functional Description Rel-19 read
TS 29.274 vk00 GTPv2-C Control Plane Protocol Rel-20 read
TS 32.182 vj00 UDC Common Baseline Information Model (CBIM) 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.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.276 vj00 VCS Online Charging from Proxy Function Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.849 vd00 VoLTE Roaming Charging Scenarios Rel-13 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.843 vf10 Security Study for ProSe UE-to-Network Relay Rel-15 read
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14 read