Inter-Service Provider LNP Operations Flow

Cancellation Conflict Flows for Provisioning Process

Figure 6

Final Narrative 3/12/97; supports NANC 1/31/97 Process Flows (Issue 0.11) and

Midwest 3/12/97 Issue 0.12

1. Is Old or New cancellation notification missing or inaccurate?

At this point in the process flow, the subscription status is cancel pending, because either the Old or New Service Provider's cancellation notification is missing or inaccurate. If the Old Service Provider's notification is at fault, then proceed to step 2. If the New Service Provider's notification is at fault, then proceed to step 4.

Note that the Cancellation Conflict process flow will be reached only for "concurred" subscriptions.

2. NPAC logs information, cancels transaction, and notifies both Service Providers of cancellation with proper cause code

If the Old Service Provider has not provided a cancellation notification message to NPAC, in spite of a Cancellation LSR sent from the New Service Provider and two reminder messages from NPAC, then the subscription is immediately canceled. NPAC notifies both Service Providers that the subscription status has been updated to canceled, and will place the proper cause code on the subscription's record.

To maintain continuity of service to the End-user, both Service Providers must cancel all related internal work orders, if they have not already done so.

3. END

The subscription status is canceled. If the End-user still desires to port their telephone number, the process must be re-started at the beginning of the Provisioning process flow.

4. NPAC logs information, places subscription in "conflict status" with proper conflict cause code, and notifies both Service Providers

If the New Service Provider has not provided a cancellation notification message to NPAC, in spite of a Cancellation LSR sent from the Old Service Provider and a reminder message from NPAC, then the subscription is placed in a conflict state by NPAC. NPAC also writes the proper conflict cause code to the subscription's record, and notifies both Service Providers, with proper conflict cause code, of the change in status via the SOA interface.

To maintain continuity of service to the End-user, both Service Providers must suspend all related internal work orders, if they have not already done so.

5. How does New Service Provider wish to continue?

With the subscription in conflict, it is only the New Service Provider who controls what happens to the transaction. The New Service Provider will make a concerted effort to contact the Old Service Provider prior to proceeding.

If the New Service Provider decides to cancel the subscription, then proceed to step 6. If they decide to proceed with the porting process, then go to step 10. If they do nothing, then 30 calendar days after being placed in the conflict state, NPAC automatically cancels the subscription in step 9.

6. New Service Provider notifies NPAC to cancel subscription

The New Service Provider may decide to cancel the subscription. If so, they notify NPAC of this decision.

7. NPAC logs information, cancels subscription, removes it from Conflict, and notifies both Service Providers of cancellation

Having been notified by the New Service Provider to cancel the subscription, NPAC logs this information, and changes the subscription status to canceled. Both Service Providers are notified of the change in the subscription status.

To maintain continuity of service to the End-user, both Service Providers must cancel all related internal work orders, if they have not already done so.

8. END

The subscription status is canceled. If the End-user still desires to port their telephone number, the process must be re-started at the beginning of the Provisioning process flow.

9. NPAC waits for 30 calendar days, cancels subscription, removes it from Conflict, and notifies both Service Providers of time-out.

After no response from the New Service Provider for 30 calendar days regarding this particular subscription, NPAC changes its status to canceled and notifies both Service Providers of the change in status via the SOA interface.

To maintain continuity of service to the End-user, both Service Providers must be careful to cancel or suspend all related internal work orders when subscriptions are in the conflict state.

10. New Service Provider notifies NPAC to remove subscription from Conflict status

The New Service Provider may chose to proceed with the porting process, in spite of a cancellation message received from the Old Service Provider. As both Service Providers are presumably basing their actions on the End-user's request, and each is apparently getting a different request from that End-user, they should ensure have an accurate request.

If the New Service Provider decides to proceed with the porting, they update the status of the subscription to pending.

It is the responsibility of the New Service Provider to contact the Old Service Provider, to request that related work orders which support the porting process are performed. The Old Service Provider must support the porting process.

11. NPAC notifies both Service Providers of conflict off via SOA

NPAC notifies both Service Providers of the change in subscription status. The porting process resumes as normal, at tie-point BB.