Print this page Print NPIF » NANC Change Orders » NANC 303

NANC 303

R3 IIS documentation-only updates

Origination Date :01/24/2000

Originator:CMA

Description:

1.

(NEW FLOW) – Subscription Version Inter-Service Provider Port of a TN with no currently active Subscription Version – Creation Prior to NPA-NXX-X Effective Date

In this scenario, the service provider SOA attempts to create an inter-service provider port with no currently active subscription version request prior to the effective date of the corresponding serviceProvNPA-NXX-X object. The NPAC SMS will reject this request, as an inter-service provider port with no currently active subscription version request cannot be created prior to the effective date of the corresponding serviceProvNPA-NXX-X.

SOA personnel take action to create an inter-service provider port with no currently active subscription version request.

 

  1. The new service provider SOA sends a valid, M-ACTION, subscriptionVersionNewSP-Create request for a TN within an NPA-NXX-X that is not yet effective.

 

NPAC SMS replies with an error, ‘soa-not-authorized’.

2.

Update flow B.5.6, Subscription Version Query by adding “subscriptionStatusChangeCauseCode (SOA)” to the list of data returned from an SV query.

3.

Update flow B.4.2.10, Scoped/Filtered GET of Network Data.

This scenario shows a request for network data via a scoped/filtered M-GET. In this case, scoping is done from the lnpNetwork object. However, s Scoping and filtering can be done from serviceProvNetwork, serviceProvLRN, and serviceProvNPA-NXX objects .

(picture update from “lnpNetwork” to “serviceProvNetwork”.)

 

  1. Action is taken by the Local SMS personnel to request network data via a scoped/filtered M-GET request.
  2. The Local SMS sends a scoped/filtered M-GET request to the NPAC SMS.
  3. The NPAC SMS sends network data objects (serviceProvNetwork, serviceProvNPA-NXX, serviceProvLRN) that pass the scope/filter criteria to the Local SMS that initiated the request.
  4. A final M-GET response is sent to the Local SMS that initiated the request once all scoped/filtered network objects have been returned, and will contain no data.

4.

Update table 4.1.1, Primary NPAC Mechanized Interface Operations.  Exhibit 1. Primary NPAC Mechanized Interface Operations Table

Column 1:  Subscription Version Modify.

Column 2:  from SOA.

Column 3:  M-ACTION:  subscriptionVersion Modify

      or

      M-SET:
       on relevant subscriptionVersionNPAC attributes for pending, active, and conflict versions.

Column 4:  lnpSubscriptions

5.

Update flow B.5.5.1, SubscriptionVersion Conflict and Conflict Resolution by the NPAC SMS, to reflect accurate notification names.

 

 

  1. NPAC personnel or NPAC SMS take action to set the status of a subscription to “conflict.”
  2. NPAC SMS issues M-SET request to update subscriptionVersionStatus to “conflict,” subscriptionConflictTimeStamp, and subscriptionModifiedTimeStamp in the subscriptionVersionNPAC object.
  3. NPAC SMS issues an M-SET response. If the M-SET fails, processing for this scenario stops.
  4. NPAC SMS issues an M-EVENT-REPORT subscriptionVersionStatusAttributeValueChange to old service provider SOA.
  5. The old service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  6. NPAC SMS issues subscriptionVersionStatusAttributeValueChange for status to new service provider SOA.
  7. The new service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  8. NPAC SMS sends a subscriptionVersionStatusAttributeValueChange to set the old service provider’s authorization to “FALSE”.
  9. The old service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  10. NPAC SMS sends an subscriptionVersion AttributeValueChange to set the new service provider authorization to “FALSE”.
  11. The new service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  12. Once the conflict is resolved, NPAC personnel take action to remove the subscriptionVersion from conflict.
  13. NPAC SMS issues an M-SET request to update the subscriptionModifiedTimeStamp and the subscriptionVersionStatus to “pending.”
  14. NPAC SMS issues an M-SET response. If the M-SET fails, processing for this scenario stops.
  15. NPAC SMS issues subscriptionVersionStatusAttributeValueChange for the new status to the old service provider SOA.
  16. The old service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  17. NPAC SMS issues subscriptionVersionStatusAttributeValueChange for the new status to the new service provider SOA.T
  18. The new service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  19. NPAC SMS sends a subscriptionVersionStatus AttributeValueChange to the old service provider’s indicating the authorization has been set to “TRUE”.
  20. The old service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.
  21. NPAC SMS sends an subscriptionVersion AttributeValueChange to the new service provider indicating the authorization has been set to “TRUE”.
  22. The new service provider SOA returns an M-EVENT-REPORT confirmation to the NPAC SMS.

6.

