Page Comparison

...

Type @ and your name to indicate your attendance

Community: Ludovic Robert Fernando Prado Cabrillo Joachim Dahlgren Eric Murray

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

• #216 Prepare Release r1.3

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

    • Still in draft state

    • No clear information about the implementation yetDT to provide updates on the PR

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

    • No update

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?#214 Create patch release r1.3

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

  • Eric Murray provided Vodafone feedback for Reachability in the issue thread.

    • When a group of devices are group under one phone number, and this phone number is queried in the API, then if at least one device is reachable then we consider the number as reachable.

• #143 Extend: Device Status Connectivity with Standard 

  • PRs are open

  • Details about implementation should be provided

• #140 Extend the possible connectivity values 

  • Read for 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

Patchrelease The patch release r1.3

...

Content: #208, #210, #215

...

was created on 05.11.2024.

DeviceDataVolume

Open PRs

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

  • Review in progress - close to be done.

• #9 Add Commonalities linting rules

  • Could be merged → Eric will ask to Sachin kumar

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

...

Open PRs

• #7 Add linting rules

  • Could be merged→ Eric will ask to Sachin kumar

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

  • Eric Murray will propose for the next meeting some ideas on how Device Quality Indicator could work.

Release Management

Meta Release

...

• See Meta-release Spring25

• M3 (first release candidate) target date: 15.12.2024

• Question from Joachim Dahlgren about shifting to v1.0 for some of our API. This is probable in the next meta-release as there are live implementation.

AOB

Action items