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

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 (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

• Release Management 
  • M1 - Commonality alpha release available, ICM pending (target 06-15)
  • M2 - Release candidates of Commonalities and ICM (target 06-15 => potential shift to 07/15)
  • M3 - First release candidates of API Sub Projects (target 07-15)
  • M4 - Final release candidates of API Sub Projects (08-30)
• One stop documentation is here: Release Management Working Group
• New API release guidelines available in GitHub: ReleaseManagement/documentation/API_Release_Guidelines.md
• New API Readiness Checklist available in GitHub: ReleaseManagement/documentation/API-Readiness-Checklist.md
• API versioning guidelines within API Design Guidelines (Chapter 5), further details are within the wiki.
• All Sub Projects are asked to prepare for the Meta-Release cycle, including creating an API release tracker for each API within their wiki pages. See API release trackers and demo
• Milestones Fall24 (Meta-release Fall24)

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

• 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

APIBacklog

• Documents

  • Live table for API backlog availablehere. Stable version.

  • Accepted API proposals stored here. 

• New Issues
• 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),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #60 (Dedicated Networks), 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)

APIBacklog

DocumentsLive table for API backlog availablehere. Stable version.

• Accepted API proposals stored here. 

• New Issues
  • OGW Drop #3 APIs:  #19 (Device Quality Indicator)
  • OGW Drop #4 APIs:  #35 (5G New Calling), #34 (Shutdown Service Status), #41 (Telco Scoring), #50 (Device Management), #54 (Number Recycling)
  • Other APIs:  #17 (Consent and Measurement), #18 (Receive SMS),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #29 (Call Status), #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

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

BlockchainPublicAddress 

Deliverable

R/O

Current status / Achievements

API Definition

R

Working in next release: v0.2.0-wip

• No additional Business Requirements so far.
• ON-HOLD: Working in technical enhancements in the meantime (see latest section)

API doc/user stories/testcases

R

CallForwardingSignal

PR on 0.1.7-wip with two Intents supported:

Intent 1: is the unconditional call fwd service active on a specific phone number?

Intent 2: which is the status of the call forwarding for a specific phone number?

CarrierBillingCheckOut

Next outputs for MetaRelease Fall24:

• Merged PR#152, covering several issues and defining initial refund functionality
• Next steps are going into the generation of the next -rc spec versions

ClickToDial

ConnectivityInsights

1. updated yaml as per latest linting rules.
2. Incorporated latest commonalities guidelines for subscriptions and notifications.
3. separated out application-profiles into a different yaml to promote using it in other APIs.

DeviceIdentifier

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)

DeviceLocation

DeviceLocation

(next minor release of the 3 APIs expected for meta-release Fall24) 

• Alignments with Commonalities and transversal issues:
• Simplification of device object
• Alignment to new subscriptions model
• PRs with proposals for test definitions
• Clarifications for implementation guidelines. enhancement of properties descriptions, new error scenarios
• Support of polygon as input for geofencing-subcriptions, under discussion

DeviceStatus

• Endpoints renamed
• New response parameter lastStatusTime

Separate endpoints into different APIs (#125)

Alignment to Commonalities 0.4.0

DeviceSwap

EdgeCloud

•Application Endpoint Discovery: Update the device object according to the commonalities v0.4.0 definition and improve the API documentation to clarify its scope.

Implementation

•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

•Simple Edge Discovery: Partly validated (Vodafone and Telstra).

HomeDevicesQoD

KnowYourCustomer/Tenure

Work in progress on KYC Match API, KYC Fill-in API, Age Verification API

- 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

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

- topic intensively discussed: the end-user whose age the API user wants to check may be different from the contract owner.  For this, scoring function by using additional input (givenName, middleNames, email etc.) is considered, which will be an optional method, because it is not always required. 

API doc/user stories/testcases

R

- KYC Match / Fill-in v0.1.0: API doc embedded in YAML, user stories available, testcases not yet available.

Implementation

R

- Not yet

API Reviews and extensions

O

- Note: Tenure API is in KnowYourCustomer Family. It will share some resources, e.g. meeting slots

LocationInsights

NetworkAccessManagement

NetworkSliceBooking

NumberVerification

R/O

Current status / Achievements

In order to align with Release Management check list, work in progress:

• Test Definition (issue104)
• User story (PR118)

OTPValidationAPI

• Preparing all asset for Meta Release (issue62)
  • Target to have a stable maturity-level version (need to go thru CAMARA TSC)
  • Candidate version is v0.6

In order to align with Release Management check list, work in progress:

Change for meta-realse:

• Alignement with commonalities & icm
  #56 Align securitySchemes and Auth description with commonalities and ICM
  #50 Make '+' mandatory

PopulationDensityData

PopulationDensityData

Working on ensuring that the API is ready for meta-release :

QualityOnDemand

• QualityOnDemand_PI1 by Deutsche Telekom (updated to v0.10.1)
• QualityOnDemand_PI2 by Orange
• QualityOnDemand_PI3 by Spry Fox Networks

API Reviews and extensions

O

• v0.11.0 - Scope definition within QualityOnDemand/issues/292
• Split into 2 APIs Quality-On-Demand and QoS Profiles done
• Consolidation issue for duration, extentDuration, time formats in review
• Update Security schemes, scopes according to Commonalities & ICM in review
• Some further enhancements to be done
• PR for new API “QoD provision mode” available for review

RegionDeviceCount

ShortMessageService

Current status / Achievements

API Definition

R

Alpha release-v0.1.0 - camaraproject/ShortMessageService at release-v0.1.0 (github.com)

API doc/user stories/testcases

R

API doc/user stories;

https://github.com/camaraproject/ShortMessageService/tree/main/documentation/API_documentation

Implementation

R

Not yet

API Reviews and extensions

PRs closed - 8

PR Open - 1

SimpleEdgeDiscovery

SimSwap

SimSwap

Deliverable

R/O

Current status / Achievements

• Preparing all asset for Meta Release (issue62)
  • Target to have a stable maturity-level version for the sims swap api (need to go thru CAMARA TSC) (not for sim swap subscription API)
  • Candidate version is v0.5
• For the simswap-notification-subscription we are aligning the API model with cloud events structure (PR111)

API Definition

R

Current release v0.4.0

In order to align with Release Management check list, work in progress for SIM swap

Change for meta-release for SIM swap:

• Alignement with commonalities & icm
  • Align securitySchemes and Auth description with commonalities and ICM
  • Make '+' mandatory (PR100)
  • Add API wildcard scope in the yam (PR103)

SiteToCloudVPN

Implementation

O

Not yet

API Reviews and extensions

O

Not yet

WebRTC

VerifiedCaller

WebRTC

NetworkAccessManagement 

Deliverable

R/O

Current status / Achievements

API Definition

O

Implementation

O

N/A

API Reviews and extensions

O

N/A

LocationInsight

Deliverable

R/O

Current status / Achievements

API Definition

Most Frequent Location (MFL): 

• KO celebrated, including discussion of use cases and area type details
• First code proposal shared (PR#6)

API doc/user stories/testcases

Implementation