New Participants

• 1091 1126 people from 386 396 companies have joined CAMARA
• 1318 1658 people and 221 337 companies are in (first) talks
• Logos see landscape
• New General Member - Indykite
  • https://www.indykite.com/
    
• New Participating Organizations - LFOD and phine.tech
  • https://lfod.io
  • https://phine.tech/

Fund Updates

• Status of the technical project (same as below)
• Budget approvals

Technical Steering Committee

• EasyCLA introduction
  • https://github.com/camaraproject/EasyCLA available as neutral repository where you can open a trivial PR and initiate the EasyCLA signing process.
    • Especially all Codeowners should use this opportunity to ensure that they can continue working after the project wide activation of EasyCLA.
  • The check for a signed CLA will be activate on all repositories soon. 

• New structure of Sub Projects agreed within the TSC (see PR Governance/pull/146)
  • A Sub Project can be now a set of API Repositories (one or multiple)
  • Details are described within ProjectStructureAndRoles.md
  • Opportunity for Sub Projects with multiple APIs to put them into separate repositories
    • Allows independent releases of APIs, simplifies the management of releases

• API Backlog 
• RegionUserCount got renamed into RegionDeviceCount
• ShortMessageService scope extended with "Receive SMS"
• DeviceStatus has been discussed the adoption of the two new APIs (Device Connection Quality Indicator, Device Data Volume)

• • EasyCLA was activated on all repositories on August 30th
  • Please test that you have a valid CLA within https://github.com/camaraproject/EasyCLA before you need it for a contribution

• API Backlog 
• Repositories for Device Quality Indicator and Device Data Volume created, work in context of Sub Project DeviceStatus can start
• Repository for Subscription Status created, Codeowners and Maintainers have to be defined, then work in context of Sub Project KnowYourCustomer can start
• Proposal for Quality By Design approved in TSC. Repository will be created. Should be first used to describe the concept in User Stories to derive which APIs are involved, need to be changed or newly created. Repository name might get changed based on results.

• Commonalities
  • Public release r0.4.0 as part of Meta-Release Fall24 available
  • Scope definition for Spring25 release (Commonalities 0.5.0) until September 30th, see below
• Commonalities
• Release candidate of v0.4.0 available
Please consider this version for your APIs, especially the ones planned for the Meta-Release Fall24

• Identity & Consent Management (ICM)
• Release candidate of v0Public release r0.2.0Please consider this version for your APIs, especially the ones planned for the as part of Meta-Release Fall24 available

• Release Management 
• See below

• Scope definition for Spring25 release (IdentityAndConsentManagement 0.5.0) until September 30th, see below

• Release Management 
• M4 approved by TSC on September 5th, actual M4 date of API repositories is the date of merge and release creation

• Exception decided for the "Test statement" of stable APIs in Fall24 Meta-Release. This requirement for stable APIs couldn't be met due to the tight time plan in the current release cycle. The APIs have added a footnote in the API Readiness checklist that there might be bugs within the test definitions (will be addressed by patch release as needed).

• M5 in preparation by Release Management (communication of Meta-Release)
• Slides about Meta-Release (will go into the CAMARA Project presentation of Marketing Group):
  

  View file
  name CAMARA Meta-release Fall24.pdf height 250

  
  
  

Marketing (Outreach Committee)

• CAMARA Powerpoint template available: template

Marketing (Outreach Committee)

• CAMARA Powerpoint template available: template
  • Please use it for all external communication, but also for internal needs
• Marketing concept finalized: https://github.com/camaraproject/Marketing/blob/main/documentation/MarketingMaterial/CAMARA%20MarketingConcept.pptx

• 2024 event list finalized:: https://wiki.camaraproject.org/display/CAM/2024+Event+Tracker

  • CAMARA webinar at 12th of June and 10th of July with outstanding registration and participation: https://understandingnetworkapis.com/
  • CAMARA presentations at Open Telco LATAM Summit and MWC Shanghai
  • Next big event is Open Source Summit EuropeNext big event is Open Source Summit Europe (Shift, Digital-X, API Days, CASA24, FutureNet Asia at the same time)

• 2025 planning started

  • Review of marketing concept for 2025
  • Working on 2025 event list / prioritization

• New versions of CAMARA presentation and CAMARA onepager coming soon available latest 13 Sept 2024  on GitHub (new logos, new APIs, new slides including these from the CAMARA webinarsrelease management / meta release)

