1. e2e Arch Diagram

E2E_Arch_AppInfra_RDK8_AI2_DAC2_NativeAppsWG.drawio

Renamed page title from RDK-8 to RDK-8q1 because not all features of this architecture will be part of RDK-8.0 release, 

Aim is to develop remain gaps and get to this architecture during 26Q1 so it can be part of next quarterly RDK8 update.


2. GAPS

2.1. Design and Specification Gaps

  1. review the RDK-8 e2e App Infrastructure architecture diagram : confirm agreement, disagreement, further clarifications in the e2e architecture diagram. Sense of urgency as RDK-8 is coming close

  2. MU: App-metadata spec for UI towards App developers (MU) (minimal for RDK-VA resident UI)

  3. Interface 6: 

    1. app metadata details required and available to VA Core UI. API and metadata spec (cfr ASMS in DAC1.0)

    2. app catalog structure (AC) and API towards RDK-VA

  4. Package dependency logic in VA Core UI (or other rdkm alternative) that ensures all dependent packages (runtime) are downloaded with associated App

  5. spec towards AI managers what formats they need to support in parallel ( eg both existing EOS widget format and new AI2 ralf format) and solution design on how to support that in parallel

  6. responsibility split unclear if Package Manager or Runtime Manager will do what part the local bundle generation

  7. interface7:  protocol use for distribution/downloading packages  (e.g. mTLS, mTLS and Token on CDN)

  8. spec of interface 3 ?

  9. spec  RDKM-VA reference Appstore: Eg UI for Appstore Admin to do metadata-override and UI to create appcatalog and add apps to it

  10. UI spec of VA Core UI on how to browse and filter apps in Appcatalog. how to install, start, stop and uninstall, see debug App state menu
  11. spec/design how App Manager will monitor memory (both App linux, GPU mem and total mem available) to use policy config to decide/perform actions on apps (in pause, suspended and hibernated mode)
  12. design: What is entity/process that takes role of RialtoServer Manager (not the Simulator, real manager) ?
  13. standard solution for App logs in Container ( and readable outside of container)
  14. spec of RALF signed format (including erofs and dm-verity)
  15. we have no encrypted format specified so far (signed + dm-crypt format)

  16. need a spec on which Dobby Plugins we will support for RDK-8

  17. version of libs in base-layer to be agreed (eg gstreamer)

  18. debug solution, debug profile addon to base-layer

  19. solution for new Netflix Graphics Player Requirement ( big impact, output of video decoder is imported as Graphics texture, Rialto Server-Client is not ready for this)
  20. ...

2.2. Development Gaps / TO DO's

  1. support for RALF unpacking in AI2.0
  2. have RUNTIME_CONFIG support new AI2.0 dataformat (see existing https://github.com/rdkcentral/entservices-apis/blob/develop/apis/PackageManager/IAppPackageManager.h#L10-L38 )
  3. support both current EntOS widget format and new AI2.0 in parallell
  4. support for merging base/gpulibs/runtime/app into one oci rootfs bundle
  5. use overlayfs or bind mount for merging 3 layers into 1 rootfs of container bundle
  6. open source common APP launcher (use or use derivates of it in wpe, cobalt) 
  7. create example app (from DAC1) with bolt, new layered structure  ,  
  8. create wpe as runtime (from DAC1)  new layered structure
  9. create cobalt as runtime (from DAC1)  new layered structure
  10. security review

2.3. Ownership Gaps

  1. product owner  RDKM-VA reference Appstore, who from RDK-M ?


3. Review notes

3.1. 22/10/2025 session

  • Yuri: PreinstallManager is missing to load at boot preinstalled apps/packages, will add to diagram  https://github.com/rdkcentral/entservices-infra/tree/develop/PreinstallManager  Resident UI aka Core UI should be started by Preinstall Manager via AppManager at boot same way like other app (with privileged property of being HOME app). adding PreinstallManager to the diagram 
  • Anil: RDK8.0 release is develop/main code base delivered by end of this year. Cannot call it "RDK 8.0" architecture because NOT all features from diagram, like multilayer (base-runtime-app layer) will be developed and delivered by end of this year.  We should continue this arch alignment and address gaps so we can have this developed during 26 Q1 and can then be delivered as RDK8 quarterly update. Name of that version TBD. RDK8.1/ RDK8Q2 / RDK8+
  • Aijth to check who will be RDK-M component owners of RDK-M VA Appstore Cloud  (product, arch & development) (includes design of interface 6) and Video Accelerator UI
  • further review sessions to be planned. Also session of what will be in RDK8.0 


  • No labels

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.