MSISDN

Mobile Station International Subscriber Directory Number

Identifier →
Introduced in R99 Also in: Core Network

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.

Category
Identifier
Introduced
R99
Where
Services › Codecs
Also touches
1 segments
Specifications
37 specs
MSISDN Description Purpose Related Classification 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.

Classification

Related approachesIMSIMSRNHLR

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (16 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 7 changes

In Release 15, the MSISDN function was updated through corrections to the Stage 2 "Subscriber Record Change" event procedures for the HLR in the CS and PS domains, as well as for the HSS in the EPS. These changes clarified and corrected the signaling mechanisms for updating subscriber directory number information in the core network.

  • Clause 5, Figure 5.1.7 Object names, number of occurrences, and structure corrections TS 24.333CR0054
  • Stage 2 Corrections to the Subscriber Record Change event by HLR for CS TS 33.107CR0288
  • Stage 2 Corrections to the Subscriber Record Change event by HLR for PS TS 33.107CR0289
  • Stage 2 Corrections to the Subscriber Record Change event by HSS for EPS TS 33.107CR0290
  • Clarification on the number of coordinates in a geographical area TS 24.333CR0063
  • CP-190170 clause numbers updated after information provided by RAN2 "See clauses 22.3.6.2 and 22.3.6.3 of 3GPP TS 36.300 [19]." TS 29.274

+ 1 more changes

Rel-16 2 changes

In Release 16, there were no specific, documented changes to the core MSISDN function itself. The provided Change Request titles and grounding context do not describe any modifications to the definition, handling, or procedures related to the MSISDN (Mobile Station International Subscriber Directory Number). The release included other updates, such as the addition of new general abbreviations, but these were not directly associated with the MSISDN.

  • Add new general abbreviations MCC Note: CR cover sheet wrongly shows CR number as "1118". TS 21.905CR0118
  • Sequence Number in RAB Context TS 29.274CR1959
Rel-17 4 changes

In Release 17, the changes to the MSISDN function were procedural and presentational, focusing on specification corrections rather than introducing new capabilities. Specifically, the release included corrections to reference numbers, section numbering, and GTPv2 Information Element octet numbering within the relevant technical documents. Furthermore, a procedure titled "Transferring Alternative IMSI between MMEs" was addressed, indicating updates to mobility management signaling related to subscriber identifiers.

  • Transferring Alternative IMSI between MMEs TS 29.274CR2048
  • Correct the reference number TS 29.274CR2051
  • Missing section number correction TS 32.240CR0441
  • GTPv2 IE with wrong octet numbering TS 29.274CR2009
Rel-18 3 changes

In Release 18, the primary update to the MSISDN function was the introduction of a procedure for MSISDN transfer during Inter-MME/AMF mobility specifically for Lawful Interception purposes. This enhancement ensures the continuity of interception when a subscriber's mobile station moves between these core network nodes. No other changes to the fundamental definition or handling of the Directory Number itself were specified in this release.

  • MSISDN transfer during Inter-MME/AMF mobility for Lawful Interception TS 29.274CR2070
  • Correct the instance number of the AMF Identifier TS 29.274CR2085
  • Rejection cause if the number of UEs in the network slice has been exceeded TS 29.274CR2103

Explore further

Broader topics and technologies where MSISDN plays a role.

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 vj00 3GPP Technical Terms and Definitions Rel-19
TS 22.066 vj00 Mobile Number Portability Stage 1 Rel-19
TS 22.085 vj00 Closed User Group (CUG) Supplementary Service Rel-19
TR 22.949 vj00 Privacy Requirements Study for 3GPP Services Rel-19
TS 23.039 v1400 SMSC to SME Interface Protocols Rel-5
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.863 vc00 SMS over IMS for MSISDN-less UEs Rel-12
TR 23.976 vj00 Push Service Requirements Analysis Rel-19
TS 24.206 v1700 Voice Call Continuity Between CS and IMS Rel-7
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19
TS 24.333 vj00 ProSe Management Objects for UE Configuration Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 26.501 vj30 5G Media Streaming (5GMS) Architecture Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 29.204 vj00 SS7 Security Gateway Functional Description Rel-19
TS 29.274 vj50 GTPv2-C Control Plane Protocol Specification 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.251 vj00 PS Domain Charging Management 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.808 v1800 Common User Profile Storage Framework Rel-8
TS 32.849 vd00 IMS Roaming Charging Study Rel-13
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 33.843 vf10 Security Study for ProSe UE-to-Network Relay Rel-15
TS 41.033 ve00 GSM Lawful Interception Interface Requirements Rel-14