• Content is moved in dedicated Marketing repository: https://github.com/camaraproject/Marketing

Release Management

• Meta-release schedule (see Meta-release

  schedule 

  Fall24 plan)

  • M1

    M4 -

    Declared

    declared at TSC

    of 2024-07-04 for Commonality alpha release available at 2024-06-10. Decision to skip the M1 for ICM and go directly to the first release-candidate for M2. 
  • M2 - Release candidates of Commonalities and ICM under TSC review till 2024-07-10. Release PRs will be merged and announced shortly on the Meta-release Fall24 plan. M2 will be declared after that.
  • M3 - First release-candidates of API Sub Projects to be provided by 07-21. 
  • M4 - Final release candidates of API Sub Projects: target 08-30.
• Supporting documentation:
  • One stop documentation is here: Release Management Working Group
  • API release documentation is available in GitHub:
    • ReleaseManagement/documentation/API_Release_Guidelines.md
    • ReleaseManagement/documentation/API-Readiness-Checklist.md
    • ReleaseManagement/documentation/CHANGELOG_TEMPLATE.md
    • An example CHANGELOG;md: ReleaseManagement/documentation/CHANGELOG_EXAMPLE.md
  • Reminder: API versioning guidelines are provided in the API Design Guidelines (Chapter 5), further details are within the wiki.
• Next steps
  • All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.
    • Reminder: the release number of this first pre-release shall have the format x.y.z-rc.1 for the targeted release of API version x.y.z in the meta-release.
    • Before M3 you may do 1 or more x.y.z-alpha.n releases as needed for teh API development, but you can also go from the current release directly to the first release-candidate by M3. Please reflect this in the CHANGELOG.md.
  • Milestone timeline is here: Meta-release Fall24.
  • The Release Management team will start checking APIs and highlighting any points related to the release process where needed using the API Sub Project's issues list to help in the meta-release progress.

• • meeting on Sept 5th. Actual API release publications finished on 2024-09-11.

  • M5 - Fall24 meta-release publication: planned for 2024-09-15

  • M6 - meta-release retrospective: planned for 2024-09-30

  • M0 - Spring25 meta-release kick-off: planned for 2024-09-30

• Meta-release APIs - 25 APIs in total:
  • 5 stable APIs (version = 1.0.0) released with exception on the "Test statement". This requirement for stable APIs couldn't be met due to the tight time plan in the current release cycle. The APIs have added a footnote in the API Readiness checklist that there might be bugs within the test definitions (will be addressed by patch release as needed).
  • 20 initial APIs (version = 0.y.z) released of which
    • 9 updated APIs from deployed previous initial API releases
    • 11 newAPIs (6 request-response APIs and 5 event notification APIs)
  • 21 additional initial APIs are in progress but are not part of this meta-release.

• Next steps

  • M6: Retrospective: feedback can be provided 1) as Release Management GitHub issues, 2) by editing the Meta-release feedback page, or 3) by email to wg-release-management@lists.camaraproject.org

  • M6: Release of the Release Management documentation in GitHub (for M6)
  • Prepare Spring25 meta-release
    • Release Management: M0 kickoff preparation
    • Commonalities & ICM: define scope and start alpha release development
• Supporting documentation (for reference)
  • One stop documentation is here: Release Management Working Group
  • API release documentation is available in GitHub: ReleaseManagement/documentation
  • API versioning guidelines are provided in the Commonalities API Design Guidelines (Chapter 5), further details are within the Release Management wiki.

Commonalities

• Version 0.4.0 of Commonalities published  23 Aug 2024 
• New issues:

  • Corrections agreed during release preparation: #284 #285

  • Test Definition template for explicit subscription API #293

  • Subscriptions enhancements #295 #296 #299 #300 
• Announcements

  Commonalities
  

  • Release 0.4.0-rc.1 of Commonalities was published on 11th of July
    • Please provide feedback on needed corrections for final release.
  • New issues:

    • Request body is required but all properties are optional #247

    • Add rules in design guideline about multi-endpoint API design & implementation requirement #246

    • How to inform API consumer about unprocessable subscription request in Async mode #243

    • Add an “Area” data-type into CAMARA_common.yaml #242

  • Announcements

    • See the Release 0.4.0-rc.1 Changelog

    • M0 for Spring25 meta-release is on 30-09-2024 2024

      • Please indicate the topics to be included

        in 

        in Commonalities v.0.5.

        0 

        0 cf. Issue #273

APIBacklog