Update flow B.5.1.6.4, Subscription Version Create: Failure to Receive Response from New SOA, to reflect accurate notification name.  Also update picture to send a “subscriptionVersionStatusAttributeValueChange” to both old and new SP (instead of the current incorrect reference to “subscriptionVersionAttributeValueChange” notification).

This scenario shows action taken by the NPAC SMS after not receiving any concurrence from the new service provider after the “Final Service Provider Concurrence Failure Window.”

 

  1. NPAC SMS receives no concurrence occurrence from the new service provider SOA in “Service Provider Concurrence Failure Window”  for the pending subscriptionVersionNPAC created by the old service provider SOA.

 

7.

Remove incorrect description in 4.2.3, Action Scoping and Filtering Support.

For messages sent to any object, the scope and filter will be checked to ensure it is appropriate for that object class.

 

  • All M-ACTIONs that relate to subscriptions and number pool blocks are targeted to lnpSubscriptions.
  • The ONLY filters allowed by the GDMO for lnpSubscriptions are "equality" and "present" for the single attribute lnpSubscriptionsName.
  • If any one of the above M-ACTIONs is sent to a subscriptionVerisonNPAC or numberPoolBlockNPAC object you will get a "no such action" error response from that object.
  • If you send a scoped/filtered M-ACTION whose scope includes objects of class subscriptionVersionNPAC or numberPoolBlockNPAC, you will receive an error "no such action" from each object specified by the filter. This could mean 1 for EVERY subscriptionVersion or numberPoolBlock in the NPAC.

8.

Update audit behavior for erroneous block on EDR LSMS.

SOA Audit Create for Subscription Versions within a Number Pool Block  (previously NNP flow  6.1)

In this scenario, the SOA initiates the audit of one or more subscription versions that are within the range of a number pool block.  For non-EDR Local SMSs, this involves the subscription version objects. For EDR Local SMSs, this involves both subscription version objects and number pool block objects.

If discrepancies are found, the NPAC SMS will create, modify or delete subscription version and number pool objects, as necessary. The NPAC SMS will report to the SOA the discrepancies with subscription version identifiers. Thus, if a numberPoolBlock object is in error, the discrepancy will be reported as all TNs within the audit range that were also within the block range. However, in the case where an EDR Local SMS erroneously contains a Number Pool Block, the NPAC SMS will send a Number Pool Block delete to the Local SMS, but will not report any discrepancy back to the requesting SOA for this Local SMS. Subscription version discrepancies will be reported as usual.

9.

Update SV status reference in B.4.1.5, NPA-NXX Deletion by the Local SMS, in step 4:

Check the subscriptions database to see if subscriptions exist with this NPA-NXX that have a status other than “old” without a Failed SP List or “canceled.”  Also, check if any NPA-NXX-Xs or Number Pool Blocks exist with this NPA-NXX.  If so, terminate processing at this point.

Update SV status reference in B.4.2.3, LRN Deletion by the SOA, in step 4:

Check the subscriptions database to see if subscriptions exist with this LRN that have a status other than “old” without a Failed SP List or “canceled.”  Also, check if any Number Pool Blocks exist with this LRN NPA-NXX .  If so, an M-SET error response complexity limitation is returned.

10.

Remove B.4.2.9, Network Data Download, as this is superceded by the text and flows in section B.7, Local SMS and SOA Recovery.

11.

Update flow B.2.7.2, NPAC SMS Performs Audit Comparisons for a SOA initiated Audit including a Number Pool Block, step #3, to include status of Old (to cover PTO scenarios).

12.

Update all audit flows (B.2.1, 2.3, 2.4, 2.5, 2.7.3, 2.8.2) to remove immediate delete steps and text (since this is based on the length of time in the tunables).  Add new text to indicate this delete is performed by housekeeping.

13.

Update flows B.5.2.3 SubscriptionVersion Modify Prior to Activate Using M-ACTION, and B.5.2.4 SubscriptionVersion Modify Prior to Activate Using M-SET, to add the following text for the AVC’s sent to the New and Old SPs.

"Attribute value change notifications will be sent to both service provider SOAs when the following attribute values change for a pending, cancel-pending, conflict or disconnect-pending subscription versions:

   subscriptionNewSP-DueDate

   subscriptionNewSP-CreationTimeStamp

   subscriptionOldSP-DueDate

   subscriptionOldSP-Authorization

   subscriptionOldSP-AuthorizationTimeStamp

   subscriptionStatusChangeCauseCode

   subscriptionVersionStatus "

14.

 Update flow B.6.5.1.12, SubscriptionVersion Port-to-Original: Successful, to correct the discrepancy between the picture and the text (picture is wrong, text is correct).  The SAVC from the NPAC SMS goes to the current owner (i.e., new SP) of SV1.

Final Resolution:

Pure Backwards Compatible:  YES

Related Release:

3.0.1

Status: Implemented