2026-01-08 API Backlog Minutes
Attendees
Organization | Name |
Orange |
|
Charter Communications |
|
CableLabs |
|
Telefonica | @Alberto Ramos Monaga @Jorge Garcia Hospital |
Vodafone | @Eric Murray |
Ericsson | @Jan Friman @Kamran Keykhosravi |
AT&T |
|
T-Mobile US |
|
KDDI |
|
Slagen |
|
Nokia | @Tanja de Groot |
China Telecom |
|
ZTE |
|
KPN |
|
GSMA | @Reg Cox |
Centilion |
|
Deutsche Telekom |
|
MTN |
|
China Mobile |
|
Verizon |
|
PlektonLabs |
|
TIM |
|
NTT |
|
China Unicom |
|
Infosys Ltd |
|
Spectrum |
|
Chunghwa Telecom |
|
Telecom Argentina |
|
Huawei |
|
xFlow Research |
|
Agenda Proposal
#141 (Energy Footprint Notification), #126 (Facial Recognition), #18 (Receive SMS), #20 (Best Interconnection), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #109 (Support application resource requirements in application profiles), #136 (eSIM Remote Management), #157 (Voice Notification), #160 (Voice Verification Code), #241 (Fraud Hotzone Alert), #63 (IMEI Fraud - reactivate from frozen status), #250 (In Home Device Management API), #267 (Radio signal attenuation API)
Approval of minutes of last conf. call
Minutes of last API backlog WG call available here
DECISION: OK
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.
New proposal Lifecycle for frozen APIs.
Recent Updates & Recap
Last TSC meeting 2025-12-18:
Two new APIs are proposed from the CAMARA Backlog WG for inclusion as Sandbox APIs:
In-Home Device Management API: #250
Taxonomy (proposed): Service Management
API family owner: Infosys – @Ravi Shekhar
API family supporters: Infosys
Scope / description: This API allows applications to manage in-home device connectivity by controlling network access (blocking or unblocking devices connected to the home network) and by monitoring network health, checking each device’s connectivity status and providing recommendations to improve overall network performance.
Create as a Sandbox repository: InHomeDeviceManagement (aligned with existing Sandbox repositories)
Decision: approved - Onboarding tracker created: https://github.com/camaraproject/APIBacklog/pull/282
Radio Signal Strength API: #267
Taxonomy (proposed): Communication Quality
API family owner: Ericsson – Kamran Keykhosravi
API family supporters: Ericsson
Scope / description: This API provides access to microwave links in the operator’s network (their endpoints, carrier frequencies, and current attenuation) and uses these radio links as virtual rain sensors. By observing how rain attenuates the microwave signal in a predictable way for each frequency, the API delivers near real-time rainfall information for a defined geographical area. API consumers can then translate attenuation (in dB) into rain intensity (mm/h) and feed this data into their own rainfall and geospatial models.
Create as a Sandbox repository: RadioSignalStrength (aligned with existing Sandbox repositories)
Decision: approved, final name to be determined in Onboarding tracker issue - Onboarding tracker created: https://github.com/camaraproject/APIBacklog/issues/291 - Final name decision: Rainfall Intensity API
Governance & Project Management
Unified Clean-up Process for Inactive Onboarding Trackers and Repositories: Ready to merge - https://github.com/camaraproject/Governance/pull/201. For already evaluated once @Alberto Ramos Monaga will create issues in APIBacklog:
Consent Info API evolution / Controlled Consent Capture Delegation.
Telefónica provided a proposal that suggests managing Consent Capture Delegation via two distinct APIs rather than overloading the existing Consent Info API.
The group agreed to separate the APIs. No objections raised. ICM will request a new repository (ConsentManagement) for the new Consent Management API. The group also agreed (no objection raised) moving the existing PR #43 content to this new repository as an initial contribution.
Further details of the above items can be found at 2025-12-17 ICM Minutes
Decision: Onboarding tracker created: https://github.com/camaraproject/APIBacklog/issues/292
Other topics
(Reminder) CAMARA APIs - Functional Differences (Use-Case & Data Semantics Edition): A white paper has been produced for publication on the CAMARA website to explain in detail what problem each API solves, what data it delivers, how to interpret it, and how to combine them in risk and error-prevention policies (Audience: Non-telco experts) APIs covered: SIM Swap · Device Swap · Tenure · Number Recycling - (link)
Discussion
Current Issues
Issue # | Company | Summary | Status Update |
Heksagon | Voice One Time Password Call The API template is available at #263 | INITIAL CONTEXT: The “Voice One Time Password Call” API is used to send short-lived one time passwords (OTP) to a phone number via voice call and validate it afterwards, in order to provide a proof of possession of the phone number. AP1: Update the PR by creating a new entry under AP2: Create an issue with the AP3: Resolve the easyCLA error by clicking the provided link and signing the authorization Sep 25, 2025: Not treated Relation with Voice Verification Code (#233) - Herbert suggest if we can merge this with this issue. Heksagon: Regarding your suggestion to merge our issue proposal with #233, we have checked and it looks like that their use case works only for "IMS based audio codes" as explained in their API description which is not the case for our API. So we don't think that merging the two issues would be a good idea. If there is any further discussion needed on that, we can have a call to evaluate it. Oct 10, 2025, Oct 23, 2025, Nov 13, 2025,Nov 27, 2025: Not treated Dec 11, 2025: Resolve the PR comments and upload the PowerPoint presentation - Not treated MEETING UPDATE: Jan 8, 2026: Not treated | |
T-Mobile US | Group Management API The API template is available at #289 | INITIAL CONTEXT: The Group Management API enables API Consumers to create and manage named groups of pre-defined entities (e.g. devices or areas). It supports batch membership operations and event-driven notifications, making it ideal for Service APIs (e.g., Geofencing) that need to manage and track sets of entities, and be informed about changes to group member states. Related Issue: Standardize Group Management for CAMARA Sub-Projects MEETING UPDATE: Jan 8, 2026: Not treated | |
NCSRD | Trust Worthiness Intent API The API template is available at #294 | INITIAL CONTEXT: TWIA is an intent-based API that lets an app submit high-level trust requirements (Security, Privacy, Reliability, Resilience, Safety) in natural language and get back per-category scores plus an overall trustworthiness level, without dealing with low-level configuration. MEETING UPDATE: Jan 8, 2026: Not treated |
Out Of Agenda
N/A
Closing Issues
Issue # | Company | Summary | Status Update |
Totogi | New Proposal: Receive SMS
The API template is available in PR#75 |
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:
→ Follow-up on API onboarding tracker: Pending. | |
Deutsche Telekom | Best Interconnection
The API template is available in PR#88
Input from OGW Drop 3 | 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: Not treated → Follow-up on API onboarding tracker: Pending. | |
Telefonica | Fixed Lines in Location The API template is available in PR#92 | METING UPDATE: Issue open in location https://github.com/camaraproject/DeviceLocation/issues/271 | |
Telefonica | Line Eligibility for Carrier Billing API The API template is available in PR#94 | MEETING UPDATE: Issue open in Carrier Billing https://github.com/camaraproject/CarrierBillingCheckOut/issues/190 | |
China Mobile | Facial Recognition The API template is available in PR#130 | EasyCLA to be solved METING UPDATE: material presented by YinMing Fu. @Eric Murray proposes in 126 to consider this API as part of already existing ModelAsA Service APi group (also from China Mobile) YinMing Fu considers API separated as MaaS focused on LLM models @Eric Murray raises issues on match with CAMARA authentication, privacy and identity existing mechanisms to be applied in this API @Jorge Garcia Hospital raised question on the telco capabilities been leveraged --> MNO face database is used AP to China Mobile to clarify open points To modify the template to ScopeEnhancement of MaaS. @YinMing Fu updated PR#130 and API will be treated in next TSC 19th dec. 15:00 UTC METING UPDATE: Approved, pending to decide whether it will be part of same repo or different from MaaS → Follow-up on API onboarding tracker: Pending. | |
China Unicom | eSIM Remote Management The API template is available in PR#140 | INITIAL CONTEXT: Action for all China Unicom Topics: @Reg.cox will ask for an update from China Unicom in the next meeting LAST UPDATES: Feb 13, 2025:@Jan Friman some sequence diagrams will be good to understand the API proposal. AP: China unicom to upload additional information and flows of the API proposal. Feb 27, 2025:
MEETING UPDATE: Mar 13, 2025: @He Dongsheng only IF1 will be standardize in CAMARA. @Eric Murray : only IoT eSIMs are considered? Q: any use case regarding eSIM is considered, including travel eSIM or other use cases. @Tanja de Groot : clean APi template language: please take care in desciptions to avoid references to "telco". Use API provider instead → API template to be fixed → Follow-up on API onboarding tracker: https://github.com/camaraproject/APIBacklog/issues/193:
|