Open APIs

 View Only
  • 1.  Open API for subscriber cumsumption limit mangament in shared bucktes

    TM Forum Member
    Posted Aug 17, 2022 08:49
    Hello,

    We are trying to find out which Open API would be the most suitable for managing the subscriber consumption limit in shared buckets.

    A bucket could be shared among several subscriber and usually it's required to be able to define a consumption limit for each subscriber. For instance, a 50GB data bucket can be shared among the different members of the family, but it should be able to define a different consumption limit for each of them. For example, the father and the mother can have a consumption limit of 20 GB and each of the children can have a limit of 7 GB.

    Reviewing the APIs where the entity bucket is defined (TMF 677 y TMF654) we haven't seen how consumption limits can be managed nor how they will be modeled following the SID model.
    • TMF677: it is only suitable for querying information about the bucket consumption. The consumption made by each resource is provided in ConsumptionSummary entity, but no resource consumption limit is modeled. 
    • TMF 645: its main purpose is the prepaid balance management, even though, non-monetary buckets are also described and it is the unique API where Create/Delete bucket operations are defined (as far as we have seem).  But in this API we also do not see any modeling of bucket consumption limits or operations to manage them.

    If anyone has faced the same problem, we would be grateful if you could share what was the approach and API used.

    Kind regards,
    Ruben Sancho.

    ------------------------------
    Ruben Sancho
    Orange Espagne S.A.U
    ------------------------------


  • 2.  RE: Open API for subscriber cumsumption limit mangament in shared bucktes

    TM Forum Member
    Posted Aug 22, 2022 05:16
    Edited by Jonathan Goldberg Aug 22, 2022 05:59
    Hi Ruben
    It does look as if this functionality is missing from the prepay balance API (TMF654). And, as you correctly state, this is relevant not just for prepay, but also for limiting postpay usage allowances, for example.
    You can of course extend the API definition to meet your specific needs, in the meantime I've opened a CR: https://projects.tmforum.org/jira/browse/AP-4077

    ------------------------------
    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: Open API for subscriber cumsumption limit mangament in shared bucktes

    TM Forum Member
    Posted Aug 23, 2022 05:58
    Hi Jonathan,

    Thanks for your answer!!

    Therefore, in your opinion, the consumption limits of a shared bucket should be managed by API 654 and we should extend its definition to meet our needs.

    In order to use the current APIs as much as possible, we were thinking about modeling the consumption limits as a bucket related to the shared bucket and to the resource (MSISDN) that can make use of it, whose initial value is the consumption limit defined for that resource. What do you think about this approach?

    Regards,

    ------------------------------
    Ruben Sancho
    Orange Espagne S.A.U
    ------------------------------