2024-09-12 API backlog minutes
Attendees
Organization | Name |
Orange |
|
Charter Communications | @Christopher Aubut |
CableLabs |
|
Telefonica | @Ricardo Serrano Gutierrez @Jorge Garcia Hospital @patricia.serranogonzalez@telefonica.com Agustin Martin |
Vodafone | @Kevin Smith @Kevin Scarr |
Ericsson | @Thorsten Lohmar |
AT&T | @Pierre Close |
T-Mobile US |
|
KDDI |
|
Slagen |
|
Nokia | @Tanja de Groot |
China Telecom |
|
ZTE |
|
KPN |
|
GSMA | @Reg Cox @Mark Cornall |
Centilion |
|
Chunghwa Telecom |
|
Deutsche Telekom |
|
MTN |
|
China Mobile | @Lingli Deng @Keguang He @zhangruqian @Haojie Li |
Agenda Proposal
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
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
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
Centillion | New Proposal for Authorization for Advertisements, Advertisements Consent, and Measurement | 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. | |
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 | |
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:
| |
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. | |
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:
| |
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 | |
China Mobile | Knowledge Base - Manage |
MEETING UPDATE:
| |
China Mobile | Q&A Assistant - Manage |
MEETING UPDATE: | |
China Mobile | Q&A Assistant - Service |
MEETING UPDATE: |