Page History

...

• XCONF​

  • Xconf is slated to be the single entity for managing firmware on set-top boxes both in the field and in various warehouses and test environments.​

  • Xconf's primary purpose is to tell set-top boxes (STBs) what version of firmware they should be running. Xconf does not push firmware to the STB, nor is not involved in any way in the actual download / upgrade process. It simply tells the STB which version to use. Xconf also tells STBs when, where (host), and how (protocol) to get the firmware.​

  • Xconf consists of two web applications, XconfDataService and Xconf Admin. XconfDataService is the app that the STBs talk to. Xconf Admin allows humans to enter all the information necessary for Xconf to provide the correct information to STBs.​

  • The interface between STBs and Xconf is simple. STBs make HTTP requests to Xconf sending information like MAC address, environment, and model. Xconf then applies various rules to determine which firmware information to return. The information is returned in JSON format.

Image Modified

• RDK Telemetry​
  • RDK Telemetry mechanism is simple in concept - grepping log files on a device - and has been hugely successful.  ​
  • The resulting data and reports are a staple for Triage and Debugging.  However, over time, that success has also resulted in a cost.  ​
  • The number of logs and strings being searched and reported for legacy telemetry can result in larger than desired CPU utilization every time DCM runs , and the resulting upload of data can grow very large.

 
Image Modified

• RDK Logging
  • RDK Logger provides common logging capability for all RDK components. It is a common logging library which is based on MPEOS logging & uses log4c for formatting and supports multiple log levels.​
  • RDK Logger Capabilities ​
  • Abstracts logging client from underlying logging utility.​
  • Dynamically enables/disables logging level at run time.​
  • Provides logging format that complies with the existing OCAP format (e.g. <timestamp> [mod=*, level=*]).​
  • Controls log level independently for each component/module.​
  • Enables logging globally via single configuration value.​Controls initial log level for each component/module from configuration file (debug.ini) at startup.​
  • The debug.ini is the main configuration file for RDK Logger and it is intended to be used globally in multi-process environment.​
  • Prints formatted data to stdout.​
  • Separates logs into separate files based on "SEPARATE.LOGFILE.SUPPORT" configuration variable.​
  • RDK logger log files will be generated under "/opt/logs" folder if SEPARATE.LOGFILE.SUPPORT=TRUE
• WebPA​
  • WebPA is the communication channel from Cloud to RDK based home gateway devices. It helps to manage devices from Cloud. ​
  • WebPA protocol provides functionality of read/write access to device management parameters​
• RDK Feature Control​
  • Operational limitations that lead to RFC​
  • The only way to disable a new feature in the field was to rollback to the older firmware​
  • Lack of options to do a feature deployment in a subset of devices​
  • Lack of options to deliver dynamic configurations to the box​
  • Using RFC​
  • Enables quicker roll out of features​
  • Enables a secure channel for delivering runtime configurations to the device​
  • Ability to control when the feature needs to be enabled/disabled ? Disable now/ Disable during reboot​

...