NANC 249

Modification of Dates for a Disconnect Pending SV

Origination Date :12/09/1998

Originator:Sprint

Description:

The NPAC should be changed to allow a Service Provider to modify the CDD (Customer Disconnect Date) and ERD (Effective Release Date) for an SV that has a status of “disconnect pending”.

Func Backwards Compatible:  NO

The current Service Provider would send a subscriptionVersionModify using an M-ACTION.

subscriptionCustomerDisconnectDate and subscriptionEffectiveReleaseDate would need to be added as modifiable attributes.

A new IIS flow needs to be developed (Subscription Version Modify Disconnect Pending Version Using M-ACTION by a Service Provider SOA).

If the newly modified ERD is the current date or a previous date, the NPAC will follow the “immediate disconnect” flow (6.5.4.1).  Otherwise, it’s BAU for the future dated ERD (6.5.4.2).

R5-25 needs to be changed to allow for a modification of an SV with a status of disconnect pending.

R5-36 and R5-38.1 needs the CDD and ERD attributes added to the list.

R5-41 and RR5-41.x need to perform exception processing (i.e., NOT send to LSMSs at this time) of modifications where the new ERD is a future date.

New requirements:

1. NPAC SMS shall reject a modification request of an SV with a status of disconnect pending, where the CDD value is zero.

Jan LNPAWG (Atlanta), group O.K. with this change order.  Move to accepted list.

01/02/02 – NPAC R4.0 as submitted to the LLC in 2000 is not going forward.  This change order has been moved back into the “accepted” section of this document.

Final Resolution:

Implemented

Related Release:

Implemented in FRS 3.2.0, IIS 3.2.0, GDMO 3.2.0 and ASN.1 3.2.0.

Status: Implemented