RDK for video provides a common method to manage complex video functions such as tuning, conditional access, DRM, and stream management. RDK accelerates the deployment of next-gen video products and services, and simplifies the customization of the application and user experience.
RDK for Video distinguishes itself
Provides the MVPD full transparency into the source code
Enables the MVPD to focus, innovate, and differentiate at the application and services layer.
Open source components and standards
Linux kernel and drivers, Busybox, OpenSSL, WPE, OpenGL, Gstreamer, UPnP libraries etc.
Vast device management capability
Supports features like SNMP, TR-069, WebPA, Feature Control ,Telemetry, Log upload etc.
Easy software deployments
Components can be added/removed easily to make different target builds .
RDK Device Structure
RDK Software Stack
Common framework for developing STB software. It incorporates functions such as tuning, IP video, media streaming/DLNA, but still allows for UI control and development by the operator.
The three different perspectives or views into the RDK software stack
- Viewing the stack as increasing levels of abstraction.
- Viewing the stack by the source or component owner.
- Viewing the stack in terms of the deployment configuration – IP, QAM or both.
Generic components (RDK and MSO):
Meant to run across all platforms and all devices.
SoC components :
Al SoC -layer software components such as the SDK and any SoC-level for generic RDK and MSO components. Eg : HAL layer implementation for QT and Gstreamer.
Device-layer software components. Specializations to generic or SoC components at the device layer or complementary software components provided by the OEM to create a fully functional set-top.
The main sources of RDK components are
Opensource Community :
The open source community of software developers.
MSO proprietary :
Components that are developed directly by MSO, third-party vendors but licensed to MSO for distribution.
Components released by the SoC manufacturer, includes the SDK and patches to RDK components.
Third-Party component owners :
Components not released by RDK-M LLC, Need special licensing arrangements with the component owners, Required to achieve full functionality.
Components released by the set-top manufacturer.
Components to execute the RDK in an IP-only video acquisition. No QAM-based tuning.Pure IP set-tops interacting with the Hybrid (IP+QAM) devices as home networking clients.
Support for IP-based video acquisition,QAM-based tuning.Headed or Headless configuration,Home networking servers.
User interface framework ( JS library providing advanced graphics )
Westeros compositor ( Wayland)
IP TSB (SD Flash )
Voice output (TTS)
Dolbi MS11 & MS12
Audio capture (Song ID)
AD Insertion (LSA)