Content for TS 26.247 Word version: 18.4.0

0f… 4 5… 6… 7… 8… 9… 10… 11… 12… 13… 14… 15 A… B… C… D… F… K… L… M…

L.1 Configuration and reporting L.2 XML configuration

L (Normative) QoE measurement collection functionalities |R14| p. 134

L.1 Configuration and reporting p. 134

As an alternative to configuration via MPD or OMA-DM, the QoE configuration can optionally be specified by the QoE Measurement Collection (QMC) functionality. In this case the QoE configuration is received via specific RRC TS 25.331 messages for UMTS, RRC TS 36.331 messages for LTE, and RRC messages for NR TS 38.331 over the control plane, and the QoE reporting is also sent back via RRC messages over the control plane.

If QMC is supported, the UE shall support the following QMC functionalities:

QoE Configuration: The QoE configuration is delivered via RRC to the UE as a container according to "Application Layer Measurement Configuration" (see TS 25.331) for UMTS, "measConfigAppLayer" (see TS 36.331) for LTE and "AppLayerMeasConfig" (see TS 38.331) for NR. The container is an octet string with gzip-encoded data (see RFC 1952) stored in network byte order. The maximum size of the container is 1000 bytes for UMTS (see TS 25.331) and LTE (see TS 36.331), and 8000 bytes for NR (see TS 38.331). The container shall be uncompressed, and is then expected to conform to XML-formatted QoE configuration data according to clause L.2 in the present document. This QoE Configuration shall be forwarded to the DASH client. The interface towards the RRC signalling is handled by the AT command +CAPPLEVMC for UMTS and LTE, and AT command +CAPPLEVMCNR for NR TS 27.007. In the case where QMC is enabled for streaming services delivered via the MBS communication service, the @communicationServiceType attribute in the QoE configuration (see clause 10.5) shall indicate whether the DASH client is requested to collect and report QoE metrics about content received via unicast, via MBS broadcast, via MBS multicast, or via all of these communication service types.
QoE Metrics: QoE Metrics from the DASH client shall be XML-formatted according to clause 10.6 in the present document. The XML data shall be compressed with gzip (see RFC 1952) and stored in network byte order into an octet string container. The maximum size of the container is 8000 bytes for UMTS (see TS 25.331) and LTE (see TS 36.331). For NR TS 38.331, the maximum size is 8000 bytes if RRC segmentation is not enabled, and 144000 bytes if enabled. The container shall be delivered via RRC to the RNC according to "Application Layer Measurement Reporting" (see TS 25.331) for UMTS, to the eNB according to "measReportAppLayer" (see TS 36.331) for LTE, and to the gNB according to "MeasurementReportAppLayer" (see TS 38.331) for NR. The behaviour if the compressed data is larger than the maximum container size is unspecified in this version of the specification. The interface towards the RRC signalling is handled by the AT command +CAPPLEVMR for UMTS and LTE, and AT command +CAPPLEVMRNR for NR TS 27.007.
The UE shall also set the QMC capability "QoE Measurement Collection for streaming services" (see TS 25.331) to TRUE for UMTS, include the QMC capability "qoe-MeasReport" (see TS 36.331) for LTE and include the QMC capability "qoe-Streaming-MeasReport" (see TS 38.331) for NR.
When a new session is started, the QoE reporting AT command +CAPPLEVMRNR TS 27.007 shall be used to send a Recording Session Indication. Such an indication does not contain any QoE report, but indicates that QoE recording has started for a session.
When the QoE configuration is to be released, an unsolicited result code, associated with the AT command +CAPPLEVMC or AT command +CAPPLEVMCNR TS 27.007 and containing the parameter <start-stop_reporting> or <start-stop_measurement> set to "1" shall be sent to the DASH client as notification of a discard request. Then the DASH client shall stop collecting quality metrics and discard any already collected information TS 28.405.

For NR, the RAN visible QoE may be supported. The gNB can use RAN visible QoE configurations to instruct the UE to collect application layer measurements for network optimization.

The RAN visible QoE configuration generated by the gNB shall be forwarded by the UE AS layer to the DASH client via AT command +CAPPLEVMCNR, including the required RAN visible QoE metrics, service type, the RRC identifier and optionally reporting periodicity. The set of RAN visible QoE metrics is a subset of the QoE metrics defined in clause 10.4. In this release of the specification, the set of RAN visible QoE metrics include "Buffer Level" and "Playout Delay for Media Startup". If the reporting periodicity for RAN visible QoE metrics is not specified, the reporting periodicity follows the baseline NR QoE configuration. The measurement interval for "Buffer Level" metric collection is given by reporting periodicity divided by "numberOfBufferLevelEntries" as specified in TS 38.331.
Based on the RAN visible QoE configuration, the RAN visible QoE report shall be delivered to the UE AS layer via AT command +CAPPLEVMRNR and the collected metrics shall be sent to the gNB via the "MeasurementReportAppLayer" message. The PDU session ID(s) corresponding to the service that is subject to RAN visible QoE measurement can also be reported by the DASH client along with the RAN visible QoE report.
When the RAN visible QoE measurement is deactivated by the gNB, the DASH client shall be notified to terminate and release the RAN visible QoE measurement.

