DRAFT MINUTES
Attendees
Organization | Name |
Orange | |
Charter Communications | |
CableLabs | |
Telefonica | |
Vodafone | |
Ericsson | |
AT&T | |
T-Mobile US | |
KDDI | |
Slagen | |
Nokia | |
China Telecom | |
ZTE | |
KPN | |
GSMA | |
Centilion | |
Chunghwa Telecom | |
Deutsche Telekom | |
MTN | |
China Mobile | |
Verizon |
...
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), #50 (Device Management), #63 (IMEI Fraud), #83 #85 #86 #87 (Model as a Service), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API)
Other APIs: #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #89 (IP High-throughput Elastic Network)
Governance: #4 (Structures and roles, RACI, Maintainers initiative)
Closing Issues
AoB
Q&A
...
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 19th September03rd October:
Repository for QualityByDesign DedicatedNetwork created (as decided last meeting), TelcoIndex naming still under discussion along supporters.
New API proposal proposals brought to TSC (2):
See
informative message https://lists.camaraproject.org/g/tsc/message/
TelcoIndex API
Supported by Telefonica, DT, Vodafone
API proposal: Link
Discussion:
Naming discussion: https://github.com/camaraproject/APIBacklog/pull/42#issuecomment-2348157633
Decision: Start this API in sandbox (repo) and then work on the name
Jorge Garcia Hospital propose first to ask to supporter companies if OK to start with this name.
Axel.Nennker@telekom.de explained that for DT the term risk indicator was used. The use of score term is very risky (from regulation). We must be clear that it will not be used to discriminate people. If it based on AI model, the model must be shared to allow people to challenge it.
Dedicated Networks API
Supported by Ericsson, Nokia, Telefonica, Vodafone
API proposal: Link
Decision : Start the work in a sandbox (repo) and then with provided assets check/reassess collision/overlap with other CAMARA API (like network slicing booking API but other APIs could be affected)
Scope Enhancement for Network info:
Supported by Vodafone and DT. Filled template: link. Original issue: 66.
Meant for including more information on current Device Status API, including Network Type (e.g.2/34G, 5GNSA/SA, non-3GPP..)
Decision: Not for decision, only informative as already agreed in both backlog and subproject. Already included into Device Status group scope, as agreed in issue 143 and PR 8.
Consent URL API:
Supported by Telefonica and KPN. Filled template: link. Original issue: 68. Additional material:
linkView file name Out_of_Band Consent Capture URLv2 (6).pptx Meant for providing an out-of-band consent gathering mechanism that can be triggered in a separated moment (apart from API authentication phase) and in an arbitrary device (not only the API-targeted device), enhancing current mechanisms tied to Authcode or CIBA token flows.
Discussed with ICM work Group in particular to define the relationship between this API & ICM
Decision: (not to be treated as no all the affected participants can attend today)
Other topics
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3 3/4 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
...
(new) Sandbox proposal from TSC to speed-up the inclusion of new APIs into CAMARA, fostering the development of new APIs and the finalization of API scope definition.
Draft proposalhttps://github.com/camaraproject/Governance/pull/161
Backlog table
Table updated in PR#79 (unmerged) New backlog table with reduction of columns → All reviews are welcomed
Discussion
Current Issues
Issue #
Company
Summary
Status Update
T-Mobile US
Capability and Runtime Restrictions
The API template is available in PR#74
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:
Clarifications will be provided by Murat.
Intended to cover these slides but time ran out:
and request ‘sandbox creation’. Will update the Issue #22 accordingly.View file name Capabilities_and_Runtime_Restrictions_Update.pptx
Totogi
New Proposal: Receive SMS
The API template is available in PR#75
20240327-02 was completed. Herbert responded but not the subgroup owners, no activity seems to had happened for a month: Issue #9 · camaraproject/ShortMessageService
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:
Reminder sent
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.
MEETING UPDATE:
Additional codeOwner required
KDDI
Number Recycling
The API template is available 55
Pending Codeowners and maintainers (requested in comment)
MEETING UPDATE:
First initial list included, pending only participants from DT
Cablelabs
New API proposal - Quality by Design
The API template is available #71
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
New repo to be created (new separated API) but included into the existing Connectivity insights family. To be confirmed base on the last meeting minutes. As soon as clarified, it will be included in next TSC
DECISION :
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
MEETING UPDATE:
Repo created
Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion
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.
MEETING UPDATE:
API approved, repo will be created after final name is proposed by the group (email sent)
Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion
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
MEETING UPDATE:
API approved, repo to be created
Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion
Issue # | Company | Summary | Status Update | |||
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 UPDATEAction: Clarifying with interested parties whether this may be a possible API or a Framework etc. MEETING UPDATE: | ||||
Governance | Adapt Project StructuresAndRoles.MD to changes in API backlog table (reduction of comments) The aim is to update the governing document to reflect on the updated changes on API submission pipeline, according to the new structure of the API backlog table. | 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 UPDATEAction: Partners to review and validate MEETING UPDATE: | ||||
TelecomsXChange | New Proposal: Carrier Wholesale Pricing The API template is available in PR#77 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: Not treated | ||||
Netfocusin Technologies | New Proposal: Steering of Roaming Management The API template is available in PR#78
| 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:Not treated | ||||
China Mobile | 5G New Calling The API template is available PR#31 | 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 of current proposal was shared in the meeting. Slides to be included in PR#31. G. Murat Karabulut asked about the proposal been part of WebRTC enhancement or new API → new API. Eric Murray asked about examples of 3rd parties in this API flow → app invoquing API to request or activate features, which can be enabled or not by the telco. Mark Cornall raised the existance of a 5G New Calling project in GSMA: https://www.gsma.com/get-involved/gsma-foundry/5g-new-calling/ & 5GNCTF Meeting#1 ACTION: Operators open to comment/ask for clarification and support the API. MEETING UPDATE: | ||||
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: API proposal presented by Mahesh Chapalamadugu , clarified this proposal is targeted for IoT device management to activate/deactivate/manage the connection of those devices. ACTION:Mahesh Chapalamadugu to upload current yaml for clarification in PR#30, and present again in next meeting. | Vodafone | Scope Enhancement for Network infoMEETING UPDATE: | ||
MTN | New API proposal - IMEI Fraud 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: Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143 Enhancement proposal to be updated by Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. | ||||
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: Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. Waiting for MTN for moving on with this API. Maybe to be included in the Device Identifier family.
| ||||
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: Huub Appelboom supports API proposal G. Murat Karabulut previously raised some concerns but seem clarified with last documentation. (uploaded in API PR#67 and also direct link) Proposal to be brought to TSC if no other concern is raised before end of week. | Deutsche Telekom | 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 | China Mobile presented the API MEETING UPDATE: To include support from ZTE and Huawei. Proposals in good shape for been moved to TSC approval, Haojie Li asked for one additional round for more clarifications and comments.
| China Mobile |
MEETING UPDATE:
| China Mobile |
MEETING UPDATE: | China Mobile |
MEETING UPDATE: |
China Mobile | IP High-throughput Elastic Network The API template is available in PR#90 | Not to be treated in this meeting. |
Closing Issues
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
Eric Murray : (IMEI status) service related, but GSMA is ok for this proposal. ACTION: Pending from MTN for moving on with this API. Maybe to be included in the Device Identifier family. MEETING UPDATE:
| ||
Deutsche Telekom | Best Interconnection The API template is available in PR#88 Input from OGW Drop 3 | 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 The API template is available in PR#84 - MaaS (Model As A Service) Family | China Mobile presented the API ACTION: To include support from ZTE and Huawei. Proposals in good shape for been moved to TSC approval, Haojie Li asked for one additional round for more clarifications and comments. MEETING UPDATE: | |
China Mobile | Knowledge Base - Manage The API template is available in PR#84 - Knowledge Base - Manage |
As per 83
| |
China Mobile | Q&A Assistant - Manage The API template is available in PR#84 - Q&A Assistant - Manage |
As per 83 | |
China Mobile | Q&A Assistant - Service The API template is available in PR#84 - Q&A Assistant - Service |
As per 83 | |
China Mobile | IP High-throughput Elastic Network The API template is available in PR#90 | METING UPDATE: | |
Telefonica | Fixed Lines in Location The API template is available in PR#92 | METING UPDATE: | |
Telefonica | Line Eligibility for Carrier Billing API The API template is available in PR#94 | METING UPDATE: |
Closing Issues
Issue # | Company | Summary | Status Update | ||||
T-Mobile US | Capability and Runtime Restrictions The API template is available in PR#74 | 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:
| |||||
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:
| |||||
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. ACTION Pending to validate remaining codeOwner MEETING UPDATE: | |||||
KDDI | Number Recycling The API template is available 55 | Pending Codeowners and maintainers (requested in comment) MEETING UPDATE: Group created and participants included, issue to be deleted. → PR merged | |||||
Cablelabs | New API proposal - Quality by Design The API template is available #71 | 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
DECISION :
MEETING UPDATE: Group created and participants included, issue to be deleted. → PR to be merged | |||||
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 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. Pending:
MEETING UPDATE: Pending to confirm codeowner/maintainers for repo creation, email sent and issue in discussion | |||||
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 Pending: Codeowners and Maintainers to be included MEETING UPDATE: Group created and participants included, issue to be deleted. → PR to be merged | |||||
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
Device status WG, as part of Device status reachability, considered this enhancement. Device Status Issue143 Pending: Enhancement proposal to be updated by Kevin Smith according to final scope agreed in Device Status group, TSC to be informed about final decision. MEETING UPDATE: As all solved, issue to be deleted → PR to be merged | |||||
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.
Huub Appelboom supports API proposal G. Murat Karabulut previously raised some concerns but seem clarified with last documentation. (uploaded in API PR#67 and also direct link) Pending: Proposal to be brought to TSC if no other concern is raised before end of week. MEETING UPDATE: | |||||
Review of Action Points
AP # | AP Owner | AP description | Related issue | Status |
20240523-01 | API Backlog Governance | Backlog Governance to reach up TelecomXchange & Netfocusin to see if the could connect next meetings | Open | |
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: | 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: Closed as per issue update | 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: Closed as per issue update | Closed | |
20240822-01 | Telefonica | Consent URL API: Discussion to follow offline in the issue/PR around Consent URL API use cases/user stories
Meeting Update: Closed as per issue update | Closed | |
20240822-02 | Vodafone | Scope Enhancement for Network info: Kevin opened PR#72 to complement Issue 66. Both still open about destination of API
Meeting Update: Closed as per issue update | Closed | |
20240912-01 | Cablelabs | QualityByDesign:
| Open | |
20240926-01 | Telefonica | Telco Scoring
| Open | |
20240926-02 | Ericsson | Dedicated Networks
| Open | |
20240926-03 | China Mobile | 5G New Calling
| Open | |
20240926-04 | Verizon | Device Management
| Open | |
20240926-05 | Vodafone | Scope Enhancement for Network info
| Open |
...
Proposal to extend meeting half hour (1:30 total) to accomodate all new APIs and also the track of existing.
@all to comment
Next Backlog conf. call: 10th 24th October, 1015-11 CET16 CET/UTC+2.
Next TSC conf. call: 3rd 17th October, 1016-1117:30 CET/UTC+2
Q&A
How does CAMARA API pipeline work?
...