RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Papers & Presentations Archive
The primary module that is responsible for discovering and managing updating images on various devices. On initialization or at some configured times, the Device Update manager will scan the update sub-filesystem of the rootfs for new images and announce the found images on the IARM bus. This can be extended to communicating with a server to identify updates on an update server that can be pulled down and announced. The Device Update Manager will also be able to aggregate data about devices that are downloaded and downloaded sessions that are executed. It will be able to gate when downloads go to devices and when they are loaded on devices. And it will be able to officiate between multiple Device Update Proxy's requesting downloads over low bandwidth or highly utilized mediums.
Each class of devices will have a single Device Update Proxy responsible for managing updates to its child devices. A Device Update Proxy can represent multiple devices as long as they are in the same class. An example of this is remote controls. The Device Update Proxy will be responsible for listening for announcements and accepting updates for specific devices that are ready for an update. It is assumed the Device Update Proxy will know the version of devices it manages and can either contact them to notify them of the update or receive polls from them asking about an update. The Device Update Proxy is responsible for understanding the physical transport connecting devices to the STB and whether downloads to those devices must be serialized or can be parallelized (and how many can be parallelized). The Device Update Manager can also restrict parallelized downloads across the same or different transports. The Device Update Proxy is responsible for accepting download and load events, informing on the status of these events and negotiating the download with the device over the device specific protocol.
The system can be figured with a config file to allow the Device Update Manager to fully manage device update activities or to have a third entity, called the Update Master, to initiate either/or downloads and loads. An example of an Update Master would be a UI which would query the user if they wanted to load and/or download the code. In a typical usage, the UI would gate on the download, then perform an immediate download followed by an automatic load or would perform a background download followed by a gated load.
#define IARM_BUS_DEVICE_UPDATE_MASTER_DOWNLOAD_ENABLED 0
#define IARM_BUS_DEVICE_UPDATE_MASTER_LOAD_ENABLED 0
#define IARM_BUS_DEVICE_UPDATE_MASTER_DOWNLOAD_ENABLED 1
#define IARM_BUS_DEVICE_UPDATE_MASTER_LOAD_ENABLED 0
DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.
Powered by a free Atlassian Confluence Open Source Project License granted to RDKCentral. Evaluate Confluence today.