NANC 297

Sending SV Problem During Recovery

Origination Date :09/15/1999

Originator:Sprint

Description:

If an LSMS is down during the broadcast, and the NPAC SMS has sent out the final retry, the LSMS will not be able to recover this broadcast (either in recovery or once recovery is complete and normal processing continues).

It was discussed that the way to ensure the recovering LSMS gets the sending SVs, is to include any of these SVs.  By including these, along with the appropriate download reason; the LSMS would be able to recover sending SVs.

New Requirements:

NPAC SMS shall include Subscription Versions with a status of sending, at the time subscription data recovery is requested by the LSMS.

NPAC SMS shall remove a Service Provider from the Failed SP List of a Subscription Version with a status of sending, even if there are additional retry attempts, at the time subscription data recovery is requested by the LSMS of that Service Provider.

Pure Backwards Compatible:  YES

Sep LNPAWG (Chicago), need to add priority during Oct meeting in KC.

Oct LNPAWG (KC), could have a problem if the SV is sent twice (once for the recovery, and once at the next retry attempt), so the group wants the failed list updated for the recovering SP.

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 in FRS 3.2.0, IIS 3.2.0 and GDMO 3.2.0.

Related Release:

Implemented in FRS 3.2.0, IIS 3.2.0 and GDMO 3.2.0. 

Status: Implemented