Print this page Print NPIF » NANC Change Orders » NANC 333

NANC 333

Doc Only Change Order for GDMO & IIS

Origination Date :09/26/2001

Originator:TSE

Description:

Doc Only Change Order for GDMO & IIS:  Clarification needed in the GDMO & two IIS Flows for the subscriptionVersionRangeObjectCreation notification (one of the new range notifications in change order NANC 179 for NPAC SMS Release 3.1).

In the ObjectInfo for subscriptionVersionRangeObjectCreationInfo there are attribute assertions for subscriptionVersionId and subscriptionTN as is done for the single objectCreation notification for a subscription version.  These values would be the SVID and TN for the first TN in the list or range for the subscriptionVersionRangeObjectCreation notification.

GDMO changes needed for clarification of the subscriptionVersionRangeObjectCreation notification:

lnpSubscriptionsBehavior BEHAVIOUR

  DEFINED AS !

   Local SMS and NPAC SMS Managed Object

   The Local SMS (Data Download Association Function) and the service

   provider SOA (SOA Management Association Function) can M-GET any

   lnpSubscriptions object.  The lnpSubscriptionsName attribute

   is read only and can not be changed via the Local SMS Interface

   once the object has been created.  The value of

   lnpSubscriptionsName will always be "lnpSubscriptions".

•   

•   

•   

   The SOA receives subscriptionVersionRangeObjectCreation notifications

   if their Service Provider TN Range Notification Indicator is set to

   TRUE on the NPAC SMS. The subscriptionVersionRangeObjectCreationPkg is

   used to send the subscriptionVersionRangeObjectCreation notification.

   When this package is sent, it will include one set of information for

   the TN range, plus a paired list of TN/Subscription Version ID

   combinations. If the feature data does not apply to all TNs in the

   range, notifications will be broken up into smaller TN Range

   Notifications such that the feature data applies to all TNs in the

   smaller TN Range, and will be sent in separate messages.

   The ObjectInfo field will contain the same data as the current object

   creation notifications sent to the old and new service provider.  The

   TN and SVID fields that are sent in the single object creation

   notification will contain the TN and subscription version id for the

   first TN in the range or list.

-- 16.0 LNP Subscription Version Range Object Creation Notification

subscriptionVersionRangeObjectCreation NOTIFICATION

  BEHAVIOUR  subscriptionVersionRangeObjectCreationBehavior;

  WITH INFORMATION SYNTAX  LNP-ASN1.VersionRangeObjectCreation

  AND ATTRIBUTE IDS

   range-object-creation-info subscriptionVersionRangeObjectCreationInfo,

   access-control accessControl;

  REGISTERED AS {LNP-OIDS.lnp-notification 16};

subscriptionVersionRangeObjectCreationBehavior BEHAVIOUR

  DEFINED  AS !

   This notification type is used to report creation of subscription

   versions for range operations.  It uses the object creation

   notification as defined in M.3100.

   The service provider supports this notification if the Service

   Provider TN Range Notification Indicator is set on the NPAC SMS and

   the service provider will no longer receive an

   object creation notification for a subscription version.

   This ObjectInfo field will contain the same data as the current

   object creation notifications sent to the old and new service

   provider. The TN and SVID fields that are sent in the single

   object creation notification will contain the TN and

   subscription version id for the first TN in the range or list.

   This notification is prioritized and transmitted

   according to its SOA Notification Priority tunable in the NPAC

   SMS.

IIS changes need for clarification subscriptionVersionRangeObjectCreation notification:

For flow B.5.1.1, step 5 should be changed as follows:

5.    If the M-ACTION was successful, the NPAC SMS issues, depending upon the old service provider’s TN Range Notification Indicator, an objectCreation or subscriptionVersionRangeObjectCreation M-EVENT-REPORT containing the following attributes to old service provider SOA of subscriptionVersionNPAC creation:

     subscriptionVersionId

     subscriptionTN

     subscriptionOldSP

     subscriptionNewCurrentSP

     subscriptionOldSp-DueDate

     subscriptionOldSP-Authorization

     subscriptionOldSP-AuthorizationTimeStamp

     subscriptionStatusChangeCauseCode

     (if subscriptionOldSP-Authorization set to false)

subscriptionVersionStatus

If the notification is a subscriptionVersionRangeObjectCreation then the TN and SVID are the TN and SVID of the first TN in the range or list.

For flow B.5.1.2, step 5 should be changed as follows:

5.    If the M-ACTION was successful, NPAC SMS issues, depending upon the old service provider’s TN Range Notification Indicator, an objectCreation or subscriptionVersionRangeObjectCreation M-EVENT-REPORT containing the following attributes to old service provider SOA of subscriptionVersionNPAC creation:

     subscriptionVersionId

     subscriptionTN

     subscriptionOldSP

     subscriptionNewCurrentSP

     subscriptionNewSP-CreationTimeStamp

     subscriptionVersionStatus

 subscriptionNewSP-DueDate

If the notification is a subscriptionVersionRangeObjectCreation then the TN and SVID are the TN and SVID of the first TN in the range or list.

Final Resolution:

Incorporate into the GDMO and IIS immediately and re-publish these documents as Release 3.1.1

October 2001 meeting:  Accepted by LNPA WG. To be included in next release of GDMO & IIS. Move to “Next Documentation Release Change Orders” sub-section of the “Accepted Change Orders” section of this document.    

 Implemented in IIS 3.2.0 and GDMO 3.2.0.

Related Release:

Implemented in IIS 3.2.0 and GDMO 3.2.0.

Status: Implemented