Page Comparison

DRAFT MINUTES

Attendees

 Agenda Proposal

• Antitrust Policy

• 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), #154 (QoS Booking), #157 (Voice Notification), #160 (Voice Verification Code), #163 (Dynamic Connectivity Data)

  • Out of Agenda:

  • API Enhancements Proposals: #109 (Support application resource requirements in application profiles)

  • Governance: N/A

• 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)

• AoB

• Q&A

...

• Minutes of last API backlog WG call available here

  • DECISION: Approved

Recent Updates & Recap

TSC meeting 05th 19th December:

• https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md

• One new API proposals brought to TSC (1) and one new API enhancement proposal.

• New API: Energy Footprint Notification:

  • Proposed by TIM and supported by DT. Original Issue #141 . Template available.

  • Decision: Approved

• API enhancement: Facial Recognition:

  • Proposed by China Mobile as part of existing ModelAsAService API repository. Original Issue #126. Template available.

  • The ModelAsAService Sandbox team should consider if they want to develop the API within the ModelAsAService repository or in a separate repository (e.g. to allow participation of contributors who want get only involved into the original ModelAsAService scope)

  • Decision: enhancement approved - target repository of this API to be decided later.

• API Backlog proposal for API management/marketing…:

  • 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 options:

    • CodeOwner/maintainer list: Includes companies actively leading the API definition, but not companies which participate in a more passive way.

    • Github contributors tool (e.g./APIBacklog/graphs/contributors ) reports the companies which have participated actively in the API, with e.g. providing code. But does not report companies who passively track the API evolution, e.g. participating in the discussion meetings.

    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 contributors.

    Companies to provide support (or concerns) about this proposal. E.g. wiki page of each repository could host a file where companies can include their support to the API(s)

...

• 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.

...