Change Request Summary: Correction to Quality Reporting Scheme Information

CR Details

• CR Number: 0194
• Specification: TS 26.247 v18.4.0
• Category: F (Correction)
• Release: Rel-18
• Work Item: NR_QoE_enh-Core

Background and Reason for Change

RAN3 identified misalignment between RAN3 and SA4 specifications regarding the usage of communication service type for QoE Measurement Collection (QMC) for MBS. This was communicated through documents S4-251660/R3-255896 and S4-260016. The issue was discussed at SA4#134 (S4-252077) and further refined in the MBS SWG Telco (S4aI260011).

Main Technical Contributions

1. Restructuring of Quality Reporting Scheme (Clause 10.1 and 10.5)

Key Changes:
- Separated generic DASH quality reporting scheme from QMC-specific functionality
- Clarified that when using MPD or OMA-DM, the Quality Reporting scheme in clause 10.5 applies
- When using QMC functionality, the Quality Reporting scheme defined in Annex L applies
- Updated clause 10.1 to reflect that QMC reporting is specified in Annex L

Moved Elements from Clause 10.5 to Annex L:
- @SliceScope attribute
- @communicationServiceType attribute
- Associated XML schema definitions for these attributes

Removed from QMC Context:
- @reportingserver attribute - not needed for QMC as per TS 26.501 clause 5.5.4

2. Updates to Annex L.1 (Configuration and Reporting)

Clarifications:
- Updated reference from clause 10.5 to Annex L.2 for QMC-specific quality reporting scheme
- Maintained explanation that @communicationServiceType attribute indicates whether DASH client should collect/report QoE metrics for:
- Unicast
- MBS broadcast
- MBS multicast
- All communication service types

3. New Annex L.2 Structure (XML Configuration)

Major Additions:

New Table X: XML Schema of QMC Configuration

Complete XML schema definition for QMC configuration including:
- QmcConfigurationType complex type
- RangeType for time-based filtering
- LocationFilterType for geographic filtering
- StreamingSourceFilterType for source filtering
- UnsignedIntVectorType for slice scope
- CommunicationServiceTypeType enumeration

Key Attributes in QMC Configuration:
- @metrics (required)
- @samplePercentage (optional)
- @reportingInterval (optional)
- @sliceScope (optional)
- @communicationServiceType (optional)
- @qoeReferenceId (optional) - network-side reference for correlation

New Table Y: Semantics of QMC Reporting Scheme Information

Comprehensive semantics table defining:
- All QMC-specific attributes and elements
- Usage indicators (Mandatory/Optional)
- Detailed descriptions for each parameter

Communication Service Type Values:
- unicast - common unicast communication type
- mbsMulticast - MBS Multicast communication service (per TS 38.300 clause 21.1)
- mbsBroadcast - MBS Broadcast communication service (per TS 38.300 clause 21.1)
- all - all communication service types (removed from QMC-specific definition)

4. XML Schema Updates

Clause 10.5 Schema Changes:
- Removed @sliceScope attribute definition
- Removed @communicationServiceType attribute definition
- Removed UnsignedIntVectorType simple type
- Removed CommunicationServiceTypeType simple type

Annex L.2 Schema Additions:
- Complete QMC-specific XML schema with namespace urn:3GPP:ns:PSS:DASH:QMC14
- All location filtering types (PolygonListType, CircularAreaListType, ShapeType)
- QMC-specific attribute definitions

5. Key Differences Between Generic DASH and QMC Reporting

| Aspect | Generic DASH (10.5) | QMC (Annex L) |
|--------|-------------------|---------------|
| Reporting Server | Required (@reportingserver) | Not applicable (uses RRC) |
| Communication Service Type | Includes "all" value | Only specific types (unicast, mbsMulticast, mbsBroadcast) |
| Configuration Delivery | MPD or OMA-DM | RRC messages |
| Report Delivery | HTTP (clause 10.6) | RRC over control plane |

Impact and Alignment

This CR ensures proper alignment between:
- SA4 specifications (TS 26.247)
- RAN3 specifications
- QMC functionality requirements
- MBS communication service type definitions (TS 38.300)

The changes maintain backward compatibility for non-QMC implementations while providing clear, separate specifications for QMC-based quality reporting.