Introduction

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

Transparency
Provides the MVPD full transparency into the source code
Design
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.
Open source
Licensed under Apache 2.0 license and is available free for licensees
Huge community user base
Used and supported by major MSOs , OEMs and SoC vendors
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
  1. Viewing the stack as increasing levels of abstraction.
  2. Viewing the stack by the source or component owner.
  3. Viewing the stack in terms of the deployment configuration – IP, QAM or both.
TYPE 1
As increasing levels of abstraction
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.
OEM components:
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.
GENERIC RDK
COMPONENTS
MSO
COMPONENTS
SOC COMPONENTS
OEM COMPONENTS
DESCREASING
ORDER OF
ABSTRACTION

TYPE 2
By the source or component owner
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.
SoC vendor:
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.
OEM :
Components released by the set-top manufacturer.

TYPE 3
In terms of the deployment configuration
IP-Only:
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.
Hybrid:
Support for IP-based video acquisition,QAM-based tuning.Headed or Headless configuration,Home networking servers.
MVPD
UX
User interface
App portal
Application
UI
Framework
User interface framework ( JS library providing advanced graphics )
Application
Platform
Webkit for
embeded
EME/CDMI
(DRM)
Plugins
NodeJS
(w/Node webGL)
Netflix
(Native)
Other
native apps
Application framework
Westeros compositor ( Wayland)
RDK Video
Profile
IP TSB (SD Flash )
HLS, DASH
4K
HDR
Voice input
Voice output (TTS)
Dolbi MS11 & MS12
Audio capture (Song ID)
AD Insertion (LSA)
HDMI- CEC
WebRTC
Wi-fi, MOCA
RDK Device
Management
Xconf
RDK logging
RDK Telemtry
WebPA
Provisioning/ Onboarding
Feature control
Go To Top