Skip to content

TS 26.247: Inconsistencies in the naming of keys for "QoE for Progressive Download and DASH" #204

Description

@dsilhavy

Description

TS 26.247 Section 10 defines "QoE for Progressive Download and DASH". During the implementation of the metrics defined in Section 10.2 we found a few inconsistencies between the definition of the keys in the respective tables and the definition of the keys in the XSD schemas. In the following I am listing our findings. My reference is 3GPP TS 26.247 V19.1.0 (2026-03).

10.2.4 Average Throughput

Problem Definition in Table 27 Definition in Listing 10.6.2-1
Camel Case numbytes numBytes
Camel Case activitytime activityTime
Camel Case inactivitytype inactivityType

10.2.7 Playlist

Problem Definition in Table 30 Definition in Listing 10.6.2-1
Camel Case starttype startType
Camel Case representationid representationId
Camel Case subreplevel subrepLevel
Camel Case playbackspeed playbackSpeed
Camel Case stopreason stopReason
Camel Case and name cut off stopreasonoth stopReasonOther
Camel Case inactivitytype subrepLevel

10.2.8 MPD information

Problem Definition in Table 31 Definition in Listing 10.6.2-1
Camel Case representationid representationId
Camel Case subreplevel subrepLevel
The description is missing the frameRate attribute defined in Listing 10.6.2-1 Mpdinfo Mpdinfo

10.2.10 Device information

Listing 10.6.2-2: "Additional QoE metrics XML schema" defines the schema for DeviceInformationEntryType twice.

Metadata

Metadata

Labels

3GPP Rel-13Issues relating to 3GPP Release 13 specifications3GPP Rel-14Issues relating to 3GPP Release 14 specifications.3GPP Rel-15Issues relating to 3GPP Release 15 specifications.3GPP Rel-16Issues relating to 3GPP Release 16 specifications.3GPP Rel-17Issues relating to 3GPP Release 17 specifications.3GPP Rel-18Issues relating to 3GPP Release 18 specifications.3GPP Rel-19Issues relating to 3GPP Release 19 specifications.3GPP TS 26.247Issues relating to "Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)" spec.Correction
No fields configured for Standards.

Projects

Status
Pre-Acceptance

Relationships

None yet

Development

No branches or pull requests

Issue actions