Quality of Experience (QOE) measurement status processing

Abstract

Techniques for managing quality of experience (QoE) measurements by a user equipment (UE). An example method includes transmitting 1010, at a first node in a radio access network (RAN), to a second node in the RAN, measurement state information related to one or more QoE measurements configured by the first node for the UE. The second node may be associated with the first node with respect to at least one of: changing a configuration of the UE for dual connectivity, mobility of the UE, RRC resume or RRC re-establishment of the UE, switching forwarding of data for a service from a path to the UE via the first RAN node to a path to the UE via the second RAN node.

Description

[Technical Field]

[0001] The present invention relates generally to wireless communication networks, and more particularly to efficient techniques for configuring, performing and reporting various Quality of Experience (QoE) measurements by User Equipment (UE) in wireless networks. [Background technology]

[0002] Long Term Evolution (LTE) is the collective term for the so-called fourth-generation (4G) radio access technology developed within the 3rd Generation Partnership Project (3GPP®) and initially standardized in Release 8 (Rel-8) and Release 9 (Rel-9). LTE, also known as the Evolved UMTS Radio Access Network (E-UTRAN), covers a variety of licensed frequency bands and is accompanied by improvements to non-radio aspects, commonly referred to as System Architecture Evolution (SAE), including the Evolved Packet Core (EPC) network. LTE has continued to evolve through subsequent releases.

[0003] 3GPP's LTE Release 10 (Rel-10) supports bandwidths greater than 20 MHz. One key requirement for Rel-10 is backward compatibility with LTE Release 8, including spectrum compatibility. Therefore, wideband LTE Release 10 carriers (e.g., wider than 20 MHz) must appear as multiple carriers ("component carriers" or CCs) to LTE Release 8 ("legacy") terminals. Legacy terminals can be scheduled on all portions of a wideband LTE Release 10 carrier. One way to achieve this is carrier aggregation (CA), which allows a Rel-10 terminal to receive multiple CCs, each preferably with the same structure as a Rel-8 carrier. Furthermore, LTE Release 12 introduced dual connectivity (DC), which allows a UE to connect to two network nodes simultaneously, improving connection robustness and capacity.

[0004] The fifth generation of cellular systems ("5G"), also known as New Radio (NR), is currently being standardized within the Third Generation Partnership Project (3GPP). NR is being developed with maximum flexibility to support several substantially different use cases, including enhanced mobile broadband (eMBB), machine-type communications (MTC), ultra-reliable and low-latency communications (URLLC), sidelink device-to-device communications (D2D), and several other use cases.

[0005] 5G / NR technology shares many similarities with LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the downlink (DL, i.e., transmission from the network) and both CP-OFDM and DFT-S-OFDM (DFT-Spread OFDM) in the uplink (UL, i.e., transmission to the network). As another example, in the time domain, NR DL and UL physical resources are organized into equal-sized 1 ms subframes. A subframe is further divided into multiple slots of equal duration, each containing multiple OFDM-based symbols.

[0006] However, NR cells allow for much more flexible configuration of time-frequency resources than LTE cells. Furthermore, NR networks not only provide coverage in cells like LTE, but also in "beams." Generally, a DL "beam" is a coverage area of ​​a network-transmitted reference signal (RS) that can be measured or monitored by a user equipment (UE, e.g., a wireless communication device).

[0007] Quality of Experience (QoE) measurements are specified for UEs operating in LTE networks and older generation UMTS networks. In both networks, measurements follow the same high-level principles. The goal is to measure the end user's experience when using a particular application on the network. For example, QoE measurements for streaming services and MTSI (Mobile Telephony Services for IMS) are supported in LTE. QoE measurements are also required for UEs operating in NR networks, so QoE measurements are specified for NR.

[0008] The solutions for LTE and UMTS are similar and the overall principle is as follows: Quality of Experience Measurement Collection (QMC) enables the configuration of application layer measurements in the UE and the transmission of QoE measurement results via Radio Resource Control (RRC) signaling. Application layer measurement configuration received from OAM or Core Network (CN) is encapsulated in a transparent container and forwarded to the UE in a downlink RRC message. Application layer measurements received from higher layers in the UE are encapsulated in a transparent container and sent to the network in an uplink RRC message. The result container is forwarded to the Trace Collector Entity (TCE).

[0009] A new study item, "Research on NR QoE management and optimization for diverse services," was approved in NR Release 17. The purpose is to explore solutions for QoE measurement in NR, including not only streaming services like LTE, but also other services such as AR / VR (augmented reality and virtual reality) and URLLC. Based on the requirements of various services, NR research will also include more adaptive QoE management schemes that enable intelligent network optimization to meet the user experience of diverse services.

[0010] Radio Resource Control (RRC) signaling is used to configure application layer measurements in the UE and to collect QoE measurement result files from the configured UE. In particular, application layer measurement configurations from the core network (e.g., EPC) or the network's Operations, Administration, and Maintenance (OAM) function (also known as a "Network Management System" or "NMS") are encapsulated in transparent containers and sent to the UE's serving RAN node, which then forwards them to the UE in RRC messages. Application layer measurements made by the UE are encapsulated in transparent containers and sent in RRC messages to the serving RAN node, which then forwards the containers to the Trace Collector Entity (TCE) or Measurement Collection Entity (MCE) associated with the core network.

[0011] Measurements may be initiated in a management-based manner, i.e. from the O&M node, in a generic manner, e.g. for a group of UEs, towards the RAN, or they may also be initiated in a signaling-based manner, i.e. from the CN towards the RAN, e.g. for a single UE. The measurement configuration contains the measurement details, which are encapsulated in a container that is transparent to the RAN.

[0012] When initiated via the core network, measurements are initiated for a specific UE. In the case of LTE, a "TRACE START" S1AP message is used. This message carries, among other things, details about the measurement configuration that the application should collect (a "Container for Application Layer Measurement Configuration" information element, transparent to the RAN) and details reaching the trace collection entity where the measurements should be sent.

[0013] The RAN is not aware of when a streaming session is ongoing in the UE access stratum, and is not aware of when measurements are ongoing. When the RAN stops measuring is an implementation decision, typically when the UE moves out of the measurement area.

[0014] One of the opportunities that legacy solutions offer is the ability to maintain QoE measurements for the entire session, even during handover. The background to the LTE (E-UTRAN) solution is as follows:

[0015] E-UTRAN - Application Layer Measurement Capabilities In E-UTRAN, UE Capability Transfer is used to transfer UE radio access capability information from the UE to the E-UTRAN, as shown in Figure 1.

[0016] The UE-EUTRA-Capability information element (IE) is used to convey E-UTRA UE radio access capability parameters and mandatory functionality feature group indicators to the network.

[0017] In the response message "UECapabilityInformation", the UE may include the "UE-EUTRA-Capability" IE. The "UE-EUTRA-Capability" IE may contain the "UE-EUTRA-Capability-v1530-IE" that the UE can use to indicate whether it supports QoE measurement collection for streaming services and / or MTSI services, as detailed in the "MeasParameters-v1530" encoding below.

[0018] Contribution CR4297 (R2-2004624) of 3GPP TS 36.331 v16.0.0 at 3GPP TSG RAN2 Meeting #110 proposed an extension to the "UE-EUTRA-Capability" IE, which may include a "measParameters-v16xy" IE containing a qoe-Extensions-r16IE within the "UE-EUTRA-Capability-v16xy-IE". The qoe-Extensions-r16IE can be used to indicate whether the UE supports Release 16 extensions for QoE measurement collection, i.e., whether the UE supports multiple QoE measurement types at a time, and whether the UE supports signaling of interiorArea, sessionRecordingIndication, qoe-Reference, temporaryStopQoE, and restartQoE.

[0019] E-UTRAN - Application Layer Measurement Reporting The purpose of the "Application Layer Measurement Reporting" procedure described in 3GPP TS 36.331 and shown in Figure 2 is to inform the E-UTRAN about application layer measurement reports.

[0020] A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure if application layer measurements are configured, i.e., if measConfigAppLayer is configured by E-UTRAN.

[0021] When initiating the procedure, the UE: 1> If application layer measurement is configured, SRB4 is configured, and the UE receives application layer measurement report information from higher layers: 2>Set the value of the application layer measurement report information in measReportAppLayerContainer of the MeasReportAppLayer message; 2>Set the serviceType of the MeasReportAppLayer message to the type of application layer measurement report information; 2> Send the MeasReportAppLayer message to the lower layer for transmission via SRB4.

[0022] E-UTRAN - QoE measurement configuration setup and release - RRC signalling The RRCConnectionReconfiguration message is used to reconfigure the UE in order to set up or release it for application layer measurements. This is signaled in the "measConfigAppLayer-15" IE within the "OtherConfig" IE.

[0023] This setup includes a transparent container measConfigAppLayerContainer that specifies the QoE measurement configuration for the target application, and a serviceTypeIE that indicates the application (or service) for which QoE measurements are configured. Supported services are streaming and MTSI.

[0024] At 3GPP TSG RAN2 Meeting #110, contribution CR4297 (R2-2004624) of 3GPP TS 36.331 v16.0.0 proposed an extension to the QoE measurement configuration.

[0025] measConfigAppLayerToAddModList-r16 can be used to add or modify multiple QoE measurement configurations (up to maxQoE-Measurement-r16). measConfigAppLayerToReleaseList-r16IE may be used to remove multiple QoE measurement configurations (up to maxQoE-Measurement-r16).

[0026] E-UTRAN - QoE Measurement Reporting - RRC Signalling As specified in 3GPP TS 36.331, the MeasReportAppLayerRRC message is used by the UE to send the QoE measurement results of an application (or service) to an E-UTRAN node. The service for which the report is being sent is indicated in the "serviceType" IE.

[0027] Contribution CR4297 (R2-2004624) of 3GPP TS 36.331 v16.0.0 at 3GPP TSG RAN2 Meeting #110 proposed adding a QoE reference to MeasReportAppLayerIE(s) containing the PLMN ID and an identifier for the QoE measurement collection.

[0028] For E-UTRAN, examples of desirable UE behavior regarding application layer measurement reporting are described in CR4297 (R2-2004624).

[0029] UE application layer measurement configuration The “UE Application layer measurement configuration” IE is described in 3GPP TS 36.413 v16.3.0 and TS 36.423 v16.3.0.

[0030] Area scope for QoE measurements According to 3GPP TS 28.405, the area scope parameter defines the area in terms of cells or tracking areas / routing areas / location areas where QoE measurement collection (QMC) will take place. If this parameter is not present, QMC shall be performed over the entire PLMN specified in the PLMN target.

[0031] The area scope parameter in UMTS is one of the following: - A list of cells identified by CGI. Up to 32 CGIs can be defined. - A list of routing areas identified by RAI. Up to eight RAIs can be defined. - A list of location areas identified by LAI. Up to eight LAIs can be defined. The area scope parameter for LTE is one of the following: - A list of cells identified by E-UTRAN-CGI. Up to 32 CGIs can be defined. - A list of tracking areas identified by TAC. Up to eight TACs can be defined. This parameter is mandatory if area-based QMC is requested. Summary of the Invention

[0032] Embodiments of the techniques and apparatus described herein enable coordinated handling between RAN nodes of QoE measurements and associated radio-related measurements (such as MDT measurements) configured for a UE, which handling relates to the following connection procedures for this UE: dual connectivity, mobility, RRC resume, RRC re-establishment.

[0033] Some embodiments of the present disclosure include example methods (e.g., procedures) for managing Quality of Experience (QoE) measurements in a Radio Access Network (RAN). These example methods are executable by a User Equipment (UE, e.g., wireless device, IoT device, modem, etc.) in communication with a Radio Access Network (RAN) node (e.g., base station, eNB, gNB, ng-eNB, en-gNB, etc.).

[0034] An exemplary method according to some of the embodiments described herein is performed by a first node in a Radio Access Network (RAN) for managing Quality of Experience (QoE) measurements by a User Equipment (UE), the exemplary method including transmitting, to a second node in the RAN, measurement state information related to one or more QoE measurements configured for the UE by the first node.

[0035] A corresponding method according to some of the embodiments described herein is performed by a second node in a Radio Access Network (RAN) for managing Quality of Experience (QoE) measurements by a User Equipment (UE). This example method includes receiving, from a first node in the RAN, measurement state information related to one or more QoE measurements configured for the UE by the first node.

[0036] Another embodiment includes a method in a user equipment (UE) for processing configuration of quality of experience (QoE) measurements in a radio access network (RAN). This exemplary method includes receiving a QoE measurement configuration (QMC) for one or more service types or applications from a RAN node and determining that the UE already has a QoE configuration for the same service types or applications.The method includes, when the determination is made, discarding the new configuration, releasing the old configuration and configuring itself and its upper layers with the new configuration, suspending the new configuration, suspending the old configuration and activating the new configuration; if the old configuration is already in a suspended state when the new configuration is received, maintaining the new configuration active and releasing the old configuration or maintaining the old configuration in a suspended state; if a service / application type or service subtype is specified by the new QoE configuration, configuring itself and its upper layers for the target service or application type or subtype with the specified service and maintaining the old configuration for the remaining applications; in a dual connectivity scenario, if one QoE configuration is received from a master node and the other from a secondary node, releasing the QoE configuration received from the secondary node and maintaining the QoE configuration received from the master node; in a dual connectivity scenario, one QoE configuration the QoE configuration received from the secondary node and keeping the QoE configuration received from the master node active if one is received from the master node and the other from the secondary node; maintaining the old configuration and releasing or suspending the new configuration if an ongoing application session (or, in case of multiple sessions, all ongoing application sessions) of the service type and / or service subtype for which the QoE configuration is intended is currently using a radio bearer towards the RAN node on which the old configuration was received; maintaining the new configuration and releasing or suspending the old configuration if an ongoing application session (or, in case of multiple sessions, all ongoing application sessions) of the service type and / or service subtype for which the QoE configuration is intended is currently using a radio bearer towards the RAN node on which the new configuration was received.

