QoE Metrics Reporting - Name Space Identifier required for DASH QoE metrics reporting parameters? #128
Labels
3GPP Rel-16
Issues relating to 3GPP Release 16 specifications.
3GPP Rel-17
Issues relating to 3GPP Release 17 specifications.
3GPP Rel-18
Issues relating to 3GPP Release 18 specifications.
3GPP TS 26.510
Issues relating to SA4's "Media delivery; intrns. and APIs for prov. and media sess. hndlng." spec.
3GPP TS 26.512
Issues relating to SA4's "5G Media Streaming (5GMS); Protocols" specification.
5GMS Metrics Reporting
Clarification
Milestone
Description
TS 26.512 Table 7.8.3-1 defines the
metrics
property as a non-empty list of metrics which shall be collected and reported. In the case of downlink media streaming and for the 3GPP schemeurn:3GPP:ns:PSS:DASH: QM10
the listed metrics shall correspond to the metrics specified in TS 26.247.Our current client-side implementation uses the following constants to identify which metrics shall be reported by the Media Session Handler to the 5GMS Application Function. Note our implementation does not support all metrics defined in TS 26.247 yet.
A corresponding entry in the Service Access Information fetched via M5 looks the following:
26.512 Annex E.2.1 defines the reporting parameters for 3GPP-DASH metrics. In the provided examples the identifiers are prefixed with the name space identifier defined as :
urn:3GPP:ns:PSS:DASH:QM10
.Consequently, to report all metrics of the
AvgThroughput
type the identifier looks like the followingurn:3GPP:ns:PSS:DASH:QM10#AvgThroughput
Discussion / Questions
scheme
property (see example above)?The text was updated successfully, but these errors were encountered: