Attendees & Representation

Type @ and your name to indicate your attendance

Community: @Akos Hunyadi @Sachin kumar David Morris (HLR Lookup) @Surajj Jaggernath @Maximilian Laue @Eric Murray @Fernando Prado Cabrillo @Ludovic Robert Sönke Peters (Vodafone)

Agenda

Antitrust Policy

• Action Items Review

• DeviceStatus

  • Open pull requests

  • Open issues

  • Release Management

• DeviceDataVolume

  • Open pull requests

  • Open issues

  • Release Management

• DeviceQualityIndicator

  • Open pull requests

  • Open issues

  • Release Management

• Meta Release

• AOB

Minutes

DeviceStatus

Open PRs

• #257 Remove INVALID_TOKEN_CONTEXT error-code based on Commonalities 0.5.0-rc.1

  • Ready to be merged

• #244 Prepare release r2.1

  • Ready for review

  • Some assets, needed for the public release, will be provided during the release candidate phase

    • Extended testcases for the 2 stable APIs

    • Use case descriptions for the 2 stable APIs

    • Test results for the 2 stable APIs
      It’s possible that these results are not available, check with Releasemanagement

• #255 Add extended test cases for device-roaming-status and device-reachability-status + refactor *.feature-files

  • Can be merged before or after RC1, not blocking RC1

Open issues

• #256 Remove INVALID_TOKEN_CONTEXT based on Commonalities v0.5.0-rc.1

  • PR #257 is open

• #253 Create user story for device-roaming-status and device-reachability-status APIs

  • Managed in PR244 or create new PR

  • Can be merged after RC1 too

• #248 [device-reachability-status-subscriptions] Align functionality with the retrieve API

  • Tabbed for discussion post current release

• #242 Create release r2.1 as RC1 for Spring25

  • Managed in PR244

• #236 Create extended test cases for device-roaming-status and device-reachability-status

  • PR #255 is open

• #224 Scope for Spring25 release

  • Team decided to go for stable versions with device-roaming-status and device-reachability-status

• #212 Support of Multi-SIM lines in DeviceStatus APIs

  • Discussion still open in commonalities

  • Target release is Spring25, with a description how the APIs work in a multi-SIM setup#138 How to respond if queried device does not have an active session?

  • Request documentation enhancement

• #119 How can a provider inform the ASP/aggregator about not implemented features in advance of the API call

  • no update

• #115 /Connectivity API there is no indication for which particular subscriber event (DATA/SMS)

  • no update

Release Management

The patch release r1.3 was created on 05.11.2024.

DeviceDataVolume

Open PRs

• #13 Basic test specifications for both Device Data Volume and Its Subscription

Open Issues

• #16 Feedback on release r1.1 review

• #14 Error Response Code 422 missing- Device Data Volume

• #12 Create basic test specifications

• #11 Initial release r1.1

Release Management

DeviceQualityIndicator

Open PRs

• -

Open Issues

• #6 Create initial version

  • Known use case: client wants to decide, whether a quality boost should be triggered or not (is it worth?)

  • No API spec can be provided for Spring25, target is Fall25

  • Collect use cases

Release Management

Meta Release

Camara Meta Release spring 2025

• See Meta-release Spring25

• M3 (first release candidate) target date: 17.01.2025

• M4 (public release) target date: 28.02.2025

AOB

Action items