2024-09-12 API backlog minutes
- Jorge Garcia Hospital
- Ben Hepworth
- Tanja de Groot
Attendees
| Organization | Name |
| Orange | |
| Charter Communications | Christopher Aubut |
| CableLabs | |
| Telefonica | |
| Vodafone | |
| Ericsson | Thorsten Lohmar |
| AT&T | Pierre Close |
| T-Mobile US | |
| KDDI | |
| Slagen | |
| Nokia | Tanja de Groot |
| China Telecom | |
| ZTE | |
| KPN | |
| GSMA | |
| Centilion | |
| Chunghwa Telecom | |
| Deutsche Telekom | |
| MTN | |
| China Mobile |
Agenda Proposal
- Antitrust Policy
- Approval of minutes of last conf. call
- Recent Updates & Recap
- Review of Action Points
- Discussion
OGW Drop #4 APIs: #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling), #63 (IMEI Fraud)
Other APIs: #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info), 68 (Resource URL) #83 #85 #86 #87 (Model as a Service)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
- Closing Issues
#20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #19 (Device Quality Indicator), #28 (Device Data Volume), #18 (Receive SMS), 70 (Quality by Design)
- AoB
- Q&A
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 (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
Approval of minutes of last conf. call
- Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 22th August:
- New repositories still to be created (by CAMARA Admins, not yet done):
- Device Quality Indicator (Sub Project DeviceStatus)
- Device Data Volume (Sub Project DeviceStatus)
- New proposal approved by API Backlog Working Group
- Subscription Status (Sub Project KnowYourCustomer), see message https://lists.camaraproject.org/g/tsc/topic/new_api_proposal_taken_for/108016665
- Provide information about active/inactive service subscription (voice/SMS/data for example) for a given mobile line
No objection from the TSC - Approved
- Subscription Status (Sub Project KnowYourCustomer), see message https://lists.camaraproject.org/g/tsc/topic/new_api_proposal_taken_for/108016665
TSC meeting 5th September:
- Patricia Serrano introduction - Patricia steps in for Ricardo. Welcome !
- Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus are created
- New API proposal brought to TSC: QualityByDesign
- See message https://lists.camaraproject.org/g/tsc/message/223
- Proposal supported by Charter, Liberty Global, Vodafone
- This API would be part of the Connectivity Insights API Family
- ... but separate repository
- API Proposal: Link
- Discussion on the name of the API - Chris Howell raised that Quality by Design is probably too marketing
- Consider to rename it.
- Herbert Damker Discussion an user story under this title make sense, but "QualityByDesign" will be a larger story, involving several APIs, including the QualityOnDemand family.
- Discussion about how the QoSscore could be computed
- Kevin Smith Research into the scoring (this is IETF, but also active in Broadband Forum via the Quality Attenuation standard): https://datatracker.ietf.org/doc/draft-olden-ippm-qoo/
- As of now QoSscore computing is not part of the API. This is an issue for Ludovic Robert Chris Howell - We need some uniformity to compute this. Kevin Smithagreed - data send back must be consistently across implementations.
- Next steps:
Do we create a repo with current name? or another name? QualityInsights? QualityAction?- TSC Proposal:
- Herbert Damker creates the repo QualityByDesign
- Ben Hepworth provides user story/ies, → AP
- (Project team) Discuss the concept & propose rename → AP
- (TSC) Adjust the name
Other topics
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress.
- Best Interconnect
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#79 (unmerged) New backlog table with reduction of columns
Discussion
Current Issues
| 17 | Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement The API template is available in PR#73. | 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. Pending to provide a concrete API description into the API proposal template MEETING UPDATE: Clarifying with interested parties whether this may be a possible API or a Framework etc. |
| 4 | Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) | PR is uploaded: New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog (github.com) PR to be checked and confirmed before issue can be closed MEETING UPDATE: Ricardo requests support for reviewing and make the PR ready |
| 23 | TelecomsXChange | New Proposal: Carrier Wholesale Pricing First YAML available here | The issue was not treated in this conference call The issue is not eligible to be closed yet. ACTION:Backlog Governance 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: Presentation for the API backlog may be done. China mobile took the point on reaching the correct team within their organization to come back to api backlog | |
Telefonica | New API Proposal: Telco Scoring The API template is available PR#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 API may fit within KYC API family → The issue was raised 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: Telefonica manage to find the support of VDF (Kevin confirmed in the chat also) and DT if no objections. The name should be readressed, Jorge was prposing Telco Index to avoid using legal restrictions for using words "Credit" and "Scoring". Nick propose Telco Trust → Discussing this in the issue ofline. Tanja (note in chat on behalf of Release Mgmt): Reminder to not use Telco specific terms in API names. To avoid: Telco, operator, CSP, subscriber, customer, EMEI, UE, etc. | |
Verizon | Device Management The API template is available PR#30 | The issue was not treated in this conference call The issue is not eligible to be closed yet. Action to contact Verizon to ensure participation in next backlog meeting MEETING UPDATE:
| |
Ericsson | New API proposal-Dedicated Networks The API template is available PR#59 | Thorsten presented the proposal: Material here
There have been a similar work in a TMF API. Pierre offered himself to Thorsten to reach up DECISION New repo/subproject to be created and a family that groups both NSB and DN ACTION Telefonica providing comments this afternoon and moving to TSC → Action complete Comments from TEF addressed in Issue PR#60 ACTION: Eric to check with Miranda in Issue PR#60 if her preference is for separate sub-projects, or for DN to join NSB sub-project No response regarding this, pending to response MEETING UPDATE: Discussion regarding separate or not separate repos. Telefonica supports having separate repos but having the conversation in the same forum as part of a unified family DECISION: Move to tsc taking care of this comment and expecting the administrative work to be clarified there. Someone for NSB group (Huawei, China etc.) should be connecting tsc that day at least to be aware of this ACTION: Thorsten to reach up NSB group by it mailing list proposing to join the TSC meeting. Next TSC meetings: 19/09/24 at 16:00 CEST / 14:00 UTC / 07:00 PST 03/10/24 at 10:00 CEST / 08:00 UTC / 01:00 PST | |
Vodafone | Scope Enhancement for Network info The API template is available PR#72 | 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 → Kevin opened PR#72 to complement Issue PR#66. Both still open. Noel commented that this is likely to be accepted New repository is likely to be required Comments have been provided in the issue
MEETING UPDATE: Conversation have been taken out. Not sure about the conclusion. To be treated in the next backlog meeting. Kevin is reaching out the team that is aware of the final decision withn DS | |
MTN | New API proposal - IMEI Fraud The API template is available PR#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 IMEI Fraud will offer more information to developers than GSMA Device Check service. MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense. Request for meeting already sent by GSMA to MTN Outcome of meeting awaited before deciding if this API proposal should proceed in CAMARA
MEETING UPDATE:
| |
Telefonica | New API proposal - Consent URL The API template is available PR#67 | The API proposal was presented, including additional slide info Discussion to follow offline in the issue/PR.
MEETING UPDATE: Consent management is not clear yet. Continue with the conversation. Suggestion to reach up TMUS. | |
| 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. DECISION API to be de-prioritised following de-prioritisation by OGW, but to remain in backlog. Issue to remain open. MEETING UPDATE:
|
| 83 | China Mobile | Model As A Service Family | China Mobile presented the API MEETING UPDATE: Nokia: on the name, as there are many types of models should the name be made more explicit, e.g. LLMaaS ? Seems to be mor of a data model as a service. Not using the API to collect data, it is just part of the |
| 85 | China Mobile | Knowledge Base - Manage | MEETING UPDATE: |
| 86 | China Mobile | Q&A Assistant - Manage | MEETING UPDATE: |
| 87 | China Mobile | Q&A Assistant - Service | MEETING UPDATE: |
Closing Issues
| 22 | T-Mobile US | Capability and Runtime Restrictions | It was accepted by the TSC to treat this as a new API Initial YAML files to be included in the API TEMPLATE MEETING UPDATE:
|
| 18 | 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:
|
| 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 committed 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 (SubscriptionStatus) The API template is available in PR#32 | DECISION Separate Repos should be created but same family (KYC) in order to have coordination meeting Pending to confirm codeowner/maintainers for repo creation, email sent Included in today's TSC approval. | |
KDDI | Number Recycling The API template is available 55 | Pending Codeowners and maintainers (requested in comment) | |
Cablelabs | Proposal is that QbD be a scope enhancement to Connectivity Insights Will likely require new API, hence new repository required QdD supporters will attend Connectivity Insights meeting next week to finalise proposal Awaiting outcome of Connectivity Insights meeting before finalising if new repository required MEETING UPDATE:
DECISION :
CableLabs cannot attend this APIBacklog meeting, but the notes above accurately describe the outcome of the TSC last Thursday. Repo still not created, but we can either close this issue now or close it once Herbert creates the repo. -Ben Hepworth |
Review of Action Points
| AP # | AP Owner | AP description | Related issue | Due date | Status |
| 20240523-01 | API Backlog Governance | Backlog Governance to reach up TelecomXchange & Verizon to see if the could connect next meetings | 23 50 | 23/05/2024 | Open |
|
(SUPPORT SEEKING ACTIONS ARE NOT FOLLOWED AS AP ANYMORE, ONLY AS OPEN DISCUSSIONS) | Discarded | |||
| 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-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: N/A, AP to be closed (updated in AP20240912-01) | 70 | 08/08/2024 | Closed |
| 20240808-01 | Ericsson | Dedicated Networks: Eric to check with Miranda in Issue #60 if her preference is for separate sub-projects, or for DN to join NSB sub-project
Meeting Update: | 60 | 08/08/2024 | Open |
| 20240822-01 | Telefonica | Consent URL API: Discussion to follow offline in the issue/PR around Consent URL API use cases/user stories
| 68 | 08/22/2024 | Open |
| 20240822-02 | Vodafone | Scope Enhancement for Network info: Kevin opened PR#72 to complement Issue 66. Both still open about destination of API
| 66 | 08/22/2024 | Open |
| 20240912-01 | Cablelabs | QualityByDesign:
| 70 | 09/12/2024 | Open |
|
Decision Points
| DP # | DP description | Related issue |
AoB
Next Backlog conf. call: 26th September, 15-16 CET/UTC+2.
Next TSC conf. call: 19th September, 16-17:30 CET/UTC+2
Q&A
How does CAMARA API pipeline work?
The pipeline consists of FOUR stages:
A. Submission of the API proposal.
B. Evaluation of the API proposal.
C. API proposal voting & decision.
D. Sub-Project setup.
The following clauses provides details on individual stages.
Stage A: Submission of the API proposal
Participants: API owner.
Description: The process is detailed here. To proceed with the submission, the API owner shall follow these steps:
- Fill in the template available here and save it with the following name: "APIproposal_<APIname>_<owner>. md" locally.
- Create a new issue in the API Backlog Working Group repository, labeled with "API Backlog".
- Upload the filled-in template to GitHub repository folder for API proposals via Pull Request. This Pull Request shall be associated to the issue created in the previous step.
Stage B: Evaluation of the API proposal
Participants: API owner, API backlog WG.
Description: The process is detailed here. Upon submission, the API owner will present the proposal in the next API backlog WG meeting, to socialize it with the rest of partners. In parallel..
- The WG chair checks that the template is duly filled in. Otherwise, the API owner is requested to provide missing information.
- After this sanity check, each WG participant declares their support. If a company wants to become supporter of an API, then a delegate of this company needs to add the company's name in the 'supporters' column in the API backlog table. The more support an API proposal gets, the better (it may get more traction).
- When the API owner considers the API proposal is in good shape to go for approval, it informs the WG chair accordingly.
- Upon receiving this information, the WG chair merges the Pull Request into the main branch, and sends the API proposal to the Technical Steering Committee (TSC) of CAMARA. This action shall be completed at least one week prior to the TSC meeting where the API proposal will be voted upon.
The whole procedure (steps 1-4) should be done within 2 regular meetings of the API Backlog WG. Nonetheless, it is up to the API owner to decide if it wants to shorten or extend this time period.
Stage C: API proposal & voting decision
Participants: TSC.
Description: The process is detailed here. Upon receiving the API proposal and notification from the API backlog WG chair, the TSC studies the proposal and votes it at the next TSC meeting.
NOTE 1: Possible decisions outcomes:
- Not Accepted: The API proposal is rejected, and thus will not be included in any API Sub-Project. The TSC will need to inform the API backlog WG of this decision, and clarify next steps: either (1) remove this API proposal from backlog, with objecting companies providing justifications why; or (2) ask for changes (e.g., clarifications, corrections, gaps to be addressed) required in order for the API to be re-submitted by the API supporters.
- Accepted: In this case, the TSC shall specify whether the API proposal is to be hosted by a new or existing Sub Project.
NOTE 2: The TSC may also propose changes to an API proposal and take the decision considering these changes. The TSC documents the decision in the CAMARA API overview list (fills in columns TSC date and TSC decision / Sub Project; in case of a No-Go "Rejected" is documented there).
Stage D: Sub-Project setup
Participants: API backlog WG, TSC, CAMARA admin team
Description: If an API proposal is accepted and there is a need to open a new Sub-Project, the following steps are needed:
- Supporting companies propose their initial maintainers to be added for the Sub-Project. The API backlog WG chair centralizes this information, and sends it to the TSC.
- The TSC will use this input to officially nominate the initial maintainers by next TSC meeting.
- The CAMARA admin team creates the Sub-Project repository.
NOTE: After the initial maintainers are nominated, the criteria for further maintainers would be three months of active contribution to the sub project. Code owners are to be decided by the maintainers within the subproject.