• Documents

  • Live table for API backlog availablehere. Stable version.

  • Accepted API proposals stored here. 

• New Issues
• OGW Drop #3 APIs:  #19 (Device Quality Indicator)Discussion

• OGW Drop #4 APIs:  #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling), #63 (IMEI Fraud)

• Other APIs:  #17 (Consent and Measurement),

#18 (Receive SMS),

•  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information),

#29 (Call Status

•  #60 (Dedicated Networks),

#28 (Device Data Volume)
• Scope Enhancement: #45 (KYC-Match API - Scoring Logic), #48 (RegionUserCount)
• Governance: #4 (Structures and roles, RACI, Maintainers initiative), #53 (Scope Enhancement API Template)
• PRs
  • Application templates for those API proposals which have not been discussed yet in TSC.
• Announcements

  • API Backlog will be held from then to now in a separate GitHub Repo and migration of issues have been completed. Active PRs will be moved to the new repo

  • Changes in the way of approving new API proposals are under review

  • Closing issues being treated in the TSC:

  • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions)

  • Created new subproject/repos:

    • Verified Caller → #27 (China Telecom, ZTE, China Unicom, Huawei, China Mobile)

    • Tenure → #2 (Vodafone, Telefonica, Orange, DT)

IdentityAndConsentManagement

•  61 (network Info), 68 (Resource URL) #83 #85 #86 #87 (Model as a Service)

• Governance: #4 (Structures and roles, RACI, Maintainers initiative)

