MSN

Multiple Subscriber Number

Services
Introduced in Rel-8
A service feature allowing a single User Equipment (UE) or IMS subscription to be assigned multiple directory numbers (MSISDNs). It enables distinct identities for different purposes, like separate numbers for business and personal use on one device. The network routes calls to the appropriate number and can apply different service logic based on which number was dialed.

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.

Key Features

  • Allows association of multiple MSISDNs with a single IMSI/IMPU
  • Enables distinct call routing and service logic per directory number
  • Supports differentiated charging, call forwarding, and voicemail per MSN
  • Network-based feature, independent of device capabilities
  • Integrates with HSS/UDM for identity mapping and service profile retrieval
  • Applicable in both circuit-switched and IMS-based telephony domains

Evolution Across Releases

Rel-8 Initial

Introduced the MSN feature in the context of IMS-based services, specified in TS 29.163 (Interworking) and TS 33.108 (Security). It defined the initial architecture for mapping multiple E.164 numbers to a single IMS subscription, enabling service differentiation and routing based on the called party number within the IMS framework.

Defining Specifications

SpecificationTitle
TS 29.163 3GPP TS 29.163
TS 33.108 3GPP TR 33.108