itaas CEO explains how Comcast's Reference Development Kit (RDK) could get cable closer to a new standard for next-gen set-top boxes
A uniform approach
Comcast set to work on the RDK about two years ago, and it's got the potential to become a big deal. With broad adoption, the RDK could provide the cable industry with a much more uniform video platform as operators embark on IP video migrations. It could also open the historically closed environment for set-top makers and app developers.
One key goal well underway is getting the RDK baked into systems-on-chip (SoCs) before box makers start building products around them, as it should translate into much faster product development cycles. At The Cable Show in May, Comcast Senior VP of Customer Premises Equipment Steve Reynolds said the typical cycle (building the box, developing software and getting it all up and running) was 24 months when the MSO launched the RDK project. The hope is that the RDK will cut that cycle to a year or even less, he said.
(A video of the RDK panel at the show is available here.)
It's anticipated that some RDK devices will use ARM, a low-power chip architecture already popular in Blu-ray players, smartphones and tablets. The idea there is to provide commonality so apps developed for mobile devices can be ported easily to the world of IP-connected set-tops and gateways.
The RDK leans on a Web-like cloud infrastructure, meaning that Comcast and its partners can create and change apps more rapidly. The old infrastructure's software environment is highly fragmented, requiring Comcast to spend gobs of time testing and retesting new software, followed by the further time-sucking task of downloading new files to boxes every time a change or upgrade is made.
It's painful. Reynolds likened the RDK's common stack model and its ability to accelerate application development to those of Android.
Next page: What's in the RDK?