You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 90 Next »

General Updates

Working Groups

Sub Projects

Sub Projects

General Updates

New Participants

  • 1108 people from 393 companies have joined CAMARA
  • 1658 people and 335 companies are in (first) talks
  • Logos see landscape
  • New General Member - Aleph Zero

Updated:  

Markus Kümmerle 

Fund Updates

  • Status of the technical project (same as below)
  • Budget approvals

Updated  

Casey Cain Evan Harrison 

Technical Steering Committee

  • EasyCLA introduction
    • EasyCLA activation on all repositories end of August (postponed to not disturb the meta-release activities during vacation period where only a few Codeowners are available)
    • Please be prepared and initiate your CLA signing and/or approval by your company with a test PR in https://github.com/camaraproject/EasyCLA
  • API Backlog 
    • Repository for NumberRecycling was created (work to be started)
    • DeviceStatus gets two new API repositories for Device Quality Indicator and Device Data Volume
  • Commonalities
    • Second release candidate of Commonalities in preparation, with some bugfixes (see Bug fixes to be included in rc.2)
    • Decision taken within TSC about mandatory and optional endpoints within APIs:
      • An API Provider must implement all mandatory endpoints of an API and should implement the optional feature endpoints
      • Mandatory endpoints MUST not define 501 as a valid response
      • Optional endpoints should be avoided in the API definition by splitting an API into distinct YAML if resources are independent
      • Optional feature endpoints which can't be split into own API YAML should define 501 (NOT_IMPLEMENTED) as a valid response
  • Identity & Consent Management (ICM)
    • Second release candidate of of IdentityAndConsentManagement 0.2.0 is available (r0.2.0-rc.2 )
    • One change impacts all APIs: the mandatory text within the Info.description about Authorization and Authentication has been updated in the second release candidate. Please update your APIs proactively (Release Management is also checking this point)
  • Release Management 
    • Aug 15th: final closing date for approved M3 release PRs (with release candidates) - submit by Aug 10th to allow for release management review.
    • Aug 26th: latest date that APIs should provide their final release PRs (with the public API version, either initial or stable)
    • TSC on Sep 5th shall make final decisions on meta-release participation and stable status
    • see more details below

Updated

Herbert Damker 

Working Group Updates

Marketing (Outreach Committee)

Updated:  

Markus Kümmerle 

Jill Lovato

Release Management

  • Meta-release schedule (see Meta-release Fall24 plan)
    • M1 - Declared at TSC on 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 - Declared at TSC on 2024-07-11. Release-candidates of Commonalities and ICM are available.
    • A second release-candidate for both Commonalities and ICM are available and need to be checked by the Sub Projects
    • M3
      • 20 release-candidates APIs by 14 Sub Projects have been provided and are under release management review.
      • 1 SimpleEdgeDiscovery API and 4 DeviceStatus APIs have passed M3. M3 pre-releases can be used by implementors for testing and feedback.
    • M3 cut-off date for review requests of API release PRs is Aug 10th. 
    • M4 - Sub Projects can start to prepare their final release PR for the public API versions. M4 target date: 08-30.
  • Next steps
    • All Sub Projects that want to participate in the meta-release are asked to prepare their release PR, including
      • creating API release trackers for their APIs under their wiki pages,
      • preparing their API readiness checklist items
      • requesting release PR review by the Release Mgmt team by including "@release-management_maintainers" in the PR as a reviewer 
    • The Release Management team is progressing the release PR review. You can check the status in the review issue linked to your release PR.
    • Please bear with the reviewers due to holiday times and missing release managers.
  • Supporting documentation (for reference)

Updated:  

Tanja de Groot 

Commonalities

  • Release PR for 0.4.0-rc.2 of Commonalities is ready
  • New issues:

    • API misuse #258

    • Simplification/automation of linting ruleset updates in CAMARA repositories #263

    • Design Guidelines should provide guidance about sinkCredentials in returned/retrieved subscription objects #276

  • Announcements

Updated:  

Rafal Artych 

