Open APIs

Expand all | Collapse all

TMF641 notification types - managing updates to service characteristics as a result of fulfilment

  • 1.  TMF641 notification types - managing updates to service characteristics as a result of fulfilment

    Posted 18 days ago

    Hi All,

    I would like to get some feedback / suggestions on an issue we are facing as a result of SOM fulfilling a TMF641 service order:

    1 - POM is submitting a service order to SOM to fulfill the activation of a service.

    2 - During the fulfillment process, the SOM enriches characteristics on the service.
    (in this case some demarcation details of the service being fulfilled).

    3 - The POM that submitted the TMF641 service order needs to be notified of this information so as it can complete it's fulfilment process.
    (the demarcation details need to be communicated to customer and assurance platforms)

    What would be the appropriate TMF641 notification event type for SOM to broadcast this information to POM?
    Given POM needs to be made aware of the information enrichment on the service within the context of the service order being fulfilled?

    Looking at TMF641 specification, the serviceOrder notification event types are:

      "ServiceOrderAttributeValueChangeNotification",
      "ServiceOrderCreateNotification",
      "ServiceOrderDeleteNotification",
      "ServiceOrderInformationRequiredNotification",
      "ServiceOrderStateChangeNotification",

    None of these notifications seems to fit the requirement.

    I almost think we would require a 

    ServiceOrder_Item_AttributeValueChangeNotification

    However I can understand that as a result of service fulfilment, we are not modifying serviceOrderItemAttributes, but rather the serviceAttributes of the services being fulfilled.


    I am aware of the event:

    ServiceAttributeValueChangeNotification

    However this event is a TMF640 notification (I think?).
    Which is outside of the context of the service order being fulfilled to activate the service.

    Am I correct in thinking POM should expect all changes as a result of SOM fulfilling a service order to be received in the context of TMF641 notifications?


    Many Thanks
    Elliot.



    ------------------------------
    Elliot Rien
    VOCUS PTY LTD
    ------------------------------


  • 2.  RE: TMF641 notification types - managing updates to service characteristics as a result of fulfilment

    TM Forum Member
    Posted 17 days ago
    Hi Elliot,
    In my opinion, you can have a customization such that SOM can invoke TMF640 API when POM submits Order via TMF640 API. In this case, POM can subscribe to event -ServiceAttributeValueChangeNotification.

    Also, have you explored TMF688 Event Management API? I think you can create an Event entity to define EventType (e.g.XYZAttributeChange). Of course, POM needs to be aware of this EventType and subscribe to EventCreateEvent

    There can be other simpler ways too but I will leave it to other experts to comment. :)

    Thanks and Regards,

    ------------------------------
    Sanket Kulkarni
    Infosys
    ------------------------------



  • 3.  RE: TMF641 notification types - managing updates to service characteristics as a result of fulfilment

    TM Forum Member
    Posted 17 days ago
    Hello Elliot, Sanket

    For my perspective, the notification
    ServiceOrderAttributeValueChangeNotification
    could be used as well for an attribute change at serviceOrderItem level. Items are part of the order.

    The challenge is to define the right event payload to identify the change (only a subset of the SO).
    You can use 640  notification but you need a one point to correlated the service order item with the service id.

    As mentioned by Sanket, TMF688 event API with topic could be an useful alternative.

    hope it helps

    Ludovic



    ------------------------------
    Ludovic Robert
    Orange
    My answer are my own & don't represent necessarily my company or the TMF
    ------------------------------