NPDB

Number Portability Data Base

Services →
Introduced in Rel-4 Also in: Core Network

NPDB is a database that stores routing information for ported telephone numbers, enabling Number Portability so subscribers can keep their number when changing service providers.

Category
Services
Introduced
Rel-4
Where
Management
Also touches
1 segments
Specifications
9 specs
NPDB Description Purpose Related Specifications

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.

Evolution Across Releases

Rel-4 Initial

Introduced the NPDB concept for GSM/UMTS networks in specifications like TS 23.066. Established the basic architecture for number portability, defining the NPDB's role in resolving routing for ported mobile numbers via MAP queries. Laid the foundation for separating subscription identity from network routing.

Enhanced support for IP Multimedia Subsystem (IMS) and the transition to all-IP networks. Updated specifications to ensure NPDB query mechanisms were compatible with emerging SIP-based call control and DIAMETER signaling.

Further refinements to interoperability and testing guidelines. Strengthened the specifications for NPDB interfaces and operations in multi-vendor environments.

Continued maintenance and updates to align with network evolution, including support for fixed-mobile convergence scenarios where number portability might span different access technologies.

Ensured NPDB architecture compatibility with the new Evolved Packet Core (EPC) for LTE. Addressed routing for ported numbers in the context of voice over LTE (VoLTE) and SRVCC handovers.

Minor updates and clarifications to existing NPDB procedures as part of general specification maintenance and enhancement for LTE.

Maintained NPDB specifications, ensuring stability of the core number portability function as networks prepared for further evolution.

Continued specification maintenance. Focused on ensuring robustness and security of the NPDB query interfaces.

Updates to support machine-type communications (MTC) and the increasing importance of SMS for IoT, ensuring ported M2M numbers were correctly routed.

Further integration with network functions virtualization (NFV) concepts, considering how NPDB functions could be virtualized and deployed as VNFs.

Enhancements related to service-based architecture (SBA) principles in preparation for 5G Core, though the core NPDB query logic remained based on established protocols.

Formalized support for number portability in the 5G System (5GS). Defined interactions between the 5G Core Network Functions (like UDM/AUSF) and external NPDB systems for routing resolution, maintaining backward compatibility.

Introduced enhancements for integrated access and backhaul (IAB) and non-public networks, ensuring NPDB queries functioned correctly in these new deployment scenarios.

Extended NPDB considerations for edge computing and network slicing, ensuring ported numbers were correctly routed within slice-specific contexts and to/from edge application servers.

Ongoing evolution to support advanced 5G-Advanced features, with a focus on ensuring the NPDB framework remains scalable and efficient for future service paradigms.

Continued maintenance, security hardening, and alignment with the latest architectural trends, ensuring the NPDB remains a robust foundation for number portability in evolving networks.

Explore further

Broader topics and technologies where NPDB plays a role.

Defining Specifications

3GPP specifications that define or reference NPDB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19
TS 32.632 vb00 Core Network Resources IRP: Network Resource Model Rel-11
TS 32.732 vb00 IMS Network Resource Model IRP: Information Service Rel-11