View source for Http://www.w3.org/2011/webtv/wiki/Media APIs/uc-tablet joins home network

= 1. Tablet Joins Home Network =

{|  style="width:100%; border-style: solid; border-width: 1px;border: 1px solid #000; color: black; background-color: #ffffcc;" 
| colspan="3" | '''Tablet joins Home Network'''
|-
| style=" width: 20%; background-color: white;"|
Author: '''Bin Hu (AT&T)'''
| style="width: 30%; background-color: grey;"|
Category: '''CHANGE'''
| style="width: 30%; background-color: yellow;"|
Status: '''GAP'''
| style="width: 30%; background-color: white;"|
'''Tracker''' [https://www.w3.org/2011/webtv/track/actions/174 174]
|}

== Description ==

* Pre-requisites:
** Subscriber has a set-top box, and has subscribed to content service
** Subscriber configures that the content service is discoverable as Local-Networked Service in home network
** Subscriber buys a new Tablet
 
* Scenario:
** Subscrier launches the “service discovery” application through the browser of new Tablet, and taps the button “Discover Service”.
** The browser starts to search for Local-Networked Service, and finds the Content Service provided by set-top box.
** Subscriber accepts to turn on the Content Service on Tablet
** Subscriber starts to enjoy the content service on both TV and Tablet, controlled and synchronized according to user’s instruction.
 
* Alternative scenario
** Subscriber may have more than one set-top boxes, and may have subscribed to more than one content services

== Motivation ==

''State the benefit to the ecosystem, and why you were not able to use existing standards''

== Dependencies ==

''Link to other use cases, proposal, specs, standardisation activities, ...''
''To avoid fragmentation of information, should we standardise it? Probably the easiest way is a double-check by chairs to avoid this?''

* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Device_Discovery_Mechanism Device Discovery Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Service_Aggregation_Mechanism Service Aggregation Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Service_Synchronisation_Mechanism Service Synchronisation Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Service_Expiry_Mechanism Service Expiry Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Device_Authentication_Mechanism Device Authentication Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Local_Access_Control Local Access Control]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Local_Network_Service_Protection_Mechanism Local Network Service Protection Mechanism]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Context-based_and_targeted_Service_Aggregation Context-based and targeted Service Aggregation]
* [http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Wake-up_Mechanism Wake-up Mechanism]

== What needs to be standardised ==

''Link to the Requirement pages''
''I suggest here that we create a page with all the REQS and we link from here to there, in order to avoid losing information on the way''