...
Type @ and your name to indicate your attendance
Community: Ludovic Robert Fernando Prado Cabrillo Joachim Dahlgren Eric Murray
Agenda
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
...
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
No update
Open issues
...
#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
PR is open
#138 How to respond if queried device does not have an active session?
#115 /Connectivity API there is no indication for which particular subscriber event (DATA/SMS)
...
#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
Corresponding PR has been created: #10
...
Open PRs
Could be merged→ Eric will ask to Sachin kumar
Open Issues
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
...
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.