Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
NPAC SMS/Individual Service Provider Certification and Regression Test Plan For New Entrants Certification and Existing Service Providers/Vendors Regression Testing up to and including NPAC Release 3.4.68
Chapter 12
November June 30, 20136
Release 3.4.68
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 2
Table of Contents
12. Individual Turn Up Test Scenarios related to NPAC Release 3.2. ____________________________ 3 12.1 NANC 169 – Delta Download File Creation by Time Range for SVs ________ 4
12.2 NANC 187 – Linked Action Replies __________________________________ 23
12.3 NANC 191 DPC/SSN Value Edits and NANC 291 SSN Edits in the NPAC SMS
________________________________________________________________ 52 12.4 NANC 192 NPA Split NPAC SMS Load File _________________________ 7675
12.5 NANC 218 – Conflict Timestamp Broadcast to SOA __________________ 7776
12.6 NANC 230 – Donor SOA Port-To-Original of Intra-Service Provider Port 8584
12.7 NANC 249 – Modification of Dates for a Disconnect Pending SV ________ 9392
12.8 NANC 297 – Sending SV Problem During Recovery ________________ 103101
12.9 NANC 319 – NPAC Edit to Ensure NPA-NXX of LRN is in Same LATA as
NPA-NXX of Ported TN _______________________________________ 104102 12.10 NANC 322 – Clean Up of Failed SP List Based on Service Provider BDD
Response File ________________________________________________ 120118 12.11 NANC 323 – Partial Migration of SPID via Mass Update Test Cases ___ 128126
12.12 NANC 354 – Delta Download File Creation by Time Range for Network Data
____________________________________________________________ 129127
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 3
12. Individual Turn Up Test Scenarios related to NPAC Release 3.2.
Section 12 contains all test cases written for individual Service Provider Turn Up testing of
Release 3.2.x of the NPAC software.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 4
12.1 NANC 169 – Delta Download File Creation by Time Range for SVs
NOTE: When executing the NANC 169 Test Case, verify the NPAC Customer Allowable Functions, LSMS
Queries/Audits – is set to TRUE.
A. TEST IDENTITY
Test Case
Number:
NANC 169-1 SUT Priority: SOA N/A
LSMS Optional
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Subscription Data –
Specifying Active/Disconnect Pending/Partial Failure Subscription Versions Only and NOT
specifying a TN range. Verification steps are performed to ensure the BDD file was processed
successfully by the Service Provider system – Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 169
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-320, RR3-312, RR3-313, RR3-314,
RR3-319, RR3-323
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 5
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ from the NPAC SMS, NPAC personnel perform the
following functions:
NOTE: If the service provider under test supports WSMSC, SV Type and/or Optional Data
elements, include these attributes (based on support thereof) in the following
subscription version and/or number pool block activities.
a) Modify a (unique) range of 500, ‘Active’ Subscription Versions where the Service
Provider under test is the Current Service Provider. Use simulators that are not
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
these Subscription Versions exist with a status of ‘Active’ and a Failed SP List. (SV
group a______________)
b) Create a filter for the NPA-NXX for which you created 500, ‘Pending’ Subscription
Versions in 1a) above.
Activate these 500, ‘Pending’ Subscription Versions. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX.
Verify that the status for all 500 is ‘Active’ on the NPAC SMS. (SV group
b______________________)
Disconnect 250 of these now, ‘Active’ Subscription Versions specifying
Effective Release and Customer Disconnect dates in the future. Use
simulators that are associated with the NPAC and are receiving downloads for
this NPA-NXX. Verify that the status of these 250 Subscription Versions is
‘Disconnect-Pending’. (SV group b1___________)
Remove the filter for this NPA-NXX for the Service Provider under test so
that this range of Subscription Versions will be included in the Bulk Data
Download File.
c) First Create and then Activate 100 Intra-Service Provider Subscription Versions using
an NPA-NXX that is open for porting and for which the Service Provider under test is
accepting downloads for this NPA-NXX. This Service Provider is neither the Old nor
New Service Provider for these Subscription Versions. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that the Subscription Versions have a status of ‘Partial-Fail’. (SV group c
___________________)
d) Activate 50 Subscription Versions with a status of ‘Pending’. The Service Provider
under test is the New Service Provider for these Subscription Versions. Use
simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that these Subscription Versions have a status of ‘Partial-Fail’.
(SV group d_________________)
e) Activate a Number Pool Block for an NPA-NXX for which this Service Provider
under test is accepting downloads, but it is another Service Provider’s Number Pool
Block. Use simulators that are associated with the NPAC and are receiving downloads
for this NPA-NXX. Verify that the Pooled Subscription Versions have Number Pool
Block has a status of ‘Partial-Fail’. (SV group e_____________________) (NPB
e______________)
f) Create and concur to a range of 100, ‘Pending’ Subscription Versions where the
Service Provider under test is the New Service Provider. (SV group
f__________________)
g) Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Activate 50
‘pending’ SVs in group f above. Verify that these subscription versions have a status
of ‘sending’. (SV group g__________________) During the test case retry timers will
exhaust, and then the status of the SVs should be ‘Partial-Fail’.
Prerequisite SP
Setup:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 6
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Subscription Data,
specifying Active/Disconnect
Pending/Partial Failure
Subscription Versions Only and
NOT specifying a TN range, for the
Service Provider under test.
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file into their LSMS.
SP The LSMS successfully processes the Bulk Data Download
file(s) and reflects the updates described in the prerequisites
above.
The systems are still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Subscription Data to verify
that the Subscription Version data
was loaded.
SV group a
SV group b
SV group b1
SV group c
SV group d
For non EDR LSMS, SV group
e
For EDR LSMS, SV group e
was not loaded
SV group g
SP Using the LSMS system, verify:
SV group a exists on the LSMS. Verify that all of them
reflect the ‘modified’ SV values from the prerequisites
above.
SV group b exists on the LSMS.
SV group b1 exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
For non EDR LSMS, SV group e exists on the LSMS.
For EDR LSMS, SV group e DOES NOT exist on the
LSMS.
SV group g exists on the LSMS.
4. SP After all NPAC ‘retry timers’ for
the Subscription Versions specified
in the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associate’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates without recovering
additional information.
5. NPAC NPAC Personnel bring the
simulated SPID LSMS that was in
recovery in Prerequisite step g
above, out of recovery.
NPAC Verify that the simulated SPID that was in recovery during step
g of the prerequisites is now out of recovery. Verify that the 50
subscription versions that were activated while this SPID was in
recovery now have a status of ‘Partial Fail’.
6. NPAC NPAC Personnel perform multiple,
Full audits for each NPA-NXX
included in the range of TNs
specified in the prerequisites above
for the Service Provider’s LSMS to
verify that all the appropriate
updates were processed from the
Bulk Data Download File by the
LSMS.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a exists on the LSMS. Verify that all of them
reflect the ‘modified’ SV values from the prerequisites
above.
SV group b exists on the LSMS.
SV group b1 exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 7
For non-EDR LSMS, SV group e exists on the LSMS.
For EDR LSMS, SV group e DOES NOT exists on the
LSMS.
SV group g exists on the LSMS.
7. NPAC NPAC Personnel ‘re-send’ the
following to the Service Provider
under test:
SV group a that exists on the
NPAC SMS with a status of
‘Active with a Failed SP List.
SV group c that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
SV group d that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group e that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
SV group g that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
.
NPAC SMS issues the appropriate
messages to the LSMS in order to
update the LSMS for these SVs.
SP LSMS receives the resend requests from the NPAC SMS and
issues a ‘duplicate object’ response to the NPAC SMS for:
SV group a
SV group c
SV group d
If the Service Provider’s EDR Indicator is set to FALSE,
SV group e
SV group g
8. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX of
the following SVs, to verify that all
the appropriate updates were
processed from the NPAC ‘re-send’
for the ‘Partial-Fail’ objects:
SV group a
SV group c
SV group d
SV group 2e
SV group g
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
SV group e exists on the non-EDR LSMS.
SV group e DOES NOT exist on the EDR LSMS.
SV group g exists on the LSMS.
E. Pass/Fail Analysis, NANC 169-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Service Provider LSMS was able to successfully process the ‘re-send’ request from the NPAC SMS for the
‘Partial-Fail’ objects.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 8
Note: Since the Bulk Data Download file selection criteria does not include a TN Range in this test case, the file
may contain additional Subscription Versions. Testers can verify appropriate behavior for any additional data that
may be in the file as is stated in the Test Steps above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 9
A. TEST IDENTITY
Test Case
Number:
NANC 169-2 SUT Priority: SOA N/A
LSMS Optional
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Subscription Data –
Specifying Active/Disconnect Pending/Partial Failure Subscription Versions Only and
specifying a TN range that is a subset of the prerequisite test data. Verification steps are
performed to ensure the BDD file was processed successfully by the Service Provider system -
Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 169
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-318, RR3-319, RR3-320, RR3-323
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 10
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ with the NPAC SMS, NPAC personnel perform the
following functions:
NOTE: If the service provider under test supports WSMSC, SV Type and/or Optional Data
elements, include these attributes (based on support thereof) in the following
subscription version and/or number pool block activities.
a) Modify a (unique) range of 500, ‘Active’ Subscription Versions where the Service
Provider under test is the Current Service Provider. . Use simulators that are not
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
these Subscription Versions exist with a status of ‘Active’ and a Failed SP List. (SV
group a______________)
b) First Create and then Activate 100 Intra-Service Provider Subscription Versions using
an NPA-NXX that is open for porting and for which an NPA-NXX filter exists for the
Service Provider under test. This Service Provider is neither the Old nor New Service
Provider for these Subscription Versions. Use simulators that are associated with the
NPAC and are receiving downloads for this NPA-NXX. Verify that the Subscription
Versions have a status of ‘Active’. (SV group b ___________________) Remove the
filter for this NPA-NXX.
c) Submit a Deferred Disconnect request for 50 of the Intra-Service Provider Subscription
Versions that were created and activated in 2b) above. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that these Subscription Versions have a status of ‘Disconnect-Pending’. (SV group c
___________________________).
d) Activate 50 Subscription Versions with a status of ‘Pending’. The Service Provider
under test is the New Service Provider for these Subscription Versions. Use simulators
that are associated with the NPAC and are receiving downloads for this NPA-NXX.
Verify that these Subscription Versions have a status of ‘Partial-Fail’. (SV group
d_________________)
e) Activate a Number Pool Block for an NPA-NXX for which this Service Provider under
test is accepting downloads, but it is another Service Provider’s Number Pool Block.
Use simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that the Pooled Subscription Versions have Number Pool Block
has a status of ‘Partial-Fail’. (SV group e_____________________) (NPB
e______________)
f) Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Activate an
uncontaminated Number Pool Block on behalf of another Service Provider. Verify that
the Pooled SVs and NPB have has a status of ‘Sending’. (SV group
f_______________), (NPB f_________________) During the test case retry timers
will exhaust, and then the status of the Pooled SVs and NPB should be ‘Partial-Fail’.
The TN Range specified in the Bulk Data Download Selection Criteria should be a ‘subset’ of
the total of the TN Range used in the prerequisite steps. TN Range
_________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Subscription Data,
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 11
specifying Active/Disconnect
Pending/Partial Failure
Subscription Versions Only and
specifying the TN Range identified
in the prerequisites above, for the
Service Provider participating in the
test case. By specifying this TN
range, the content of the BDD will
actually be a subset of the
prerequisite data.
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their LSMS
systems.
SP The LSMS successfully processes the Bulk Data Download
file(s) and reflect the updates described in the prerequisites
above.
The systems are still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Subscription Data to verify
that the data was loaded.
NOTE: The BDD request was a
subset of the total TNs
manipulated in the Prerequisite
Setup above. Verify the subset of
data.
SV group a
SV group b
SV group c
SV group d
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group e
If the Service Provider’s EDR
Indicator is set to TRUE, SV
group e DOES NOT exist on
the LSMS.
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group f
If the Service Provider’s EDR
Indicator is set to TRUE, SV
group f DOES NOT exists on
the LSMS.
SP Using the LSMS system, verify:
NOTE: The BDD request was a subset of the total TNs
manipulated in the Prerequisite Setup above. Verify the
subset of data.
SV group a exists on the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group e exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group e DOES NOT exist on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group f exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group f DOES NOT exist on the LSMS.
4. SP After all NPAC ‘retry timers’ for
the Subscription Versions specified
in the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associate’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates with the NPAC SMS
without recovering additional information.
5. NPAC NPAC Personnel bring the
simulated SPID LSMS that was in
recovery in Prerequisite step f
above, out of recovery.
NPAC Verify that the simulated SPID that was in recovery during step
f of the prerequisites is now out of recovery. Verify that the
number pool block and respective pooled subscription versions
that were activated while this SPID was in recovery now have a
status of ‘Partial Fail’.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 12
6. NPAC NPAC Personnel perform multiple,
Full audits for each NPA-NXX
included in the range of TNs
specified in the prerequisites above
for the Service Provider’s LSMS to
verify that all the appropriate
updates were processed from the
Bulk Data Download File by the
LSMS.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a exists on the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group e exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group e DOES NOT exist on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group f exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group f DOES NOT exist on the LSMS.
7. NPAC NPAC Personnel ‘re-send’ the
following to the Service Provider
under test:
NOTE: The BDD request was a
subset of the total TNs
manipulated in the Prerequisite
Setup above. Resend the
respective subset of data.
SV group a that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
SV group d that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group e that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group f that exists on the NPAC
SMS with a status of ‘Partial-
Fail’.
NPAC SMS issues the appropriate
messages to the LSMS in order to
update the LSMS for these SVs.
LSMS LSMS receives the resend requests from the NPAC SMS and
issues a ‘duplicate object’ response to the NPAC SMS for:
NOTE: The BDD request was a subset of the total TNs
manipulated in the Prerequisite Setup above. Verify the
subset of data.
SV group a
SV group d
If the Service Provider’s EDR Indicator is set to FALSE,
SV group e
If the Service Provider’s EDR Indicator is set to FALSE
SV group f
8. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX of
the following SVs to verify that all
the appropriate updates were
processed from the NPAC ‘re-send’
for the ‘Partial-Fail’ objects:
SV group 2a
SV group 2d
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group 2a
SV group 2d
If the Service Provider’s EDR Indicator is set to FALSE,
SV group 2e
Formatted: Bulleted + Level: 1 + Aligned at: 0" + Tabafter: 0.25" + Indent at: 0.25"
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 13
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group 2e
If the Service Provider’s EDR
Indicator is set to FALSE SV
group 2f
If the Service Provider’s EDR Indicator is set to FALSE,
SV group 2f
E. Pass/Fail Analysis, NANC 169-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Service Provider LSMS was able to successfully process the ‘re-send’ request from the NPAC SMS for the
‘Partial-Fail’ objects.
Note: Since the TN Range specified in the Bulk Data Download selection criteria is a subset of the test data created
in the prerequisites, the Bulk Data Download file will not contain the full set of TNs. Testers should verify this
‘subset’ of TN in the verification steps.
Formatted: Bulleted + Level: 1 + Aligned at: 0" + Tabafter: 0.25" + Indent at: 0.25"
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 14
A. TEST IDENTITY
Test Case
Number:
NANC 169-3 SUT Priority: SOA N/A
LSMS Optional
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Subscription Data –
Specifying Latest View of Subscription Version Activity a valid Time Range, and NOT
specifying a TN range. Verification steps are performed to ensure the BDD file was processed
successfully by the Service Provider system – Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 169
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-315, RR3-316, RR3-317, RR3-319
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 15
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ with the NPAC SMS, NPAC personnel perform the
following functions:
a) Modify a range of 250, ‘Active’ Subscription Versions where the Service Provider
under test is the Current Service Provider. Use simulators that are not associated with
the NPAC and are receiving downloads for this NPA-NXX. Use a subset of SV group
1a above, and verify that these Subscription Versions exist with a status of ‘Active’
and a Failed SP List. (SV group 2a______________)
b) Activate 50 Subscription Versions with a status of ‘Pending’, for which a filter for this
NPA-NXX exists for the Service Provider under test. The Service Provider under test
is the New Service Provider for these Subscription Versions. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that these Subscription Versions have a status of ‘Active’. Remove the filter for this
NPA-NXX so that these Subscription Versions will be included in the BDD for the
service provider under test. (SV group 2b_________________)
c) Disconnect a subset of the 250, ‘Active’ Subscription Versions (in step 2b) specifying
Effective Release and Customer Disconnect dates in the future. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that the status of these Subscription Versions is ‘Disconnect-Pending’. (SV group
2c___________)
d) Activate a Number Pool Block for an NPA-NXX for which this Service Provider
under test is accepting downloads, but it is another Service Provider’s Number Pool
Block. Use simulators that are associated with the NPAC and accepting downloads for
this NPA-NXX. Verify that the Pooled Subscription Versions have Number Pool
Block has a status of ‘Partial-Fail’. (SV group 2d_____________________) (NPB
2d______________)
e) Activate a range of 100, ‘Pending’ Subscription Versions on behalf of another Service
Provider. Use simulators that are associated with the NPAC and are receiving
downloads for this NPA-NXX. Set a filter for this NPA-NXX on behalf of the Service
Provider under test. Verify that the Subscription Versions have a status of ‘Active’
with an empty Failed SP List. Remove filter for this NPA-NXX for the service
provider under test before performing following steps. (SV group e____________)
f) Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Modify 50 of
the TNs that were activated in step e above. Verify that the Subscription Versions have
a status of ‘Sending’. (SV group f___________________). During the test case retry
timers will exhaust, and then the status of the SVs should be ‘Partial-Fail’.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Subscription Data,
specifying Latest View of
Subscription Version Activity a valid
Time Range and not specifying a
TN range, for the Service Provider
participating in the test case.
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 16
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their LSMS
systems.
SP The LSMS successfully processes the Bulk Data Download
file(s) and reflects the updates described in the prerequisites
above.
The system is still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Subscription Data to verify
that the Subscription Version data
was loaded.
SV group a
SV group b
SV group c
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d
If the Service Provider’s EDR
Indicator is set to TRUE, SV
group d is not included
SV group f
SP Using the LSMS system, verify:
SV group a exists on the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group d DOES NOT exist on the LSMS.
SV group f exists on the LSMS.
4. SP After all NPAC ‘retry timers’ for
the Subscription Versions specified
in the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associate’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates with the NPAC SMS
without recovering additional information.
5. NPAC NPAC Personnel bring the
simulated SPID LSMS that was in
recovery in Prerequisite step f
above, out of recovery.
NPAC Verify that the simulated SPID that was in recovery during step
f of the prerequisites is now out of recovery. Verify that the 50
subscription versions that were modified while this SPID was in
recovery now have a status of ‘Active’ with a Failed SP List –
including the service provider under test. 6. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX
included in the range of TNs
specified in the prerequisites above
for the Service Provider’s LSMS to
verify that all the appropriate
updates were processed from the
Bulk Data Download File by the
LSMS.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a exists on the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group d DOES NOT exist on the LSMS.
SV group f exists on the LSMS.
7. NPAC NPAC Personnel ‘re-send’ the
following to the Service Provider
under test:
SV group a that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
SP LSMS receives the resend requests from the NPAC SMS and
issues a ‘duplicate object’ response to the NPAC SMS for:
SV group a
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d
SV group f
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 17
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
SV group f that exists with a
status of ‘Active’ and a Failed
SP List including the service
provider under test.
NPAC SMS issues the appropriate
messages to the LSMS in order to
update the LSMS for these SVs.
8. NPAC NPAC Personnel perform multiple,
Full audits for each NPA-NXX of
the following SVs to verify that all
the appropriate updates were
processed from the NPAC ‘re-send’
for the ‘Partial-Fail’ objects:
SV group a
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d
SV group f
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d
SV group f
E. Pass/Fail Analysis, NANC 169-3 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Service Provider LSMS was able to successfully process the ‘re-send’ request from the NPAC SMS for the
‘Partial-Fail’ objects.
Note: Since the Bulk Data Download file selection criteria does not include a TN Range in this test case, the file
may contain additional Subscription Versions. Testers can verify appropriate behavior for any additional data that
may be in the file as is stated in the Test Steps above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 18
A. TEST IDENTITY
Test Case
Number:
NANC 169-4 SUT Priority: SOA N/A
LSMS Optional
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Subscription Data –
Specifying Latest View of Subscription Version Activity a valid Time Range, and a TN range
that is a subset of the prerequisite test data. Verification steps are performed to ensure the BDD
file was processed successfully by the Service Provider system – Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 169
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-319, RR3-320, RR3-321, RR3-322
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 19
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ from the NPAC SMS, NPAC personnel perform the
following functions:
a) Activate range of 500, ‘Pending’ Subscription Versions where the Service Provider
under test is the Current Service Provider. Use simulators that are associated with the
NPAC and are receiving downloads for this NPA-NXX. Verify these Subscription
Versions exist with a status of ‘Partial Fail’. (SV group 2a______________)
b) Activate 500, unique, ‘Pending’ Subscription Versions for which a filter for this NPA-
NXX exists for the Service Provider under test. Use simulators that are associated with
the NPAC and are receiving downloads for this NPA-NXX. Verify that the status of
these 500 Subscription Versions is ‘Active’. (SV group 2b___________) Remove the
filter for this NPA-NXX.
c) Submit a Deferred Disconnect request for 50, unique, ‘Active’ Subscription Versions.
The Service Provider under test is the Current Service Provider for these Subscription
Versions. Use simulators that are associated with the NPAC and are receiving
downloads for this NPA-NXX. Verify that these Subscription Versions have a status
of ‘Disconnect-Pending’. (SV group 2c_________________)
d) Activate a Number Pool Block for an NPA-NXX for which this Service Provider under
test is accepting downloads, but it is another Service Provider’s Number Pool Block.
Use simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that the Pooled Subscription Versions have Number Pool Block
has a status of ‘Partial-Fail’. (SV group 2d_____________________) (NPB
2d______________)
e) Activate an uncontaminated Number Pool Block on behalf of another Service Provider.
Use simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Set a filter for this NPA-NXX on behalf of the Service Provider under
test. Verify that the Number Pool Block has a status of ‘Active’ with an empty Failed
SP List. Remove the filter for this NPA-NXX for the Service Provider under test prior
before performing following steps. (SV group e ________________), (NPB group
e_________________________)
f) Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Modify the
Number Pool Block that was activated in step e above. Verify that the Number Pool
Block has a status of ‘Sending’. (SV group f___________________), (NPB group
f_________________________) During the test case retry timers will exhaust, and
then the status of the SVs and NPB should be ‘Partial-Fail’.
The TN Range specified in the Bulk Data Download Selection Criteria should be a ‘subset’ of
the total of the TN Range used in the prerequisite steps. TN Range
_________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Subscription Data,
specifying Latest View of
Subscription Version Activity a valid
Time Range and specifying the TN
range identified in the prerequisites
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 20
above, for the Service Provider
participating in the test case. By
specifying this TN range, the
content of the BDD will actually be
a subset of the prerequisite data.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their LSMS
systems.
SP The LSMS successfully processes the Bulk Data Download
file(s) and reflects the updates described in the prerequisites
above.
The system is still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Subscription Data to verify
that the Subscription Version data
that matched the BDD criteria was
loaded.
NOTE: The BDD request was a
subset of the total TNs
manipulated in the Prerequisite
Setup above. Verify the subset of
data.
SV group a
SV group b
SV group c
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d
If the Service Provider’s EDR
Indicator is set to TRUE, SV
group d DOES NOT exist
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group f
If the Service Provider’s EDR
Indicator is set to TRUE, SV
group f DOES NOT exist
SP Using the LSMS system, verify:
NOTE: The BDD request was a subset of the total TNs
manipulated in the Prerequisite Setup above. Verify the
subset of data.
SV group a exists on the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group d DOES NOT exist on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group f exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group f DOES NOT exist on the LSMS.
4. SP After all NPAC ‘retry timers’ for
the Subscription Versions specified
in the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associate’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates with the NPAC SMS
without recovering additional information. .
5. NPAC NPAC Personnel bring the
simulated SPID LSMS that was in
recovery in Prerequisite step f
above, out of recovery.
NPAC Verify that the simulated SPID that was in recovery during step
f of the prerequisites is now out of recovery. Verify that the
number pool block and respective pooled subscription versions
that were modified while this SPID was in recovery now have a
status of ‘Active’ with a Failed SP List that includes the service
provider under test.
6. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX in
the range of TNs specified in the
prerequisites above for the Service
Provider’s LSMS to verify that all
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a exists on the LSMS.
Formatted: List Bullet, Indent: Left: 0", First line: 0", Tabstops: Not at 0.55"
Formatted: List Bullet
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 21
the appropriate updates were
processed from the Bulk Data
Download File by the LSMS.
SV group b exists on the LSMS.
SV group c exists on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group d DOES NOT exist on the LSMS.
If the Service Provider’s EDR Indicator is set to FALSE,
SV group f exists on the LSMS.
If the Service Provider’s EDR Indicator is set to TRUE, SV
group f DOES NOT exist on the LSMS.
7. NPAC NPAC Personnel ‘re-send’ the
following to the Service Provider
under test:
NOTE: The BDD request was a
subset of the total TNs
manipulated in the Prerequisite
Setup above. Resend the
respective subset of data.
SV group a that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d that exists on the
NPAC SMS with a status of
‘Partial-Fail’.
If the Service Provider’s EDR
Indicator is set to FALSE,
pooled SV group f that exists
on the NPAC SMS with a
status of ‘Active’ with a Failed
SP List that includes the service
provider under test.
NPAC SMS issues the appropriate
messages to the LSMS in order to
update the LSMS for these SVs.
SP
LSMS receives the resend requests from the NPAC SMS and
issues a ‘duplicate object’ response to the NPAC SMS for:
NOTE: The BDD request was a subset of the total TNs
manipulated in the Prerequisite Setup above. Verify the
subset of data.
SV group a
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d
If the Service Provider’s EDR Indicator is set to FALSE,
pooled SV group f
8. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX in
the following SVs to verify that all
the appropriate updates were
processed from the NPAC ‘re-send’
for the ‘Partial-Fail’ objects:
SV group a
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group d
If the Service Provider’s EDR
Indicator is set to FALSE, SV
group f
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
SV group a
If the Service Provider’s EDR Indicator is set to FALSE,
SV group d
If the Service Provider’s EDR Indicator is set to FALSE,
SV group f
Formatted: List Bullet, Indent: Left: 0", First line: 0", Tabstops: Not at 0.55"
Formatted: Bulleted + Level: 1 + Aligned at: 0" + Tabafter: 0.25" + Indent at: 0.25"
Formatted: List Bullet, Indent: Left: 0"
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 22
E. Pass/Fail Analysis, NANC 169-4 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Service Provider LSMS was able to successfully process the ‘re-send’ request from the NPAC SMS for the
‘Partial-Fail’ objects.
Note: Since the TN Range specified in the Bulk Data Download selection criteria is a subset of the test data created
in the prerequisites, the Bulk Data Download file will not contain the full set of TNs. Testers should verify this
‘subset’ of TN in the verification steps.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 23
12.2 NANC 187 – Linked Action Replies
NOTE: Service Provider’s Local SMS Linked Replies Indicator, Service Provider’s SOA Linked Replies Indicator,
NPAC Customer LSMS NPA-NXX-X Indicator, and NPAC Customer SOA NPA-NXX-X Indicator should be set to
production values for testing NANC 187 functionality.
The Service Provider and Network Data, Block Data, Subscription Version Data and Notification Data Linked
Replies Blocking Factors and Maximum Linked Recovered Objects should be set to predetermined values identified
by the test team. These parameters may not be set to ‘production or default’ values so as to be able to complete
testing in an expeditious manner.
The test data identified in the prerequisites for these test cases are recommendations to achieve the test case
objectives. Many permutations of prerequisite data may create the appropriate test scenario and thus meet the test
objective. Test Engineers should consider each Service Provider’s capabilities and tailor the test data as is
appropriate to meet the test objective and execute the test case expeditiously. For example, consider whether the
Service Provider supports NPA-NXX-X’s, Ranged Notifications and Linked Action Replies. Based on this
information, you may need to perform more or less activity to meet the test case objective.
If the Region and the Service Provider under test support PLRN, in the prerequisite set up include some PLRN SVs
and NPBs consistent with the existing prerequisite data (if a prerequisite does not already call for NPA-NXX-
Xs/NPBs don’t add PLRN NPBs to the prerequisites). Verify that the SUT is included in the “PLRN Accepted
SPID List” in their service provider profile so that they will receive PLRN information including respective
downloads and notifications. Verify this information as appropriate in the test results.
This is a recovery test case written to cover both Service Provider systems that DO and DO NOT support Linked
Replies, thus, this test case will supersede Test Case 8.1 from the NPAC SMS/Service Provider Certification &
Regression Test Plan.
NANC 187 Test Cases are written to test regular recovery. Please refer to NANC 351 Test Cases to explicitly test
SWIM recovery.
A. TEST IDENTITY
Test Case
Number:
NANC 187-1 SUT Priority: SOA N/A
LSMS Required
Objective:
LSMS – Service Provider Personnel for an LSMS submit a resynchronization request for
Service Provider Data, Network Data, Block Data, Subscription Version Data and Notification
Data by time range, over the LSMS to NPAC SMS Interface, with the Service Provider’s Local
SMS Linked Replies Indicator set to their production setting. The recovery response includes a
number of Service Provider Data objects, Network Data objects, Number Pool Block objects,
Notifications and Subscription Versions less than or equal to their respective Linked Replies
Blocking Factors. - Success
Note: Per IIS3_4_1aPart2 scenario B.7.2, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187 and NANC 297
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-85, RR6-93, RR6-97, RR6-98, RR6-99,
RR6-100, RR6-101, RR6-102, RR6-103,
RR6-90, RR6-105
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.1.1, B.7.1.2
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 24
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
Prerequisite data may be set up different depending on if this test case is being run during
Individual testing versus Group Testing. For example, during Individual Testing, if the service
provider under test does not support NPA-NXX-X’s, don’t perform any of the related tasks or
verify related data.
During Group testing, need to create prerequisite data such that you meet the test case objective.
If service providers under test don’t support Ranged Notifications for example, you will either
need to not perform the number pool block activities, or you may filter the NPA-NXX of the
number pool block data for the service provider(s) that doesn’t support Range Notifications.
1. While the LSMS is disconnected from the NPAC SMS, NPAC Personnel should perform
the following functions:
Create at least one Service Provider.
Create an LRN.
Delete an LRN for a different Service Provider.
Create an NPA-NXX.
Delete an NPA-NXX for a different Service Provider.
Activate a new Number Pool Block.
DePool an existing Number Pool Block.
Create NPA-NXX-X Information for different Service Providers.
Modify NPA-NXX-X Information for different Service Providers.
Delete NPA-NXX-X Information for different Service Providers.
Create an Inter-SP Subscription Version for a Pooled TN.
Disconnect a Pooled Ported TN.
Create an Inter-SP, Port-To-Original Subscription Version for a Pooled Ported TN.
Create a Subscription Version with the NPA-NXX created above.
Issue an activate request for an Inter-Service Provider Subscription Version.
Issue an Activate request for a range of two Inter-Service Provider Subscription
Versions, where the broadcast to the LSMSs goes to a ‘partial failure’ state.
Using an NPANXX with filters set for the LSMS under test, and using a simulator
Activate 2 ‘pending’ SVs. Verify that these subscription versions have a status of
‘Sending’.
Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Activate an
uncontaminated Number Pool Block on behalf of another Service Provider. Verify that
the Pooled SVs and NPB have a status of ‘Sending’.
2. While the LSMS is in recovery, NPAC personnel should perform the following functions:
Create an NPA-NXX.
Activate a Subscription Version.
NOTE: If the Service Provider LSMS under test supports WSMSC, Optional Data elements
and/or SV Type include these attributes in the subscription version and number pool block
processing above.
Prerequisite SP
Setup:
The Service Provider LSMS should be ‘disassociated’ from the NPAC SMS while NPAC
Personnel are performing the setup specified above.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 25
1. SP The Service Provider establishes an
association from their LSMS to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
LSMS. Once the association is established, the NPAC SMS
queues all current updates.
2. SP The LSMS issues an M-ACTION
Request lnpDownload (service
provider data) to the NPAC SMS
and specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single, normal
M-ACTION Response lnpDownload message back to the
LSMS with the Service Provider Data.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the Service Provider Data updates. The data
does not exceed the Service Provider and Network Data
Linked Replies Blocking factor, so there shall be only 1
normal message sent in this instance.
NOTE: If the Service Provider Type LSMS Indicator is set to
TRUE, the SP Type will be included in the download
information.
3. SP The LSMS issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single, normal
M-ACTION Response lnpDownload message back to the
LSMS with the Network Data.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the Network Data updates. The data does not
exceed the Service Provider and Network Data Linked
Replies Blocking factor, so there shall be only 1 normal
message sent in this instance.
4. NPAC As soon as the M-ACTION Request
is received, NPAC Personnel issue
an activate for an Intra or Inter
Service Provider Subscription
Version AND create a new NPA-
NXX, belonging to any Service
Provider.
NPAC The NPAC SMS receives the M-ACTION Requests for the
activate and NPA-NXX create. It then sends an M-ACTION
response to itself for the NPA-NXX create.
5. NPAC NPAC SMS issues an M-SET
Request to itself to set the
subscriptionVersionNPAC object
(subscription version).
NPAC NPAC SMS issues an M-SET Response to itself.
The subscription version status is set to ‘sending.’
The subscriptionVersionActivationTimeStamp and
subscriptionVersionModifiedTimeStamp are set.
6. NPAC The NPAC SMS checks to see if the
M-CREATE subscriptionVersion
can be sent to the Service Provider
LSMS
NPAC The NPAC SMS does NOT send the M-CREATE
subscriptionVersion to the Service Provider LSMS, since the
LSMS is still in recovery mode.
7. NPAC The NPAC SMS checks to see if the
M-CREATE serviceProvNPA-NXX
can be sent to the Service Provider
LSMS
NPAC The NPAC SMS does NOT send the M-CREATE
serviceProvNPA-NXX to the Service Provider LSMS, since the
LSMS is still in recovery mode.
8. SP The LSMS Service Provider issues
an M-ACTION Request
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 26
lnpDownload (subscription data) to
the NPAC SMS and specifies the
start time for the resync request.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single, normal
M-ACTION Response lnpDownload message back to the
LSMS with the Subscription Version Data.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the Subscription Version data. The data does
not exceed the Subscription Version Data Blocking factor,
so there shall be only 1 normal message sent in this
instance.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will
be included in the downloads as appropriate.
9.
condit
ional
SP The LSMS Service Provider issues
an M-ACTION Request
lnpDownload (number pool block
data) to the NPAC SMS and
specifies the resync start time.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the number pool block updates.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the number pool block updates. The data does
not exceed the Number Pool Block Data Blocking factor,
so there shall be only 1 normal message sent in this
instance.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will
be included in the downloads as appropriate.
10. SP The LSMS Service Provider issues
an M-ACTION Request
lnpNotificationRecovery
(notification data) to the NPAC
SMS and specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
11. NPAC The NPAC SMS sends the M-
EVENT-REPORT(s) to the Block
Holder SOA for a number pool
block with the SOA-Origination
flag set to TRUE whose
subscriptionFailedSP-List was just
updated due to the number pool
block download. The status
attribute value change contains the
current status and the
subscriptionFailedSP-List of the
number pool block object.
SP Block Holder SOA, to which the NPAC SMS issued an M-
EVENT-REPORT, issue an M-EVENT-REPORT Confirmation
back to the NPAC SMS.
12. SP The LSMS Service Provider issues
an M-ACTION Request
lnpRecoveryComplete to the NPAC
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and sets the resynchronization flag to ‘off’.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 27
SMS to set the resynchronization
flag to FALSE.
13. NPAC NPAC SMS issues the following
messages to the LSMS for the
requests made while the LSMS was
in recovery:
M-CREATE Request
serviceProvNPA-NXX for the
NPA-NXX that was created
during recovery.
M-CREATE Request
subscriptionVersion for the
subscription version that was
activated during recovery.
SP The service provider’s LSMS receives the requests from the
NPAC SMS for the requests that occurred during recovery and
issues the following responses:
M-CREATE Response serviceProvNPA-NXX for the
NPA-NXX that was created during recovery, indicating the
LSMS successfully received/processed the request.
M-CREATE Response subscriptionVersion for the
subscription version that was activated during recovery,
indicating the LSMS successfully received/processed the
request.
14. SP Service Provider Personnel, using
the LSMS, perform a local query for
the data updated in this test case.
SP Verify that the following updates were sent:
Service Provider create(s) based on prerequisite data; If the
Service Provider Type LSMS Indicator is set to TRUE, the
SP Type is included.
1 LRN create.
1 LRN delete.
1 NPA-NXX create.
1 NPA-NXX delete.
1 Number Pool Block activate.
1 Number Pool Block depool.
1 NPA-NXX-X create – if supported by the Service
Provider LSMS.
1 NPA-NXX-X modify – if supported by the Service
Provider LSMS.
1 NPA-NXX-X delete – if supported by the Service
Provider LSMS.
1 Pooled Ported TN disconnect.
1 First port of NPA-NXX notification.
1 Single subscription version activate.
2 subscription versions that were activated.
1 Number Pool Block activate.
1 NPA-NXX create after recovery is complete
1 Subscription Version activate after recovery is complete
Verify that the WSMSC, Optional Data elements and/or
SV Type attributes are present if the Service Provider
under test supports these attributes on their LSMS and
based on how they were specified in the prerequisite
subscription version and number pool block data.
15. NPAC NPAC Personnel perform a Full
audit for the Subscription Versions
that were activated during this test
case.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
E. Pass/Fail Analysis, NANC 187-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 28
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 29
A. TEST IDENTITY
Test Case
Number:
NANC 187-2 SUT Priority: SOA N/A
LSMS Required
Objective:
LSMS – Service Provider Personnel for an LSMS submit a resynchronization request for
Network Data, and Subscription Version Data by time range, over the LSMS to NPAC SMS
Interface, with the Service Provider’s Local SMS Linked Replies Indicator set to their
production setting. The recovery response includes a number of Network Data objects greater
than the Service Provider and Network Data Linked Replies Blocking Factor and less than the
Service Provider and Network Data Maximum Linked Recovered Objects as well as a number
of Subscription Version objects greater than the Subscription Data Linked Replies Blocking
Factor and less than the Subscription Data Maximum Linked Recovered Objects. – Success
Note: Per IIS3_4_1aPart2 scenario B.7.2, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-87, RR6-88, RR6-93, RR6-103, RR6-
90, RR6-95, RR6-104, RR6-96
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.1.1, B.7.1.2
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 30
Prerequisite
NPAC Setup:
1. While the LSMS is disconnected from the NPAC SMS, NPAC Personnel should perform
the following functions:
a) Create 10 LRNs. (LRN group a)
b) Delete 10 LRNs for a different Service Provider. (LRN group b)
c) Create 20 NPA-NXXs. (NPA-NXX group c)
d) Delete 10 NPA-NXXs for a different Service Provider. (NPA-NXX group d)
e) Activate 40 new Blocks. (NPB group e)
f) DePool 20 existing Blocks. (NPB group f)
g) Create 2 NPA-NXX-Xs for different Service Provider. (Dash X group g)
h) Modify an NPA-NXX-X for different Service Provider. (Dash X group h)
i) Delete an NPA-NXX-X for a different Service Provider. (Dash X group i)
j) Activate 20 Inter-SP Subscription Version for a Pooled TN. (SV group j)
k) Disconnect 25 Pooled Ported TN. (SV group k)
l) Activate 20 Inter-SP, Port-To-Original Subscription Version for a Pooled Ported TN.
(SV group l)
m) Create 50 Subscription Version with the NPA-NXX created above. (SV group m)
n) Issue an activate request for 20 Inter-Service Provider Subscription Version. (SV group
n)
o) Issue an Activate request for a range of 10 Inter-Service Provider Subscription Versions.
(SV group o)
p) Modify the NPA-NXX Effective Date for an NPA-NXX where the current date is less
than the existing Effective Date and no pending-like SVs, NPA-NXX-Xs or NPBs
exist for the respective NPA-NXX. (NPA-NXX group p)
2. While the LSMS is in recovery, NPAC personnel should perform the following functions:
Create an NPA-NXX.
Activate a Subscription Version.
NOTE: If the Service Provider LSMS under test supports WSMSC, Optional Data elements
and/or SV Type include these attributes in the subscription version and number pool block
processing above.
NOTE: If the Region and the Service Provider under test support PLRN, establish (some)
respective prerequisite data (PLRN SVs and NPB’s). Verify that the SUT is included in the
“PLRN Accepted SPID List” in their service provider profile so that they will receive
respective PLRN information during resynchronization including notifications and
downloads as appropriate for the test case. If the SUT is not included in the “PLRN
Accepted SPID List” they will not receive this information during resynchronization.
Prerequisite SP
Setup:
The Service Provider LSMS should be ‘disassociated’ from the NPAC SMS while NPAC
Personnel are performing the setup specified above.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP The Service Provider establishes an
association from their LSMS to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
LSMS. Once the association is established, the NPAC SMS
queues all current updates.
2. SP The LSMS issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single M-
ACTION Response lnpDownload message back to the
LSMS with the Network Data updates for
LRN group a
LRN group b
NPA-NXX group c
NPA-NXX group d
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 31
Dash X group g, if supported by the Service Provider
under test
Dash X group h, if supported by the Service Provider
under test
Dash X group i, if supported by the Service Provider
under test
Modified NPA-NXX (NPA-NXX group p)
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked
reply data) back to the LSMS with the Network Data
updates. These messages shall be linked for groups of (50)
objects – there should be 2 linked replies.
3. NPAC As soon as the M-ACTION Request
is received, NPAC Personnel issue
an activate for an Intra or Inter
Service Provider Subscription
Version (SV 3) AND create a new
NPA-NXX, belonging to any
Service Provider.
NPAC The NPAC SMS receives the M-ACTION Requests for the
activate and NPA-NXX create. It then sends an M-ACTION
response to itself for the NPA-NXX create.
4. NPAC NPAC SMS issues an M-SET
Request to itself to set the
subscriptionVersionNPAC object
(subscription version).
NPAC NPAC SMS issues an M-SET Response to itself.
The subscription version status is set to ‘sending.’
The subscriptionVersionActivationTimeStamp and
subscriptionVersionModifiedTimeStamp are set.
5. NPAC The NPAC SMS checks to see if the
M-CREATE subscriptionVersion
can be sent to the Service Provider
LSMS
NPAC The NPAC SMS does NOT send the M-CREATE
subscriptionVersion to the Service Provider LSMS, since the
LSMS is still in recovery mode.
6. NPAC The NPAC SMS checks to see if the
M-CREATE serviceProvNPA-NXX
can be sent to the Service Provider
LSMS
NPAC The NPAC SMS does NOT send the M-CREATE
serviceProvNPA-NXX to the Service Provider LSMS, since the
LSMS is still in recovery mode.
7. SP The LSMS Service Provider issues
an M-ACTION Request
lnpDownload (subscription data) to
the NPAC SMS and specifies the
start time for the resync request.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS Service Provider.
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single M-
ACTION Response lnpDownload messages back to the
LSMS with the Subscription Version Data updates for:
If non-EDR LSMS, Pooled Subscription Versions
associated with NPB group e
If non-EDR LSMS, Pooled Subscription Versions
associated with NPB group f
SV group j
SV group k
SV group l
SV group n
SV group o
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked
reply data) back to the LSMS (with the ‘non-pooled’
Subscription Version Data updates to the LSMS and pooled
and non-pooled Subscription Version Data updates to the
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 32
LSMS). This message shall be linked for groups of (50)
objects – there should be at least 3 linked replies, if the
Service Provider under test is and does not support Ranged
Notifications, there will be at least 43 linked replies. If the
service provider under test supports Ranged Notifications,
there may be fewer than 43 linked replies based on the
parameter setting.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will be
included in the downloads as appropriate.
8.
condit
ional
SP The LSMS Service Provider issues
an M-ACTION Request
lnpDownload (number pool block
data) to the NPAC SMS and
specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS:
If the Service Provider’s Local SMS Linked Replies Indicator is
set to FALSE, NPAC issues single, normal M-ACTION
Response lnpDownload message back to the with the number
pool block updates for:
NPB group e
NPB group f
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked
reply data) back to the LSMS with the number pool block
updates. These messages shall be linked for groups of (50)
objects – there should be 2 linked replies.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will
be included in the downloads as appropriate.
9.
condit
ional
SP The LSMS Service Provider issues
an M-ACTION Request
lnpNotificationRecovery
(notification data) to the NPAC
SMS and specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
10. SP The LSMS Service Provider issues
an M-ACTION Request
lnpRecoveryComplete to the NPAC
SMS to set the resynchronization
flag to FALSE.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and sets the resynchronization flag to ‘off’.
11. NPAC NPAC SMS issues the following
messages to the LSMS for the
request made while the LSMS was
in recovery:
M-CREATE Request
serviceProvNPA-NXX for the
NPA-NXX that was created
during recovery.
M-CREATE Request
subscriptionVersion for the
SP The service provider’s LSMS receives the requests from the
NPAC SMS for the requests that occurred during recovery and
issues the following responses:
M-CREATE Response serviceProvNPA-NXX for the
NPA-NXX that was created during recovery, indicating the
LSMS successfully received/processed the request.
M-CREATE Response subscriptionVersion for the
subscription version that was activated during recovery,
indicating the LSMS successfully received/processed the
request.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 33
subscription version that was
activated during recovery.
12. SP Service Provider Personnel, using
the LSMS, perform a local query for
the data updated in this test case.
SP Verify that the following updates were sent:
LRN group a was created.
LRN group b was deleted.
NPA-NXX group c was activated.
NPA-NXX group d was depooled.
On non-EDR LSMSs, Pooled Subscription Versions
associated with NPB e were created.
On non-EDR LSMSs, Pooled Subscription Versions
associated with NPB f were deleted.
NPA-NXX-X (Dash X group g) was created – if supported
by the Service Provider LSMS.
NPA-NXX-X (Dash X group h) was modified – if
supported by the Service Provider LSMS.
NPA-NXX-X (Dash X group i) was deleted – if supported
by the Service Provider LSMS.
SV group j was created/activated.
SV group k was disconnected.
SV group l was created/activated.
First port of NPA-NXX notification associated with SV
group m was sent.
SV group n was activated.
SV group o was activated.
1 NPA-NXX create after recovery is complete
SV3 was activated after recovery is complete.
Verify that the WSMSC, Optional Data elements and/or
SV Type attributes are present if the Service Provider
under test supports these attributes on their LSMS and
based on how they were specified in the prerequisite
subscription version and number pool block data.
NPA-NXX group p, to verify the Effective Date was
modified as indicated in the prerequisite data.
13. NPAC NPAC Personnel perform a Full
audit for the Subscription Versions
that were activated during this test
case.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
E. Pass/Fail Analysis, NANC 187-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 34
A. TEST IDENTITY
Test Case
Number:
NANC 187-3 SUT Priority: SOA N/A
LSMS Required
Objective:
LSMS – Service Provider Personnel for an LSMS submit a resynchronization request for
Network Data, Number Pool Block data and Subscription Version Data by time range, over the
LSMS to NPAC SMS Interface, with the Service Provider’s Local SMS Linked Replies
Indicator set to their production setting. The recovery response includes a number of Network
Data objects, Number Pool Block objects and Subscription Version objects greater than the
respective Maximum Linked Recovered Objects and Maximum Number Download Records
parameters. – Success
Note: Per IIS3_4_1aPart2 scenario B.7.2, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-95, RR6-104, RR6-106
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.1.1, B.7.1.2
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Determine the settings for the Maximum Recovered objects and then substitute the ‘X
number references following in order to exceed these parameter settings.
2. While the LSMS is disconnected from the NPAC SMS, NPAC Personnel should perform
the following functions:
a) Create 10 LRNs. (LRN group a)
b) Delete 10 LRNs for a different Service Provider. (LRN group b)
c) Create 10 NPA-NXXs. (NPA-NXX group c)
d) Delete 10 NPA-NXXs for a different Service Provider. (NPA-NXX group d)
e) Activate 20 new Blocks. (NPB group e)
f) DePool 20 existing Blocks. (NPB group f)
g) Create 5 NPA-NXX-Xs for different Service Provider. (Dash X group g)
h) Modify 5 NPA-NXX-X for different Service Provider. (Dash X group h)
i) Delete 5 NPA-NXX-X for a different Service Provider. (Dash X group i)
j) Activate 25 Inter-SP Subscription Version for a Pooled TN. (SV group j)
k) Disconnect 25 Pooled Ported TN. (SV group k)
l) Activate 25 Inter-SP, Port-To-Original Subscription Version for a Pooled Ported TN.
(SV group l)
m) Create 1 Subscription Version with the NPA-NXX created above. (SV group m)
n) Issue an activate request for 25 Inter-Service Provider Subscription Version. (SV group
n)
0) Issue an Activate request for a range of 25 Inter-Service Provider Subscription Versions.
(SV group 0)
NOTE: If the Service Provider LSMS under test supports WSMSC, Optional Data elements
and/or SV Type include these attributes in the subscription version and number pool block
processing above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 35
Prerequisite SP
Setup:
The Service Provider LSMS should be ‘disassociated’ from the NPAC SMS while NPAC
Personnel are performing the setup specified above.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP The Service Provider establishes an
association from their LSMS to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
LSMS. Once the association is established, the NPAC SMS
queues all current updates.
2. SP The LSMS issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and determines that for the time range requested, the
Network Data exceeds the Service Provider and Network Data
Maximum Recovered Objects parameter (if the service provider
supports linked replies) or the Maximum Number of Download
Records (if the service provider does not support linked
replies). The NPAC SMS issues an M-ACTION Response
lnpDownload, Criteria-too-large to the requesting LSMS.
3. SP After receiving the M-ACTION
Response ‘Criteria-to-large’ the
LSMS issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies a smaller time range (than
that indicated in row 2 above) for
the resync request.
Note: Row 2 may occur over and
over until the M-ACTION Request
indicates a time range that yields
data less than the ‘Service Provider
and Network Data Maximum
Linked Recovered Objects’ for
service provider’s that support
Linked Replies – or less than the
Maximum Number of Download
Records for those service provider’s
that don’t support Linked Replies.
NPAC Once the NPAC SMS receives an M-ACTION request that
specifies time range that yields an amount of data less than the
‘Service Provider and Network Data Maximum Linked
Recovered Objects’ for service provider’s that support Linked
Replies, or less than the ‘Maximum Number of Download
Records’ for service provider’s that don’t support Linked
Replies:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single M-
ACTION Response lnpDownload message back to the
LSMS with the Network Data updates for
LRN group a
LRN group b
NPA-NXX group c
NPA-NXX group d
Dash X group g, if supported by the Service Provider
under test
Dash X group h, if supported by the Service Provider
under test
Dash X group i, if supported by the Service Provider
under test
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked reply
data) back to the LSMS with the Network Data updates. These
messages shall be linked for groups of (50) objects – there
should be 2 linked replies.
4. SP The LSMS Service Provider issues
an M-ACTION Request
lnpDownload (subscription data) to
the NPAC SMS and specifies the
start time for the resync request.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and determines that for the time range requested, the
Subscription Version data exceeds the Subscription Version
Data Maximum Recovered Objects parameter (if the service
provider supports linked replies) or the Maximum Number of
Subscription Records (if the service provider does not support
linked replies). The NPAC SMS issues an M-ACTION
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 36
Response lnpDownload, Criteria-too-large to the requesting
LSMS.
5. SP After receiving the M-ACTION
Response ‘Criteria-to-large’ the
LSMS issues an M-ACTION
Request lnpDownload (subscription
data) to the NPAC SMS and
specifies a smaller time range (than
that indicated in row 4 above) for
the resync request.
Note: Row 4 may occur over and
over until the M-ACTION Request
indicates a time range that yields
data less than the ‘Subscription Data
Maximum Linked Recovered
Objects’ for service provider’s that
support Linked Replies – or less
than the Maximum Number of
Subscription Records for those
service provider’s that don’t support
Linked Replies.
NPAC Once the NPAC SMS receives an M-ACTION request that
specifies time range that yields an amount of data less than the
‘Subscription Data Maximum Linked Recovered Objects’ for
service provider’s that support Linked Replies, or less than the
‘Maximum Number of Subscription Records’ for service
provider’s that don’t support Linked Replies:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single M-
ACTION Response lnpDownload message back to the
LSMS with the Network Data updates for
If non-EDR LSMS, Pooled Subscription Versions
associated with NPB group e
If non-EDR LSMS, Pooled Subscription Versions
associated with NPB group f
SV group j
SV group k
SV group l
SV group n
SV group o
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked
reply data) back to the LSMS with the Subscription
Version Data updates. This message shall be linked for
groups of (50) objects – For the EDR LSMS there should
be at least 3 linked replies of non-pooled subscription
version data, if the Service Provider under test is non-EDR
and does not support Ranged Notifications, there will be at
least 43 linked replies. If the service provider under test
supports Ranged Notifications, there may be fewer than 43
linked replies based on the parameter setting.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will
be included in the downloads as appropriate.
6. SP The LSMS Service Provider issues
an M-ACTION Request
lnpDownload (number pool block
data) to the NPAC SMS and
specifies the resync start time.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and determines that for the time range requested, the
Number Pool Block data exceeds the Number Pool Block Data
Maximum Recovered Objects parameter (if the service provider
supports linked replies) or the Maximum Number of Download
Records (if the service provider does not support linked
replies). The NPAC SMS issues an M-ACTION Response
lnpDownload, Criteria-too-large to the requesting LSMS.
7. SP After receiving the M-ACTION
Response ‘Criteria-to-large’ the
LSMS issues an M-ACTION
Request lnpDownload (number pool
block data) to the NPAC SMS and
specifies a smaller time range (than
that indicated in row 6 above) for
the resync request.
NPAC Once the NPAC SMS receives an M-ACTION request that
specifies a time range that yields an amount of data less than
the ‘Number Pool Block Data Maximum Linked Recovered
Objects’ for service provider’s that support Linked Replies, or
less than the ‘Maximum Number of Download Records’ for
service provider’s that don’t support Linked Replies:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues a single M-
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 37
Note: Row 4 may occur over and
over until the M-ACTION Request
indicates a time range that yields
data less than the ‘Number Pool
Block Data Maximum Linked
Recovered Objects’ for service
provider’s that support Linked
Replies – or less than the Maximum
Number of Download Records for
those service provider’s that don’t
support Linked Replies.
ACTION Response lnpDownload message back to the
LSMS with the Network Data updates for
NPB group e
NPB group f
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues multiple, linked M-
ACTION replies, lnpDownload, followed by a non-linked,
empty, normal response (indicating the end of the linked
reply data) back to the EDR LSMS with the number pool
block updates. These messages shall be linked for groups of
(50) objects – there should be 2 linked replies.
NOTE: If the Service Provider LSMS supports WSMSC,
Optional Data elements and/or SV Type, these attributes will be
included in the downloads as appropriate.
8.
condit
ional
SP The LSMS Service Provider issues
an M-ACTION Request
lnpNotificationRecovery
(notification data) to the NPAC
SMS and specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS:
1) If the Service Provider’s Local SMS Linked Replies
Indicator is set to FALSE, NPAC issues single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
2) If the Service Provider’s Local SMS Linked Replies
Indicator is set to TRUE, NPAC issues a single, normal M-
ACTION Response lnpDownload message back to the
LSMS with the notification updates.
9. SP The LSMS Service Provider issues
an M-ACTION Request
lnpRecoveryComplete to the NPAC
SMS to set the resynchronization
flag to FALSE.
NPAC The NPAC SMS receives the M-ACTION Request from the
LSMS and replies back to the LSMS with data updates at the
next scheduled interval for the NPA-NXX that was created
during resynchronization and the Subscription Version that was
activated during resynchronization.
10. SP The LSMS receives the M-ACTION
Response from the NPAC SMS..
11. NPAC NPAC Personnel verify that no data
was sent in the initial action
responses for the network data,
subscription data and number pool
block data requests from the
LSMS..
NPAC Verify that no data was sent in the initial action responses sent
for network data, subscription data and number pool block data
request from the LSMS.
Note to Test Engineers: NPAC Personnel may watch the router
of the service provider under test to verify the 1st request for
data types (network data, subscription data and number pool
block data) result in a ‘criteria-too-large’ response.
E. Pass/Fail Analysis, NANC 187-3 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 38
This is a recovery test case written to cover both Service Provider systems that DO and DO NOT support Linked
Replies, thus, this test case will supersede TC 8.3 from the NPAC SMS/Service Provider Certification & Regression
Test Plan
A. TEST IDENTITY
Test Case
Number:
NANC 187-4 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel submit a resynchronization request for Service Provider
Data, Network Data and Notification Data by time range, over the SOA to NPAC SMS
Interface, with the Service Provider’s SOA Linked Replies Indicator set to their production
setting. The recovery response includes a number of Service Provider Data objects, and
Network Data objects less than or equal to the Service Provider and Network Data Linked
Replies Blocking Factor and a number of Notifications less than or equal to the Notification
Data Linked Replies Blocking Factor. – Success
Note: Per IIS3_4_1aPart2 scenario B.7.3, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-92, RR6-89
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.2
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 39
Prerequisite
NPAC Setup:
Prerequisite data may be set up different depending on if this test case is being run during
Individual testing versus Group Testing. For example, during Individual Testing, if the service
provider under test does not support NPA-NXX-X’s, don’t perform any of the related tasks or
verify related data.
1) While the SOA is disconnected from the NPAC SMS, NPAC Personnel should perform the
following functions for data within the time range to be‘:
Create at least one Service Provider.
Create an LRN.
Delete an LRN for a different Service Provider.
Create an NPA-NXX.
Delete an NPA-NXX for a different Service Provider.
Create NPA-NXX-X Information for different Service Providers.
Modify NPA-NXX-X Information for different Service Providers.
Delete NPA-NXX-X Information for different Service Providers.
Activate a Block on behalf of the Service Provider that is ‘down’ with SOA
Origination TRUE. If the SOA under test supports SV Type and/or Optional Data
elements include these attributes in the NPB.
Create a Subscription Version with the NPA-NXX created above on behalf of the Old
Service Provider and where the Service Provider Under Test is the New Service
Provider; let the Initial and Final Concurrence timers expire.
Issue a Scheduled Downtime Notification.
Issue an immediate disconnect for a subscription version where the Service Provider
Under Test is the Donor Service Provider.
Issue a Cancel request for a pending Inter-Service Provider Subscription Version for
which both service providers have concurred to the pending port, on behalf of the
Service Provider Under Test, let the Cancellation Initial Concurrence Timer expire.
Issue a Create request for a range of two pending subscription versions that were
initially created by the New Service Provider, on behalf of the Old Service Provider,
where the Authorization Flag is set to “False” and provide a Cause Code.
Issue an activate request for an Inter-Service Provider Subscription Version on behalf
of the Service Provider Under Test.
Issue an Activate request for a range of two Inter-Service Provider Subscription
Versions where a broadcast to the LSMSs goes into a Partial Failure status.
2) While the SOA is in recovery, NPAC personnel should perform the following functions:
Create an NPA-NXX.
Activate a Subscription Version as the Service Provider Under Test.
NOTE: If the Service Provider SOA supports Optional Data elements and/or SV Type, these
attributes will be included in the Number Pool Block and Subscription Version prerequisite
steps above; these attributes will be appropriately included in the notifications recovered.
NOTE: If the Service Provider under test supports Medium Timer Indicator, perform the
respective prerequisite Subscription Version create requests including the MTI indicator; this
attribute will be included in the appropriate notifications recovered.
Prerequisite SP
Setup:
The service provider SOA should be ‘disassociated’ from the NPAC SMS while NPAC
Personnel are performing the setup specified above
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 40
1. SP The Service Provider establishes an
association from their SOA to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
SOA. Once the association is established, the NPAC SMS
queues all current updates.
2. SP The SOA issues an M-ACTION
Request lnpDownload (service
provider data) to the NPAC SMS
and specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION.
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single, normal M-ACTION
Response lnpDownload messages back to the SOA with
the Service Provider Data.
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues a single, normal M-ACTION
Response lnpDownload message back to the SOA with the
Service Provider Data updates. The data does not exceed
the Service Provider and Network Data Linked Replies
Blocking factor, so there shall be only 1 message sent in
this instance.
NOTE: If the Service Provider Type SOA Indicator is set to
TRUE, the SP Type will be included in the downloaded
information.
3. SP The SOA issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION.
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single, normal M-ACTION
Response lnpDownload messages back to the SOA with
the Network Data.
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues a single, normal M-ACTION
Response lnpDownload message back to the SOA with the
Network Data updates. The data does not exceed the
Service Provider and Network Data Linked Replies
Blocking factor, so there shall be only 1 message sent in
this instance.
4. NPAC As soon as the M-ACTION Request
is received, NPAC Personnel issue a
create for an NPA-NXX.
NPAC The NPAC SMS receives the M-CREATE Request
serviceProvNPA-NXX.
5. NPAC The NPAC SMS checks to see if the
M-CREATE servProvNPA-NXX
can be sent to the SOA in recovery.
NPAC The NPAC SMS does NOT issue the M-CREATE
servProvNPA-NXX to the SOA since the SOA is still in
recovery.
6. NPAC NPAC Personnel issue an SV
activate request.
NPAC The NPAC SMS receives the M-ACTION Request.
The NPAC SMS issues an M-SET Request to itself and sets the
SV’s status to ‘sending.’
The NPAC SMS issues an M-SET Response to itself.
7. NPAC The NPAC SMS checks to see if the
M-ACTION
subscriptionVersionActivate can be
sent to the SOA in recovery.
NPAC The NPAC SMS does NOT issue the M-ACTION
subscriptionVersionActivate to the SOA since the SOA is still
in recovery.
8. NPAC The NPAC SMS checks to see if the
M-EVENT-REPORT
objectCreation can be sent to the
SOA in recovery.
NPAC The NPAC SMS does NOT issue the M-EVENT-REPORT
objectCreation to the SOA since the SOA is still in recovery.
9. SP The SOA Service Provider issues an
M-ACTION Request
lnpNotificationRecovery
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 41
(notification data) to the NPAC
SMS and specifies a time range.
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single, normal M-ACTION
Response lnpDownload messages back to the SOA with
the Notification updates.
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues a single, normal M-ACTION
Response lnpDownload message back to the SOA with
Notification updates. The data does not exceed the
Notification Data Blocking factor, so there shall be only 1
message sent in this instance.
NOTE: If the Service Provider SOA supports Optional Data
elements and/or SV Type, these attributes will be included in
the numberPoolBlock-objectCreation and subscriptionVersion-
objectCreation notifications recovered.
NOTE: If the Service Provider under test supports Medium
Timer Indicator, perform the respective prerequisite SV create
requests including the MTI indicator; this attribute will be
included in the subscriptionVersion-objectCreation (including
Range) notifications.
10. SP The SOA Service Provider issues an
M-ACTION Request lnpRecovery
to the NPAC SMS to set the
resynchronization flag to FALSE.
NPAC The NPAC SMS receives the M-ACTION Request from
the SOA and sets the resynchronization flag to ‘off’.
11. NPAC NPAC SMS issues the following
messages to the SOA for the request
made while the SOA was in
recovery:
M-CREATE Request
serviceProvNPA-NXX for the
NPA-NXX that was created
during recovery.
The NPAC SMS will issue,
depending upon the new
service provider’s TN Range
Notification Indicator, a
subscriptionVersionStatusAttri
buteValueChange or
subscriptionVersionRangeStatu
sAttributeValueChange M-
EVENT-REPORT notifications
to the new service provider
SOA of the status change using
an M-EVENT-REPORT
subscriptionVersionStatusAttri
buteValueChange
SP The service provider’s SOA receives the requests from the
NPAC SMS for the requests that occurred during recovery and
issues the following responses:
M-CREATE Response serviceProvNPA-NXX for the
NPA-NXX that was created during recovery, indicating the
SOA successfully received/processed the request.
M-EVENT-REPORT Confirmation for the subscription
version that NPAC personnel activated on behalf of the
service provider during recovery, indicating the SOA
successfully received the M-EVENT-REPORT.
12. SP The SOA receives the M-ACTION
Response from the NPAC SMS
with the data updates since the
association was re-established.
13. NPAC NPAC Personnel verify the data
was sent in the action response.
NPAC Verify that the appropriate data was sent.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 42
14. SP Service Provider Personnel, using
the SOA, perform a local query for
the actions taken in this test case.
SP Verify that the following updates were made:
Service Provider create(s) based on prerequisite data; If
the Service Provider Type SOA Indicator is set to TRUE,
the SP Type will be included.
1 LRN create.
1 LRN delete.
1 NPA-NXX create.
1 NPA-NXX delete.
1 NPA-NXX-X create – if supported by the Service
Provider SOA.
1 NPA-NXX-X modify – if supported by the Service
Provider SOA.
1 NPA-NXX-X delete – if supported by the Service
Provider SOA.
1 First port of NPA-NXX notification.
1 numberPoolBlock-objectCreation including SV Type
and/or Optional Data elements– if the SOA under test
supports blocks and these attributes.
objectCreation notification and for the SV created where
SP under test is NSP.
1 Scheduled Downtime notification.
statusAttributeValueChange notification for the immediate
disconnect initiated during prerequisite steps.
statusAttributeValueChange notification for the SV
canceled during prerequisite steps.
attributeValueChange notification (or range notification
depending on whether the SP under test supports range
notifications) for the SV range created by the OSP in
response to a NSP (SUT) create during prerequisite steps.
statusAttributeValueChange for the SV activate indicated
in the prerequisite steps.
1 NPA-NXX create after recovery is complete
1 Subscription Version activate after recovery is complete
E. Pass/Fail Analysis, NANC 187-4 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 43
A. TEST IDENTITY
Test Case
Number:
NANC 187-5 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel submit a resynchronization request for Network Data and
Notification Data by time range, over the SOA to NPAC SMS Interface, with the Service
Provider’s SOA Linked Replies Indicator set to their production setting. The recovery response
includes a number of Network Data objects and Notifications greater than the respective Linked
Replies Blocking Factor and less than the respective Maximum Linked Recovered Notifications.
– Success
Note: Per IIS3_4_1aPart2 scenario B.7.3, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-85, RR6-86, RR6-84, RR6-92, RR6-89,
RR6-94, RR6-91
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.3
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 44
Prerequisite
NPAC Setup:
Prerequisite data may be set up different depending on if this test case is being run during
Individual testing versus Group Testing in order to meet test case objectives.
Evaluate each service provider’s capabilities and tailor the prerequisite data to meet the test case
objective. Consider which category the service provider under test fits into:
The service provider under test does not support linked replies or ranged notifications.
The service provider under test supports linked replies but does not support ranged
notifications.
The service provider under test supports linked replies and ranged notifications.
Set the Service Provider and Network Data Blocking Factor parameter to a low number (for
example 5 – to create linked replies based on the network data in the prerequisites that follow).
While the SOA is disconnected from the NPAC SMS, NPAC Personnel should perform the
following functions for data within the time range to be resync’d:
a) Activate a Block on behalf of the Service Provider that is ‘down’ with SOA
Origination TRUE. If the SOA under test supports SV Type and/or Optional Data
elements attributes include these in the number pool block. (NPB group a)
b) Create a range of 10 Subscription Versions on behalf of the Old Service Provider and
where the Service Provider Under Test is the New Service Provider; let the Initial
Concurrence timer expire. When you create, do this in two ranges, where the last half
of the TNs in the range is the first range that you create. In a second request, create
the first half of the TNs in the range. (SV group b2 and SV group b1)
c) Issue a Scheduled Downtime Notification.Deleted.
d) Issue an immediate disconnect for 20 subscription versions where the Service Provider
Under Test is the Donor Service Provider. (SV group d)
e) Issue a Cancel request for each subscription version in a range of 10 pending Inter -
Service Provider Subscription Versions for which both service providers have
concurred to the pending port, on behalf of the Service Provider Under Test, let each
Cancellation Initial Concurrence Timer expire for each of the TNs that were cancelled.
(SV group e)
f) On behalf of the service provider under test, acting as the Old service provider, issue a
Create request for a range of 20 pending subscription versions that were initially
created by the New Service Provider, where the Authorization Flag is set to “False”
and provide a Cause Code. ( SV group f)
g) After the Initial Concurrence Timer has expired, but prior to the Final Concurrence
Timer expiration, on behalf of the service provider under test, where they are the
‘New’ service provider, concur to the range created in (b) above. (SV group g
______________).
h) Create 10 LRNs. (LRN group h)
i) Create 15 NPA-NXXs. (NPA-NXX group i)
j) Modify the NPA-NXX Effective Date for an NPA-NXX where the current date is less
than the existing Effective Date and no pending-like SVs, NPA-NXX-Xs or NPBs
exist for the respective NPA-NXX. (NPA-NXX group j)
k) If the SUT’s, S-3.00 C, Attribute Value Change, For Mass Update of Active SVs and
NPBs notification priority is set to a value other than NONE, issue a Mass Update for
non-pooled Subscription Versions and NPBs/pooled Subscription Versions. (SV/NPB
group k)
NOTE: If the Service Provider SOA supports Optional Data elements and/or SV Type, these
attributes will be included in the Number Pool Block and Subscription Version prerequisite steps
above; these attributes will be appropriately included in the notifications recovered.
NOTE: If the Service Provider under test supports Medium Timer Indicator, perform the
respective prerequisite Subscription Version create requests including the MTI indicator; this
attribute will be included in the appropriate notifications recovered.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 45
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP The Service Provider establishes an
association from their SOA to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
SOA. Once the association is established, the NPAC SMS
queues all current updates.
2.
condit
ional
SP The SOA issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA:
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues single, normal M-ACTION
Response lnpDownload message back to the SOA with the
network data updates for
LRN group h
NPA-NXX group i
Modified NPA-NXX (NPA-NXX group j).
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues multiple, linked M-ACTION
replies, lnpDownload followed by a non-linked, empty,
normal response (indicating the end of the linked reply
data) back to the SOA with the network data updates.
These messages shall be linked for groups of (5) objects
(based on the special Service Provider and Network Data
Linked Replies Blocking Factor setting for this test case) –
there should be 5 linked replies.
3. SP The SOA Service Provider issues an
M-ACTION Request
lnpNotificationRecovery
(notification data) to the NPAC
SMS and specifies a time range.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA.
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single, normal M-ACTION
Response lnpDownload message back to the SOA with the
Notification updates.
Number Pool Block object Creation Notification for (NPB
group a). If the SOA under test supports SV Type and/or
Optional Data elements these attributes are included in the
notification.
Subscription Version New SP Create Request Notification
or if the SOA supports ranges, Subscription Version Range
New SP-Create Request for (SV group b)
Downtime Notification
Subscription Version Donor SP – Customer Disconnect
Date or if the SOA supports ranges, Subscription Version
Range Donor SP – Customer Disconnect Date for (SV
group d)
Subscription Version Status Attribute Value Change
Notification for (SV group e)
Subscription Version Status Attribute Value Change or if
the SOA supports ranges, Subscription Version Range
Status Attribute Value Change for (SV group f)
Subscription Version Status Attribute Value Change or if
the SOA supports ranges, Subscription Version Range
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 46
Status Attribute Value Change with a SVID list for (SV
group g2 and SV group g1)
NOTE: If the SUT’s S-3.00 C Attribute Value Change for
Mass Update of Active SVs and NPBs notification priority is
set to a value other than NONE, they will receive M-EVENT-
REPORT AttributeValueChange notifications for the modified
attributes. This will be a
subscriptionVersionAttributeValueChange for the non-pooled
Subscription Versions and/or
numberPoolBlockAttributeValueChange to the Current/Block Holder Service Provider if the numberPoolBlockSOA-
OriginationIndicator is set to TRUE. (SV/NPB group k)
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues multiple, linked M-ACTION
replies, lnpDownload, followed by a non-linked, empty,
normal response (indicating the end of the linked reply
data) back to the SOA with Notification updates. The data
does exceeds the Notification Data Blocking factor, so
there shall be at least (2) messages sent in this instance.
NOTE: If the Service Provider SOA supports Optional Data
elements and/or SV Type, these attributes will be included in
the appropriate Number Pool Block and Subscription Version
notifications.
NOTE: If the Service Provider under test supports Medium
Timer Indicator, this attribute will be included in the
appropriate notifications.
4. SP The SOA Service Provider issues an
M-ACTION Request lnpRecovery
to the NPAC SMS to set the
resynchronization flag to FALSE.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA and sets the resynchronization flag to ‘off’.
5. There weren’t any actions taken
while the Service Provider was in
recovery so there aren’t any
subsequent actions to
send/receive/or verify.
6. SP Service Provider Personnel, using
the SOA, perform a local query for
the actions taken in this test case.
SP Verify that the notifications were received:
Number Pool Block object Creation Notification for (NPB
group a). If the SOA under test supports SV Type and/or
Optional Data elements these attributes are included in the
notification.
Subscription Version New SP Create Request Notification
or if the SOA supports ranges, Subscription Version Range
New SP Create Request for (SV group b)
Downtime Notification
Subscription Version Donor SP – Customer Disconnect
Date or if the SOA supports ranges, Subscription Version
Range Donor SP – Customer Disconnect Date for (SV
group d)
Subscription Version Status Attribute Value Change
Notification for (SV group e)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 47
Subscription Version Status Attribute Value Change or if
the SOA supports ranges, Subscription Version Range
Status Attribute Value Change for (SV group f)
Subscription Version Status Attribute Value Change or if
the SOA supports ranges, Subscription Version Range
Status Attribute Value Change with a SVID list for (SV
group g2 and SV group g1)
If the SUT’s S-3.00 C Attribute Value Change for Mass
Update of Active SVs and NPBs notification priority is set
to a value other than NONE, they will receive M-EVENT-
REPORT AttributeValueChange notifications for the
modified attributes. This will be a
subscriptionVersionAttributeValueChange for the non-
pooled Subscription Versions and/or
numberPoolBlockAttributeValueChange to the
Current/Block Holder Service Provider if the
numberPoolBlockSOA-OriginationIndicator is set to
TRUE. (SV/NPB group k)
Verify the following network data changes are reflected:
LRN group h was created
NPA-NXX group i was created
NPA-NXX group j reflects the modified NPA-NXX
Effective Date
NOTE: If the Service Provider SOA supports Optional Data
elements and/or SV Type, these attributes will be included in
the Number Pool Block and Subscription Version prerequisite
steps above; these attributes will be appropriately included in
the notifications recovered
NOTE: If the Service Provider under test supports Medium
Timer Indicator, perform the respective prerequisite
Subscription Version create requests including the MTI
indicator; this attribute will be included in the appropriate
notifications recovered.
E. Pass/Fail Analysis, NANC 187-5 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 48
A. TEST IDENTITY
Test Case
Number:
NANC 187-6 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel submit a resynchronization request for Network Data and
Notification Data by time range, over the SOA to NPAC SMS Interface, with the Service
Provider’s SOA Linked Replies Indicator set to their production setting. The recovery response
includes a number of Network Data objects greater than the Service Provider and Network Data
Maximum Linked Recovered Objects and Notifications greater than the Notification Data
Maximum Linked Recovered Notifications and Maximum Number of Download Records. –
Success
Note: Per IIS3_4_1aPart2 scenario B.7.3, this flow is not available over the XML interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 187
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR6-94, RR6-91
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.7.2
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 49
Prerequisite
NPAC Setup:
1) Decide what the Notification Data Maximum Linked Recovered Notifications setting
should be for this test case and then substitute the ‘X number references’ following in order
to exceed this parameter setting.
2) Decide what the Service Provider and Network Data Maximum Linked Recovered Objects
setting should be for this test case and then substitute the ‘X number references’ following
in order to exceed this parameter setting.
3) While the SOA is disconnected from the NPAC SMS, NPAC Personnel should perform the
following functions for data within the time range to be resync’d:
a) Create X number Subscription Versions on behalf of the Old Service Provider and
where the Service Provider Under Test is the New Service Provider; let the Initial
Concurrence timer expire. (SV group a)
b) Modify X number of Subscription Versions on behalf of the Old Service Provider, the
Service Provider under test, setting authorization to false with a valid cause code (SV
group b)
c) Issue an immediate disconnect for X number subscription versions where the Service
Provider Under Test is the Donor Service Provider. (SV group c).
d) Activate a Number Pool Block on behalf of the Service Provider under test. (NPB
group d) (If the SOA under test supports SV Type and/or Optional Data elements
include these attributes in the number pool block.
e) Issue a Cancel request for a range of X number pending Inter-Service Provider
Subscription Version for which both service providers have concurred to the pending
port, on behalf of the Service Provider Under Test, let the Cancellation Initial
Concurrence Timer expire. (SV group e)
f) Issue a Create request for a range of 20 pending subscription versions that were
initially created by the New Service Provider, on behalf of the Old Service Provider,
where the Authorization Flag is set to “False” and provide a Cause Code. ( SV group
f)
g) Create X number of LRNs on behalf of the service provider under test. (LRN group g)
h) Create X number of NPA-NXXs on behalf of the service provider under test. (NPA-
NXX group h).
NOTE: If the Service Provider SOA supports Optional Data elements and/or SV Type, these
attributes will be included in the Number Pool Block and Subscription Version prerequisite
steps above; these attributes will be appropriately included in the notifications recovered.
NOTE: If the Service Provider under test supports Medium Timer Indicator, perform the
respective prerequisite Subscription Version create requests including the MTI indicator; this
attribute will be included in the appropriate notifications recovered.
Prerequisite SP
Setup:
The service provider SOA should be ‘disassociated’ from the NPAC SMS while NPAC
Personnel are performing the setup specified above
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP The Service Provider establishes an
association from their SOA to the
NPAC SMS with the
resynchronization flag set to TRUE.
NPAC The NPAC SMS receives the association bind request from the
SOA. Once the association is established, the NPAC SMS
queues all current updates.
2. SP The SOA issues an M-ACTION
Request lnpDownload (network
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA and determines that for the time range requested, the
Network Data exceeds the Service Provider and Network Data
Maximum Recovered Objects parameter (if the service provider
supports linked replies) or the Maximum Number of Download
Records (if the service provider does not support linked
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 50
replies). The NPAC SMS issues an M-ACTION Response
lnpDownload, Criteria-too-large to the requesting SOA.
3. SP After receiving the M-ACTION
Response ‘Criteria-to-large’ the
SOA issues an M-ACTION Request
lnpDownload (network data) to the
NPAC SMS and specifies a smaller
time range (than that indicated in
row 2 above) for the resync request.
Note: Row 2 may occur over and
over until the M-ACTION Request
indicates a time range that yields
data less than the ‘Service Provider
and Network Data Maximum
Linked Recovered Objects’ for
service provider’s that support
Linked Replies – or less than the
Maximum Number of Download
Records for those service provider’s
that don’t support Linked Replies.
NPAC Once the NPAC SMS receives an M-ACTION request that
specifies time range that yields an amount of data less than the
‘Service Provider and Network Data Maximum Linked
Recovered Objects’ for service provider’s that support Linked
Replies, or less than the ‘Maximum Number of Download
Records’ for service provider’s that don’t support Linked
Replies:
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single M-ACTION
Response lnpDownload message back to the SOA with the
Network Data updates for
LRN group g
NPA-NXX group h
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues multiple, linked M-ACTION
replies, lnpDownload, followed by a non-linked, empty, normal
response (indicating the end of the linked reply data) back to
the LSMS with the Network Data updates. These messages
shall be linked for groups of (X) objects – there should be ( X
)linked replies.
4. SP The SOA issues an M-ACTION
Request lnpDownload (notification
data) to the NPAC SMS and
specifies the time range for the
resync request.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA and determines that for the time range requested, the
Notification Data exceeds the Notification Data Maximum
Recovered Notifications parameter (if the service provider
supports linked replies) or the Maximum Number of Download
Records (if the service provider does not support linked
replies). The NPAC SMS issues an M-ACTION Response
lnpDownload, Criteria-too-large to the requesting SOA.
5. SP After receiving the M-ACTION
Response ‘Criteria-to-large’ the
SOA issues an M-ACTION Request
lnpDownload (notification data) to
the NPAC SMS and specifies a
smaller time range (than that
indicated in row 2 above) for the
resync request.
Note: Row 4 may occur over and
over until the M-ACTION Request
indicates a time range that yields
data less than the ‘Notification Data
Maximum Linked Recovered
Notifications’ for service provider’s
that support Linked Replies – or less
than the Maximum Number of
Download Records for those service
provider’s that don’t support Linked
Replies.
NPAC Once the NPAC SMS receives an M-ACTION request that
specifies time range that yields an amount of data less than the
‘Notification Data Maximum Linked Recovered Notifications
for service provider’s that support Linked Replies, or less than
the ‘Maximum Number of Download Records’ for service
provider’s that don’t support Linked Replies:
1) If the Service Provider’s SOA Linked Replies Indicator is
set to FALSE, NPAC issues a single M-ACTION
Response lnpDownload message back to the SOA with the
Notification Data updates for
Subscription Version New SP Create Request
Notification or if the SOA supports ranges,
Subscription Version Range New SP Create Request
for (SV group a)
Subscription Version Status Attribute Value Change or
if the SOA supports ranges, Subscription Version
Range Status Attribute Value Change for (SV group b)
Subscription Version Status Attribute Value Change or
if the SOA supports ranges, Subscription Version
Range Status Attribute Value Change for (SV group c)
If SOA Origination is marked as TRUE, Number Pool
Block object Creation notification for (NPB group d).
If the SOA under test supports SV Type and/or
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 51
Optional Data elements these attributes are included in
the notification.
Subscription Version Status Attribute Value Change or
if the SOA supports ranges, Subscription Version
Range Status Attribute Value Change for (SV group e)
Subscription Version Status Attribute Value Change or
if the SOA supports ranges, Subscription Version
Range Status Attribute Value Change for (SV group f)
2) If the Service Provider’s SOA Linked Replies Indicator is
set to TRUE, NPAC issues multiple, linked M-ACTION
replies, lnpDownload, followed by a non-linked, empty, normal
response (indicating the end of the linked reply data) back to
the LSMS with the Notification Data updates. These messages
shall be linked for groups of (X) objects – there should be (X)
linked replies.
NOTE: If the Service Provider SOA supports Optional Data
elements and/or SV Type, these attributes will be included in
the appropriate Number Pool Block and Subscription Version
notifications.
NOTE: If the Service Provider under test supports Medium
Timer Indicator, this attribute will be included in the
appropriate notifications.
6. SP The SOA Service Provider issues an
M-ACTION Request
lnpRecoveryComplete to the NPAC
SMS to set the resynchronization
flag to FALSE.
NPAC The NPAC SMS receives the M-ACTION Request from the
SOA and replies back to the SOA with data updates at the next
scheduled interval for the NPA-NXX that was created during
resynchronization and the Subscription Version that was
activated during resynchronization.
7. SP The SOA receives the M-ACTION
Response from the NPAC SMS.
8.. NPAC NPAC Personnel verify that no data
was sent in the initial action
response for notification data.
NPAC Verify that no data was sent in the initial action response for
notification data.
Note to Test Engineers: NPAC Personnel may watch the router
of the service provider under test to verify the 1st request for
notification data resulted in a ‘criteria-too-large’ response.
E. Pass/Fail Analysis, NANC 187-6 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 52
12.3 NANC 191 DPC/SSN Value Edits and NANC 291 SSN Edits in the NPAC SMS
NOTE: Identify combinations of valid/invalid DPC/SSN values for each Service Provider under test for a
minimum of CNAM, CLASS, ISVM and LIDB even if the Service Provider under test does not support all of these
enhanced features in production. If the Service Provider supports WSMSC data – this must also be included in the
NANC 191/291 test case test data suite.
Service Provider’s whose systems cannot create the ‘failure’ scenarios that follow pass those test cases be default. If
their system does not ‘stop’ the invalid message before it goes across the interface, then their system must be able to
successfully execute the test case and handle the failure response from the NPAC SMS.
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-1 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to create a Subscription Version specifying some
valid and some invalid DPC/SSN information. The regional SSN Edit Flags (CLASS, LIDB,
CNAM, ISVM and WSMSC) are set to production values. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-380, RR3-381, RR3-382, RR3-383,
RR3-384, RR3-385, RR3-386, RR3-387,
RR3-388, RR3-389, RR3-375, RR3-376,
RR3-377, RR3-378, RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.1.2
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify the NPA-NXX exists and is open for porting for the TN that is going to be used
during this test case.
2. Verify that the LRN exists for the Service Provider under test.
3. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all scenarios
with the Service Provider.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 53
Prerequisite SP
Setup:
For Row 1 of the test steps that follow use some combination of the following ‘invalid’
DPC/SSN data entry scenarios to create a Subscription Version request with invalid DPC/SSN
data:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using their SOA system,
Service Provider Personnel
submit a Subscription Version
Create request for a single TN.
2. The SOA system sends an M-
ACTION Request
subscriptionVersionNewSP-
Create in CMIP (or NCRQ –
NewSpCreateRequest in XML)
to the NPAC SMS to create the
subscriptionVersionNPAC
(Subscription Version) on the
NPAC SMS.
The following attributes must be
specified:
subscriptionTN or a valid
subscriptionVersionTN-Range
subscriptionNewCurrentSP
subscriptionOldSP
subscriptionNewSP-DueDate
(seconds set to zero)
subscriptionLNPType
subscriptionLRN
subscriptionNewSPMediumTi
merIndicator – if supported by
the Service Provider SOA
Specify a combination of valid and
invalid DPC/SSN data for the
following attributes.
subscriptionCLASS-DPC
subscriptionCLASS-SSN
NPAC The NPAC SMS receives the M-ACTION Request in CMIP (or
NCRQ – NewSpCreateRequest in XML) from the Request
from the Service Provider’s SOA and determines the following:
The request contains invalid DPC/SSN data based on system
requirements and the regional ‘SSN Edit Flag’ settings. (This
violates system requirements.)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 54
subscriptionLIDB-DPC
subscriptionLIDB-SSN
subscriptionCNAM-DPC
subscriptionCNAM-SSN
subscriptionISVM-DPC
subscriptionISVM-SSN
subscriptionWSMSC-DPC - if
supported by the Service
provider SOA
subscriptionWSMSC-SSN - if
supported by the Service
Provider SOA
The following attributes are
optional:
subscriptionEndUser
LocationValue
subscriptionEndUser
LocationType
subscriptionBillingID
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or NCRR – NewSpCreateReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or NCRR – NewSpCreateReply in XML).
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version does not
exist on the NPAC SMS.
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version does not exist on the local
database.
E. Pass/Fail Analysis, NANC 191/291 - 1 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 55
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-2 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to modify a ‘Pending’ Subscription Version
specifying some valid and some invalid DPC/SSN information. The regional SSN Edit Flags
(CLASS, LIDB, CNAM, ISVM and WSMSC) are set to production values. – Failure
Note: Per IIS3_4_1aPart2, the flow for scenario B.5.2.4 is not available over the XML
interface. This functionality is handled by flow B.5.2.3, “SubscriptionVersion Modify Prior to
Activate Using M-ACTION”.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-380, RR3-381, RR3-382, RR3-383,
RR3-384, RR3-385, RR3-386, RR3-387,
RR3-388, RR3-389, RR3-405, RR3-406,
RR3-407, RR3-408, RR3-409, RR3-375,
RR3-376, RR3-377, RR3-378, RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.3 or B.5.2.4
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that a ‘pending’ subscription version exists for the TN that is going to be used
during this test case.
Prerequisite SP
Setup:
For Row 1 of the test steps that follow use some combination of the following ‘invalid’
DPC/SSN data entry scenarios to modify a Subscription Version request with invalid DPC/SSN
data:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 56
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using their SOA system, Service
Provider Personnel submit a request
to the NPAC SMS to modify a
single TN, ‘Pending’ Subscription
Version that already exists on the
NPAC SMS.
The request must specify the TN
and the version status or the version
ID of the Subscription Version to be
modified and the data to be
modified.
The following attributes must be
specified:
Specify a combination of valid and
invalid DPC/SSN data for the
following attributes.
subscriptionCLASS-DPC
subscriptionCLASS-SSN
subscriptionLIDB-DPC
subscriptionLIDB-SSN
subscriptionCNAM-DPC
subscriptionCNAM-SSN
subscriptionISVM-DPC
subscriptionISVM-SSN
subscriptionWSMSC-DPC - if
supported by the Service
provider SOA
subscriptionWSMSC-SSN - if
supported by the Service
Provider SOA
The Service Provider SOA submits
an M-ACTION Request
subscriptionVersionModify in
CMIP (or MODQ – ModifyRequest
in XML) or an M-SET Request
subscriptionVersionNPAC in CMIP
(not available over the XML
interface) (depending on the system
implementation) to the NPAC SMS
lnpSubscription object to update the
‘Pending’ Subscription Version.
NPAC The NPAC SMS receives the M-ACTION in CMIP (or MODQ
– ModifyRequest in XML) /M-SET Request in CMIP (not
available over the XML interface) from the Service Provider’s
SOA and determines the following:
The request contains invalid DPC/SSN data based on system
requirements and the regional ‘SSN Edit Flag’ settings. (This
violates system requirements.)
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or MODR – ModifyReply in XML)
or M-SET Response failure in
CMIP (not available over the XML
interface) (depending on the
message received in Row 1)
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or MODR – ModifyReply in XML) or the M-SET
Response failure in CMIP (not available over the XML
interface) from the NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 57
indicating an error with the request
to the SOA.
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version exists
with a status of ‘Pending’ however, the attributes were not
modified.
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version exists on the local database
with the original attribute values.
E. Pass/Fail Analysis, NANC 191/291 - 2 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 58
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-3 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to activate a ‘Pending’ Subscription Version that
contains some valid and some invalid DPC/SSN information. The regional SSN Edit Flags
(CLASS, LIDB, CNAM, ISVM and WSMSC) are set to production values. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-427
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.1.5
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that a ‘Pending’ Subscription Version with some combination of the valid and
invalid DPC/SSN data scenarios following exists on the NPAC and local databases:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using their SOA system, Service
Provider Personnel submit a request
to the NPAC SMS to activate a
single TN, ‘Pending’ Subscription
NPAC The NPAC SMS receives the M-ACTION Request in CMIP (or
ACTQ – ActivateRequest in XML) from the Service Provider’s
SOA and determines the following:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 59
Version that already exists on the
NPAC SMS with valid and invalid
DPC/SSN information as described
in the prerequisites.
The request must specify the
subscription version ID,
subscription version TN, or a range
of subscription version TNs to be
activated.
The Service Provider SOA submits
an M-ACTION Request
subscriptionVersionActivate in
CMIP (or ACTQ – ActivateRequest
in XML) to the NPAC SMS
lnpSubscription object to activate
the ‘Pending’ Subscription Version.
The request to activate is for a ‘Pending’ Subscription Version
that contains invalid DPC/SSN data based on system
requirements and the regional ‘SSN Edit Flag’ settings. (This
violates system requirements.)
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or ACTR – ActivateReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the Response in CMIP (or
ACTR – ActivateReply in XML) from the NPAC SMS.
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version exists
with a status of ‘Pending’ and invalid DPC/SSN data.
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version exists on the local database
with the invalid DPC/SSN data.
E. Pass/Fail Analysis, NANC 191/291 - 3 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 60
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-4 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to modify an ‘Active’ Subscription Version that
contains some valid and some invalid DPC/SSN information. The regional SSN Edit Flags
(CLASS, LIDB, CNAM, ISVM and WSMSC) are set to production values. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-380, RR3-381, RR3-382, RR3-383,
RR3-384, RR3-385, RR3-386, RR3-387,
RR3-388, RR3-389, RR3-405, RR3-406,
RR3-407, RR3-408, RR3-409, RR3-375,
RR3-376, RR3-377, RR3-378, RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.1
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that an ‘Active’ Subscription Version with some combination of the valid and
invalid DPC/SSN data scenarios following exists on the NPAC and local databases:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
Prerequisite SP
Setup:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 61
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using their SOA system, Service
Provider Personnel submit a request
to the NPAC SMS to modify a
single TN, ‘Active’ Subscription
Version that already exists on the
NPAC SMS with valid and invalid
DPC/SSN information as described
in the prerequisites.
The request must specify the TN,
TN range, and the version status, or
the version ID of the subscription
version to be modified; and the data
to be modified.
Modify any of the following
attributes:
subscriptionLRN
subscriptionEndUserLocationV
alue
subscriptionEndUserLocationT
ype
subscriptionBillingId
The Service Provider SOA submits
an M-ACTION Request
subscriptionVersionModify in
CMIP (or MODQ – ModifyRequest
in XML) to the NPAC SMS
lnpSubscription object to modify the
‘Active’ Subscription Version.
NPAC The NPAC SMS receives the M-ACTION Request in CMIP (or
MODQ – ModifyRequest in XML) from the Service Provider’s
SOA and determines the following:
The request to modify the ‘Active’ Subscription Version
contains invalid DPC/SSN data based on system requirements
and the regional ‘SSN Edit Flag’ settings. (This violates
system requirements.)
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or MODR - ModifyReply in XML)
indicating an error with the request
to the SOA.
SP The Service Provider SOA receives the Response in CMIP (or
MODR - ModifyReply in XML) from the NPAC SMS.
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version exists
with a status of ‘Active’ and invalid DPC/SSN data.
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version exists on the local database
with the invalid DPC/SSN data.
E. Pass/Fail Analysis, NANC 191/291 - 4 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 62
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-5 SUT Priority: SOA N/A
LSMS Required
Objective:
NPAC OP GUI – NPAC Personnel attempt to submit a mass update request for a range of
Subscription Versions that currently exist. Some of these Subscription Versions have valid
DPC/SSN data and some of these Subscription Versions have invalid DPC/SSN data. The
Mass Update request specifies new DPC/SSN values that will correct some but not all of the
Subscription Versions that currently exist with invalid DPC/SSN attributes. The NPAC SMS
processes the Mass Update request, modifies some but not all of the DPC/SSN attributes for the
range specified in the Mass Update Request and logs the objects that could not be updated to
the Mass Update Exception Report. The regional SSN Edit Flags (CLASS, LIDB, CNAM,
ISVM and WSMSC) are set to production values. - Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-429
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.8.3
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that a range of ‘Active’ Subscription Versions exists.
One subset range of Subscription Versions should have all valid DPC/SSN. (SV group
2a)
One subset range of Subscription Versions should exist with invalid CNAM DPC/SSN
data (all other DPC/SSN data should be valid. (SV group 2b)
One subset range of Subscription Versions should exist with all invalid DPC/SSN data
– at a minimum should be CNAM plus at least one other feature set. (SV group 2c)
3. Identify the appropriate TN range to use in this test case ________________________.
4. Identify DPC/SSN attributes that should be specified in the Mass Update request such that
some of the Subscription Versions that currently have invalid DPC/SSN attributes will be
corrected, and some will remain invalid.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel submit a Mass Update
request for a range of ‘Active’
Subscription Versions that exist,
NPAC The NPAC SMS searches the Subscription Version database for
Subscription Versions that match the input Mass Update
criteria.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 63
some with valid DPC/SSN data and
some with invalid DPC/SSN
(identified in the prerequisites
above).
Modify CNAM DPC/SSN data,
specifying valid values for the
following attributes.
subscriptionCNAM-DPC
subscriptionCNAM-SSN
The NPAC SMS determines that a subset of the TNs in the
Subscription Version range exist with invalid DPC/SSN data
that is not corrected by the new values specified in the Mass
Update request. The NPAC SMS makes an entry to the Mass
Update Exception report for these TNs, and continues updating
the remaining Subscription Versions that meet the Mass Update
criteria. request is valid.
2. NPAC NPAC SMS sends multiple M-
SET(s) in CMIP (or SVMD –
SvModifyDownload in XML) for
each contiguous range of
Subscription Versions that met the
Mass Update criteria to all LSMSs
that are accepting downloads for the
NPA-NXX of the Subscription
Versions to update the valid
DPC/SSN values.
SP All LSMSs that are accepting downloads for the NPA-NXXs of
the Subscription Versions being updated, receive the M-SET
request(s) in CMIP (or SVMD – SvModifyDownload in XML)
from the NPAC SMS to modify the DPC/SSN values.
The LSMSs issue an M-SET Response(s) in CMIP (or DNLR –
DownloadReply in XML) indicating they successfully
processed the NPAC SMS request(s).
These M-SET Requests are for the subscription versions that
were successfully updated based on the Mass Update criteria –
and do not include those subscription versions that could not be
updated based on the Mass Update criteria. The subscription
versions that could not be updated are included on the Mass
Update Exception report.
3. NPAC
1. If the current Service Provider’s
TN Range Notification
Indicator is set to TRUE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionRangeStatu
sAttributeValueChange in
CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) for the range of
Subscription Versions that were
updated indicating the status is
now ‘Active’.
2. If the current Service Provider’s
TN Range Notification
Indicator is set to ‘FALSE’,
NPAC SMS issues a
subscriptionVersionStatusAttri
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) for each
Subscription Version that was
updated, indicating the status
is now ‘Active’.
SP The current Service Provider receives the M-EVENT-REPORT
in CMIP (or VATN – SvAttributeValueChangeNotification in
XML) from the NPAC SMS and issues an M-EVENT-
REPORT response in CMIP (or NOTR – NotificationReply in
XML)indicating it successfully received the message.
4. NPAC NPAC Personnel generate a Mass
Update Exception report.
NPAC Verify that the subset of Subscription Versions (SV group 2c)
within the Mass Update criteria that’s invalid DPC/SSN data
was not corrected by the new specified attributes are included
on the report.
5. SP Service Provider Personnel perform
a local query on their LSMS to
SP On the LSMS verify:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 64
verify the Mass Update was
completed.
1. The subset of Subscription Versions (SV group 2c) within
the Mass Update request who’s invalid DPC/SSN data was
not corrected by the new specified DPC/SSN attributes
were not updated with the new DPC/SSN values.
2. The subsets of Subscription Versions (SV groups 2a and
2b) within the Mass Update request who’s DPC/SSN
values were previously valid, or were invalid but the Mass
Update specified attributes corrected the previous issues
were updated with the new DPC/SSN values.
6. NPAC NPAC Personnel perform a full
audit for the subscription version
range specified in the Mass Update
request.
NPAC Verify that there are no discrepancies found.
The subscription versions (SV group 2c) that previously existed
with invalid DPC/SSN data that were not corrected by the Mass
Update specified attributes – still exist in their previous state.
All other subscription versions (SV groups 2a and 2b) specified
in the Mass Update criteria were updated appropriately.
E. Pass/Fail Analysis, NANC 191/291 - 5 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 65
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-6 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to create a Number Pool Block specifying some
valid and some invalid DPC/SSN information. The regional SSN Edit Flags (CLASS, LIDB,
CNAM, ISVM and WSMSC) are set to production values. – Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-390, RR3-391, RR3-392, RR3-393,
RR3-394, RR3-395, RR3-396, RR3-397,
RR3-398, RR3-399, RR3-400, RR3-401,
RR3-402, RR3-403, RR3-404, RR3-375,
RR3-376, RR3-377, RR3-378, RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.4.4.2
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that the NPA-NXX exists and is open for porting for the Number Pool Block that is
going to be used during this test case.
3. Verify that the NPA-NXX-X exists respective to the Number Pool Block that is going to be
used during this test case.
4. Verify that there are no contaminated TNs or ‘pending-like’ Subscription Versions for the
range of TNs in the NPA-NXX-X.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 66
Prerequisite SP
Setup:
1. Verify that the NPA-NXX-X exists for the Number Pool Block that Service Provider
Personnel will create during this Test Case.
2. Verify that the current date is equal to or greater than the NPA-NXX-X Effective Date.
3. For Row 1 of the test steps that follow use some combination of the following ‘invalid’
DPC/SSN data entry scenarios to create a Subscription Version request with invalid
DPC/SSN data:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, Service Provider
Personnel, submit a M-ACTION
numberPoolBlock-Create Request
in CMIP (or PBCQ –
NpbCreateRequest in XML) to the
NPAC SMS to create a Number
Pool Block.
The request must include the
following attributes:
numberPoolBlockNPA-NXX-X
numberPoolBlockSPID
numberPoolBlockLRN
Specify a combination of valid and
invalid DPC/SSN data for the
following attributes:
numberPoolBlockCLASS-DPC
numberPoolBlockCLASS-SSN
numberPoolBlockCNAM-DPC
numberPoolBlockCNAM-SSN
numberPoolBlockISVM-DPC
numberPoolBlockISVM-SSN
numberPoolBlockLIDB-DPC
numberPoolBlockLIDB-SSN
numberPoolBlockWSMSC-
DPC – if supported by the
Service Provider SOA
NPAC The NPAC SMS receives the M-ACTION numberPoolBlock-
Create Request in CMIP (or PBCQ – NpbCreateRequest in
XML) from the Service Provider’s SOA and determines the
following:
The request contains invalid DPC/SSN data based on system
requirements and the regional ‘SSN Edit Flag’ settings. (This
violates system requirements.)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 67
numberPoolBlockWSMSC-
SSN – if supported by the
Service Provider SOA
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or PBCR – NpbCreateReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or PBCR – NpbCreateReply in XML).
3. NPAC NPAC Personnel perform a query
for the Number Pool Block and
respective ‘Pooled’ Subscription
Versions Service Provider personnel
attempted to schedule during this
test case.
NPAC NPAC Personnel verify that the Number Pool Block and
respective ‘Pooled’ Subscription Versions do not exist on the
NPAC SMS.
4. SP Service Provider Personnel, perform
a local query for the Number Pool
Block and the respective ‘Pooled’
Subscription Versions they
attempted to schedule during this
test case.
SP Verify that the Number Pool Block and the respective ‘Pooled’
Subscription Versions do not exist on the local database.
E. Pass/Fail Analysis, NANC 191/291 - 6 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 68
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-7 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to modify a Number Pool Block specifying some
valid and some invalid DPC/SSN information. The regional SSN Edit Flags (CLASS, LIDB,
CNAM, ISVM and WSMSC) are set to production values. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-390, RR3-391, RR3-392, RR3-393,
RR3-394, RR3-395, RR3-396, RR3-397,
RR3-398, RR3-399, RR3-400, RR3-401,
RR3-402, RR3-403, RR3-404, RR3-405,
RR3-406, RR3-407, RR3-408, RR3-409,
RR3-421, RR3-422, RR3-423, RR3-424,
RR3-425, RR3-426, RR3-375, RR3-376,
RR3-377, RR3-378, RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.4.4.13
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify the Number Pool Block to be modified exists on the NPAC SMS with a status of
‘active’ and an empty Failed SP List.
Prerequisite SP
Setup:
For Row 1 of the test steps that follow use some combination of the following ‘invalid’
DPC/SSN data entry scenarios to modify a Number Pool Block with invalid DPC/SSN data:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 69
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, Service Provider
Personnel submit an M-SET
Request numberPoolBlock in CMIP
(or PBMQ – NpbModifyRequest in
XML) to modify a Number Pool
Block.
The following attributes may be
modified:
numberPoolBlockLRN
Specify a combination of valid and
invalid DPC/SSN data for the
following attributes:
numberPoolBlockCLASS-DPC
numberPoolBlockCLASS-SSN
numberPoolBlockCNAM-DPC
numberPoolBlockCNAM-SSN
numberPoolBlockLIDB-DPC
numberPoolBlockLIDB-SSN
numberPoolBlockISVM-DPC
numberPoolBlockISVM-SSN
numberPoolBlockWSMSC-
DPC – if supported by the
Service Provider SOA
numberPoolBlockWSMSC-
SSN – if supported by the
Service Provider SOA
NPAC The NPAC SMS receives the M-SET Request
numberPoolBlock in CMIP (or PBMQ – NpbModifyRequest in
XML) from the Service Provider’s SOA and determines the
following:
The request contains invalid DPC/SSN data based on system
requirements and the regional ‘SSN Edit Flag’ settings. (This
violates system requirements.)
2. NPAC The NPAC SMS issues an M-SET
Response failure in CMIP (or
PBMR – NpbModifyReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-SET Response in
CMIP (or PBMR – NpbModifyReply in XML).
3. NPAC NPAC Personnel perform a query
for the Number Pool Block and
respective ‘Pooled’ Subscription
Versions Service Provider personnel
attempted to modify during this test
case.
NPAC NPAC Personnel verify that the Number Pool Block and
respective ‘Pooled’ Subscription Versions were not modified on
the NPAC SMS.
4. SP Service Provider Personnel, perform
a local query for the Number Pool
Block and the respective ‘Pooled’
Subscription Versions they
attempted to modify during this test
case.
SP Verify that the Number Pool Block and the respective ‘Pooled’
Subscription Versions were not modified on the local database.
E. Pass/Fail Analysis, NANC 191/291 - 7 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 70
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 71
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-8 SUT Priority:
NPAC One Time
Only
SOA N/A
LSMS N/A
Objective:
NPAC – Upon Number Pool Block scheduled activation, NPAC SMS fails the Number Pool
Block activation based on some invalid DPC/SSN information. The regional SSN Edit Flags
(CLASS, LIDB, CNAM, ISVM and WSMSC) are set to production values. – Failure
Note: Per IIS3_4_1aPart_2, this flow does not involve XML messaging over the interface.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-390, RR3-391, RR3-392, RR3-393,
RR3-394, RR3-395, RR3-396, RR3-397,
RR3-398, RR3-399, RR3-400, RR3-401,
RR3-402, RR3-403, RR3-404, RR3-428,
RR3-375, RR3-376, RR3-377, RR3-378,
RR3-378
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.4.4.2
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
NPAC Test Engineers, set SSN Edit Flags to FALSE, create an NPA-NXX-X, schedule a
respective Number Pool Block for at least 1 day in the future containing invalid DPC/SSN
data (as described below). After the Number Pool Block has been scheduled, but prior to
activation, set the SSN Edit Flags to TRUE. Perform test steps as specified below.
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify the Number Pool Block create event exists on the NPAC SMS with some
combination of the following invalid DPC/SSN data value scenarios:
If the ‘SSN Edit Flags’ are set to TRUE, invalid data would include
Specifying DPC values of (network 001-255, cluster 000-255, member 000-255) and
corresponding SSN values other than (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values of (000).
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and corresponding SSN values other than (000).
If the ‘SSN Edit Flags’ are set to FALSE, invalid data would include
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) when the SSN value is between 000-255.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a value for the corresponding SSN value.
Specifying DPC values other than (network 001-255, cluster 000-255, member 000-
255) and also not specifying a valid SSN value is between 000-255.
Prerequisite SP
Setup:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 72
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Upon reaching the Number Pool
Block scheduled date, the NPAC
SMS attempts to automatically
‘Create’ the Number Pool Block
and respective ‘Pooled’
Subscription Versions for a Number
Pool Block create event that has
been scheduled with some
combination of invalid DPC/SSN
information outlined in the
prerequisites.
NPAC The NPAC SMS determines the following:
The Number Pool Block and respective ‘Pooled’ Subscription
Version Create request contains invalid DPC/SSN data based
on system requirements and the regional ‘SSN Edit Flag’
settings. (This violates system requirements.)
2. NPAC The NPAC SMS fails the Number
Pool Block Create request and
generates appropriate errors.
NPAC The error log is appropriately updated to reflect the Number
Pool Block and respective ‘Pooled’ Subscription Version create
request failure.
3. NPAC NPAC Personnel perform a query
for the Number Pool Block and
respective ‘Pooled’ Subscription
Versions the NPAC SMS attempted
to automatically create during this
test case.
NPAC NPAC Personnel verify that the Number Pool Block and
respective ‘Pooled’ Subscription Versions were not created on
the NPAC SMS.
4. SP Service Provider Personnel, perform
a local query for the Number Pool
Block and the respective ‘Pooled’
Subscription Versions the NPAC
SMS attempted to automatically
create during this test case.
SP Verify that the Number Pool Block and the respective ‘Pooled’
Subscription Versions were not created on the local database.
E. Pass/Fail Analysis, NANC 191/291 - 8 Pass Fail NPAC Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting for which the
Service Provider under test may operate in production.
Pass Fail Service Provider Personnel performed the test case as written for each ‘SSN Edit Flag’ indicator setting where
they may operate in production.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 73
A. TEST IDENTITY
Test Case
Number:
NANC 191/291-9 SUT Priority: SOA N/A
LSMS Required
Objective:
NPAC OP GUI – NPAC Personnel attempt to submit a mass update request that includes at
least three complete, ‘Active’ Number Pool Blocks. One of these Number Pool Blocks should
currently exist with valid DPC/SSN data, two should exist with invalid DPC/SSN data. The
Mass Update criteria shall include all three Number Pool Blocks and the request specifies new
DPC/SSN values that will correct one, but not both of the Number Pool Blocks that currently
exists with invalid DPC/SSN data. The NPAC SMS processes the Mass Update request,
modifies some but not all of the DPC/SSN attributes for the range specified in the Mass Update
Request and logs the objects that could not be updated to the Mass Update Exception report.
The regional SSN Edit Flags (CLASS, LIDB, CNAM, ISVM and WSMSC) are set to
production values. - Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 191/NANC 291
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR3-429
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.8.3, B.8.3.1
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the ‘SSN Edit Flag’ indicators are set to production settings for the regions in
which the Service Provider under test operates. If the Service Provider operates in regions
where the ‘SSN Edit Flag’ indicators may be set to different settings, be sure to test all
scenarios with the Service Provider.
2. Verify that at least 3 ‘Active’ Number Pool Block exist.
One of these Number Pool Blocks should exist with valid DPC/SSN values. (NPB 2a)
One Number Pool Block should exist with invalid CNAM DPC/SSN data (all other
DPC/SSN data should be valid. (NPB 2b)
One Number Pool Block should exist with all invalid DPC/SSN data – at a minimum
should be CNAM plus at least one other feature set. (NPB 2c)
3. Identify the appropriate Number Pool Block range to use in this test case
_____________________.
4. Identify DPC/SSN attributes that should be specified in the Mass Update request such that
one of the Number Pool Blocks that currently have invalid DPC/SSN attributes will be
corrected, and the other Number Pool Block will remain invalid.
5. Verify that non-pooled TNs within the Mass Update TN range exist.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel submit a Mass Update
NPAC The NPAC SMS receives the Mass Update Request from the
NPAC OP GUI and searches the Number Pool Block and
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 74
request that includes at least 3
complete, ‘Active’ Number Pool
Blocks. (Identified in the
prerequisites above).
Modify CNAM DPC/SSN data,
specifying valid values for the
following attributes.
subscriptionCNAM-DPC
subscriptionCNAM-SSN
Subscription Version databases for Number Pool Blocks and
Subscription Versions that match the input Mass Update
criteria.
The NPAC SMS determines that a subset of the Number Pool
Blocks and Subscription Versions requested exist with invalid
DPC/SSN data that is not corrected by the new values specified
in the Mass Update request. The NPAC SMS makes an entry to
the Mass Update Exception report for these Number Pool Block
and Subscription Version objects, and continues updating the
remaining Number Pool Blocks and Subscription Versions that
meet the Mass Update criteria.
2. NPAC NPAC SMS sends to all LSMSs that
are accepting downloads for the
NPA-NXX(s):
to LSMSs, NPAC SMS issues
M-SET Request(s)
numberPoolBlock in CMIP (or
PBMD – NpbModifyDownload
in XML) to update the
DPC/SSN data.
to LSMSs, NPAC SMS issues
M-SET Request(s)
subscriptionVersion in CMIP
(or SVMD –
SvModifyDownload in XML)
for each contiguous range of
non-pooled TN’s within the
Mass Update TN range to
update the DPC/SSN data.
SP All LSMSs that are accepting downloads for the NPA-NXXs of
the Number Pool Block objects and Subscription Versions
being updated, receive the M-SET requests in CMIP (or
PBMD/SVMD – NpbModifyDownload/SvModifyDownload in
XML) from the NPAC SMS to modify the DPC/SSN values.
The LSMSs issue M-SET Responses in CMIP (or DNLR –
DownloadReply in XML) indicating they successfully
processed the NPAC SMS request.
These M-SET Requests are for the Number Pool Blocks and
Subscription Versions that were successfully updated based on
the Mass Update criteria – and does not include those Number
Pool Blocks or Subscription Versions that could not be updated
based on the Mass Update criteria. The Number Pool Blocks
and Subscription Versions that could not be updated are
included on the Mass Update Exception report.
3. NPAC 1. If the current Service Provider’s
TN Range Notification
Indicator is set to TRUE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionRangeStatu
sAttributeValueChange in
CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) for the range of
Subscription Versions that were
updated indicating the status is
now ‘Active’.
2. If the current Service Provider’s
TN Range Notification
Indicator is set to ‘FALSE’,
NPAC SMS issues a
subscriptionVersionStatusAttri
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) for each
Subscription Version that was
SP The current Service Provider receives the M-EVENT-REPORT
in CMIP (or VATN – SvAttributeValueChangeNotification in
XML) from the NPAC SMS and issues an M-EVENT-
REPORT response in CMIP (or NOTR – NotificationReply in
XML) indicating it successfully received the message.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 75
updated, indicating the status
is now ‘Active’.
4. NPAC NPAC Personnel generate a Mass
Update Exception report.
NPAC Verify Number Pool Block (NPB 2c) and the respective
Subscription Versions within the Mass Update criteria who’s
invalid DPC/SSN data was not corrected by the new specified
attributes are included on the report.
5. SP Service Provider Personnel perform
a local query on their LSMS to
verify the Mass Update was
completed.
SP On the LSMS verify:
1. Number Pool Block (NPB 2c) and the respective
Subscription Versions within the Mass Update request
who’s invalid DPC/SSN data was not corrected by the new
specified DPC/SSN attributes were not updated with the
new DPC/SSN values.
2. Number Pool Blocks (NPB 2a and 2b) and the respective
Subscription Versions within the Mass Update request
who’s DPC/SSN values were previously valid, or were
invalid but the Mass Update specified attributes corrected
the previous issues were updated with the new DPC/SSN
values.
6. NPAC NPAC Personnel perform a full
audit for the range specified in the
Mass Update request.
NPAC Verify that there are no discrepancies found.
Number Pool Block (NPB 2c) and respective Subscription
Versions that previously existed with invalid DPC/SSN data
that were not corrected by the Mass Update specified attributes
– still exist in their previous state.
Number Pool Blocks (NPB 2a and 2b) and respective
Subscription Versions specified in the Mass Update criteria
were updated appropriately.
E. Pass/Fail Analysis, NANC 191/291 - 9 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 76
12.4 NANC 192 NPA Split NPAC SMS Load File
A. TEST IDENTITY
Test Case
Number:
NANC 192-1 SUT Priority: SOA Required
LSMS Required
Objective:
SOA/LSMS - Service Provider Personnel perform basic LNP functions before, during and after
Permissive Dial Period for NPA Splits that are created on the NPAC SMS. - Success
Test Case procedures incorporated into test case 8.5.1 from Release 1.0.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 77
12.5 NANC 218 – Conflict Timestamp Broadcast to SOA
A. TEST IDENTITY
Test Case
Number:
NANC 218-1 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – (Old) Service Provider Personnel submit a single TN, subscription version modify
request specifying Authorization (FALSE) and a valid status change cause code, setting the
subscription version status to conflict after both Service Providers have created/concurred to the
port, and prior to the Conflict Restriction Window – SUCCESS
Note: Per IIS3_4_1aPart2, the flow for scenario B.5.2.4 is not available over the XML
interface. This functionality is handled by flow B.5.2.3, “SubscriptionVersion Modify Prior to
Activate Using M-ACTION”..
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 218
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-44.2, RR5-44.3
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.3, B.5.2.4
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Pending’ exists for the TN that will be
used in the Subscription Version modify request by the Old Service Provider in this test
case, exists on the NPAC SMS.
2. Verify that the current time is prior to the Conflict Restriction Window expiration.
3. The Subscription Version that is going to be used during this Test Case should not
previously have been put in conflict before, should have never had a status of ‘Conflict’,
and should not have a Conflict Time Stamp value.
4. TN Used:______________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using their SOA system, Old
Service Provider Personnel
submit a Subscription Version
Modify request for a ‘Pending’
Subscription Version that has
previously been created by the
NPAC NPAC SMS receives the M-ACTION request in CMIP (or
MODQ – ModifyRequest in XML)/M-SET Request in CMIP
(not available over the XML interface) from the Old SP SOA
and verifies that each attribute specified is valid according to
system requirements.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 78
New Service Provider and
concurred to by the Old Service
Provider. Specify the TN
identified in the prerequisite
steps above.
2. The SOA sends either an M-
ACTION Request
subscriptionVersionModify in
CMIP (or MODQ –
ModifyRequest in XML) or an
M-SET Request
subscriptionVersionNPAC in
CMIP (not available over the
XML interface) specifying the
TN identified in the
prerequisite above and setting
the subscriptionOldSP-
Authorization to FALSE and
indicating a valid
subscriptionStatusChangeCause
Code.
2. NPAC The NPAC SMS:
1. If an M-ACTION Request
subscriptionVersionModify was
sent, issues an M-ACTION
Response in CMIP (or MODR
– ModifyReply in XML) back
to the Old SP SOA followed by
an (internal) M-SET Request
subscriptionVersionNPAC and
M-SET Response
subscriptionVersionNPAC to
itself.
2. If an M-SET Request
subscriptionVersionNPAC was
sent, issues an M-SET
Response
subscriptionVersionNPAC in
CMIP (not available over the
XML interface) to the Old SP
SOA.
SP The Old Service Provider SOA receives the Response in CMIP
(MODR – ModifyReply in XML) from the NPAC SMS.
3. NPAC NPAC SMS issues an M-EVENT-
REPORT to the Old SP SOA based
on their Customer TN Range
Notification Indicator.
1. If the setting is TRUE, NPAC
SMS issues an M-EVENT-
REPORT
subscriptionVersionRangeAttri
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) including the
attributes bulleted below:
2…..If the setting is FALSE, NPAC
SMS issues an M-EVENT-
SP The Old Service Provider SOA receives the M-EVENT-
REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML) from the NPAC
SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 79
REPORT attributeValueChange
in CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) including the
attributes bulleted below:
subscriptionNewSP-
DueDate
subscriptionOldSP-
Authorization (set to
FALSE)
subscriptionOldSP-
AuthorizationTimeStamp
subscriptionStatusChange
CauseCode
subscriptionVersionStatus
(Conflict) – XML only
subscriptionConflictTime
Stamp
4. SP Old SP SOA issues an M-EVENT-
REPORT Confirmation in CMIP (or
NOTR – NotificationReply in
XML) to the NPAC SMS indicating
it successfully received the M-
EVENT-REPORT in CMIP (or
VATN –
SvAttributeValueChangeNotificatio
n in XML) from the NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (or NOTR – NotificationReply in XML) from the Old SP
SOA.
5. NPAC The NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionStatusAttribute
ValueChange in CMIP (not
available over the XML interface)
to the Old Service Provider SOA to
update the Subscription Version
status to ‘Conflict’.
SP The Old Service Provider SOA receives the M-EVENT-
REPORT from the NPAC SMS and issues an M-EVENT-
REPORT Confirmation in CMIP (not available over the XML
interface) back to the NPAC.
6. SP Old SP SOA issues an M-EVENT-
REPORT Confirmation in CMIP
(not available over the XML
interface) to the NPAC SMS
indicating it successfully received
the M-EVENT-REPORT from the
NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (not available over the XML interface) from the Old SP
SOA.
7. SP At the same time as row 3 above,
NPAC SMS issues an M-EVENT-
REPORT to the New SP SOA based
on their Customer TN Range
Notification Indicator.
1. If the setting is TRUE, NPAC
SMS issues an M-EVENT-
REPORT
subscriptionVersionRangeAttri
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
SP The New Service Provider SOA receives the M-EVENT-
REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML) from the NPAC
SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 80
cation in XML) including the
attributes bulleted below:
2…..If the setting is FALSE, NPAC
SMS issues an M-EVENT-
REPORT attributeValueChange
in CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) including the
attributes bulleted below:
subscriptionNewSP-
DueDate
subscriptionOldSP-
Authorization (set to
FALSE)
subscriptionOldSP-
AuthorizationTimeStamp
subscriptionStatusChange
CauseCode
subscriptionVersionStatus
(Conflict) – XML Only
subscriptionConflictTime
Stamp
8. SP New SP SOA issues an M-EVENT-
REPORT Confirmation in CMIP (or
NOTR – NotificationReply in
XML) to the NPAC SMS indicating
it successfully received the M-
EVENT-REPORT in CMIP (or
VATN –
SvAttributeValueChangeNotificatio
n in XML) from the NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (or NOTR – NotificationReply in XML) from the New
SP SOA.
9. NPAC The NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionStatusAttribute
ValueChange in CMIP (not
available over the XML interface)
to the New Service Provider SOA to
update the Subscription Version
status to ‘Conflict’.
SP The New Service Provider SOA receives the M-EVENT-
REPORT from the NPAC SMS and issues an M-EVENT-
REPORT Confirmation in CMIP (not available over the XML
interface) back to the NPAC,
10. SP New SP SOA issues an M-EVENT-
REPORT Confirmation in CMIP
(not available over the XML
interface) to the NPAC SMS
indicating it successfully received
the M-EVENT-REPORT from the
NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (not available over the XML interface)from the New SP
SOA.
11. SP Using their SOA, Old SP Personnel
perform a local query for the
subscription version modified
during this test case.
SP The subscription version exists with a status of ‘conflict’ and
that the ConflictTimeStamp is set appropriately.
12. NPAC NPAC Personnel perform a query
for the subscription version
modified in this test case.
NPAC The subscription version exists with a status of ‘conflict’.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 81
E. Pass/Fail Analysis, NANC 218-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel confirm they received all attributes included in the M-EVENT-REPORT request
from the NPAC SMS listed in row 3 above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 82
This test case will supersede NANC 214-1 in the functional and regression test plan.
A. TEST IDENTITY
Test Case Number: NANC 218-2 SUT
Priority: SOA Required
LSMS N/A
Objective:
SOA – Old Service Provider personnel successfully put a pending
Subscription Version into conflict using an Old Service Provider create after
the Conflict Restriction Window Tunable Time has been reached but before
the Final Concurrence Timer (T2) has expired. – Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s): NANC 218
NANC FRS Version
Number:
3.2.0.a Relevant
Requirement(s): RR5-44.2, RR5-44.3
NANC IIS Version
Number:
3.2.0.a Relevant Flow(s): Based on B.5.1.4
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite NPAC
Setup:
Verify that a New Service Provider pending Subscription Version has been created where the
Service Provider under test is the Old Service Provider, the due date is today and the Final
Concurrence Timer has not expired.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, Old Service Provider
personnel create a subscriptionVersionOldSP-
Create M-ACTION Request in CMIP (or
OCRQ – OldSpCreateRequest in XML) with
the authorization flag set to “FALSE” for a
‘pending’ Subscription Version created by the
New Service Provider where the due date is
today and the Final Concurrence Timer has
not expired.
SP The SOA issues a subscriptionVersionOldSP-Create M-
ACTION in CMIP (or OCRQ – OldSpCreateRequest in
XML) to the NPAC SMS.
2. NPAC The NPAC SMS accepts the M-ACTION
Request in CMIP (or OCRQ –
OldSpCreateRequest in XML) from the
Service Provider.
NPAC The NPAC SMS sets the Subscription Version to conflict
and sets all of the other values from the
subscriptionVersionOldSP-Create M-ACTION Request
in CMIP (or OCRQ – OldSpCreateRequest in XML).
3. NPAC The NPAC SMS issues an M-ACTION
Response in CMIP (or OCRR –
OldSpCreateReply in XML).
SP The SOA receives the successful
subscriptionVersionOldSP-Create M-ACTION Response in CMIP (or OCRR – OldSpCreateReply in XML).
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 83
4. NPAC NPAC SMS issues an M-EVENT-REPORT to
the Old SP SOA based on their Customer TN
Range Notification Indicator.
1. If the setting is TRUE, NPAC SMS issues
an M-EVENT-REPORT
subscriptionVersionRangeAttributeValue
Change in CMIP (or VATN –
SvAttributeValueChangeNotification in
XML) including the attributes bulleted
below:
2. If the setting is FALSE, NPAC SMS
issues an M-EVENT-REPORT
attributeValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotification in
XML)including the attributes bulleted
below:
subscriptionVersionID
subscriptionTN
subscriptionOldSP
subscriptionNewCurrentSP
subscriptionOldSP-DueDate (seconds set
to zeros)
subscriptionOldSP-Authorization
subscriptionStatusChangeCauseCode
subscriptionOldSP-
AuthorizationTimeStamp
subscriptionOldSP-ConflictTimeStamp
subscriptionVersionStatus (Conflict) –
XML Only
subscriptionTimerType – if supported by
the Service Provider SOA
subscriptionBusinessType – if supported
by the Service Provider SOA
subscriptionOldSPMediumTimerInd
icator – if supported by the Service
Provider SOA
SP The Old Service Provider SOA receives the M-EVENT-
REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML) from the
NPAC SMS.
5. SP Old SP SOA issues an M-EVENT-REPORT
Confirmation in CMIP (or NOTR –
NotificationReply in XML) to the NPAC SMS
indicating it successfully received the M-
EVENT-REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML)
from the NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT
Confirmation in CMIP (or NOTR – NotificationReply in
XML) from the Old SP SOA.
6. NPAC The NPAC SMS issues an M-EVENT-
REPORT
subscriptionVersionStatusAttributeValueChan
ge in CMIP (not available over the XML
interface) to the Old Service Provider SOA to
update the Subscription Version status to
‘Conflict’.
SP The Old Service Provider SOA receives the M-EVENT-
REPORT from the NPAC SMS and issues an M-
EVENT-REPORT Confirmation in CMIP (not available
over the XML interface) back to the NPAC.
7. SP Old SP SOA issues an M-EVENT-REPORT
Confirmation in CMIP (not available over the
XML interface) to the NPAC SMS indicating
NPAC NPAC SMS receives the M-EVENT-REPORT
Confirmation in CMIP (not available over the XML
interface) from the Old SP SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 84
it successfully received the M-EVENT-
REPORT from the NPAC SMS.
8. NPAC At the same time as row 4 above,
NPAC SMS issues an M-EVENT-REPORT to
the New SP SOA based on their Customer TN
Range Notification Indicator.
1. If the setting is TRUE, NPAC SMS issues
an M-EVENT-REPORT
subscriptionVersionRangeAttributeValue
Change in CMIP (or VATN –
SvAttributeValueChangeNotification in
XML) including the attributes bulleted in
step 4 above.
2. If the setting is FALSE, NPAC SMS
issues an M-EVENT-REPORT
attributeValueChange in CMIP (or VATN
– SvAttributeValueChangeNotification in
XML).
SP The New Service Provider SOA receives the M-EVENT-
REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML) from the
NPAC SMS.
9. SP New SP SOA issues an M-EVENT-REPORT
Confirmation in CMIP (or NOTR –
NotificationReply in XML) to the NPAC SMS
indicating it successfully received the M-
EVENT-REPORT in CMIP (or VATN –
SvAttributeValueChangeNotification in XML)
from the NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT
Confirmation in CMIP (or NOTR – NotificationReply in
XML) from the New SP SOA.
10. NPAC The NPAC SMS issues an M-EVENT-
REPORT
subscriptionVersionStatusAttributeValueChan
ge in CMIP (not available over the XML
interface) to the New Service Provider SOA to
update the Subscription Version status to
‘Conflict’.
SP The New Service Provider SOA receives the M-EVENT-
REPORT from the NPAC SMS and issues an M-
EVENT-REPORT Confirmation in CMIP (not available
over the XML interface) back to the NPAC,
11. SP New SP SOA issues an M-EVENT-REPORT
Confirmation in CMIP (not available over the
XML interface) to the NPAC SMS indicating
it successfully received the M-EVENT-
REPORT from the NPAC SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT
Confirmation in CMIP (not available over the XML
interface) from the New SP SOA.
12. SP Using their SOA, Old SP Personnel perform a
local query for the subscription version they
created during this test case.
SP The subscription version exists with a status of ‘conflict’
and that the ConflictTimeStamp is set appropriately.
13. NPAC NPAC Personnel perform a query for the
Subscription Version to verify that it has a
status of ‘conflict’.
NPAC The Subscription Version has a status of ‘conflict’, the
cause code, the authorization time stamp, the conflict
time stamp and the Old Service Provider due date is set
and the authorization flag is set to False.
E. Pass/Fail Analysis, NANC 218-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel confirm they received all attributes included in the M-EVENT-REPORT request
from the NPAC SMS listed in row 4 above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 85
12.6 NANC 230 – Donor SOA Port-To-Original of Intra-Service Provider Port
A. TEST IDENTITY
Test Case
Number:
NANC 230-1 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel create an Intra-Service Provider, Port-to-Original
Subscription Version where a previously ‘Active’ Subscription Version exists, that is not part of
a Number Pool Block – Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 230
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-4, RR5-122, RR5-6.1
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.1.11
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Active’ exists for the TN that will be
used in the Intra-Service Provider, Port-to-Original Subscription Version create request in
this test case, for the current Service Provider, on the NPAC SMS.
2. The TN that is going to be used during this Test Case should not be part of a Number Pool
Block or be associated in any way with an existing NPA-NXX-X on the NPAC SMS.
3. TN Used:______________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION
subscriptionVersionNewSP-
Create request to the NPAC
SMS for an Intra-Service
Provider, Port-to-Original,
single TN, Subscription
Version for which there is a
currently ‘Active’ Subscription
Version for which they are the
current Service Provider.
2. The SOA sends an M-ACTION
subscriptionVersionNewSP-
Create in CMIP (or NCRQ –
NewSpCreateRequest in XML)
to the NPAC SMS for the
NPA
C
NPAC SMS receives the M-ACTION
subscriptionVersionNewSP-Create request in CMIP (or NCRQ
– NewSpCreateRequest in XML) from the New/Current SP
SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 86
single TN and includes only the
following attributes:
subscriptionTN
subscriptionNewCurrentSP
subscriptionOldSP
subscriptionNewSP-
DueDate (seconds set to
zeros)
subscriptionPortingToOrigina
l-SPSwitch
2. NPAC NPAC SMS issues an M-CREATE
Request subscriptionVersionNPAC
to itself for the TN to create the
Subscription Version, sets the
subscriptionVersionStatus to
‘Pending’, and sets the
subscriptionNewSPCreationTimeSt
amp, and the
subscriptionModifedTimeStamp to
the current date and time.
NPAC NPAC SMS issues an M-CREATE Response to itself.
3. NPAC NPAC SMS issues an M-ACTION
Response
subscriptionVersionNPAC in CMIP
(or NCRR – NewSpCreateReply in
XML) to the New/Current SP
indicating it successfully received
the Intra-Service Provider, Port-to-
Original, Subscription Version
create request.
SP New/Current SP SOA receives the M-ACTION Response in
CMIP (or NCRR – NewSpCreateReply in XML).
4. NPAC NPAC SMS issues an M-EVENT-
REPORT to the New/Current SP
SOA based on their Customer TN
Range Notification Indicator:
1. If the setting is TRUE, NPAC
SMS issues an M-EVENT-
REPORT
subscriptionVersionRangeObjectCr
eation in CMIP (or VOCN –
SvObjectCreationNotification in
XML) specifying the following
attributes:
start TN
end TN
start SVID
end SVID
those attributes bulleted
below:
2. If the setting is FALSE, NPAC
SMS issues an M-EVENT-
REPORT objectCreation in
CMIP (or VOCN –
SvObjectCreationNotification
in XML) specifying the
following attributes::
subscriptionVersionId
NPAC New/Current SP SOA receives the M-EVENT-REPORT in
CMIP (or VOCN – SvObjectCreationNotification in XML)
from the NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 87
subscriptionTN
The following attributes will also be
sent in the ObjectCreation or
subscriptionVersionRangeObjectCr
eation notification:
subscriptionOldSP
subscriptionNewCurrentSP
subscriptionNewSP-
DueDate
subscriptionNewSP-
CreationTimeStamp
subscriptionVersionStatus
subscriptionTimerType (if
supported)
subscriptionBusinessType
(if supported)
5. SP New/Current SP SOA issues an M-
EVENT-REPORT Confirmation in
CMIP (or NOTR –
NotificationReply in XML) to the
NPAC SMS indicating it
successfully received the M-
EVENT-REPORT from the NPAC
SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (or NOTR – NotificationReply in XML) from the
New/Current SP SOA.
6. SP Using their SOA, New/Current SP
Personnel perform a local query for
the Subscription Version created in
this test case.
SP The Subscription Version exists with a status of ‘Pending’, an
LNP type of ‘LISP’ and the Port-to-Original indicator set to
TRUE.
7. NPAC NPAC Personnel perform a query
for the Subscription Version created
in this test case.
NPAC The Subscription Version exists with a status of ‘Pending’, an
LNP type of ‘LISP’, and the Port-to-Original indicator set to
TRUE.
E. Pass/Fail Analysis, NANC 230-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 88
A. TEST IDENTITY
Test Case
Number:
NANC 230-2 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel create an Intra-Service Provider, Port-to-Original
Subscription Version where a previously ‘Active’ Subscription Version exists with a matching
NPA-NXX-X, after the NPA-NXX-X Creation and prior to the Number Pool Block Activation -
Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 230
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-121
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.1.11
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Active’ exists for the TN that will be
used in the Intra-Service Provider, Port-to-Original Subscription Version create request in
this test case, for the current Service Provider, on the NPAC SMS.
2. The TN/Subscription Version that is going to be used during this Test Case should have an
NPA-NXX-X that exists on the NPAC SMS, but the respective Number Pool Block has not
yet been Activated.
3. TN Used:______________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, SP Personnel
submit an M-ACTION
subscriptionVersionNewSP-Create
request in CMIP (or NCRQ –
NewSpCreateRequest in XML) to
the NPAC SMS for an Intra-Service
Provider, Port-to-Original, single
TN, Subscription Version for which
there is a currently ‘Active’
Subscription Version for which they
are the current Service Provider.
This TN should have a respective
NPA-NXX-X that has been created
on the NPAC SMS but respective
Number Pool Block has not yet
been activated.
NPAC NPAC SMS receives the M-ACTION
subscriptionVersionNewSP-Create request in CMIP (or NCRQ
– NewSpCreateRequest in XML) from the New/Current SP
SOA and determines the request is invalid because system
requirements have been violated:
NPAC SMS shall reject a request for an Intra-Service Provider,
Port-to-Original Subscription Version create after the creation
of the NPA-NXX-X and prior to the existence of the respective
Block.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 89
The SOA sends an M-ACTION
subscriptionVersionNewSP-Create
in CMIP (or NCRQ –
NewSpCreateRequest in XML) to
the NPAC SMS for the single TN
and includes only the following
attributes:
subscriptionTN
subscriptionNewCurrentSP
subscriptionOldSP
subscriptionNewSP-DueDate
(seconds set to zeros)
subscriptionPortingToOriginal-
SPSwitch
2. NPAC 1. NPAC SMS issues an M-
ACTION Response in CMIP
(or NCRR –
NewSpCreateReply in XML)
subscriptionVersionNPAC to
the New/Current SP SOA
indicating it did not
successfully validate the Intra-
Service Provider, Port-to-
Original, Subscription Version
create request.
2. Further processing is ceased.
SP New/Current SP SOA receives the M-ACTION Response in
CMIP (or NCRR – NewSpCreateReply in XML).
3. SP Using their SOA, New/Current SP
Personnel perform a local query for
the Subscription Version they
attempted to create in this test case.
SP Verify the Subscription Version does not exist.
Verify that an error response was received from the NPAC
SMS.
4. NPAC NPAC Personnel perform a query
for the Subscription Version that the
SP personnel attempted to create in
this test case.
NPAC Verify that the Subscription Version does not exist.
E. Pass/Fail Analysis, NANC 230-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 90
A. TEST IDENTITY
Test Case
Number:
NANC 230-3 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel create an Intra-Service Provider, Porting to Original
Subscription Version after NPA-NXX-X Effective Date and Block Activation – Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 230
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-57
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.1.11
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. On behalf of the service provider under test, create and activate a Subscription Version
from a Code Holder. The service provider under test is the ‘New’ service provider.
2. On behalf of the service provider under test, create an NPA-NXX-X whereby the
Subscription Version created in step 1 above, is respective to the NPA-NXX-X to be
created.
3. On behalf of the service provider under test, activate a respective Number Pool Block for the
NPA-NXX-X that was created in step 2 above. Verify that the Number Pool Block and
Pooled Subscription Versions exist. Verify that the Subscription Versions that was
activated in step 1 above exists as an LSPP port with a status of ‘Active’ where the service
provider under test is the current service provider for the port.
4. TN Used:______________________________
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION
subscriptionVersionNewSP-
Create request in CMIP (or
NCRQ – NewSpCreateRequest
in XML) to the NPAC SMS for
an Intra-Service Provider, Port-
to-Original, single TN,
Subscription Version for which
there is a currently ‘Active’
Subscription Version for which
they are the current Service
Provider. Specify the TN
NPAC NPAC SMS receives the M-ACTION
subscriptionVersionNewSP-Create request in CMIP (or NCRQ
– NewSpCreateRequest in XML) from the New/Current SP
SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 91
identified in the prerequisites
above.
2. The SOA sends an M-ACTION
subscriptionVersionNewSP-
Create in CMIP (or NCRQ –
NewSpCreateRequest in XML)
to the NPAC SMS for the
single TN and includes only the
following attributes:
subscriptionTN
subscriptionNewCurrentSP
subscriptionOldSP
subscriptionNewSP-DueDate
(seconds set to zeros)
subscriptionPortingToOriginal-
SPSwitch
2. NPAC NPAC SMS issues an M-CREATE
Request subscriptionVersionNPAC
to itself for the TN to create the
Subscription Version, sets the
subscriptionVersionStatus to
‘Pending’, and sets the
subscriptionNewSPCreationTimeSt
amp, and the
subscriptionModifedTimeStamp to
the current date and time.
NPAC NPAC SMS issues an M-CREATE Response to itself.
3. NPAC NPAC SMS issues an M-ACTION
Response
subscriptionVersionNPAC in CMIP
(or NCRR – NewSpCreateReply in
XML) to the New/Current SP
indicating it successfully received
the Intra-Service Provider, Port-to-
Original, Subscription Version
create request.
SP New/Current SP SOA receives the M-ACTION Response in
CMIP (or NCRR – NewSpCreateReply in XML).
4. NPAC NPAC SMS issues an M-EVENT-
REPORT to the New/Current SP
SOA based on their Customer TN
Range Notification Indicator:
1. If the setting is TRUE, NPAC
SMS issues an M-EVENT-
REPORT
subscriptionVersionRangeObjectCr
eation in CMIP (or VOCN –
SvObjectCreationNotification in
XML) specifying the following
attributes:
start TN
end TN
start SVID
end SVID
those attributes bulleted
below:
2. If the setting is FALSE, NPAC
SMS issues an M-EVENT-
NPAC New/Current SP SOA receives the M-EVENT-REPORT in
CMIP (or VOCN – SvObjectCreationNotification in XML)
from the NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 92
REPORT objectCreation in
CMIP (or VOCN –
SvObjectCreationNotification
in XML) specifying the
following attributes:
subscriptionVersionId
subscriptionTN
The following attributes will also be
sent in the ObjectCreation or
subscriptionVersionRangeObjectCr
eation notification:
subscriptionOldSP
subscriptionNewCurrentSP
subscriptionNewSP-
DueDate
subscriptionNewSP-
CreationTimeStamp
subscriptionVersionStatus
subscriptionTimerType (if
supported)
subscriptionBusinessType
(if supported)
5. SP New/Current SP SOA issues an M-
EVENT-REPORT Confirmation in
CMIP (or NOTR –
NotificationReply in XML) to the
NPAC SMS indicating it
successfully received the M-
EVENT-REPORT from the NPAC
SMS.
NPAC NPAC SMS receives the M-EVENT-REPORT Confirmation in
CMIP (or NOTR – NotificationReply in XML) from the
New/Current SP SOA.
6. SP Using their SOA, New/Current SP
Personnel perform a local query for
the Subscription Version created in
this test case.
SP The Subscription Version exists with a status of ‘Pending’, an
LNP type of ‘LISP’ and the Port-to-Original indicator set to
TRUE.
7. NPAC NPAC Personnel perform a query
for the Subscription Version created
in this test case.
NPAC The Subscription Version exists with a status of ‘Pending’, an
LNP type of ‘LISP’, and the Port-to-Original indicator set to
TRUE.
E. Pass/Fail Analysis, NANC 230-3 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 93
12.7 NANC 249 – Modification of Dates for a Disconnect Pending SV
NOTE: Service Provider’s whose systems cannot create the ‘failure’ scenarios that follow pass those test cases be
default. If their system does not ‘stop’ the invalid message before it goes across the interface, then their system
must be able to successfully execute the test case and handle the failure response from the NPAC SMS.
A. TEST IDENTITY
Test Case
Number:
NANC 249-1 SUT Priority: SOA Required
LSMS Required
Objective:
SOA – Service Provider Personnel submit a Subscription Version modify request for a
‘Disconnect-Pending’ Subscription Version, modifying the Effective Release Date and
Customer Disconnect Date to the current date/time or a date/time in the past. - Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 249
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-124, RR5-125, RR5-127, RR5-129,
RR5-126, RR5-11
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.7, B.5.4.1, B.5.4.1.1
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Disconnect-Pending’ exists on the
NPAC SMS for the Service Provider participating in this Test Case. The Subscription
Version should have an Effective Release Date and a Customer Disconnect Date currently
set to at least one day in the future.
2. TN Used __________________________________
Prerequisite SP
Setup:
Disconnect an ‘Active’ Subscription Version for which you are the Current Service Provider
and specify an Effective Release Date and a Customer Disconnect Date that are at least one day
in the future. The Effective Release and Customer Disconnect Dates do not have to be the same
date/time.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION Request
subscriptionVersionModify to
the NPAC SMS to modify the
Effective Release Date and
Customer Disconnect Date to
either the current dates/time or
some other date in the past, for
a single TN Subscription
Version that has a current status
of ‘Disconnect-Pending’.
NPAC NPAC SMS receives the M-ACTION Request
subscriptionVersionModify in CMIP (or MODQ –
ModifyRequest in XML) from the Current SP SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 94
2. The SOA sends an M-
ACTION
subscriptionVersionModify
request in CMIP (or MODQ –
ModifyRequest in XML) to the
NPAC SMS for the single TN
and modifies the
subscriptionCustomerDisconne
ctDate and the
subscriptionEffectiveReleaseDa
te to the current or past
date/times.
2. NPAC The NPAC SMS validates the SOA
request and issues an M-SET
Request subscriptionVersionNPAC
to itself, updating the modified
attributes and setting the
subscriptionModifiedTimeStamp to
the current date/time.
NPAC NPAC SMS receives the M-SET Request
subscriptionVersionNPAC.
3. NPAC The NPAC SMS issues an M-
ACTION Response
subscriptionVersionModify in
CMIP (or MODR – ModifyReply in
XML) to the Current SP SOA
indicating the request was
successfully processed by the
NPAC SMS.
SP Current SP SOA receives the M-ACTION Response in CMIP
(or MODR – ModifyReply in XML) from the NPAC SMS.
4. NPAC NPAC SMS issues an M-SET
Request subscriptionVersionNPAC
updating the
subscriptionVersionStatus to
‘Sending’ and setting the
subscriptionCustomerDisconnectDa
te and
subscriptionBroadcastTimeStamp.
NPAC NPAC SMS receives the M-SET subscriptionVersionNPAC
and issues an M-SET Response to itself.
5. NPAC If the donor Service Provider’s
TN Range Notification
indicator is set to TRUE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionRangeDono
rSP-CustomerDisconnectDate
in CMIP (or VCDN –
SvCustomerDisconnectDateNot
ification in XML) to the donor
Service Provider.
If the donor Service Provider’s
TN Range Notification
indicator is set to FALSE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionDonorSP-
CustomerDisconnectDate in
CMIP (or VCDN –
SvCustomerDisconnectDateNot
SP The donor Service Provider receives the M-EVENT-REPORT
in CMIP (or VCDN – SvCustomerDisconnectDateNotification
in XML) from the NPAC SMS and issues an M-EVENT-
REPORT Confirmation in CMIP (or NOTR –
NotificationReply in XML) back.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 95
ification in XML) to the donor
Service Provider.
The notification indicates the TN is
being disconnected with the
customer disconnect date.
6. NPAC NPAC SMS issues an M-DELETE
Request subscriptionVersion in
CMIP (or SVDD –
SvDeleteDownload in XML) to all
LSMSs that are accepting
downloads for the NPA-NXX for
Subscription Version that was
modified in Row 1 above.
LSMS Each LSMS receives the M-DELETE request in CMIP (or
SVDD – SvDeleteDownload in XML) from the NPAC SMS.
7. LSMS Each LSMS issues an M-DELETE
Response in CMIP (or DNLR –
DownloadReply in XML) back to
the NPAC SMS indicating they
successfully processed the M-
DELETE request.
NPAC NPAC SMS receives an M-DELETE Response in CMIP (or
DNLR – DownloadReply in XML) from each LSMS accepting
downloads for this NPA-NXX.
8. NPAC NPAC SMS issues an M-SET
Request subscriptionVersionNPAC
updating the
subscriptionVersionStatus to ‘Old’
and setting the
subscriptionModifiedTimeStamp
and
subscriptionDisconnectCompleteTi
meStamp.
NPAC NPAC SMS receives the M-SET subscriptionVersionNPAC
and issues an M-SET Response to itself.
9. NPAC NPAC SMS issues an M-EVENT-
REPORT
subscriptionVersionStatusAttribute
ValueChange in CMIP (or VATN –
SvAttributeValueChangeNotificatio
n in XML) to the Service Provider
SOA that issued the disconnect
request, indicating the Subscription
Version status is ‘Old’.
SP The SOA receives the M-EVENT-REPORT
subscriptionVersionStatusAttributeValueChange in CMIP (or
VATN – SvAttributeValueChangeNotification in XML) from
the NPAC SMS, and returns an M-EVENT-REPORT
Confirmation in CMIP (or NOTR – NotificationReply in XML)
to the NPAC SMS.
10. SP Using their SOA, New/Current SP
Personnel perform a local query for
the ‘Disconnect-Pending’
Subscription Version that was
modified and then subsequently
‘disconnected’ from the NPAC
network during this test case.
SP The Subscription Version exists with a status of ‘Old’, or
something equivalent to indicate that this Subscription Version
is no longer active.
11. NPAC NPAC Personnel perform a query
for the ‘Disconnect-Pending’
Subscription Version that was
modified and then subsequently
‘disconnected’ from the NPAC
network during this test case.
NPAC The Subscription Version exists with a status of ‘Old’.
E. Pass/Fail Analysis, NANC 249-1 Pass Fail NPAC Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 96
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 97
A. TEST IDENTITY
Test Case
Number:
NANC 249-2 SUT Priority: SOA Conditional
LSMS Conditional
Objective:
SOA – Service Provider Personnel submit a Subscription Version modify request for a range of
‘Disconnect-Pending’ Subscription Versions, modifying the Effective Release Date and
Customer Disconnect Date to a different date/time in the future. The range of Subscription
Versions had Effective Release Dates that were not the same prior to the modification. - Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 249
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-127
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.7
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a range of at least 20 Subscription Version with a status of ‘Disconnect-
Pending’ exist on the NPAC SMS for the Service Provider participating in this Test Case.
These Subscription Versions should have an Effective Release Date and a Customer
Disconnect Date currently set to at least one day in the future. Make sure that the set of
Subscription Versions have a wide range of different Effective Release Dates and a
Customer Disconnect Dates from one another.
2. TNs Used __________________________________
Prerequisite SP
Setup:
Disconnect a range of at least 20 ‘Active’ Subscription Versions for which you are the Current
Service Provider and specify a variety of different Effective Release Dates and a Customer
Disconnect Dates that are at least one day in the future. The Effective Release and Customer
Disconnect Dates should not have the same date/time – all should be deferred disconnects.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION Request
subscriptionVersionModify to
the NPAC SMS to modify the
Effective Release Date and
Customer Disconnect Date to a
date/time at least one day in the
future, for a range of at least 20
TNs that have a current status
of ‘Disconnect-Pending’.
2. The SOA sends an M-
ACTION
subscriptionVersionModify
request in CMIP (or MODQ –
ModifyRequest in XML) to the
NPAC SMS for the range of at
NPAC NPAC SMS receives the M-ACTION Request
subscriptionVersionModify in CMIP (or MODQ –
ModifyRequest in XML) from the Current SP SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 98
least 20 TNs and modifies the
subscriptionCustomerDisconne
ctDate and the
subscriptionEffectiveReleaseDa
te to a date/time at least one day
in the future.
2. NPAC The NPAC SMS validates the SOA
request and issues an M-SET
Request subscriptionVersionNPAC
to itself, updating the modified
attributes and setting the
subscriptionModifiedTimeStamp to
the current date/time.
NPAC NPAC SMS receives the M-SET Request
subscriptionVersionNPAC.
3. NPAC The NPAC SMS issues an M-
ACTION Response
subscriptionVersionModify in
CMIP (or MODR – ModifyReply in
XML) to the Current SP SOA
indicating the request was
successfully processed by the
NPAC SMS.
SP Current SP SOA receives the M-ACTION Response in CMIP
(or MODR – ModifyReply in XML) from the NPAC SMS.
4. SP Using their SOA, New/Current SP
Personnel perform a local query for
the ‘Disconnect-Pending’
Subscription Versions that were
modified during this test case.
SP The Subscription Versions exists with a status of ‘Disconnect-
Pending’ with the new Effective Release and Customer
Disconnect Dates that were specified in Row 1 above.
5. NPAC Personnel perform a query
for the ‘Disconnect-Pending’
Subscription Versions that were
modified during this test case.
NPAC The Subscription Versions exists with a status of ‘Disconnect-
Pending’ with the new Effective Release and Customer
Disconnect Dates that were specified in Row 1 above.
E. Pass/Fail Analysis, NANC 249-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 99
A. TEST IDENTITY
Test Case
Number:
NANC 249-3 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel submit a Subscription Version modify request for a
‘Disconnect-Pending’ Subscription Version, without specifying the Customer Disconnect Date -
Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 249
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-128, R5-39.1, R5-29.2
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.7
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Disconnect-Pending’ exists on the
NPAC SMS for the Service Provider participating in this Test Case. The Subscription
Version should have an Effective Release Date and a Customer Disconnect Date currently
set to at least one day in the future.
2. TN Used __________________________________.
Prerequisite SP
Setup:
Disconnect an ‘Active’ Subscription Version for which you are the Current Service Provider
and specify an Effective Release Date and a Customer Disconnect Date that are at least one day
in the future. The Effective Release and Customer Disconnect Dates do not have to be the same
date/time.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION Request
subscriptionVersionModify to
the NPAC SMS to modify the
Effective Release Date to either
the current date/time or some
other date in the past, for a
single TN Subscription Version
that has a current status of
‘Disconnect-Pending’.
2. The SOA sends an M-
ACTION
subscriptionVersionModify
request in CMIP (or MODQ –
ModifyRequest in XML) to the
NPAC SMS for the single TN
and modifies the
subscriptionEffectiveReleaseDa
te to the current or past
NPAC NPAC SMS receives the M-ACTION Request
subscriptionVersionModify in CMIP (or MODQ –
ModifyRequest in XML) from the Current SP SOA and
determines that the request violates system requirements.
The subscriptionCustomerDisconnectDate must be
populated in the modify request message.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 100
date/times. The message leaves
the
subscriptionCustomerDisconne
ctDate unpopulated.
2. NPAC The NPAC SMS issues an M-
ACTION Response
subscriptionVersionModify in
CMIP (or MODR – ModifyReply in
XML) to the Current SP SOA
indicating the request was not
successfully processed by the
NPAC SMS and includes an
appropriate error message,
‘invalidAurgumentValue’.
SP Current SP SOA receives the M-ACTION Response in CMIP
(or MODR – ModifyReply in XML) from the NPAC SMS.
3. SP Using their SOA, New/Current SP
Personnel perform a local query for
the ‘Disconnect-Pending’
Subscription Version that they
attempted to modify during this test
case.
SP The Subscription Version exists with a status of ‘Disconnect-
Pending’ with the original Effective Release and Customer
Disconnect Dates that were specified in the prerequisites above.
4. NPAC Personnel perform a query
for the ‘Disconnect-Pending’
Subscription Version that they
attempted to modify during this test
case.
NPAC The Subscription Version exists with a status of ‘Disconnect-
Pending’ with the original Effective Release and Customer
Disconnect Dates that were specified in the prerequisites above.
E. Pass/Fail Analysis, NANC 249-3 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 101
A. TEST IDENTITY
Test Case
Number:
NANC 249-4 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel submit a Subscription Version modify request for a
‘Disconnect-Pending’ Subscription Version, specifying an invalid format for the Effective
Release Date and/or Customer Disconnect Date - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 249
NANC FRS
Version Number:
3.2.0a Relevant
Requirement(s):
RR5-125
NANC IIS
Version Number:
3.2.0a Relevant
Flow(s):
B.5.2.7
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that a Subscription Version with a status of ‘Disconnect-Pending’ exists on the
NPAC SMS for the Service Provider participating in this Test Case. The Subscription
Version should have an Effective Release Date and a Customer Disconnect Date currently
set to at least one day in the future.
2. TN Used __________________________________.
Prerequisite SP
Setup:
Disconnect an ‘Active’ Subscription Version for which you are the Current Service Provider
and specify an Effective Release Date and a Customer Disconnect Date that are at least one day
in the future. The Effective Release and Customer Disconnect Dates do not have to be the same
date/time.
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP 1. Using the SOA, SP Personnel
submit an M-ACTION Request
subscriptionVersionModify to
the NPAC SMS to modify the
Effective Release and Customer
Disconnect Dates to either the
current date/time or some other
date in the past, for a single TN
Subscription Version that has a
current status of ‘Disconnect-
Pending’.
2. The SOA sends an M-ACTION
subscriptionVersionModify
request in CMIP (or MODQ –
ModifyRequest in XML) to the
NPAC SMS for the single TN
and modifies the
subscriptionCustomerDisconne
ctDate and the
NPAC NPAC SMS receives the M-ACTION Request
subscriptionVersionModify in CMIP (or MODQ –
ModifyRequest in XML) from the Current SP SOA and
determines that the request violates system requirements.
The subscriptionCustomerDisconnectDate and/or
subscriptionEffectiveReleaseDate must follow the valid
format defined in Table 3-6 Subscription Version Data
Model, of the FRS..
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 102
subscriptionEffectiveReleaseDa
te to the current or past
date/times. The message
includes both attributes but at
least one of these date/time
attributes is in an invalid
format. The valid format is
defined in Table 3-6
Subscription Version Data
Model of the FRS. This should
be a timestamp, month, day,
year, hour, minute, and
seconds.
2. NPAC The NPAC SMS issues an M-
ACTION Response
subscriptionVersionModify in
CMIP (or MODR – ModifyReply in
XML) to the Current SP SOA
indicating the request was not
successfully processed by the
NPAC SMS and includes an
appropriate error message,
‘invalidAurgumentValue’.
SP Current SP SOA receives the M-ACTION Response in CMIP
(or MODR – ModifyReply in XML) from the NPAC SMS.
3. SP Using their SOA, New/Current SP
Personnel perform a local query for
the ‘Disconnect-Pending’
Subscription Version that they
attempted to modify during this test
case.
SP The Subscription Version exists with a status of ‘Disconnect-
Pending’ with the original Effective Release and Customer
Disconnect Dates that were specified in the prerequisites above.
4. NPAC Personnel perform a query
for the ‘Disconnect-Pending’
Subscription Version that they
attempted to modify during this test
case.
NPAC The Subscription Version exists with a status of ‘Disconnect-
Pending’ with the original Effective Release and Customer
Disconnect Dates that were specified in the prerequisites above.
E. Pass/Fail Analysis, NANC 249-4 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 103
12.8 NANC 297 – Sending SV Problem During Recovery This section of test cases has been incorporated into test case 187-1.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 104
12.9 NANC 319 – NPAC Edit to Ensure NPA-NXX of LRN is in Same LATA as
NPA-NXX of Ported TN
NOTE: Service Provider’s whose systems cannot create the ‘failure’ scenarios that follow pass those test cases be
default. If their system does not ‘stop’ the invalid message before it goes across the interface, then their system
must be able to successfully execute the test case and handle the failure response from the NPAC SMS.
A. TEST IDENTITY
Test Case
Number:
NANC 319–1 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to create a Subscription Version specifying a TN and
an LRN with different LATA Ids. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR5-120
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.5.1.1, B.5.1.2
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify the NPA-NXX exists and is open for porting for the TN that is going to be used
during this test case.
2. Verify that the LRN exists for the Service Provider under test. Note the LATA ID for this
LRN _______________________.
3. Identify which TN is to be used in this test case TN: _____________________ and
respective LATA ID: ________________________.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using their SOA system, Service
Provider Personnel submit a
Subscription Version Create request
for a single TN.
The SOA system sends an M-
ACTION Request
subscriptionVersionNewSP-Create
in CMIP (or NCRQ –
NewSpCreateRequest in XML) to
the NPAC SMS to create the
subscriptionVersionNPAC
NPAC The NPAC SMS receives the M-ACTION Request in CMIP (or
NCRQ – NewSpCreateRequest in XML) from the Request
from the Service Provider’s SOA and determines the following:
The LATA ID for the TN does not match the LATA ID for the
LRN. (This violates system requirements.)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 105
(Subscription Version) on the
NPAC SMS.
The following attributes must be
specified:
subscriptionTN or a valid
subscriptionVersionTN-Range
(specify the TN identified in
the prerequisites)
subscriptionNewCurrentSP
subscriptionOldSP
subscriptionNewSP-DueDate
(seconds set to zero)
subscriptionLNPType
subscriptionLRN (specify the
LRN identified in the
prerequisites)
subscriptionNewSPMediumTi
merIndicator – if supported by
the Service Provider SOA
Specify a combination of valid and
invalid DPC/SSN data for the
following attributes.
subscriptionCLASS-DPC
subscriptionCLASS-SSN
subscriptionLIDB-DPC
subscriptionLIDB-SSN
subscriptionCNAM-DPC
subscriptionCNAM-SSN
subscriptionISVM-DPC
subscriptionISVM-SSN
subscriptionWSMSC-DPC - if
supported by the Service
provider SOA
subscriptionWSMSC-SSN - if
supported by the Service
Provider SOA
The following attributes are
optional:
subscriptionEndUser
LocationValue
subscriptionEndUser
LocationType
subscriptionBillingID
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or NCRR – NewSpCreateReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or NCRR – NewSpCreateReply in XML).
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version does not
exist on the NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 106
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version does not exist on the local
database.
E. Pass/Fail Analysis, NANC 319-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 107
A. TEST IDENTITY
Test Case
Number:
NANC 319–2 SUT Priority: SOA Required
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to modify a ‘Pending’, Subscription Version
specifying an LRN with a different LATA Id from the NPA-NXX of the TN in the Subscription
Version. – Failure
Note: Per IIS3_4_1aPart2, the flow for scenario B.5.2.4 is not available over the XML
interface. This functionality is handled by flow B.5.2.3, “SubscriptionVersion Modify Prior to
Activate Using M-ACTION”.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR5-123
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.5.2.3, B.5.2.4
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Verify that the NPA-NXX exists and is open for porting for the TN that is going to be used
during this test case. TN__________________
2. Verify that a ‘Pending’ Subscription Version exists for the TN that is going to be used
during this test case. Note the current LRN for the Subscription Version _____________.
3. Identify another LRN that exists for the Service Provider under test which has a different
LATA ID from the TN of the Subscription Version used during this test case
______________.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using their SOA system, Service
Provider Personnel submit a request
to the NPAC SMS to modify a
single TN, ‘Pending’ Subscription
Version that already exists on the
NPAC SMS.
Specify the TN and the new LRN
identified in the prerequisites above.
The request must specify the TN
and the version status or the version
ID of the Subscription Version to be
NPAC The NPAC SMS receives the M-ACTION/M-SET Request in
CMIP (or MODQ – ModifyRequest in XML) from the Service
Provider’s SOA and determines the following:
The LATA ID for the TN of the Subscription Version and the
LATA ID for the modified LRN value do not match. (This
violates system requirements.)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 108
modified and the data to be
modified.
The Service Provider SOA submits
an M-ACTION Request
subscriptionVersionModify in
CMIP (or MODQ – ModifyRequest
in XML) or an M-SET Request
subscriptionVersionNPAC (not
available over the XML interface)
(depending on the system
implementation) to the NPAC SMS
lnpSubscription object to update the
‘Pending’ Subscription Version.
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or MODR – ModifyReply in XML)
or M-SET Response failure (not
available over the XML interface)
(depending on the message received
in Row 1) indicating an error with
the request to the SOA.
SP The Service Provider SOA receives the Response in CMIP (or
MODR – ModifyReply in XML) from the NPAC SMS.
3. NPAC NPAC Personnel perform a query
for the Subscription Version.
NPAC NPAC Personnel verify that the Subscription Version exists
with a status of ‘Pending’ however, the attributes were not
modified. The original LRN identified in the prerequisites
above is still associated with the TN/Subscription Version used
during this test case.
4. SP Service Provider Personnel, perform
a local query for the Subscription
Version.
SP Verify that the Subscription Version exists on the local database
with the original attribute values.
The original LRN identified in the prerequisites above is still
associated with the TN/Subscription Version used during this
test case.
E. Pass/Fail Analysis, NANC 319-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 109
A. TEST IDENTITY
Test Case
Number:
NANC 319–3 SUT Priority: SOA Required
LSMS N/A
Objective:
NPAC OP GUI – NPAC Personnel submit a mass update request for a range of ‘Active’,
Subscription Versions where some of the Subscription Versions exist with valid LATA ID
relationships and some of the Subscription Versions exist with invalid LATA ID relationships.
Specify new DPC/SSN data. Subscription Versions with valid LATA ID relationships will be
updated and Subscription Versions that exist without valid LATA ID relationships will not be
updated. - Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-254
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.8.3
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Activate a contiguous range of at least 100 SVs for the Service Provider under test where the
LATA ID of the NPA-NXX for the range of SVs is THE SAME AS the LATA ID of the
LRN specified in the subscription versions. SV Range A________________________.
1. For example, LRN=303-555-0000 has a LATA ID of 656 and is owned by SP
under test.
2. Activate SVs (303-100-1000 through 303-100-1100) with LRN (303-555-0000),
NPA-NXX 303-100 has a LATA ID of 656
2. Activate another contiguous range of at least 100 SVs for the Service Provider under test
where the LATA ID of the NPA-NXX for the range of SVs is DIFFERENT THAN the
LATA ID of the LRN specified in the subscription versions (pre 3.2 valid data). SV Range
B __________________________________.
3. For example, LRN=303-888-0000 has a LATA ID of 658 and is owned by SP
under test.
4. Activate SVs (303-100-2000 through 303-100-2100) with LRN (303-888-0000),
NPA-NXX 303-100 has a LATA ID of 656
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel submit a Mass Update
request for a range of ‘Active’
Subscription Versions (specify SV
Range A and SV Range B identified
in the prerequisites above).
NPAC The NPAC SMS searches the Subscription Version database for
Subscription Versions that match the input Mass Update
criteria.
The NPAC SMS determines that a subset of the TNs in the
Subscription Version range have a LATA ID different from the
LATA ID of the associated LRN attribute. The NPAC SMS
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 110
Modify the at least one set of
DPC/SSN data for these
Subscription Versions.
makes an entry to the Mass Update Exception Report for these
TNs that contain NPA-NXXs where the LATA ID does not
match the LATA ID of the associated LRN, and continues
updating the remaining Subscription Versions that meet the
Mass Update criteria.
2. NPAC NPAC SMS sends multiple M-
SET(s) in CMIP (or SVMD –
SvModifyDownload in XML) for
each contiguous range of
Subscription Versions to all LSMSs
that are accepting downloads for the
NPA-NXXs of the Subscription
Versions to update the DPC/SSN
value for those Subscription
Versions whose LATA IDs of the
NPA-NXXs matches the LATA ID
of the associated LRN.
SP All LSMSs that are accepting downloads for the NPA-NXXs of
the Subscription Versions being updated, receive the M-SET
request(s) in CMIP (or SVMD – SvModifyDownload in XML)
from the NPAC SMS to modify the DPC/SSN data.
The LSMSs issue an M-SET Response(s) in CMIP (or DNLR –
DownloadReply in XML) indicating they successfully
processed the NPAC SMS request(s).
These M-SET Requests are for the Subscription Versions that
were successfully updated based on the Mass Update criteria –
and does not include those Subscription Versions that could not
be updated based on invalid LATA ID relationships. The
Subscription Versions that could not be updated are included on
the Mass Update Exception report.
3. NPAC 1. If the current Service Provider’s
TN Range Notification
Indicator is set to TRUE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionRangeStatu
sAttributeValueChange in
CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) for the range of
Subscription Versions that were
updated indicating the status is
now ‘Active’.
2. If the current Service Provider’s
TN Range Notification
Indicator is set to ‘FALSE’,
NPAC SMS issues a
subscriptionVersionStatusAttri
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) for each
Subscription Version that was
updated, indicating the status is
now ‘Active’.
SP The current Service Provider receives the M-EVENT-REPORT
in CMIP (or VATN – SvAttributeValueChangeNotification in
XML) from the NPAC SMS and issues an M-EVENT-
REPORT response in CMIP (or NOTR – NotificationReply in
XML) indicating it successfully received the message.
4. NPAC NPAC Personnel generate a Mass
Update Exception report.
NPAC Verify that the subset of Subscription Versions within the Mass
Update request who’s LATA ID for the NPA-NXX of the TN
that did not match the LATA ID for the associated LRN
attribute are included on the report.
5. SP Service Provider Personnel perform
a local query on their LSMS to
verify the Mass Update was
completed.
SP On the LSMS verify:
1. The subset of Subscription Versions within the Mass
Update request who’s LATA ID for the NPA-NXX of the
TN that did not match the LATA ID for the associated
LRN attribute were not updated with the new DPC/SSN
value(s).
2. The subset of Subscription Versions within the Mass
Update request who’s LATA ID for the NPA-NXX of the
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 111
TNs did match the LATA ID for the associated LRN
attribute were updated with the new DPC/SSN value.
6. NPAC NPAC Personnel perform a full
audit for the subscription version
range specified in the Mass Update
request.
NPAC Verify that there are no discrepancies found.
1. The subscription versions who’s LATA ID for the NPA-
NXX of the TNs did not match the LATA ID for the
associated LRN attribute were not updated – they still exist
in their previous state.
2. All other subscription versions specified in the Mass
Update criteria were updated appropriately.
E. Pass/Fail Analysis, NANC 319-3 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail NPAC Personnel were able to view the Mass Update Exception report that included the TNs that were not
updated because the LATA ID of their NPA-NXX does not match the LATA ID for the associated LRN
attribute.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 112
A. TEST IDENTITY
Test Case
Number:
NANC 319–4 SUT Priority: SOA Conditional
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to create a Number Pool Block specifying an LRN
with a different LATA Id than the TNs in the Number Pool Block. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-334
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.4.4.1
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Identify the Number Pool Block that will be used during this test case (NPA-NXX-X
_________________.
2. Verify that the NPA-NXX exists and is open for porting for the Number Pool Block that is
going to be used during this test case.
3. Verify that the NPA-NXX-X exists respective to the Number Pool Block that is going to be
used during this test case.
4. Verify that there are no contaminated TNs or ‘Pending-Like’ Subscription Versions for the
range of TNs in the NPA-NXX-X.
5. Identify an LRN that already exists on the NPAC SMS for the Service Provider under test
which has a LATA ID different than the Number Pool Block identified above to be used
during this test case ___________________.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, Service Provider
Personnel, submit a M-ACTION
numberPoolBlock-Create Request
in CMIP (or PBCQ –
NpbCreateRequest in XML) to the
NPAC SMS to create a Number
Pool Block.
The request must include the
following attributes:
numberPoolBlockNPA-NXX-X
(specify the NPA-NXX-X
identified in the prerequisites)
numberPoolBlockSPID
NPAC The NPAC SMS receives the M-ACTION numberPoolBlock-
Create Request in CMIP (or PBCQ – NpbCreateRequest in
XML) from the Service Provider’s SOA and determines the
following:
The LATA ID for the NPA-NXX-X specified in the request and
the LATA ID for the LRN specified in the request do not
match. (This violates system requirements.)
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 113
numberPoolBlockLRN (specify the
LRN identified in the
prerequisites)
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or PBCR – NpbCreateReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or PBCR – NpbCreateReply in XML).
3. NPAC NPAC Personnel perform a query
for the Number Pool Block and
respective ‘Pooled’ Subscription
Versions Service Provider personnel
attempted to schedule during this
test case.
NPAC NPAC Personnel verify that the Number Pool Block and
respective ‘Pooled’ Subscription Versions do not exist on the
NPAC SMS.
4. SP Service Provider Personnel, perform
a local query for the Number Pool
Block and the respective ‘Pooled’
Subscription Versions they
attempted to schedule during this
test case.
SP Verify that the Number Pool Block and the respective ‘Pooled’
Subscription Versions do not exist on the local database.
E. Pass/Fail Analysis, NANC 319-4 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 114
A. TEST IDENTITY
Test Case
Number:
NANC 319–5 SUT Priority: SOA Conditional
LSMS N/A
Objective:
SOA – Service Provider Personnel attempt to modify a Number Pool Block specifying an LRN
with a different LATA ID than the TNs in the Number Pool Block. - Failure
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-335
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.4.4.13
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Identify a Number Pool Block that already exists (with a status of ‘Active’ and an empty
Failed SP List) on the NPAC SMS for the Service Provider under test to be used during this
test case ____________________________.
2. Identify an LRN that already exists on the NPAC SMS for the Service Provider under test
that has a LATA ID different from the Number Pool Block that has been identified to be
used during this test case _______________________.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. SP Using the SOA, Service Provider
Personnel submit an M-SET
Request numberPoolBlock in
CMIP (or PBMQ –
NpbModifyRequest in XML) to
modify a Number Pool Block.
Modify the numberPoolBlockLRN
(specify the LRN identified in the
prerequisites)
NPAC The NPAC SMS receives the M-SET Request
numberPoolBlock in CMIP (or PBMQ – NpbModifyRequest in
XML) from the Service Provider’s SOA and determines the
following:
The LATA ID of the Number Pool Block specified in the
modify request and the LATA ID of the LRN to be modified to,
do not match. (This violates system requirements.)
2. NPAC The NPAC SMS issues an M-
ACTION Response failure in CMIP
(or PBMR – NpbModifyReply in
XML) indicating an error with the
request to the SOA.
SP The Service Provider SOA receives the M-ACTION Response
in CMIP (or PBMR – NpbModifyReply in XML).
3. NPAC NPAC Personnel perform a query
for the Number Pool Block and
respective ‘Pooled’ Subscription
Versions Service Provider personnel
NPAC NPAC Personnel verify that the Number Pool Block and
respective ‘Pooled’ Subscription Versions were not modified on
the NPAC SMS.
The original LRN is still associated with the Number Pool
Block.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 115
attempted to modify during this test
case.
4. SP Service Provider Personnel, perform
a local query for the Number Pool
Block and the respective ‘Pooled’
Subscription Versions they
attempted to modify during this test
case.
SP Verify that the Number Pool Block and the respective ‘Pooled’
Subscription Versions were not modified on the local database.
The original LRN is still associated with the Number Pool
Block.
E. Pass/Fail Analysis, NANC 319-5 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 116
A. TEST IDENTITY
Test Case
Number:
NANC 319–6 SUT Priority: SOA N/A
LSMS Required
Objective:
NPAC OP GUI – NPAC Personnel submit a mass update request including at least three
complete Number Pool Blocks where two of the Number Pool Blocks exist with valid LATA ID
relationships and one Number Pool Block exists with invalid LATA ID relationships. Specify
new DPC/SSN data. Number Pool Blocks with valid LATA ID relationships will be updated
and the Number Pool Block that exists with invalid LATA ID relationships will not be updated.
- Success
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 319
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-254
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
B.8.3
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. Activate two NPBs for the Service Provider under test where the LATA ID of the NPA-NXX
for the TNs within the block is the SAME AS the LATA ID of the LRN(s) specified in the
NPBs. NPB A __________________________, NPB B _______________________.
1. For example, LRN=303-333-0000 has a LATA ID of 656 and is owned by SP
under test.
2. Activate NPB A (303-100-3) with LRN (303-333-0000), and Activate NPB B
(303-100-7) with LRN (303-333-0000). NPA-NXX 303-100 has a LATA ID
of 656.
2. Activate another NPB for the Service Provider under test where the LATA ID of the NPA-
NXX for the TNs within the block is DIFFERENT THAN the LATA ID of the LRN
specified in the NPB (pre 3.2 valid data). NPB C_________________________________.
3. For example, LRN=303-555-0000 has a LATA ID of 658 and is owned by SP
under test.
4. Activate NPB C (303-100-4) with LRN (303-888-0000), NPA-NXX 303-100
has a LATA ID of 656
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel submit a Mass Update
request for a range TNs that
includes three Number Pool Blocks
(identified in the prerequisites
above).
NPAC The NPAC SMS searches the Subscription Version database for
Subscription Versions that match the input Mass Update
criteria.
The NPAC SMS determines that the request completely
includes three Number Pool Blocks and the range of TNs for
one of the Number Pool Blocks have a LATA ID different from
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 117
Modify at least one set of DPC/SSN
data for these Number Pool Blocks
the LATA ID of the associated LRN attribute. The NPAC SMS
makes an entry to the Mass Update Exception Report for these
TNs/Number Pool Block where the LATA ID for the associated
LRN does not match the LATA ID of the respective NPA-
NXX, and continues updating the remaining Subscription
Versions that meet the Mass Update criteria.
2. NPAC NPAC SMS sends to all LSMSs that
are accepting downloads for the
NPA-NXX(s):
to those LSMSs, NPAC SMS
issues M-SET Request(s)
numberPoolBlock in CMIP (or
PBMD – NpbModifyDownload
in XML) to update the
DPC/SSN attribute(s) for the
two Number Pool Blocks who’s
LATA ID for the respective
NPA-NXX matches the LATA
ID for the associated LRN
attribute value – to update the
DPC/SSN value(s).
to those LSMSs, NPAC SMS
issues M-SET Request(s)
subscriptionVersion in CMIP
(or SVMD –
SvModifyDownload in XML)
for each contiguous range of
non-pooled TN’s within the
Mass Update TN range who’s
LATA ID for the respective
NPA-NXX match the
associated LRN attribute value
– to update the DPC/SSN
value(s).
SP All LSMSs that are accepting downloads for the NPA-NXX of
the Number Pool Block objects and Subscription Versions
being updated, receive the M-SET Request(s) in CMIP (or
PBMD/SVMD – NpbModifyDownload/SvModifyDownload in
XML) from the NPAC SMS to modify the DPC/SSN value(s).
The LSMSs issue an M-SET Response(s) in CMIP (or DNLR –
DownloadReply in XML) indicating they successfully
processed the NPAC SMS request.
These M-SET Requests are for the Number Pool Blocks and
Subscription Versions that were successfully updated based on
the Mass Update criteria – and does not include those Number
Pool Blocks or Subscription Versions that could not be updated
based because the LATA ID of the respective NPA-NXX did
not match the LATA ID of the associated LRN.. The Number
Pool Blocks and Subscription Versions that could not be
updated are included on the Mass update Exception report.
3. NPAC 1. If the current Service Provider’s
TN Range Notification
Indicator is set to TRUE,
NPAC SMS issues an M-
EVENT-REPORT
subscriptionVersionRangeStatu
sAttributeValueChange in
CMIP (or VATN –
SvAttributeValueChangeNotifi
cation in XML) for the range of
Subscription Versions not of
LNP Type = ‘POOL’ out of the
range of Subscription Versions
that were updated indicating the
status is now ‘Active’.
2. If the current Service Provider’s
TN Range Notification
Indicator is set to ‘FALSE’,
NPAC SMS issues a
subscriptionVersionStatusAttri
SP The current/Block Holder Service Provider receives the M-
EVENT-REPORT(s) in CMIP (or VATN –
SvAttributeValueChangeNotification in XML) from the NPAC
SMS and issues an M-EVENT-REPORT response in CMIP (or
NOTR – NotificationReply in XML) indicating it successfully
received the message.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 118
buteValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) for each
Subscription Version not of
LNP Type = ‘POOL’ out of the
range of Subscription Versions
that were updated, indicating
the status is now ‘Active’.
3 If the numberPoolBlockSOA-
Origination indicator is set to
‘TRUE’ for the Number Pool
Block(s) updated, NPAC SMS
issues an M-EVENT-REPORT
numberPoolBlockStatusAttribu
teValueChange in CMIP (or
VATN –
SvAttributeValueChangeNotifi
cation in XML) to the Block
Holder SOA for the Number
Pool Block objects that were
updated indicating the status is
‘Active’.
4. NPAC NPAC Personnel generate a Mass
Update Exception report.
NPAC Verify that the subset of Number Pool Blocks/Subscription
Versions within the Mass Update request who’s LATA ID for
the respective NPA-NXX that did not match the LATA ID for
the associated LRN attribute are included on the report.
5. SP Service Provider Personnel perform
a local query on their LSMS to
verify the Mass Update was
completed.
SP On the LSMS verify:
1. The subset Subscription Versions (both Pooled and non-
Pooled) within the Mass Update request who’s LATA ID
for the respective NPA-NXX that did not match the LATA
ID for the associated LRN attribute were not updated with
the new DPC/SSN value(s).
2. The subset of Subscription Versions (both Pooled and non-
Pooled) within the Mass Update request who’s LATA ID
for the respective NPA-NXX did match the LATA ID for
the associated LRN attribute were updated with the new
DPC/SSN value(s).
3. EDR LSMSs only, the Number Pool Blocks within the
Mass Update request who’s LATA ID for the respective
NPA-NXX that did not match the LATA ID for the
associated LRN attribute was not updated with the new
DPC/SSN value(s).
4. EDR LSMSs only, the Number Pool Blocks within the
Mass Update request who’s LATA ID for the respective
NPA-NXX that did match the LATA ID for the associated
LRN attribute was updated with the new DPC/SSN
value(s).
E. Pass/Fail Analysis, NANC 319-6 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 119
Pass Fail NPAC Personnel were able to view the Mass Update Exception report that included the TNs/Number Pool
Blocks that were not updated because the LATA ID of their respective NPA-NXX does not match the LATA ID
for the associated LRN attribute.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 120
12.10 NANC 322 – Clean Up of Failed SP List Based on Service Provider BDD
Response File
A. TEST IDENTITY
Test Case
Number:
NANC 322-1 SUT Priority: SOA N/A
LSMS Conditional
Objective:
LSMS – Service Provider Personnel create a Bulk Data Download Response File for
Subscription Version data. NPAC Personnel process the Bulk Data Download Response File.
The Service Provider was previously on the Failed SP List for at least some of the Subscription
Versions in the respective file. Verification steps are performed to ensure the Service
Provider’s LSMS is now in synch with the NPAC SMS. - Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 322
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-330, RR3-329, RR3-332, RR3-333,
RR3-325, RR3-326
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NANC 169-1
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 121
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ from the NPAC SMS, NPAC personnel perform the
following functions:
a) Modify a (unique) range of 500, ‘Active’ Subscription Versions where the Service
Provider under test is the Current Service Provider. . Use simulators that are not
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
these Subscription Versions exist with a status of ‘Active’ and a Failed SP List. (SV
group 2a______________)
b) Create a filter for the NPA-NXX for which you created 500, ‘Pending’ Subscription
Versions in 1a) above.
Activate these 500, ‘Pending’ Subscription Versions. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX.
Verify that the status for all 500 is ‘Active’ on the NPAC SMS. (SV group
2b______________________)
Disconnect 250 of these now, ‘Active’ Subscription Versions specifying Effective
Release and Customer Disconnect dates in the future. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that the status of these 250 Subscription Versions is ‘Disconnect-Pending’. (SV
group 2b1___________)
Remove the filter for this NPA-NXX for the Service Provider under test so that
this range of Subscription Versions will be included in the Bulk Data Download
File.
c) Create and Activate 100 Intra-Service Provider Subscription Versions using an NPA-
NXX that is open for porting and for which the Service Provider under test is
accepting downloads for this NPA-NXX. This Service Provider is neither the Old or
New Service Provider for these Subscription Versions. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. Verify
that the Subscription Versions have a status of ‘Partial-Fail’. (SV group 2c
___________________)
d) Activate 50 Subscription Versions with a status of ‘Pending’. The Service Provider
under test is the New Service Provider for these Subscription Versions. Use
simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that these Subscription Versions have a status of ‘Partial-Fail’.
(SV group 2d_________________) .
e) Create and concur to a range of 100, ‘Pending’ Subscription Versions where the
Service Provider under test is the New Service Provider. (SV group
e__________________)
f) Put simulated SPID LSMS in recovery. Use at least one simulator that is associated
with the NPAC and is accepting downloads for this NPA-NXX. Verify that the
Service Provider under test is accepting downloads for this NPA-NXX. Activate 50
‘pending’ SVs in group f above. Verify that these subscription versions have a status
of ‘sending’. (SV group f__________________) During the test case retry timers will
exhaust, and then the status of the SVs should be ‘Partial-Fail’.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Subscription Data,
specifying Active/Disconnect
Pending/Partial Failure
Subscription Versions Only and
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File and automatically
“FTP’s” the file to the Service Provider’s directory on the
NPAC SMS.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 122
specifying the TN range identified
in the prerequisites above, for the
Service Provider under test.
2. SP Service Provider Personnel receive
the Bulk Data Download File and
load the file into their LSMS.
SP The LSMS successfully processes the Bulk Data Download file
and reflects the updates described in the prerequisites above.
The systems are still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Subscription Data to verify
that the Subscription Version data
was loaded.
SV group a
SV group b
SV group b1
SV group c
SV group d
SV group f
SP Using the LSMS system, verify:
SV group a exists on the LSMS. Verify that all of them
reflect the ‘modified’ SV values from the prerequisites
above.
SV group b exists on the LSMS.
SV group b1 exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
SV group f exists on the LSMS.
4. SP Service Provider personnel/system
generate a Bulk Data Download
Response File for the original Bulk
Data Download file and places it in
the Service Provider’s directory on
the NPAC SMS.
NPAC NPAC SMS processes the Bulk Data Download Response File
for the original file, and updates the Subscription Versions
appropriately.
5. NPAC NPAC Personnel query for the
Subscription Version data included
in the Bulk Data Download File:
SV group a
SV group b
SV group b1
SV group c
SV group d
SV group f
NPAC Verify the following:
SV group a exists with a status of ‘Active’ and an empty
Failed SP List.
SV group b exists with a status of ‘Active’ and an empty
Failed SP List.
SV group b1 exists with a status of ‘Disconnect-Pending’
and an empty Failed SP List.
SV group c exists with a status of ‘Active’ and an empty
Failed SP List.
SV group d exists with a status of ‘Active’ and an empty
Failed SP List.
SV group f exists with a status of ‘Sending’.
6. SP After all NPAC ‘retry timers’ for
the Subscription Versions specified
in the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associate’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates with the NPAC SMS
without recovering additional information
7. NPAC NPAC Personnel bring the
simulated SPID LSMS that was in
recovery in Prerequisite step f
above, out of recovery.
NPAC Verify that the simulated SPID that was in recovery during step
g of the prerequisites is now out of recovery. Verify that the 50
subscription versions that were activated while this SPID was in
recovery now have a status of ‘Partial Fail’.
8. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX
included in the range of TNs
specified in the prerequisites above
for the Service Provider’s LSMS to
verify that all the appropriate
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 123
updates were processed from the
Bulk Data Download File by the
LSMS.
SV group a exists on the LSMS. Verify that all of them
reflect the ‘modified’ SV values from the prerequisites
above.
SV group b exists on the LSMS.
SV group b1 exists on the LSMS.
SV group c exists on the LSMS.
SV group d exists on the LSMS.
SV group f exists on the LSMS.
E. Pass/Fail Analysis, NANC 322-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Bulk Data Download Response File was processed in a timely fashion.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 124
A. TEST IDENTITY
Test Case
Number:
NANC 322-2 SUT Priority: SOA N/A
LSMS Conditional
Objective:
LSMS – Service Provider Personnel create a Bulk Data Download Response File for Number
Pool Block data. NPAC Personnel process the Bulk Data Download Response File. The
Service Provider was previously on the Failed SP List for at least some of the Number Pool
Blocks in the respective file. Verification steps are performed to ensure the Service Provider’s
LSMS is now in synch with the NPAC SMS. - Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 322
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-330, RR3-331, RR3-332, RR3-333,
RR3-325, RR3-327
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 125
Prerequisite
NPAC Setup:
While the LSMS is ‘dis-associated’ from the NPAC SMS, NPAC personnel perform the
following functions:
a) Modify an existing Number Pool Block for which the Service Provider under test is
accepting downloads. Use simulators that are associated with the NPAC and are
receiving downloads for this NPA-NXX. Verify that the Number Pool Block and
respective Subscription Versions have a status of ‘Partial-Fail’ and the Service
Provider under test is on the Failed SP List (SV group a______________), (NPB
group a ______________).
b) Delete an existing NPA-NXX-X with a respective Number Pool Block for which the
Service Provider under test is accepting downloads, and none of the respective
‘Pooled’ Subscription Versions have been ported away. Use simulators that are
associated with the NPAC and are receiving downloads for this NPA-NXX. (SV
group 2b___________), (NPB group 2b__________________).
c) Activate a Number Pool Block (associated with another NPA-NXX-X that has
reached its Effective date ) for an NPA-NXX for which the Service Provider under test
is NOT accepting downloads - it is another Service Provider’s Number Pool Block.
Use simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that the Number Pool Block and respective Subscription Versions
have has a status of ‘Active’. (SV group c_____________________) (NPB
c______________)
d) Modify the Number Pool Block that was just activated in step ‘c’ above. Make sure
that the Service Provider under test is now accepting downloads for this NPA-NXX.
Use simulators that are associated with the NPAC and are receiving downloads for this
NPA-NXX. Verify that the Number Pool Block and respective Subscription Versions
have has been updated and have a status of ‘Active’ with a Failed SP List. (SV group c
and NPB c).
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Number Pool Block
Data, specifying Latest View of
Activity a valid Time Range and
specifying the range identified in
the prerequisites above, for the
Service Provider participating in the
test case.
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their LSMS
systems.
SP The LSMS successfully processes the Bulk Data Download
file(s) and reflects the updates described in the prerequisites
above.
The system is still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their LSMS, perform a local query
for the Pooled Subscription and/or
Number Pool Block Data to verify
that the data was loaded.
Pooled SV group a
SP Using the LSMS system, verify:
Pooled SV group a exists on the LSMS with the modified
attributes specified in step a of the prerequisites above.
Pooled SV group b does not exist on the LSMS.
Pooled SV group c exists on the LSMS with the modified
attributes specified in step d of the prerequisites above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 126
Pooled SV group b
Pooled SV group c
NPB group a
NPB group b
NPB group c
NPB group a exists on the LSMS with the modified
attributes specified in step a of the prerequisites above.
NPB group b does not exist on the LSMS.
NPB group c exists on the LSMS with the modified
attributes specified in step d of the prerequisites above.
4. SP Service Provider personnel/system
generate a Bulk Data Download
Response File for the original Bulk
Data Download file(s) and places it
in the Service Provider’s directory
on the NPAC SMS.
NPAC NPAC SMS processes the Bulk Data Download Response
File(s) for the original file, and updates the Pooled Subscription
Versions/Number Pool Blocks appropriately.
5. NPAC NPAC Personnel query for the
Pooled Subscription Version and
Number Pool Block data included in
the Bulk Data Download File:
Pooled SV group a
Pooled SV group b
Pooled SV group c
NPB group a
NPB group b
NPB group c
NPAC Verify the following:
Pooled SV group a exists with a status of ‘Active’ and an
empty Failed SP List.
Pooled SV group b exists with a status of ‘Old’ and an
empty Failed SP List.
Pooled SV group c exists with a status of ‘Active’ and an
empty Failed SP List.
NPB group a exists with a status of ‘Active’ and an empty
Failed SP List.
NPB group b exists with a status of ‘Old’ and an empty
Failed SP List.
NPB group c exists with a status of ‘Active’ and an empty
Failed SP List.
6. SP After all NPAC ‘retry timers’ for
the Subscription Versions and
Number Pool Blocks specified in
the prerequisites above have
expired, Service Provider personnel
perform appropriate steps to
‘associated’ with the NPAC SMS
such that they will not recover
additional information.
SP The LSMS successfully re-associates with the NPAC SMS
without recovering additional information.
7. NPAC NPAC Personnel perform multiple
Full audits for each NPA-NXX
included in the range of TNs
specified in the prerequisites above
for the Service Provider’s LSMS to
verify that all the appropriate
updates were processed from the
Bulk Data Download File by the
LSMS.
NPAC Using the Audit Results Log, verify that there were no updates
made. If any updates were made as a result of running this
audit, this test case fails.
Verify that:
Pooled SV group a exists on the LSMS with the modified
attributes specified in step a of the prerequisites above.
Pooled SV group b does not exist on the LSMS.
Pooled SV group c exists on the LSMS with the modified
attributes specified in step d of the prerequisites above.
NPB group a exists on the LSMS with the modified
attributes specified in step a of the prerequisites above.
NPB group b does not exist on the LSMS.
NPB group c exists on the LSMS with the modified
attributes specified in step d of the prerequisites above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 127
E. Pass/Fail Analysis, NANC 322-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Pass Fail Bulk Data Download Response File was processed in a timely fashion.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 128
12.11 NANC 323 – Partial Migration of SPID via Mass Update Test Cases
This section of test cases shall be executed only during the group test phase due to the impact to the entire test
environment.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 129
12.12 NANC 354 – Delta Download File Creation by Time Range for Network Data
NOTE: SOA Network Data Management, LSMS Network Data Management, NPAC Customer SOA NPA-NXX-
X Indicator and NPAC Customer LSMS NPA-NXX-X Indicator (s) are all set to production values for the Service
Provider under test.
Network Data filters need not be set to execute NANC 354 test cases.
A. TEST IDENTITY
Test Case
Number:
NANC 354-1 SUT Priority: SOA Required
LSMS Required
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Network Data –
Specifying the Latest View of Network Data Activity and a valid time range. Verification steps
are preformed to ensure the BDD file was processed successfully by the Service Provider
system. - Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 354
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-220, RR3-301, RR3-302, RR3-304,
RR3-311
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 130
Prerequisite
NPAC Setup:
1. While the SOA and LSMS are ‘associated’ with the NPAC SMS, NPAC personnel perform
the following functions:
a) Create an NPA-NXX that is not yet open for porting (Effective date is in the future) on
behalf of the Service Provider under test( NPA-NXX 1a_____________).
b) Create an NPA-NXX-X respective to NPA-NXX 1a on behalf of the Service Provider
under test (NPA-NXX-X 1a_________________).
c) Create an NPA-NXX with an Effective date equal to today, on behalf of the Service
Provider under test (so that it is now open for porting) (NPA-NXX
1c_________________).
d) Immediately after initiating requests 1a), 1b) and 1c) above, dis-associate the Service
Provider’s SOA and LSMS systems.
2. While the SOA and LSMS are ‘dis-associated’ with the NPAC SMS, NPAC personnel
perform the following functions:
a) Create an NPA-NXX that is not yet open for porting (Effective date is in the future) on
behalf of the Service Provider under test NPA-NXX 2a _____________.
b) Create an NPA-NXX-X respective to NPA-NXX 2a on behalf of the Service Provider
under test (NPA-NXX-X 2a ___________________).
c) Modify NPA-NXX-X respective to 2a on behalf of the Service Provider under test,
note the modified attributes.
d) Modify existing NPA-NXX-X 1a above, note the modified attributes.
e) Create an NPA-NXX that is not yet open for porting (Effective date is in the future) on
behalf of another Service Provider under test NPA-NXX 2e __________________.
f) Delete the NPA-NXX (NPA-NXX 1c above) that is ‘owned’ by the Service Provider
under test and is currently open for porting and for which respective Subscription
Versions, Number Pool Blocks and NPA-NXX-X DO NOT exist, NPA-NXX 1c
____________________________.
g) Delete NPA-NXX-X 1a above.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Network Data,
specifying Latest View of Network
Data Activity and a valid time range
for the Service Provider under test.
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their SOA and
LSMS.
SP The SOA and LSMS successfully process the Bulk Data
Download file(s) and reflect the updates described in the
prerequisites above.
The systems are still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their SOA and LSMS, perform a
local query for the Network Data to
verify that the NPA-NXX and NPA-
NXX-X data was loaded.
SP Verify the following on the respective systems.
On the SOA verify:
If the Service Provider’s SOA Network Data Management
Indicator is set to TRUE,
o NPA-NXX 1a exists on the SOA (wasn’t in the BDD
file).
o NPA-NXX 1c does not exist on the SOA.
o NPA-NXX 2a exists on the SOA.
o NPA-NXX 2e exists on the SOA.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 131
If the Service Provider’s SOA NPA-NXX-X Indicator is
set to TRUE,
o NPA-NXX-X 1a does not exist on the SOA (see step 2g
above).
o NPA-NXX-X 2a with the modified attributes (see step
2c above) exists on the SOA
On the LSMS verify
If the Service Provider’s LSMS Network Data
Management Indicator is set to TRUE,
o NPA-NXX 1a exists on the LSMS (wasn’t in the BDD
file).
o NPA-NXX 1c DOES NOT exist on the LSMS.
o NPA-NXX 2a exists on the LSMS.
o NPA-NXX 2e exists on the LSMS.
If the Service Provider’s NPA-NXX-X Indicator is set to
TRUE,
o NPA-NXX-X 1a does not exist on the LSMS. (see step
2g above).
o NPA-NXX-X 2a with the modified attributes (see step
2c above) exists on the LSMS.
4. SP Service Provider personnel perform
appropriate steps to ‘associate’ with
the NPAC SMS.
SP The SOA and LSMS successfully re-associate with the NPAC
SMS.
5. SP Service Provider Personnel, using
their SOA and LSMS, perform an
NPAC query for the Network Data
in the prerequisites:
On the SOA and LSMS query:
If the Service Provider’s
SOA/LSMS Network Data
Management Indicator is set to
TRUE,
o NPA-NXX 1a .
o NPA-NXX 1c
o NPA-NXX 2a
o NPA-NXX 2e
If the Service Provider’s
SOA/LSMS NPA-NXX-X
Indicator is set to TRUE,
o NPA-NXX-X 1a
o NPA-NXX-X 2a
SP Verify the following on the respective systems.
On the SOA/LSMS verify:
If the Service Provider’s SOA/LSMS Network Data
Management Indicator is set to TRUE,
o NPA-NXX 1a exists.
o NPA-NXX 1c does not exist.
o NPA-NXX 2a exists.
o NPA-NXX 2e exists.
If the Service Provider’s SOA NPA-NXX-X Indicator is
set to TRUE,
o NPA-NXX-X 1a does not exist.
o NPA-NXX-X 2a exists with the new, modified
attributes (see step 2c above).
E. Pass/Fail Analysis, NANC 354-1 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 132
A. TEST IDENTITY
Test Case
Number:
NANC 354-2 SUT Priority: SOA Required
LSMS Required
Objective:
NPAC OP GUI – NPAC Personnel initiate a Bulk Data Download of Network Data –
Specifying the All Network Data. Verification steps are preformed to ensure the BDD file was
processed successfully by the Service Provider system. - Success
Note: Bulk Data Download scenarios for the XML interface will include Last Activity
Timestamp, if supported by the Service Provider.
B. REFERENCES
NANC Change
Order Revision
Number:
Change Order
Number(s):
NANC 354
NANC FRS
Version Number:
3.2.0 Relevant
Requirement(s):
RR3-303, RR3-307, RR3-308, RR3-309,
RR3-310, RR3-311
NANC IIS
Version Number:
3.2.0 Relevant
Flow(s):
N/A
C. PREREQUISITE
Prerequisite Test
Cases:
Prerequisite
NPAC Setup:
1. While the SOA and LSMS are ‘associated’ with the NPAC SMS, NPAC personnel
perform the following functions:
a) Create an LRN that does not yet exist on the NPAC SMS on behalf of the Service
Provider under test( LRN 1a_____________).
b) Create an NPA-NXX with an Effective date equal to today, on behalf of the Service
Provider under test (so that it is now open for porting) (NPA-NXX
1b_______________).
c) Immediately after initiating requests 1a) and 1b) above, dis-associate the Service
Provider’s SOA and LSMS systems.
2. While the SOA and LSMS are ‘dis-associated’ with the NPAC SMS, NPAC personnel
perform the following functions:
a) Modify LRN 1a (above), note the modified attributes. Deleted.
b) Create an NPA-NXX-X respective to NPA-NXX 1b on behalf of the Service Provider
under test (NPA-NXX-X 1b ___________________).
c) Modify NPA-NXX-X respective to 1b on behalf of the Service Provider under test,
note the modified attributes.
d) Modify LRN 1a (above) again, note the modified attributes.Deleted.
e) Create an NPA-NXX that is not yet open for porting (Effective date is in the future) on
behalf of another Service Provider under test NPA-NXX 2e __________________.
f) Delete NPA-NXX 2e that was just created above.
g) Create a unique NPA-NXX that is not yet open for porting (Effective date is in the
future) on behalf of another Service Provider, NPA-NXX 2g __________________.
Prerequisite SP
Setup:
D. TEST STEPS and EXPECTED RESULTS
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 133
Row # NPAC
or SP Test Step
NPAC
or SP Expected Result
1. NPAC Using the NPAC OP GUI, NPAC
Personnel request a Bulk Data
Download for Network Data,
specifying All Network Data for the
Service Provider under test.
NPAC The NPAC SMS performs the request, generates the
appropriate Bulk Data Download File(s) and automatically
“FTP’s” the file(s) to the Service Provider’s directory on the
NPAC SMS.
2. SP Service Provider Personnel receive
the Bulk Data Download File(s) and
load the file(s) into their SOA and
LSMS.
SP The SOA and LSMS successfully process the Bulk Data
Download file(s) and reflect the updates described in the
prerequisites above.
The systems are still ‘dis-associated’ from the NPAC SMS.
3. SP Service Provider Personnel, using
their SOA and LSMS, perform a
local query for the Network Data to
verify that the NPA-NXX and NPA-
NXX-X data was loaded.
SP Verify the following on the respective systems.
On the SOA verify:
If the Service Provider’s SOA Network Data Management
Indicator is set to TRUE,
o LRN 1a exists on the SOA with the modified attributes
from perquisite step 2d above.
o NPA-NXX 1b exists on the SOA, this was not part of
the BDD.
o NPA-NXX 2e does not exist on the SOA.
o NPA-NXX 2g exists on the SOA.
If the Service Provider’s SOA NPA-NXX-X Indicator is
set to TRUE,
o NPA-NXX-X 1b exists on the SOA with the new,
modified attributes (see step 2c above).
On the LSMS verify
If the Service Provider’s LSMS Network Data
Management Indicator is set to TRUE,
o LRN 1a exists on the LSMS with the modified attributes
from prerequisite step 2d above.
o NPA-NXX 1b exists on the LSMS, this was not part of
the BDD .
o NPA-NXX 2e does not exist on the LSMS.
o NPA-NXX 2g exists on the LSMS.
If the Service Provider’s LSMS NPA-NXX-X Indicator is
set to TRUE,
o NPA-NXX-X 1b exists on the LSMS with the new,
modified attributes (see step 2c above).
4. SP Service Provider personnel perform
appropriate steps to ‘associated’
with the NPAC SMS.
SP The SOA and LSMS successfully re-associate with the NPAC
SMS.
5. SP Service Provider Personnel, using
their SOA and LSMS, perform an
NPAC query for the Network Data
in the prerequisites:
On the SOA and LSMS query:
If the Service Provider’s
SOA/LSMS Network Data
Management Indicator is set to
TRUE,
o LRN 1a .
o NPA-NXX 1b.
o NPA-NXX 2e.
o NPA-NXX 2g.
SP Verify the following on the respective systems.
On the SOA/LSMS verify:
If the Service Provider’s SOA/LSMS Network Data
Management Indicator is set to TRUE,
o LRN 1a exists with the modified attributes from
prerequisite step 2d above.
o NPA-NXX 1b exists.
o NPA-NXX 2e does not exist.
o NPA-NXX 2g exists.
If the Service Provider’s SOA/LSMS NPA-NXX-X
Indicator is set to TRUE,
o NPA-NXX-X 1b exists with the new, modified
attributes, see step 2c above.
NPAC SMS/Individual Service Provider Certification & Regression Test Plan
Release 3.4.68: 1999-20161, 2013 Neustar, Inc. November June 30, 20136
Page - 134
If the Service Provider’s
SOA/LSMS NPA-NXX-X
Indicator is set to TRUE,
o NPA-NXX-X 1b.
E. Pass/Fail Analysis, NANC 354-2 Pass Fail NPAC Personnel performed the test case as written.
Pass Fail Service Provider Personnel performed the test case as written.
Pass Fail Service Provider Personnel were able to successfully process the Bulk Data Download file updates with their
local databases in a timely fashion.
Note: The Bulk Data Download file may contain additional network data. Testers can verify appropriate behavior
for any additional data that may be in the file as is stated in the Test Steps above.