Open dsilhavy opened 10 months ago
If we detect the change of an access network directly in the MediaSessionHandler, dispatching and handling of _access_networkchanged events are not needed, right?
If we detect the change of an access network directly in the MediaSessionHandler, dispatching and handling of _access_networkchanged events are not needed, right?
Yes, let's continue discussion in https://github.com/5G-MAG/rt-5gms-media-stream-handler/issues/56 and then adjust the issue description
Agreed to put this to the backlog as the desired behavior needs to be clarified.
Feature description
TS 26.512 Section 4.7.4 defines procedures for consumption reporting. One requirement is the handling of access network changes:
For that reason the MediaStreamHandler sends a
access_network_changed
event once the access network has changed (see https://github.com/5G-MAG/rt-5gms-media-stream-handler/issues/56). The MediaSessionHandler then needs to check ifclientConsumptionReportingConfiguration.accessReporting
is set totrue
. Iftrue
the MediaSessionHandler requests a consumption report from the MediaStreamHandler similar to what is already being done once thereportingInterval
has elapsed.Whenever a consumption report is produced, the Media Session Handler shall reset its reporting interval timer to the value of the clientConsumptionReportingConfiguration.reportingInterval property and it shall begin countdown of the timer again.