General Updates

Working Groups

Sub Projects

• 1203 people from 413 companies have joined CAMARA

• 2078 people and 527companies are in (first) talks

• Logos see landscape

• New Premier / General Member

  • n/a

• New Participating Organizations

  • Airtel

  • JIO

  • Stechs

  • Vivo

  • Unryo

Updated: Dec 11, 2024 

@Markus Kümmerle 

• If you require support or meeting changes, please send an email to support@camaraproject.org

Updated Nov 12, 2024 

@Casey Cain @Evan Harrison 

• There was only one TSC meeting on December 19th since last All Hands Call.
  Draft minutes: 2024-12-19 TSC Minutes

• Next steps on Sandbox/Incubated/Graduated approach:

  • Candidates for the first round of incubation are the API Repositories which were part of the Fall24 meta-release. They will be evaluated if they meet the incubation criteria (e.g. sustainable maintainer and codeowner team, implementation of a released version by operator(s), …)

  • All repositories which were not part of the Fall24 meta-release are considered for now as Sandbox API Repositories

  • Details of Incubation will be worked out into an updated “API-Onboarding-and-Lifecycle.md” (previously “API-Onboarding”).

  • New structure of wiki will have sections Working Groups, Sub Projects (as today), Graduated/Incubated API Repositories, and Sandbox Repositories. This will make API Repositories first-citizens within the CAMARA wiki beside the Sub Projects.

• API Backlog

  • The following new Sandbox API Repositories are currently in their onboarding process – in case of interest you can e.g. leave comments on the Onboarding Tracker issues, join the mailing lists, open issues or discussions within the repositories

    • ModelAsAService

      • [Onboarding Tracker] ModelAsAService · Issue #162 · camaraproject/APIBacklog

    • HighThroughputElasticNetwork

      • [Onboarding Tracker] HighThroughputElasticNetworks · Issue #133 · camaraproject/APIBacklog

    • CapabilitiesAndRuntimeRestrictions

      • [Onboarding Tracker] CapabilityAndRuntimeRestrictions · Issue #134 · camaraproject/APIBacklog

    • EnergyFootprintNotification

      • [Onboarding Tracker] Energy Footprint Notification · Issue #165 · camaraproject/APIBacklog

• Release Management

  • The M3 milestone (release candidate versions of the APIs) for Spring25 release was originally planned for Dec 21st. The TSC has decided to move this date to January 17th (cut-off date for providing the release PRs to the Release Management team).

  • All API repositories from Fall24 are encouraged to participate in Spring25, at least do the updates induced by Commonalities 0.5.0 changes. The goal is to have again a consistent set of APIs in the release.

  • For further details see the Release Management updates below.

  • Next TSC meeting is on January 16th, will reevaluate the situation

• Commonalities

  • r2.1 with 0.5.0-alpha.1 available, still some open issues (see below). Release Candidate version expected for the M3 milestone (on risk)

• Identity & Consent Management (ICM)

  • r2.1 with 0.3.0-alpha.2 available. Release Candidate version expected for the M3 milestone.

Updated Jan 8, 2025

@Herbert Damker 

• Marketing materials:

  • CAMARA Presentation and Onepager are updated; new versions are available on GitHub and Website

  • Marketing concept 2025 finalized

• Events:

  • Planning for MWC in progress

    • will share signage for members to use in their booth

    • Reception hosted by Red Hat on 4 March 19:00

  • 2025 planning completed, see list of events

• Website:

  • Update planned for API descriptions:

    • API table on CAMARA and Open Gateway website, linking to GSMA site

    • Developer-friendly API descriptions, implemented as sub-pages of CAMARA website, replacing current Sub Project pages

    • Wiki, API repositories, API definitions - updates in progress

  • LF creative team in progress to create a blueprint

Updated: Jan 9, 2025 

@Markus Kümmerle 

@Jill Lovato

• Meta-release Spring25

  • 13 new APIs and 21 updated Fall24 APIs (of 25) are candidate for Spring25.

  • Reminder that all Fall24 APIs need to check the Commonalities & ICM updates, as it is expected that all Fall24 APIs need to create an update of their APIs for Spring25.

• M3 (2025-01-17) - preparation of API release-candidates

  • Complete the Spring25 API release tracker(s), especially with the scope issue.

    • Check the email sent to codeowners for a few other updates requested on the release trackers.

  • Finalize development of the API and its release assets, as well as the release PR

  • Request Release Management review latest by Jan 17, though earlier is much appreciated

    • To do this, include release-management-maintainers as a reviewer of your release PR once ready

• Sandbox APIs: any APIs not planned for any meta-release should also create their API release tracker to give wide visibility - please label the tracker with “camara-other”. See: Sandbox APIs

• Meta-release Fall24

  • Patches of Fall24 API releases may be created as needed and shall be documented on the existing release tracker. Please involve @camaraproject/release-management_maintainers as usual (important for proper updates of Fall24 information).