APIBacklog

  • Documents

    • Live table for API backlog available here. Stable version.

    • Accepted API proposals stored here. 

  • New Issues

    • 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), #18 (Receive SMS),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #60 (Dedicated Networks), 61 (network Info)

    • 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), #19 (Device Quality Indicator), #28 (Device Data Volume)

    • Proposals to be discussed in next TSC: 

      • Number Recycling → #54 (KDDI, Vodafone, DT)

    • Ongoing discussions. Proposals to be included under family....
      • DeviceStatus → #19 (Device Quality Indicator), #28 (Device Data Volume), #61 (network Info)
      • KYC → #54 (Number Recycling), #34 (Shutdown Service Status), #2 Tenure

Updated:  

Ricardo Serrano Gutierrez 

IdentityAndConsentManagement

  • Release of v0.2.0-rc.1 of IdentityAndConsentManagement was published on 11th of July
    • Please provide feedback on needed corrections for final release.
  • Release of r0.2.0-rc.2 of IdentityAndConsentManagement was published.
    • This is a bug fix release. 
    • Please provide feedback on needed corrections for final release.

Updated:  

Axel Nennker 

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.
  • ON-HOLD: 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

Some typos fixed in PR#55

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:  

Pedro Diez Garcia 

CallForwardingSignal

Deliverable

R/O

Current status / Achievements

API Definition

R

Released and approved v0.2.0-rc.2.

The API has completed the Fall24 review and has been released for the Fall 24 Meta Release.

Release tag: r1.2

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-rc.2.

Implementation

O

NA (Optional according to CAMARA Readiness Checklist)

API Reviews and extensions

O

NA

Updated:  

Fabrizio Moggio 

CarrierBillingCheckOut

Deliverable

R/O

Current status / Achievements

API Definition

R

API spec:

  • Current API Spec Release is v0.2.1.

M3 Milestone:

  • API Readiness Checklist Updated. PR#166 MERGED
  • Generation of Firts Release Candidate (r1.1). PR#167 ONGOING 

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. Next Steps focused on the M4 target

Updated:  

Pedro Diez Garcia 

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

work in progress for fall release of 0.4.0-rc.1

API doc/user stories/testcases

R

Documentation is now available as part of the yaml

user stories available.

Basic test cases created as per guidelines. 

Implementation

R

Not Yet

API Reviews and extensions

O

Open Issues:

Updated:  

Mahesh Chapalamadugu 

DeviceIdentifier

Deliverable

R/O

Current status / Achievements

API Definition

R

Device Identifier API: Initial public release 0.1.0 now available

API doc/user stories/testcases

R

Device Identifier API:

Implementation

R

China Unicom

API Reviews and extensions

O

Ongoing review for compliance with Commonalities 0.4.0 and Identity & Consent Management 0.2.0

Updated:  

Eric Murray 

DeviceLocation

Deliverable

R/O

Current status / Achievements

API Definition

R

PR ready (pending on Release Management approval) for API family release: r1.1, including 3 APIs: 
    • location-verification v1.0.0-rc1
    • location-retrieval v0.3.0-rc.1
    • geofencing-subscriptions v0.3.0-rc.1

API doc/user stories/testcases

R

  • All API documentation consolidated within spec.
  • PR includes test plans for location-verification and location-retrieval. geofencing-subscriptions tdb prior to M4 

Implementation

R

No contribution  yet

API Reviews and extensions

O

  • PR for r1.1
  • PRs with (very basic) proposal for test definitions for geofencing-subscriptions
  • Rest of issues and PRs on hold until end of meta-release Fall24

Updated:  

Jose Luis Urien 

DeviceStatus

Deliverable

R/O

Current status / Achievements

API Definition

R

Release 1.1 

    • device-roaming-status v0.6.0-rc.1
    • device-roaming-status-subscriptions v0.6.0-rc.1
    • device-reachability-status v0.6.0-rc.1
    • device-reachability-status-subscriptions v0.6.0-rc.1

API doc/user stories/testcases

R

Basic testcases prepared according to API Testing Guidelines

Implementation

R

No implementation available yet

API Reviews and extensions

O

PRs with ( basic) proposals for test definitions: #186, #187

Updated:  

Rafal Artych 


DeviceSwap

Deliverable

R/O

Current status / Achievements

API Definition

R

Work to be started

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

Updated:  

