2024-11-06 Device Status - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

Community: Ludovic Robert

Agenda

• Antitrust Policy

• 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

• #221 [device-reachability-status]: support for reachability with multiple connectivity-types

• New APIs - retrieve network type

  • #158 Create connected-network-type.yaml

    • Review in progress with ongoing discussion

    • DT to provide updates on the PR

  • #171 Create connected-network-type-subscriptions.yaml

Open issues

• #222 Enhance API documentation

• #220 Example Section Error: Status Should be "ACTIVE" for Synchronous Subscriptions

• #218 Explicit initialEvent for event type org.camaraproject.roaming-status-subscriptions.v0.roaming-status

• #217 Device Reachability Status - Is it mandatory to support all values?

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

• #143 Extend: Device Status Connectivity with Standard 

  • PRs are open

  • Details about implementation should be provided

• #140 Extend the possible connectivity values 

  • PR is open

• #138 How to respond if queried device does not have an active session?

  • No new activity

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

  • No new activity

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

Release Management

The patch release r1.3 has been created on 05.11.2024.

DeviceDataVolume

Open PRs

• #10 [Device Data Volume]: Initial version of api

  • Review in progress

• #9 Add Commonalities linting rules

Open Issues

• #7 Create initial version

  • Corresponding PR has been created: #10

Release Management

DeviceQualityIndicator

Open PRs

• #7 Add linting rules

Open Issues

• #6 Create initial version

  • Open for discussion

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

  • A mapping of input values to the expected output is needed

  • Idea: provide current and potential usable network performance

  • We need more use cases from the product teams

Release Management

Meta Release

Camara Meta Release spring 2025

• See Meta-release Spring25

• M3 (first release candidate) target date: 15.12.2024

AOB

Action items