Requirements for a Web and TV environment Jean-Claude Dufourd Telecom ParisTech Institut Telecom
Overview ¢ Context ¢ Requirements for a Web and TV environment ¢ Current implementations ¢ Standards page 1 Telecom ParisTech Web and TV, Feb 8-9, 2011
Context: home around the TV Connected picture frame Connected TV Mobile phone + printer + new sensors … Desktop computer PDA Tablet Laptop page 2 Telecom ParisTech Web and TV, Feb 8-9, 2011
R1: Apps to run on all devices Connected TV Connected picture frame Common ground: HTML + CSS + ES Mobile phone « Very close » to W3C Widgets è OK Desktop computer PDA Tablet Laptop page 3 Telecom ParisTech Web and TV, Feb 8-9, 2011
R2: Apps to run on a dynamic network Connected TV Connected picture frame No complex network setup Mobile phone è Need a discovery and service protocol : UPnP/ DLNA – Bonjour – WS Discovery – SIP-based … Ex: see mobile phone pictures on TV, then display on picture frame, then store on desktop. Desktop computer PDA Tablet Laptop page 4 Telecom ParisTech Web and TV, Feb 8-9, 2011
R3: Services accessible from all devices Connected TV Connected picture frame An EPG widget runs on TV only Mobile phone Desktop computer PDA Tablet Laptop page 5 Telecom ParisTech Web and TV, Feb 8-9, 2011
R3: Services accessible from all devices Connected TV Connected picture frame An EPG widget runs on TV only An EPG service, built on communicating widgets, Mobile phone runs on any device è Distributed documents (pervasive, ubiquitous) è Service adaptation by distribution Desktop computer PDA Tablet Laptop page 6 Telecom ParisTech Web and TV, Feb 8-9, 2011
R3: Services accessible from all devices Connected TV Connected picture frame An EPG widget runs on TV only An EPG service, built on communicating widgets, Mobile phone runs on any device è Distributed documents (pervasive, ubiquitous) è Service adaptation by distribution Desktop computer PDA Tablet Laptop page 7 Telecom ParisTech Web and TV, Feb 8-9, 2011
R4: Services to move to best device at any time Connected TV Connected picture frame Service starts on TV Mobile phone Desktop computer PDA Tablet Laptop page 8 Telecom ParisTech Web and TV, Feb 8-9, 2011
R4: Services to move to best device at any time Connected TV Connected picture frame Service starts on TV Mobile phone Interactivity appears Desktop computer PDA Tablet Laptop page 9 Telecom ParisTech Web and TV, Feb 8-9, 2011
R4: Services to move to best device at any time Connected TV Connected picture frame Service starts on TV Mobile phone Interactivity appears è move to tablet Desktop computer PDA Tablet Laptop page 10 Telecom ParisTech Web and TV, Feb 8-9, 2011
R4: Services to move to best device at any time Connected TV Connected picture frame Service starts on TV Mobile phone Interactivity appears è move to tablet Tablet gets preempted è move to office Keeping current service state Desktop computer PDA Tablet Laptop page 11 Telecom ParisTech Web and TV, Feb 8-9, 2011
R5: Native/widget/HW: no difference Connected TV Connected picture frame Why should it make any difference that one part of a service is hardware, native code, or widget ? Mobile phone è Services as cooperation of any type of part Ø Framework for native code behaving as a widget Desktop computer Ø Compile widget to native code Ø Native app « equivalent » of a widget PDA Tablet Laptop page 12 Telecom ParisTech Web and TV, Feb 8-9, 2011
R6: No standard dependency Connected TV Connected picture frame True for network and codecs, why not for other stds: Mobile phone - Widgets in HTML or SVG or BIFS (for 3D) - Discovery with UPnP or Bonjour or SIP or WS Discovery Desktop computer - HTTP streaming or RTP PDA Tablet Laptop page 13 Telecom ParisTech Web and TV, Feb 8-9, 2011
Implementation Connected TV Connected picture frame GPAC and WebKit players Mobile phone HbbTV (xHTML+CSS+ES+huge OIPF API +DVB+MPEG TS+DSMCC+codecs), SVG, W3C Widgets (PC + Interface), UPnP/DLNA, MPEG-U, RTP/RTSP Desktop computer PDA Tablet Laptop page 14 Telecom ParisTech Web and TV, Feb 8-9, 2011
Standardization Connected TV Connected picture frame • « Smaller » profiles • « Common » Device APIs, including capabilities Mobile phone • Document discovery, communication and migration: - Declarative - Not just widgets Desktop computer PDA Tablet Laptop page 15 Telecom ParisTech Web and TV, Feb 8-9, 2011
Thank you for your attention ¢ Discussion … page 16 Telecom ParisTech Web and TV, Feb 8-9, 2011
Recommend
More recommend