-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QoE Metrics Reporting - Support for BufferLevel metric #33
Comments
Follow up question: Should the buffer level be derived once the metrics are requested or at a certain interval. For the latter, we can then return a list of all the collected bufferlevel entries since the last request. |
I envisage two asynchronous activities:
|
Thanks @rjb1000
This periodic interval is in place and follows the
This would indeed be required with the current implementaton as the buffer level is requested via the Exoplayer API and is currently not event driven like |
In a real world implementation, the QoE metrics sampling period is not something that would be signalled in a service catalogue feed at reference point M8 (think DVB-I). Ideally, the M1 and M5 APIs would be extended to explicitly specify the data sampling period to the Media Session Handler. I suggest you raise an issue in 5G-MAG/Standards. But, as a short term measure, I think that adding a configuration parameter to our test M8 feed isn't an unreasonable way of temporarily compensating for this gap in the specifications. |
Similar to
A period timeout solution would also be possible if signaled via M8 or M5 (see above). However, the ExoPlayer API endpoints can only be called from the main thread so we cannot simply use a timer function for this. We will need to use something like a Handler to post a Runnable on the main thread. Example report as currently generated: <QoeMetric>
<BufferLevel>
<BufferLevelEntry level="29992" t="1688980890949" />
<BufferLevelEntry level="31886" t="1688980891024" />
<BufferLevelEntry level="29972" t="1688980892972" />
<BufferLevelEntry level="31918" t="1688980892996" />
<BufferLevelEntry level="30013" t="1688980894929" />
<BufferLevelEntry level="31898" t="1688980895019" />
<BufferLevelEntry level="30020" t="1688980896923" />
<BufferLevelEntry level="31869" t="1688980897041" />
<BufferLevelEntry level="30021" t="1688980898921" />
</BufferLevel>
</QoeMetric> |
Implemented in #67 |
Feature description
Buffer level status events should be exposed by the
ExoPlayerAdapter
class and included in the QoE metrics report.Relevant specifications and corresponding clauses
Example
The text was updated successfully, but these errors were encountered: