4.5 Management based activation in NR

28.4053GPPControl and configurationQuality of Experience (QoE) measurement collectionRelease 18Telecommunication managementTS

4.5.1 Activation of measurement collection job and reporting of collected information in NR

Management Based Activation enables collection of application layer measurements from the UEs in the specified area for specified end user service type.

The parameters for the network request session are sent from the MnS Consumer via the management system to the gNBs that host the cells that are included in the QoE Measurement Collection job request in the Create MOI QMC operation [15]. A QMC Job is activated by creating a QMCJob object instance in the MnS producer.

Figure 4.5.1-1 and the text below describe the activation of QoE measurement collection.

Figure 4.5.1-1: QMC activation example for Management Based Activation and Reporting in NR

1) A QoE Measurement Collection Job begins when the MnS Consumer sends createMOI request for QMCJob to the MnS Producer serving the impacted gNB(s), and includes the parameters: serviceType, areaScope, qoECollectionEntityAddress, qoEReference, mDTAlignmentInformation, availableRANqoEMetrics and qMCConfigFile. Step 2 and step 3 are asynchronous in time with respect to Step 1; they may occur before or after step 1.

NOTE: The RAN visible QoE measurements are supported for the DASH streaming and VR services.

2) Application level measurement configuration. The Application in the UE shall send AT command +CAPPLEVMCNR [5] containing the parameter <n> set to 1 to the Access Stratum. This enables the the Access Stratum to present an unsolicited result code to the Application at a later time. Step 2 and step 3 are asynchronous in time with respect to Step 1; they may occur before or after step 1.

3) UE registration procedure. The UE shall register QMC capability with the gNB by setting qoe-Streaming-MeasReport to “supported” in UE-NR-Capability [11]. Step 2 and step 3 are asynchronous in time with respect to Step 1; they may occur before or after step 1.

4) The gNB starts a network request session, with the QoE Reference [3] given in createMOI for QMCJob [3]. For the duration of the network request session, the gNB(s) checks for connections where the UE has qoe-Streaming-MeasReport set to “supported” [11] in step 2.

5) If a UE has the wanted capability, the gNB stores the associated qoECollectionEntityAddress and starts a UE request session by sending RRCReconfiguration to the UE including serviceType, measConfigAppLayerId (set to the value of qoEReference from step 3) and measConfigAppLayerContainer.

NOTE: The IE measConfigAppLayerId indicates the identity of the application layer measurement configuration, see [11].

6) The access stratum in the UE sends an unsolicited response to the Application including app‑meas_service_type, meas_config_app_layer_id and app-meas_config_file. These IEs map directly to the IEs in step 5. The unsolicited response is for the AT command +CAPPLEVMCNR [5] which is sent from Application in step 2.

7) The QMC Job remains inactive until the Application for the specified serviceType initiates service.

8) When the Application begins service, it sends the AT command +CAPPLEVMRNR [5], including meas_config_app_layer_id and qoe_measurement_status to indicate a recording session has started, to the access stratum.

9) The UE sends the message MeasurementReportAppLayer including measConfigAppLayerId and appLayerSessionStatus to the gNB to indicate a recording session has started.

10) While active, the Application collects measurement reports. When the QMC is completed or at the end of period for periodic report, the recorded information is formatted in a QMC report, see [6] for DASH, [7] for MTSI or [13] for VR.

11) When a formatted measurement report is available, the Application sends the AT command +CAPPLEVMRNR [5] including meas_config_app_layer_id, qoe_measurement_status and app-meas_report to the Access Stratum. If the QMC Job has ended, qoe_measurement_status is set to indicate the Job has ended.

12) When the AT command +CAPPLEVMRNR is received from the Application, the Access Stratum sends the message MeasurementReportAppLayer including measConfigAppLayerId, appLayerSessionStatus and measReportAppLayerContainer to the gNB.

13) The gNB sends the QMCRecord to the MCE associated to the qoECollectionEntityAddress. The report contains the QoE Reference from step 3 and measReportAppLayerContainer from step 12.

4.5.3 Deactivation of measurement collection job in NR

4.5.3.1 Forced deactivation

When the operator technician or the management application wants to deactivate a measurement collection job, the management system sends the deactivateQMCJob operation [3] to the gNB. The gNB sets the network request session to ended, but does not delete the UE request session id and the Collection Entity Address parameters [3], as the UE still may send reports which shall be sent to the collection centre. For UE request sessions which have reported that a recording session is started, the gNB sends the RRCReconfiguration message [11] to relevant UEs. The RRCReconfiguration message is including measConfigAppLayerId set to discard application layer measurement report information in otherConfig [11]. The Access Stratum sends +CAPPLEVMC AT command [5] to the application with the discard request. The application stops the recording session and stops recording of the requested information. The QoE Reference Id and the QoE Collection Entity Address parameters [3] in the gNB are deleted when the UE request session is ended.

4.5.3.2 Deactivation of recording session

The recording session continues to be active until the session for the Application is ended.

4.5.4 Temporary stop and restart of QoE information reporting during RAN overload in NR

In case of overload in RAN, the gNB may temporarily stop the reporting from the UE by sending the RRCReconfiguration message [11] to relevant UEs. The RRCReconfiguration message [11] includes pauseReporting set to TRUE in appLayerMeasConfig to temporarily stop application layer measurement reporting. The access stratum continues recording further information until the data storage capacity for the reporting is fully used or the UE request session ends. Then the recorded data is kept until it is reported to the gNB or when the UE request session is ended.

When the overload situation in RAN is ended the gNB restart the reporting from the UE by sending the RRCReconfiguration message [11] to relevant UEs. The RRCReconfiguration message is including pauseReporting set to FALSE in appLayerMeasConfig to restart application layer measurement reporting.

The UE application level is not directly affected by the RAN overload.