@Wassam


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

    • API Documentation inline within API OAS and commonalities v0.4.0
    • Documentation needs to be updated to be aligned with API-Readiness-Checklist requirements


Implementation

R

No provider implementation (PI) available yet.However:

•Traffic Influence: Implementation under validation by Telecom Italia (TIM)

API Reviews and extensions

O

    • Edge Discovery  Service API (old MEC Exposure & Experience Management API) has functionalities that are covered by existing APIs, but some new capabilities will be combined to enhance those APIs, especially the Application Endpoint Discovery API. Other capabilites will be proposed as new APIs within the Edge Cloud Family (still under discussion - Discussion 279 )
    • Traffic Influence planning is available in Discussion 282
    • All APIs of the Edge Cloud family are being revised to comply with commonalites v0.4.0.

Updated:  

Cristina Santana 

HomeDevicesQoD


Deliverable

R/O

Current status / Achievements

API Definition

R

Pre-release r1.1 of API version 0.4.0-rc.1 is now available (review completed at HomeDevicesQoD/pull/68).

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.

Updated:  

Jesús Peña 

KnowYourCustomer/Tenure

Deliverable

R/O

Current status / Achievements

API Definition

R

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

KYC Match and KYC Fill-in: release v0.1.1 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) 

API doc/user stories/testcases

R

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

- Age Verification v0.1.0: User story is being discussed, in alignment with API definition discussion; Issue #81.

Implementation

R

- TBC

API Reviews and extensions

O

- KYC Match and KYC Fill-in v0.2.0: work in progress for enhancements; Issues #38 #39, #47, #65, #66, #71, #77, #85, #86, #87, #88, #89, #90, #91, #95, #96, #101(closed), #123, #124, and PRs #43, and some others. 

- KYC Match Scoring: was agreed, and KYC Match v0.2.0 including Match Scoring function was created.  Related issues:  #85,  #112(closed).  Related PRs: #100, #104, #111 (all merged).  

- Match Scoring function: if Match result for a string-type attribute is 'false', a score on how close the string sent by the API request and the data stored in the MNO/CSP database are will be calculated and returned.   

- Meta Release Fall-24 candidate ; Work in progress to include KYC Match v0.2 (basic Match + Match Scoring) and KYC Fill-in v0.1 (basic Fill-in). 

- Related issues: #75, #107(closed), #116, #117, #120(closed), #125(closed), #129(closed) 

- Related PRs: #108(closed), #114(merged), #115, #118(merged), #119 -RC PR-, #121(merged), #126(merged), #130(merged)          



- Note: In addition to Tenure API, Number Recycling API has been in KnowYourCustomer Family.  They share some resources, e.g. meeting slots, with other KYC Family APIs.  Furthermore, Shutdown Service Status API will be in KYC Family, once it is approved by TSC to start its work.  Related issues: #109, some API Backlog issues/PRs  

Updated:  

 Toshiyasu Wakayama 

LocationInsights

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


MFL: Included as part of first code proposal

Implementation


N/A

API Reviews and extensions


N/A

Updated:  

Fan Yang Fernando Prado Cabrillo 

NetworkAccessManagement

Deliverable

R/O

Current status / Achievements

API Definition

O

Working on first release: Scope | PR

Additional alignment issues opened for first release:

Adding new maintainer: Ben Hepworth (CableLabs)

API doc/user stories/testcases

O

Documentation integrated into yaml file.

Implementation

O

N/A

API Reviews and extensions

O

N/A

Updated:  

Christopher Aubut @Justin Pace

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:  

Shuting Qing 

NumberVerification

Deliverable

R/O

Current status / Achievements

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

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

  • Additional documentation (Sequence diagram) in progress (PR94)

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

Implementation

R

Live implementation could be fine here in:

  • Brazil
  • China
  • Finland
  • France
  • Germany
  • Indonesia (Certified)
  • Italy
  • Netherlands
  • Singapour
  • South Africa (Certified)
  • Spain (Certified)
  • Thailand (Certified)

API Reviews and extensions


Updated:  

Ludovic Robert 

OTPvalidationAPI

Deliverable

R/O

Current status / Achievements

  • 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

API Definition

R

Current release v0.5.0
https://github.com/camaraproject/OTPvalidationAPI/releases/tag/v0.5.0

