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 | |
TIM | |
NTT |
...
Minutes of last API backlog WG call available here
DECISION: Approved
Recent Updates & Recap
TSC meeting 16th January:
...
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 |
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: 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: No 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: No 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 Recommendation is that China Mobile join regular WebRTC call to discuss 5G New Calling proposal there. MEETING UPDATE: No updates | |
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 ACTION: Review match with other Device management APIs (home devices or similar) and IoT/Device status (AP Backlog: contact Mahesh) Also ensure this is a proper telco capacity to be consumed by developers, in comparison with Operate API (TM Forum) that are related to Aggregators. METING UPDATE: Potential of merging IoT SIM Status Mgmt API in, will be checked by Mahesh Chapalamadugu until next meeting. | |
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 Telecom | IoT SIM Status Mgmt API The API template is available in PR#105 | Relationship with device management proposal, to confirm relationship. AP: China Telecom Meeting considered that this proposal has some overlap with the Device Management proposal from Verizon APs: China Telecom
Moyuan Sun proposal to be modified to “communication capabilities” to avoid overlap with Device Management API proposal 50 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 MEETING UPDATE:Next backlog meeting will be treated jointly with device managementMahesh Chapalamadugu Action point verify the merge with Device Management for next meeting. | |
China Telecom | IoT SIM Fraud Prevention API The API template is available in 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
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. China Telecom updates proposal in PR#103, keep offline discussion around Device Management. MEETING UPDATE:Next backlog meeting will be treated jointly with device management Opinion shared, that it could two different YAMLs. Check for TSC. | |
Verizon | Support application resource requirements in application profiles The API template is available in PR#110 | METING UPDATE:No update Mahesh Chapalamadugu presented this topic, asking for review until the next meeting | |
China Unicom | SIM Historical Information The API template is available in PR#114 | Eric Murray comment: Sounds like a “historical SIM Swap” API. Discuss with SIM Swap sub-project. APs: China Unicom
METING UPDATE: no updates | |
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
METING UPDATE: no updates | |
China Unicom | Number Of Cards Under User's ID The API template is available in PR#119 | Use case appears to be a KYC use case APs: China Unicom
METING UPDATE: no updates | |
China Unicom | Network Health Assessment The API template is available in PR#129 | EasyCLA to be solved METING UPDATE: No updates | |
China Unicom | Network Traffic Analysis The API template is available in PR#129 | EasyCLA to be solved METING UPDATE: No updates | |
China Unicom | eSIM Remote Management The API template is available in PR#140 | METING UPDATE:No updates Action for all China Unicom Topics: Reg.cox will ask for an update from China Unicom in the next meeting | |
TIM | IoT Data Transfer Activation The API template is available in PR#144 | Focused on booking resources for a non-warranted connection for IoT, group of many devices at once, during a certain period. Not directly related to QoD or HighThroughput API. Kevin Smith posible overlap with Dedicated Network API (proposal), related to configure a network for a set of devices. To be reviewed. Issue#14 raised to discuss about posible overlap fabrizio moggio : Proposal to include IoT API (separate repo) as part of the Dedicated Network “family” (share participants and meetings) to align use cases and definitions. Jan Friman : this API looks like a specialization of Dedicated network API Proposal: To be proposed in the Dedicated network issue to validate Issue#14 TIM proposed an alternative approach to complement Dedicated Networks API, so that developer can manage energy modes, IoT slice selection os similar for a IOT device. Tanja de Groot Thorsten Lohmar proposed those features to be generic, not dedicated to IoT use cases Continue discussion with the new scope, including new API name. Dedicated network group will still be used to include the previous scope (scheduling a network config for IoT) New scope of API will be discussed separately. AP: modify current API proposal (PR and name) with new use cases (TIM) METING UPDATE: fabrizio moggio will provide feedback of the status in the next backlog call | |
China Unicom | Voice Notification The API template is available in PR#158 | METING UPDATE: not treated | |
China Unicom | Voice Verification Code The API template is available in PR#161 | METING UPDATE: not treated | |
Telefonica | Dynamic Connectivity Data The API template is available in PR#164 | METING UPDATE: not treated | |
Cellcard | IdentityAndConsentManagement The API template is available in PR#166 | METING UPDATE: not treated | |
TIM | Traffic Influence API - Sandbox repository https://github.com/camaraproject/EdgeCloud/discussions/313#discussioncomment-11409923 | Approve the creation of a separated sandbox repository for Traffic Influence API, now under EdgeCloud repo. If no objection, tracker will be created accordingly. API and repo will be linked to EdgeCloud subproject. METING UPDATE: |
...