New Participants

• 1126 people from 396 companies have joined CAMARA
• 1658 people and 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
  • 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

• Identity & Consent Management (ICM)
• Public release r0.2.0 as part of Meta-Release Fall24 available
• 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
  • 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

  • Next 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 available latest 13 Sept 2024  on GitHub (new logos, new APIs, new slides including release management / meta release)

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

Release Management

• Meta-release schedule (see Meta-release Fall24 plan)

  • M4 - declared at TSC 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

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

    • Please indicate the topics to be included in Commonalities v.0.5.0 cf. Issue #273

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 Europe

• 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 (new logos, new slides including these from the CAMARA webinars)

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

Release Management

• Meta-release schedule 
  • M1 - 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.

Commonalities

• Release 0.4.0-alpha.1 of Commonalities was published on 10th of June
• Current PRs

  • Further topics for the v0.4.0 release

    Proposal to simplify device object and improve interoperability
    • Enhance API-Testing-Guidelines.md
    • Alignment with Release Management
      • Update versioning section in api design guidelines
    • Alignment with Identity and Consent Management
      • Adapt to ICM Security and Interoperability Profile
    • Error model alignment - chapter 6 of API Design Guidelines
• Annoucements

  • Release 0.4.0-alpha.1 Changelog:

  • This version introduces Event Subscription model based on CloudEvents Subscriptions API draft

    • Notification Subscription Template

APIBacklog

• Documents

  • Live table for API backlog availablehere. Stable version.

  • Accepted API proposals stored here. 

• New Issues
• Discussion

• OGW Drop

#3

• #4 APIs:

  #19 (Device Quality Indicator)OGW Drop #4 APIs:  #35

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

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

Governance:

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

  • Created new subproject/repos:

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

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

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

IdentityAndConsentManagement

Deliverable

N/A yet. 

If identified, a proposal will be made once core issues are clarified and closed.

New CAMARA "Security and Interoperablitity" profile created

Existing CAMARA "API access and user consent management document" updated according to the new profile.

New CAMARA ICM examples file created.

Release 0.2.0 scope definition for Fall 24 CAMARA meta-release is defined and available in IdentityAndConsentManagement/issues/146. Only one issue still under discussion to close all items under the scope of the meta-release.

CallForwardingSignal

BlockchainPublicAddress 

CarrierBillingCheckOut

CallForwardingSignal

ClickToDial

ConnectivityInsights

DeviceIdentifier

Expand

Repository, Mailing list have been set up.  API Definition - Draft version available Subsequent modifications and improvements will be made. API doc - First version contributed TBD part will be added in next version. Use Cases - First version available TBD part will be added in next version, format needs to be adjusted.            Test Cases - Work in progressNo implementation available yet Deliverable R/O Current status / Achievements API Definition R Device Identifier API: Initial public release 0.1.0 now available Working towards v0.2.0-alpha.1 Incorporate Commonalities WG recommendations on Simplification of Device object Remove format: uuid  requirement for x-correlator Update info.description API doc/user stories/testcases R Device Identifier API: Documentation embedded within OAS definition User Stories now added Additional user stories proposed: EUDI Wallet Device-Binding User Story Mobile Device Insurance User Story Test cases under development Implementation R China Unicom API Reviews and extensions O N/A Ongoing review for compliance with Commonalities 0.4.0 and Identity & Consent Management 0.2.0

DeviceLocation

Expand

Working in release: 0.4.0 which is targeted to be  a tagged release Documentation is now available as part of the yaml user stories available. test cases, not yetNot Yet Deliverable R/O Current status / Achievements API Definition R Release 1.2, including 3 APIs:  location-verification v1.0.0 location-retrieval v0.3.0 geofencing-subscriptions v0.3.0 API doc/user stories/testcases R All API documentation consolidated within spec User story for location-verification Test plans available for the 3 APIs. Implementation R location-verification noted the Fall24 EXCEPTION: Test results not available, as agreed in Release Management #89 Implementations of previous versions: Open Gateway Status Map API Reviews and extensions O updated yaml as per latest linting rules. Incorporated latest commonalities guidelines for subscriptions and notifications. separated out application-profiles into a different yaml to promote using it in other APIs.

