sTVe: Sychronized TV Ecosystem Myra Einstein & Sheau Ng W3C - - PowerPoint PPT Presentation

NBCUniversal sTVe – W3C Workshop on Rich Multimodal Application Development P1

sTVe: Sychronized TV Ecosystem

Myra Einstein & Sheau Ng W3C Workshop on Rich Mulitmodal Application Development

Date 7/22/13

NBCUniversal

Synchronized Television Ecosystem

P2

sTVe (Pronounced “Stevie”)

Set of protocols to allow a display renderer, such as a TV, to participate in a synchronized orchestration of multiple content that is delivered to the renderer in different paths.

What is sTVe?

Date 7/22/13 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

iTV lacks a Production/Distribution Ecosystem

Date 7/22/13 P3

Motivation Video iTV

Author Edit Distribute Consume

? ? ?

sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

The sTVe Ecosystem

Date 7/22/13 P4

Production & Operational Tools Distribution Applications Responses and Special features

Skills needed:

• Syndication logic for targeting

multiple types of devices

• Integrations with other core

programmer technology Skills needed:

• UI design for non-technical

personnel

• Knowledge of various

production workflows Skills needed:

• UI/UX Design for viewer

interactions

• HTML5, CSS, Javascript, other

native device app technologies Skills needed:

• Response server: Ability to

process 100,000s transactions/sec

• Feature Server: Specialized

knowledge for specific event (fantasy football, judging apps, etc)

Content Identification

Skills needed:

• Fingerprint / Watermark /

Signaling content identification

• Maintaining massively growing

database of available content

• Servicing 100,000s

transactions per second

sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

IP layer and Semantic Standard

• Proliferation of IP connected devices that use HTML, CSS,

Javascript for creating applications

• Can use these technologies as a base for building a semantic

layer on top

• By defining a timeline object from which other event objects are

hung, interactive applications can focus on user experience and less on basic data representations

• The device/application is responsible for identifying the content

being watched (ACR, sync-to-broadcast, etc). The application then marries objects on timeline to current temporal location.

• For HTML applications, only a basic CSS reskin would be

necessary to change the look and feel

• Other non-HTML platforms could use these protocols as well, as

the data objects don’t explicitly define the presentation layer and would provide the hooks necessary to invoke their own methods for applying styles

Date 7/22/13 P5 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

SmartTV ACR Application Usecase

Date 7/22/13 P6 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

Mobile/Tablet Application Usecase

Date 7/22/13 P7 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

Benefits of sTVe Recap

• Allows vendors to play to their strengths and helps open

ecosystem up to become more mainstream

• Allows Application creators to start with a framework for how

data will be represented

• Allows programmers to plug in new functionalities without

replacing or replicating the entire system

• Allows interactive content to follow video content into

syndication for reruns and International audiences

Date 7/22/13 P8 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

Future Work

• Compile lessons learned from first prototypes

developed

• Further detailing in Browser-Server environment

needed

• W3C would be ideal place to develop these

standards for browsers and the Multimodal Applications that sit on top of them.

Date 7/22/13 P9 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

Thank you

Date 7/22/13 P10 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

APPENDIX

Date 7/22/13 P11 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal Date 7/22/13 P12

sTVe Conceptual Diagram

sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal

Connected TV Screenshots

Date 7/22/13 P13 sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal Date 7/22/13 P14

sTVe Protocols and Standards Synchronous Content Protocol

• Specify Communication Layer and Interactive Content Templates
• JSON-Based
• Abstract communication layer, and focus on how to request and

receive synchronous content

• One Client, using Web technologies (HTML, Javascript, CSS) for

browser based apps

• Utilizing any backend system that adheres to the spec
• Alternate content for different display devices
• Tablet, Smartphone, Laptop/Desktop, Connected TV, IP Connected

Devices

• Style classes provided to link to CSS or other method of applying style

(native platforms)

• Content Types: Poll, Trivia, Fun Fact, Chat, Data Table, Listing

(headlines), E-Commerce, Video, Audio, Ad Unit, Link, Clear, Others

sTVe – W3C Workshop on Rich Multimodal Application Development

NBCUniversal Date 7/22/13 P15

sTVe Protocols and Standards Timeline Data Structure

• Discreet Cues
• Can have multiple display resources in each cue targeted

to different areas on the screen

• Multiple display resources in a cue can be user-advanced
• r auto-advanced like a slideshow
• Each object has a duration, min-duration, and transition

type.

• Min duration is for determining if an object should be

displayed if a user tunes in mid-broadcast

Timeline

Poll CTA Poll Results Fun Fact Chat Results Other Custom Event sTVe – W3C Workshop on Rich Multimodal Application Development