Requirements for a Web and TV environment Jean-Claude Dufourd - - PowerPoint PPT Presentation

requirements for a
SMART_READER_LITE
LIVE PREVIEW

Requirements for a Web and TV environment Jean-Claude Dufourd - - PowerPoint PPT Presentation

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


slide-1
SLIDE 1

Requirements for a Web and TV environment

Jean-Claude Dufourd

Telecom ParisTech Institut Telecom

slide-2
SLIDE 2

Overview

¢ Context ¢ Requirements for a Web and TV environment ¢ Current implementations ¢ Standards

page 1 Telecom ParisTech Web and TV, Feb 8-9, 2011

slide-3
SLIDE 3

Context: home around the TV

page 2 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV + printer + new sensors …

slide-4
SLIDE 4

R1: Apps to run on all devices

page 3 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Common ground: HTML + CSS + ES « Very close » to W3C Widgets è OK

slide-5
SLIDE 5

R2: Apps to run on a dynamic network

page 4 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV No complex network setup è 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.

slide-6
SLIDE 6

R3: Services accessible from all devices

page 5 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV An EPG widget runs on TV only

slide-7
SLIDE 7

R3: Services accessible from all devices

page 6 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV An EPG widget runs on TV only An EPG service, built on communicating widgets, runs on any device è Distributed documents (pervasive, ubiquitous) è Service adaptation by distribution

slide-8
SLIDE 8

R3: Services accessible from all devices

page 7 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV An EPG widget runs on TV only An EPG service, built on communicating widgets, runs on any device è Distributed documents (pervasive, ubiquitous) è Service adaptation by distribution

slide-9
SLIDE 9

R4: Services to move to best device at any time

page 8 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Service starts on TV

slide-10
SLIDE 10

R4: Services to move to best device at any time

page 9 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Service starts on TV Interactivity appears

slide-11
SLIDE 11

R4: Services to move to best device at any time

page 10 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Service starts on TV Interactivity appears è move to tablet

slide-12
SLIDE 12

R4: Services to move to best device at any time

page 11 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Service starts on TV Interactivity appears è move to tablet Tablet gets preempted è move to office Keeping current service state

slide-13
SLIDE 13

R5: Native/widget/HW: no difference

page 12 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV Why should it make any difference that one part

  • f a service is hardware, native code, or widget ?

è Services as cooperation of any type of part Ø Framework for native code behaving as a widget Ø Compile widget to native code Ø Native app « equivalent » of a widget

slide-14
SLIDE 14

R6: No standard dependency

page 13 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV True for network and codecs, why not for other stds:

  • Widgets in HTML or SVG or BIFS (for 3D)
  • Discovery with UPnP or Bonjour or SIP
  • r WS Discovery
  • HTTP streaming or RTP
slide-15
SLIDE 15

Implementation

page 14 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV GPAC and WebKit players HbbTV (xHTML+CSS+ES+huge OIPF API +DVB+MPEG TS+DSMCC+codecs), SVG, W3C Widgets (PC + Interface), UPnP/DLNA, MPEG-U, RTP/RTSP

slide-16
SLIDE 16

Standardization

page 15 Telecom ParisTech Web and TV, Feb 8-9, 2011

Connected picture frame Desktop computer Laptop Tablet PDA Mobile phone Connected TV

  • « Smaller » profiles
  • « Common » Device APIs, including capabilities
  • Document discovery, communication and

migration:

  • Declarative
  • Not just widgets
slide-17
SLIDE 17

Thank you for your attention

¢ Discussion…

page 16 Telecom ParisTech Web and TV, Feb 8-9, 2011