Open APIs

 View Only

TMF620 - differnce between recurringChargePeriod/recurringChargePeriodLength and unitOfMeasure:amount/unit

  • 1.  TMF620 - differnce between recurringChargePeriod/recurringChargePeriodLength and unitOfMeasure:amount/unit

    TM Forum Member
    Posted 8 days ago

    Hi

    I have a question regarding some conflicting attributes in the Product Offering Price for the Product Catalog.

    With regards to TMF620 for the Product Offering - the 'POPCharge' object contains the following attributes:

    • recurringChargePeriod (String) - The period type to repeat the application of the price could be month, week...
    • recurringChargePeriodLength (Integer) - the period of the recurring charge:  1, 2, ... .It sets to zero if it is not applicable

    If I had a monthly charge then I would set recurringChargePeriod=1 & recurringChargePeriodLength=month.

    The 'POPCharge' object also contains the 'unitOfMeasure' object (pointing to the schema location 'Quantity') that contains the following attributes:

    • amount (float) - numeric value in a given unit
    • unit (string) - unit

    In the example, in the TMF620 the example identifies the 'amount=1' & 'unit= Month'.

    Would I be correct in assuming that although the recurringChargePeriod/recurringChargePeriodLength and unitOfMeasure:amount/unit are doing the same thing (in my given example), the intention was intended to be slightly different?

    For example, although the charge is monthly; the unitOfMeasure, is attempting to measure something other than the recurring duration (monthly), such as the number of inclusive data Mbps I have included as part of this product offering. Is this a correct assumption?

    Many thanks in advance

    Pete



    ------------------------------
    Pete Bains
    Ultrafast Fibre Limited
    ------------------------------