2024-09-26 API backlog minutes
Attendees
Organization | Name |
Orange | @Ludovic Robert |
Charter Communications |
|
CableLabs |
|
Telefonica | @Jorge Garcia Hospital |
Vodafone | @Eric Murray @Kevin Smith |
Ericsson | @Thorsten Lohmar |
AT&T | @Pierre Close |
T-Mobile US | @Murat Karabulut |
KDDI | Yusuke Nakano |
Slagen |
|
Nokia |
|
China Telecom |
|
ZTE |
|
KPN | @Appelboom, Huub |
GSMA | Reg Cox @Mark Cornall |
Centilion |
|
Chunghwa Telecom |
|
Deutsche Telekom |
|
MTN |
|
China Mobile | @Haojie Li @Keguang He @zhangruqian |
Verizon | @Mahesh Chapalamadugu |
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
OGW Drop #4 APIs: #35 (5G New Calling), #50 (Device Management), #63 (IMEI Fraud), #83 #85 #86 #87 (Model as a Service),
Other APIs: #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #66 (network Info), #68 (Consent URL), #89 (IP High-throughput Elastic Network)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
Closing Issues
AoB
Q&A
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:
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.
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 (10-11 CET)
4th Thursday of the month (15-16 CET)
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.
Meeting Minutes within Wiki instead of Github
CAMARA community agreed that meeting minutes would only be recorded in the wiki
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 19th September:
Repository for QualityByDesign created (as decided last meeting)
New API proposal brought to TSC (2):
See message https://lists.camaraproject.org/g/tsc/message/227
TelcoIndex API
Supported by Telefonica, DT, Vodafone
API proposal: Link
Discussion:
Naming discussion: https://github.com/camaraproject/APIBacklog/pull/42#issuecomment-2348157633
Decision: Start this API in sandbox (repo) and then work on the name
Jorge Garcia Hospital propose first to ask to supporter companies if OK to start with this name.
Axel.Nennker@telekom.de explained that for DT the term risk indicator was used. The use of score term is very risky (from regulation). We must be clear that it will not be used to discriminate people. If it based on AI model, the model must be shared to allow people to challenge it.
Dedicated Networks API
Supported by Ericsson, Nokia, Telefonica, Vodafone
API proposal: Link
Decision : Start the work in a sandbox (repo) and then with provided assets check/reassess collision/overlap with other CAMARA API (like network slicing booking API but other APIs could be affected)
Other topics
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3 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
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.
(new) Sandbox proposal from TSC to speed-up the inclusion of new APIs into CAMARA, fostering the development of new APIs and the finalization of API scope definition.
Backlog table
Table updated in PR#79 (unmerged) New backlog table with reduction of columns → All reviews are welcomed
Discussion
Current Issues
Issue # | Company | Summary | Status Update |
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement | 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 MEETING UPDATE: Clarifying with interested parties whether this may be a possible API or a Framework etc. | |
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | PR is uploaded: New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog (github.com) PR to be checked and confirmed before issue can be closed MEETING UPDATE: Partners to review and validate | |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML available here | 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 MEETING UPDATE: Not treated | |
Netfocusin Technologies | New Proposal: Steering of Roaming Management
| 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) Meeting Update: Not treated | |
China Mobile | 5G New Calling The API template is available PR#31 | 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) Pending to clarify scope with VerifedCaller MEETING UPDATE: 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: https://www.gsma.com/get-involved/gsma-foundry/5g-new-calling/ & 5GNCTF Meeting#1 Operators open to comment/ask for clarification and support the API. | |
Verizon | Device Management The API template is available PR#30 | The issue was not treated in this conference call The issue is not eligible to be closed yet. Action to contact Verizon to ensure participation in next backlog meeting MEETING UPDATE: API proposal presented by @Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. @Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. | |
Vodafone | Scope Enhancement for Network info The API template is available PR#72 | To clarify if new API is proposed in the Device Status Family or it's an enhancement over an existing API. To clarify its relationship with Open Gateway Telco Finder API → Kevin opened PR#72 to complement Issue PR#66. Both still open. Noel commented that this is likely to be accepted New repository is likely to be required Comments have been provided in the issue
MEETING UPDATE: Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143 Enhancement proposal to be updated by @Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. | |
MTN | New API proposal - IMEI Fraud The API template is available PR#64 | 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
MEETING UPDATE: @Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. Waiting for MTN for moving on with this API. Maybe to be included in the Device Identifier family.
| |
Telefonica | New API proposal - Consent URL The API template is available PR#67 | The API proposal was presented, including additional slide info Discussion to follow offline in the issue/PR.
MEETING UPDATE: @Appelboom, Huub supports API proposal @Murat Karabulut previously raised some concerns but seem clarified with last documentation. (uploaded in API PR#67 and also direct link) Proposal to be brought to TSC if no other concern is raised before end of week. | |
Deutsche Telekom | Best Interconnection | Seek for support ACTION: See if there is any overlap within EdgeCloud ACTION: Nick (centillion) to review with Noel (DT) about the match of use cases and consider support. DECISION API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open. MEETING UPDATE:
| |
China Mobile | Model As A Service Family | China Mobile presented the API MEETING UPDATE: To include support from ZTE and Huawei. Proposals in good shape for been moved to TSC approval, @Haojie Li asked for one additional round for more clarifications and comments.
| |
China Mobile | Knowledge Base - Manage |
MEETING UPDATE:
| |
China Mobile | Q&A Assistant - Manage |
MEETING UPDATE: | |
China Mobile | Q&A Assistant - Service |
MEETING UPDATE: | |
China Mobile | IP High-throughput Elastic Network The API template is available in PR#90 | Not to be treated in this meeting. |
Closing Issues
Issue # | Company | Summary | Status Update |
T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API Initial YAML files to be included in the API TEMPLATE MEETING UPDATE:
| |
Totogi | New Proposal: Receive SMS |
Seems to fit in the SMS as a new scope enhancement The issue is not eligible to be closed yet. ACTION: Ricardo to formally proceed with the scope enhancement os the SMS group MEETING UPDATE:
| |
Deutsche Telekom |