[0037] The disclosed techniques and apparatus enable consistent processing of QoE measurements and radio-related measurements (such as MDT) related to QoE measurements in scenarios where multiple RAN nodes are involved in attachment procedures for a wireless terminal or group of wireless terminals.

[0038] These and other objects, features, and advantages of embodiments of the present disclosure will become apparent from the following detailed description taken in conjunction with the drawings, which are briefly described below. [Brief explanation of the drawings]

[0039] [Figure 1] FIG. 1 illustrates UE capability transfer in LTE (E-UTRAN). [Figure 2] FIG. 1 illustrates application layer measurement reporting in E-UTRAN. [Figure 3] FIG. 1 is a high-level block diagram illustrating an example architecture of a Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN) and Evolved Packet Core (EPC) network as standardized by 3GPP. [Figure 4] FIG. 1 is a high-level diagram illustrating an example of a 5G / NR network architecture. [Figure 5] FIG. 1 is a high-level diagram illustrating an example of a 5G / NR network architecture. [Figure 6] A diagram showing an example of the configuration of the protocol stack of the NR user plane (UP) and control plane (CP). [Figure 7A] 1 illustrates various procedures between UTRAN and UE for Quality of Experience (QoE) measurements in legacy UMTS networks; [Figure 7B] 1 illustrates various procedures between UTRAN and UE for Quality of Experience (QoE) measurements in legacy UMTS networks; [Figure 7C] 1 illustrates various procedures between UTRAN and UE for Quality of Experience (QoE) measurements in legacy UMTS networks; [Figure 7D]1 illustrates various procedures between UTRAN and UE for Quality of Experience (QoE) measurements in legacy UMTS networks; [Figure 8A] A diagram illustrating various aspects of a QoE measurement configuration for a UE in an LTE network. [Figure 8B] A diagram illustrating various aspects of a QoE measurement configuration for a UE in an LTE network. [Figure 9A] A diagram illustrating various aspects of QoE measurement collection for a UE in an LTE network. [Figure 9B] A diagram illustrating various aspects of QoE measurement collection for a UE in an LTE network. [Figure 9C] A diagram illustrating various aspects of QoE measurement collection for a UE in an LTE network. [Figure 10] FIG. 1 is a flow diagram of an example method (e.g., procedure) for a first RAN node (RNN, e.g., eNB, gNB, ng-eNB, etc., or component(s) thereof) in accordance with various example embodiments of the present disclosure. [Figure 11] FIG. 10 is a flow diagram of an example method (e.g., procedure) for a second RAN node (RNN, e.g., eNB, gNB, ng-eNB, etc., or component(s) thereof) in accordance with various example embodiments of the present disclosure. [Figure 12] 1 is a flow diagram of an example method (e.g., procedure) for a user equipment (UE, e.g., wireless device, IoT device, etc., or component(s) thereof), in accordance with various example embodiments of the present disclosure. [Figure 13] FIG. 1 is a block diagram of an example wireless device or UE in accordance with various example embodiments of the present disclosure. [Figure 14] FIG. 2 is a block diagram of an example network node in accordance with various example embodiments of the present disclosure. [Figure 15] FIG. 1 is a block diagram of an example network configured to provide over-the-top (OTT) data services between a host computer and a UE, in accordance with various example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0040] Certain embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0041] In general, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is expressly given and / or implied from the context in which they are used. All references to an element, apparatus, component, means, step, etc. shall be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding other steps and / or it is implied that a step must follow or precede other steps. Any feature of any embodiment disclosed herein may also be applied to other embodiments, where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa.

[0042] Additionally, the following terms are used in the following description: Wireless Node: As used herein, a "wireless node" can be either a "wireless access node" or a "wireless device." Radio Access Node: As used herein, a “radio access node” (or equivalently, a “radio network node,” “radio access network node,” or “RAN node”) may be any node of a Radio Access Network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, base stations (e.g., New Radio (NR) base stations (gNB / en-gNB) in 3GPP fifth-generation (5G) NR networks or enhanced or evolved Node Bs (eNB / ng-eNB) in 3GPP's LTE networks), base station distributed components (e.g., CU and DU), base station control and / or user plane components (e.g., CU-CP, CU-UP), high-power or macro base stations, low-power base stations (e.g., micro, pico, femto, or home base stations, etc.), integrated access backhaul (IAB) nodes, transmission points, remote radio units (RRUs or RRHs), and relay nodes. Thus, the term "RAN node" may apply, for example, to any of the following: gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, IAB node, IAB donor DU, IAB donor CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB. Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network Gateway (P-GW), an Access and Mobility Management Function (AMF), a Session Management Function (AMF), a User Plane Function (UPF), a Service Capability Exposure Function (SCEF), etc. Wireless Device: As used herein, a "wireless device" (abbreviated "WD") is any type of device that can gain access to (i.e., receive service from) a cellular communications network by wirelessly communicating with network nodes and / or other wireless devices. Wireless communication may include transmitting and / or receiving radio signals using electromagnetic waves, radio waves, infrared rays, and / or other types of signals suitable for conveying information over the air. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cellular phones, VoIP phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), mobile telecommunications (MTC) devices, Internet of Things (IoT) devices, in-vehicle wireless terminal equipment, etc. Unless otherwise noted, the term "wireless device" is used interchangeably herein with the term "user equipment" (abbreviated "UE"). Network Node: As used herein, a "network node" refers to any node that is part of the radio access network (e.g., the radio access node or equivalent designation described above) or core network (e.g., the core network node described above) of a cellular communications network. Functionally, a network node is a configured, arranged, and / or operable device that can communicate directly or indirectly with wireless devices and / or other network nodes or equipment of the cellular communications network, enable and / or provide wireless access to wireless devices, and / or perform other functions (e.g., management) in the cellular communications network. The terms "QoE measurement report", "QoE report", "measurement report" and "report" are used interchangeably. The terms "QoE measurement configuration", "QoE measurement", "QoE configuration" and "application layer measurement configuration" are used interchangeably. The terms "service" and "application" are used interchangeably. The terms "MCE" and "TCE" are used interchangeably.

[0043] It should be noted that this specification focuses on 3GPP cellular communication systems, and therefore 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems. Furthermore, although the term "cell" is used herein, it should be understood that a beam may be used instead of a cell (particularly with respect to 5G NR), and therefore the concepts described herein apply equally to both cells and beams.

[0044] As noted above, 3GPP Release 17 agrees to provide RAN nodes with visibility into QoE reporting so that they can adapt various aspects of performance based on the UE's QoE measurements. However, adapting traditional QoE measurements for use by RAN nodes in this manner presents various issues, challenges, and / or difficulties, which are discussed in more detail below following the description of LTE and NR network architectures.

[0045] One approach to handling QoE measurements for a UE when setting up and operating in dual connectivity where a first network node acts as an MN and a second network node acts as an SN may include the following steps performed by the first RAN node: - Creating a QoE configuration for the UE; - transmitting all or part of the QoE configuration to the UE; - transmitting all or part of the QoE configuration to a second network node when setting up or reconfiguring the SN (wherein the SN-related QoE configuration and the MN-related QoE configuration may be different); There is a possibility of receiving QoE measurement data from a second network node.

[0046] This approach may also satisfy the requirement that measurements should continue until the end of a session, even if the UE moves out of the coverage area during the session. This can be achieved by the network controlling the start and stop of measurements, for example, by area updates. For example, in one approach, the network can send a release command to release the QoE measurements. Session feedback indications may be used by the network to help it know when to stop measurements, for example. These approaches may be used, for example, when the UE performs a handover or re-establishes a connection to a cell controlled by a node outside the configured coverage area.

[0047] However, using this approach, some issues remain unresolved. For example, when a first RAN node and a second RAN node are both involved in a connectivity procedure (MR-DC, mobility, resume, re-establishment, etc.) with a wireless terminal / UE, and the first RAN node configures the wireless terminal for QoE measurements, there are some scenarios where the second RAN node is unaware of: - Status information of QoE measurements configured in the wireless terminal - the state of radio measurements (such as MDT) configured in the radio terminal and related to QoE measurements; - the action to be taken with respect to the QoE measurements configured in the wireless terminal; - Actions configured in the wireless terminal and to be performed regarding radio measurements (such as MDT) related to QoE measurements.

[0048] Since the second RAN node is unaware of the above states and actions, it may happen that the second node tampers with (eg, overwrites) the ongoing QoE measurements configured for the UE.

[0049] This document presents a solution to enable coordinated processing between RAN nodes of QoE measurements configured for UEs and related radio-related measurements (e.g. MDT measurements) related to the following UE-related connection procedures (dual connectivity, mobility, RRC resume, RRC re-establishment).

[0050] Non-limiting examples of applicability of the proposed solution are listed below, where state information about already configured QoE measurements is transmitted from one RAN node to another. Examples of state information are one or more of the following: - Identification of QoE measurement configurations and corresponding setting details; - information about whether the measurement configuration is active, suspended, to be resumed, to be stopped or inactive; - remaining time of the QoE measurement collection process (after which the process will be stopped); - a list of network slice identifiers on which the QoE measurements for the configuration were collected; -MDT measurement configuration in conjunction with QoE measurement configuration; - the size of the QoE measurement report signaled to the TCE; - the period within which the QoE measurement report must be notified to the TCE; An indication, signaled together with the QoE report, indicating whether the QoE report has already been signaled to the TCE.

[0051] Example 1): An MR-DC-capable UE is initially configured with single connectivity to a first cell provided by a first RAN node. Additionally, there is a second RAN node serving a second cell that is available to serve the UE, but the UE is not configured to connect to this cell either, i.e., it is not initially configured for MR-DC operation (the reason for this may be implementation-specific). Alternatively, there is a second RAN node serving a second cell that is unavailable to serve the UE, e.g., due to an energy saving policy. During or after the initial connection setup to the first cell, the first RAN node sends an RRC message to the UE containing a QoE configuration for QoE measurement. Subsequently, the second cell provided by the second RAN node becomes available, and the UE is reconfigured for MR-DC operation using two cells: one cell is the second cell of the second RAN node, and the other cell is either the first cell of the first RAN node or the third cell of a third RAN node. During the reconfiguration from single connectivity to dual connectivity, information about the previously configured status of QoE measurements is sent from the first RAN node to the second RAN node. If the dual connectivity constitutes a third cell of a third RAN node, the first RAN node sends the previously configured status of QoE measurements to the third RAN node. 1. As an example, in the case of EN-DC, the UE is initially configured with a single LTE connection to a first E-UTRA cell of a first eNB, and a second NR cell served by a second gNB is present and available but not in use (or the second NR cell is unavailable). The eNB sends an RRC message containing the QoE configuration to the UE for QoE measurement. The UE is then reconfigured for EN-DC. The state of the QoE configuration is transmitted from the first eNB to the second gNB. 2. For NR-DC, as another example, a UE may be initialized with a single NR connection to a first NR cell of a first gNB, and a second NR cell provided by a second gNB may be present and available but not in use (or alternatively, the second NR cell may be unavailable). The first gNB may send an RRC message including a QoE configuration to the UE for QoE measurement. The UE is then reconfigured for NR-DC. The state of the QoE configuration is transmitted from the first gNB to the second gNB.

[0052] Example 2): An MR-DC capable UE is initially configured with dual connectivity towards a first cell served by a first RAN node and a second cell served by a second RAN node. During the initial connection setup or during the lifetime of the connection, the first RAN node sends an RRC message containing a QoE configuration to the UE for QoE measurements. Subsequently, a third cell provided by a third RAN node becomes available and the UE configuration is changed to either replace the first cell of the first RAN node with the third cell of the third RAN node or replace the second cell of the second RAN node with the third cell of the third RAN node. The state of the QoE configuration is transmitted from the first RAN node to the third RAN node or from the second RAN node to the third RAN node.

[0053] Case 3): The UE is in a single connectivity state to a first RAN node or in a dual connectivity state to the first RAN node and a second RAN node. The first RAN node sends an RRC message with QoE configuration to the UE for QoE measurement. The UE then performs mobility towards a cell served by a third RAN node. The state of the QoE configuration is transmitted from the first RAN node to the third RAN node.

[0054] Case 4): UE with single connection to a first RAN node or dual connectivity to a first and second RAN node. The first RAN node sends an RRC message containing QoE configuration to the UE for QoE measurements and optionally sends the state of the QoE measurements to the second RAN node. The first RAN node (and optionally the second RAN node in case of dual connectivity) maintains the state of the QoE configuration for the UE. The UE then transitions to RRC inactive. In the cell served by the third RAN node Execute RRC resume. The third RAN node obtains the state of the UE's QoE configuration from the first RAN node (if there was dual connectivity before the transition to inactive, it may obtain the QoE configuration from the second RAN node).

