General Updates

Working Groups

Sub Projects

• 1186 people from 409 companies have joined CAMARA

• 1825 people and 389 companies are in (first) talks

• Logos see landscape

• New Premier / General Member

  • n/a

• New Participating Organizations

  • Chenosis

  • IEEE5G6GTestbed

  • KT

  • LG U+

  • Lytn

  • M1

  • Optare Solutions

  • Plusmo

  • Pryvx

  • Sinch

  • Stechs

  • Tata Exlsi

  • Telstra

  • Virtus

  • WCG

  • Xacria

  • Xecurity Pulse

Updated: Nov 12, 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 

• TSC Election 2024 done. The newly elected members:

  • Doug Makishima

  • Nick Venezia

  • Massimiliano Troiani

  • Jan Friman

  • Herbert Damker

  • Eric Murray

  • Ludovic Robert

  • Jose Luis Urien

  • Shilpa Padgaonkar

  • Diego González

  • Mahesh Chapalamadugu

  • Tanja de Groot

  • Toshiyasu Wakayama

• TSC Chair and Vice-Chair election started with nomination phase.

• API Backlog 

  • TSC approved “Model As A Service” API family, repository is created.

  • For “Capability and Runtime Restrictions” there were further questions, will be again discussed on Nov 21st.

  • “Consent URL API” must first be discussed in Identity & Consent Management (ICM) working group

• Release Management

  • TSC has declared the M1 milestone for the Spring25 meta-release on Nov 7th

  • API Sub Projects are asked to create the scope and release trackers for the Spring25 meta-release

  • M2 milestone (release candidates of Commonalities & ICM) is on Dec 7th.

• Commonalities

  • Commonalities has provided for the M1 milestone the important PRs for the Spring25 scope (Commonalities/issues/273)

  • Sub Project should review the PRs (details see below) and consider the changes within their scope planning

• Identity & Consent Management (ICM)

  • Also ICM has provided the PRs with the important changes at M1 (IdentityAndConsentManagement/issues/193)

  • For details see below.

Updated Nov 12, 2024

@Herbert Damker 

• Marketing materials:

  • CAMARA Powerpoint template is updated; new version is available on GitHub and Website

  • Marketing concept 2025 finalized

• Events:

  • NetworkX and MWC Las Vegas

  • KubeCon NA Nov. 12-15

  • API Days Paris Dec. 3-5

  • 2025 planning is in progress, budget approved, see list of events

• Website:

  • Update planned for API descriptions

Updated: Nov 12, 2024 

@Markus Kümmerle 

@Jill Lovato

• Meta-release Spring25

  • M1 declared by TSC on 2024-11-07

    • Commonalities and ICM: PRs are available. The alpha releases will be ready shortly. An M1 update message will be sent when they are available.

  • Sub Projects to do API development for M3 (2024-12-21)

    • Please create your API release tracker(s) for Spring25. See Meta-release Spring25: only 6 APIs sofar.

  • Sandbox 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”

  • For Fall25 meta-release APIs, please label the API trackers with “camara-fall25”

• Meta-release Fall24

  • M6 will be declared shortly

  • Release Management documentation has been updated with the feedback and will be released as r2.1.

• All documentation is here: Release Management Working Group

Updated: Nov 14, 2024 

@Tanja de Groot 

• Scope definition for Spring25 release, see Commonalities 0.5.0 - prepare the scope · Issue #273 · camaraproject/Commonalities

  • M1: PRs linked to each issue - please review

  • Main changes:

    • Error responses - PR #316, PR #329;

    • info.description template for device / phone number identifiers #PR 324

    • Updates of event subscription and notification guidelines #PR 313

• Issues:

  • Support of Multi-SIM lines in CAMARA APIs · Issue #302 · camaraproject/Commonalities

  • Clean up and redesign of API Design Guidelines Commonalities/issues/306

• Announcements

  • Oct 25: OpenAPI Initiative announced specification versions 3.0.4 and 3.1.1 · Issue #338 · camaraproject/Commonalities - recommends to update.

Updated: Nov 14, 2024 

@Rafal Artych 

• Documents

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

  • Accepted API proposals stored here. 

• New Issues

• Discussion

  • OGW APIs:  #35 (5G New Calling),  #50 (Device Management), #63 (IMEI Fraud),  #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #97 (IoT SMS send API), #115 (SIM Historical Information)

  • Other APIs:  #17 (Consent and Measurement),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #89 (IP High-throughput Elastic Network), #109 (Support application resource requirements in application profiles), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID) 

