{"id":11460,"date":"2023-12-06T09:08:19","date_gmt":"2023-12-06T09:08:19","guid":{"rendered":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/device_management\/xconf\/"},"modified":"2025-03-25T05:18:32","modified_gmt":"2025-03-25T05:18:32","slug":"xconf","status":"publish","type":"page","link":"https:\/\/developer.rdkcentral.com\/documentation\/documentation\/device_management\/xconf\/","title":{"rendered":"Xconf"},"content":{"rendered":"


\n<\/p>\n

\n
\n
\n
\n

XConf is a management service that delivers certain configuration details to CPEs (Customer Premises Equipment). For instance, CPEs 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).<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

XConf (X1 Configuration Manager) and Device Configuration Manager (DCM) began as separate solutions. Both the server and CPE\/STB implementations evolved separately, yet both had overlapping functionality. Now, engineers have consolidated the server modules. The single name of the device configuration management service is XConf.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

XConf is a system composed of a client component (CPE device) and a server-side component. The client-side scripts and components retain the name DCM. The main function of these client and server-side components is to inform CPE of the configurations. The configurations can be of where to send log files or which telemetry metrics to transmit. The XConf server consists of two web applications: the Data Service and Angular-admin (UI). The Data Service handles the configuration details queried by CPEs, while Angular-admin (UI) allows administrators to create targeting rules and input necessary configuration information. XConf-dataservice, the core component, communicates with the CPEs and interacts with a Cassandra database to store firmware configurations, common data sets (MAC list, Model, and Environment), telemetry profiles, download locations, RFC, and feature updates. When a CPE requests configuration, the Dataservice fetches the relevant data from the Cassandra database and sends it as a response.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n
<\/div>\n
\"XconfDCM\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Below listed are the capabilities achieved using xconf:<\/strong><\/p>\n