- Created by Casey Cain, last modified by Herbert Damker on Oct 10, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 154 Next »
General Updates
Working Groups
Sub Projects
General Updates
New Participants
1147 people from 402 companies have joined CAMARA
1751 people and 370 companies are in (first) talks
Logos see landscape
New General Member
n/a
New Participating Organizations
Lytn
M1
Plusmo
Pryvx
Updated:
Fund Updates
EasyCLA deployed
If you’re not set up on EasyCLA yet, make sure you do a test PR in the GitHub EasyCLA repo.
Report issues to support@camaraproject.org
Wiki migration to Atlassian Cloud
If you are having trouble logging in or editing the wiki, please contact support@camaraproject.org
Updated
Technical Steering Committee
TSC Election 2024 has been started, currently nomination phase until October 18th. Eligible for nomination and voting are Maintainers of Sub Projects and Working Groups (10 “Sub Project Representatives”) and End User Council (3 “End User Representatives”). More information on TSC Election Overview.
Introduction of approach for (new) API Repositories with Sandbox / Incubated / Graduated with three stages of maturity agreed, draft PR to change Project Charter and ProjectStructuresAndRoles in work.
API Backlog
TSC approved DedicatedNetworks and CustomerInsights (originally proposed under the name “Telco Index”) as new API repositories
Repository QualityByDesign created (as approved in TSC 2024-09-05) as part of ConnectivityInsights Sub Project.
Commonalities
Scope definition for Spring25 release discussed, see Commonalities/issues/273
Identity & Consent Management (ICM)
Scope definition for Spring25 release discussed, see IdentityAndConsentManagement/issues/193
Release Management
Spring25
M0: Spring25 meta-release kickoff declared by TSC on October 3rd.
M1: Exception decided that it is sufficient to have PRs with the important changes ready by M1.
Fall24
M5 delivered on time (2024-09-15) for announcements in many public events in September
M6: see Release Management report below.
Updated
Working Group Updates
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://lf-camaraproject.atlassian.net/wiki/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
M5 - Fall24 meta-release publication: delivered on time on 2024-09-15
M6 - Feedback integration ongoing - preparation of r2.1 of the RM process for 2024-10-31 with main updates e.g.
improvements on the API release tracker
updates on the patch release process
introduction of release numbering for Commonalities, ICM and Release Management to be able to separate from versioning their documentation.
M0 - Spring25 meta-release kick-off declared by TSC on 2024-10-03.
M1 - delayed by 2 weeks to 2024-10-31 due to delay impacts from Fall24.
Exception: Commonalities and ICM will not yet have their pre-release ready but will produce PRs for the M1 date. The actual M1 pre-release as soon as possible after that.
From 2024-10-15 for critical PRs, and from M1 for other PRs, Sub Project teams are asked to review (and comment) the PRs.
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
Scope definition for Spring25 release, see https://github.com/camaraproject/Commonalities/issues/273
Issues:
All issues from the scope are marked with Spring25 label
Critical issues are additionally marked with priority label
PR that covers updates to subscriptions & notifications Commonalities/pull/313
Clean up and redesign of API Design Guidelines Commonalities/issues/306
Announcements
Correction of version 0.4.0 needed https://github.com/camaraproject/Commonalities/issues/301 PR: Commonalities/pull/311 ➡️ patch release of Commonalities (no impact on APIs)
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:
Proposals to be discussed in next TSC:
Dedicated Networks
Telco Scoring
Info: New repositories for DeviceQualityIndicator, DeviceDataVolume, SubscriptionStatus and QualityByDesign are created
Updated:
IdentityAndConsentManagement
Public release r0.2.1 as part of Meta-Release Fall24 available
Scope definition for Spring25 release (IdentityAndConsentManagement 0.3.0)
Proposed candidate topics:
Documentation improvements
CAMARA Security and Interoperability Profile - Restrictions
New features
Updated:
Sub Project Updates
BlockchainPublicAddress
Deliverable | R/O | Current status / Achievements |
API Definition | R | Working in next release: v0.2.0-wip
|
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 | Next Steps
- 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-up the binding relationship |
Updated:
CallForwardingSignal
Deliverable | R/O | Current status / Achievements |
API Definition | R | Released and approved the public release v0.2.0 The API has completed the Fall24 review and reached Fall24 M4. Release tag: r1.3 Next Steps: creation of a Stable version (Next Steps · camaraproject/CallForwardingSignal · Discussion #107 (github.com)) |
API doc/user stories/testcases | R | User Story and Documentation released. Readiness Checklist completed. Changelog. md file completed. Test Cases for the two endpoints released. YAML v0.2.0. |
Implementation | O | NA (Optional according to CAMARA Readiness Checklist) |
API Reviews and extensions | O | NA |
Updated:
CarrierBillingCheckOut
Deliverable | R/O | Current status / Achievements |
API Definition | R | M5 milestone achieved - Metarelease Fall24 |
API doc/user stories/testcases | R | Use Cases aligned with Release r1.2. |
Implementation | R | Not yet |
API Reviews and extensions | O | Open Issues, listed here. |
Updated:
ClickToDial
Deliverable | R/O | Current status / Achievements |
API Definition | R | Repository, Mailing list have been set up. API Definition - Draft version available Subsequent modifications and improvements will be made. |
API doc/user stories/testcases | R | 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 progress |
Implementation | R | No implementation available yet |
API Reviews and extensions | O | N/A |
Updated:
@Hanbai
ConnectivityInsights
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release of r1.2 of Connectivity Insights now available which includes 3 APIs:
|
API doc/user stories/testcases | R | Documentation is now available as part of the yaml user stories available. test cases available for each of the API. |
Implementation | R | Not Yet |
API Reviews and extensions | O | Open Issues: |
Updated:
CustomerInsights
Deliverable | Current status / Achievements |
---|---|
API Definition | Not yet, newly started repository |
API doc/user stories/testcases | Not yet |
Implementation |
|
API Reviews and extensions | Approved within TSC 2024-09-19 under the name “TelcoIndex”, “CustomerInsights” is the final name decided by the team and in APIBacklog WG. For scope see https://github.com/camaraproject/APIBacklog/pull/42 |
Updated:
(initial entry added by Herbert Damker) Pedro Díez García
DedicatedNetworks
Deliverable | Current status / Achievements |
---|---|
API Definition | Not yet, newly started repository |
API doc/user stories/testcases | Not yet |
Implementation |
|
API Reviews and extensions | Approved within TSC 2024-09-19, for scope see APIproposal_DedicatedNetworks.md |
Updated:
(initial entry added by Herbert Damker) Thorsten Lohmar
DeviceIdentifier
Deliverable | Current status / Achievements |
---|---|
API Definition | Device Identifier API: Initial public release 0.1.0 available
|
API doc/user stories/testcases | Device Identifier API:
|
Implementation | |
API Reviews and extensions | Open discussion on defining a PPID as a third option for the physical device identifier |
Updated:
DeviceLocation
Deliverable | R/O | Current status / Achievements |
API Definition | R | Release 1.2, including 3 APIs:
|
API doc/user stories/testcases | R |
|
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:
DeviceStatus
Deliverable | R/O | Current status / Achievements |
API Definition | R | Preparation of patch release r1.3 PR
2 New APIs - retrieve network type (+subscriptions) planned for Spring25 |
API doc/user stories/testcases | R | Basic testcases created according to API Testing Guidelines |
Implementation | R | No implementation available yet |
API Reviews and extensions | O | Open for discussion: |
DeviceSwap
Deliverable | R/O | Current status / Achievements |
API Definition | R | yaml for for a version 0.1-rc (or 0.1) is available Test definition will come soon |
API doc/user stories/testcases | R |
|
Implementation | R |
|
API Reviews and extensions | O | Please add to https://github.com/camaraproject/DeviceSwap/issues/1 and on the mailing list if interested to support |
Addition informations:
Device Swap had a lot of development lately.
We have worked on the documentation - basically to answer the main question: what is a device swap?
A clean yaml is available (Thanks to Jorge Garcia Hospital ).
First implementation are planned by operators
Updated:
EdgeCloud / SimpleEdgeDiscovery
SimpleEdgeDiscovery
Deliverable | R/O | Current status / Achievements |
API Definition |
| |
API doc/user stories/testcases |
| Gherkin .feature, user story and inline YAML documentation in r1.3 |
Implementation |
| A previous version of the API implemented by Telstra (Australia), Verizon (United States), KT (South Korea). GSMA certified implementation by Telstra (source: https://www.open-gateway.com/operators-map as of 2024-08-16). |
API Reviews and extensions |
| M4 r1.3 approved by Release Management and released |
EdgeCloud
Deliverable | R/O | Current status / Achievements |
API Definition | R | •Traffic Influence – 0.9.5-wip: PR to update the API with the new requirements is under review. - PR 278 •Edge Application Management – 0.9.3-wip: New functionalities are being added to extend the computational capabilities. PR 280 |
API doc/user stories/testcases | R |
|
Implementation | R | No provider implementation (PI) available yet.However: •Traffic Influence: Implementation under validation by Telecom Italia (TIM) |
API Reviews and extensions | O |
|
Updated:
HomeDevicesQoD
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release r1.2 of API version 0.4.0 is now available (review completed at HomeDevicesQoD/pull/70). Release tracking page: https://lf-camaraproject.atlassian.net/wiki/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. |
Updated:
KnowYourCustomer / Tenure
Deliverable | R/O | Current status / Achievements |
API Definition | R | Initial Public Release r1.3 provided for M4 of CAMARA Fall24 Meta-release, including
Age Verification v0.1.0 is WIP on Issue #46, PR #50 (initial API definition proposal) |
API doc/user stories/testcases | R | KYC Match / Fill-in Age Verification: User story is being discussed, in alignment with API definition discussion; Issue #81. |
Implementation | R | KYC Match / Fill-in: Live implementation status could be found here
|
API Reviews and extensions | O | Work for Spring25 Meta-release has started:
|
|
| Note:
|
Updated:
LocationInsights
Deliverable | R/O | Current status / Achievements |
API Definition |
| Most Frequent Location (MFL):
|
API doc/user stories/testcases |
| MFL: Included as part of first code proposal |
Implementation |
| N/A |
API Reviews and extensions |
| N/A |
Updated:
NetworkAccessManagement
Deliverable | R/O | Current status / Achievements |
API Definition | O | Working on first release. |
API doc/user stories/testcases | O | Documentation integrated into yaml file. |
Implementation | O | N/A |
API Reviews and extensions | O | N/A |
Updated:
NetworkSliceBooking
Deliverable | R/O | Current Status / Achievements |
API Definition | O | Work in progress in API Yaml and User Stories. Specs: Initial API definition of create, query, and deletion session: https://github.com/camaraproject/NetworkSliceBooking/pull/11 |
API doc/user stories/testcases | 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 | Not yet |
API Reviews and extensions | O | Not yet |
Updated:
NumberVerification
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release r1.3 of API version 1.0.0 is now available (review completed at Fixed Test Definition and patch release r1.3 by bigludo7 · Pull Request #148 · camaraproject/NumberVerification (github.com)). Release tracking page: number-verification v1.0.0 |
API doc/user stories/testcases | R | Documentation integrated into YAML file
Existing test definitions for v1.0.0 are available in the repository. |
Implementation | R | Live implementation could be fine here in:
|
API Reviews and extensions |
|
r1.2 is the public release for v1.0.0. This is the first public release of a stable version of the NumberVerification API |
Additional information:
The API definition is unchanged compared to r1.2. The patch release r1.3 fixes only 4 test definition scenarios
No a lot of update & evolution → We plan to suspend the bi-weekly call and work via the git
Discussion could be started again following outcome of EAP-AKE discussion from ICM
Updated:
OTPValidationAPI
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release r1.2 of API version 1.0.0 is now available (review completed at OTPValidation/pull/81). Release tracking page: one-time-password-sms v1.0.0 |
API doc/user stories/testcases | R | Documentation integrated into YAML file Existing test definitions for v1.0.0 are available in the repository. |
Implementation | R | Live implementation could be fine here in:
|
API Reviews and extensions | O |
r1.2 is the public release for v1.0.0. This is the first public release of a stable version of the OTPValidation API |
Additional information:
No update & evolution → We plan to suspend the bi-weekly call and work via the git
Updated:
PopulationDensityData
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release for fall24 r1.2 Including:
|
API doc/user stories/testcases | R | Reference Use case closed in API documentation. Test cases included |
Implementation | R | N/A |
API Reviews and extensions | O |
|
Updated:
QualityOnDemand
Deliverable | Current status / Achievements |
API Definition | Public release: r1.2 with
|
API doc/user stories/testcases | Documentation inline within API OAS |
Implementation(s) | Three repositories for Provider Implementations (PI):
|
API Reviews and extensions |
|
Updated:
RegionDeviceCount
Deliverable | R/O | Current status / Achievements |
API Definition | R | API Specs will be discussed in first meeting: |
API doc/user stories/testcases | R | API Doc and User Stories: |
Implementation | R | Not Yet |
API Reviews and extensions |
| Not Yet |
Updated:
ShortMessageService
Deliverable | R/O | Current status / Achievements |
API Definition | R | 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. 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 |
Updated:
SimpleEdgeDiscovery
(Part of EdgeCloud Sub Project … information to be moved there)
Deliverable | R/O | Current status / Achievements |
API Definition |
| |
API doc/user stories/testcases |
| Gherkin .feature, user story and inline YAML documentation in r1.3 |
Implementation |
| A previous version of the API implemented by Telstra (Australia), Verizon (United States), KT (South Korea). GSMA certified implementation by Telstra (source: https://www.open-gateway.com/operators-map as of 2024-08-16). |
API Reviews and extensions |
| M4 r1.3 approved by Release Management and released |
Updated:
SimSwap
Deliverable | R/O | Current status / Achievements |
API Definition | R | Public release r1.2 featuring:
Release tracking page: sim-swap v1.0.0
|
API doc/user stories/testcases | R | Documentation integrated into YAML file Existing test definitions for sim-swap v1.0.0 and sim-swap-subscriptions v0.1.0 are available in the repository. |
Implementation | R | Live implementation could be fine here in for sim-swap only:
|
API Reviews and extensions | O |
r1.2 is the public release for sim-swap v1.0.0. This is the first public release of a stable version of the Sim Swap API. This release features also initial version for sim-swap-subscriptions |
Additional information:
Only evolution is about adding a monitoredPeriod in the retrieve-date operation to accommodate privacy constraints
No a lot of update & evolution → We plan to suspend the bi-weekly call and work via the git
Updated:
SiteToCloudVPN
Deliverable | R/O | Current Status / Achievements |
API Definition | O | API definition in progress:
|
API doc/user stories/testcases | O | API Doc and User Stories:
https://github.com/camaraproject/SiteToCloudVPN/pull/1 https://github.com/camaraproject/SiteToCloudVPN/pull/2 |
Implementation | O | Both China Telecom Open lab and China Mobile Open lab are currently working in the implementation |
API Reviews and extensions | O | Not yet |
Updated:
@Dan Xu
VerifiedCaller
Deliverable | R/O | Current Status / Achievements |
API Definition | O | API definition in progress: |
API doc/user stories/testcases | O | API scope doc:
|
Implementation | O | Not yet |
API Reviews and extensions | O | Not yet |
Updated:
@Dan Xu
WebRTC
Deliverable | R/O | Current status / Achievements |
API Definition | R | Current release v0.1.1
API Definition: |
API doc/user stories/testcases | R | Documentation & UML ready:
API flow MVP ready (copying also to Confluence), helps to interpretate the protocol and define the API itself. |
Implementation | R |
|
API Reviews and extensions | O | Under discussion for next releases:
|
Updated:
- No labels