Open APIs

 View Only
  • 1.  Dynamic service catalog

    TM Forum Member
    Posted 20 days ago
    Hi All,

    Currently we are using one CFS for multiple Products and we want to send only specific characteristics per product for same CFS in 633 API, So that service catalogue can be dynamic for Get service and filter characteristics as per product.
    Can you please suggest.

    Regards,
    Prashanth

    ------------------------------
    Prashanthbabu Bhimarapu
    Proximus SA
    ------------------------------


  • 2.  RE: Dynamic service catalog

    TM Forum Member
    Posted 19 days ago

    Hi Prashanth

    Can you please give a concrete business example (if you can do this without leaking IP).
    And what do you mean by "send" - is it POSTing a service order for the CFS via TMF641?

    These clarifications could help the community to understand your dilemma.



    ------------------------------
    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.
    ------------------------------



  • 3.  RE: Dynamic service catalog

    TM Forum Member
    Posted 19 days ago
    Hi Jonathan,

    Thank you for your response.

    For example I have Products Internet, Voice, TV and we use one common CFS  ex. CFS X for  all three products and this CFS have multiple characteristics, some are necessary for internet and some are necessary for Voice, and when any consumer tries to retrieve service specification for CFS X for product Internet using GET 633 API, We would like to expose only characteristics which are necessary for internet in 633 GET response and when consumer tries to retrieve service specification for VOICE for CFS X only characteristics which are necessary for VOICE should be exposed in 633 GET response.

    Regards,
    Prashanth

    ------------------------------
    Prashanthbabu Bhimarapu
    Proximus SA
    ------------------------------



  • 4.  RE: Dynamic service catalog

    TM Forum Member
    Posted 19 days ago
    It seems to me that you are looking for a capability of having additional metadata at the characteristic level - we don't have this in the Open API model but you could add as an extension.
    But it's still not clear to me how this would work - perhaps a consumer that does retrieve (GET by ID) in TMF633 will receive all the characteristics, it will then have the responsibility, based on consumer context, to use this metadata to decide which characteristics are relevant.

    ------------------------------
    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.
    ------------------------------



  • 5.  RE: Dynamic service catalog

    TM Forum Member
    Posted 19 days ago
    Why would you want to squeeze all this complexity into one service? It doesn't seem like a good idea.

    The general guideline for good design is "separation of concerns". The various TM Forum standards have always been developed using this design rule.
    A CFS should provide one and only one atomic service. This keeps you processes clearly defined, simple and reusable.

    Regards

    ------------------------------
    Koen Peeters
    OryxGateway
    ------------------------------