The exact implementation is not specified here, but example signalling diagrams for UMTS, LTE and NR below show the QMC functionality with a hypothetical "QMC Handler" entity.

Copy of original 3GPP image for 3GPP TS 26.247, Fig. L-1: Example signalling diagram for UMTS

Figure L-1: Example signalling diagram for UMTS
(⇒ copy of original 3GPP image)

Copy of original 3GPP image for 3GPP TS 26.247, Fig. L-2: Example signalling diagram for LTE

Figure L-2: Example signalling diagram for LTE
(⇒ copy of original 3GPP image)

Copy of original 3GPP image for 3GPP TS 26.247, Fig. L-3: Example signalling diagram for NR

Figure L-3: Example signalling diagram for NR
(⇒ copy of original 3GPP image)

Note that the QMC Handler is only shown here as one possible implementation, and it need not be implemented as such. The corresponding QMC functionality could be built into the DASH client or into other UE entities. In this version of the specification the detailed implementation of the above functionalities is left to the UE vendor.

L.2 XML configuration p. 137

When QoE reporting is configured via the QMC functionality, the configuration is done according to the XML schema below. The interpretation of the different elements and attributes are the same as described in clauses 10.4, 10.5 and Annex F in the present document.

Note that if geographical filtering is handled on the network side (i.e. QoE reporting is turned on/off by the network depending on the UE location), no LocationFilter should be specified in the QoE Configuration, as this would mean two consecutive filterings.

Also note that the optional attribute qoeReferenceId is a reference set by the network side (see TS 28.405), which is not directly used by the client. However, if this attribute is defined, it shall be copied into each QoE report, to facilitate network-side correlation.

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:3GPP:ns:PSS:DASH:QMC14"
    elementFormDefault="qualified"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:sv="urn:3gpp:metadata:2016:PSS:schemaVersion"
    xmlns="urn:3GPP:ns:PSS:DASH:QMC14">
    <xs:element name="QmcConfiguration" type="QmcConfigurationType"/>
    
    <xs:complexType name="QmcConfigurationType">
        <xs:sequence>
            <xs:element name="Range" type="RangeType" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="LocationFilter" type="LocationFilterType" minOccurs="0"/>
            <xs:element name="StreamingSourceFilter" type="StreamingSourceFilterType" minOccurs="0" maxOccurs="unbounded"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="metrics" type="xs:string" use="required"/>
        <xs:attribute name="samplePercentage" type="xs:double" use="optional"/>
        <xs:attribute name="reportingInterval" type="xs:unsignedInt" use="optional"/>
        <xs:attribute name="qoeReferenceId" type="xs:hexBinary" use="optional"/>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
    <xs:complexType name="RangeType">
        <xs:sequence>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="startTime" type="xs:unsignedInt" use="optional"/>
        <xs:attribute name="duration" type="xs:duration" use="required"/>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
<xs:complexType name="LocationFilterType">
        <xs:sequence>
            <xs:element name="cellID" type="xs:unsignedLong" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="shape" type="ShapeType" minOccurs="0"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
    <xs:complexType name="ShapeType">
        <xs:sequence>
            <xs:element name="PolygonList" type="PolygonListType" minOccurs="0"/>
            <xs:element name="CircularAreaList" type="CircularAreaListType" minOccurs="0"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
    <xs:complexType name="PolygonListType">
        <xs:annotation>
            <xs:documentation> see [OMA MLP] </xs:documentation>
        </xs:annotation>
        <xs:sequence>
            <xs:element name="Polygon" minOccurs="0" maxOccurs="unbounded"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="ConfLevel" type="xs:unsignedInt" use="optional"/>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
    <xs:complexType name="CircularAreaListType">
        <xs:annotation>
            <xs:documentation> see [OMA MLP] </xs:documentation>
        </xs:annotation>
        <xs:sequence>
            <xs:element name="CircularArea" minOccurs="0" maxOccurs="unbounded"/>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="ConfLevel" type="xs:unsignedInt" use="optional"/>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
    <xs:complexType name="StreamingSourceFilterType">
        <xs:sequence>
            <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:attribute name="streamingSource" type="xs:string" use="required"/>
        <xs:anyAttribute namespace="##other" processContents="lax"/>
    </xs:complexType>
</xs:schema>