• All documentation is here: Release Management Working Group

Updated: Jan 8, 2025 

@Tanja de Groot 

• Important Changes from Commonalities version 0.5.0-alpha.1 published in release 2.1:

  • Common artifacts for testing error scenarios for device and phoneNumber camaraproject#325

  • String format/pattern recommendation camaraproject#330

  • ACCESS_TOKEN_EXPIRED termination reason guidance camaraproject#364

  • Updated rules when using POST for sensitive data camaraproject#358

• Issues:

  • Newly proposed Corrections to alpha

  • Removing or changing `x-camara-commonalities` extension field · Issue #327 · camaraproject/Commonalities

  • Improve definition of x-correlator header · Issue #352 · camaraproject/Commonalities

  • Should error 429 (TOO_MANY_REQUESTS) be mandatory in CAMARA specifications? · Issue #365 · camaraproject/Commonalities

  • Cleanup and slim down design guidelines document - planned when pending changes are introduced

• Announcements

  • Analysis of Commonalities 0.5.0-rc.1 changes started to help subprojects align to Commonalities

Updated: Jan 9, 2025 

@Rafal Artych 

• Documents

  • Live table for API backlog available here. Updated version including new information.

  • Accepted API proposals stored here. 

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

  • API Enhancements Proposals: N/A

• Announcements

  • Changes in the way of approving new API proposals are under review, following sandbox approach.

  • Follow-up of approved APIs during onboarding phase

  • Closing issues as validated by TSC or in process of been resolved (APs pending):

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

  • Proposals to be discussed in next TSC: 

    • QoS Booking (#154)

  • Info: New repositories under creation for

    • Facial Recognition (126)

    • Energy Footprint Notification (141)

Updated: Jan 9, 2025 

@Jorge Garcia Hospital

• ICM 0.3.0 - preparing the scope for meta-release Spring25 #193

• Authentication method in authorization code flow #215

  • root question: Is network-based authentication mandatory in OIDC Authorization Code flow?

  • No agreement yet

• Consent URL API vs OIDC consent collection #224

  • ICM work item

• Sender-constrained tokens for higher security

  • Clarifications on using sender-constraint tokens DPoP by AxelNennker · Pull Request #225 · camaraproject/IdentityAndConsentManagement

• New PR recommending to ignore login_hint in OIDC authorization code flow

• Update CAMARA-ICM-examples.md with CIBA examples #237

Updated: Jan 9, 2025

@Axel Nennker

Updated: Dec 11, 2024 

@Pedro Díez García 

Updated: Jan 8, 2025 

@fabrizio moggio 

Updated: Dec 12, 2024 

@G. Murat Karabulut @Lyle Bertz

Updated: Dec 11, 2024 

@Pedro Díez García 

Updated: Jun 13, 2024 

@Hanbai

Updated: Oct 10, 2024 

@Mahesh Chapalamadugu @Ben Hepworth

Updated: Dec 11, 2024 

@Pedro Díez García

Updated: Jan 9, 2025 

@Thorsten Lohmar

DeviceDataVolume

Updated:

@Maximilian Laue @Sachin kumar

Updated: Dec 12, 2024 

@Eric Murray 

Updated: Dec 11, 2024 

@Jose Luis Urien Pinedo 

Updated: Dec 12, 2024

@Akos Hunyadi

@Rafal Artych  

Updated: Dec 11, 2024 

@Ludovic Robert

Updated: Aug 5, 2024 

@cristina.santanacasillas 

Updated: Dec 12, 2024 

TBD

Updated: Sep 10, 2024 

@Jesús Peña García-Oliva 

Updated: Jan 8, 2025 

 @Toshi Wakayama 

Updated: Dec 11, 2024 

@Fernando Prado Cabrillo @Stefano Falsetto

Updated: Nov 12, 2024 

(initial entry added by @Herbert Damker)

Updated: Dec 12, 2024 

@Christopher Aubut @Randy Levensalor @Ben Hepworth @Justin Pace

Updated: Jun 13, 2024 

@Shuting Qing 

Updated: Dec 11, 2024 

@Ludovic Robert

Updated: Dec 11, 2024 

@Ludovic Robert

Updated: Sep 11, 2024 

@Jorge Garcia Hospital 

Updated: Dec 11, 2024 

@Herbert Damker 

Updated: Jun 13, 2024 

@Fan Yang 

Updated Dec 12, 2024 :

@Ben Hepworth @Mahesh Chapalamadugu @Kevin Smith

Updated: Jul 10, 2024 

@Ramit Chawla

Updated: Jun 13, 2024 

@Kevin Smith 

Updated: Nov 14, 2024 

@Ludovic Robert

Updated: Sep 12, 2024 

@Dan Xu

Updated: Sep 12, 2024 

@Dan Xu

Updated: Jan 9, 2025

 @Santiago Troncoso