Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Working GroupsGeneral Updates
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Working Groups
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Sub Projects
| Table of Contents | ||||
|---|---|---|---|---|
|
Sub Projects
| Table of Contents | ||||
|---|---|---|---|---|
|
| Children Display |
|---|
General Updates
New Participants
Updated: //
Fund Updates
Updated //
Working Group Updates
- 1126 people from 396 companies have joined CAMARA
- 1658 people and 337 companies are in (first) talks
- Logos see landscape
- New General Member - Indykite
- New Participating Organizations - LFOD and phine.tech
Updated:
Fund Updates
- Status of the technical project (same as below)
- Budget approvals
Updated
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
Updated
Working Group Updates
Technical Steering Committee
- EasyCLA introduction - Board decision done, is ready for deployment
- GitHub teams for all *_maintainers and *_codeowners for all Sub Projects created
- Few outstanding invitations. Please ensure that you receive notifications emails from GitHub!
- Current proposals to improve the Governance in discussion:
- API Sub Project = one to n API repositories (for API development and release purposes) (Governance/issues/142)
- API Project lifecycle with Sandbox and Incubated (Governance/issues/129)
- API Backlog
- Now in https://github.com/camaraproject/APIBacklog - please direct all new issues and PR there!
- New API repositories for Tenure (part of KYC family) and VerifiedCaller approved and created
- Commonalities
- Alpha version of v0.4.0 released, please consider the changes in your Sub Projects!
- Some further topics for the v0.4.0 release in work
- Identity & Consent Management (ICM)
- Release Management
- See next page
Updated
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
- Release Management
- 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)
- 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)
Updated:
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
- Alignment with Identity and Consent Management
- Error model alignment - chapter 6 of API Design Guidelines
- Annoucements
This version introduces Event Subscription model based on CloudEvents Subscriptions API draft
Updated:
APIBacklog
DocumentsLive table for API backlog availablehere. Stable version.Accepted API proposals stored here.
- 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)
- Application templates for those API proposals which have not been discussed yet in TSC.
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)
- /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 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.
Updated:
Commonalities
- Version 0.4.0 of Commonalities published
- New issues:
- 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
Updated:
APIBacklog
- Documents
- 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).
- 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
Updated:
Sub Project Updates
BlockchainPublicAddress
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
CallForwardingSignal
| Expand |
|---|
Updated:
IdentityAndConsentManagement
Deliverable | R/O | Current status / Achievements |
API Definition | R | N/A yet. If identified, a proposal will be made once core issues are clarified and closed. |
API doc/user stories/testcases | R | 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. OpenAPI securitySchemes ICM guidelines relevant information included in Commonalities API Design Guidelines documentation. |
Implementation | R | N/A yet |
API Reviews and extensions | O | 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. |
Updated:
Sub Project Updates
BlockchainPublicAddress
Deliverable | R/O | Current status / Achievements |
API Definition | R | Working in next release: v0.2.0-wip No additional Business Requirements so far. Working in technical enhancements in the meantime (see latest section) |
API doc/user stories/testcases | R | 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 | 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 |
Updated:
CallForwardingSignal
Deliverable | R/O | Current status / Achievements |
API Definition | R | Released and approved v0.1.6-wip 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? |
API doc/user stories/testcases | R | User Story and Documentation released. Draft Test Case |
Implementation | O | NA (Optional according to CAMARA Readiness Checklist) |
API Reviews and extensions | O | NA |
Updated:
|
API spec:
|
|
Use Cases - First version available
Implementation
R
|
Several Open Issues, listed here. Main tracks in the short-term in:
- Issue#104 - Carrier Billing Refunds. PR in the last mile, mainly pending alignment topics and final review of solution
- Issue#155 - Carrier Billing Scope for MetaRelease Fall24.
- Issues#154 and #158 - Alignments with Commonalities Meta-Release Fall24 (Notifications & Errors)
Updated:
|
Updated:
CarrierBillingCheckOut
ClickToDial
| 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.
|
TBD part will be added in next version, format needs to be adjusted.
Test Cases - Work in progress
|
|
ClickToDial
| Expand |
|---|
|
Working in release: 0.4.0 which is targeted to be a tagged release
API doc/user stories/testcases
R
Documentation is now available as part of the yaml
user stories available.
test cases, not yet
Implementation
R
|
- 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.
|
ConnectivityInsights
| Expand |
|---|
|
Device Identifier API: Initial pre-release version 0.1.0 now published here
- Two separate endpoints now defined for the two identified use cases:
- retrieve-identifier, to get the IMEI (and other optional information)
- retrieve-type, to get the Type Approval Code (and other optional information)
- lastChecked field added to provide timestamp for data validity
- Security scheme and scopes now defined for all endpoints
|
Updated:
DeviceIdentifier
| Expand | ||||
|---|---|---|---|---|
|
IMEI Fraud API:
- API referred back to GSMA OGW Product Workstream for review
- If resubmitted to CAMARA (via API Backlog WG), will be allocated a separate repository
|
- Documentation embedded within OAS definition
- Test cases will be proposed before next meeting
- PR #59 adds User Stories for the two identified use cases
Implementation
R
No implementations yet available
API Reviews and extensions
O
None
|
Updated:
DeviceLocation
Updated:
DeviceLocation
| Expand |
|---|
|
|
|
|
|
(next minor release of the 3 APIs expected for meta-release Fall24)
|
|
|
|
|
|
No contribution yet
API Reviews and extensions
O
- 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
Updated:
|
Updated:
DeviceStatus
DeviceStatus
Deliverable
| Expand | |
|---|---|
|
|
|
|
|
Separate endpoints into different APIs (#125)
Alignment to Commonalities 0.4.0
DeviceSwap
| Expand |
|---|
Updated:
@Noel
|
Updated:
@Wassam
EdgeCloud
| Expand | |||||
|---|---|---|---|---|---|
|
Implementation
R
API Reviews and extensions
O
Updated:
@Christina
HomeDevicesQoD
Deliverable | R/O | Current status / Achievements |
API Definition | R | Current API Spec release is v0.3.0 |
API doc/user stories/testcases | R | Existing test definitions are available in the repository. |
Implementation | R | N/A |
API Reviews and extensions | O |
|
Updated:
|
Updated:
HomeDevicesQoD
| Expand |
|---|
|
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
- discussion on going, Issue #46, PR #50(initial API definition proposal)- 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.
- Age Verification v0.1.0: User story is being discussed; Issue
|
Updated:
KnowYourCustomer/Tenure
#81.Implementation
R
- Not yet
API Reviews and extensions
O
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
- Note: Tenure API is in KnowYourCustomer Family. It will share some resources, e.g. meeting slots
|
Updated:
LocationInsights
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NetworkAccessManagement
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NetworkSliceBooking
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
NumberVerification
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
OTPValidationAPI
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
PopulationDensityData
| Expand |
|---|
Updated:
|
|
O
Work in progress in API Yaml and User Stories. Specs:
Initial API definition of create, query, and deletion session:
|
|
O
API Doc and User Stories:
ppt can be found in https://github.com/camaraproject/NetworkSliceBooking/pull/4, while md with reference scenario can be found in https://github.com/camaraproject/NetworkSliceBooking/pull/13
Implementation
O
|
|
QualityOnDemand
| Expand |
|---|
|
|
|
|
- Dawid Wróblewski left DT, Axel Nennker volunteered to step in
- Since April 4th 2024 WG meeting minutes are on: https://wiki.camaraproject.org/display/CAM/Number+Verification
- Working on next release 0.4.0 that contains changes introduced by community in past months
Updated:
@
|
Updated:
RegionDeviceCount
| Expand |
|---|
|
|
|
|
|
O
|
ShortMessageService
| Expand |
|---|
|
RC2 version under review → RC2
First version to be released soon :
- Prediction/Extrapolation algorithm draft proposal under review → Algorithm
API doc/user stories/testcases
R
Reference Use case closed in API documentation.
Test cases pending.
Implementation
R
N/A
API Reviews and extensions
O
- First release to be closed
- Inclusion in Meta-release
- Start creating scope for v2
Updated:
|
QualityOnDemand
Deliverable
R/O
Current status / Achievements
API Definition
R
API doc/user stories/testcases
R
Documentation inline within API OAS
Implementation(s)
R
Three repositories for Provider Implementations (PI):
|
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
Updated:
|
Updated:
SimpleEdgeDiscovery
| Expand |
|---|
API Specs will be discussed in first meeting:
https://github.com/camaraproject/RegionUserCount/pull/2
https://github.com/camaraproject/RegionUserCount/pull/5
|
R
|
R
API Doc and User Stories:
Implementation
R
Not Yet
API Reviews and extensions
|
Updated:
SimSwap
| Expand |
|---|
|
Send SMS API Spec is defined.
https://github.com/camaraproject/ShortMessageService/commits/main/code/API_definitions/SMS.yaml
SMS Delivery Notification Subscription API is defined.
|
|
API doc/user stories;
https://github.com/camaraproject/ShortMessageService/tree/main/documentation/API_documentation
Implementation
R
Not yet
API Reviews and extensions
PRs closed - 6
PR Open - 1
Updated:
|
SimSwap
Deliverable
R/O
Current status / Achievements
API Definition
R
Current release v0.4.0
https://github.com/camaraproject/SimSwap/releases/tag/v0.4.0
API doc/user stories/testcases
R
Documentation integrated into YAML file
Implementation
R
|
Version 0.5.0 work in progress, adding subscriptions, test cases, adapting to Commonalities, etc
|
Updated:
SiteToCloudVPN
| Expand |
|---|
Updated:
@
|
|
|
|
Updated:
13 Jun@Dan Xu
VerifiedCaller
| Expand | |||
|---|---|---|---|
|
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
Updated:
@Dan Xu
WebRTC
Deliverable
R/O
|
R
First and current release is ready v0.1.0.
camaraproject/WebRTC at v0.1.0 (github.com)
API Definition:
WebRTC/code/API_definitions at v0.1.0 · camaraproject/WebRTC (github.com)
API doc/user stories/testcases
R
Documentation is ready:
New API flow for user story is under review
Flow review - BYON by stroncoso-quobis · Pull Request #27 · camaraproject/WebRTC · GitHub
Implementation
R
- T-Mobile US is currently working in the implementation
- One more operator is needed to validate new versions of the API
API Reviews and extensions
O
Under discussion for next releases:
- Emergency calls to be supported is under proposal
- Propper error codes have been included
- Linting Rules script have been performed and is under review
- New version of the API have been merged recently. Preparing for META release
Updated:
NetworkAccessManagement
Deliverable
R/O
Current status / Achievements
API Definition
O
API definition in progress:
https://github.com/camaraproject/NetworkAccessManagement/pull/7
API doc/user stories/testcases
O
|
Updated:
@Dan Xu
WebRTC
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updated:
Implementation
O
N/A
API Reviews and extensions
O
N/A
Updated:
@Justin
LocationInsight
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
Updated:
SimpleEdgeDiscovery
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
Updated:
Tenure
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions