Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  18.3.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.2.5…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.8…   16.9…   16.10…   16.12…   16.12.5…   16.12.6…   16.12.6.3   16.12.7   16.13…   16.14…   16.15…   16.18…   16.19…   16.21…   16.21.3…   17…   18…   19   20…   21…   A…   B…   C…   G…

 

21  Application Layer Measurement Collection |R17|p. 241

21.1  Overviewp. 241

The QoE Measurement Collection function enables collection of application layer measurements from the UE. QoE measurement collection is supported for the following service types in NR cells:
  • QoE Measurement Collection for DASH streaming services;
  • QoE Measurement Collection for MTSI services;
  • QoE Measurement Collection for VR services.
The QoE Measurement Collection function also supports collection of QoE measurements for any of the supported service types carried by the MBS communication service. The QoE Measurement Collection is supported for the following two communication service types:
  • MBS broadcast;
  • MBS multicast.
For DASH streaming, MTSI and VR, QMC is supported in RRC_CONNECTED state only, unless the application data is delivered via the MBS broadcast communication service.
For application sessions delivered via MBS broadcast, QMC is supported in RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states. QMC for the application sessions delivered via MBS multicast is supported in RRC_CONNECTED state only. Both signalling based and management based QoE measurement collection are supported in NR SA and NR-DC. Further details of NR-DC operation can be found in TS 37.340.
Up

21.2  QoE Measurement Configurationp. 241

21.2.1  QoE Measurement Collection Activation and Reportingp. 241

The feature is activated in the gNB either by direct configuration from the OAM system (management-based activation), or by signalling from the OAM via the 5GC (signalling-based activation), containing UE-associated QoE configuration. One or more QoE measurement collection configurations can be activated at a UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference.
For signalling-based QoE measurements, the OAM initiates the QMC activation for a specific UE via the 5GC, and the gNB receives one or more QoE measurement configurations by means of UE-associated signalling. The QoE measurement configuration for signalling-based QMC activation includes an application layer measurement configuration list and the corresponding information for QoE measurement collection, e.g., QoE reference, service type, MCE IP address, slice scope, area scope, MDT alignment information, the indication of available RAN visible QoE metrics and assistance information.
For management-based QMC activation, the OAM sends one or more QoE measurement configurations directly to the gNB. The QoE measurement configuration for management-based QMC activation also includes an application layer measurement configuration list and the corresponding information for QoE measurement collection. The gNB selects UE(s) that have the required QoE measurement capability, and the measurement collection criteria related to area scope and slice scope.
An application layer measurement configuration received by the gNB from the OAM or from the 5GC is encapsulated in a transparent container, which is forwarded to a UE as measConfigAppLayerContainer in the RRCReconfiguration message (there can be multiple configurations in the same message). Application layer measurement reports received from UE's application layer are encapsulated in a transparent container and sent to the network in the MeasurementReportAppLayer message, as specified in TS 38.331. The UE can send multiple application layer measurement reports to the gNB in one MeasurementReportAppLayer message. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. A measurement configuration application layer ID conveyed in the RRC signalling is used to identify the application layer measurement configuration and report between the gNB and the UE. The measurement configuration application layer ID is mapped to the QoE reference in the gNB, and the gNB forwards the application layer measurement report to MCE together with the QoE reference. The gNB can release one or multiple application layer measurement configurations from the UE in one RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to indicate to the gNB when a QoE measurement session starts or stops for a certain application layer measurement configuration.
Up

21.2.2  QoE Measurement Collection Deactivationp. 242