[0055] Example 5): There is a UE with single connectivity to a first RAN node or dual connectivity to a first RAN node and a second RAN node. The first RAN node sends an RRC message to the UE containing QoE configuration for QoE measurements and optionally sends the state of the QoE measurements to the second RAN node. The first RAN node (and optionally the second RAN node in case of dual connectivity) maintains the state of the QoE configuration for the UE. Thereafter, e.g. Following a radio link failure, the UE Towards cells served by the third RAN node Perform RRC re-establishment. The third RAN node fetches the UE's QoE configuration state from the first RAN node (and (potentially) from the second RAN node in case of dual connectivity before re-establishment).

[0056] Example 6): A UE is configured with dual connectivity (EN-DC or NR-DC) to a first RAN node and a second RAN node. Application session data for a service for which QoE measurement is desired is carried to the UE via the first RAN node, and the first RAN node sends an RRC message to the UE containing a QoE configuration for QoE measurement. Thereafter, Data of an application session of a service for which QoE measurements have been configured is reconfigured to be transmitted to the UE via a second RAN node instead of being transmitted to or received from the UE via the first RAN node. The state of the QoE configuration is transmitted from the first RAN node to the second RAN node.

[0057] Each of the above examples 1) through 6) describes example events involving one UE. Furthermore, signaling procedures, e.g., related to dual connectivity, mobility, RRC resume, and RRC re-establishment, are typically performed for one UE at a time. However, the operations described herein are equally applicable to events affecting a group of UEs simultaneously, where QoE configuration state transfer between two RAN nodes may occur simultaneously (e.g., in the same message) for multiple UEs and their QoE configurations. An example of an event affecting a group of UEs is load balancing, where a group of UEs are simultaneously migrated from one IAB donor CU to another IAB donor CU.

[0058] To help put these technologies in context, Figure 3 shows an overall example architecture of a network consisting of LTE and SAE as shown in Figure 1. E-UTRAN 100 includes one or more evolved node Bs (eNBs), such as eNBs 105, 110, and 115, and one or more user equipment (UEs), such as UE 120. As used within 3GPP standards, "user equipment" or "UE" refers to any wireless communication device (e.g., a smartphone or computing device) that can communicate with 3GPP standards-compliant network equipment such as E-UTRAN and UTRAN and / or GERAN, as third-generation ("3G") and second-generation ("2G") 3GPP RANs are commonly known.

[0059] As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in the uplink and downlink, as well as security of communications with UEs. These functions reside in eNBs, such as eNBs 105, 110, and 115. Each of the eNBs may provide a geographic coverage area containing one or more cells, including cells 106, 111, and 116, which are served by eNBs 105, 110, and 115, respectively.

[0060] The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1. The eNBs are also responsible for the E-UTRAN interface to the EPC 130, specifically the S1 interface to the Mobility Management Entity (MME) and Serving Gateway (SGW), collectively shown in Figure 1 as MME / S-GWs 134 and 138. Generally, the MME / S-GW handles both the overall control of the UE and the data flow between the UE and the rest of the EPC. More specifically, the MME handles the signaling (e.g., control plane) protocols between the UE and the EPC, known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as a local mobility anchor for data bearers when the UE moves between eNBs, such as eNBs 105, 110, and 115.

[0061] The EPC 130 may also include a Home Subscriber Server (HSS) 131 that manages user and subscriber-related information. The HSS 131 may also provide support functions in mobility management, call and session setup, user authentication, and access authorization. The functionality of the HSS 131 may relate to the functionality or operation of a legacy Home Location Register (HLR) and Authentication Center (AuC). The HSS 131 may also communicate with the MMEs 134 and 138 via their respective S6a interfaces.

[0062] In some embodiments, the HSS 131 can communicate with a User Data Repository (UDR) (labeled EPC-UDR 135 in FIG. 3) via a Ud interface. The EPC-UDR 135 can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor-specific), ensuring that the encrypted credentials stored in the EPC-UDR 135 cannot be accessed by vendors other than the vendor of the HSS 131.

[0063] The multiple access scheme of the LTE PHY is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in the downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) with a cyclic prefix in the uplink. To support transmission in paired and unpaired spectrum, the LTE PHY supports both Frequency Division Duplex (FDD) (including full-duplex and half-duplex operation) and Time Division Duplex (TDD). An LTE FDD downlink (DL) radio frame has a fixed duration of 10 ms and consists of 20 slots, numbered 0 through 19 (each slot has a fixed duration of 0.5 ms). A 1 ms subframe consists of two consecutive slots, where subframe i consists of slots 2i and 2i+1.

[0064] As briefly mentioned above, LTE Release 12 introduced the Dual Connectivity (DC) framework. In LTE DC, a UE is configured with a Master Cell Group (MCG) associated with a Master eNB (MeNB) and a Secondary Cell Group (SCG) associated with a Secondary eNB (SeNB). Each CG includes a Primary Cell (PCell) and optionally one or more Secondary Cells (SCells). The term "Special Cell" (abbreviated "SpCell") refers to the PCell of the MCG or the PSCell of the SCG, depending on whether the UE's Medium Access Control (MAC) entity is associated with the MCG or SCG, respectively. In non-DC operation (e.g., CA), the SpCell refers to the PCell. The SpCell is always active and supports Physical Uplink Control Channel (PUCCH) transmissions and contention-based random access by the UE.

[0065] 4 shows a high-level diagram of a 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 299 and a 5G Core (5GC) 298. The NG-RAN 299 may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 200 and 250, connected via interfaces 202 and 252, respectively. Additionally, the gNBs may connect to each other via one or more Xn interfaces, such as Xn interface 240 between gNBs 200 and 220. With respect to the NR interface to the UE, each of the gNBs may support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.

[0066] The NG-RAN299 is divided into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and the interfaces between them, are defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant TNL protocols and functions are specified. The TNL provides services for user plane transmission and signaling transmission. In some configuration examples, each gNB is connected to all 5GC nodes within the "AMF domain" defined in 3GPP TS 23.501. If supported, NDS / IP shall be applied to secure CP and UP data in the TNL of the NG-RAN interface.

[0067] The RAN logical node of the NG shown in FIG. 4 includes a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 200 includes gNB-CU 210 and gNB-DUs 220 and 230. A CU (e.g., gNB-CU 210) is a logical node that performs various gNB functions, such as hosting upper layer protocols and controlling the operation of the DUs. Each DU is a logical node that hosts lower layer protocols and may include various subsets of gNB functions depending on the functional division. Each CU and DU may include various circuits necessary to perform their respective functions, including processing circuits, transceiver circuits (e.g., for communication), and power supply circuits. Furthermore, the terms “central unit” and “centralized unit” are used interchangeably herein, as are the terms “distributed unit” and “decentralized unit.”

[0068] The gNB-CU connects to the gNB-DU via respective F1 logical interfaces, such as interfaces 222 and 232 shown in Figure 4. The gNB-CU and connected gNB-DU are visible only to other gNBs and 5GC as gNBs; that is, the F1 interface is not visible beyond the gNB-CU. In the gNB split CU-DU architecture shown in Figure 4, DC can be achieved by allowing a UE to connect to multiple DUs served by the same CU or by allowing a UE to connect to multiple DUs served by different CUs.

[0069] FIG. 5 shows another high-level diagram of an example 5G network architecture, including a Next Generation Radio Access Network (NG-RAN) 399 and a 5G Core (5GC) 398. As shown, the NG-RAN 399 may include gNBs 310 (e.g., 310a, b) and ng-eNBs 320 (e.g., 320a, b), interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs also connect to the 5GC 398 via an NG interface, and more specifically to AMFs (Access and Mobility Management Functions) 330 (e.g., AMFs 330a, b) via respective NG-C interfaces and to UPFs (User Plane Functions) 340 (e.g., UPFs 340a, b) via respective NG-U interfaces. Additionally, the AMFs 330a, b can communicate with one or more Policy Control Functions (PCFs, e.g., PCFs 350a, b) and Network Exposure Functions (NEFs, e.g., NEFs 360a, b).

[0070] Each of the gNBs 310 can support an NR radio interface, including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of the ng-eNBs 320 can support an LTE radio interface. However, unlike traditional LTE eNBs, the ng-eNB(s) 320 connect to 5GC via an NG interface. Each of the gNBs and ng-eNBs can provide a geographic coverage area that includes more than one cell, such as cells 311a-b and 321a-b shown in FIG. 3. Depending on the particular cell in which it is located, the UE 305 can communicate with the gNB or ng-eNB serving that particular cell via the NR or LTE radio interface, respectively. While FIG. 3 shows the gNB and ng-eNB separately, it is also possible for a single NG-RAN node to provide both types of functionality.

[0071] Figure 6 shows an example configuration of the NR user plane (UP) and control plane (CP) protocol stack between the UE, gNB, and AMF, as shown in Figures 4 and 5. The physical (PHY), medium access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP) layers between the UE and gNB are common to the UP and CP. The PDCP layer provides encryption / decryption, integrity protection, sequence numbering, reordering, and duplicate detection for both the CP and UP. Additionally, PDCP provides header compression and retransmission of UP data.

[0072] On the UP side, Internet Protocol (IP) packets arrive at the PDCP layer as Service Data Units (SDUs), and PDCP creates Protocol Data Units (PDUs) and delivers them to the RLC. As each IP packet arrives, PDCP starts a discard timer. When this timer expires, PDCP discards the associated SDU and the corresponding PDU. If the PDU is delivered to the RLC, PDCP also instructs the RLC to discard it.

[0073] The RLC layer transfers PDCP PDUs to MAC via logical channels (LCHs). RLC performs error detection / correction, concatenation, segmentation / reassembly, sequence numbering, and reordering of data transferred to and from upper layers. When RLC receives a discard instruction related to a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been transmitted to the lower layer.

[0074] The MAC layer provides mapping between LCH and PHY transport channels, LCH prioritization, multiplexing to / demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, dynamic scheduling (gNB side), etc. The PHY layer provides transport channel services to the MAC layer and handles transmission over the NR air interface, including modulation, coding, antenna mapping, and beamforming.

[0075] On the UP side, the Service Data Adaptation Protocol (SDAP) layer handles Quality of Service (QoS), including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS Flow Identifiers (QFIs) in UL and DL packets. On the CP side, the Non-Access Stratum (NAS) layer sits between the UE and the AMF and handles UE / gNB authentication, mobility management, and security control.

[0076] The RRC layer is located below the UE's NAS but terminates in the gNB instead of the AMF. RRC controls communication between the UE and gNB over the air interface and UE mobility between cells within the NG-RAN. RRC also broadcasts system information (SI) and establishes, configures, maintains, and releases DRBs and signaling radio bearers (SRBs) used by the UE. Furthermore, RRC controls the addition, modification, and release of the UE's carrier aggregation (CA) and dual connectivity (DC) configurations. RRC also performs various security functions, such as key management.

[0077] After powering up, a UE enters the RRC_IDLE state until an RRC connection with the network is established, at which point it transitions to the RRC_CONNECTED state (i.e., a state where data transfer is possible). Once the network connection is released, the UE returns to RRC_IDLE. In the RRC_IDLE state, the UE's radio is active with a discontinuous reception (DRX) schedule configured by higher layers. During the DRX active period (also called the "DRX on period"), a UE in RRC_IDLE receives SI broadcasts in the cell where the UE is camped, performs measurements on neighboring cells to support cell reselection, and monitors the PDCCH paging channel for pages from the 5GC via the gNB. An NR UE in the RRC_IDLE state is not known to the gNB serving the cell where the UE is camped. However, NR RRC includes the RRC_INACTIVE state, where the UE is known by the serving gNB (e.g., via the UE context). RRC_INACTIVE has some characteristics similar to the "suspended" state used in LTE.

[0078] As mentioned above, QoE measurements are specified for UEs operating in LTE networks and older generation UMTS networks. In both networks, measurements follow the same high-level principles. The goal is to measure the end user's experience when using specific applications on the network. For example, QoE measurements for streaming services and MTSI (Mobile Telephony Services for IMS) are supported in LTE.

[0079] QoE measurements may be initiated from the OAM node towards the RAN generally for a group of UEs (e.g. all UEs that meet one or more criteria) or from the CN towards the RAN for a specific UE. The measurement configuration contains the measurement details, encapsulated in a container that is transparent to the RAN.

[0080] The "TRACE START" S1AP message is used by the LTE EPC to initiate QoE measurements by a specific UE. This message conveys details about the measurement configuration that the application should collect in the "Container for Application Layer Measurement Configuration" IE, which is transparent to the RAN. The message also contains the details necessary to reach the TCE to which the measurements should be sent.

[0081] Figures 7A-7D show various procedures between the UMTS RAN (UTRAN) and the UE for QoE measurements in legacy UMTS networks. These are similar to those specified for LTE (E-UTRAN). As shown in Figure 7A, the UTRAN can send a UECapabilityEnquiry message to request the UE to report its application layer measurement capabilities. As shown in Figure 7B, the UE can provide its application layer measurement capabilities to the UTRAN via a UECapabilityInformation message, in particular a "Measurement Capability" IE that contains information related to the UE's ability to perform QoE measurement collection for streaming services and / or MTSI services. Table 1 below shows an example of the content of this IE:

[0082] [Table 1]

[0083] The UTRAN can respond with a UE Capability Information Confirm message. Figure 7C shows that the UTRAN can send a Measurement Control message containing an "Application Layer Measurement Configuration" IE to configure QoE measurements for the UE. Table 2 below shows an example of the content of this IE:

[0084] [Table 2]

[0085] Figure 7D shows that the UE can send QoE measurement results to the TCE via the UTRAN using a measurement report message containing the "Application Layer Measurement Report" IE. Table 3 below shows an example of the content of this IE:

