Page History

...

• RFC Manager sends an HTTP request to the configured XConf URL, including key device identifiers:

  • STB MAC Address

  • Account ID

  • Partner ID

  • Firmware Version

    Code Block

    2026-09-01T14:50:24.096558 [INFO ] [read_RFCProperty][205] RFC name=Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Bootstrap.XconfUrl,type=0,value=https://xconf.rdkcentral.com,status=0 2026-09-01T14:50:24.096601 [INFO ] XconfUrl: = https://xconf.rdkcentral.com, found after 1 attempts 2026-09-01T15:03:28.161794 [INFO ] [DownloadRuntimeFeatutres][2026] Xconf Request : [https://xconf.rdkcentral.com/featureControl/getSettings?estbMacAddress=E4%3A5F%3A01%3A56%3AF4%3A82&firmwareVersion=lib32-rdk-fullstack-image-RPI4-20260824125316&env=dev&model=RPI4&manufacturer=RaspberryPi&controllerId=2504&channelMapId=2345&VodId=15660&partnerId=community&osClass=&accountId=Unknown&Experience=X1&version=2]

• XConf uses these identifiers to locate the appropriate configuration and returns it as a JSON payload.

  Code Block

  251124-19:50:21.532196 [mod=RFCMGR, lvl=INFO] [tid=2157] [PreProcessJsonResponse][2018] Xconf Response: {"featureControl":{"features":[{"name":"TC-NTP","enable":true,"effectiveImmediate":true,"configData":{"tr181.Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.TR069support.Enable":"false","tr181.Device.Time.NTPServer1":"time.google.com","tr181.Device.Time.NTPServer2":"time1.google.com","tr181.Device.Time.NTPServer3":"time2.google.com","tr181.Device.Time.NTPServer4":"time3.google.com","tr181.Device.Time.NTPServer5":"time4.google.com"},"featureInstance":"TC-NTP"}]}}

  
  

...

3. Configuring the xconf server url

...

• Parses the JSON response to extract all configuration parameters.

• Updates TR-181 parameters by invoking tr181 set commands for each relevant RFC value.

• tr181 set uses RFC API which in turn calls the tr69hotif API to store these environment variables and TR-181 parameters.

• After applying all parameters, the processor updates the stored hash and timestamp in the database. This allows future invocations to skip re-applying the same configuration.

...

5. tr181 Set and RFC API

• The tr181 set commands internally call the RFC API to perform parameter get/set operations.

• The RFC API communicates with the local HTTP server running within tr69hostif using HTTP GET or POSTrequests.

tr69hostif uses the below files for storing the configuration:

• 
  

  /opt/secure/RFC/rfcVariable.ini	RFC environment variables	Contains environment-level variables derived from RFC config
  /opt/secure/RFC/tr181store.ini	RFC namespace TR-181 parameters	Contains TR-181 parameters managed within the RFC namespace
  /opt/secure/RFC/bootstrap.ini	Bootstrap TR-181 parameters	Contains TR-181 parameters with the bsUpdate attribute
  Profile-specific storage	Non-RFC TR-181 parameters	Managed by respective profile handlers with their own storage mechanism

  
  

  
  

...

6. tr69hostif Request Routing

• The tr69hostif component routes incoming parameter requests based on their namespace or attributes:

  bsUpdate attribute present	Bootstrap handlers	Handles bootstrap get/set requests
  RFC namespace	RFC handlers	Manages parameters controlled by RFC
  Other (non-RFC) parameters	Profile handlers	Routed to profile-specific get/set implementations

...

7. Runtime Sources and Priority

• Runtime Sources Overview

•  RFC Library Runtime Priority

...

• Bootstrap Runtime Priority (XBSStore via tr69hostif)

• Combined Conceptual Priority (All Paths Union)

8. mTLS support

• RDKE expects xconf connections to be secure. This expects RFC to use MTLS by default.
• Support to add MTLS to RDKM xconf server is under investigation.
• Until then, we are disabling MTLS support by not enabling rdkcertselector
  • mTLS is enabled in the RFC code when the macro LIBRDKCERTSELECTOR is defined.

...