...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
| GSMA | Mark Cornall |
| Charter Communications | Chris Aubut, |
| Ericsson | Jan Friman |
| Telefónica | Ricardo Serrano Gutierrez (Chairing) Jorge Garcia Hospital Javier Villa Labarra |
| Vodafone | Eric Murray |
| AT&T | Pierre Close |
| KPN | Huub Appelboom |
| Shabodi | Nitin Sood |
| Totogi | Ailton Santana |
| Vonage | Qaunain Meghjee |
| Slagen | D. Garavito |
Agenda Proposal
...
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
...
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Minutes are approved
Recent Updates & Recap
TSC meeting 21st march:
...
- Presentation of the process shared and commented by Ricardo Serrano Gutierrez and Helene Vigue (GSMA)
- Support to be shared.
- Presented material:
Backlog table
- Table updated in PR#396
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20230208-02 | WG delegates | Delegates from interested parties to prepare a list of questions for this API, for Nick to answer them. | 2024/02/21 | Open | |
| 20230208-01 | Centilion | To draft a simple figure illustrating the API logic with a high-level workflow, and attach it to the PR. | 2024/02/21 | Open | |
| 20240314-01 | Governance | Ricardo to share the RACI in the issue 367 comments, after making CAMARA specific document and validation by TSC | 367 | 2024/03/14 | Open |
| 20240314-02 | Charter Communications | Write in the API template the scope of the API that have been provided as a comment in the PR#379. | 378 | 2024/03/14 | Closed |
Discussion
...
| 330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | China Unicom and Telefonica to create a single family for both API: Location Insights, Use historical informations to manage location information of the user. The issue is not eligible to be closed yet. DECISION: Move to TSC |
| 336 | Telefónica | New API proposal: OGW Home Location Verification The API template is available in PR#337. Input from OGW Drop 3 | China Unicom and Telefonica to create a single family for both APIs: Location Insights, Use historical informations to manage location information of the user. TIM is supporting Home Location Verification but changing the name so to reach a wider scope.
The issue is not eligible to be closed yet. ACTION Jorge to reopen the PR#337 and change the Proposal name (Most Frequent Location) and add the new supporters (TIM) DECISION: Move to TSC |
| 351 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | The issue was not treated in this conference call
The issue is not eligible to be closed yet. |
| 367 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Progress ongoing, and offline discussion on RACI matrix to WoW among OGW Product, CAMARA APIBacklog and CAMARA TSC. PR pending submission. The RACI was presented to the TSC and there was no objection anyhow explicit approval is not reflected in the TSC Minutes 21/03 This way of work have been firstly adopted by the QoD subgroup which is proposing a scope change in the Working Group issues (#404 and #403) which may be treated in the next conference call The issue is not eligible to be closed yet. |
| 372 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
Integrate this API proposal in the existing ShortMessageService subproject to create this new family. ACTION: Ricardo propose this to SMS Sp owners before moving to tsc The issue is not eligible to be closed yet. |
| 375 | Deutsche Telekom | Device Quality Indicator | The issue was not treated in this conference call. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API DECISION: Move to TSC |
| 376 | Deutsche Telekom | Best Interconnection | The issue was not treated in this conference call. Noel aplogized in advance and suggested to wait till April first week TSC meeting to move on with this API DECISION: Move to TSC |
| 395 | TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML avaliable here | The issue was not treated in this conference call The issue is not eligible to be closed yet. |
...
| 378 | Charter Communications | CPE management | CPE Management API proposal was approved by TSC. Ricardo has to provide the CODEOWNERS and initial MAINTAINERS to the TSC. This have been provided within Issue#378_comment HomeDevicesQoD owners queried to have this API in a separated github project despite having regular meetings to align common terms (API Family). This involves having more than one CODEOWNER for this API (no further problem) DECISION: New github subproject to be created: Home Devices CPE Management |
| 383 | T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API intitial YAML files to be included in the API TEMPLATE The issue was not treated in this conference call |
...
| 397 | Netfocusin Technologies | New Proposal: Steering of Roaming Management | Does not seem to be in the Scope of Camara. DECISION: Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) |
Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240327-01 | Telefonica | Jorge to reopen the PR#337 and change the Proposal name (Most Frequent Location) and add the new supporters (TIM) | 336 |
| Open |
| 20240327-02 | Ricardo | Propose to SMS (ShortMessageService) Subproject-owners integrating ReceiveSMS API proposal in the existing SMS (ShortMessageService) Subproject to create a new API family before moving to tsc | 372 |
| Open |
Decision Points
| DP # | DP description | Related issue |
| 20240327-04 | Discuss this in the next meeting (whenever Netfocusin Technologies is able to connect) | |
| 20240327-03 | New github subproject to be created: Home Devices CPE Management | |
| 20240327-02 | Home Location Verification API proposal to move foward TSC as part of the LocationInsights API family and newly named after Most Frequent Location | |
| 20240327-01 | Device Visit Location API proposal to move foward TSC as part of the LocationInsights API family | |
| 20240314-01 | CPE management API proposal to move foward TSC | |
| 20240314-02 | Bring this issue to the TSC for approval as a new API subproject | |
| 20240222-01 | Device Quality Indicator to move foward to TSC for aproval (wait till April 4th) | |
| 20240222-02 | Best Interconnection to move foward to TSC for aproval (wait till April 4th) |
AoB
Next Backlog conf. call: 11th April, 10-11 CET.
Next TSC conf. call: 4th April, 11-12 CET
Q&A
How does CAMARA API pipeline work?
...