Predictive Delivery, End to End

One title, from forecast to playout, across the Grand Unified Testbed

Predictive Delivery, End to End One title, from forecast to playout, across the Grand Unified Testbed DC-Pred: tomorrow's titles SC-Sel: ranked selection POST /streams stream id, or queued satellite pre-push endpoint registered (SReg) which pathway? use the far edge playout, no satellite in the loop Tel: QoE and views Predict and schedule Pre-position Serve and learn Peach · content prediction · Sequence participant Peach content prediction Demand Control · priority + selection · Sequence participant Demand Control priority + selection SCAL · HNR Demand API · Sequence participant SCAL HNR Demand API Fenix API · Arctic Space DTE · Sequence participant Fenix API Arctic Space DTE Far edge cache · testbed site · Sequence participant Far edge cache testbed site Content Steering · HNR, DASH-IF · Sequence participant Content Steering HNR, DASH-IF Player · consumer device · Sequence participant Player consumer device Legend request return async trace default message

Prediction is a demand-side decision

  • • Peach forecasts demand; it does not move content
  • • Demand Control turns the forecast into a ranked selection
  • • Nothing is testbed-specific until the request reaches SCAL

SCAL is the only door

  • • One HNR-owned Demand API fronts Fenix, FTA and CAMARA
  • • A queued Fenix response is the satellite saying "not yet"
  • • Swapping the transmission hop does not change the calls above it

The loop closes at the player

  • • Content is at the far edge before anyone requests it
  • • Steering routes the player to the cache that already holds it
  • • Telemetry returns to Peach, so the next forecast is better informed