Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backlog WG] Question about IoT Data Transfer Activation #13

Closed
jgarciahospital opened this issue Dec 7, 2024 · 3 comments
Closed

[Backlog WG] Question about IoT Data Transfer Activation #13

jgarciahospital opened this issue Dec 7, 2024 · 3 comments
Labels
question Further information is requested

Comments

@jgarciahospital
Copy link
Contributor

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.

@jgarciahospital jgarciahospital added the question Further information is requested label Dec 7, 2024
@tlohmar
Copy link
Contributor

tlohmar commented Dec 9, 2024

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.

@FabrizioMoggio
Copy link

Sorry I didn't noticed this Issue and opened a new one: #14

let's continue there the discussion.

@jgarciahospital
Copy link
Contributor Author

Closing as discussed in #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants