Overall metrics configuration is done on the network level, for instance defining which geographical areas that shall have metrics collection active, and how often metrics shall be reported.
The metrics configuration(s) is/are sent from the OAM to the RAN, which does not forward that information to the UE at this stage.
Time passes, and it is assumed that the UE moves around during that period.
The UE enters an area (cell, location area, etc.,) which is inside the geographical constraint. This is discovered by the RAN, and it now needs to activate metrics reporting for the UE.
The actual metrics configuration is sent from the RAN to the Media Session Handler, via the 5G control plane.
Additional time passes, and the UE has a metrics configuration, but no streaming session has started.
A streaming session is started.
The session setup is done in conjunction with signalling transactions (not shown here).
A new metrics collection job is created in the Media Player.
A reference to the new metrics collection job is returned.
The configuration for the metrics collection job is sent to the Media Player (i.e. which metrics should be measured).
Media is delivered and rendered, and...
...more media is delivered...
The configured metrics reporting interval has passed, and the Media Session Handler now requests the collected metrics from the Media Player.
The Media Player returns the collected metrics.
The metrics are reported via the 5G control plane.
The session continues...
more media is delivered, and then the session is finished.
The Media Session Handler requests the final metrics collected.
The Media Player returns the final collected metrics.
The metrics are reported to the OAM via the 5G control plane.
The metrics collection job is deleted.
Time passes, the UE moves around.
The UE leaves the geographical area specified by the metrics configuration.
The RAN sends metrics (de)configuration to the UE, to stop future metrics collection.