General Updates
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Fund Updates Casey Cain Evan Harrison
Working Group Updates
Technical Steering Committee Herbert Damker Updated
- 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
Marketing (Outreach Committee) Markus Kümmerle
Deliverable
Current status / Achievements
Documents
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
PRs
2024 event list finalized:: https://wiki.camaraproject.org/display/CAM/2024+Event+Tracker
2024 marketing budget is approved
New versions of CAMARA presentation and CAMARA onepager
New issues
Announcements
Content is moved in dedicated Marketing repository: https://github.com/camaraproject/Marketing
Release Management Tanja de Groot Updated
- 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)
Commonalities Rafal Artych Updated:
- 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
Deliverable
Current status / Achievements
Documents
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
New Issues
not updated, see https://github.com/camaraproject/Commonalities/issues
Announcements
Release 0.4.0-alpha.1 Changelog:
This version introduces Event Subscription model based onCloudEvents Subscriptions API draftAPIBacklog Ricardo Serrano Gutierrez Updated:
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)
IdentityAndConsentManagement Axel Nennker Updated:
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. |
Status of Sub Project
BlockchainPublicAddress Pedro Diez Garcia Updated:
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 |
CallForwardingSignal Fabrizio Moggio Updated:
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 |
Implementation | O | NA (Optional according to CAMARA Readiness Checklist) |
API Reviews and extensions | O | NA |
CarrierBillingCheckOut Pedro Diez GarciaUpdated:
Deliverable | R/O | Current status / Achievements |
API Definition | R | API spec: • Current API Spec Release is v0.2.1. Working in Payment v0.3.0 and refund functionality |
API doc/user stories/testcases | R | Use Cases - First version available |
Implementation | R | Not yet |
API Reviews and extensions | O | 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 - Issues#154 and #158 - Alignments with Commonalities Meta-Release Fall24 (Notifications & Errors) |
ClickToDial @hanbai Updated:
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 |
ConnectivityInsights Mahesh Chapalamadugu Updated:
Deliverable | R/O | Current status / Achievements |
API Definition | R | 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 | Not Yet |
API Reviews and extensions | O |
|
DeviceIdentifier Eric Murray Updated:
Deliverable
R/O
Current status / Achievements
API Definition
R
Device Identifier API: Initial pre-release version 0.1.0 now published here
|
Working Groups
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Sub Projects
Table of Contents | ||||
---|---|---|---|---|
|
Children Display |
---|
General Updates
Working Group Updates
Sub Project Updates
- 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
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
API doc/user stories/testcases
R
Device Identifier API:
- 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
DeviceLocation Jose Luis Urien Updated:
Last location-verification family release: 0.2.0, including 3 APIs: 0location-retrieval v0.0- All API documentation consolidated within spec.
- Working on test plans for the 3 APIs
- 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
0.6.0-alpha.1 -
- Endpoints renamed
- New response parameter lastStatusTime
Separate endpoints into different APIs (#125)
Alignment to Commonalities 0.4.0
Implementation
R
Please add to https://github.com/camaraproject/DeviceSwap/issues/1 and on the mailing list if interested to support
EdgeCloud @cristina Updated:
API doc/user stories/testcases
R
Implementation
R
API Reviews and extensions
O
HomeDevicesQoD Jesús Peña Updated:
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
- The next expected activity is to make the necessary adjustments for the Fall24 meta-release to align with CAMARA Commonalities and IdentityAndConsentManagement.
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
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#81.Implementation
R
- Note: Tenure API is in KnowYourCustomer Family. It will share some resources, e.g. meeting slots
NetworkSliceBooking Shuting Qing Updated:
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 |
NumberVerification Updated:
Deliverable
R/O
Current status / Achievements
API Definition
R
Current release is v0.3.1: https://github.com/camaraproject/NumberVerification/releases/tag/v0.3.1
API doc/user stories/testcases
R
Documentation integrated into YAML file
Implementation
R
N/A
API Reviews and extensions
- 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
OTPvalidationAPI @ Updated:
Deliverable
githubcom/OTPvalidationAPIreleases/tag/5https://github.com/camaraproject/OTPvalidationAPI/blob/v0.5.0/documentation/API_documentation/OTP_SMS_API.mdVersion v06 in work, only minor changes so far, adapting to Commonalities changes
PopulationDensityData Jorge Garcia Hospital Updated:
RC2 version under review → RC2
First version to be released soon :
Prediction/Extrapolation algorithm draft proposal under review → AlgorithmTest cases pendingReference Use case closed in API documentation.
N/AInclusion inQualityOnDemand Herbert Damker Updated:
Deliverable | R/O | Current status / Achievements |
API Definition | R | Current release: v0.10.1 |
API doc/user stories/testcases | R | Documentation inline within API OAS |
Implementation(s) | R | Three repositories for Provider Implementations (PI):
|
API Reviews and extensions | O |
|
RegionDeviceCount Fan Yang Udpated:
Deliverable
R/O
Current status / Achievements
API Definition
R
R
API Doc and User Stories:
testcasesgithubcamaraproject/RegionUserCount/pull/3Implementation
R
Not Yet
Not Yet
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 - 6
PR Open - 1
SimSwap @ Updated:
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 | N/A |
API Reviews and extensions | O | Version 0.5.0 work in progress, adding subscriptions, test cases, adapting to Commonalities, etc |
SiteToCloudVPN @dan xu Updated:
issues9 Stories: 1/SiteToCloudVPN/pull/2SiteToCloudVPNpull3ImplementationNot yet
API Reviews and extensions
O
Not yet
VerifiedCaller @Dan Xu Updated:
Deliverable
R/O
Current Status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
API Definition:
WebRTC/code/API_definitions at v0.1.0 · camaraproject/WebRTC ()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
NetworkAccessManagement @justin pace Updated:
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
Implementation
O
N/A
API Reviews and extensions
O
N/A
LocationInsight Fan Yang Updated:
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
SimpleEdgeDiscovery Kevin Smith Updated:
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation
API Reviews and extensions
Tenure Updated:
Deliverable
R/O
Current status / Achievements
API Definition
API doc/user stories/testcases
Implementation