2025-11-13 API backlog minutes

2025-11-13 API backlog minutes

 

Attendees

Organization

Name

Orange

 

Charter Communications

CableLabs

 

Telefonica

Alberto Ramos Monaga

Vodafone

Kevin Smith Eric Murray @lauren kaye

Ericsson

Jan Friman @Kamran Keykhosravi

AT&T

 

T-Mobile US

 

KDDI

 

Slagen

 

Nokia

 

China Telecom

 

ZTE

 

KPN

 

GSMA

 

Centilion

 

Deutsche Telekom

 

MTN

 

China Mobile

 

Verizon

PlektonLabs

 

TIM

 

NTT

 

China Unicom

 

Infosys Ltd

Ravi Shekhar

Spectrum

 

Chunghwa Telecom

 

Telecom Argentina

 

Huawei

 

xFlow Research

ALI IQBAL

Agenda Proposal

  • Antitrust Policy

  • Approval of minutes of last conf. call

  • Recent Updates & Recap

  • Discussion

    • New APIs Proposals:  

      • #250 (In Home Device Management API), #256 (Voice One Time Password Call), #267 (Radio signal attenuation API)

    • Scope Enhancement:

      • N/A

    • Out of Agenda: N/A

  • Closing Issues

    • #141 (Energy Footprint Notification), , #126 (Facial Recognition), #18 (Receive SMS), #89 (IP High-throughput Elastic Network), #41 (Telco Scoring), #83 #85 #86 #87 (Model as a Service), #20 (Best Interconnection), #68 (Consent URL), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #50 (Device Management) #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #109 (Support application resource requirements in application profiles), #163 (Dynamic Predictive Connectivity Data), #143 (IoT Network Optimization), #127 (Network Health Assessment), #128 (Network Traffic Analysis), #136 (eSIM Remote Management), #157 (Voice Notification), #160 (Voice Verification Code), #223 (Sponsored Data), #241 (Fraud Hotzone Alert), #262 (Provider Implementation - Energy Footprint Notification), #261 (Scope enhancement: Proposal to Expand DCB Applicability Beyond Mobile Subscribers to Home Accounts), #63 (IMEI Fraud - reactivate from frozen status)

  • Frozen API

    • #35 (5G New Calling), #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #115 (SIM Historical Information), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID), #167 (IdentityAndConsentManagement)

  • Review of Action Points

  • Decision Points

  • AoB

  • Q&A


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:

  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.

  9. New proposal Lifecycle for frozen APIs.