...
...
...
...
Attendees
Organization | Name |
Orange | |
Charter Communications | |
CableLabs | |
Telefonica | |
Vodafone | |
Ericsson | |
AT&T | |
T-Mobile US | |
KDDI | |
Slagen | |
Nokia | |
China Telecom | |
ZTE | |
KPN | |
GSMA | Reg Cox Mark Cornall |
Centilion | |
Chunghwa Telecom | |
Deutsche Telekom | |
MTN | |
China Mobile | @yinming Fu |
Verizon | |
PlektonLabs | |
TIM | fabrizio moggio Antonio Varvara |
...
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 (9-10:30 UTC)
4th Thursday of the month (15-16:30 UTC)
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.
New API proposals are included in backlog table when template PR is created, linking to the pending PR
PR will be merged as soon as ready for TSC, and should be merged before TSC review
API enhancements requires existing group’s validation. TSC is informed accordingly to validate
Link and status in backlog table will be updated accordingly
Issue to track API onboarding will be opened once new API is confirmed in TSC.
Approval of minutes of last conf. call
...
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 yetApproved for Sandbox repository Follow-up on API onboarding: | ||||||||||||||
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 ScoringDeutsche Telekom | Best Interconnection The API template is available PR#42available in PR#88 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 Interconnection3 | 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 | ||||||||||||||||
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#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 | China Mobile | 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 |
As per 83
| China Mobile |
As per 83 | China Mobile |
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 PR#94 | MEETING UPDATE: Issue open in location https://github.com/camaraproject/DeviceLocation/issues/271 | |||||||||||||||
China Mobile | IP High-throughput Elastic Network The API template is available in PR#90 | Approved for Sandbox repository Follow-up on API onboarding: https://github.com/camaraproject/APIBacklog/issues/133 |
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: Waiting for more updates, any other operator open to join | Open | |
20240912-01 | Cablelabs | QualityByDesign:
|
China Mobile
IP High-throughput Elastic Network
The API template is available in PR#90
Approved for Sandbox repository
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: Waiting for more updates, any other operator open to join | Open | ||
20240912-01 | Cablelabs | QualityByDesign:
| Open | ||
20240926-01 | Telefonica | Telco Scoring
| Open | ||
20240926-03 | China Mobile | 5G New Calling China mobile to further present the API proposal and include material in API PR#31.
| Closed | ||
20240926-01 | Telefonica | Telco Scoring
| Closed | ||
20240926-03 | China Mobile | 5G New Calling
| Open | ||
20241010-01 | China Mobile | IP High-throughput Elastic Network
Pending review from Kevin about responses in the PR. Jorge Garcia Hospital raised concerns about technology dependancy in this API proposal | Closed | ||
20241010-02 | ALL | IMEI Fraud
| Open | ||
20241024-01 | China Telecom | Clarifications required in IoT API Proposals | Closed | ||
20241024-02 | Verizon | Device Management
| Open | ||
20241024-03 | T-Mobile US | Capability and Runtime Restrictions Ask to G. Murat Karabulut to provide some examples where this API will be useful. To be revisited during the after-next TSC meeting . | Closed | ||
20241114-01 | Cablelabs | QualityByDesign:
| Open | ||
20241010-01 | China Mobile | IP High-throughput Elastic Network
Pending review from Kevin about responses in the PR. Jorge Garcia Hospital raised concerns about technology dependancy in this API proposal | Open | ||
20241010-02 | ALL | IMEI Fraud
| Open | ||
20241024-01 | China Telecom | Clarifications required in IoT API Proposals | Open | ||
20241024-02 | Verizon | Device Management
| Open | ||
20241024-03 | T-Mobile US | Capability and Runtime Restrictions Ask to G. Murat Karabulut to provide some examples where this API will be useful. To be revisited during the after-next TSC meeting . | Open | ||
20241114-01 | Cablelabs | QualityByDesign:
| 116
| Closed | |
20241128-01 | China Telecom | IoT SIM Status Mgmt API: Slides presented in the meeting (to be updated into the API proposal documentation) Eric Murray G. Murat Karabulut New proposal focused on the management of services of devices (activate/deactivate) but still in relation with Device Management concept Mahesh Chapalamadugu (Verizon) to confirm if both proposals may still be merged AP: Email thread to be opened to provide a common position | Open | ||
20241128-02 | China Telecom | IoT SIM Fraud Prevention API New proposal shared byMoyuan Sun about SIM-Device binding change (possibly related to Device Swap) and area alerting (possibly related to Geofencing). Actions over lines are part of Device Management. AP: China Telecom to update proposal in PR#103 | Open | ||
20241128-03 | Backlog Admins | IoT SMS send API Proposal to be withdrawn → AP to take it out | Open | ||
20241128-04 | China Mobile | Facial Recognition Eric Murray proposes in 126 to consider this APi as part of already existing ModelAsA Service APi group (also from China Mobile) YinMing Fu considers APi separated as MaaS focused on LLM models Eric Murray raises issues on match with CAMARA authentication, privacy and identity existing mechanisms to be applied in this API Jorge Garcia Hospital raised question on the telco capabilities been leveraged, to be clarified AP to China Mobile to clarify open points | Open | ||
20241128-05 | TIM | IoT Data Transfer Activation Kevin Smith posible overlap with Dedicated Network API (proposal), related to configure a network for a set of devices. To be reviewed. AP: Open issue in Dedicated Network API to discuss. | Open |
Decision Points
DP # | DP description | Status |
1 | Increase backlog meeting duration from 1 to 1:30:
| Agreed |
2 | Move meeting schedule to UTC:
Or align with TSC:
| Agreed |
|
| |
|
| |
|
|
...