Mobile Number Portability/Signalling Relay Function

Description

The Mobile Number Portability/Signalling Relay Function (MNP-SRF) is a critical network element defined within the 3GPP architecture to facilitate the implementation of Mobile Number Portability (MNP). Its primary role is to act as an intermediary or relay point within the signaling path, specifically for call setup and session establishment procedures. When a call is placed to a ported number, the originating network's signaling messages (e.g., ISUP, SIP) are routed to the MNP-SRF. The function then performs a real-time query to a Number Portability Database (NPDB) or similar repository to ascertain the current serving network for the dialed mobile subscriber number (MSISDN). Based on the query response, which typically includes a routing number (e.g., a Mobile Network Code, MNC, or a specific routing prefix), the MNP-SRF modifies the signaling message accordingly and relays it towards the correct destination network. This process is transparent to the end-users and ensures that calls are correctly delivered without requiring the calling party to know the subscriber's new network.

Architecturally, the MNP-SRF is often implemented as part of or in conjunction with signaling transfer points (STPs) or dedicated application servers within the core network, particularly in the circuit-switched (CS) domain. It interfaces with the NPDB using protocols like TCAP over SS7 or Diameter, depending on the network generation and implementation. The function must handle high volumes of signaling traffic with low latency to avoid impacting call setup times. Its operation is defined to be interoperable across different network operators and generations, supporting both legacy 2G/3G CS calls and, in evolved implementations, sessions in the IP Multimedia Subsystem (IMS).

The MNP-SRF's role extends beyond simple query-and-relay. It is responsible for managing error conditions, such as database unavailability, and may implement caching mechanisms to improve efficiency for frequently queried numbers. In the broader MNP ecosystem, it works in tandem with other functions like the Number Portability Gateway (NPG) and the donor/recipient network's Home Location Register (HLR) or Home Subscriber Server (HSS) to ensure a consistent subscriber experience. Its specifications across 3GPP releases ensure standardized behavior, which is crucial for regulatory compliance in regions where number portability is mandated by law.

Purpose & Motivation

The MNP-SRF was created to solve the fundamental routing problem introduced by Mobile Number Portability (MNP). Before MNP, a mobile number (MSISDN) contained embedded routing information (like the network operator's code), allowing switches to directly route calls to the correct home network. When regulators mandated that subscribers could keep their number when switching operators, this embedded routing information became obsolete and misleading, as a number might be 'ported' to a different network than its original allocation. Without a mechanism to resolve the current network, calls would be misrouted to the old (donor) operator, causing failed connections.

The purpose of the MNP-SRF is to provide a centralized, standardized interception and resolution point within the signaling architecture. It addresses the limitations of earlier, non-standardized, or operator-specific MNP solutions that could lead to interoperability issues. By defining a clear functional entity within 3GPP standards, it ensures that all network equipment vendors and operators implement MNP routing in a consistent and reliable manner. This was particularly important for enabling cross-border and multi-vendor network operations.

Its creation was motivated by regulatory requirements across many countries, driving the need for a technical solution that was scalable, efficient, and did not degrade the quality of service. The MNP-SRF allows operators to comply with portability regulations while maintaining the performance and reliability of their core networks. It abstracts the complexity of number portability from other network elements, allowing switches and call session control functions (CSCFs) to operate based on traditional routing logic, with the MNP-SRF handling the exception case for ported numbers.

Key Features

• Signaling message interception and analysis for call/session setup
• Real-time querying of Number Portability Databases (NPDB)
• Modification of signaling messages (e.g., inserting routing numbers)
• Relay of signaling towards the correct recipient network
• Support for both SS7-based and IP-based (e.g., Diameter) query protocols
• Error handling and fallback procedures for database failures

Evolution Across Releases

Defining Specifications