NANC 392

Removal of Cloned Copies of SVs and NPBs

Origination Date :03/11/2004

Originator:Arch Planning Team

Description:

Business Need:

Currently, the FRS requires the NPAC to create cloned copies of SVs and NPBs (a pre-change snapshot, with a new ID and status = old) when various updates are performed (modifies, NPA Splits, SPID Migrations, etc.).  This is in addition to updating the data on the “real” SV/NPB.  These cloned copies are never broadcast to the SOA or LSMS, so neither system knows about these SVs/NPBs.

As an example, a TN is ported, and is assigned SV-ID 100.  That number is part of an NPA Split, a cloned copy is created (SV-ID 110 status = old), and SV-ID 100 is updated with the current NPA Split info.  The number has a GTT data change, a cloned copy is created (SV-ID 120 status = old), and SV-ID 100 is updated with the new GTT info.  The number has another GTT data change, a cloned copy is created (SV-ID 130 status = old), and SV-ID 100 is updated with the new GTT info.  The number is then ported to another SP, and a new known/broadcasted SV is created (SV-ID 200).

When discussed during the Mar ’04 APT meeting, some Service Providers stated that the current functionality is confusing because of the cloned copies, which are returned in a query, since the SOA or LSMS does not know about these ported numbers and their associated “intermediate” SV-IDs.

This change order will remedy this situation by eliminating the “intermediate” records (110, 120, 130).  The known/broadcasted records (100, 200, 300) will remain in the NPAC, based on current functionality.

Based on current tunable values, these cloned copies are maintained for 180 days, and maintaining them utilizes a significant amount of NPAC processing.

Final Resolution:

Func Backwards Compatible:  YES

The functionality for SV/NPB data within the NPAC will be modified to only update the known/broadcasted SV/NPB to reflect the current SV/NPB data.

In the proposed update, “intermediate” SVs/NPBs (i.e., pre-change snapshots which are the cloned copies) will no longer be maintained in the NPAC.

Implemented in FRS 3.3.0a.

Related Release:

Implemented in FRS 3.3.0a.

Status: Implemented