Number Portability Location Register

Description

The Number Portability Location Register (NPLR) is a critical functional entity within the 3GPP core network architecture, specifically defined for the support of Mobile Number Portability (MNP). It acts as a centralized or distributed database that holds the mapping between a ported mobile subscriber's Mobile Station International Subscriber Directory Number (MSISDN) and the identity of the network (the recipient network) to which the number has been ported. When a subscriber switches operators but retains their phone number, their MSISDN is no longer associated with their original home network's Home Location Register (HLR). The NPLR provides the necessary intelligence to route calls and messages correctly.

Architecturally, the NPLR interfaces with other core network elements like the Gateway Mobile Switching Center (GMSC) or the IP Multimedia Subsystem (IMS) core. When a call is made to a ported number, the originating network's GMSC performs a query, typically using an ENUM or Signaling System 7 (SS7)-based mechanism, to determine if the number is ported. If it is, the query is directed to the NPLR (or a centralized number portability database that may be considered synonymous). The NPLR responds with the routing number (e.g., a Mobile Network Code (MNC) or a specific routing prefix) that identifies the recipient network. This routing information is then used to forward the call to the correct network's gateway for final delivery to the subscriber.

Its role is purely for routing resolution; it does not handle subscriber authentication, service profiles, or session management. The NPLR's operation is transparent to the end-user but is fundamental for regulatory compliance and seamless service continuity in competitive telecommunications markets. It decouples the subscriber's identity (MSISDN) from the network infrastructure identity, enabling true number portability.

Purpose & Motivation

The NPLR was created to solve the fundamental problem introduced by Mobile Number Portability (MNP): how to route a call to a subscriber who has changed network operators but kept their phone number. Before MNP, an MSISDN contained embedded routing information (the country and network codes). A call was routed to the network identified by those codes, which then used its HLR to locate the subscriber. When a number is ported, this inherent routing breaks because the number's original network code no longer points to the subscriber's actual serving network.

The primary motivation was regulatory, driven by government policies to increase market competition by lowering the barrier for subscribers to switch operators. Without a technical solution like the NPLR, ported numbers would be unreachable, negating the benefit of portability. The NPLR provides the essential lookup service that translates a ported MSISDN into the correct destination network identifier, solving the call routing problem. It addressed the limitations of the pre-portability architecture where routing was statically determined by number ranges assigned to operators, enabling a dynamic, query-based routing mechanism that is essential for a modern, competitive telecom ecosystem.

Key Features

• Stores mappings between ported MSISDNs and recipient network identifiers
• Provides query/response interface for routing resolution (e.g., via SS7 or IP)
• Enables regulatory compliance for Mobile Number Portability (MNP)
• Works alongside GMSC and HLR for call routing
• Centralized or distributed architectural deployment options
• Supports both voice and SMS routing for ported numbers

Evolution Across Releases

Defining Specifications