The QoE Measurement Collection deactivation permanently stops all or some of the QoE measurement collection configurations at a UE, resulting in the release of the corresponding QoE measurement configuration(s) in the UE. QoE Measurement Collection deactivation is initiated by the OAM towards the gNB (via the core network in case of a signalling-based QoE measurement configuration). For a signalling-based QoE measurement configuration, the deactivation of QoE measurement collection is supported by using UE-associated NGAP signalling. A list of QoE references is used to deactivate the corresponding QoE measurement collection(s).
Upon reception of the QoE release message for an application layer measurement configuration, the UE deletes the application layer measurement configuration at the application layer and the associated parameters in the UE Access Stratum and discards any unsent application layer measurement reports corresponding to the released application layer configuration. The UE discards the reports received from the application layer when it has no associated application layer measurement configuration configured.
The network can replace a QoE measurement configuration with another one by releasing an existing QoE measurement configuration and configuring another QoE measurement configuration. The network is not expected to release a signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration.
Up

21.2.3  Handling of QMC during RAN Overloadp. 242

The QoE measurement reporting pause/resume procedure is used to pause/resume reporting of one or multiple QoE measurement configurations in a UE in RAN overload situation.
The gNB can use the RRCReconfiguration message to temporarily stop the UE from sending application layer measurement reports associated with one or multiple application layer measurement configurations. When the UE receives the QoE measurement reporting pause indication, the UE temporarily stores application layer measurement reports in the AS layer. When the UE receives the QoE measurement reporting resume indication, the UE sends the stored application layer measurement reports to the gNB.
For a QoE measurement configuration, the assistance information provided by the OAM may be considered by the gNB for deciding whether to pause/resume the QoE measurement reporting for certain QoE measurement configurations in case of RAN overload.
Up

21.2.4  QoE Measurement Handling in RRC_IDLE and RRC_INACTIVE Statesp. 242

If the UE enters RRC_INACTIVE, the UE AS configuration for the QoE is stored in the UE Inactive AS context.
If the UE enters RRC_IDLE state, the UE releases all application layer measurement configurations except the application layer configurations explicitly indicated by the gNB as applicable in RRC_IDLE and RRC_INACTIVE states.
Upon UE's transition from RRC_IDLE to RRC_CONNECTED, the gNB serving the UE should ensure that it does not release an already configured signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration.
QoE measurements for ongoing sessions should be continued when switching between 5GC Shared MBS traffic delivery and 5GC Individual MBS traffic delivery modes for MBS multicast.
When the UE resumes the connection with a gNB that does not support QMC, the UE releases all configured application layer measurement configurations.
For application measurement configurations applicable in RRC_IDLE and RRC_INACTIVE states, the UE continues on-going QoE measurement collection when entering RRC_IDLE or RRC_INACTIVE state, and also when returning to RRC_CONNECTED state. The UE may also start QoE collection according to the stored QoE configuration while in RRC_IDLE or RRC_INACTIVE state. The UE keeps the application layer measurement configurations but does not start new QoE measurement sessions when it is outside of the area scope for QoE configurations in RRC_IDLE and/or RRC_INACTIVE state. The UE stores the application layer measurement reports generated while in RRC_IDLE and/or RRC_INACTIVE state in the AS layer. The gNB can retrieve the application layer measurement reports/configurations and session status indication by configuring SRB4 or SRB5 after it receives an indication of application layer measurement report/configuration availability. The UE can send to the gNB the application layer measurement reports buffered when in RRC_IDLE and/or RRC_INACTIVE state, only when the UE has moved to RRC_CONNECTED state due to other reasons. The UE should not transit from RRC_IDLE or RRC_INACTIVE state to RRC_CONNECTED state for the sole purpose of sending stored application layer measurement reports.
For the application measurement configurations applicable in RRC_IDLE state (i.e. for MBS broadcast service), the gNB that configures the QoE measurement collection also indicates the UE the QoE reference, MCE ID, service type, area scope, QoE measurement type (signalling-based or management-based measurement), and available RVQoE metrics, per QoE reference, the UE stores the received information including the QoE reference, measurement configuration application layer ID, MCE ID, service type, area scope, QoE measurement type, and available RVQoE metrics, per QoE reference when entering RRC_IDLE. Upon UE's transition from RRC_IDLE to RRC_CONNECTED, the UE indicates the stored information to the new serving gNB, and the new serving gNB can use the information when managing the QoE configurations including configuring, releasing, updating the QoE configuration, and receiving and forwarding the QoE reports buffered in RRC_IDLE.
Up