API doc/user stories/testcases

R

Documentation integrated into YAML file

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

  • Test Definition (PR61)
  • User story (TBD)

Implementation

R

Live implementation could be fine here in:

  • China (Certified)
  • Brazil
  • Italy
  • Saudi Arabia (Certified)
  • Sri Lanka

API Reviews and extensions

O

Change for meta-realse:

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

Updated:  

Ludovic Robert 

PopulationDensityData

Deliverable

R/O

Current status / Achievements

API Definition

R

Version 0.1 released: https://github.com/camaraproject/PopulationDensityData/releases/tag/v0.1.0

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

  • Prediction/Extrapolation algorithm draft proposal under review → Algorithm
  • ATP
  • User stories

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

  1. First release ready
  2. Start creating scope for v2

Updated:  

Jorge Garcia Hospital 

QualityOnDemand

Deliverable

R/O

Current status / Achievements

API Definition

R

Current public release: v0.10.1
https://github.com/camaraproject/QualityOnDemand/releases/tag/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

  • Release PR for r1.1 in review by release management. This pre-release will contain:
    • quality-on-demand v0.11.0-rc.1
    • qos-profiles v0.11.0-rc.1
    • qod-provisioning v0.1.0-rc.1

Updated:  

Herbert Damker 

RegionDeviceCount

Deliverable

R/O

Current status / Achievements

API Definition

R

API Specs will be discussed in first meeting:

https://github.com/camaraproject/RegionUserCount/pull/2

https://github.com/camaraproject/RegionUserCount/pull/5

API doc/user stories/testcases

R

API Doc and User Stories:

https://github.com/camaraproject/RegionUserCount/pull/3

Implementation

R

Not Yet

API Reviews and extensions


Not Yet

Updated:  

Fan Yang 

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.

https://github.com/camaraproject/ShortMessageService/blob/release-v0.1.0/code/API_definitions/sms-delivery-notification-subscription.yaml

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:  

Ramit Chawla Tet (Tetsuya) CHIBA 

SimpleEdgeDiscovery

Deliverable

R/O

Current status / Achievements

API Definition


v0.11.0-rc.1

API doc/user stories/testcases


Gherkin .feature, user story and inline YAML documentation in r1.1

Implementation


two operators: R0.93 (done) and v0.9.2 (underway) 

API Reviews and extensions


M3 r1.1 approved by Release Management and (pre)released

Updated:  

Kevin Smith 

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

https://github.com/camaraproject/SimSwap/releases/tag/v0.4.0

API doc/user stories/testcases

R

Documentation integrated into YAML file

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

  • Test Definition (PR70)
  • User story (TBD)

Implementation

R

Live implementation could be fine here in:

  • Argentina (Certified)
  • Brazil (Certified)
  • China (Certified)
  • Ethiopia
  • France
  • Germany (Certified)
  • Indonesia (Certified)
  • Italy
  • Netherlands
  • South Africa (Certified)
  • Spain (Certified)
  • Thailand (Certified)
  • UAE (Certified)
  • UK (Certified)
  • USA

API Reviews and extensions

O

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)

Updated:  

Ludovic Robert 

SiteToCloudVPN

Deliverable

R/O

Current Status / Achievements

API Definition

O

API definition in progress:

https://github.com/camaraproject/SiteToCloudVPN/issues/9

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

https://github.com/camaraproject/SiteToCloudVPN/pull/3

Implementation

O

Not yet

API Reviews and extensions

O

Not yet

Updated:  

@Dan Xu

VerifiedCaller

Deliverable

R/O

Current Status / Achievements

API Definition



API doc/user stories/testcases



Implementation



API Reviews and extensions



Updated:  

@Dan Xu

WebRTC

Deliverable

R/O

Current status / Achievements

API Definition

R

First and current release is ready v0.1.0.

camaraproject/WebRTC at v0.1.0 (github.com)

API Definition:

WebRTC v0.1.2

API doc/user stories/testcases

R

Documentation is ready:

WebRTC/documentation/API_documentation at main · camaraproject/WebRTC (github.com)

API flow is ready

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:

Updated:  

Ricardo Serrano Gutierrez 

  • No labels