Page Comparison

...

Type @ and your name to indicate your attendance

Community: Akos HunyadiSachin kumar Ludovic Robert Joachim Dahlgren Eric Murray Fernando Prado Cabrillo Javier Carro Rafal Artych Huub Appelboom

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

...

• #216 Prepare Release r1.3

• New API - retrieve network type

  • #158 Create connected-network-type.yaml

    • Review in progress with ongoing discussion

    • Still in draft state

    • No clear information about the implementation yet

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

  • No clear information about the implementation yet

Open issues

Open issues

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

• #214 Create patch release r1.3

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

  • Ready Read for PR?.

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

...

• Content: #208, #210, #215

• Target date: CW40

DeviceDataVolume

Open PRs

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

Open Issues

• #7 Create initial version

  • Open for discussion

  • We should focus on the currently active volume

  • Both 2 and 3 legged tokens are possible, depending on the market

  • To be clarified the expected response. If it’s a static categorization, it might be out-dated soon

  • Rather check operation?

  • 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

  • Check draft PR from DT: provides all values separately, non-aggregated

  • Idea: provide current and potential usable network performance

  • We need more use cases from the product teams

  #3 Review initial CODEOWNERS and MAINTAINERS.md

Release Management

Meta Release

...

• See Meta-release Spring25

• M3 (first release candidate) target date: 15.12.2024

AOB

• Meeting time: Daylight Saving Time ends on 27.10 in Europe

  • Currently the meeting linked to the CET/CEST, but it should be based on UTC

  • Team chose UTC 9:00, which means 11:00 CEST and 10:00 CET

Action items

•  Akos Hunyadi after approval of the PR, create the Patch Release r1.3
•  Akos Hunyadi to check if DT is already preparing PR for #140, if not Eric Murray offered to create it.