DRAFT MINUTES
...
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: APPROVED
Recent Updates & Recap
TSC meeting 1st August:
...
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.
Backlog table
- Table updated in PR#62 (merged)
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240523-01 | API Backlog Governance | Ricardo to reach up TelecomXchange, Totogi and Netfocusin Technologies to see if the could connect next meetings | 23 18 24 | 23/05/2024 | Open |
| 20240523-07 | DT | Best interconnection: Review whether there is overlap with EdgeCloud subproject Meeting Update:
| 20 | 23/05/2024 | Completed |
| 20240627-01 | China Unicom, KDDI, Vodafone, DT | Check whether Tenure + Shutdown service + Number recycling fit in KYC (parts involved align internally) Closed for Tenure and Number Recycling (accepted and repo created) Shutdown Service pending to create repo. Codeowners to be required by email (China Unicom, China Telecom, Huawei) and reported to TSC. Meeting Update:
| 54 2 34 | 28/06/2024 | Completed |
| 20240627-02 | API Backlog Governance | New use cases are usually proposed. Modify the Scope template to show this and approve | 53 | 28/06/2024 | Completed |
| 20240711-01 | Netfocusin Technologies | Seek for support/commitment from the partners (technical implementation approach important) | 24 | 11/07/2024 | Open |
| 20240711-02 | Telefonica | Provide comments for dedicated network | 60 | 11/07/2024 | Completed |
| 20240711-03 | Vodafone | Create the template for network info | 61 | 11/07/2024 | Completed |
| 20240711-04 | MTN/Chenosis | IMEI Fraud: Check the material shared by Eric/GSMA regarding DeviceCheck, and validate the inclusion of the API in the Device Identifier group Meeting Update:
| 63 | 11/07/2024 | Open |
| 20240801-01 | Deutsche Telekom | Device Quality Indicator: To provide list of Maintainer/Codeowner Meeting Update:
| 19 | 16/08/2024 | Completed |
| 20240801-02 | Deutsche Telekom | Device Data Volume: To provide list of Maintainer/Codeowner Meeting Update:
| 16/08/2024 | Completed | |
| 20240801-03 | China Unicom | Shutdown ServiceStatus: To provide list of Maintainer/Codeowner Meeting Update:
| 16/08/2024 | Completed | |
| 20240801-04 | Vodafone | Scope Enhancement for Network info: To clarify if new API is proposed in the Device Status Family or it's an enhancement over an existing API. To clarify it's relationship with Open Gateway Telco Finder API. Meeting Update: | 61 | 08/08/2024 | Open |
| 20240801-05 | Cablelabs | Quality by Design: Clarification pending on the differences with current Mobile/Fixed QoD and Network info / Quality indicator APis / Connectivity Insights Meeting Update:
| 70 | 08/08/2024 | Open |
Discussion
Current Issues
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#386. | 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. |
MEETING UPDATE:
| |||
| 4 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | Ricardo is currently working on modeling a new table Struggling with the new Table model. Bring the PRs from the old repo Makes sense to bring the table to confluence? GitHub seems to be more accesible and is visited by further people (devs. etc.) The issue is not eligible to be closed yet. |
MEETING UPDATE:
| |||
| 23 | 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. ACTION: Ricardo to reach up TelecomXchange to see if the could connect next meetings |
MEETING UPDATE:
| |||
| 24 | Netfocusin Technologies | New Proposal: Steering of Roaming Management | 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:
|
China Mobile | 5G New Calling The API template is available PR#31 | Not treated 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) Pending to clarify scope with VerifedCaller |
MEETING UPDATE:
| |||
Telefonica | New API Proposal: Telco Scoring The API template is available #42 Input from OGW Drop 4 | Presented slides: API-Overview-TelcoScore.pptx The API seems to not fit within KYC and new sg should be created. Support is required, feel free Scoring can be calculated both with any user registered in the telco. Less information means less scoring, Algorithm may be different for each of the implementators (MNO) ACTION: Toshi validate if This APImay fit within KYC API familiy → The issue was rised but still under discussion →(Toshi's proposal 20240627) In API Backlog 20240613 meeting, Jorge TEF and Toshi KDDI agreed that the API does not fit within the existing KYC-SP. Then, in KYC-SP 20240625 meeting, that was shared within KYC-SP and there was no objection. Closed. Pending meeting with DT to seek for support. ACTION Noel to come back to TEF |
MEETING UPDATE:
| |||
Verizon | Device Management The API template is available #30 | The issue was not treated in this conference call The issue is not eligible to be closed yet. |
MEETING UPDATE:
| |||
Ericsson | New API proposal-Dedicated Networks The API template is available #59 | Thorsten presented the proposal: Material here
There have been a similar work in a TMF API. Pierre offere himself to Thorsten to reach up DECISION New repo/subproject to be created and a family that groups both NSB and DN |
|
Vodafone | Scope Enhancement for Network info | Seems that Connectivity Insigts is more suitable as there is already work done in the Device Status regarding connection status. As there is more alike a device centric information maybe fits better in device status. Connectivity insights is more focused in the network status As it could be used in both of the contexts a new API may be the best option. DECISION: There is not such a big change for DS subproject so scope could be enhanced and new repo created within the same Device status family
|
To clarify if new API is proposed in the Device Status Family or it's an enhancement over an existing API. To clarify its relationship with Open Gateway Telco Finder API. MEETING UPDATE:
|
MTN | New API proposal - IMEI Fraud The API template is available #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 ACTION |
Chenosis Check the material shared by Eric/GSMA regarding DeviceCheck VDF propose to include it under Device Identifier group, to be validated by Chenosis/MTN MEETING UPDATE:
| |||
Telefonica | New API proposal - Consent URL The API template is available #67 | The API proposal was presented, including additional slide info Discussion to follow offline in the issue/PR. MEETING UPDATE:
| |
Cablelabs | New API being proposed to allow 3rd party applications to interact with the access network. |
|
Closing Issues
MEETING UPDATE:
| |||
| 20 | Deutsche Telekom | Best Interconnection | 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. MEETING UPDATE: |
DECISION API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open. |
Closing Issues
| 22 | T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API intitial Initial YAML files to be included in the API TEMPLATEThe issue was not treated in this conference call MEETING UPDATE:
|
| 18 | Totogi | New Proposal: Receive SMS The API template is available in PR#391 |
Seems to fit in the SMS as a new scope enhancement The issue is not eligible to be closed yet. ACTION: Ricardo to formaly proceed with the scope enhancement os the SMS group MEETING UPDATE:
|
| 19 | Deutsche Telekom | New Proposal: Device Quality Indicator | Noel proposed Device Status subgroup to integrate their APIs within Noel's. Noel to make the proposal to the API Backlog and provide update Two proposals Issue 19 and 28 would be integrating within the Device Status subproject The subgroup people is okay with this The issue is not eligible to be closed yet. Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue, Vodafone commited and a third supporter is being queried) Both issue 19 and 28 to the DeviceStatus family and separate repositories (deviceStatus) → Device Quality Indicator DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status) DECISION There is agreement Orange, DT and VDF, next backlog meeting there should be the outcome for this issue Pending to confirm codeowner/maintainers for repo creation, email sent MEETING UPDATE: |
Deutsche Telekom | New API Proposal: Device Data Volume New template in PR#39 | Move to TSC, check wether there is support for this API (Interested parties provide comments in the Issue) Both issue 19 and 28 to the DeviceStatus family and separate repositories (deviceStatus) → Device Data Volume DECISION formal agreement from the Device Status subgroup is required. To be treated in next meeting (Device Status) DECISION There is agreement Vonage, DT and VDF, next backlog meeting there should be the outcome for this issue Pending to confirm codeowner/maintainers for repo creation, email sent MEETING UPDATE: | |
China Unicom | New API Proposal: Shutdown ServiceStatus The API tempate is available in PR#32 | DECISION Separate Repos should be created but same familiy (KYC) in order to have coordination meeting Pending to confirm codeowner/maintainers for repo creation, email sent MEETING INVITE: |
Closed Issues
| Issue | Owner | API | Repository |
China Telecom | Verified Caller | VerifiedCaller | |
Vodafone | Tenure | Tenure | |
| 37 | Vodafone | Move Simple Edge Discovery to own repository | |
API Backlog | Scope Enhancement Template The API template is available #52 | N/A | |
KDDI | Number Recycling The API template is available 55 | ||
Telefonica | Scope Enhancement: KYC-Match API -Scoring logic The API template is available #46 |
Decision Points
| DP # | DP description | Related issue |
| 20240711-01 | Formal agreement from the Device Status subgroup is required for Device Data Volume and Device Quality indicator. To be decided in next API Backlog Meeting | |
| 20240711-02 | Shutdown Service: Separate Repos should be created but same family (KYC) in order to have coordination meeting | |
| 20240711-03 | Number recycling has enough support, move to TSC. Proposal is to be in the same KyC family but separate repos | 54 |
| 20240711-04 | Dedicated Networks: Proposal is to have separate repos/subproject yet, this needs to be addressed | 60 |
AoB
Next Backlog conf. call: 22th August, 15-16 UTC+2.
Next TSC conf. call:22th August, 16:30 UTC+2
Q&A
How does CAMARA API pipeline work?
...