...
...
...
Attendees
Organization | Name |
Orange | |
Charter Communications | |
CableLabs | |
Telefonica | Alberto Ramos Monaga violeta.gonzalezfernandez@telefonica.com |
Vodafone | |
Ericsson | |
AT&T | |
T-Mobile US | |
KDDI | |
Slagen | |
Nokia | |
China Telecom | @moyaun Sun |
ZTE | |
KPN | |
GSMA | |
Centilion | |
Chunghwa Telecom | |
Deutsche Telekom | |
MTN | |
China Mobile | |
Verizon | |
PlektonLabs | |
TIM | |
NTT |
Agenda Proposal
Approval of minutes of last conf. call
Recent Updates & Recap
Review of Action Points
Discussion
New APIs Proposals: #35 (5G New Calling), #50 (Device Management), #63 (IMEI Fraud), #17 (Consent and Measurement), #23 (Carrier Wholesale Pricing), #24 (Steering of Roaming Information), #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #115 (SIM Historical Information), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID), #127 (Network Health Assessment), #128 (Network Traffic Analysis), #136 (eSIM Remote Management), #143 (IoT Data Transfer Activation), #157 (Voice Notification), #160 (Voice Verification Code), #163 (Dynamic Connectivity Data), IdentityAndConsentManagement (#167)
Out of Agenda:
API Enhancements Proposals: #109 (Support application resource requirements in application profiles)
Governance: Sandbox Repository for Traffic Influence API (#169)
Closing Issues
#22 (Capability and Runtime Restrictions), #18 (Receive SMS), #41 (Telco Scoring), #20 (Best Interconnection), #68 (Consent URL), #83 #85 #86 #87 (Model as a Service), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #89 (IP High-throughput Elastic Network), #141 (Energy Footprint Notification), #126 (Facial Recognition), #154 (QoS Booking)
AoB
Q&A
...
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.
...
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 | |||
2024112820250109-0401 | 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) | 143 TIM | IoT Data Transfer Activation Modify current API proposal (PR and name) with new use cases (TIM) | Open | |
20250123-01 | Verizon/China Telecom | Device Management & IoT SIM Status Mgmt API Agree on next steps, Mahesh Chapalamadugu to confirm way forward e.g. mix both API proposals | Open | |||
20250123-02 | China Telecom | IoT SIM Fraud Prevention API Consider merging in previous APIs or requesting it’s access in other group. | Open | |||
20250123-03 | TEF/DT | Dynamic Connectivity Data Modify current API proposal according to comments. | Open | |||
20250123-04 | ALL | Traffic Influence API - Sandbox repository Confirm inclusion of Traffic Influence API new repository (offline approval if no against comments are received) | 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. Decision based on TSC feedback:
| Agreed |
|
| |
|
|
...