2025-01-09 API backlog minutes
Attendees
Organization | Name |
Orange | @Ludovic Robert |
Charter Communications | @Christopher Aubut |
CableLabs |
|
Telefonica | @Jorge Garcia Hospital |
Vodafone | Ali Gilani @Eric Murray @Kevin Smith |
Ericsson | @Jan Friman |
AT&T |
|
T-Mobile US |
|
KDDI | @Yusuke Nakano @Masaharu Hattori @Toshi Wakayama |
Slagen |
|
Nokia |
|
China Telecom |
|
ZTE |
|
KPN |
|
GSMA | Reg Cox @Mark Cornall |
Centilion |
|
Chunghwa Telecom | @Guang-Han Ma |
Deutsche Telekom |
|
MTN |
|
China Mobile |
|
Verizon |
|
PlektonLabs |
|
TIM | @fabrizio moggio@Antonio Varvara |
NTT |
|
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
New APIs Proposals: #35 (5G New Calling), #50 (Device Management), #63 (IMEI Fraud), #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #115 (SIM Historical Information), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID), #127 (Network Health Assessment), #128 (Network Traffic Analysis), #136 (eSIM Remote Management), #143 (IoT Data Transfer Activation), #154 (QoS Booking), #157 (Voice Notification), #160 (Voice Verification Code), #163 (Dynamic Connectivity Data)
Out of Agenda:
API Enhancements Proposals: #109 (Support application resource requirements in application profiles)
Governance: N/A
Closing Issues
#22 (Capability and Runtime Restrictions), #18 (Receive SMS), #41 (Telco Scoring), #20 (Best Interconnection), #68 (Consent URL), #83 #85 #86 #87 (Model as a Service), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #89 (IP High-throughput Elastic Network), #141 (Energy Footprint Notification), #126 (Facial Recognition)
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 (9-10:30 UTC)
4th Thursday of the month (15-16:30 UTC)
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.
New API proposals are included in backlog table when template PR is created, linking to the pending PR
PR will be merged as soon as ready for TSC, and should be merged before TSC review
API enhancements requires existing group’s validation. TSC is informed accordingly to validate
Link and status in backlog table will be updated accordingly
Issue to track API onboarding will be opened once new API is confirmed in TSC.
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 19th December:
https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md
One new API proposals brought to TSC (1) and one new API enhancement proposal.
New API: Energy Footprint Notification:
API enhancement: Facial Recognition:
Proposed by China Mobile as part of existing ModelAsAService API repository. Original Issue #126. Template available.
The ModelAsAService Sandbox team should consider if they want to develop the API within the ModelAsAService repository or in a separate repository (e.g. to allow participation of contributors who want get only involved into the original ModelAsAService scope)
Decision: enhancement approved - target repository of this API to be decided later.
API Backlog proposal for API management/marketing…:
As in APIBacklog/issues/123 , companies see a suitable feature to have a spot in each repository where participants can be reported, stating the interest of those participant companies for this API.
Current options:
CodeOwner/maintainer list: Includes companies actively leading the API definition, but not companies which participate in a more passive way.
Github contributors tool (e.g./APIBacklog/graphs/contributors ) reports the companies which have participated actively in the API, with e.g. providing code. But does not report companies who passively track the API evolution, e.g. participating in the discussion meetings.
Proposal to create a place where companies can provide their support or willingness to participate in an API, not official as maintainer/codeowner and not providing proper code as in
contributors.Companies to provide support (or concerns) about this proposal. E.g. wiki page of each repository could host a file where companies can include their support to the API(s)
Decision: Provide a proposal to backlog group about what to be added in the confluence page to track companies supporting the API (without necessarily be code owner and/or maintainer).
Meeting update:
Create a participants / interested parties template to be included in each confluence page. Company names to be included.
Create a description of the meaning of participant (companies interested in an API, participating actively or passively in the WG…)
About repository lifecycle, sandbox…archived proposal will be finalized and started (before spring25).
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.
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.
(new) Backlog table information review https://github.com/camaraproject/APIBacklog/issues/123
Problem description
Current supporters field in backlog table is intended to report original participants who pushed the API proposal template in its inclusion to backlog.
As per #118 , @StefanoFalsetto-CKHIOD proposed to include current supporters in the table.
To discuss in the modification of the Supporters field:
- Or to maintain current info, it is, original supporters of the API proposal
- Or to include current supporters of the API under specification (similar to maintainers list in subgroups)
Meeting Update:
@fabrizio moggio : update developers about operators working in the API. Could be part of the readme.md of each API subgroup, valuable even before an operator have launched an API, just a list of contributors.
Proposal: Create a list of contributors? (complementing current codeowners and maintainers list) @Markus Kümmerle marketing team of CAMARA/GSMA
Closed based on TSC feedback
Meeting management
Participants are encouraged to get registered in LF page for Zoom meeting identification, both individuals and their affiliation.
Github account can be used to facilitate registration and tracking
Also required for CAMARA easyCLA process https://github.com/camaraproject/EasyCLA
Participants are encouraged to get registered in CAMARA confluence to facilitate meeting management and comments/Action Points considerations.
Discussion
Current Issues
Issue # | Company | Summary | Status Update |
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement
The API template is available in PR#73. | 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 MEETING UPDATE: No update | |
TelecomsXChange | New Proposal: Carrier Wholesale Pricing
The API template is available in PR#77 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: No update | |
Netfocusin Technologies | New Proposal: Steering of Roaming Management
The API template is available in PR#78
| 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: No update | |
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) 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: 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. MEETING UPDATE: No updates | |
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 API proposal presented by @Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. ACTION:@Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. @Mahesh Chapalamadugu AP to upload documentation Slides presented by @Mahesh Chapalamadugu & @joshua Slide will be uploaded and reviewed offline before approval MEETING UPDATE: Review match with other Device management APIs (home devices or similar) and IoT/Device status (AP Backlog: contact Mahesh) Also ensure this is a proper telco capacity to be consumed by developers, in comparison with Operate API (TM Forum) that are related to Aggregators. | |
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
@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 MEETING UPDATE: No update (pending) | |
China Telecom | IoT SIM Status Mgmt API The API template is available in PR#105 | Relationship with device management proposal, to confirm relationship. AP: China Telecom Meeting considered that this proposal has some overlap with the Device Management proposal from Verizon APs: China Telecom
@Moyuan Sun proposal to be modified to “communication capabilities” to avoid overlap with Device Management API proposal 50 Slides presented in the meeting (to be updated into the API proposal documentation) @Eric Murray @Murat Karabulut New proposal focused on the management of services of devices (activate/deactivate) but still in relation with Device Management concept @Mahesh Chapalamadugu (Verizon) to confirm if both proposals may still be merged AP: Email thread to be opened to provide a common position MEETING UPDATE: Next backlog meeting will be treated jointly with device management | |
China Telecom | IoT SIM Fraud Prevention API The API template is available in PR#103 | @Jorge Garcia Hospital is it required to create a new set of APIs only for IoT devices or can they live in the existing groups? @Eric Murray agrees, device status can take in charge of this new parameters, check first with this subgroup https://github.com/camaraproject/DeviceStatus MEETING UPDATE: Meeting agreed with China Telecom that this proposal does not fit within Device Status sub-project APs: China Telecom
New proposal shared by@Moyuan Sun about SIM-Device binding change (possibly related to Device Swap) and area alerting (possibly related to Geofencing). Actions over lines are part of Device Management. China Telecom updates proposal in PR#103, keep offline discussion around Device Management.
MEETING UPDATE: Next backlog meeting will be treated jointly with device management | |
Verizon | Support application resource requirements in application profiles The API template is available in PR#110 | METING UPDATE: No update | |
China Unicom | SIM Historical Information The API template is available in PR#114 | @Eric Murray comment: Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project. APs: China Unicom
|
