RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
Overview
Remote devices like set top boxes and DVRs have settings to control certain activities. For instance, STBs need to know when to upload log files, or when to check for a new firmware update. In order to remotely manage a large population of devices, we need a solution that lets support staff define instructions and get the instructions to the devices. These are Device Configuration Manager (DCM) and Xconf (X1 Configuration Manager). DCM and Xconf are management services that delivers certain configuration details to set-top-boxes (STB).
...
Traditional code download were using eCM interface which had some limitations like URL resolution not supported. XCONF way of code download allows Code download from the Embedded STB (eSTB) interface and provides set-top with
- Which firmware version to download
- From where to download
- How (protocol) to download
RDK Code Download (RCDL)
| draw.io Diagram | ||||
|---|---|---|---|---|
|
Server side (Business logic) identifies which version of code need to be provided for download. Xconf download is triggered by the device ie: device reaches out to server sending information like current firmware and capabilities. It asks for which firmware version to download and from where to download. RCDL (RDK Code Download or Remote Code Download) uses eSTB interface to download code from server.
...
| Capability | Description |
|---|---|
| rebootDecoupled | lets Xconf know that reboot has been decoupled from firmware download. If not specified in the rebootImmediately response, the STB will still reboot immediately after firmware download. |
| downloadScheduled | lets Xconf know that STB is able to schedule firmware download based on information received from Xconf. ?? do we still want this ?? |
| RCDL | STB is capable of performing HTTP firmware downloads using DNS resolved URIs. The download will run in the eSTB. Until this, the eCM performed the download. eCM does not have DNS and thus requires an IP address. |
| supportsFullHttpUrl | lets Xconf know that the STB can accept a full URL specifier (http://hostname.com); initially, the STB only accepted a hostname and prepended the hostname with the protocol, then appended it with a port and resource path. Xconf should specify the entire URL |
...
There are times when Xconf does not wish to respond to the STB. In these cases it will send an HTTP 404 (not found) response and a prose text reason for why the response was not handled. The STB should ignore these responses (and not retry the request to Xconf).
Service & Scripts
Service Name : /lib/systemd/system/swupdate.service
Helper Script : /lib/rdk/swupdate_utility.sh
Main Script : /lib/rdk/deviceInitiatedFWDnld.sh
Overview
Community Forums
Content Tools
Tasks