21.2.5  Per-slice QoE Measurementp. 243

When a service is provided within a configured slice, the QoE Measurement for this service type can also be configured together with the corresponding slice scope, so that the user experience of this service can also be evaluated on a per-slice basis. Multiple QoE measurement configurations can be configured for the same service type, and each configuration can pertain to different slices, where each QoE measurement configuration is identified with a QoE reference.
The UE includes the network slice identifier inside the QoE measurement report container when sending the QoE measurement reports.
Up

21.3  QoE Measurement Continuity for Mobilityp. 243

QoE measurement collection continuity for intra-system intra-RAT/inter-RAT handover is supported, with the Area Scope parameters configured by the OAM, where the network is responsible for keeping track of whether the UE is inside or outside the area scope. A UE continues an ongoing QoE measurement even if it leaves the area scope, unless the network indicates to the UE to release the application layer measurement configuration.
For handover, the source gNB may transmit the information related to one or more application layer measurement configurations of the UE to the target gNB via XnAP or NGAP. For signalling-based QoE, the service type indication, the QoE reference, and, optionally, the container for application layer measurement configuration, MCE IP address, measurement configuration application layer ID, MDT alignment information, area scope, slice support list for QMC, available RAN visible QoE metrics, QoE measurement status, MBS communication service type, and assistance information for QoE measurement are passed to the target gNB. For management-based QoE, the QoE reference, service type indication, and, optionally, the measurement configuration application layer ID, the MCE IP address, area scope, slice support list for QMC, MBS communication service type, assistance information for QoE measurement and QoE measurement session status are passed to the target gNB. For RRC_INACTIVE state mobility, QoE measurement configuration(s) of a specific UE can be retrieved from the gNB hosting the UE context when the UE resumes to the RRC_CONNECTED state.
For signalling-based QoE, at handover to a target gNB that supports QoE measurement collection, the target gNB decides which of the application layer measurement configurations should be kept and which should be released, e.g., based on application layer measurement configuration information received from the source gNB in Xn/NG signalling.
When the UE is handed over to a target that does not support QMC, the UE releases all configured application layer measurement configurations.
The continuity of QoE measurement configuration and reporting in NR-DC scenario is supported as specified in TS 37.340.
QoE measurement collection continuity for intra-system inter-RAT handover is supported. For a handover from a source gNB to a target ng-eNB, measurements continuity for only one QoE measurement configuration can be supported when the UE connects to the target ng-eNB. The source gNB decides which QoE measurement to keep and sends the information about this QoE measurement to the target ng-eNB.
For intra-5GC handover from a source ng-eNB to a target gNB, the UE releases all LTE QoE configurations and it applies the NR QoE configuration(s), if received from the target RAT.
For intra-5GC handover from a source gNB to a target ng-eNB, the UE releases all NR QoE configuration(s) and it applies the LTE QoE configuration if received.
Up

21.4  RAN Visible QoE Measurementsp. 244

