NANC 394

Consistent Behavior of Five-Day Waiting Period Between NPA-NXX-X Creation and Number Pool Block Activation, and Subscription Version Creation and its Activation

Origination Date :06/16/2004

Originator:LNPA-WG

Description:

Business Need:

As specified in the PIM 38 problem statement, “The current NPA-NXX-X object (1K Pool Block) tunable of five(5) business days between the Create and Activate is too long and acts as a constraint against service providers. ”

Many service providers use the 1K Pool Block methodology (in addition to Number Pooling Activities) to accomplish Network Re-Home and Acquisition activities.  Between the NPA-NXX-X (1K Pool Block) Object Creation date and the Block Activation date there is a mandatory five business day tunable period.  During this time, service providers cannot conduct SV activity until the NPA-NXX-X is both created and activated at the NPAC.  Any activity will result in error transactions or “SOA NOT AUTHORIZED” 7502.  The five business day waiting period allows for increased errors as service providers are unable to conduct activities for pending NPA-NXX-X objects.

Currently, the FRS does not require the NPAC to enforce a five business day delay for conventional ports (inter or intra).  However, the FRS does require the NPAC to enforce the waiting period for all Number Pool Blocks (NPBs).  Since the reason for the interval is to allow time to provision a switch trigger, consistent behavior is desired.

This change order will assist in resolving most of this problem.  Since almost all of these NPBs, have already had some porting activity and therefore a first port notification has previously been broadcast, the five day waiting period is not necessary.  This change order would require the NPA-NXX-X Holder Effective Date Window tunable parameter  to be applied in situations only where the first port notification for the corresponding NPA-NXX had not previously been broadcast.

Additionally, this change order would add consistency by requiring the five day waiting period to be applied to SVs (inter or intra) in situations where the first port notification for the corresponding NPA-NXX had not previously been broadcast.

Final Resolution:

Func Backwards Compatible:  YES

The functionality for both SV and NPB data within the NPAC will be modified to enforce the waiting period minimum (NPA-NXX-X Holder Effective Date Window tunable parameter , defaulted to five business days) only when a first port notification for the corresponding NPA-NXX has NOT previously broadcast.

In the proposed update, once a first port notification for an NPA-NXX has been broadcast, the NPA-NXX-X Holder Effective Date Window tunable parameter  will not apply for subsequent NPB creates/activates, and will therefore allow NPA-NXX-X Creation to be followed by an immediate NPB Activation.

Additionally, for SV data, the addition of the waiting period minimum will provide a restriction that is currently not in the NPAC.  Once a first port notification for an NPA-NXX has been broadcast, the minimum restriction window will not apply for subsequent SV creates/activates.

Appropriate changes will also be made for modifications.

Implemented in FRS 3.3.0a, IIS 3.3.0a and GDMO 3.3.0.

Related Release:

Implemented in FRS 3.3.0a, IIS 3.3.0a and GDMO 3.3.0.

Status: Implemented