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

• #158 Create connected-network-type.yaml

  • Ready to be merged

  • Alignment of error codes with Commonalities 0.5.0 will be done in separate PR

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

  • Should be updated to align with #158

  • Alignment with error codes and subscription template of Commonalities 0.5.0 will be done in separate PR

• #232 Update device error model

• #231 Update device-reachability-status-subscriptions.yam

• #228 Update info.description

  • The current description should be added to other APIs too

Open issues

• #234 Create basic test specifications for network-type APIs

• #230 Align Device Errors with last Commonalities agreement for Spring25

  • Corresponding PR is open

• #224 Scope for Spring25 release

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

• #222 Enhance API documentation

  • Ongoing discussion about the behavior with initialEvent in roaming-status-subscriptions

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

  • Should be fixed in next MR

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

  • Linked to 222 discussion

• #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

• #143 Extend: Device Status Connectivity with Standard 

  • PRs are open

  • Details about implementation should be provided

• #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

• -

Open Issues

• #11 Scope for Spring25 release

• #12 Create basic test specifications

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: 21.12.2024

• M4 (public release) target date: 28.02.2025

AOB

• Next DeviceStatus call on 15.01.2025

Action items

• Akos Hunyadi Create DeviceStatus issue to align subscriptions for all 3 APIs with Commonalities 0.5.0
• Akos Hunyadi Check for additional necessary (and missing) assets for the stable versions
• Akos Hunyadi Create issue for adapting error codes for network-type APIs
• Ludovic Robert Create PR to add description for initialEvent to all 3 subscription APIs
• Eric Murray Create alpha-release for DeviceDataVolume