Number Portability Data Base

Description

The Number Portability Data Base (NPDB) is a fundamental network element specified across multiple 3GPP technical specifications (e.g., TS 23.066, TS 28.702) that enables Number Portability (NP) services. Its primary function is to store the mapping between a subscriber's dialed telephone number (the MSISDN) and the current network operator or service provider that is serving that number. When a number is ported from an original donor network to a new recipient network, this mapping is updated in the NPDB. Architecturally, the NPDB can be implemented as a single national database, a distributed system, or a set of interconnected operator databases, depending on the regulatory model adopted by a country.

How it works involves a query-and-response mechanism. When a call is placed to a ported number, the originating network's call control element (like an MSC or CSCF) cannot determine the correct destination network based on the number's prefix alone. It therefore initiates a query, typically using signaling protocols like MAP or DIAMETER, to an NPDB (or a routing broker that accesses it). The query contains the dialed number. The NPDB consults its records and returns a response indicating the current serving network's routing number (e.g., a Mobile Network Code (MNC) or a specific routing number like a Network Routing Number (NRN)). The originating network then uses this routing information to direct the call to the correct recipient network's gateway for completion.

Key components of the NPDB system include the database itself, the query interfaces (standardized signaling interfaces like Np), and the management systems for updating records (often involving a separate Number Portability Administration Center or NPAC). Its role is critical not just for voice calls but also for SMS, MMS, and other services that rely on correct number routing. By decoupling a number's identity from its network affiliation, the NPDB acts as the central nervous system for number portability, ensuring seamless service continuity for users and enabling efficient inter-operator routing. It must be highly available, secure, and provide low-latency responses to avoid impacting call setup times.

Purpose & Motivation

The Number Portability Data Base (NPDB) was created to solve a fundamental market barrier in telecommunications: the locking-in of customers to a specific operator because changing operators meant losing their phone number. Before number portability, a subscriber's number was intrinsically tied to the operator that issued it. This stifled competition, as the inconvenience of changing numbers was a significant deterrent for users to switch providers, even if better services or prices were available elsewhere. The NPDB enables the technical implementation of number portability, which was driven by regulatory mandates worldwide to promote consumer choice and market competition.

Its purpose is to provide a reliable, standardized mechanism for routing communications to a number that is no longer hosted on its original "home" network. It solves the critical network routing problem that arises when a number's point of attachment to the network changes. Without an NPDB, calls to a ported number would continue to be routed to the donor network, which would then have to forward them (often inefficiently) or the call would fail. The NPDB introduces a level of indirection, allowing all networks to discover the current serving network directly.

The historical context involves the evolution from simple operator-specific routing to complex, query-based routing. Early solutions like call forwarding were inefficient and costly. The NPDB, as standardized by 3GPP and other bodies, provided an optimized, scalable solution. It addresses the limitations of previous non-portable environments by creating a centralized authority for number-to-operator mapping. This technical capability was essential for regulators to enforce pro-competitive policies, making the NPDB a key enabler of liberalized telecom markets and enhanced user convenience.

Key Features

• Stores real-time mapping of ported numbers to current serving network
• Provides query/response interface using standardized signaling (e.g., MAP)
• Supports multiple portability types (operator, service, geographic)
• Enables low-latency routing resolution for call setup
• Integrates with management systems for secure record updates
• Designed for high availability and scalability to handle national query loads

Evolution Across Releases

Defining Specifications