Open APIs

 View Only
  • 1.  TMF641 ServiceRelationship in single serviceOrder

    TM Forum Member
    Posted Apr 02, 2020 17:50
    Dears,

    I am struggling with TMF641 for a specific use case I would like to apply.

    I am trying to, in a single TMF641 POST call, create three different services with some ServiceRelationship between them.
    However, to be able to do this, I think I need the ServiceRef ID from previous created services and they dont exist at this point..

    The example is basically to POST an order with three items:
    - CFS A
    - CFS B (reliesOn A)
    - CFS C (reliesOn B)

    How can I handle this in a single POST?

    Thanks in advance

    ------------------------------
    Carlos Portela
    Proximus SA
    ------------------------------


  • 2.  RE: TMF641 ServiceRelationship in single serviceOrder

    TM Forum Member
    Posted Apr 03, 2020 02:07
    Hi Carlos

    You can use service order item relationship.
    The order item B relies on the A for example.

    Then your delivery system has to 'read' these relationships and orchestrate acordingly the fulfillment plan. The relationship depending on the sematic has to be stored in the inventory.

    Hope it helps

    Ludovic


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



  • 3.  RE: TMF641 ServiceRelationship in single serviceOrder

    TM Forum Member
    Posted Apr 06, 2020 19:50
    Hi Carlos,
    I would assume that in the service specification, you would have already published the required service relationship, therefore the requester would be aware of the need of this relationship.
    If the requester is intending to send all the order items (for creating the service instances) in a single TMF 641 request, they can add it as Order Item relationship and the provider system translate the order item relationship into service instance relationship run time. The order of execution (workflow, orchestration) is based on provider's fulfilment plan. Note that the order relationship for fulfilment purpose, translating to service relationship is more for inventory/operation purpose.
    This is my take.

    ------------------------------
    Varun Nair
    Telstra Corporation
    ------------------------------