NANC 302

R3 FRS documentation-only updates

Origination Date :01/24/2000

Originator:CMA

Description:

RR5-56 Create Inter-Service Provider Port-to-Original Port – NPAC and SOA After NPA-NXX-X Creation

NPAC SMS shall reject an inter-service provider Subscription Version Create message where there is no active subscription version for the TN in the NPAC SMS, or inter-service provider Port-to-Original Subscription Version Create message for a TN within the 1K Block, from NPAC Personnel, a Service Provider SOA via the SOA to NPAC SMS Interface, or Service Provider via the NPAC SOA Low-tech Interface, after the Creation of the NPA-NXX-X, and prior to the existence of the Block in the NPAC SMS, ~~where there is no active subscription version for the TN in the NPAC SMS~~ . (Previously SV-180)

R5-74.3 Query Subscription Version - Output Data

NPAC SMS shall return the following output data for a Subscription Version query request initiated by NPAC personnel or a SOA to NPAC SMS interface user:

(need to add the following to the list)

1. Broadcast Time Stamp

2. Old SP Conflict Resolution Time Stamp

3. Download Reason

Subscription Version Data Model and Number Pool Block Data Model. Change “Disconnect Broadcast Complete Time Stamp” to “Disconnect Complete Time Stamp”, to make consistent with the GDMO.

Add NPA-NXX to filter requirements.

RR3-5 Create Filtered NPA-NXX for a Local SMS

NPAC SMS shall allow a Service Provider to create a filtered NPA-NXX for a given Local SMS, via the NPAC SMS to Local SMS interface and the SOA to NPAC SMS interface, which results in the SMS NOT broadcasting NPA-NXX, subscriptions, NPA-NXX-X information or Number Pool Blocks with the filtered NPA-NXX to the Local SMS.

RR3-6 Delete Filtered NPA-NXX for a Local SMS

NPAC SMS shall allow a Service Provider to delete a filtered NPA-NXX for a given Local SMS, via the NPAC SMS to Local SMS interface and the SOA to NPAC SMS interface, which results in the SMS broadcasting NPA-NXX, subscriptions, NPA-NXX-X information and Number Pool Blocks with the filtered NPA-NXX to the given Local SMS.

Change SPID reference.

RR9-4 Pooled Number Reports – Block Holder Default Routing Report Page Break

NPAC SMS shall page break the report listed in RR9-3, for every change in new ~~SPID~~ Block Holder ID . (Previously R-26)

Update pending SV retention to include Old SP Due Date.

RR5-1.4 Pending Subscription Retention - Tunable Parameter Expiration

NPAC SMS shall cancel a Subscription Version by setting the subscription version to cancel after a pending Subscription Version has existed in the system for a Pending Subscription Retention number of calendar days subsequent to new Service Provider Due Date, or old Service Provider Due Date if the new Service Provider Due Date has not been received by the NPAC SMS .

Update audit requirement to reflect audit behavior when EDR LSMS erroneously contains a Number Pool Block.

RR8-6 Audit Processing for All Subscription Versions in a Number Pooling Environment

NPAC SMS shall process an audit request of an Active-Like Subscription Version(s), by performing the following steps: (Previously A-2)

…

Send audit results and notification of discrepancies, back to requesting SOA, only for the TN Range that was requested, even if other TNs were affected because of EDR Local SMS. The existing notification report will be unchanged, and will not contain block information. In cases where an EDR Local SMS erroneously contained a Number Pool Block, the NPAC SMS shall send a Number Pool Block delete to the Local SMS, but shall not report any discrepancy back to the requesting SOA for this Local SMS.

Update incorrect requirement number. Number Pool NPA-NXX-X Holder information notification of First Port, requirement number R3-113, was incorrectly given a “R3-” prefix instead of a “RR3-“ prefix. This requirement will be renumbered to RR3-228 (or the next available requirement number in section 3).

Update incorrect BDD information. In the Subscription Version BDD description, the last sentence should be removed “The files available for LSMS compares will be defined as one NPA-NXX per file”.

Update requirement RR3-172 to reflect the actual business requirement and not restrict the implementation. In this case, the GUI may display the Block, but disable the ‘Delete” button, thereby restricting the user from deleting the block (which is the actual business need).

RR3-172 Deletion of Number Pool Block Holder Information – LTI

NPAC SMS shall not allow Service Provider Personnel to request a delete of a Block in the NPAC SMS via the NPAC SOA Low-tech Interface, ~~and will return an error message to the LTI user~~ . (Previously B-415)

10.

Update incorrect requirement number. In R3, RR5-38.1 became two requirements (numbered RR5-38.1.1 and RR5-38.1.2). However, they were incorrectly numbered RR5-38.1 and RR5-38.2. This created a situation where there are two RR5-38.2 requirements.

11.

Update requirement RR3-90 to explicitly identify the number of days “between”, that is referenced in the requirement.

RR3-90 Addition of Number Pooling NPA-NXX-X Holder Information Effective Date Window– Tunable Parameter

NPAC SMS shall provide a NPA-NXX-X Holder Effective Date Window tunable parameter which is defined as the minimum length of time between the current date (exclusive) and the effective date (inclusive) , when Creating a NPA-NXX-X in the NPAC SMS. (Previously N-140)

Note: If the current date is Tuesday the 2^nd , the tunable is set to 5 business days, and we’re using short business days (i.e., Monday-Friday), the minimum effective date for the NPA-NXX-X would be Tuesday the 9^th .

12.

Delete requirement RN3-4.10, which becomes obsolete with NANC 244 being implemented in R3.

RN3-4.10 NPA Split - Retention of NPA-NXX(s) involved in an NPA Split

NPAC SMS shall leave the old NPA-NXX(s) involved in a split as valid NPA-NXX(s).

Note: Old NPA-NXX(s) may be deleted via normal processing after the end of permissive dialing.

Final Resolution:

Pure Backwards Compatible: YES

Related Release:

3.0.1

Status: Implemented