Skip to content

Latest commit

 

History

History
48 lines (42 loc) · 3.25 KB

use-cases.md

File metadata and controls

48 lines (42 loc) · 3.25 KB
Raw

Use-Cases for WebTransport

Ordinality of listing does not imply priority.

  1. Machine learning
    1. Speech translation/emotion analysis - sending audio/video data from client to server for analysis and receiving translated data/text/audio in return.
    2. Security camera analysis - data and/or video sent to cloud service for analysis. Service may return data instructions.
  2. Multiplayer Gaming - web and consoles
    1. Game play instructions sent from client to cloud based game engine. Some instructions are time sensitive (such as location data), others are stateful (avatar selection). Dataflow is bi-directional between client and server.
    2. AR gaming requires real-world interaction, including virtual theatre - geo-separate actors with virtual backgrounds.
  3. Low-latency live streaming
    1. Unidirectional Broadcast - one to many - sports events, news, wagering, latency equivalent to social media delay and quality to support UHD, HDR, HFR, DRM.
    2. Bi-directional few-to-few video chats via server, reduced connection time/complexity compared to WebRTC. Example - Apple Facetime
  4. Cloud Game Streaming
    1. Server-side game rendering (such as Google Stadia) transmitted to thin client with low latency.
    2. Bi-directional Game play instructions (between server and client).
  5. Server-based video conferencing
    1. Simpler session establishment
    2. Censorship circumvention - preventing fingerprinting and identification during session establishment.
  6. Remote desktop
    1. Transmission of screen capture/sharing and control instructions.
    2. Collaborative work on a shared screen.
    3. Including scaling to very large audiences.
    4. Online document sharing
    5. Remote assistance temporarily "taking over" control of a system
  7. Time Synchronized Multimedia Web communications
    1. Showing a HUD-type overlay over received video with time synchronized information from sensors or game data.
    2. Add HUD overlay on top of received video from sensors or game data.
  8. IOT sensor and analytics data transfer
    1. Efficient and intermittent transmission of data. For example - sending a 1 bit flag, GPS position updates, mouse clicks on site etc.
    2. Sensor data upload - including filters, aggregation, triggers.
  9. PubSub Models - avoid long-polling
    1. Social feeds - Twitter etc, Financial tickers
    2. Messaging platforms, including Enterprise messaging infrastructure

The purpose of defining these use-cases is to extract requirements to drive and constrain the API design. These requirements are listed in the table below:

Note to editors: these requirements need to be verified and completed by persons familiar with the various fields listed above.

Requirement Description
R01 Deliver ordered and reliable data (streams)
R02 Deliver unordered and unreliable data (datagrams) with minimal latency
R03 Deliver unordered but reliable data (use new stream for each data object?)
R04 Deliver ordered and unreliable data (cancelable streams)
R05 Performant integration with existing media components such as MSE/EME.
R06 Let web applications be able to handle large amounts of data without visible user-experience degredation.