Open APIs

 View Only

  • 1.  TMF620: Product Catalog API: Complex Product Spec Relationships Modelling

    Posted yesterday
    Edited by Akshay Sahni yesterday

    Hi All,

    While modelling a broadband package we realized the ProductSpecificationRelationship object isn't sufficient to handle complex relationships. Consider the following scenario & modelling constraints:

    1. A broadband package consists of a service and an access which can be fiber/hybrid co-axial
    2. The delivery factories/SOM for both the access is unique
    3. A single product specification can decompose into a single CFS
    4. Obviously at a time either the fiber OR hybrid co-axial can be opted
    5. The 'order orchestrator' doesn't have a view of the PO hierarchy and only refers to PSs

    Given the above scenario and attached resulting product catalog model, what would be the best way to model the relationship between Broadband Service and Access PSs based on the TMF620 API spec

    Option 1:

    Model a relationship type reliesOnXOR between the "Service" and the "Access" i.e. two relationships

    1) from Service to FTTH with type "reliseOnXOR"

    2) from Service to Hybrid with type "reliesOnXOR"

    A regular reliesOn/requires won't work since the orchestration engine would wait for the second association to be fulfilled (which would never happen)

    where in the orchestrator validates either of the instances of PS (fiber or hybrid) and proceeds with the orchestration of the order

    Option 2: Enhance the current API data model  

    Enhance the ProductSpecificationRelationship object to somehow accommodate a "list" of target PS (both FTTH and Hybrid) with a XOR relationship between the two?

    --> Broadband reliesON (Fiber XOR Hybrid Access).

    Option 3: 3 relationships objects  in total

    1. Service reliesOn Fiber
    2. Service reliesOn Hybrid Access
    3. Fiber excludes Hybrid Access

    What would be the community suggestions around this with respect to TMF compliance.

    Current TMF API object:

     

     



    ------------------------------
    Akshay Sahni
    Orange S.A.
    ------------------------------



  • 2.  RE: TMF620: Product Catalog API: Complex Product Spec Relationships Modelling

    Posted an hour ago

    Hi.

    Wouldn't this be solvable at the ProductOffering level using a BundledGroupProductOffering?

    Based on the diagram, the Broadband Package consists of a mandatory Broadband Service product offering (PO) and exactly one of the two POs within the Access Group, with FTTH Access having a default cardinality of 1.

    Additional question: Which orchestration engine are you using? Is it an in‑house implementation, or are you working with a commercial product?



    ------------------------------
    Jan Brnka
    T-Mobile Czech & Slovak Telekom, a.s.
    ------------------------------

    Original Message


Related Content