Open roberto-unified opened 1 month ago
The player already knows the ept associated with a segment because it is the entity decoding the media data and adding to the decode buffer.
Intermediate CDN servers admittedly do not know ept, however what use case does 'ept' provide the CDN server that 'at' does not terms of 'identifying upstream issues'? Is the main benefit that the latency can be calculated at any intermediate node?
The player may know the ept
; however, not all media players use this value to calculate the upstream latency from the origin server. Most players, such as the dash.js, only present the glass-to-glass latency.
Indeed, intermediate servers can benefit from the latency value upstream of the origin and identify upstream issues. Specifically, in live streaming scenarios where the efficiency of live encoders can be evaluated and optimized based on the ept
and at
values.
We propose the following key-value pair in CMSD-Static to enable the optimization of live streaming workflows.
ept
Example in the form of a response header:
Advantages of
ept
in combination withat
(Availability time) keys: