Support for ROUTE

[dsilhavy]

Description

The ROUTE/DASH broadcasting method is designed to deliver DASH-formatted streaming content over ROUTE in the form of objects to a large number of broadcast receivers.

Background & Important terms

• ROUTE was developed by extending FLUTE
• ROUTE optimization principles
  • Reduction in metadata frequency using template mechanism
  • Enhanced metadata embedding in (ROUTE) packet header
  • Alleviating needs to know file sizes before start of sending to optimize end to end latency

Implementation steps & recommendations

to be discussed

Related specifications or documents

• https://www.researchgate.net/publication/294137876_ROUTEDASH_IP_Streaming-Based_System_for_Delivery_of_Broadcast_Broadband_and_Hybrid_Services
• https://datatracker.ietf.org/meeting/111/materials/slides-111-tsvarea-route-real-time-transport-object-delivery-over-unidirectional-transport-00

[rbouqueau]

Status and TODO:

• PR ROUTE support using GPAC #18 (ROUTE) to be merged.
• Then the Seamless switching #19 PR is merged (Seamless switching).
• Add local service announcement (from Seamless switching #19, cf bootstrap.multipart). Update the code to make the ROUTE demo independent. We may need to test more of HLS since that what the middleware supports best..
• Add low latency. 2 options: integrate more of GPAC (in particular a HTTP server) or update the data interface to push, then make nginx deliver partial files while keeping the connection alive.
• @kuehnhammer will look into a build-time switch to enable/disable ROUTE.
• @rbouqueau will look into minimizing the footprint (build size).

[dsilhavy]

@kuehnhammer is looking into harmonizing the different branches to enable support for ROUTE, FLUTE in a single code base