[0086] [Table 3]

[0087] As mentioned above, Figures 1 and 2 show the procedure between the E-UTRAN and the UE for configuring QoE measurements in an LTE network. Figure 1 shows an example of a UE capability transfer procedure used to transfer the UE's radio access capability information from the UE to the E-UTRAN. First, the E-UTRAN can send a UECapabilityEnquiry message, similar to the arrangement shown in Figure 7A. The UE can respond with a UECapabilityInformation message containing the "UE-EUTRA-Capability" IE.

[0088] This IE may further include a UE-EUTRA-Capability-v1530IE, which can be used to indicate whether the UE supports QoE measurement collection for streaming services and / or MTSI services. In particular, the UE-EUTRA-Capability-v1530IE may include a measParameters-v1530IE containing information about the UE's measurement support. In some cases, the UE-EUTRA-CapabilityIE may also include a "UE-EUTRA-Capability-v16xy-IE" which may include a qoe-Extensions-r16 field. Figure 8A shows an example of the ASN.1 data structure of these various IEs, with the various fields defined in Table 4 below.

[0089] [Table 4]

[0090] FIG. 8B is a diagram showing an example of the ASN.1 data structure of the qoe-Reference parameter described in Table 4 above.

[0091] 9A-9C illustrate various aspects of QoE measurement collection for a UE in an LTE network. In particular, FIG. 9A is an example signaling flow diagram of a QoE measurement collection process for LTE. To initiate QoE measurements, a serving eNB sends an RRCConnectionReconfiguration message to a UE in RRC_CONNECTED state, including a QoE configuration file, e.g., a measConfigAppLayerIE within an OtherConfigIE. As described above, the QoE configuration file is an application layer measurement configuration received by the eNB (e.g., from the EPC), encapsulated in a transparent container, and forwarded to the UE in an RRC message. The UE responds with an RRCConnectionReconfigurationComplete message. The UE then performs the configured QoE measurements and sends a MeasReportAppLayer RRC message including a QoE measurement result file to the eNB. Although not shown, the eNB can transparently forward this result file (e.g., to the EPC).

[0092] Figure 9B shows an example of the ASN.1 data structure of the measConfigAppLayerIE. This setup includes a transparent container, measConfigAppLayerContainer, that specifies the QoE measurement configuration for the target application. In the serviceType field, a value of "qoe" indicates quality of experience measurement collection for streaming services, and a value of "qoemtsi" indicates enhanced quality of experience measurement collection for MTSI. This field also includes various reserved values.

[0093] Figure 9C shows an example of an ASN.1 data structure for measReportAppLayerIE, which allows the UE to send QoE measurement results for an application (or service) to E-UTRAN (e.g., via SRB4). The service for which the report is being sent is indicated in serviceTypeIE.

[0094] As specified in 3GPP TS 28.405, an LTE RAN node (i.e., eNB) is allowed to temporarily suspend and resume QoE measurement reporting if an overload condition is observed. This behavior can be summarized as follows: In the event of a RAN overload, the eNB can temporarily suspend UE reporting by sending an RRCConnectionReconfiguration message to the associated UE with the measConfigAppLayerIE (in otherConfig) set to temporarily suspend application layer measurement reporting. The application can then suspend reporting and stop recording further information. Once the RAN overload condition has ended, the eNB can resume UE reporting by sending an RRCConnectionReconfiguration message to the associated UE with the measConfigAppLayerIE (in otherConfig) set to resume application layer measurement reporting. The application resumes reporting and recording if it was suspended.

[0095] Generally, the RAN (e.g., E-UTRAN or NG-RAN) is unaware of the UE's ongoing streaming session, and is also unaware when QoE measurements are being performed by the UE. Nevertheless, it is important for the client or management function that analyzes the measurements that the entire streaming session is measured. Therefore, it is beneficial to maintain QoE measurements for the entire session, even when the UE is in handover. However, it is an implementation decision when the RAN stops QoE measurements. This could happen, for example, if the UE moves out of the measurement area, e.g., due to a handover.