RAN visible QoE measurements are configured at the UE by the gNB, where a subset of configured QoE metrics is reported from the UE to the gNB as an explicit IE readable by the gNB. The RAN visible QoE measurements can be used by the gNB for network optimization. The RAN visible QoE measurements are supported for the DASH streaming and VR services. The gNB configures the RAN visible QoE measurement of all or some of the available RAN visible QoE metrics, where the indication of metric availability is received by the gNB as part of the management-based or the signalling-based QoE configuration. The set of available RAN visible QoE metrics is a subset of the metrics configured as part of QoE measurement configuration encapsulated in the application layer measurement configuration container. RAN visible QoE measurements and encapsulated QoE measurements can be configured together or separately. RAN visible QoE measurements can only be configured if there is a corresponding QoE measurement configuration for the same service type configured at the UE. The gNB may modify a RAN visible QoE configuration by releasing it and configuring the UE with a new RAN visible QoE configuration pertaining to the same QoE reference. In this case, the new RAN visible QoE configuration applies immediately, i.e., even during the same application session.
Multiple simultaneous RAN visible QoE measurement configurations and reports can be supported for RAN visible QoE measurements, and each RAN visible QoE measurement configuration and report is identified by the same measurement configuration application layer ID as the corresponding QoE measurement configuration and measurement report. After receiving the RAN visible QoE measurement configuration, the UE AS layer forwards the configuration to the application layer, indicating the service type, the measurement configuration application layer ID and, optionally, the reporting periodicity for RAN visible QoE. The application layer sends the RAN visible QoE measurement report associated with the measurement configuration application layer ID to the UE's AS layer. The PDU session ID(s) and QoS Flow ID(s) per PDU session ID corresponding to the service that is subject to QoE measurements can also be reported by the UE along with the RAN visible QoE measurement results.
The RAN visible QoE measurements can be reported with a reporting periodicity different from the one of the corresponding encapsulated QoE measurements, when a dedicated RAN visible QoE reporting periodicity is configured by the gNB. The UE Application layer can measure the RAN visible QoE metrics based on this reporting periodicity. If there is no reporting periodicity defined in the RAN visible QoE configuration, the UE sends both RAN visible QoE measurement reports and the QoE measurement reports to the gNB in the same MeasurementReportAppLayer message, except when QoE measurement reporting pause indication is received (e.g., in case of RAN overload). When a QoE measurement collection is paused, if there is no reporting periodicity defined in the RAN visible QoE configuration, the encapsulated QoE reports are stored at the UE's AS layer, but the RAN visible QoE reports continue to be reported to the gNB with the reporting periodicity configured for encapsulated QoE reporting.
The gNB can release one or multiple RAN visible QoE measurement configurations from the UE in one RRCReconfiguration message at any time. If the encapsulated QoE configuration is released, the corresponding RAN visible QoE configuration is released as well.
The RAN visible QoE configuration can be transferred from the source gNB to the target gNB upon mobility and from the old gNB to the new gNB during context retrieval. The target gNB or the new gNB can generate a new RAN visible QoE configuration based on the available RAN visible QoE metrics received and it can send the new RAN visible QoE configuration to the UE during handover or the RRC resume procedure.
Up

21.5  Alignment of MDT and QoE Measurementsp. 245

The radio-related measurements may be collected via immediate MDT for all types of supported services for the purpose of QoE analysis. The MCE/TCE performs the correlation of the immediate MDT measurement results and the QoE measurement results collected at the same UE.
The following is supported:
  • Alignment between a signalling-based QoE measurement and a signalling-based MDT measurement. In this case, the signalling-based QoE configuration sent to the gNB includes the NG-RAN Trace ID of the signalling-based MDT measurement.
  • Alignment between a management-based QoE measurement and a management-based MDT measurement.
The UE configured with QoE measurements sends an indication to inform the gNB about the start or the stop of a QoE measurement session of configured QoE measurements. The gNB can activate the MDT measurements that are to be aligned with the QoE measurements performed by the UE upon/after receiving the QoE measurement session start indication from the UE. The gNB may activate the MDT measurements upon/after receiving the MDT activation message from the OAM. The gNB can deactivate the aligned MDT measurements according to an OAM command which may, e.g., be triggered by the session stop indication.
The gNB includes time stamp information to the QoE measurement reports to enable the correlation of corresponding measurement results of MDT and QoE at the MCE/TCE. In addition, the gNB includes the MDT session identifiers (Trace Reference and Trace Recording Session Reference) in the corresponding QoE measurement report.
Up

21.6  QoE Measurement Collection in High Mobility Scenarios |R18|p. 245

QoE measurements can be confined to high mobility state of the UE and/or to HSDN cells.

21.7Void


Up   Top   ToC