/
2025-03-13 API backlog minutes

2025-03-13 API backlog minutes

 

Attendees

Organization

Name

Orange

 

Charter Communications

 

CableLabs

 

Telefonica

@Alberto Ramos Monaga @Jorge Garcia Hospital

Vodafone

@Eric Murray @Surajj Jaggernath

Ericsson

@Jan Friman

AT&T

 @Pierre Close

T-Mobile US

 

KDDI

 @Toshi Wakayama

Slagen

 

Nokia

 @Tanja de Groot

China Telecom

 

ZTE

 

KPN

 

GSMA

@Reg Cox

Centilion

 

Chunghwa Telecom

 

Deutsche Telekom

 @Noel Wirzius

MTN

 

China Mobile

 

Verizon

 

PlektonLabs

 

TIM

 

NTT

 

China Unicom

 @Xiao Dongrui

Agenda Proposal

Approval of minutes of last conf. call

  • Minutes of last API backlog WG call available here

    • DECISION: Approved

Antitrust Policy

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LinusFoundation.

 

 

New Procedures in API Backlog WG meetings

A number of improvements are under discussion with leadership team of OGW project (Henry), CAMARA Project (Markus), Product Definition WS (Helene) and TSC (Herbert). As of today, the WG adopted agreements are three:

  1. To close the agenda SEVEN DAYS BEFORE the conf. call.

    • In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.

    • Exceptional situations will be treated separately.

  2. New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)

    • 2nd Thursday of the month (9-10:30 UTC)

    • 4th Thursday of the month (15-16:30 UTC)

  3.  Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them. 

  4. New API proposals are included in backlog table when template PR is created, linking to the pending PR

  5. PR will be merged as soon as ready for TSC, and should be merged before TSC review

  6. API enhancements requires existing group’s validation. TSC is informed accordingly to validate

  7. Link and status in backlog table will be updated accordingly

  8. Issue to track API onboarding will be opened once new API is confirmed in TSC.

Recent Updates & Recap

TSC meeting 2025-03-06:

4 new API proposal(s) from APIBacklog working group.

Note: as “special” TSC meeting due to MWC week, APIs will only get approval this time if enough TSC quorum is reached.

  • IoT Network Optimization, supported by TIM.

    • Proposal to enable specific IoT services (e.g. energy saving) for certain set of IoT devices connected to a edge application instance.

    • Original Issue 143; IoT Network Optimization template

    • Comments: none

    • TSC conclusion: approval of TSC will be requested in vote

  • Network Health Assessment, supported by China Unicom.

    • Proposal to provide health score for networks (not individual terminal connections).

    • Original Issue 127; Network Health Assessment template

    • Comments:

      • @Jorge Garcia Hospital API should be not be restricted to private networks

      • @Kevin Smith how does it apply to public networks

      • @Tanja de Groot should apply also to “dedicated networks”, so “private” networks in a sense

      • Conclusion: not intended to be applied to the public network

      • Q @Jan Friman difference to ConnectivityInsights

        • @Jorge Garcia Hospital Connectivity and Session Insight are focused on analysing an specific device connection, while these two proposals are meant for a whole network

    • TSC conclusion: description to be reworked, conclusion next time

  • Network Traffic Analysis, supported by China Unicom.

    • Proposal to provide statistical information of the network traffic (not individual terminal connections).

    • Original Issue 128; Network Traffic Analysis template

    • Comments:

      • @Jorge Garcia Hospital API should not be restricted to private networks

      • see discussion above

    • TSC conclusion:description to be reworked, conclusion next time

  • Dynamic Predictive Connectivity Data, supported by Telefonica and DT.

    • Proposal to provide network coverage information in certain area/volume for a future period of time, allowing to predict whether network coverage will be available e.g. for a drone on certain sky sector.

    • Original Issue 163; Dynamic Predictive Connectivity Data template

    • Comments: none

    • TSC conclusion: approval of TSC will be requested in vote

  • Update on consent URL API proposal:

    • I&CM (minutes) agreed in a way forward for this API proposal, actions pending on repository creation (under ICM working group).

Action Items from the meeting:

  • AP 1: Initiate a TSC vote to approve the creation of Sandbox API Repositories for “IoT Network Optimization” and “Dynamic Predictive Connectivity Data” Mar 9, 2025

  • AP 2: Initiate as TSC vote to approve the creation of a Sandbox API Repository for “ConsentInfo” under the supervision of the ICM Working Group Mar 9, 2025

Other topics

  • GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3/4 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress. 

    • Best Interconnect

    • IMEI Fraud API

For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.

  • Updated API-onboarding guidelines including sandbox, incubated.. repositories and new WoW. PR approved, second phase with restructuring of content table (and split of API and repo lifecycle) ongoing:

  • After the API description proposal was accepted, the process of filling in the API descriptions in the wiki has started using the information published by the marketing team in CAMARA. Please continue adding descriptions and ensure that the relevant participants are included for each API. For example: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/81134043.

Discussion

Current Issues 

Issue #

Company

Summary

Status Update

17 

Centillion

New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement

The API template is available in PR#73.

