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 | |
PlektonLabs |
...
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 7th November:
...
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 Action: Clarifying with interested parties whether this may be a possible API or a Framework etc. AP: provide required information and examples MEETING UPDATE:Nick Venezia : Framework proposal including different APIs that may interact with existing ecosystem. Pending to provide info, work expected to be started in 1Q25 No 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 treatedNo update | |||||||||||
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 treatedNo update | |||||||||||
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) 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. Eric Murray asks for user stories that can explain the behaviour of the proposed API, as not clear how this interacts with the proper 5G New Calling standard and how it solves the features that are proposed. AP for Haojie Li https://github.com/camaraproject/WebRTC/issues/52 to discuss in WebRTC about relationship new information to be uploaded and treated in next session MEETING UPDATE: | Verizon | Device Management The API template is available PR#30No-one from China Mobile present. Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there. | |||||||||
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 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. Mahesh Chapalamadugu AP to upload documentation Slides presented by Mahesh Chapalamadugu & @joshua Slide will be uploaded and reviewed offline before approval MEETING UPDATE: No update | |||||||||||
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
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. @reg no further information from MTN, consider to de-prioritize, pending to further update Any other operator open to take the lead of this API is welcomed MEETING UPDATE: No update (pending) | |||||||||||
China Mobile | IP High-throughput Elastic Network The API template is available in PR#90 | Supporting document (presented) https://github.com/camaraproject/APIBacklog/raw/0a447dd4c53d0c675f8d72fc5622ff65eb48f7e3/documentation/SupportingDocuments/APIproposal_IP-high-throughput-elastic-network_ChinaMobile.pptx Jan Friman asked about the relation of this proposal with current CAMARA’s APis dedicated to network config (QoD, slice booking…). @qiuhai explained that this proposal is focused on enabling new network technologies like Srv6 Mark Cornall shared comments about the technology dependence on QoD solutions Kevin Smith & Jorge Garcia Hospital asked for more details on the difference with current proposals Pending review from Kevin about responses in the PR. Jorge Garcia Hospital raised concerns about technology dependancy in this API proposal MEETING UPDATE: | China Telecom | IoT SIM Status Mgmt API The API template is available in PR#105 | China Telecom | Relationship with device management proposal, to confirm relationship.Jianfeng Huang presented an update of the proposal. API will now be technology agnostic. Mark Cornall agrees with proposed modifications No other objections to modified proposal raised in the meeting AP: China Telecom MEETING UPDATE: | China Telecom | IoT SIM Fraud Prevention API The API template is available in PR#103 | IoT SMS send Mobile
DECISION: If update is done by end Friday , proposal can be put to to TSC meeting on Thursday for final approval. Otherwise will need to be meeting. | ||||
China Telecom | IoT SIM Status Mgmt API The API template is available in PR#104Jorge Garcia Hospital Mahesh Chapalamadugu requires to validate this proposal with existing SMS Send API https://github.com/camaraproject/ShortMessageService PR#105 | China Unicom | Relationship with device management proposal, to confirm relationship. AP: China Telecom MEETING UPDATE: | Verizon | Support application resource requirements in application profiles The API template is available in PR#110 | SIM Historical InformationMeeting considered that this proposal has some overlap with the Device Management proposal from Verizon APs: China Telecom
| |||||||
China Telecom | IoT SIM Fraud Prevention API The API template is available in PR#114 METING UPDATE: | China Unicom | User Account Spend Count The API template is available in PR#120 | China Unicom | Number Of Cards Under User's ID The API template is available in PR#119 | METING UPDATE:PR#103 | Jorge Garcia Hospital is it required to create a new set of APIs only for IoT devices or can they live in the existing groups? Eric Murray agrees, device status can take in charge of this new parameters, check first with this subgroup https://github.com/camaraproject/DeviceStatus MEETING UPDATE: Meeting agreed with China Telecom that this proposal does not fit within Device Status sub-project APs: China Telecom
| ||||||
China Telecom | IoT SMS send API The API template is available in PR#104 | Jorge Garcia Hospital Mahesh Chapalamadugu requires to validate this proposal with existing SMS Send API https://github.com/camaraproject/ShortMessageService AP: China Telecom MEETING UPDATE: Proposal to be withdrawn | |||||||||||
Verizon | Support application resource requirements in application profiles The API template is available in PR#110 | METING UPDATE: No update | |||||||||||
China Unicom | SIM Historical Information The API template is available in PR#114 | METING UPDATE: Eric Murray comment: Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project. APs: China Unicom
| |||||||||||
China Unicom | User Account Spend Count The API template is available in PR#120 | METING UPDATE: Use case appears to be a KYC use case APs: China Unicom
| |||||||||||
China Unicom | Number Of Cards Under User's ID The API template is available in PR#119 | METING UPDATE: Use case appears to be a KYC use case APs: China Unicom
|
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: TSC Decision: Ask to G. Murat Karabulut to provide some examples where this API will be useful. To be revisited during the after-next TSC meeting . | |||||
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:
| |||||
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: All ready, to be closed | |||||
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: Not treated | |||||
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: under discussion in I&CM | |||||
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: Group created, actions pending to be solved
| |||||
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 | |||||
Telefonica | Fixed Lines in Location The API template is available in PR#92 | METING UPDATE: Issue open in Carrier Billing https://github.com/camaraproject/CarrierBillingCheckOut/issues/190 | |||||
Telefonica | Line Eligibility for Carrier Billing API The API template is available in PR#94 | MEETING UPDATE: Issue open in location https://github.com/camaraproject/DeviceLocation/issues/271 |
...