International Mobile User Number

Description

The International Mobile User Number (IMUN) is a telecommunications identifier defined within the 3GPP framework, specifically for use in IP Multimedia Subsystem (IMS) networks. As outlined in specifications such as TS 22.101 (Service Aspects) and TS 23.003 (Numbering, Addressing, and Identification), the IMUN is a public user identity that conforms to the ITU-T E.164 international numbering plan. This means it appears as a standard, globally routable telephone number (e.g., +441234567890). Its primary purpose is to address a user for multimedia session establishment, like Voice over IP (VoIP) calls, video calls, and other IMS-based services.

Within the IMS architecture, a user can have multiple public user identities. The IMUN is one type, alongside SIP URIs (like [email protected]). The IMUN is stored in the user's subscription profile within the Home Subscriber Server (HSS). When a user registers with the IMS network, their assigned public user identities (including any IMUNs) are registered and become reachable. The IMUN is used in the signaling path, particularly in protocols like SIP (Session Initiation Protocol). For instance, when initiating a video call, the calling party would use the callee's IMUN as the Request-URI in the SIP INVITE message. The IMS core, including the Serving-Call Session Control Function (S-CSCF), uses this E.164 number to perform number analysis, routing, and service triggering based on the user's profile.

The IMUN plays a crucial role in interworking and interoperability. Because it follows the globally understood E.164 format, it allows IMS users to be called from, and to call to, users in traditional circuit-switched telephone networks (PSTN, PLMN) via appropriate breakout gateways (e.g., MGCF). This bridges the gap between all-IP IMS networks and legacy telephony. Furthermore, for services like Video Telephony, the IMUN provides a familiar dialing experience for users accustomed to entering phone numbers.

The lifecycle and management of an IMUN are tied to the subscriber's IMS subscription. It can be provisioned by the operator, and a single user may have both an IMUN and a SIP URI, allowing flexibility in how they are contacted. The Tel URI format (which also encodes an E.164 number) is often used in SIP signaling to carry the IMUN. The continued relevance of the IMUN lies in the enduring need for E.164-based addressing in a world where many communication services still rely on telephone numbers, even as they migrate to packet-switched, IMS-based delivery.

Purpose & Motivation

The IMUN was created to provide a standardized, E.164-compliant addressing scheme for users within the IP Multimedia Subsystem (IMS), the core network architecture for delivering multimedia services in 3GPP networks. As 3GPP evolved circuit-switched voice to packet-switched Voice over IP (VoIP) and multimedia, a key challenge was maintaining interoperability with the existing global telephone network (PSTN/PLMN) and providing a user-friendly identifier.

The problem it solved was twofold. First, users and existing business processes were (and still are) deeply familiar with telephone numbers. Introducing a completely different addressing scheme (like SIP URIs only) for new multimedia services would create a barrier to adoption. The IMUN allowed new IMS-based services, like video telephony, to be accessed using a familiar phone number. Second, for network operators, seamless interworking between IMS and legacy networks was essential for service continuity. An E.164-based identity like the IMUN allows routing logic and gateway functions (like the MGCF) to translate between SIP-based IMS signaling and ISUP/BICC-based circuit-switched signaling using a common number format.

Historically, as IMS was developed from Release 5 onwards, the IMUN was defined alongside SIP URIs to offer a dual addressing capability. It addressed the limitations of relying solely on device-centric identifiers (like IMSI) or non-dialable identifiers, ensuring that IMS users could be integrated into the global numbering plan. This was a critical factor for the commercial success of IMS-based services, enabling them to replace and enhance traditional telephony rather than exist as a separate, incompatible silo.

Key Features

• E.164 format global telephone number used in IMS
• Serves as a Public User Identity for session establishment
• Stored in the Home Subscriber Server (HSS) user profile
• Used in SIP signaling (often as a Tel URI) for routing calls
• Enables interworking between IMS and traditional circuit-switched networks
• Provides a familiar dialing experience for multimedia services like video calls

Evolution Across Releases

Defining Specifications