[0096] In addition to QoE measurements, the UE can be configured to perform and report measurements supporting Minimized Drive Testing (MDT), which aims to reduce and / or minimize the requirement for manual testing of actual network performance (i.e., by driving around the network's geographical coverage). MDT functionality was first studied in LTE Release 9 (e.g., 3GPP TR 36.805) and first standardized in Release 10. MDT can address a variety of network performance improvements, including coverage optimization, capacity optimization, mobility optimization, quality of service (QoS) verification, and parameterization of common channels (e.g., PDSCH).

[0097] The UE can be configured to perform logged and / or immediate MDT measurements. A UE in the RRC_IDLE state can be configured to perform periodic MDT measurement logging (e.g., via a LoggedMeasurementConfiguration RRC message from the network). The received MDT configuration can include a logging interval and a logging duration. Upon receiving the configuration, the UE starts a timer (T330) set to the logging duration (e.g., 10 to 120 minutes) and performs MDT logging periodically every logging interval (1.28 to 61.44 seconds) within the logging duration while the UE is in the RRC_IDLE state. In particular, the UE collects DL reference signal received strength and quality (i.e., RSRP, RSRQ) based on existing measurements required for cell reselection purposes. The UE reports the collected / logged information to the network when the UE returns to the RRC_CONNECTED state. Figure 4 shows an example of a logged MDT procedure performed by a UE.

[0098] In contrast, the UE can be configured to perform and report instantaneous MDT measurements while in the RRC_CONNECTED state. Similar to logged MDT, instantaneous MDT measurements are based on existing UE and / or network measurements performed while the UE is in the RRC_CONNECTED state and can include any of the following measurement quantities: · M1: Measurement of RSRP and RSRQ by the UE. ·M2: Power headroom measurement by UE. ·M3: Received interference power measurement by eNB. M4: Measurement of data volume by eNB for each UE and QCI (QoS Class Indicator) separately for DL ​​and UL. · M5: Scheduled IP layer throughput for MDT measurements by eNB per RAB per UE, per UE in DL, per UE in UL, for DL ​​and UL separately. · M6: Packet delay measurements per UE per QCI for DL ​​and UL separately (referring to PDCP delay in UL by the UE and packet delay in DL per QCI by the eNB). M7: eNB measures packet loss rate for each UE and QCI separately for DL ​​and UL. · M8: Received signal strength (RSSI) measurement by the UE. · M9: Round Trip Time (RTT) measurement by UE.

[0099] For example, reporting of M1 measurements can be event-triggered according to existing RRM configurations for either events A1-A6 or B1-B2. Furthermore, M1 reporting can be periodic, A2-event-triggered, or A2-event-triggered periodic according to MDT-specific measurement configurations. As another example, reporting of M2 measurements can be based on receiving a power headroom report (PHR), and reporting of M3-M9 can be triggered by the expiration of a measurement collection period.

[0100] As mentioned above, existing solutions for QoE measurement in LTE networks are designed to collect broad measurement sets for different services, which can result in a large amount of measurement data to report to requesting entities such as CNs and OAMs. 3GPP Release 17 agrees to provide visibility into QoE reports so that RAN nodes can adapt various aspects of their performance based on UE QoE measurements. This is particularly beneficial for URLLC services, as QoE reporting is fast and frequent, allowing RAN nodes to quickly adapt their performance to meet the requirements of URLLC services.

[0101] However, as mentioned above, if a first RAN configures the UE for QoE measurements and then reconfigures the UE's connection, the second RAN may unknowingly tamper with the ongoing measurements.Detailed below is a solution to enable coordinated processing between RAN nodes of QoE measurements configured for a UE and related radio-related measurements (e.g., MDT measurements), which are relevant for the following connectivity procedures related to this UE: dual connectivity, mobility, RRC resume, RRC re-establishment.

[0102] These solutions may be explained by first detailing techniques related to a first RAN node, i.e., the node that configures a UE with QoE measurements in some of the scenarios briefly described above. According to various scenarios, this first RAN node becomes associated with a second RAN node through an operation or signaling procedure involving both the first and second RAN nodes, such as dual connectivity, mobility, RRC resume, RRC re-establishment, or switching the transfer of data for a service from a path via the first RAN node to a path via the second RAN node (non-limiting examples). The first RAN node sends an RRC message to configure the wireless terminal for QoE measurements.

[0103] FIG. 10 is a process flow diagram illustrating an exemplary method in accordance with the techniques as detailed immediately below and generally described herein for a first RAN node.

[0104] In a first approach according to various of the presently disclosed technologies, a first RAN node transmits to a second RAN node measurement-related status information relating to one (or a list of) QoE measurements for which the first RAN node has configured a wireless terminal. This is shown in block 1010 of Figure 10. This QoE measurement status information may consist of some or all of the following: - Information about configured QoE measurements A list of UE identifiers for UEs or groups of UEs that are configured / are configured for QoE measurements One or a list of QoE measurement(s) or QoE measurement configuration(s) configured for a wireless terminal or group of wireless terminals A reference or list of references, such as one or a list of QoE Reference ID(s) related to the configured QoE measurements Indication of the type of QoE measurement configured, such as management-based QoE or signaling-based QoE (e.g., as part of a dual connectivity scenario) An indication or list of indications indicating the service type or service subtype to which the QoE measurement relates An indication of whether a session of an application belonging to the service type or service subtype for which QoE measurements are configured is in progress or a list of such indications An indication that a session has started for an application belonging to the service type or service subtype for which QoE measurements are configured, or a list of such indications An indication or a list of such indications that a session of an application belonging to a service type or service subtype for which QoE measurements are configured has terminated. An indication per service type and subtype, or a list of indications per service type or service subtype, showing whether each QoE measurement is configured (i.e., the measurement is configured but not yet started), activated (i.e., the application session has started and the measurement is currently in progress), suspended or deactivated An indication that slice-wise QoE measurement is enabled and a list of the corresponding S-NSSAIs Indication of RAT type for which QoE measurements are available An indication or list of indications regarding the MCE associated with the configured QoE measurement an indication that the second RAN node considers the configured QoE measurements to be valid for a certain period of time or until a certain time, or an indication of the time remaining in the QoE measurement collection process, or the overall time from the start of QoE measurement collection to the end of QoE measurement collection; Indication of the area scope or list of area scopes for which the configured QoE measurement configuration is valid A reference, or list of references, to ongoing radio-related measurements (e.g., MDT measurements) that are coupled to the ongoing QoE measurements. - Information about QoE measurement reporting configuration The size of the QoE measurement report signaled to the TCE -Period for notifying TCE of QoE measurement reports An indication, signaled together with the QoE report, of whether the QoE report has already been signaled to the TCE. Information about radio-related measurements (e.g., MDT measurements) coupled to the configured QoE measurement: Configuration of radio-related measurements in conjunction with ongoing QoE measurements A reference or list of references to ongoing radio-related measurements that are combined with the ongoing QoE measurements A reference or list of references for QoE measurements combined with radio-related measurements If a group of UEs are simultaneously undergoing one of the above-mentioned signaling procedures of interest (dual connectivity, mobility, RRC resume, RRC re-establishment, etc.), the operations and corresponding measurement state transfer signaling described herein can carry state related to multiple UEs (e.g., a list of measurements configured for all UEs currently undergoing handover). Note that, for example, since signaling procedures for mobility, RRC resume, and RRC re-establishment are typically performed for one UE at a time, the above-mentioned state information transfer for a group of UEs may be carried in a newly defined procedure.

[0105] In a second approach according to various presently disclosed embodiments, a first RAN node sends to a second RAN node a request for QoE measurements related to one (or a list of) QoE measurement configurations that the first RAN node previously sent to a wireless terminal for QoE measurements, or a request for radio-related measurements (e.g., MDT) related to said QoE measurements. An example is shown in block 1020 of Figure 10. These requests may be configured as follows: -Requests regarding configured QoE measurements, e.g.: A request to suspend one or a list of activated QoE measurements A request to resume one or a list of interrupted QoE measurements A request to unbind or suspend one or a list of activated QoE measurements In a first example relating to inter-RAT or inter-system mobility, the second RAN node belongs to a RAT or system that does not support one or more service types or service subtypes relevant to the ongoing QoE measurements, meaning that measurements relating to these service types and / or subtypes are therefore terminated or suspended. Another example is when a procedure (e.g. related to dual connectivity operation) is about to be triggered and the first RAN node that configured the UE for QoE measurements receives an indication (e.g. from OAM) that it must stop or suspend the full set or part of the ongoing QoE measurements. Reconfiguration of QoE measurement configurations, e.g. requests for replacement, or a list of such reconfigurations / replacements A request to transmit (or buffer and subsequently transmit to) the first RAN node a QoE report received by the second RAN node, said request optionally including additional conditions related to starting and stopping said reporting, for example: (signaling) radio bearer reconfiguration in the UE resulting in a switch of the RAN node receiving the QoE report, an overload indication sent from the first RAN node to the second RAN node, duration, until session termination, until the next mobility event is triggered, until further UE reconfiguration, service type or service subtype, slice or list of slices -Requests regarding radio measurements (e.g. MDT measurements) combined with configured QoE measurements, for example: A request to configure the wireless terminal with the same configuration used by the first RAN node to configure the wireless terminal for wireless measurements. A subset of the configuration used by the first RAN node may be requested by the first RAN node (or accepted by the second RAN node). This may be desired (or necessary) if, for example, (1) the QoE measurement configuration is modified such that some previously configured radio measurements are no longer needed, or (2) the second RAN node supports only some of the radio measurement configurations that the first RAN node configured for the radio terminal. Requests to trigger or clear a previously configured measurement, suspend an ongoing measurement, abort a QoE configuration, or resume radio-related measurements (e.g., MDT measurements). In an alternative solution, the first RAN node may first send a request message, and the second RAN node may respond with an acknowledgment or a failure, for example, indicating that the second RAN node can fulfill the request, or can fulfill part of the request. This response is shown in block 1030 of Figure 10. The first RAN node may then send a second, modified, request message based on the response from the second RAN node, as shown in block 1040 of Figure 10. If the operations according to the second embodiment need to be performed for a group of UEs, the described requests for multiple UEs may be carried in the same message (e.g. a list of measurements configured for all UEs currently in handover). Note that, since signaling procedures for e.g. mobility, RRC resume, RRC re-establishment, etc. are usually performed for one UE at a time, the above mentioned requests for a group of UEs may be carried in a newly defined procedure. In a sub-embodiment, the request message includes a UE identifier for a list of one or more UEs to which the QoE measurement related request is to be sent. The UE identifier can be any variant of the XnAP ID of the NG-RAN node UE. Some non-limiting examples are: the XnAP ID of the M-NG-RAN node UE or the XnAP ID of the S-NG-RAN node UE. In other subembodiments, the requests for multiple UEs may be of the same type for all UEs (in which case a single request type indication is required for the entire list of UEs) or may be of different types for different UEs (including where in a list of various request types for a group of multiple UEs there may still be UEs for which the same request type is indicated). In all of the above, multiple types of requests relating to the same UE or the same QoE measurement configuration may be conveyed in the same message (i.e. multiple requests per UE or QoE measurement configuration may be included in the same message from the first RAN node to the second RAN node).

[0106] Other aspects of the presently disclosed techniques may be described with respect to the second RAN node discussed in the various scenarios above, i.e., a node that receives specific information from the first RAN node regarding previous QoE measurement configurations for the UE. This second RAN node is associated with the first RAN node by an operation or signaling procedure involving both the first and second RAN nodes, such as dual connectivity, mobility, resume, re-establishment, etc. Figure 11 is a process flow diagram illustrating an exemplary method in accordance with these techniques for the second RAN node.

[0107] In some embodiments, the second RAN node receives from the first RAN node status information regarding QoE measurements related to one (or a list of) QoE measurement configurations for which the first RAN node has configured the wireless terminal for QoE measurements. This is indicated by block 1110 in Figure 11. This QoE measurement status information may comprise the information detailed in the embodiments for the first RAN node above.

[0108] In some of these and other embodiments, the second RAN node receives from the first RAN node requests for QoE measurements related to one (or more) (list of) QoE measurement configurations for which the first RAN node has sent an RRC message with QoE configurations to the UE for QoE measurements. An example is shown in block 1120 of Figure 11. These requests may comprise any of the requests detailed in the embodiments for the first RAN node above.

[0109] In response to a request of one of the types indicated above from the first RAN node, the second RAN node may transmit a status indication of the execution of the request, for example, such status indication may indicate one of, for example, “success”, “rejected”, “pending”, “partial success-partial rejection”, or “partial pending-partial rejection” (other execution status indications are not excluded).

[0110] In the above, if multiple UEs simultaneously undergo a procedure (status information transmission or request transmission) that triggers the above action, the corresponding network signaling may convey status indications and / or requests relating to one or more of these UEs in the same message.

[0111] When the second RAN node receives a message from the first RAN node containing a request (one of the request type(s) described above), the second RAN node may respond with an indication of the execution state of the first RAN node's request. An example is shown in block 1130 of FIG. 11. The indication may be per UE or per QoE measurement configuration, and each indication may be, for example, one of "success", "reject", "pending", "partial success-partial reject", or "partial pending-partial reject" (wherein other execution state indications are not excluded).

[0112] In some embodiments, upon receiving from the first RAN node a QoE measurement configuration associated with the UE or an indication of a QoE measurement configuration associated with the UE (where the UE is or will be served by a second RAN node after ongoing or preparing mobility or dual / multi-connectivity operation is terminated), or at any later time while the UE is served by the second RAN node and the QoE measurement configuration is still present and valid, the second RAN node may send an MDT or RRM measurement configuration to the first RAN node to be forwarded to the UE, which MDT or RRM measurement configuration may optionally be linked to the QoE measurement configuration (e.g., to enable synchronization and / or coordination of QoE measurements with MDT and / or RRM measurements). An example of this is shown in block 1140 of FIG. 11.

[0113] In other embodiments, upon receiving from the first RAN node a QoE measurement configuration associated with a UE, or an indication of a QoE measurement configuration associated with a UE (where the UE is served by the second RAN node, or will be served by the second RAN node after an ongoing or preparing mobility or dual / multi-connectivity operation has ended), or at any later time while the UE is served by the second RAN node and the QoE measurement configuration is still present and valid, the second RAN node may send a request to the first RAN node to configure the UE with MDT or RRM measurements linked to the QoE measurement configuration (e.g., to enable synchronization and / or coordination of QoE measurements with MDT and / or RRM measurements).

[0114] In yet another embodiment, upon receiving from the first RAN node a QoE measurement configuration associated with the UE or an indication of a QoE measurement configuration associated with the UE (wherein the UE is served by the second RAN node or will be served by the second RAN node after an ongoing or preparing mobility or dual / multi-connectivity operation has ended), or at any later time while the UE is served by the second RAN node and the QoE measurement configuration is still present and valid, the second RAN node transmits an MDT or RRM measurement configuration to the UE, which may optionally be linked to the QoE measurement configuration (e.g., to enable synchronization and / or coordination of QoE measurements with MDT and / or RRM measurements).

[0115] In one embodiment, when the second RAN receives a set of information about the QoE measurement status from the first RAN, the second RAN can use them to manage any new QoE measurement configurations that may have been received: If the second RAN receives the new signaling-based configuration and the second RAN operates on a different RAT than the first RAN, the second RAN configures the UE with the new signaling-based configuration, either directly or via a first RAN node. If the second RAN receives a new signaling-based configuration and the second RAN is serving the UE with the same RAT as the first RAN, the second RAN compares the newly received QoE measurement configuration with the information received from the first RAN node. If the new configuration is included in the current ongoing configuration, the second RAN may decide not to configure the UE with that configuration. If the new configuration includes part of the current configuration in the first RAN, the second RAN may decide to configure the UE with a configuration that merges the configurations in the first and second RAN nodes. Alternatively, the second RAN may decide to configure the UE with the newly received configuration and overwrite the configuration in place. If the second RAN receives the new signaling-based configuration and the second RAN is serving the UE over the same RAT as the first RAT, the second RAT may decide to inform the first RAN of the new signaling-based configuration so that the first RAN can either accept the new configuration and signal to the UE, merge the new configuration with the old configuration and signal to the UE, or reject the new configuration and keep the UE on the existing configuration (if configured via the first RAN). The above process may be repeated for management-based QoE configuration In another embodiment, if the second RAN node receives an indication of whether a QoE report has been signaled to the TCE together with a QoE measurement configuration including a report size and / or a frequency of reporting to the TCE, the second RAN node: Check whether the QoE report received from the first RAN node has been signaled to the TCE, and if not, Continue adding new QoE measurements to the QoE report until the report size set as part of the QoE measurement configuration is reached, and / or Continue adding new QoE measurement results to the QoE report until the QoE reporting period (derived from how often the second RAN node should report QoE reports to the TCE) expires, after which the RAN notifies the TCE of the report. If both the QoE report size and the reporting frequency of the QoE report are configured as part of the QoE measurement configuration, the second RAN node should signal a QoE report to the TCE when the first of these two conditions (report size or expiry of the reporting period) is met. As a further option, the RAN node may signal a QoE report to the TCE when the UE leaves its current serving cell(s), and at least thereby also leaves the area scope configured for the QoE configuration.

[0116] The techniques described herein can also be described with respect to a UE in the various scenarios described above: To resolve the situation where the UE's RRC receives two QoE configurations from two different legs, the UE's RRC can take several actions without network involvement (i.e., without QoE configuration state signaling between the first and second RAN nodes).

[0117] 12 illustrates an example approach. The UE receives a QoE measurement configuration for one or more service types from a RAN node, as shown in block 1210. Upon receiving this QoE measurement configuration for a service type or application, the UE can check whether the RRC and higher layers are already configured with an existing QoE configuration for the same service type or application, as shown in block 1220. If a QoE configuration for the same service type exists, as shown in block 1230, the UE's RRC can take one of the following actions: Discard the new configuration, or -Remove the old configuration and configure itself and the upper layer with the new configuration Suspend the new configuration, or Suspend the old configuration and start the new one If a new configuration is received and the old configuration is already suspended, either keep the new configuration active and release the old configuration, or keep the old configuration suspended. If a service / application type or service subtype is specified in the new QoE configuration, configure itself and its upper layers for that service or application type or subtype with the specified services, and maintain the old configuration for the remaining applications. In a dual connectivity scenario, if one QoE configuration is received from the master node and the other from the secondary node, release the QoE configuration received from the secondary node and keep the QoE configuration received from the master node. In a dual connectivity scenario, if one QoE configuration is received from the master node and the other from the secondary node, the QoE configuration received from the secondary node is suspended and the QoE configuration received from the master node is kept active. If an ongoing application session (or, if multiple sessions are ongoing, all of them) of the service type and / or service subtype covered by the QoE configuration is using a radio bearer towards the RAN node that received the old configuration, the old configuration shall be maintained and the new configuration shall be released or suspended. If an ongoing application session (or, if multiple sessions are ongoing, all of them) of the service type and / or service subtype covered by the QoE configuration is currently using a radio bearer towards the RAN node that received the new configuration, the new configuration shall be maintained and the old configuration shall be released or suspended.

[0118] Next, we will describe implementation examples of the above techniques in accordance with the NG-RAN specifications. These examples are provided in the context of dual connectivity operation, mobility, resume, and re-establishment.

[0119] Non-limiting examples of X2AP procedures and associated messages that can be impacted for dual connectivity: Preparation for adding SgNB, SGNB ADDITION REQUEST · SgNB release initiated by SgNB, SGNB RELEASE REQUIRED MeNB initiates SgNB release, SGNB RELEASE REQUEST ·SgNB cell change, SGB CHANGE REQUIRED Preparation for adding SeNB, SENB ADDITION REQUEST ·SeNB release initiated by SeNB, SENB RELEASE REQUIRED MeNB initiated SeNB release, SENB RELEASE REQUEST Trace start

[0120] Non-limiting examples of XnAP procedures and associated messages that can be impacted for dual connectivity: ·Preparing to add an S-NG-RAN node, S-NODE ADDITION REQUEST. S-NG-RAN node change initiated by S-NG-RAN node, S-NODE CHANGE REQUIRED · S-NODE RELEASE REQUEST initiated by M-NG-RAN node to release S-NG-RAN node S-NG-RAN node initiated S-NG-RAN node release, S-NODE RELEASE REQUIRED Trace start

[0121] Non-limiting examples of X2AP procedures and associated messages that can impact mobility: Handover preparation, HANDOVER REQUEST Handover Cancellation Handover successful, HANDOVER SUCCESS Conditional Handover Cancellation Handover Report

[0122] Non-limiting examples of XnAP procedures and associated messages that can impact mobility: Handover preparation, HANDOVER REQUEST Handover Cancellation Handover successful, HANDOVER SUCCESS Access and Mobility Indication

[0123] Non-limiting examples of X2AP procedures and associated messages that can be affected for resume and re-establishment: Retrieve UE context, RETRIEVE UE CONTEXT RESPONSE

[0124] Non-limiting examples of XnAP procedures and associated messages that can be effected for resume and re-establishment: Retrieve UE context, RETRIEVE UE CONTEXT RESPONSE

[0125] Non-limiting examples of NGAP procedures and associated messages that can affect mobility Handover preparation, HANDOVER REQUIRED, HANDOVER COMMAND Handover resource allocation, HANDOVER REQUEST, HANDOVER REQUEST ACKNOWLEDGE Handover successful, HANDOVER SUCCESS Handover Cancellation

[0126] As a non-limiting example of implementation, the IE "UE Application Layer Measurement Config", which contains QMC related configuration parameters, is extended to include the option according to the invention. The "UE Application Layer Measurement Config" is added to various XnAP, X2AP, NGAP, S1AP messages. An example of an S-NODE ADDITION REQUEST applicable to the NR-DC scenario is shown below:

[0127] -----Start of proposed 3GPP specification---- 9.1.2.1 S-NODE ADDITION REQUEST This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the provisioning of resources for dual connectivity operation for a particular UE. Direction: M-NG-RAN node → S-NG-RAN node TIFF0007823055000005.tif228153TIFF0007823055000006.tif244153TIFF0007823055000007.tif13153TIFF0007823055000008.tif201539.2.3.X UE Application Layer Measurement Configuration This IE defines the configuration information for the QoE Measurement Collection (QMC) function. TIFF0007823055000009.tif172153TIFF0007823055000010.tif159153TIFF0007823055000011.tif26153-----END OF PROPOSED 3GPP SPECIFICATION-----

[0128] While various embodiments have been described above in terms of methods, techniques, and / or procedures, those skilled in the art will readily appreciate that such methods, techniques, and / or procedures may be embodied in a combination of hardware and software in various systems, communication devices, computing devices, control devices, apparatus, non-transitory computer-readable media, computer program products, and the like.

[0129] 13 illustrates a block diagram of an exemplary wireless device or user equipment (UE) 1300 (hereinafter referred to as “UE 1300”) in accordance with various embodiments of the present disclosure, including those described above with reference to other figures. For example, UE 1300 may be configured to perform operations corresponding to one or more of the example methods described herein by execution of instructions stored on a computer-readable medium.

[0130] The UE 1300 may include a processor 1310 (also referred to as “processing circuitry”) that may be operatively connected to a program memory 1320 and / or a data memory 1330 via a bus 1370, which may comprise a parallel address and data bus, a serial port, or other methods and / or structures known to those skilled in the art. The program memory 1320 may store software code, programs, and / or instructions (collectively shown in FIG. 13 as computer program product 1321) that, when executed by the processor 1310, may configure and / or facilitate the UE 1300 to perform various operations, including operations corresponding to various example methods described herein. As part of, or in addition to, such operations, execution of such instructions may configure and / or facilitate UE 1300 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as commonly known as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, 1xRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or other current or future protocols that may be utilized in combination with wireless transceiver 1340, user interface 1350, and / or control interface 1360.

[0131] As another example, the processor 1310 may execute program code stored in the program memory 1320 corresponding to MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). As a further example, the processor 1310, in conjunction with the wireless transceiver 1340, may execute program code stored in the program memory 1320 that implements corresponding PHY layer protocols such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). As another example, the processor 1310, in conjunction with the wireless transceiver 1340, may execute program code stored in the program memory 1320 that implements Device-to-Device (D2D) communications with other compatible devices and / or UEs.

