Open APIs

Expand all | Collapse all

TMF620-Product Catalog Management API

  • 1.  TMF620-Product Catalog Management API

    TM Forum Member
    Posted Apr 26, 2021 10:00
    Hi Team,

    We have one use case in which we have to support product offering with national sms,data,international minutes(selected countries).
    For this we can create Product Specification Characteristics like sms,data,international_minutes but not sure how to handle selected countries (international minutes in selected countries)
    We have though of below approaches :
    Approach 1
    1.) Create Product Specification Characteristic i.e Country
    2.) Create Multiple PSCVS - India,Hongkong,Japan

    Approach 2
    Introduce new attribute "COUNTRY" under TmaProductSpecCharactersticValue model
    1.)Create PSC -> International calls
    2.)Create PSCV -> 30 Mins, list of countries (India,Hongkong,Japan etc..)

    Which Approach is better or if you can suggest any other approach to support it.

    Thanks & Regards,
    Piyush Gupta
    Senior Advisory System Analyst

    IBM Corporation

  • 2.  RE: TMF620-Product Catalog Management API

    TM Forum Member
    Posted Apr 27, 2021 01:29
    Hi Piyush

    It depends on your pricing model, and also how much you want the quantity of the allowance (number of minutes, messages, MB) to vary.

    A simple approach (e.g. if the quantities are fixed across all countries) that would allow you to set tariffs that are different for each country, you might want to create an explicit ProductOfferingPrice (POP) per country, that encapsulates the allowances for the various usage types (voice, SMS, data) for the country. At order capture time you could then allow the end user to select the POPs to be instantiated in the Product as part of the order; these Product Prices would then be notified to billing + charging as part of order delivery.

    If you need multiple sets of quantities, you could define POPs for each quantity (but we are at risk of a POP explosion), but you would then have to find some way to represent the allowance values in the underlying product spec, since we don't currently support characteristics on POP itself in the catalog API. In this case your best bet would probably be to define a custom characteristic of type object array, which I think is a combination of your approaches 1 and 2 above.  Note that in future API versions and design guidelines, we plan to have a multitude of typed characteristics, one of which is indeed an array of objects.

    Hope it helps

    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.