The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: One main motivation of mobile network evolution is to improve the user experience, which is why the evaluation of the user experience at the UE side is vital to network operators. This is especially true when the operators provide high bit rate real-time services like streaming services (typically video services), where even intermittent quality degradation is very annoying. Many of these streaming services are a significant part of the commercial traffic growth rate, therefore the focus is on the end users' experience. Quality of Experience (QoE) information collection provides detailed information at session level on a number of UEs. The capability to log information within a UE, and in particular the QoE of an end user service, initiated by an operator, provides the operator with QoE information. The collected information (specified in TS 26.247) cannot be deduced from performance measurements in the mobile network. The QoE information is information collected by the end user application in the UE. The QoE information is collected by the management system for analysis and/or KPI calculations.

The present document addresses the mechanisms used for the function Quality of Experience (QoE) measurement collection in 3GPP networks . The measurements that are collected are DASH [6], MTSI [7] and Virtual Reality (VR) (see TS 26.118) measurements. The function includes collecting QoE information from UEs frequenting a specified area or an individual UE for a specified end user service/end user service type. The document describes the activation and deactivation of a network request session, UE request session and recording session and also the reporting of recorded information [2].

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

• References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.