[0132] The program memory 1320 may also include software code executed by the processor 1310 to control the functionality of the UE 1300, including configuring and controlling various components such as the wireless transceiver 1340, the user interface 1350, and / or the control interface 1360. The program memory 1320 may also include one or more application programs and / or modules containing computer-executable instructions embodying any of the example methods described herein. Such software code may be specified or written using any known or future-developed programming language, such as, for example, Java, C++, C, ObjectiveC, HTML, XHTML, machine code, assembler, etc., so long as the desired functionality, e.g., as defined by the implemented method steps, is preserved. Additionally or alternatively, the program memory 1320 may constitute an external storage arrangement (not shown) remote from the UE 1300, from which instructions can be downloaded to the program memory 1320 located within or removably coupled to the UE 1300 to enable execution of such instructions.

[0133] The data memory 1330 may include memory areas for the processor 1310 to store variables used in protocol, configuration, control, and other functions of the UE 1300, including operations corresponding to or constituting any of the example methods described herein. Additionally, the program memory 1320 and / or the data memory 1330 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. Additionally, the data memory 1330 may comprise memory slots into which one or more forms of removable memory cards (e.g., SD cards, memory sticks, CompactFlash cards, etc.) can be inserted and removed.

[0134] Those skilled in the art will recognize that the processor 1310 may include multiple individual processors (e.g., including multi-core processors), each of which performs some of the functions described above. In such cases, the multiple individual processors may be commonly connected to the program memory 1320 and the data memory 1330, or may be individually connected to multiple individual program memories and / or data memories. More generally, those skilled in the art will recognize that the various protocols and other functions of the UE 1300 can be implemented in many different computer arrangements consisting of different combinations of hardware and software, such as, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and / or programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

[0135] The wireless transceiver 1340 may include radio frequency transmitter and / or receiver functionality that facilitates the UE 1300 communicating with other devices supporting similar wireless communication standards and / or protocols. In some demonstrative embodiments, the wireless transceiver 1340 includes one or more transmitters and one or more receivers that enable the UE 1300 to communicate in accordance with various protocols and / or methodologies proposed for standardization by 3GPP and / or other standards organizations (SSOs). For example, such functionality may operate in coordination with the processor 1310 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques, as described herein with respect to other figures.

[0136] In some exemplary embodiments, the wireless transceiver 1340 includes one or more transmitters and one or more receivers that can facilitate the UE 1300 communicating with various LTE, LTE-Advanced (LTE-A), and / or NR networks in accordance with standards promulgated by 3GPP. In some exemplary embodiments of the present disclosure, the wireless transceiver 1340 includes the circuitry, firmware, etc. necessary for the UE 1300 to communicate with various NR, NR-U, LTE, LTE-A, LTE-LAA, UMTS, and / or GSM / EDGE networks, also in accordance with 3GPP standards. In some embodiments, the wireless transceiver 1340 may include circuitry supporting device-to-device (D2D) communications between the UE 1300 and other compatible devices.

[0137] In some embodiments, the wireless transceiver 1340 includes the circuitry, firmware, etc. necessary for the UE 1300 to communicate with various CDMA2000 networks in accordance with the 3GPP2 standard. In some embodiments, the wireless transceiver 1340 is capable of communicating using wireless technologies operating in unlicensed frequency bands, such as IEEE 802.11 WiFi, which operates using frequencies in the 2.4, 5.6, and / or 60 GHz range. In some embodiments, the wireless transceiver 1340 may include a transceiver capable of wired communication, such as by using IEEE 802.3 Ethernet technology. Functionality particular to each of these embodiments may be coupled to and / or controlled by other circuitry within the UE 1300, such as the processor 1310 executing program code stored in the program memory 1320 in conjunction with and / or supported by the data memory 1330.

[0138] The user interface 1350 can take various forms or can be completely absent from the UE 1300 depending on the particular embodiment of the UE 1300. In some embodiments, the user interface 1350 can comprise a microphone, a loudspeaker, slidable buttons, depressible buttons, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface feature commonly found on a mobile phone. In other embodiments, the UE 1300 can comprise a tablet computing device including a larger touchscreen display. In such embodiments, one or more of the mechanical features of the user interface 1350 can be replaced by equivalent or functionally equivalent virtual user interface features (e.g., a virtual keypad, virtual buttons, etc.) implemented using a touchscreen display, as is well known to those skilled in the art. In other embodiments, the UE 1300 can be a digital computing device such as a laptop computer, desktop computer, workstation, or the like, that comprises an integrated, detachable, or detachable mechanical keyboard depending on the particular embodiment. Such a digital computing device can also comprise a touchscreen display. Many exemplary embodiments of the UE 1300 having a touchscreen display can receive user inputs known to those skilled in the art, such as inputs related to the exemplary methods described herein.

[0139] In some embodiments, the UE 1300 may include an orientation sensor, which may be used in various ways depending on the features and capabilities of the UE 1300. For example, the UE 1300 may use the output of the orientation sensor to determine when a user changes the physical orientation of the UE 1300's touchscreen display. The indicator signal from the orientation sensor is available to any application program running on the UE 1300, allowing the application program to automatically change the screen display orientation (e.g., from portrait to landscape) when the indicator signal indicates an approximately 90-degree change in the device's physical orientation. In this example aspect, the application program can maintain the screen display in a manner that is readable by the user, regardless of the device's physical orientation. Furthermore, the output of the orientation sensor may be used in combination with various exemplary embodiments of the present disclosure.

[0140] The control interface 1360 of the UE 1300 can take a variety of forms, depending on the particular example embodiment of the UE 1300 and the particular interface requirements of other devices with which the UE 1300 is intended to communicate and / or control. For example, the control interface 1360 may be an RS-232 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“Firewire”) interface, an I / O interface, an IEEE 802.11a interface, an IEEE 802.11b ... 2 C interface, PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, control interface 1360 may comprise an IEEE 802.3 Ethernet interface as described above. In some exemplary embodiments of the present disclosure, control interface 1360 may comprise an analog interface circuit including, for example, one or more digital-to-analog converters (DACs) and / or analog-to-digital converters (ADCs).

[0141] Those skilled in the art will recognize that the above list of features, interfaces, and radio frequency communication standards is merely exemplary and does not limit the scope of the present disclosure. In other words, the UE 1300 may be configured with more functionality than shown in FIG. 13 , including, for example, a video and / or still camera, a microphone, a media player and / or recorder, etc. Furthermore, the wireless transceiver 1340 may include circuitry necessary to communicate using additional radio frequency communication standards, including Bluetooth, GPS, and / or others. Furthermore, the processor 1310 may execute software code stored in the program memory 1320 to control such additional functionality. For example, the direction, speed, and / or position estimates output from the GPS receiver may be available to any application program executing on the UE 1300, including any program code corresponding to and / or embodying any exemplary embodiment (e.g., of the methods) described herein.

[0142] FIG. 14 is a block diagram of an exemplary network node 1400 according to various embodiments of the present disclosure, including those described above with reference to other figures. For example, the exemplary network node 1400 may be configured to perform operations corresponding to one or more of the example methods described herein through execution of instructions stored on a computer-readable medium. In some exemplary embodiments, the network node 1400 may constitute a base station, an eNB, a gNB, or one or more components thereof. For example, the network node 1400 may be configured as a central unit (CU) and one or more distributed units (DUs) in accordance with the gNB architecture for NR specified by 3GPP. More generally, the functionality of the network node 1400 may be distributed across various physical devices and / or functional units, modules, etc.

[0143] The network node 1400 may include a processor 1410 (also referred to as a "processing circuit") operably connected to a program memory 1420 and a data memory 1430 via a bus 1470, which may include a parallel address and data bus, a serial port, or other methods and / or structures known to those skilled in the art.

[0144] The program memory 1420 may store software code, programs, and / or instructions (collectively shown in FIG. 14 as computer program product 1421) that, when executed by the processor 1410, may configure and / or facilitate the network node 1400 to perform various operations, including operations corresponding to various example methods described herein. As part of such operations, and / or in addition, the program memory 1420 may also execute software code by the processor 1410 that may configure or facilitate the network node 1400 to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or NR, or any other higher layer (e.g., NAS) protocols utilized with the radio network interface 1440 and / or core network interface 1450. As an example, the core network interface 1450 may constitute an S1 or NG interface, and the radio network interface 1440 may constitute a Uu interface, as standardized by 3GPP. The program memory 1420 may also configure software code that is executed by the processor 1410 to control the functions of the network node 1400, including configuring and controlling various components such as the radio network interface 1440 and the core network interface 1450.

[0145] Data memory 1430 may provide a memory area for processor 1410 to store variables used in protocol, configuration, control, and other functions of network node 1400. Program memory 1420 and data memory 1430 may consist of non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., “cloud”) storage, or a combination thereof. Those skilled in the art will recognize that processor 1410 may include multiple individual processors (not shown), each of which performs some of the functionality described above. In that case, the multiple individual processors may be commonly connected to program memory 1420 and data memory 1430 or individually connected to multiple individual program memories and / or data memories. More generally, those skilled in the art will recognize that the various protocols and other functions of network node 1400 may be implemented in many different combinations of hardware and software, including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuits, programmable digital circuits, analog baseband circuits, radio frequency circuits, software, firmware, and middleware.

[0146] The radio network interface 1440 may be comprised of transmitters, receivers, signal processors, ASICs, antennas, beamforming units, and other circuitry that enables the network node 1400 to communicate with other devices, such as, in some embodiments, multiple compatible user equipment (UE). In some embodiments, the interface 1440 may also enable the network node 1400 to communicate with compatible satellites of a satellite communications network. In some exemplary embodiments, the radio network interface 1440 may comprise various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and / or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc., modifications thereof as described above herein, or other higher layer protocols utilized in combination with the radio network interface 1440. According to further exemplary embodiments of the present disclosure, the radio network interface 1440 may comprise a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques. In some embodiments, such PHY layer functionality may be provided cooperatively by the wireless network interface 1440 and the processor 1410 (including program code in the memory 1420).

[0147] The core network interface 1450, in some embodiments, may comprise transmitters, receivers, and other circuitry that enables the network node 1400 to communicate with other devices in a core network, such as a circuit-switched (CS) and / or packet-switched core (PS) network. In some embodiments, the core network interface 1450 may comprise an S1 interface standardized by 3GPP. In some embodiments, the core network interface 1450 may comprise an NG interface standardized by 3GPP. In some exemplary embodiments, the core network interface 1450 may comprise one or more interfaces to one or more AMFs, SMFs, SGWs, MMEs, SGSNs, GGSNs, and other physical devices that comprise functionality found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks known to those skilled in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the layers below the core network interface 1450 may comprise one or more of asynchronous transfer mode (ATM), internet protocol (IP)-over-Ethernet, SDH over optical fiber, T1 / E1 / PDH over copper, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art.

[0148] In some embodiments, network node 1400 may include hardware and / or software that configures and / or facilitates network node 1400 to communicate with other network nodes in a RAN (also referred to as a "radio network"), such as other eNBs, gNBs, ng-eNBs, en-gNBs, or IAB nodes. Such hardware and / or software may be part of radio network interface 1440 and / or core network interface 1450, or it may be a separate functional unit (not shown). For example, such hardware and / or software may configure and / or facilitate network node 1400 to communicate with other RAN nodes over an X2 or Xn interface, as standardized by 3GPP.

[0149] OA&M interface 1460 may be comprised of transmitters, receivers, and other circuitry that enables network node 1400 to communicate with external networks, computers, databases, etc., for purposes of operation, administration, and maintenance of network node 1400 or other network equipment operatively connected thereto. The layers below OA&M interface 1460 may comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethernet, SDH over optical fiber, T1 / E1 / PDH over copper wire, microwave radio, or other wired or wireless transmission technologies known to those skilled in the art. Furthermore, in some embodiments, one or more of wireless network interface 1440, core network interface 1450, and OA&M interface 1460 may be multiplexed together on a single physical interface, such as the examples given above.