• Announcements

  • Backlog meeting duration are extended from 1 to 1:30 and in UTC time aligned with TSC slots (one week shifted):

    • Backlog 2nd Thursday: 09:00 UTC (10:00 CET / 01:00 PT) [Note: during next DST, 11:00 CEST / 02:00 PST]

    • Backlog 4th Thursday: 15:00 UTC (16:00 CET / 07:00 PT) [Note: during next DST, 17:00 CEST / 08:00 PST]

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

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

    • #22 () #68 (Consent URL),

  • Proposals to be discussed in next TSC: 

    • Consent URL (#68)

    • Capability and Runtime Restrictions API (#22)

    • IP High-throughput Elastic Network (pending on final validations offline) (#109)

  • Info: New repositories created for ModelAsAService, CustomerInsight, DedicatedNetworks, QualityByDesign

Updated: Nov 14, 2024 

@Jorge Garcia Hospital

• CAMARA Security and Interoperability Profile und CAMARA APIs Access and User Consent Management were updated for better wording.

• The section info.description was clarified which has impact on all subprojects. All subprojects are asked to integrate the new section into their API description when they do a release. There should be no new release if this is the only change. ReleaseManagement is going to check that new release have the updated text.
  The wording in the Mandatory template for info.description is unclear #178
  ICM text should not state that Telco Operators are the ones providing these APIs #190

• Authentication method in authorization code flow #215

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

• Consent URL API vs OIDC consent collection #224

• Scope definition for Spring25 release (IdentityAndConsentManagement 0.3.0)

  • Merged PRs

    • Recommend signed authentication requests for CIBA #217

    • MERGED PR #182 split - terms and definitions (part 1 of 3) #212

    • MERGED PR #182 split - better english improvements (part 2 of 3) #213

  • Proposed candidate topics:

    • Documentation improvements

      • Authentication method in authorization code flow #215

      • Improve Access and User Consent document #182. This PR is now split into:

        • PR #182 split - info.description template review (part 3 of 3) #214

      • Clarity on the use of login_hint #191

      • OIDC authorization code flow error response #209

      • Add response codes for error scenarios #220

      • Spring25: Proposal to RECOMMEND the use of Signed Request Object for the /authorize endpoint to prevent abuse #205

      • Proposal for CAMARA mandated minimum acceptable JWT token lifetime #208

      • Update section on client authentication #216

        DPoP support in CAMARA OIDC Profile #125

        • RECOMMEND using sender-constraint tokens DPoP #225

      • Allow to use operator_token (from TS43) to identify device on authentication request  #145

      • operator token login_hint format #218

      • Authentication method in authorization code flow #215

Updated: Nov 14, 2024 

@Axel Nennker 

Updated: Nov 13, 2024 

@Pedro Díez García 

Updated: Nov 14, 2024 

@fabrizio moggio 

Updated: Nov 13, 2024 

@Pedro Díez García 

Updated: Jun 13, 2024 

@Hanbai

Updated: Oct 10, 2024 

@Mahesh Chapalamadugu @Ben Hepworth

Updated: Nov 13, 2024 

@Pedro Díez García

Updated: Oct 10, 2024 

(initial entry added by @Herbert Damker) @Thorsten Lohmar

DeviceDataVolume

Updated:

@Maximilian Laue @Sachin kumar

Updated: Nov 13, 2024 

@Eric Murray 

Updated: Nov 14, 2024 

@Jose Luis Urien Pinedo 

Updated: Nov 14, 2024

@Akos Hunyadi

@Rafal Artych  

Updated: Nov 14, 2024 

@Ludovic Robert

Updated: Aug 5, 2024 

@cristina.santanacasillas 

Updated: Sep 10, 2024 

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

Updated: Nov 14, 2024 

 @Toshi Wakayama 

Updated: Jul 8, 2024 

@Fan Yang @Fernando Prado Cabrillo 

Updated: Nov 12, 2024 

(initial entry added by @Herbert Damker)

Updated: Nov 13, 2024 

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

Updated: Jun 13, 2024 

@Shuting Qing 

Updated: Nov 14, 2024 

@Ludovic Robert

Updated: Nov 14, 2024 

@Ludovic Robert

Updated: Sep 11, 2024 

@Jorge Garcia Hospital 

Updated Nov 13, 2024 :

@Ben Hepworth @Mahesh Chapalamadugu @Kevin Smith

Updated: Oct 10, 2024 

@Herbert Damker 

Updated: Jun 13, 2024 

@Fan Yang 

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: Nov 12, 2024

 @Santiago Troncoso