LIGHTWEIGHTM2M Firmware Update (5)

RELEASE VERSION OVERVIEW
  Version 1.0 Functionality
  Version 1.0.1 Functionality
  Version 1.0.2 Functionality
   * Editorial and metadata updates.
  Version 1.0.3 Functionality
  Version 1.1 Functionality
   * Resource ID (5), extending Update Result enumeration
   * New Resources IDs: 10, 11, 12 and 13

DOCUMENT LISTING FOR SUP LightweightM2M Firmware Update v1.1
Publication Considerations
  Doc Reference
   * [LWM2M_Firmware_Update_XML]

  Permanent Document Reference:
   * File: OMA-SUP-XML_5-V1_1-20201110-A.xml
   * Path: http://www.openmobilealliance.org/release/ObjLwM2M_Firmware/

  OMNA LwM2M Registry:
   * File: 5.xml
   * Path: https://github.com/OpenMobileAlliance/lwm2m-registry

OMNA Considerations
The OMNA registry needs to add and maintain the following Objects:
  * Object URN Identifier: urn:oma:lwm2m:oma:5:1.1
  * Object Name: Firmware Update
  * Object Specification URL: OMA-TS-LightweightM2M-Core-V1_2
  * Description: This LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software.
The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification.
A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose.
A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object.
A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.