Number Portability Database Dip Indicator

Description

The Number Portability Database Dip Indicator (NPDI) is a signaling parameter defined within the Session Initiation Protocol (SIP) for use in 3GPP IMS networks. It is carried in specific SIP header fields, most notably the P-Charging-Vector header defined in 3GPP TS 24.229 and further detailed in TS 29.163. The NPDI is not a database itself but a Boolean-like flag or indicator that conveys the result of a database lookup. Its value signals to subsequent network nodes in the call path whether a dip (query) into an external Number Portability Database (NPDB) has been executed by a preceding node, such as an Interrogating Call Session Control Function (I-CSCF) or a Breakout Gateway Control Function (BGCF).

The primary architectural role of the NPDI is within the call routing and charging functions of the IMS. When a call is made to a telephone number, the originating network must determine the current serving network of the called party, especially if the number has been ported away from its original operator. An IMS node equipped with the appropriate functionality will perform a query to an NPDB (often via the ENUM/DNS system or a direct protocol like SOAP/XML). Upon receiving the response, this node inserts the NPDI parameter into the SIP request (e.g., INVITE), setting its value to indicate 'yes' (dip was performed) or conveying the ported number's routing number (RN) if applicable.

As the SIP request propagates through the network, downstream nodes, including the Serving-CSCF (S-CSCF) and charging systems like the Online Charging System (OCS) or Offline Charging System (OFCS), inspect the NPDI. This information is critical for several reasons. First, it prevents redundant and costly NPDB queries by subsequent nodes, optimizing call setup time and reducing signaling load. Second, it provides essential data for accurate charging. The knowledge that a number is ported and the associated routing information can affect the tariff applied to the call. The NPDI, therefore, acts as a key piece of metadata that ensures efficient, correct, and billable call routing in a multi-operator environment where number portability is mandatory.

Purpose & Motivation

The NPDI was introduced to solve operational and technical challenges arising from the implementation of number portability in all-IP networks, specifically the IMS. Number portability allows subscribers to retain their phone number when switching service providers, breaking the inherent link between a number's prefix and its network. In traditional circuit-switched telephony, dedicated signaling systems handled this. With the migration to IMS and SIP-based control, a standardized mechanism was needed to communicate the outcome of number portability checks across different network functions and potentially between operators.

Without an indicator like NPDI, each IMS node involved in routing a call might independently query the NPDB, leading to signaling inefficiency, increased call setup delays, and unnecessary load on the NPDB systems. More critically, the lack of a standardized way to convey portability information could lead to routing errors or incorrect charging. The NPDI provides a lightweight, in-band signaling solution that solves these problems. It enables the originating network to perform the dip once, share the result with the entire call path, and ensures that charging systems are aware of the portability status for accurate billing, which is a fundamental regulatory and commercial requirement. Its creation was motivated by the need for interoperability and efficiency as core network evolved from TDM to VoIP and IMS.