[0150] 15 is a block diagram of an example communication network configured to provide over-the-top (OTT) data services between a host computer and a user equipment (UE) in accordance with various example embodiments of the present disclosure. The UE 1510 can communicate with a radio access network (RAN, also referred to as a "radio network") 1530 via an air interface 1520, which can be based on the protocols discussed above, including, for example, LTE, LTE-A, and 5G / NR. For example, the UE 1510 can be configured and / or arranged as shown in the other figures discussed above.

[0151] The RAN 1530 may include one or more terrestrial network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) capable of operating in licensed spectrum bands and one or more network nodes capable of operating in unlicensed spectrum (e.g., using LAA or NR-U technologies), such as the 2.4 GHz and / or 5 GHz bands. In such cases, the network nodes comprising the RAN 1530 may operate cooperatively using licensed and unlicensed spectrum. In some embodiments, the RAN 1530 may include or be capable of communicating with one or more satellites comprising a satellite access network.

[0152] The RAN 1530 can communicate with the core network 1540 according to the various protocols and interfaces described above. For example, one or more devices (e.g., base stations, eNBs, gNBs, etc.) comprising the RAN 1530 can communicate to the core network 1540 via the core network interface 1550 described above. In some demonstrative embodiments, the RAN 1530 and the core network 1540 may be configured and / or arranged as shown in other figures described above. For example, the eNBs comprising the E-UTRAN 1530 can communicate with the EPC core network 1540 via an S1 interface. As another example, the gNBs and ng-eNBs comprising the NG-RAN 1530 can communicate with the 5GC core network 1530 via an NG interface.

[0153] The core network 1540 can further communicate with an external packet data network, illustrated in FIG. 15 as the Internet 1550, according to various protocols and interfaces known to those skilled in the art. Many other devices and / or networks can also connect to and communicate via the Internet 1550, such as an exemplary host computer 1560. In some exemplary embodiments, the host computer 1560 can communicate with the UE 1510 using the Internet 1550, the core network 1540, and the RAN 1530 as intermediaries. The host computer 1560 can be a server (e.g., an application server) owned and / or under the control of the service provider. The host computer 1560 can be operated by the OTT service provider or by another entity on behalf of the service provider.

[0154] For example, the host computer 1560 may provide over-the-top (OTT) packet data services to the UE 1510 using facilities of the core network 1540 and the RAN 1530 and may be unaware of the routing of outgoing / incoming communications to / from the host computer 1560. Similarly, the host computer 1560 may be unaware of the routing of transmissions from the host computer to the UE, e.g., through the RAN 1530. A variety of OTT services may be provided using the exemplary configuration shown in FIG. 15, including, for example, streaming (one-way) audio and / or video from the host computer to the UE, interactive (two-way) audio and / or video between the host computer and the UE, interactive messaging or social communications, interactive virtual or augmented reality, etc.

[0155] The exemplary network shown in FIG. 15 may also include measurement procedures and / or sensors that monitor network performance metrics, including data rates, latency, and other factors improved by the exemplary embodiments disclosed herein. The exemplary network may also include functionality for reconfiguring links between endpoints (e.g., host computers and UEs) in response to fluctuations in the measurements. Such procedures and functionality are known and practiced. If the network hides or abstracts the air interface from the OTT service provider, measurements may be facilitated by proprietary signaling between the UE and the host computer.

[0156] The embodiments described herein provide novel techniques for configuring, implementing, and reporting lightweight QoE metrics by UEs. Such techniques can facilitate better analysis and optimization decisions in the RAN while avoiding unnecessary network traffic caused by traditional measurement reports containing large amounts of information, such as traditional QoE metrics. When used in NR UEs (e.g., UEs 1510) and gNBs (e.g., gNBs comprising the RAN 1530), the embodiments described herein can provide various improvements, benefits, and / or advantages that can improve QoE decisions and network optimization for OTT applications and / or services. As a result, this improves the performance of these services experienced by OTT service providers and end users, including more accurately delivering services with lower latency without excessive UE energy consumption or other degradation of the user experience.

[0157] The foregoing merely illustrates the principles of the present disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in light of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the present disclosure and therefore may be within the spirit and scope of the present disclosure. The various exemplary embodiments may be used in conjunction with and interchangeably with one another, as would be understood by those skilled in the art.

[0158] As described herein, devices and / or apparatus may be represented by semiconductor chips, chipsets, or (hardware) modules constituting such chips or chipsets. However, this does not exclude the possibility that the functionality of a device or apparatus may be implemented as a software module, such as a computer program or computer program product including executable software code portions for execution or running on a processor, instead of being implemented in hardware. Furthermore, the functionality of a device or apparatus may be implemented by any combination of hardware and software. A device or apparatus may also be considered an assembly of multiple devices and / or apparatus, whether functionally cooperating with each other or independent. Furthermore, devices or apparatus may be implemented distributed throughout a system, as long as the functionality of the devices or apparatus is maintained. These and similar principles are believed to be known to those skilled in the art.

[0159] Any suitable step, method, feature, function, or advantage disclosed herein can be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may be composed of a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware including digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a function corresponding to the respective functional unit in accordance with one or more embodiments of the present disclosure.

[0160] Furthermore, functionality described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functionality of the network nodes and wireless devices described herein is not limited to being performed by a single physical device, but may in fact be distributed across multiple physical devices.

[0161] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Terms used herein should be interpreted as having a meaning consistent with their meaning in the context of the present specification and related art, and will be further understood not to be interpreted in an idealized or overly formal sense unless expressly defined as such herein.

[0162] Furthermore, certain terms used in this disclosure, including the specification, drawings, and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, for example, data and information. These words and / or other words that can be synonyms for each other can be used synonymously herein, although it should be understood that there may be cases where such words are not intended to be used synonymously. Furthermore, to the extent that prior art knowledge has not been expressly incorporated by reference herein above, it is expressly incorporated herein in its entirety. All referenced publications are incorporated herein by reference in their entirety.

[0163] As used herein, unless expressly stated to the contrary, the phrases "at least one" and "one or more" followed by a connected list of enumerated items (e.g., "A and B," "A, B and C") are intended to mean "at least one item," with each item selected from the list of enumerated items. For example, "at least one of A and B" is intended to mean any of the following: A; B; A and B. Similarly, "one or more of A, B, C" is intended to mean any of the following: A; B; C; A and B; B and C; A and C; A, B and C.

[0164] As used herein, unless expressly stated to the contrary, the term "plurality" followed by a connected list of enumerated items (e.g., "A and B," "A, B and C") is intended to mean "a plurality of items, each item selected from the list of enumerated items." For example, "a plurality of A's and B's" is intended to mean any of the following: a plurality of A's, a plurality of B's, at least one A and at least one B.

[0165] Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following listed examples:

[0166] A1. A method for a user equipment (UE) for processing configuration of quality of experience (QoE) measurements in a radio access network (RAN), the method comprising: receiving a QoE measurement configuration (QMC) for one or more service types or applications from a RAN node; determining that the UE already has a QoE configuration for the same service type or application; If the above decision is made, Discarding the new configuration, Releasing the old configuration and configuring itself and its higher layers with the new configuration; Suspending the new configuration, Suspending the old configuration and activating the new one, If a new configuration is received and the old configuration is already in a suspended state, keeping the new configuration active and releasing the old configuration or keeping the old configuration in a suspended state; If a service / application type or service subtype is specified by a new QoE configuration, configure itself and its upper layers for that service or application type or subtype with the specified services, and maintain the old configuration for the remaining applications; In a dual connectivity scenario, when one QoE configuration is received from a master node and the other is received from a secondary node, releasing the QoE configuration received from the secondary node and maintaining the QoE configuration received from the master node; In a dual connectivity scenario, when one QoE configuration is received from a master node and the other is received from a secondary node, suspending the QoE configuration received from the secondary node and keeping the QoE configuration received from the master node active; maintaining the old configuration and releasing or suspending the new configuration if an ongoing application session (or, in case of multiple ongoing sessions, all ongoing application sessions) of the service type and / or service subtype covered by the QoE configuration currently uses a radio bearer towards the RAN node on which the old configuration was received; If an ongoing application session (or, in case of multiple ongoing sessions, all ongoing application sessions) of the service type and / or service subtype covered by the QoE configuration currently uses a radio bearer towards the RAN node on which the new configuration was received, maintaining the new configuration and releasing or suspending the old configuration; performing one or more of the actions of Contains method.

[0167] B1. A method for managing Quality of Experience (QoE) measurements by a User Equipment (UE) at a first node in a Radio Access Network (RAN), the method comprising: transmitting, to a second node within the RAN, measurement status information relating to one or more QoE measurements configured for the UE by the first node. method. B2. The second node is associated with the first node with respect to changing the configuration of the UE (e.g., for dual connectivity), mobility, RRC resume or RRC re-establishment, and switching the transfer of data for a service from a path to the UE via the first RAN node to a path to the UE via the second RAN node. The method of embodiment B1. B3. Configuring the UE for the one or more QoE measurements prior to said transmitting. The method of embodiment B1 or B2. B4. The status information is an identifier of a UE or a list of UE identifiers for a group of UEs configured for QoE measurements; one or a list of QoE measurements or QoE measurement configurations configured for a wireless terminal or a group of wireless terminals; a reference or list of references related to the configured QoE measurement, such as one or a list of QoE Reference IDs; An indication on the type of QoE measurement configured, such as management-based QoE or signaling-based QoE (e.g., as part of a dual connectivity scenario); an indication or list of indications indicating the service type or service subtype to which the QoE measurement relates; an indication of whether a session of an application belonging to the service type or service subtype for which QoE measurements are configured is in progress, or a list of such indications; an indication that a session of an application belonging to the service type or service subtype for which QoE measurements are configured has started, or a list of such indications; an indication that a session of an application belonging to a service type or service subtype for which QoE measurements are configured has been terminated, or a list of such indications; an indication of service subtypes per service type or a list of indications per service type or service subtype, indicating whether QoE measurements are configured (i.e. measurements are configured but not yet started), activated (i.e. application session has started and measurements are in progress), suspended or deactivated; An indication that per-slice QoE measurements are enabled and a list of corresponding S-NSSAIs; Indication of the RAT type for which QoE measurements are valid, an indication about the MCE related to the configured QoE measurement or a list of such indications; an indication that the second RAN node considers the configured QoE measurements to be valid for a certain period of time or until a predetermined time; an indication of the area scope or list of area scopes for which the configured QoE measurement configuration is valid; A reference or list of references to ongoing radio-related measurements that are combined with ongoing QoE measurements (e.g., MDT measurements). Contains one or more of the following: The method of any one of embodiments B1 to B3. B5. The status information is Configuring radio-related measurements coupled with ongoing QoE measurements; a reference or list of references to ongoing radio-related measurements that are coupled to the ongoing QoE measurements; A reference or list of references for QoE measurements combined with radio-related measurements Contains one or more of any A method according to any one of embodiments B1 to B4. B6. The status information is transmitted to the second node along with status information associated with one or more additional UEs. A method according to any one of embodiments B1 to B5. B7. The method further includes sending a request for the one or more QoE measurements to the second node. The method of any one of embodiments B1 to B6. B8. The request is: A request to suspend one or a list of activated QoE measurements, A request to resume one or a list of suspended QoE measurements, A request to deactivate or stop one or a list of activated QoE measurements, A request to reconfigure (e.g., replace) the measurement configuration, or a list of such reconfigurations / replacements; a request to transmit the QoE report received by the second RAN node to the first RAN node (or to the first RAN node after transmitting it to a buffer), the request optionally including additional conditions relating to the start and end of such reporting; a request to configure the radio terminal with the same configuration used by the first RAN node to configure the radio terminal for radio measurements; Requests to trigger or clear a previously configured measurement, stop an ongoing measurement, suspend a QoE configuration, or resume a radio-related measurement Contains one of the following: The method of embodiment B7. B9. The method includes receiving a message from the second node approving the request or indicating that the request is not or cannot be complied with. The method of embodiment B7 or B8. B10. The method further includes sending a second request to the second node, the second request being modified based on the message received from the second node. The method of embodiment B9. B11. The request relates to multiple UEs The method of any one of embodiments B7 to B10. B12. A method for managing quality of experience (QoE) measurements by a user equipment (UE) at a second node in a radio access network (RAN), the method comprising: receiving, from a first node in the RAN, measurement status information relating to one or more QoE measurements configured for the UE by the first node; method. B13. The second node is associated with the first node with respect to changing the configuration of the UE (e.g., for dual connectivity), mobility, RRC resume or RRC re-establishment, and switching the transfer of data for a service from a path to the UE via the first RAN node to a path to the UE via the second RAN node. The method of embodiment B12. B14. The method includes refraining from configuring or changing a configuration of QoE measurements by the UE in response to the status information. The method of embodiment B12 or B13. B15. The status information is an identifier of a UE or a list of UE identifiers for a group of UEs configured for QoE measurements; one or a list of QoE measurements or QoE measurement configurations configured for a wireless terminal or a group of wireless terminals; a reference or list of references related to the configured QoE measurement, such as one or a list of QoE Reference IDs; An indication on the type of QoE measurement configured, such as management-based QoE or signaling-based QoE (e.g., as part of a dual connectivity scenario); an indication or list of indications indicating the service type or service subtype to which the QoE measurement relates; an indication of whether a session of an application belonging to the service type or service subtype for which QoE measurements are configured is in progress, or a list of such indications; an indication that a session of an application belonging to the service type or service subtype for which QoE measurements are configured has started, or a list of such indications; an indication that a session of an application belonging to a service type or service subtype for which QoE measurements are configured has been terminated, or a list of such indications; an indication of service subtypes per service type or a list of indications per service type or service subtype, indicating whether QoE measurements are configured (i.e. measurements are configured but not yet started), activated (i.e. application session has started and measurements are in progress), suspended or deactivated; An indication that per-slice QoE measurements are enabled and a list of corresponding S-NSSAIs; Indication of the RAT type for which QoE measurements are valid, an indication about the MCE related to the configured QoE measurement or a list of such indications; an indication that the second RAN node considers the configured QoE measurements to be valid for a certain period of time or until a predetermined time; an indication of the area scope or list of area scopes for which the configured QoE measurement configuration is valid; A reference or list of references to ongoing radio-related measurements that are combined with ongoing QoE measurements (e.g., MDT measurements). Contains one or more of the following: The method of any one of embodiments B12 to B14. B16. The status information is Configuring radio-related measurements coupled with ongoing QoE measurements; a reference or list of references to ongoing radio-related measurements that are coupled to the ongoing QoE measurements; A reference or list of references for QoE measurements combined with radio-related measurements Contains one or more of any The method of any one of embodiments B12 to B15. B17. The status information is received from the first node along with status information associated with one or more additional UEs. The method of any one of embodiments B12 to B16. B18. The method further includes receiving a request for the one or more QoE measurements from the first node. The method of any one of embodiments B12 to B17. B19. The request is A request to suspend one or a list of activated QoE measurements, A request to resume one or a list of suspended QoE measurements, A request to deactivate or stop one or a list of activated QoE measurements, A request to reconfigure (e.g., replace) the measurement configuration, or a list of such reconfigurations / replacements, a request to transmit the QoE report received by the second RAN node to the first RAN node (or to the first RAN node after transmitting it to a buffer), the request optionally including additional conditions relating to the start and end of such reporting; a request to configure the radio terminal with the same configuration used by the first RAN node to configure the radio terminal for radio measurements; Requests to trigger or clear a previously configured measurement, stop an ongoing measurement, suspend a QoE configuration, or resume a radio-related measurement Contains one of the following: The method of embodiment B18. B20. The method further includes responding with an indication of the execution status of the request. The method of embodiment B18 or B19. B21. The method includes, in response to the request, sending a message to the first node approving the request or indicating that the request is not or cannot be complied with. The method of embodiment B18 or B19. B22. The method further includes receiving a second request from the first node, the second request being modified based on the message received from the second node. The method of embodiment B21. B23. The request relates to multiple UEs The method of any one of embodiments B18 to B22. B24. Further comprising: sending to the first node a request to configure the UE with one or more radio measurements to be linked to QoE measurements of the UE. The method of any one of embodiments B12 to B23.

