https://github.com/camaraproject/CarrierBillingCheckOut/issues/194

WG Management

ONGOING

19/FEB: After Pre-Release generation, issue is kept open until Public Release is generated. Some sub-issues mentioned below has been opened (Issues 203 and 204). Milestone for M4 (Public Release PR triggered is 28th February)

https://github.com/camaraproject/CarrierBillingCheckOut/issues/195

WG Management

ONGOING

30/JAN: API release trackers updated with Pre-Release information.
19/FEB: No Updates required until Public Release is delivered

https://github.com/camaraproject/CarrierBillingCheckOut/issues/199

WG Management

ONGOING

08/JAN: In principle no new requirements for MetaRelease. Ludovic comments not sure whether we can close the topic so far. WG agrees on indicating a comment within the issue and effectively close on M4 milestone.

https://github.com/camaraproject/CarrierBillingCheckOut/issues/203

WG

NEW

19/FEB: Issue opened to align API specifications with Commonalities and ICM public releases. Document in issue updates needed and trigger PR. Expected few work.

https://github.com/camaraproject/CarrierBillingCheckOut/issues/204

WG

NEW

19/FEB: Issue opened to align Testing with Commonalities Public Release Guidelines. Document in issue updates needed and trigger PR. Expected few work, probably only needed to update version.

Certification Topic

WG

ADRESSED

05/FEB: Ajmal Hussain (Etisalat UAE) asks for help during GSMA certification of Carrier Billing API. They have implemented 2-legged access. However GSMA is requesting 3-legged access for certification.
Internally, within WG is commented that could be allowed in case the market does not have privacy considerations to have 3-legged flow and also there is an aligment among Operators in such a market. Ludovic also indicates has faced the seam situation for One-time-passowrd-sms. WG agrees on opening an issue in I&CM WG and also involve GSMA. Ajmal will create an issue. Ludovic also will contact in advance to TSC.

19/FEB: Issue addressed. Open issue in CAMARA Governance https://github.com/camaraproject/Governance/issues/181. TSC aware of it.

Implementation Status

WG

NOTE

Current Implementation Status:

• Etisalat UAE Complete Carrier Billing v0.3 (1-STEP, 2-STEP), SYNC MODE. Only have 1-STEP Business Cases

• Telefonica ES Carrier Billing v0.3 (1-STEP), ASYNC MODE. GET features pending

• Orange has no defined roadmap yet

• DT has no defined roadmap yet

19/FEB: After checked offline with ORA and DT status is the same

https://github.com/camaraproject/CarrierBillingCheckOut/issues/205

WG Management

NEW

19/FEB: From TEF no official confirmation yet from Business side. Probably recurrent payments. Also welcome input from other Telco Operators to have an initial view for the next MetaRelease. To be checked in the next meeting

AoB

WG

Other points:

• If any issue durign implementation, feel free to track issues to enhance API specification

• Question raised by Luis Miguel (Digital Virgo) about Payment Susbcriptions. Currently in Carrier Billing the supported model is implicit susbcription (like QoD), API Consumer may indicate a sink where receives events associated to the lifecycle of the resource (e.g. Payment). So implementation is transparent to API Consumer. In other CAMARA APIs there is the explicit subscription model (e.g. sim-swap susbcriptions, device status roaming susbcriptions) where API consumer may subscribe to receive events under certain conditions.