MSN

Multiple Subscriber Number

Services →
Introduced in Rel-8

MSN is a service feature allowing a single IMS subscription or device to be assigned multiple directory numbers, enabling distinct identities like separate business and personal numbers on one device.

Category
Services
Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
MSN Description Purpose Related Classification Detected Changes Specifications

Description

Multiple Subscriber Number (MSN) is a service capability that allows a single subscriber identity (linked to an IMSI or IMS Public User Identity) to be associated with more than one E.164 directory number (MSISDN). Architecturally, this involves coordination between the HSS/UDM, which stores the association of multiple MSISDNs to a single user profile, and the Telephony Application Server (TAS) or other service logic in the IMS core. When a call is placed to one of the MSNs, the network (e.g., the MSC Server for circuit-switched or the IMS core for IP-based calls) uses signaling information, like the Called Party Number, to identify the target MSISDN. It then queries the HSS/UDM to resolve this MSISDN to the corresponding subscriber's IMSI or IMPU. The key technical mechanism is the mapping and routing logic that treats each MSISDN as a separate addressable endpoint that ultimately resolves to the same physical or logical user equipment. Service logic on the TAS can be tailored per MSISDN; for instance, different call forwarding rules, voicemail greetings, or charging rates can be applied depending on which number was called. In the IMS context, each MSISDN is typically associated with a distinct Tel URI (e.g., tel:+1234567890), and these may be implicitly or explicitly registered as Public User Identities linked to the same private user identity and service profile. This allows the network to present the appropriate identity (the called number) to the called party and to apply service logic specific to that 'line' or identity.

Purpose & Motivation

The MSN service was developed to meet the demand for a single device to support multiple telephony identities for different roles or contexts, such as separate numbers for personal life, work, and fax line. Before such a standardized feature, users had to carry multiple devices or SIM cards. The problem it solves is identity management and service differentiation on a single subscription. It allows operators to offer flexible service packages where a user can have distinct billing, call routing, and supplementary services (like voicemail) for each number, all billed to a single account. Its creation was motivated by business user needs and the evolution towards converged services. It provides a network-centric solution for multi-identity management, which is more seamless than relying on device-side applications or multiple SIMs, and integrates cleanly with existing network routing and service control infrastructure.

Classification

Part ofMSISDN
Related approachesIMSIIMPU

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 1 change

In Release 15, the MSN function was enhanced through a correction to the interworking of the Redirecting Number. This update specifically refined the mapping procedures for non-E.164 numbers, such as local numbers with a `phone-context` in a SIP or tel URI, to the appropriate Nature of Address indicator (e.g., "network-specific number") in ISUP/BICC signaling.

  • Correction of the Interworking of the Redirecting Number TS 29.163CR1042
Rel-16 4 changes

In Release 16, the MSN function was enhanced with specific interworking procedures for the Local Number Format in both the Generic Number and From header field. It also introduced modifications for setting the P-Asserted-Identity header when a calling party number is unavailable and defined the mapping of the SIP History-Info header field to the ISUP Original Called Number parameter.

  • Interworking of Local Number Format in Generic Number TS 29.163CR1070
  • Interworking of Local Number Format in From Header Field TS 29.163CR1072
  • Modification on the setting of P-Asserted-Identity header field when a calling party number is not available. TS 29.163CR1058
  • Mapping of History-Info header field to ISUP Original called number TS 29.163CR1069

Explore further

Broader topics and technologies where MSN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19