Page History

...

Remember as per architecture description, the RDK-M instance of the DAC cloud system is responsible for creating appropriate DAC bundle out of oci-image for a specific app & version and make it available for Video Accelerator to download and store securely on certain location URL. That bundle is also specific for certain Video Accelerator Hardware (SoC/OEM) platform, can be encrypted or not (is optional) and is specific for range of firmware versions on that platform, represented by a ID which we call "dacBundleFirmwareCompatibilityKey". See more information on latter here.

So for ASMS to provide right location of a bundle, it needs to get from the requester (STB) the following:

• the applicationID and app_version : for which application are you requesting a bundle?  And for which version of that application. example for version "1.0.0" of appId "com.rdk.app.flutter-slide-puzzle" is represented by string "com.rdk.app.flutter-slide-puzzle:1.0.0"   If you don't provide version, then default "latest" version is assumed
• the platformName of the STB as defined in ASMS:  because bundles are specific to specific modeltype. Each CPE modeltype registered in DAC cloud system has a template for autogenerating the appropriate oci run config. The RDK-VA modeltype specific templates are available in https://github.com/stagingrdkm/lgpub/tree/master/dac/templates/oe_3.1 You can find platformName of STB in filename of files listed here example is "7218c". That platformName is also retrievable via LISA (defined in lisa config see  https://code.rdkcentral.com/r/plugins/gitiles/components/generic/rdk-oe/meta-cmf-video/+/refs/heads/rdk-next/recipes-extended/rdkservices/rdkservice-lisa-dac-config.inc  more info see LISA#lisa.dac.confg )
• dacBundleFirmwareCompatibilityKey:  this is unique ID that represents a set of firmware versions of a given platform for which the same App bundle is guaranteed to keep on working. example for 7218c platform this is the "1.0.0-41abf2fba994b2d04baedeca6d5adf097ece9f79" part of of  "7218c_1.0.0-41abf2fba994b2d04baedeca6d5adf097ece9f79-dbg_dac_configs.tgz" file you see here . You can also retrieval current applicable "dacBundleFirmwareCompatibilityKey" of the STB from LISA when configured correctly in here 

...