Hi Dan,
Few elements of answer:
1 - We think that SID needs to be enriched with the capability to manage Usage Volume and balances at service level, as illustrated in TMFS009. Refer to SID JIRA ticket [ISA-1129] UsageVolumeBalance should also exist in Service (CFS) domain - TM Forum JIRA
2 - At ODA components level, the initially identified Product Rating component has been merge with TMFC040 Product Usage Mgt, with a first version already specified and published (and an update v1.1.0 in progress): TMFC040: Product Usage Management v1.0.0 - Components and Canvas - TM Forum Confluence
You can also find an overview of ODA billing components interaction in IG1242 chapter 4.1.2 : IG1242 ODA Component Inventory v15.0.0 - editable version (Sprint 4 2024) - Components and Canvas - TM Forum Confluence It still needs to be enrich at Service level to position Service Balance Mgt.
Hope it helps.
Best regards
Sylvie
------------------------------
Sylvie Demarest
Orange
------------------------------
Original Message:
Sent: Aug 13, 2024 23:40
From: Dan d'Albuquerque
Subject: Open APIs for Product Rating and Session Balance Mgmt (UsageVolumeProductSpec??)
Hi all, @Sylvie Demarest
Various changes to the Open APIs have made in the area of product/service/resource usage APIs, e.g. TMF635 is now dedicated to only product usage, TMF727 and TMF771 are new for service and resource usage. There have also been discussions ongoing relating to how to evolve the TMF654 Prepay Balance Mgmt API to handle more than just prepay subscription types, i.e. aligning with 3GPP Converged Charging System concepts. Relating to ODA, there are planned new components called "TMFC0xy - Product Rating" and "TMFC013 - Service Balance Management" and use cases TMFS009 relating to the Usage and Balance Mgmt for mobile lines (mobile network usage).
What seems to be missing thus far is how the balances/quotas/buckets/pockets will be supported through the Open APIs. SID currently defines a non-monetary and monetary balance in terms of the UsageVolumeProductSpec entity, which derives from an AtomicProductSpecification (see the diagram below). My question is ... what was the reasoning behind? Will it be expected to place a product order item for this UsageVolumeProductSpec entity?
Thanks in advance
------------------------------
Dan d'Albuquerque
Individual
------------------------------