NANC 251

Documentation Change to the GDMO Behavior

Origination Date :12/17/1998

Originator:National Number Pooling Sub-Com'ttee

Description:

The following discrepancies should be updated in the GDMO documentation.

under the subscriptionVersion object (20.0 LNP subscription Version Managed Object Class):

*Correct the definition in behavior to read:

subscriptionVersionBehavior BEHAVIOUR

  DEFINED AS !

  Local SMS Managed Object used for the NPAC SMS

  to Local SMS interface.

Under the subscriptionVersionNPAC object (21.0 LNP NPAC Subscription Version Managed Object Class):

*Correct the disconnect complete time stamp description to read:

  When the subscription version is being

  disconnected and the first

  successful response is received from the Local SMS

  to the subscription

  version disconnect request, the

  subscriptionDisconnectCompleteTimeStamp

  is updated with the current date and system time.

*Correct the failed SP List description to read:

  When a subscription version broadcast is not

  successful to all

  service providers, the subscriptionFailed-SP-List is

  populated with a list of the failed service providers.

Under Attribute 48 – subscriptionActivationTimeStamp

*Correct behavior to read:

  This attribute is set by the NPAC SMS as the current time

Under Action 1 – lnpDownload

* Correct this behaviour sentence to read:

   Time range requests

   will be limited to a tunable range specified in the NPAC SMS

   and must be specified in Coordinated Universal Time (UTC).

Under Action 2 – lnpRecoveryComplete

* Add to behaviour:

   The NPAC SMS will queue up all new events while the Local SMS is

   in recovery mode and send them to the Local SMS after responding

   with the lnpRecoveryComplete action reply.

 Under Notification 11 - subscriptionVersionAttributeValueChange

* Correct behaviour sentence to read:

   Failed lists will also be potentially sent for subscription versions

   with statuses of active, failed, partial-failure, disconnect-pending

   and old.

Under Action 7 – subscriptionVersionModifyAction, the subscriptionWSMSC-DPC and SSN should be moved from the current list of attributes and instead put in a paragraph that states:

    The new service provider may specify modified valid values for the

  following attributes, when the service provider’s “SOA WSMSC DPC

  SSN Data” indicator is TRUE, and may NOT specify these values when

  the Indicator is FALSE:

  subscriptionWSMSC-DPC

  subscriptionWSMSC-SSN

Under Action 11 – subscriptionVersionNewSP-Create subscriptionVersionCreateAction , the subscriptionWSMSC-DPC and SSN should be moved from the list of required attributes and instead put in a paragraph that states:

  The new service provider must specify valid values for the following

  attributes, when the service provider’s “SOA WSMSC DPC SSN Data”

  indicator is TRUE, and must NOT specify these value when the indicator

  is FALSE:

If the SOA WSMSC DPC SSN Data Indicator is set in the service provider's profile, the following attributes should be provided:

   subscriptionWSMSC-DPC

   subscriptionWSMSC-SSN

Final Resolution:

Backwards Compatible:  YES

Jan LNPAWG (Atlanta), group requested that the actual changes be identified in the text (i.e., bold).

Feb LNPAWG (San Ramon), updated several points for the change order (disconnect time stamp, subscriptionActivationTimeStamp, subscriptionVersionModifyAction, subscriptionVersionNewSP-Create).  These are identified by yellow hightlighting.

Related Release:

3.0.0

Status: Implemented