Media APIs/uc-tablet joins home network
1. Tablet Joins Home Network
Tablet joins Home Network | |||
Author: Bin Hu (AT&T) |
Category: CHANGE |
Status: GAP |
Tracker 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?
- Device Discovery Mechanism
- Service Aggregation Mechanism
- Service Synchronisation Mechanism
- Service Expiry Mechanism
- Device Authentication Mechanism
- Local Access Control
- Local Network Service Protection Mechanism
- Context-based and targeted Service Aggregation
- 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