Inter-Service Provider LNP Operations Flow

Cancellation Flows for Provisioning Process

Figure 5

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

Midwest 3/12/97 Issue 0.12

A service order and/or subscription may be canceled through various means:

1. The end-user contacts the Old or New Service Provider and requests cancellation of their porting request.

1. Conflict Resolution process flow: Where as a result of the Conflict Resolution process (at tie-point C) the Old and New Service Providers agree to cancel the subscription and applicable service orders.

1. Provision Service process flow: Where the missing or inaccurate information is from the New Service Provider, and the New Service Provider fails to respond to NPAC's request for information within two nine (9) hour windows [tunable parameter]. In this instance, the subscription is canceled automatically by NPAC SMS with a proper cause code in the notification message and subscription log, and notification is provided to both Service Providers. The Cancellation process flow is not entered for this type of cancellation.

1. Conflict Resolution and Cancellation Conflict process flows: Where the conflict remains unresolved for 30 calendar days [tunable parameter] after the subscription has been placed in conflict status. In this instance, the subscription is canceled automatically by NPAC SMS with a proper cause code in the notification message and subscription log, and notification is provided to both Service Providers. The Cancellation process flow is not entered for this type of cancellation.

1. Cancellation Conflict process flow: Where the missing or inaccurate information is from the Old Service Provider, and the Old Service Provider fails to respond to NPAC's request for information within two nine (9) hour windows [tunable parameter]. In this instance, the subscription is canceled automatically by NPAC SMS with a proper cause code in the notification message and subscription log, and notification is provided to both Service Providers.

1. End-user

The Cancellation Process may begin with an End-user requesting cancellation of their pending port. If their porting has already been completed, then should they wish to revert back to their former Service Provider, it must be done via the Provisioning Process. The Cancellation process flow applies only to that period of time between subscription creation, and either activation or cancellation of the porting request.

2. Did End-user contacted New or Old Service Provider?

The End-user calls their New or Old Service Provider to cancel the porting request for the porting of their telephone number. Only the Old or New Service Provider can initiate this transaction, not another Service Provider.

The contacted Service Provider gathers information necessary for sending the LSR to the other Service Provider noting cancellation, and for sending the cancellation request to NPAC SMS.

If the End-user contacted the Old Service Provider, then proceed to step 3. If the End-user contacted the New Service Provider, proceed to step 8.

3. Old Service Provider obtains End-user authorization.

The Old Service Provider obtains actual authority from the End-user to act as the official agent on behalf of then End-user to cancel the porting request. The Old Service Provider will be responsible for demonstrating such authority as necessary.

4. Old Service Provider sends notification to New Service Provider

Via their inter-company interface, the Old Service Provider fills out and sends the LSR form to the New Service Provider, indicating that the porting request is to be canceled.

5. Old Service Provider cancels all orders & sends cancellation to NPAC, if appropriate

The Old Service Provider, either having been contacted directly by the End-user or else notified by the New Service Provider via their inter-company interface, sends a cancellation message to NPAC via the SOA interface. This cancellation message is accepted by NPAC SMS only if the Old Service Provider had previously uploaded during the subscription creation. If the Old Service Provider sends a cancellation message when they had not previously sent a create message, the NPAC responds with a reject message. Hence, if the Old Service Provider had not previously uploaded to NPAC SMS for this subscription, it does not upload a cancellation message.

The Old Service Provider cancels all internal company orders, to ensure that the end-user customer maintains continuity of service.

6. Did NPAC receive notification(s) within 9 hours?

The NPAC applies a nine (9) hour [tunable parameter] time limit on receiving cancellation messages from both Service Providers. This is referred to as the Initial Cancellation Window.

The NPAC SMS tests for receipt of cancellation messages from the two Service Providers based on which Service Providers had previously uploaded into NPAC SMS. Since the Old Service Provider's upload is optional for subscription creation, if the Old Service Provider had not uploaded during the creation process, the Old Service Provider's input during cancellation is not accepted by NPAC SMS. Similarly, if during the subscription creation process only the Old Service Provider had uploaded, and not the New Service Provider, then only the Old Service Provider's input is accepted when canceling an order.

For a "concurred" subscription, upon receipt of the first cancellation message, NPAC sets the subscription status to cancel-pending. Both the Old and New Service Providers are notified of this change in status via the SOA interface. If the second cancellation notification, from the other Service Provider, was received within nine (9) hours, then proceed to step 7; otherwise, proceed to step 10.

For a "non-concurred" subscription, upon receipt of a correct cancellation message, NPAC sets the subscription status directly to cancel, and proceeds to step 7. Both the Old and New Service Providers are notified of this change in status via the SOA interface.

7. NPAC logs information and cancels subscription

The porting request is canceled by changing the subscription status to canceled. Both Service Providers are notified of the cancellation via the SOA interface.

END

The cancellation process has ended. If the customer is to be ported after this point is reached, the porting process must be started again from the beginning of the Provision Service process flow.

8. New Service Provider sends LSR to Old Service Provider noting cancellation as soon as possible prior to activation time

The End-user contacts their New Service Provider and asks that their porting request be canceled. Via their inter-company interface, the New Service Provider fills out and sends the LSR form to the Old Service Provider, indicating that the porting request is to be canceled.

9. New Service Provider sends notification of cancellation to NPAC if appropriate

The New Service Provider, either having been contacted directly by the End-User or else notified by the Old Service Provider via their inter-company interface, sends a cancellation message to NPAC via the SOA interface. This cancellation message is accepted by NPAC SMS only if the New Service Provider had previously uploaded during the subscription creation. If the New Service Provider sends a cancellation message when they had not previously sent a create message, the NPAC responds with a reject message. Hence, if the New Service Provider had not previously uploaded to NPAC SMS for this subscription, it does not upload a cancellation message.

The New Service Provider cancels all internal company orders, to ensure that the end-user customer maintains continuity of service.

10. NPAC notifies appropriate Service Provider that information is missing

The Initial Cancellation Window starts with receipt at NPAC of the first cancellation message. When this timer times out, the NPAC requests the missing information from the Service Provider who has not yet provided the cancellation message via the SOA interface. Only "concurred" subscriptions will reach this point in the process flow.

11. Does NPAC receive concurring notification within 9 hours?

The NPAC applies a nine (9) hour [tunable parameter] time limit on receiving cancellation messages from both Service Providers. This is referred to as the Final Cancellation Window.

Upon receipt of the missing notification, proceed to step 7. If no notification is received by the time this timer times out, then proceed to tie-point H, "Cancellation Conflict Process Flow."