Main Page/Cloud Browser TF/UseCases/state
State
UC-state-1: Cloud Browser Client sends state through control channel to the Cloud Browser upon request
Extends
Description
- The application running within the Cloud Browser depends on state that is stored within the client. Therefore the Cloud Browser uses the control channel to query the client for this state by issuing a request.
- Work flow:
- Cloud Browser Client receives a request from the Cloud Browser.
- It collects the requested state and sends it back through the control channel.
Actors
- Cloud Browser Client
- Cloud Browser
Dependencies
- None.
Gaps
- None.
Notes
- This use case could be mapped to all current architectural approaches.
- List of possible state information:
- Capabilities and constrains of media output devices
- Resolution
- Color space
- Stereo or Dolby Digital
- Number of media output devices
- Current selected media output device
- Supported media codecs
- Plugged and unplugged devices
- Playback info
- source
- time
- duration
- volume
- quality (dropped frames, ...)
- paused, stopped
- Sensor data
- heat
- light
- battery
- Smart devices
- Conditional access module
- Content Protection (CAS/DRM)
- Capabilities and constrains of media output devices
Requirements
- There MUST be a control channel.
- The requested state MUST be available from the client.
Author(s)
History
- 6-9-2016 Eugen Osiptschuk (talk) created
UC-State-2: Cloud Browser Client sends state through control channel to the Cloud Browser upon an event
Extends
- Nothing.
Description
- An event made it necessary to signal the Cloud Browser that the current state has changed.
- Work flow:
- An event occurred.
- Client forwards necessary state change to the Cloud Browser.
Actors
- Cloud Browser Client
- Cloud Browser
Dependencies
Gaps
- None.
Notes
- This use case could be mapped to all current architectural approaches.
- Possible events:
- Key press.
- Remote control unit (RCU) stopped the playback of the video.
- Devices plugged or unplugged
Requirements
- There MUST be a control channel.
Author(s)
History
- 6-9-2016 Eugen Osiptschuk (talk) created