INITIAL CONTEXT:

Published new standards, Next meeting (this time) Nick will bring all the documentation and present everything putted together

The issue is not eligible to be closed yet.

Pending to provide a concrete API description into the API proposal template

Action: Clarifying with interested parties whether this may be a possible API or a Framework etc.

AP: provide required information and examples

LAST UPDATES: No response since October 8, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

23

TelecomsXChange

New Proposal: Carrier Wholesale Pricing

The API template is available in PR#77

First YAML available here

INITIAL CONTEXT:

The issue was not treated in this conference call

The issue is not eligible to be closed yet.

ACTION: Backlog Governance to reach up TelecomXchange to see if the could connect next meetings

LAST UPDATES: No response for 6 months.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

24

Netfocusin Technologies

New Proposal: Steering of Roaming Management

The API template is available in PR#78

INITIAL CONTEXT:

Does not seem to be in the Scope of Camara. 

Not an east-west (not between telcos) Already included in 3GPP as technical viable (provided in comment)

The issue is not eligible to be closed yet.

ACTION: Check for support/commitment from the partners (technical implementation approach important)

LAST UPDATES: No response since May 10, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

35

China Mobile

5G New Calling

The API template is available PR#31

INITIAL CONTEXT:

Telefonica and Vodafone willing to see the presentation to check whether there is support for this

To be treated in next session (still pending for providing extra info)

Presentation of current proposal was shared in the meeting. Slides to be included in  PR#31.

@Murat Karabulut asked about the proposal been part of WebRTC enhancement or new API → new API.

@Eric Murray asked about examples of 3rd parties in this API flow → app invoquing API to request or activate features, which can be enabled or not by the telco.

@Mark Cornall raised the existance of a 5G New Calling project in GSMA: 5G New Calling & 5GNCTF Meeting#1

ACTION: Operators open to comment/ask for clarification and support the API.

@Eric Murray asks for user stories that can explain the behaviour of the proposed API, as not clear how this interacts with the proper 5G New Calling standard and how it solves the features that are proposed.

AP for @Haojie Li

https://github.com/camaraproject/WebRTC/issues/52 to discuss in WebRTC about relationship

new information to be uploaded and treated in next session

Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there.

LAST UPDATES: No response since June 11, 2024.

Feb 27, 2025: not treated

MEETING UPDATE:

Mar 13, 2025:

63

MTN

New API proposal - IMEI Fraud

The API template is available PR#64

INITIAL CONTEXT:

This API was presented already and included in an existing group but no work was done so discontinued. Now Rebecca is presenting the proposal seeking for support

DeviceCheck GSMA proposal overlaps this

IMEI Fraud will offer more information to developers than GSMA Device Check service.

MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense.

Request for meeting already sent by GSMA to MTN

Outcome of meeting awaited before deciding if this API proposal should proceed in CAMARA

  • Pending to be confirmed by MTN, AP to be raised.

@Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal.

ACTION: Pending from MTN for moving on with this API. Maybe to be included in the Device Identifier family.

 @reg no further information from MTN, consider to de-prioritize, pending to further update

Any other operator open to take the lead of this API is welcomed

LAST UPDATES: No response since September 6, 2024.

Feb 27, 2025: no treated

MEETING UPDATE:

Mar 13, 2025:

115

China Unicom

SIM Historical Information

The API template is available in PR#114

INITIAL CONTEXT:

@Eric Murray comment: Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project.

APs: China Unicom

  • Upload presentation to github by adding as additional document to PR#114

  • Raise issue in SIM Swap sub-project proposing to bring new use case into SIM Swap. Refer to PR#114 in the new issue.

  • If SIM Swap sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting

LAST UPDATES:

Feb 13, 2025: @Fan Yang to review issue offline and provide feedback and current status of the proposal.

Feb 27, 2025: @Fan Yang no updates, will be reviewed in next meeting

MEETING UPDATE:

Mar 13, 2025:

121

China Unicom

User Account Spend Count

The API template is available in PR#120

INITIAL CONTEXT:

Use case appears to be a KYC use case

APs: China Unicom

  • Upload presentation to github by adding as additional document to PR#120

  • Raise issue within KYC sub-project proposing to bring new use case into KYC. Refer to PR#120 in the new issue.

  • If KYC sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting

LAST UPDATES:

Feb 13, 2025: @Fan Yang to review issue offline and provide feedback and current status of the proposal.

Feb 27, 2025: @Fan Yang no updates, will receive new in next meeting

MEETING UPDATE:

Mar 13, 2025:

122

China Unicom

Number Of Cards Under User's ID

The API template is available in PR#119

INITIAL CONTEXT:

Use case appears to be a KYC use case

APs: China Unicom

  • Upload presentation to github by adding as additional document to PR#119

  • Raise issue within KYC sub-project proposing to bring new use case into KYC. Refer to PR#119 in the new issue.

  • If KYC sub-project agree that new API fits within the scope of that sub-project, then submit a sub-project scope modification request to API backlog, otherwise try to progress proposal as a new sub-project at next API Backlog meeting

LAST UPDATES: