Device Update for IoT Hub agent overview
The Device Update agent consists of two conceptual layers:
- The interface layer builds on top of Azure IoT Plug and Play, allowing for messaging to flow between the Device Update agent and Device Update service.
- The platform layer is responsible for the high-level update actions of download, install, and apply that may be platform- or device-specific.
The interface layer
The interface layer is made up of the Device Update core interface and the Device information interface.
These interfaces rely on a configuration file for the device specific values that need to be reported to the Device Update services. For more information, see Device Update configuration file.
Device Update core interface
The Device Update core interface is the primary communication channel between the Device Update agent and services. For more information, see Device Update core interface.
Device information interface
The device information interface is used to implement the Azure IoT PnP DeviceInformation
interface. For more information, see Device information interface.
The platform Layer
The Linux platform layer integrates with Delivery Optimization for downloads and is used in our Raspberry Pi reference image, and all clients that run on Linux systems.
The Linux platform layer implementation can be found in the src/platform_layers/linux_platform_layer
and it integrates with the Delivery Optimization client for downloads.
This layer can integrate with different update handlers to implement the
installers. For instance, the SWUpdate
update handler, Apt
update handler, and Script
update handler.
If you choose to implement with your own downloader in place of Delivery Optimization, be sure to review the requirements for large file downloads.
Update handlers
Update handlers are used to invoke installers or commands to do an over-the-air update. You can either use existing update content handlers or implement a custom content handler that can invoke any installer and execute the over-the-air update needed for your use case.
Updating to latest Device Update agent
We have added many new capabilities to the Device Update agent in the latest public preview refresh agent (version 0.8.0). For more information, see the list of new capabilities.
If you're using the Device Update agent versions 0.6.0 or 0.7.0, please migrate to the latest agent version 0.8.0. For more information, see Migrate devices and groups to public preview refresh.
You can check the installed version of the Device Update agent and the Delivery Optimization agent in the device properties section of your IoT device twin. For more information, see device properties of the Device Update core interface.
Next Steps
Understand Device Update agent configuration file
You can use the following tutorials for a simple demonstration of Device Update for IoT Hub:
Image Update: Getting Started with Raspberry Pi 3 B+ Reference Yocto Image extensible via open source to build your own images for other architecture as needed.
Package Update: Getting Started using Ubuntu Server 18.04 x64 Package agent
Proxy Update: Getting Started using Device Update binary agent for downstream devices
Getting Started Using Ubuntu (18.04 x64) Simulator Reference Agent
Device Update for Azure IoT Hub tutorial for Azure-Real-Time-Operating-System