search

OpenMobileAlliance / OMA_LwM2M_for_Developers

OMA LightweightM2M public resources.
http://openmobilealliance.github.io/OMA_LwM2M_for_Developers/
Other
238 stars 52 forks source link

Firmware Update object: Both Package and Package URI are mandatory #88

Closed jvermillard closed 7 years ago

jvermillard commented 8 years ago

Having both "package" and "Package URI" as mandatory in object 5 doesn't make sense. A device is likely to support one or another.

For example a LWPA or 6LowPAN device will have issue to implement the Package URI due to lack of TCP or HTTP support.

Or a large 4G modem/gateway will have very large firmware package (100MB) and it doesn't make sense to implement the "package" resource because it's impossible to send 100MB over CoAP reliably.

DavidAntliff commented 8 years ago

This suggests that a new relationship - perhaps "jointly mandatory" - could be considered, whereby a client must support at least one of the resources in the relationship.

Can't the package URI can be a CoAP URI for CoAP block-based download?

If block transfers use confirmable CoAP, 100MB is not impossible, although it may be painful in some environments.

hannestschofenig commented 7 years ago

We will investigate this requested functionality in LwM2M v1.1. Interested parties are welcome to join the standardization work on v1.1.