RDK Revisited: Use Cases
One of the questions swirling around the topic of RDK – the Reference Design Kit – is what it means, beyond getting to market more quickly with hardware and cloud-based services.
Perhaps this was best phrased by reader John, who sent this emailed query last week: “RDK, service velocity, got it. Have you any more consumer-facing angles, so that I can pitch this to my management for budget? And win?”
Well, John. Far be it from us to separate a man from a budget. And, as luck would have it, that RDK session at TVOT, the audio of which is finally up on iTunes, highlighted three use cases that may inform your mission.
First: RDK as a way to enable better, faster graphics, by making it easier for people within the RDK community to “see” and use each other’s advancements. Take chip providers, for example. They build out product roadmaps just like anyone else. For them, a feature advancement, like “hardware acceleration,” makes graphics more crisp and swift.
The example shown at TVOT was Espial’s HTML5-based navigation of TV, on a tablet. Two things made it visually an ooo-ahh: The crispness of the graphics, and how quickly one could scroll through titles (with cover art).
And what made that possible was the use of RDK components that exposed ways for developers, like Espial, to reach directly down to exposed “hooks” in the chip. The difference is, before RDK, a developer up top couldn’t get directly to a feature set in a chip.
Two: RDK as a way to port apps developed for mobile, to TV. Ericsson was the example on this one, with a sports app it had originally developed for use on mobile devices. Using RDK, they were able to port it to TV in two weeks.
For that app to be ported to existing, non-RDK set-tops, they would’ve needed Java developers to learn the Java class libraries that are part of OCAP (Open Cable Applications Platform). Learning curve: Steep.
Third example: Porting services like Twitter to TV, with built-in channel change capabilities. Symphony Teleca (which also goes by “ST”) was the demo darling for this one, showing a way for the viewer to enter the Twitter hashtag of the show of interest, then see all tweets related to that show spill across the screen, live.
“It’s a great example of how a developer was able to tap into something that already exists, like the Twitter RSS, and bring that into a TV environment – without having to kjnow anything specific about the set-top box,” explained Steve Reynolds, SVP of premises technologies for Comcast, who narrated the three use cases at TVOT.
The hashtags can also be used to change channels, which sounds easier than it really is. “It sounds obvious, but it’s not easy,” Reyolds noted. “I’ve been doing this for a while now, and it’s one of those problems that we had to solve for over and over again.”
John, hope that helps. And may the budget forces be with you.
This column originally appeared in the Platforms section of Multichannel News.
CableNet 2000 Tour, Part 3: CLASSIC IN HINDSIGHT – The First Tablets with Companion TV Apps
Yes, dear viewer, there was a time (2000) when this stuff really did seem like pie in the sky. In this interview with Ericsson’s Frank Risseeuw, wireless home networking is a distinct possibility — over a 720 kbps Blu-tooth router. BRING IT! Nearby is what we’d now call a (rather blobbish) tablet, destined to let viewers watch TV on the big screen, and do interactive stuff using a companion app on the smaller screen.
Posting this in 2012 and feeling a bit silly…
Video courtesy The Cable Channel.