• PRs
  • Application templates for those API proposals which have not been discussed yet in TSC + new API Backlog table with reduction of columns (New APIbacklog.md by TEF-RicardoSerr · Pull Request #80 · camaraproject/APIBacklog · GitHub).
• Announcements

  • API Backlog will be held from then to now in a separate GitHub Repo and migration of issues have been completed. Active PRs will be moved to the new repo

  • Changes in the way of approving new API proposals are under review

  • Closing issues being treated in the TSC:

  • #20 (Best Interconnection), #22 (Capability and Runtime Restrictions), #19 (Device Quality Indicator), #28 (Device Data Volume), #18 (Receive SMS), 70 (Quality by Design)

  • Proposals to be discussed in next TSC: 

    • Dedicated Networks

    • Telco Scoring
  • Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus and QualityByDesign are created

IdentityAndConsentManagement

• Public release r0.2.0 as part of Meta-Release Fall24 available
• Scope definition for Spring25 release (IdentityAndConsentManagement 0.5.0) until September 30th
  • Please indicate the topics to be included https://github.com/camaraproject/IdentityAndConsentManagement/issues/193

BlockchainPublicAddress

Expand

Deliverable R/O Current status / Achievements API Definition R Released and approved v0.1.9-wip Working in next release: v0PR on 0.2.0-wip with further alignment with CAMARA guidelines (error codes). Conditional Call FWD endpoint as optional (error code 501 No additional Business Requirements so far. ON-HOLD: Working in technical enhancements in the meantime (see latest section) API doc/user stories/testcases R User Story and Documentation released. PR for the full Test Cases for the two endpoints Implementation O NA (Optional according to CAMARA Readiness Checklist) API Reviews and extensions O NA API Doc Full API documentation pending to be consolidated under API Spec Use Cases - First version available Implementation R Not yet API Reviews and extensions O Some typos fixed in PR#55 Pending Points: - Issue #16 - Discussion about consent management considerations in retrieval of blockchain public addresses ON-HOLD - Issue #51 - Avoiding the use of "plain" phoneNumber as filter criteria of blockchain retrieval - Issue #52 - Enhancement of blockchainPublicAddress belongs to the user whose phoneNumber is indicated to set-tp the binding relationship

CallForwardingSignal

Expand

Deliverable R/O Current status / Achievements API Definition R API spec: Current API Spec Release is  Released and approved the public release v0.2. 1. Next outputs for MetaRelease Fall24: Payment Evolution v0.3.0 align with NEW Refund functionality v0.1.0. 0  The API has completed the Fall24 review and reached Fall24 M4. Release tag: r1.3 API doc/user stories/testcases RUse Cases - First version available User Story and Documentation released. Readiness Checklist completed. Changelog. md file completed. Test Cases for the two endpoints released. YAML v0.2.0. Implementation R O NA (Optional according to CAMARA Readiness Checklist)Not yet API Reviews and extensionsO O NA

CarrierBillingCheckOut

ClickToDial

ConnectivityInsights

DeviceIdentifier

DeviceLocation

DeviceStatus

DeviceSwap

EdgeCloud

HomeDevicesQoD

Expand

- KYC Match / Fill-in v0.1.1: API doc embedded in YAML, user stories available, testcases not yet available. - Age Verification v0.1.0: User story is being discussed, in alignment with API definition discussion; Issue#81. - KYC Match and KYC Fill-in v0.2.0: work in progress for enhancements; Issues #38 #39, #47, #65, #66, #71, #77, #85, #86, #87, #88, #89, #90, #91, #95, #96, and PRs #43, and some others.  - KYC Match Scoring function has been discussed on #85 since June 2024, which is in line with KYC Match enhancement proposal approved in API Backlog WG.  → KYC Match Scoring function was agreed as optional function, and to create KYC Match v0.2.0 including Match Scoring function, PR #104 has been approved and merged.  - KYC Match Scoring: if Match result for a string-type attribute is 'false', a score on how close the string sent by the API request and the data stored in the MNO/CSP database are will be calculated and returned.    - Meta Release Fall-24 candidate is being discussed; Plans to include KYC Match v0.2 (basic Match + Match Scoring) and KYC Fill-in v0.1 (basic Fill-in). Issue#75 Deliverable R/O Current status / Achievements API Definition R Work in progress on KYC Match API, KYC Fill-in API, Age Verification API KYC Match and KYC Fill-in: release v0.1.0 is available here - KYC Match: provides the customer with the ability to compare information it has for a particular user with that owned by MNO - KYC Fill-in: provides the customer with the ability to request to MNO and receive KYC information for a particular user - KYC Match and Fill-in: upgrade to v0.1.1 with some corrections → Approved PR #100 (June 18, 2024) Age Verification: release v0.1.0 discussion ongoing - provides the customer with the ability to check age information for a particular user with MNO data - discussion on going, Issue #46, PR #50(initial API definition proposal)  API doc/user stories/testcases R Implementation R - Not yet API Reviews and extensions O - Note: Tenure API is in KnowYourCustomer Family. Tenure API will share some resources, e.g. meeting slots, with other KYC-SP APIs.  In addition, API Backlog WG is discussing on whether two new APIs, NumberRecycling API and ShtudownServiceStatus API, can fit in KnowYourCustomer Family. Public release r1.2 of API version 0.4.0 is now available (review completed at HomeDevicesQoD/pull/70). Release tracking page: https://wiki.camaraproject.org/display/CAM/home-devices-qod+v0.4.0 API doc/user stories/testcases R Existing test definitions for v0.4.0 are available in the repository. Implementation R N/A API Reviews and extensions O The 0.4.0 API version is only intended to conform previous 0.3.0 version to the Commonalities and ICM guidelines included in the Meta Release "Fall24". No new features are added.

KnowYourCustomer/Tenure

LocationInsights

NetworkAccessManagement NetworkAccessManagement

NetworkSliceBooking

NumberVerification

OTPValidationAPI

PopulationDensityData

QualityOnDemand

RegionDeviceCount

ShortMessageService

SimpleEdgeDiscovery

SimSwap

Expand

Deliverable R/O Current status / Achievements API Definition R Public release r1.2 featuring: sim-swap version 1.0.0 is now available (review completed at SimSwap/pull/148) - version stable sim-swap-subscriptions version 0.1.0 is now available (review completed at SimSwap/pull/148) - version initial Release tracking page: sim-swap v1.0.0 0.11.0-alpha.1 near completion, wip  available   API doc/user stories/testcases Gherkin .feature available, user story to be ported from EdgeCloud Implementation two operators: R0.93 (done) and v0.9.2 (underway)  API Reviews and extensions 0.11.0-alpha.1 is mostly alignment with Commonalities 0.4-rc.1

SimSwap

SiteToCloudVPN

VerifiedCaller

Expand

Deliverable R/O Current Status / Achievements API Definition O API API  definition in progress:progress： https://github.com/camaraproject/SiteToCloudVPNVerifiedCaller/issues/96 API doc/user stories/testcases O API Doc and User Stories:      https://github.com/camaraproject/SiteToCloudVPN/pull/1scope doc: In the first stage, cover the message in the "Business card" https://github.com/camaraproject/SiteToCloudVPN/pull/2https://github.com/camaraproject/SiteToCloudVPNVerifiedCaller/pull/38 Implementation O Not yet API Reviews and extensions O Not yet

WebRTC

WebRTC