The UE may include many detailed subfunctions that can be used individually or controlled individually by the 5GMSd-Aware Application. This clause breaks down several relevant identified subfunctions for which stage 3 specification is available.
The 5GMSd-Aware Application itself may include many functions that are not provided by the 5GMSd Client or by the 5G UE. Examples include service and content discovery, notifications and social network integration. The 5GMSd-Aware Application may also include functions that are equivalent to ones provided by the 5GMSd Client and may only use a subset of the 5GMSd client functions. The 5GMSd-Aware Application may act based on user input or may for example also receive remote control commands from the 5GMSd Application Provider through M8d.
With respect to Media Player functions, Figure 4.2.2-1 below shows more detailed functional components of a UE for media player functions to access the 5GMSd AS.
The following subfunctions are identified as part of a more detailed breakdown of the Media Player function:
Media Access Client: Accesses media content such as DASH-formatted media segments.
Media Decapsulation: Extracts the elementary media streams for decoding and provides media system related functions such as time synchronization, capability signalling, accessibility signalling, etc.
Consumption Measurement and Logging Client: Performs the measurement and logging of content consumption-related information in accordance with the Consumption Reporting Configuration part of provisioning data, supplied by the 5GMSd Application Provider to the 5GMSd AF, and forwarded by the 5GMSd AF to the Media Player via the Media Session Handler.
Metrics Measurement and Logging Client: Performs the measurement and logging of QoE metrics in accordance with the Metrics Reporting Configuration part of provisioning data, supplied by the 5GMSd Application Provider to the 5GMSd AF, and forwarded by the 5GMSd AF to the Media Player via the Media Session Handler.
DRM Client (optional): When present, the DRM client might or might not be a part of the Media Player. It provides a content protection mechanism with its unique key management and key delivery system, authentication/authorization, policy enforcement and entitlement check. The DRM Client is not defined within 5G Media Streaming specifications.
Media Decryption (optional): When present, media decryption is responsible to decrypt the media samples using the keys provided in the DRM license, and further passing to the Media Decoder to enable playback of encrypted media. The media decryption and media decoding could be implemented on a general-purpose processor in software or hardware or, for a more secure and robust architecture, the decryption, decoding and rendering could be implemented on the hardware of secure processors.
Media Decoder: Decodes the media, such as audio or video.
Media Presentation and Rendering: Presents the media using an appropriate output device and enables possible interaction with the media.
With respect to the Media Session Handler, Figure 4.2.2-2 below shows more detailed functional components of a UE to access the 5GMSd AF.
The following subfunctions are identified as part of a more detailed breakdown of Media Session Handler:
Core Functions: Realization of a "session" concept for media communications, optionally spanning multiple stateless sessions. May optionally interact with network-based 5GMSd AFs.
Metrics Collection and Reporting: executes the collection of QoE metrics measurement logs from the Media Player and sending of metrics reports to the 5GMSd AF for the purpose of metrics analysis or to enable potential transport optimizations by the network.
Consumption Collection and Reporting: executes the collection of content consumption measurement logs from the Media Player and sending of consumption reports to a 5GMSd AF about the currently consumed media within the available presentation, about the UE capabilities and about the environment of the media session for potential transport optimizations by the network or consumption report analysis.
Network Assistance: downlink streaming delivery assisting functions provided by the network to the 5GMSd Client and Media Player in the form of bit rate recommendation (or throughput estimation) and/or delivery boost. Network Assistance functionality may be supported by 5GMSd AF or ANBR-based RAN signaling mechanisms.
Media control interface(s) to configure and interact with the different UE media functions.
Media control interface for media session management.
Control interface for collectionof logged QoE metrics measurements..
Control interface for collection of logged content consumption measurements.
Decoded media samples are handed over to the media renderer.
Decrypted, compressed media samples are handed over to a trusted media decoder.
In case of encryption, the encrypted, compressed media samples are handed over to the DRM Client.
The Service Access Information is the set of parameters and addresses which are needed by the 5GMSd Client to activate and control the reception of a downlink streaming session, and to report service/content consumption and/or QoE metrics.
The Service Access Information may be provided together with other service announcement information using M8d. Alternatively, the 5GMSd Client fetches the Service Access Information from the 5GMSd AF. Regardless of how it is provided, the Service Access Information contains different information, depending on the collaboration model between the 5GMS System and the 5GMSd Application Provider, and also depending on offered features. Baseline parameters are listed in Table 4.2.3-1 below:
A list of 5GMSd AF addresses (in the form of opaque URLs) which offer the APIs for dynamic policy invocation sent by the 5GMS Media Session Handler.
Valid Policy Template Ids
A list of Policy Template identifiers which the 5GMSd Client is authorized to use.
Service Data Flow Methods
A list of recommended Service Data Flow description methods (descriptors), e.g. 5-Tuple, ToS, 2-Tuple, etc, which should be used by the Media Session Handler to describe the Service Data Flows for the traffic to be policed.
Additional identifier for this Policy Template, unique within the scope of its Provisioning Session, that can be cross-referenced with external metadata about the streaming session.
When the metrics collection and reporting feature is activated for a downlink streaming session, one or more parameter sets for metrics configuration, according to Table 4.2.3-4, are additionally present. Each metrics configuration set contains specific settings valid for that configuration, which is typically metric scheme dependent, and collection and reporting shall be done separately for each set.
The scheme associated with this metrics configuration set. A scheme may be associated with 3GPP or with a non-3GPP entity. If not specified, a default 3GPP metrics scheme shall apply.
Metrics schemes shall be uniquely identified by URIs.
A list of 5GMSd AF addresses to which metric reports shall be sent for this metrics configuration set.
The Data Network Name (DNN) which shall be used when sending metrics report for this metrics configuration set.
If not specified, the default DNN shall be used.
The sending interval between metrics reports for this metrics configuration set.
If not specified, a single final report shall be sent after the streaming session has ended.
The proportion of streaming sessions that shall report metrics for this metrics configuration set.
If not specified, reports shall be sent for all sessions.
Streaming source filter
A list of content URL patterns for which metrics reporting shall be done for this metrics configuration set.
If not specified, reporting shall be done for all URLs.
A list of metrics which shall be collected and reported for this metrics configuration set.
For progressive download and DASH streaming services, the listed metrics are associated with the 3GPP metrics scheme and shall correspond to one or more of the metrics as specified in clause 10.3 of TS 26.247 and clause 10.4 of TS 26.247, respectively.
In addition, for the 3GPP metrics scheme as applied to DASH streaming, the quality reporting scheme and quality reporting protocol as defined in clause 10.5 of TS 26.247 and clause 10.6 of TS 26.247, respectively, shall be used.
If not specified, a complete (or default if applicable) set of metrics will be collected and reported.
When 5GMSd AF-based Network Assistance is activated for a downlink streaming session the parameters from Table 4.2.3-5 below shall be additionally present.