NANC 375

Limiting Ability to Remove Conflict Status with Certain Cause Code Values

Origination Date :11/27/2002

Originator:Verizon

Description:

Business Need:

Customers have been taken out of service inadvertently due to the New Service Provider continuing with a port that had been placed into Conflict by the Old Service Provider after the 6 hour timer had expired, instead of investigating why the port was placed into Conflict.

When the Old Service Provider receives a SOA notification from NPAC that another service provider has issued a CREATE message to NPAC in order to schedule a port-in of the Old Service Provider’s customer, the Old Service Provider should check to see that a matching Local Service Request (LSR) has been received from that service provider regarding that specific TN.  If no matching LSR is found, the Old Service Provider may place the port into Conflict status with a Cause Value set to “LSR Not Received” (Cause Value 50).  In some instances, the New Service Provider is waiting for the 6 hour Conflict Resolution New Service Provider Restriction Tunable Parameter timer to expire, and is proceeding with porting the number.  This has led to a number of customers being inadvertently ported and taken out of service from a terminating call perspective because the wrong TN was entered in the original CREATE message sent by the New Service Provider to NPAC.

This proposed Change Order, as did PIM 22 accepted by the LNPA, seeks to prevent instances where customers are taken out of service inadvertently after the New Service Provider continues with a port that had been placed into Conflict by the Old Service Provider.  In these cases, the port was placed into Conflict Status by the Old Service Provider because of indications that the New Service Provider may possibly be porting the wrong TNs.

This proposed Change Order, as did PIM 22 accepted by the LNPA, seeks to prevent instances where customers are taken out of service inadvertently after the New Service Provider continues with a port that had been placed into Conflict by the Old Service Provider.  In these cases, the port was placed into Conflict Status by the Old Service Provider because of indications that the New Service Provider may possibly be porting the wrong TNs.

Final Resolution:

Func Backwards Compatible:  NO 

Description of Change:

The current Cause Values indicating why the Old Service Provider has placed a port into Conflict are as follows:

50 – LSR/WPR Not Received

51 – Initial Confirming FOC/WPRR Not Issued

52 - Due Date Mismatch

53 - Vacant Number Port

54 – General Conflict

This Change Order proposes that the LNPA revisit the philosophy that led to enabling the New Service Provider to remove a Subscription Version from Conflict status after a specified period of time without first resolving the original conflict with the Old Service Provider.  NPAC requirements and functionality should be modified such that only the Old Service Provider is able to remove Conflict status and move a Subscription Version to Pending status when the Conflict Cause Value is set to 50, which signifies that the Old Service Provider has not received a matching Local Service Request (LSR) or Wireless Porting Request (WPR) for the telephone number received in the New Service Provider CREATE notification from NPAC, or when the Conflict Cause Value is set to 51 (Firm Order Confirmation Not Issued).

Subscription Versions should only be placed into Conflict with a Cause Value set to 50 when the Old Service Provider cannot match an LSR or WPR with the New Service Provider CREATE notification and is reasonably confident that the wrong number is about to be ported.  Also, Subscription Versions should only be placed into Conflict with a Cause Value set to 51 when the Old Service Provider has a legitimate reason for withholding the Firm Order Confirmation.  A Cause Value of 50 or 51 should not be used in lieu of any other appropriate Conflict Cause Value in order to inappropriately prevent the New Service Provider’s ability to remove Conflict status.

Implemented in FRS 3.3.0a, IIS 3.3.0a and GDMO 3.3.0. 

Subscription Versions should only be placed into Conflict with a Cause Value set to 50 when the Old Service Provider cannot match an LSR or WPR with the New Service Provider CREATE notification and is reasonably confident that the wrong number is about to be ported.  Also, Subscription Versions should only be placed into Conflict with a Cause Value set to 51 when the Old Service Provider has a legitimate reason for withholding the Firm Order Confirmation.  A Cause Value of 50 or 51 should not be used in lieu of any other appropriate Conflict Cause Value in order to inappropriately prevent the New Service Provider’s ability to remove Conflict status.

Implemented in FRS 3.3.0a, IIS 3.3.0a and GDMO 3.3.0.

Related Release:

Implemented in FRS 3.3.0a, IIS 3.3.0a and GDMO 3.3.0.

Status: Implemented