NANC 193

TN Processing During NPAC SMS NPA Split Processing

Origination Date :01/23/1998

Originator:NANC T&O

Description:

There was group consensus that NPAC behavior would not change until the start of permissive dialing. An example would be an audit that occurred during split processing one-minute before the start of permissive dialing. The NPAC should act as if permissive dialing has not yet started for the audit initiated during split processing. The Split processing should have no effect on operations of the system.
 
A clarification requirement should be added as follows:
 
NPAC SMS shall processes requests during split processing prior to the start of permissive dialing as if the split processing has not yet occurred.
 
Additional clarification requirement:
 
NPAC SMS shall in a download request made after permissive dialing start for subscription version data sent prior to permissive dialing start, return the new NPA-NXX for subscription versions involved in an NPA Split.
 
The above requirements do not reflect the current Lockheed NPAC SMS implementation.
 
Dec ’05 comments: move to cancel-pending.

Final Resolution:

Pure Backwards Compatible: YES
 
Lockheed in release 1.2 currently holds requests until the NPA Split processing completes (regardless of the NPA or NPA-NXX). Nortel/Perot rejects the requests during NPA split processing. It was not clear if errors were for all requests or just requests related to the NPA or NPA-NXX being split.
 
Desired behavior would be to have no errors occur. Requests put on hold or queued would only be those related to NPA-NXXs involved in the NPA split being processed.
 
Lockheed in Release 1.3 will perform NPA- NXX locking.
 
The following questions need to be answered by vendors:
 
What will the SOA do if it sends an old NPA-NXX prior to PDP and the NPAC returns the new SV with the new NPA-NXX? What would happen for a create/audit/query?
What will LSMS systems do if an audit is sent for new NPA prior to PDP?
Are there LSMS that will not be able to handle audits on new NPA-NXX right at the start of PDP?
How long does it take for NPAC/SOA/LSMS to split an NPA-NXX?
What is the NPAC behavior for recovery spanning time before & after PDP?
If NPAC splits starting at midnight and SOA sends new NPA-NXX for an NPA-NXX not in split what would happen?
 
After reviewing the above questions. It was determined that the NPAC should act as if the split had not occurred during split processing prior to permissive dialing.
 
A matrix of answers received above has been created.
 
It was discussed that this requirement would have to be implemented by SOA, LSMS, and NPAC vendors. This requirement would shorten the window when errors could occur for the change of an NPA. It was requested that we review and document on behavior in the following situations: When the NPAC receives a request sent before the splits after the split start, how should it respond? Also when an SOA or LSMS receives a request sent before the split after the split start, how should it respond?
 
IIS flows for error scenarios will be created. If an active is received by the NPAC SMS before PDP it will be rejected. If the old SP is received after the end of PDP it will be treated as the old NPA-NXX if that NPA- NXX is still a valid portable NPA-NXX in the NPAC SMS otherwise it will be rejected. Download requests after the start of PDP for information occurring before PDP should reflect the new NPA- NXX for subscription versions involved in a Port.
 
The matrix was finalized on the 5/22 T&O call.

12/05 – Moved to Cancel-Pending per LNPAWG discussion.
 
3/06 – Deleted following March LNPAWG meeting

Related Release:

N/A

Status: Closed