The Number Portability (NP) Service Does Not Find Some Numbers When DN Ranges of the Same Entry Type Overlap
(Doc ID 1638227.1)
Last updated on APRIL 11, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
The Number Portability (NP) Service is not sending the correct ported number digits to Network switches. Other symptoms include the Service Management System's (SMS) User Interface (UI), Services -> NP Service -> Subscriber and Network -> Common Find Panel screen, and/or the Provisioning Interface (PI) NPDS1=QRY command, failing to find the destination number (DN) range for a ported number, even though a database query of the NP_DN_RANGE table shows that the number is provisioned inside a DN range.
Closer analysis of the database query shows the queried number belongs to multiple overlapping DN ranges of the same entry type (Operator or Subscriber). Provisioning of overlapping DN ranges of the same entry type should not be possible and is against the NP Service design rules. It results in a control plan's NP Destination Selection (NDST) node failing to correctly match a ported number, and hence not send the correct information to the Network's switches.
The following example demonstrates the issue:
Three overlapping DN ranges (A-C) have been defined as follows:
- A: 64210340150 - 64210340150 (subscriber - internal ported number)
- B: 64210340140 - 64210340155 (operator - external range)
- C: 64210340100 - 64210340199 (operator - external range)
When a small set of numbers (64210340150, 64210340152, 64210340175) is directly queried in the database the following results are given:
These examples use Operator entries to show overlapping DN ranges as it is the more likely scenario. It is possible to produce the same behaviour for Subscriber DN ranges though.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document