...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees
Organization | Delegates |
---|---|
China Unicom | Yan Fang |
China Telecom | Dan Xu |
Deutsche Telekom | Noel Wirzius |
Ericsson | Jan Friman |
GSMA | Mark Cornall |
Huawei | Zhang Kai, Shuting Qing |
Infosys | Chintan Lodariya |
KDDI | Toshi Wakayama |
Orange | Ludovic Robert |
Telecom Italia | Fabrizio Moggio |
Telefónica | Jose Ordonez-Lucena, Jorge García Hospital |
Vodafone | Eric Murray, Kevin Smith |
...
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
- 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
Recent Updates & Recap
- Minutes of last API backlog WG call available here
- Last TSC call held on Dec 21st. Minutes available here. Key takeaways:
- Population Density Data (replaces "Dynamic People Density Information") API proposal was approved, after backlog WG took required action.
- Short Message Service (replaces "Send SMS") API proposal was approved, after backlog WG took required action.
- Decision about names & maintainer lists for already approved sub projects will be taken in lazy consensus if there there are no objections or additional nominations on the TSC mailing list within 48 hours.
- New repos:
- RegionUserCount Sub-Project is up and running → issue 328 is closed
- PopulationDensityData Sub-Project is up and running → issue 334 is closed
- ShortMessageService Sub-Project is up and running -> issue 352 is closed
Review of Action Points
AP | Owner | Description | Issue | Due Date | Status |
---|---|---|---|---|---|
20231214-01 | Orange | Address received comments on Device Location Retrieval in in PR#366 | 2024/01/10 | Closed |
Discussion
Current Issues
Issue | Owner | Description | Discussion |
---|---|---|---|
317 | China Unicom | New Proposal: Network Slicing API | Progress offline in the PR thread since last conf. call. Huawei presented a deck (c.f. slides 11-14) shedding light on the open questions raised by delegates with regards to:
Further questions were raised calling for clarifications on how API logic on other scenarios (access control, user provisioning and resource guarantees).
API owner asked the WG to endorse the API proposal. No objections were raised, but API owner was asked to update the API template before sending it out to the TSC. GSMA (Mark Cornall) also noted that the API definition should align with current GSMA OPG/OPAG activities.
The issue is not eligible to be closed yet. |
330 | China Unicom | New API proposal: Device Visit Location The API template is available in PR#329 | The issue was not treated in this conf. call. Awaiting for GSMA-TSC mails, with global privacy group of Open Gateway involved as well.
The issue is not eligible to be closed yet. |
336 | Telefónica | New API proposal: OGW Home Location Verification The API template is available in PR#337. Input from OGW Drop 3 | No progress since last conf. call.
The issue is not eligible to be closed yet. |
343 | Orange | New API proposal: Device Location Retrieval The API template is available in PR#366. Input from OGW Drop 3 | Orange updated the API template, according to the comments received in last conf. call. Further clarity on the new feature proposed for inclusion in the Device Location family.
Ludovic asked the WG to endorse the API proposal. No objections were raised.
The issue is eligible to be closed. |
351 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#350. | No delegate from Centillion attended. The issue was not treated in this conf. call. |
359 | Telecom Italia | New API proposal: Call Forwarding Signal | Progress offline in the PR thread since last conf. call. API supporters: the API needs a supporting company other than TIM (owner).
API scope: The scope (mobile-only or mobile+fixed) needs to be agreed for this API. While we have quorum on the need for mobile domain to be included in the scope of the original API, there is no consensus on the fixed domain.
The API proposal is not ready for WG endorsement. The issue is not eligible to be closed yet. |
Closed Issues
Issue | Owner | Description | Discussion |
---|---|---|---|
328 | China Unicom | New Proposal: Region User Count | Sub-Project is up and running |
334 | China Unicom | New API proposal: Device Visit Location The API template is merged, available here Input from OGW Drop 3 | Sub-Project is up and running |
352 | Telefónica | New API proposal: OGW Home Location Verification The API template is merged, available here Input from OGW Drop 3 | Sub-Project is up and running |
...
Issue | Owner | Description | Discussion |
---|---|---|---|
367 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | The issue was not treated in this conference call. ACTION: Jose (Telefónica) to open a new PR to address this issue. |
372 | New Proposal: Receive SMS No PR available. | The issue was not treated in this conference call. |
Action Points
AP | Owner | Description | Issue | Due Date | Status |
---|---|---|---|---|---|
20240111-04 | Telefónica | Open a new PR to update governing document for API submission pipeline | 2024/02/15 | Open | |
20240111-03 | WG operators | Post position on what the scope (mobile-only or mobile+fixed) of "Call Forwarding" API should be | 2024/01/24 | Open | |
20240111-02 | China MobileUnicom, Orange | Submit PRs for their companies to become supporters of the Call Forwarding API | 2024/01/24 | Open | |
20240111-01 | China MobileUnicom | Update the API template on Network Slicing, clarifying the issues covered in the deck and questions covered in the call. | 2024/01/12 | Open |
AoB
Next conf. call: 25th January, 15-16 CET.
Q&A
How does CAMARA API pipeline work?
...