TM Forum Community

Hi, We are working on the adoption of the Carrier Billing OTT flow (mobile/home) and we would like to clarify some doubts we have and ask for your help regarding the proposed solution of the process. We have 3 proposed scenarios.

Scenario 1:

For scenario 1: Is it feasible for a developer, either internal (labeled as "developer" on the upper box) or external (labeled as "Integrators" on the lower box), to consume TMF APIs Considering that this would be for a Carrier billing-type flow.​

What would be the TMF recommendation for executing a Carrier billing-type flow (e.g an OTT purchase)?

Scenario 2:

Question for scenario 2: Similar to scenario 1, the difference would be that the internal developers and external integrators would consume GSMA standard APIs, while TMF will be used towards the internal systems. Is this recommended according to TM FORUM's architecture?

Scenario 3:

Question about scenario 3: A combined solution from scenario 1 and 2. That is, exposing GSMA APIs towards external integrators, while exposing TMF APIs towards internal developers. Is it recommended according to the architecture of TMFORUM? What would be the TMF recommendation for executing a Carrier billing-type flow (e.g an OTT purchase)?

We remain attentive to any questions or comments,

Thank you!

For Scenario 1:  What would be the TMF recommendation for executing a Carrier billing-type flow (e.g an OTT purchase)?

 API Usage Recommendations
TMF622 – Product Order API
TMF637 – Product Inventory API