DeviceStatus

Expand

Device Identifier API: Initial public release 0.1.0 now available API specification now being reviewed for compliance with updated Commonalities and Identity & Consent Management guidelines Rename X-Correlator to x-correlator Simplification of Device objectChina Unicom IMEI Fraud API: API removed from scope of Sub-Project for now, but has been resubmitted to API Backlog WG by Chenosis (see Issue #63) Deliverable R/O Current status / Achievements API Definition R Public Release 1.2 provided for M4 of Camara Fall24 with: device-roaming-status v0.6.0 device-roaming-status-subscriptions v0.6.0 device-reachability-status v0.6.0 device-reachability-status-subscriptions v0.6.0 API doc/user stories/testcases R Device Identifier API: Documentation embedded within OAS definition User Stories now added Test cases under development Basic testcases created according to API Testing Guidelines Implementation R No implementation available yet API Reviews and extensions O DeviceQualityIndicator, DeviceDataVolume

DeviceSwap

DeviceStatus

EdgeCloud

HomeDevicesQoD

Expand

•Traffic Influence – 9.5-wip :PR for v0.9.6-wip: addition of the "sourceTrafficFilters" object to help identify the traffic flow to influence. Minor updates following commonalities. •Edge Application Management – 0.9.3-wip:A couple of PRs have been created to improve the onboarding of an Application using K8s. •Application Endpoint Discovery: Update the device object according to the commonalities v0.4.0 definition and improve the API documentation to clarify its scope. Deliverable R/O Current status / Achievements API Definition R Public release r1.2 of API version 0. API doc/user stories/testcases R •The documentation was provided according to Commonalities v0.3.0 but will be updated according to the new requirements of Commonalities v.0.4.0. •Edge Cloud User Story now available to understand the relationship of the 4 current APIs Implementation R No provider implementation (PI) available yet.However: •Traffic Influence: Implementation under validation by Telecom Italia (TIM): •Simple Edge Discovery: Partly validated (Vodafone and Telstra). API Reviews and extensions O Exposure and Experience Management API:This API has recently received a contribution and has been renamed the Edge Service Discovery API. As the name suggests, the API has discovery functionalities but does not overlap with the current APIs but has advanced functionalities that can enhance Simple Edge and App Endpoint Discovery. We are discussing next steps. 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

HomeDevicesQoD

KnowYourCustomer

LocationInsights

NetworkAccessManagement

NetworkSliceBooking

NumberVerification

OTPValidationAPI

PopulationDensityData

QualityOnDemand

RegionDeviceCount

ShortMessageService

SimSwap

SiteToCloudVPN

SimpleEdgeDiscovery

SimSwap

SiteToCloudVPN

Expand
Deliverable R/O Current Status / Achievements API Definition API doc/user stories/testcases Implementation API Reviews and extensions

WebRTC

VerifiedCaller

Expand

status Merged reworked initial proposal with updates to align with commonalities:NetworkAccessManagement7 Created follow up issues for additional alignment: Add HATEOAS links Clarity on fine-grained and role-based scope format Remove CPE to remove network specific terms Documentation integrated into yaml file N/AN/A Deliverable R/O Current Status / Achievements API Definition O API  definition in progress： https://github.com/camaraproject/VerifiedCaller/issues/6 API doc/user stories/testcases O API scope doc: In the first stage, cover the message in the "Business card" https://github.com/camaraproject/ VerifiedCaller/pull/ API doc/user stories/testcases O 8 Implementation O Not yet API Reviews and extensions O Not yet

WebRTC

Expand

Most Frequent Location (MFL):  KO celebrated, including discussion of use cases and area type details First code proposal shared (PR#6) Deliverable R/O Current status / Achievements API Definition R Current release is ready v0.1.1. https://github.com/camaraproject/WebRTC/releases/tag/v0.1.1 API Definition: https://github.com/camaraproject/WebRTC/tree/v0.1.1/code/API_definitions API doc/user stories/testcases R MFL: Included as part of first code proposal Implementation N/A API Reviews and extensions N/A