[0168] C1. A user equipment (UE) configured to perform quality of experience (QoE) measurements in a radio access network (RAN), the UE comprising: a radio transceiver circuit configured to communicate with at least one RAN node; a processing circuit operably coupled to the wireless transceiver circuit, the processing circuit and the wireless transceiver circuit configured to perform operations corresponding to the method of embodiment A1; Equipped with UE. C2. A user equipment (UE) configured to perform quality of experience (QoE) measurements in a radio access network (RAN), the UE further configured to perform operations corresponding to the method described in embodiment A1. UE. C3. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to perform quality of experience (QoE) measurements in a radio access network (RAN), configure the UE to perform operations corresponding to the method described in embodiment A1. C4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to perform quality of experience (QoE) measurements in a radio access network (RAN), configure the UE to perform operations corresponding to the method described in embodiment A1.

[0169] D1. A Radio Access Network (RAN) node arranged to configure a User Equipment (UE) to perform Quality of Experience (QoE) measurements, the RAN node comprising: a communications interface circuit configured to communicate with a UE and a network node or function external to the RAN; a processing circuit operably coupled to the communications interface circuit, the processing circuit and the communications interface circuit configured to perform operations corresponding to the method of any one of embodiments B1 to B15; and Equipped with RAN node. D2. A Radio Access Network (RAN) node configured to configure a user equipment (UE) to perform quality of experience (QoE) measurements, the RAN node further configured to perform operations corresponding to the method of any one of embodiments B1 to B15. RAN node. D3. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a Radio Access Network (RAN) node prepared to configure a User Equipment (UE) to perform Quality of Experience (QoE) measurements, configure the RAN node to perform operations corresponding to the method described in any one of embodiments B1 to B24. D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a Radio Access Network (RAN) node arranged to configure a user equipment (UE) to perform quality of experience (QoE) measurements, configure the RAN node to perform operations corresponding to the method of any one of embodiments B1 to B24.

[0170] Abbreviation 3GPP 3rd Generation Partnership Project 5GCN 5G Core Network 5GS 5G System AF Application Features AMF Access and Mobility Management Functions AN Access Network API Application Programming Interface AGV automated guided vehicle BAP Backhaul Adaptation Protocol CN Core Network CP Control Plane CU Central Unit DC Dual Connectivity DU Distributed Unit eNB E-UTRAN Node B EN-DC E-UTRA-NR dual connectivity E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN gNB NR radio base station IAB Integrated Access and Backhaul ID Identifier / Identity IE Information Elements LTE Long Term Evolution MCE Measurement Collector Entity Minimizing MDT Drive Tests MME Mobility Management Entity MN Master Node MR-DC Multi-Radio Dual Connectivity NE-DC NR-E-UTRA dual connectivity NG Next generation NGEN-DC NG-RAN_E-UTRA-NR dual connectivity NG-RAN NG Radio Access Network NR New Radio OAM / O&M Operations and Maintenance PCF Policy Control Function QCI QoS Class Identifier QMC QoE measurement collection QoE quality of experience QoS Quality of Service RAN Radio Access Network RAT Radio Access Technology RRC Radio Resource Control S1 Interface between RAN and CN in LTE S1AP S1 Application Protocol SMF Session Management Facility SMO Service Management and Orchestration SN Secondary Node S-NSSAI Single Network Slice Selection Assistance Information TCE Trace Collector Entity UE User Equipment UPF User Plane Function

Claims

1. 1. A method for managing Quality of Experience (QoE) measurements by a User Equipment (UE) in a Radio Access Network (RAN) at a first RAN node, the method comprising: sending (1010) to a second RAN node within the RAN measurement status information relating to one or more QoE measurements configured for the UE by the first RAN node; sending a request for the one or more QoE measurements to the second RAN node (1020); receiving a message from the second RAN node approving the request or indicating that the request is not or cannot be complied with (1030); sending a second request to the second RAN node, the second request being modified based on the message received from the second RAN node; Including, The status information is an indication of whether a session of an application belonging to a service type for which QoE measurements are configured is in progress; an indication that a session of an application belonging to a service type for which QoE measurement is configured has started; and The second RAN node is associated with the first RAN node for dual connectivity. method.

2. The second RAN node Modifying the configuration of the UE for dual connectivity; the mobility of the UE; RRC resume or RRC re-establishment of the UE; switching the forwarding of data for a service from a path to the UE via the first RAN node to a path to the UE via the second RAN node; associated with the first RAN node with respect to at least one of The method of claim 1.

3. and configuring the UE for the one or more QoE measurements prior to the transmitting. The method according to claim 1 or 2.

4. The status information further includes: an identifier of the UE or a list of UE identifiers for a group of UEs that includes the UE and is configured for QoE measurements; QoE measurements or QoE measurement configurations configured for a wireless terminal or a group of wireless terminals; References relating to configured QoE measurements, an indication as to the type of QoE measurement configured; an indication of the service type or service subtype to which the QoE measurement relates; an indication that a session of an application belonging to a service type or service subtype for which QoE measurements are configured has been stopped; an indication of service subtypes per service type or a list of indications per service type or service subtype, indicating whether QoE measurements are configured, activated, suspended or deactivated; an indication that per-slice QoE measurements are enabled and a list of corresponding S-NSSAIs; an indication of the RAT type for which QoE measurements are valid; an indication regarding the MCE associated with the configured QoE measurement; an indication that the second RAN node considers the configured QoE measurements to be valid for a certain period of time or until a predetermined time; an indication of an area scope or a list of area scopes for which the configured QoE measurement configuration is valid; Reference to ongoing radio-related measurements coupled to ongoing QoE measurements Contains one or more of the following:

4. The method according to any one of claims 1 to 3.

5. The status information further includes: Configuring radio-related measurements coupled with ongoing QoE measurements; a reference or list of references to ongoing radio related measurements coupled to the ongoing QoE measurements; A reference or list of references for QoE measurements coupled to radio-related measurements Contains one or more of the following:

5. The method according to any one of claims 1 to 4.

6. The method includes transmitting the status information to the second RAN node along with status information associated with one or more additional UEs.

6. The method according to any one of claims 1 to 5.

7. The request is a request to suspend one or a list of activated QoE measurements; a request to resume one or a list of suspended QoE measurements; a request to deactivate or stop one or a list of activated QoE measurements; A request to reconfigure or replace the measurement configuration, or a list of such reconfigurations / replacements; a request to transmit the QoE report received by the second RAN node to the first RAN node; a request to configure the wireless terminal with the same configuration used by the first RAN node to configure the wireless terminal for radio measurements; Requests to trigger or clear previously configured measurements, stop ongoing measurements, suspend QoE configuration, or resume radio-related measurements Contains one of the following:

7. The method according to any one of claims 1 to 6.

8. 1. A method for managing Quality of Experience (QoE) measurements by a User Equipment (UE) in a Radio Access Network (RAN) at a second RAN node, the method comprising: receiving, from a first RAN node within the RAN, measurement status information relating to one or more QoE measurements configured for the UE by the first RAN node (1110); receiving a request for the one or more QoE measurements from the first RAN node (1120); In response to the request, sending a message to the first RAN node (1130) approving the request or indicating that the request is not or cannot be complied with; receiving 1140 a second request from the first RAN node, the second request being modified based on the message received from the second RAN node; Including, The status information is an indication of whether a session of an application belonging to a service type for which QoE measurements are configured is in progress; an indication that a session of an application belonging to a service type for which QoE measurement is configured has started; and The second RAN node is associated with the first RAN node for dual connectivity. method.

9. The second RAN node Modifying the configuration of the UE for dual connectivity; the mobility of the UE; RRC resume or RRC re-establishment of the UE; switching the forwarding of data for a service from a path to the UE via the first RAN node to a path to the UE via the second RAN node; associated with the first RAN node with respect to at least one of The method of claim 8.

10. The method includes refraining from configuring or modifying a configuration of QoE measurements by the UE in response to the status information.

10. The method according to claim 8 or 9.

11. The status information further includes: an identifier of the UE or a list of UE identifiers for a group of UEs that includes the UE and is configured for QoE measurements; QoE measurements or QoE measurement configurations configured for a wireless terminal or a group of wireless terminals; References relating to configured QoE measurements, an indication as to the type of QoE measurement configured; an indication of the service type or service subtype to which the QoE measurement relates; an indication that a session of an application belonging to a service type or service subtype for which QoE measurements are configured has been stopped; an indication of service subtypes per service type or a list of indications per service type or service subtype, indicating whether QoE measurements are configured, activated, suspended or deactivated; an indication that per-slice QoE measurements are enabled and a list of corresponding S-NSSAIs; an indication of the RAT type for which QoE measurements are valid; an indication regarding the MCE associated with the configured QoE measurement; an indication that the second RAN node considers the configured QoE measurements to be valid for a certain period of time or until a predetermined time; an indication of an area scope or a list of area scopes for which the configured QoE measurement configuration is valid; Reference to ongoing radio-related measurements coupled to ongoing QoE measurements Contains one or more of the following:

11. The method according to any one of claims 8 to 10.

12. The status information further includes: Configuring radio-related measurements coupled with ongoing QoE measurements; a reference or list of references to ongoing radio related measurements coupled to the ongoing QoE measurements; A reference or list of references for QoE measurements coupled to radio-related measurements Contains one or more of the following:

12. The method according to any one of claims 8 to 11.

13. The method includes receiving the state information from the first RAN node along with state information associated with one or more additional UEs.

13. The method according to any one of claims 8 to 12.

14. The request is a request to suspend one or a list of activated QoE measurements; a request to resume one or a list of suspended QoE measurements; a request to deactivate or stop one or a list of activated QoE measurements; A request to reconfigure or replace the measurement configuration, or a list of such reconfigurations / replacements; a request to transmit the QoE report received by the second RAN node to the first RAN node; a request to configure the wireless terminal with the same configuration used by the first RAN node to configure the wireless terminal for radio measurements; Requests to trigger or clear previously configured measurements, stop ongoing measurements, suspend QoE configuration, or resume radio-related measurements Contains one of the following:

14. A method according to any one of claims 8 to 13.

15. The method further includes responding with an indication of the execution status of the request.

15. The method of claim 14.

16. The request relates to multiple UEs.

16. The method of claim 14 or 15.

17. A Radio Access Network (RAN) node (1400) arranged to configure a User Equipment (UE) to perform Quality of Experience (QoE) measurements, the RAN node (1400) comprising: a communication interface circuit (1440, 1450) configured to communicate with a UE and a network node or function external to the RAN; a processing circuit (1310, 1320, 1330) operably coupled to the communication interface circuit (1440, 1450), the processing circuit (1310, 1320, 1330) and the communication interface circuit (1440, 1450) being configured to perform a method according to any one of claims 1 to 16; Equipped with RAN node.

Images