Open APIs

 View Only
  • 1.  Cease Multiple Services in a single request

    TM Forum Member
    Posted Jan 20, 2022 06:40

    I have a scenario to cease list of services of one location. The consumer application would provide the list of service details in a single request. TMF 638 POST service object will support only one service with action delete(

    OrderItemActionType

    in the request. But serviceRelationship list of objects can be used which can have multiple service objects. There may be scenario where one service cannot be related to another. Could you please give your suggestions?



    ------------------------------
    Francis Borgio Muthuswamy
    Capgemini
    ------------------------------


  • 2.  RE: Cease Multiple Services in a single request

    TM Forum Member
    Posted Jan 21, 2022 05:41
    Hello Francis,

    I'm not sure TMF638 is the right API to cease service. Indeed TMF638 provide a view on the inventory of the service. This inventory is a representation in a database of the service...not the service themselves. In this inventory, for a given service you can find the list of serviceOrder that have managed this service and the itemAction is the action done on this service. This is for 'history' and not for action.

    Triggering a service cease could be done by TMF641 but in this case you have to manage a service order to embed a list of action on service (here you can have a list) or TMF640 which is an api operating directly on your service (this one is unitary).

    Hope it helps

    Ludovic

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



  • 3.  RE: Cease Multiple Services in a single request

    TM Forum Member
    Posted Jan 23, 2022 05:40
    Hi Francis
    Great answer by Ludovic. More generally, we must be careful when discussing operations that change (or in your case disconnect) multiple items. You need to consider what happens (for example) if some of the operations succeed and some fail.
    There is a definite tension between efficiency/latency on the one hand (I want to do many things at once in a single operation), as against complexity on the other hand (how to deal with failures).
    At least currently, the Open API doesn't really address this, our operations in general operate on a single managed entity.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------