DRAFT MINUTES
Attendees
Organization | Name |
Orange | |
Charter Communications | |
CableLabs | |
Telefonica | |
Vodafone | Ali Gilani Eric Murray Kevin Smith |
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 | |
Verizon | |
PlektonLabs | |
TIM | |
NTT |
...
GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/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
IMEI Fraud API
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.
...
Issue # | Company | Summary | Status Update |
T-Mobile US | Capability and Runtime Restrictions The API template is available in PR#74 | Approved 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:
| |
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 | |
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 | |
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 | |
China Mobile | Facial Recognition The API template is available in PR#130 | EasyCLA to be solved METING UPDATE: material presented by YinMing Fu. 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 --> MNO face database is used AP to China Mobile to clarify open points To modify the template to ScopeEnhancement of MaaS. YinMing Fu updated PR#130 and API will be treated in next TSC 19th dec. 15:00 UTC METING UPDATE: Approved, pending to decide whether it will be aprt part of same repo or different from MaaS | |
TIM | Energy Footprint Notification The API template is available in PR#142 | Approved: |
...
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 | |
20240926-03 | China Mobile | 5G New Calling
| Open | |
20241010-02 | ALL | IMEI Fraud
| Open | |
20241024-02 | Verizon | Device Management
| Open | |
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-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 | Closed | |
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. | Closed | |
20241212-01 | KDDI | QoS Booking Open issue in Dedicated Network API to discuss possible overlap. | Closed | |
20250109-01 | TIM | IoT Data Transfer Activation Modify current API proposal (PR and name) with new use cases (TIM) | 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 |
3 | As in APIBacklog/issues/123 , companies see a suitable feature to have a spot in each repository where participants can be reported, stating the interest of those participant companies for this API. Current optionsDecision based on TSC feedback:
Proposal to create a place where companies can provide their support or willingness to participate in an API, not official as maintainer/codeowner and not providing proper code as in
| Agreed |
|
| |
|
|
AoB
N/A
Q&A
How does CAMARA API pipeline work?
...