WebAPI/PresentationAPI:Protocol Draft: Difference between revisions
< WebAPI
Jump to navigation
Jump to search
m (→Requirement: add protocol version) |
m (→References: update references) |
||
| Line 44: | Line 44: | ||
== References == | == References == | ||
[https://github.com/ | * [https://github.com/w3c/presentation-api/blob/gh-pages/interoperability.md Protocol suggestion by Second Screen WG] | ||
[https://github.com/ | * [https://github.com/mfoltzgoogle/freeplay/blob/master/architecture.md Architecture proposed by Google] | ||
Revision as of 08:50, 29 March 2016
This is a draft of protocol proposal for 2-UAs Presentation Scenario
Requirement
- Device Discovery
- Device information: unique name, user-friendly name,
- Device capability: resolution, supported media type, supported apps
- Protocol information: protocol version
- Service Launching
- Service information: app/page URL
- Session information: session Id
- Controlling message: launch, reconnect, terminate
- User settings: preferred locale
- Communication
- establish dedicate transportation channel
- Security
- device challenge
- data encryption
Architecture
Protocol Details
Launch
- STEP 1: find device
- STEP 1a: query device capability
- STEP 2: setup control channel to remote device
- STEP 2a: device challenge / device pairing
- STEP 3: launch app / page
- STEP 4: setup communication channel
- STEP 5: close control channel
Terminate
- STEP 1: setup control channel to remote device
- STEP 1a: complete challenge with stored information
- STEP 2: terminate app / page via session Id
- STEP 3: close control channel
Reconnect
- STEP 1: setup control channel to remote device
- STEP 1a: complete challenge with stored information
- STEP 2: reconnect app / page via session Id
- STEP 3: setup communication channel
- STEP 4: close control channel