You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question was raised about posible overlap with Dedicated Networks Scope, as targeted to define an API for booking resources for a non-warranted connection for IoT, group of many devices at once, during a certain period.
Dedicated Network group is required to provide feedback.
The text was updated successfully, but these errors were encountered:
Several aspects resonate, like negotiating a time window and a maximum aggregate bitrate. The offered resources and capabilities for off-peak and peak hours seem to be more on the the Network Provider side, e.g. there can be different reasons for rejecting a request.
The slogans "background data transfers" and "non-urgent updates or downloads" could be translated to a need for "connectivity with a qos profile, suitable for a background data transfer".
I dont see a reason, why the dedicated network API cannot be used for a background data transfer use-case. However, the dedicated network API design is still in an early phase and there might be some use-case specific requirements.
During last Backlog meeting, new proposal of IoT Data Transfer Activation was presented
Question was raised about posible overlap with Dedicated Networks Scope, as targeted to define an API for booking resources for a non-warranted connection for IoT, group of many devices at once, during a certain period.
Dedicated Network group is required to provide feedback.
The text was updated successfully, but these errors were encountered: