Page Comparison

...

• #216 Prepare Release r1.3

• New API - retrieve network type

  • #158 Create connected-network-type.yaml

    • Review in progress with ongoing discussions

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

  • No clear information about the implementation yet

...

• #143 Extend: Device Status Connectivity with Standard 

  • PRs are open

  • Details about implementation should be provided

• #140 Extend the possible connectivity values 

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

...

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

Release Management

DeviceQualityIndicator

...

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

  • More use cases are necessary

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

  • Check draft PR

• #3 Review initial CODEOWNERS and MAINTAINERS.md

...