Attendees & Representation

Type @ and your name to indicate your attendance

Community: @Ludovic Robert @David Morris @Eric Murray @Fernando Prado Cabrillo @Joachim Dahlgren @Sachin kumar

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

• #262 Make lastStatusTime mandatory in 200 responses of the status APIs

  • It's not a breaking change, so it can be added in the next release

Open issues

• #268 Remove "Generic High Entropy Secret"

• #250 Test statement for device-roaming-status & device-reachability-status APIs

  • We have them from DT.

  • We keep the issue open to have more statement.

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

  • Tabled for discussion post current release

  • We can work on this one to make proposal on event type alignement with the ‘sync’ API

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

  • Discussion still open in commonalities

    • Proposal: let’s wait to commonalities output - if no output from it we can discuss in this WG how to adapt

  • 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

  • → move to discussion

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

  • no update

  • @Eric Murray will check if the issue is still relevant, else transfer to a discussion (or close the issue)

Release Management

Public release r2.2 was published on Mar 14, 2025

DeviceDataVolume

Open PRs

Open Issues

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

Release Management

Alpha release r1.1 was published on Jan 16, 2025

Should be part of the Autumn 25 release

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 fall 2025

• See Meta-release Fall25

• M3 (first release candidate) target date: Jun 21, 2025

AOB

• Move forward on splitting the device status repo in 3 distincts repos - to be check with @Akos Hunyadi

Action items