MNP

Mobile Number Portability Signalling Relay Function

Services →
Introduced in Rel-4 Also in: Services

MNP is a network function that routes signaling messages to the correct network for a ported number by intercepting queries and consulting a Number Portability database.

Category
Services
Introduced
Rel-4
Where
Core Network › Evolved Packet Core
Also touches
1 segments
Specifications
7 specs
MNP Description Purpose Related Classification Detected Changes Specifications

Description

The Mobile Number Portability Signalling Relay Function (MNP SRF) is a critical network element specified by 3GPP to implement Mobile Number Portability (MNP). MNP allows subscribers to retain their mobile telephone number when switching service providers (Mobile Network Operators). The core technical challenge solved by the MNP SRF is the routing of voice calls and signaling messages (like SMS) to the correct recipient network after a number has been ported away from its original "donor" network.

Architecturally, the MNP SRF typically resides in the signaling path, often integrated with or adjacent to a Signal Transfer Point (STP) or as part of an IP-based signaling router. Its operation is triggered during call or session setup. When a call is placed to a ported number, the originating network's switch or call session control function sends a signaling query, such as a Send Routing Information (SRI) query in the MAP protocol, to what it believes is the home network based on the number's range. The MNP SRF intercepts this query. It then queries a central or distributed Number Portability Database (NPDB) to determine if the dialed number has been ported, and if so, to which recipient network it now belongs.

Upon receiving a response from the NPDB, the MNP SRF performs a key function: it modifies the signaling message. For a ported number, it will replace the original destination Global Title (GT) address (pointing to the donor network's HLR) with the GT of the recipient network's HLR. It then forwards the modified query to the correct network. This process is transparent to the originating switch. The MNP SRF may also be involved in other procedures, such as handling errors or managing cache of portability data to optimize performance. Its implementation ensures that all networks, including those not directly involved in the porting transaction, can correctly route traffic without requiring universal updates to their own routing tables for each ported number.

Purpose & Motivation

MNP and the MNP SRF were created to foster consumer choice and market competition by removing a major barrier to switching providers: the loss of one's phone number. Before MNP, subscribers were effectively "locked in" to their operator because changing numbers caused significant inconvenience and cost. Regulatory bodies in many countries mandated MNP to stimulate competition, leading to the need for a standardized technical solution.

The MNP SRF solves the problem of distributed routing logic. Without it, every network operator would need to continuously update its internal routing tables with the latest porting information for every number in the country—a highly inefficient and error-prone process. The SRF centralizes this intelligence. It provides a single point of interrogation, allowing the originating network to route calls based on the dialed digits as usual, while the SRF ensures the query is redirected to the correct network's database. This architecture, standardized by 3GPP starting in Release 4, provided a scalable and reliable method for implementing a regulatory requirement, ensuring interoperability between all operators in a market.

Classification

Part ofMAP
Related approachesHLRGTNPDB

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-4, normative work from Rel-16.

Rel-16 1 change

In Release 16, the primary introduction for the MNP function was the addition of new general abbreviations to the 3GPP specifications. This update provided standardized terminology for key concepts directly related to Mobile Number Portability, such as defining the "Donor network" as the subscription network from which a number is ported. The changes ensured the technical documentation clearly distinguished between the ported number's origin and its current network.

  • Add new general abbreviations MCC Note: CR cover sheet wrongly shows CR number as "1118". TS 21.905CR0118

Explore further

Broader topics and technologies where MNP plays a role.

Defining Specifications

3GPP specifications that define or reference MNP, 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 23.066 vj00 Mobile Number Portability Technical Realization Rel-19
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19
TS 29.204 vj00 SS7 Security Gateway Functional Description Rel-19
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TS 32.808 v1800 Common User Profile Storage Framework Rel-8