WO2024035295A1

WO2024035295A1 - Radio access network (ran) visible quality of experience (rvqoe) measurement configuration originating from the distributed unit (du) or control unit-user plane (cu-up)

Info

Publication number: WO2024035295A1
Application number: PCT/SE2023/050753
Authority: WO
Inventors: Filip BARAC; Luca LUNARDI; Johan Rune
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-08-09
Filing date: 2023-07-25
Publication date: 2024-02-15

Abstract

A method, system and apparatus for methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unit-user plane (CU-UP) are disclosed. According to one aspect, a method in a first network node configured to communicate with a second network node is provided, the first network node being one of a DU, and a CU-UP, and the second network node being one of a centralized unit CU and a centralized unit-control plane (CU-CP). The method includes determining whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements based at least in part on communication parameters. The method also includes sending to a second network node a request for RVQoE measurements for at least one wireless device, WD, based at least in part on the collection determination.

Description

RADIO ACCESS NETWORK (RAN) VISIBLE QUALITY OF EXPERIENCE (RVQOE) MEASUREMENT CONFIGURATION ORIGINATING FROM THE DISTRIBUTED UNIT (DU) OR CONTROL UNIT-USER PLANE (CU-UP)

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unituser plane (CU-UP).

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. Sixth Generation (6G) wireless communication systems are also under development.

The NG-radio access network (RAN) includes a set of gNBs (network nodes) connected to the 5G core through the NG interface.

As specified in 3GPP Technical Standard (TS) 38.300, NG-RAN may also include a set of ng-eNBs. An ng-eNB may include an ng-eNB-CU and one or more ng-eNB- DU(s). An ng-eNB-CU and an ng-eNB-DU may be connected via W1 interface. The general principle described in this section also applies to the ng-eNB and W1 interface, if not explicitly specified otherwise.

A network node may support frequency division duplex (FDD) mode, time division duplex (TDD) mode or dual mode operation. Network nodes may be interconnected through the Xn interface. A network node may include a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via an Fl interface. One gNB-DU is connected to only one gNB-CU.

In cases of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of public land mobile network (PLMNs) corresponds to a gNB- DU and the gNB-CU it is connected to, i.e., the corresponding gNB-DUs share the same physical layer cell resources. For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation.

NG-RAN interfaces, namely, NG, Xn, and Fl, are logical interfaces.

For NG-RAN, the NG and Xn-C interfaces for a network node that includes a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a network node that includes a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a network node.

The node hosting a user plane part of NR packet data convergence protocol (PDCP) (e.g., gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node having a C-plane connection towards the core network (e.g., over El, X2). The node hosting NR radio link control (RLC) (e.g., gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g., gNB-CU or gNB-CU-CP.

An uplink (UL) PDCP configuration (i.e., how the WD uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and Fl-C. Radio Link Outage/Resume for DL and/or UL is indicated via X2-U (for EN-DC), Xn-U (for NG- RAN) and Fl -U.

The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as a part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport.

In NG-Flex configuration, each NG-RAN node is connected to all access and mobility management function (AMFs) of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are, for example, defined in 3GPP TS 23.501.

If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP 3GPP TS 33.501 is applied.

Overall architecture for separation of gNB-CU-CP and gNB-CU-UP

An example of an overall NG-RAN architecture is shown in FIG. 1. An example of an overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in FIG. 2 and an example is specified in 3GPP TS 37.483. With respect to the example architecture, the following is noted:

A network node may include a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs;

The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface; The gNB-CU-UP is connected to the gNB-DU through the Fl-U interface; The gNB-CU-UP is connected to the gNB-CU-CP through the El interface; One gNB-DU is connected to only one gNB-CU-CP; and

One gNB-CU-UP is connected to only one gNB-CU-CP.

For resiliency, a gNB-DU and/or a gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. The following examples are noted:

One gNB-DU may be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP;

One gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP; and

The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB-CU-CP using Bearer Context Management functions.

The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the WD. In case of multiple CU-UPs they belong to same security domain, for example, as defined in 3GPP TS 33.210.

Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

RAN visible quality of experience (RVQoE)

In NR, 3GPP Technical Release 17 (3GPP Rel-17) introduced RAN visible quality of experience (QoE) (RVQoE) measurements. A general description may be found in 3GPP TS 38.300 vl7.0.0 clause 21.4.

RVQoE measurements are configured by the NG-RAN node, where a subset of QoE metrics is reported from the WD as an explicit information element (IE) readable by the NG-RAN node. RAN visible QoE measurements (e.g., RVQoE metrics, RVQoE values) may be utilized by the NG-RAN node for network optimization. RAN visible QoE measurements are supported for the Dynamic Adaptive Streaming over hypertext transfer protocol (HTTP) (DASH) streaming and VR services. The NG-RAN node configures the RAN visible QoE measurement to collect all or some of the available RAN visible QoE metrics, where the indication of metric availability is received from the Operation and Maintenance (0AM) or core network (CN). The set of available RAN visible QoE metrics is a subset of the metrics which are already configured as part of QoE measurement configuration encapsulated in the transparent container. The packet data unit (PDU) session ID(s) corresponding to the service that is subject to QoE measurements may also be reported by the WD along with the RAN visible QoE measurement results.

A request for collecting QoE measurements not visible to RAN (also called OAM-QoE in 3GPP R3-223290) is started from 0AM and identified by a QoE Reference. A definition for this identifier may be found, e.g., in 3GPP TS 28.405 V17.1.0, clause 5.2.

The QoE reference parameter specifies the network request session. The QoE reference shall be globally unique therefore it is composed as follows:

MCC+MNC+QMC ID, where the mobile country code (MCC) and mobile network code (MNC) are coming with the QoE measurement collection (QMC) activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 byte Octet String.

The QMC ID is generated by the management system or the operator and is used to identify the QoE measurement collection job in the traffic nodes and in the measurement collection center.

The WD access stratum (AS) layer may report to a network node the RAN visible QoE measurements in radio resource control (RRC) format and a WD Application Layer may be configured for performing more application layer measurements at the same time (in NR 3GPP Rel-17 up to 16) and, e.g., in 3GPP TS 38.331, an application layer measurement is identified by the MeasConfigAppLayerld IE.

In a network node, RAN visible QoE information may be transferred from gNB- CU to the gNB-DU in a procedure described in 3GPP TS 38.473 vl7.0.0. The procedure is WD-associated, i.e., it is specific for a WD. The corresponding excerpts from 3GPP TS 38.473 V17.1.0 are shown below to provide an understanding.

- Start of excerpts from3GPP TS 38.473 -

QoE Information Transfer

The purpose of the QoE Information Transfer procedure is to transfer RAN visible QoE information from the gNB-CU to the gNB-DU. The procedure uses WD-associated signaling. See FIG. 3.

The gNB-CU initiates the procedure by sending the QOE INFORMATION TRANSFER message to the gNB-DU.

If the QoE Information List IE is included in QoE INFORMATION TRANSFER message, the gNB-DU may take it into account according to 3GPP TS 38.300.

QOE INFORMATION TRANSFER This message is sent by a gNB-CU to a gNB-DU, to indicate information related to

RAN visible QoE.

Direction: gNB-CU -> gNB-DU.

QoE Metrics This IE provides the RAN visible QoE measurement report to gNB-DU.

- End _of excerpts from TS 38.473 -

In the contribution R3-223128 to 3 GPP TSG-RAN WG3 Meeting #116-e, the association of RAN visible QoE report to a reference is discussed. In F1AP a list containing currently considered RVQoE metrics is transferred over Fl using WD-associated signalling. But the reports are not associated with e.g., any reference or other identification (ID). So the gNB-DU will not know how many different application sessions that provide reports, and the currently defined signalling will therefore not allow the gNB-DU to distinguish between QoE reports coming from the different application sessions. Also, the gNB-DU will not be able to group reports that it successively receives from a given application session and will therefore not be able to trace e.g., any tendencies in the reported data.

A candidate reference or other ID that could solve this issue would typically be the QoE reference or the short RRC id (measConfigAppLayerld) allocated by the WD. In the F1AP CR submitted to the present meeting in R3 -223131, the QoE reference was considered, but the ultimate choice may be subject for further evaluation.

In the same contribution, the following proposal was made according to the reported considerations:

Proposal 3: RAN3 to discuss identifying RVQoE report information over Fl using QoE Reference or short RRC id (measConfigAppLayerld).

Current 3 GPP specifications stipulate that, in the case of split gNB architecture, it is the CU-CP or the CU that assembles the RVQoE configuration for the WD, based on the RVQoE measurement availability indication received from the 0AM. This means that the decision about whether a WD will run RAN visible QoE (RVQoE) measurements is, as of today, solely up to the CU/CU-CP.

On the other hand, RAN nodes other than the CU-CP/CU, such as the DU or the CU-UP, may benefit from receiving the RVQoE reports, and therefore the 3GPP TS 38.473 specifies the F1AP signaling to deliver the RVQoE report from the CU/CU-CP to the DU. Nevertheless, even though the DU may be a recipient/user/consumer of RVQoE reports, as of today, the DU has no say in assembling the RVQoE configuration or even deciding whether RVQoE measurements are to be executed by the WDs.

SUMMARY

Some embodiments advantageously provide methods and network nodes for methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unituser plane (CU-UP).

Some embodiments provide a solution enabling the DU and/or CU-UP to assemble the RVQoE configuration for the WD and deliver it to the CU/CU-CP, which then delivers it to one or more WDs.

In some embodiments, the DU or CU-UP is enabled to request the RVQoE measurements and/or decide the content of the RVQoE measurement configuration.

Some embodiments enable the network entities that are the recipients of the RVQoE reports, and that may benefit from receiving RVQoE reports, to participate in assembling the RVQoE measurement configuration, leading to a better adjustment of RVQoE measurements to the needs of the network.

According to one aspect, a first network node configured to communicate with a second network node is provided. The first network node is a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node is a centralized unit, CU, or a centralized unit-control plane CU-CP. The first network node is configured to determine whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements. The first network node is configured to send to the second network node a request for RVQoE measurements for at least one wireless device, WD, based at least in part on the collection determination.

According to this aspect, in some embodiments, the first network node is configured to update the request for RVQoE measurements based at least in part on the received RVQoE measurements. In some embodiments, the request for RVQoE measurements includes a request to configure the at least one WD with measurements of available RVQoE metrics. In some embodiments, the collection determination is based at least in part on at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node. In some embodiments, the first network node is configured to configure an application layer of the WD to perform application layer measurements. In some embodiments, the first network node is configured to determine at least one of RVQoE metric to be measured, a duration of an RVQoE measurement and a periodicity for sending RVQoE reports. In some embodiments, the first network node is configured to identify a group of WDs for RVQoE measurements based at least in part on at least one of whether a WD is in multi-broadcast session, whether a WD is in a particular paging group and whether a WD is in a particular tracking area. In some embodiments, the first network node is configured to send to the second network node at least one of an RVQoE configuration and a list of RVQoE reporting periodicities. In some embodiments, the first network node is configured to send an RVQoE configuration to the WD. According to another aspect, a method implemented in a first network node configured to communicate with a second network node is provided. The first network node is a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node is one a centralized unit, CU, or a centralized unit-control plane CU-CP. The method includes determining whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements. The method also includes sending to the second network node a request for RVQoE measurements for at least one wireless device, WD, based at least in part on the collection determination.

According to this aspect, the method includes updating the request for RVQoE measurements based at least in part on the received RVQoE measurements. In some embodiments, the request for RVQoE measurements includes a request to configure the at least one WD with measurements of available RVQoE metrics. In some embodiments, the collection determination is based at least in part on at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node. In some embodiments, the method includes configuring an application layer of the WD to perform application layer measurements. In some embodiments, the method includes determining at least one of RVQoE metric to be measured, a duration of an RVQoE measurement and a periodicity for sending RVQoE reports. In some embodiments, the method includes identifying a group of WDs for RVQoE measurements based at least in part on at least one of whether a WD is in multi-broadcast session, whether a WD is in a particular paging group and whether a WD is in a particular tracking area. In some embodiments, the method includes sending to the second network node at least one of an RVQoE configuration and a list of RVQoE reporting periodicities. In some embodiments, the method includes sending an RVQoE configuration to the WD.

According to another aspect, a second network node configured to communicate with a first network node is provided. The first network node is a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node is a centralized unit, CU, or a centralized unit-control plane CU-CP. The second network node is configured to receive from the first network node a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD. The second network node is configured to configure the at least one WD to perform RVQoE measurements according to the request.

According to this aspect, in some embodiments, configuring the at least one WD is based at least in part on a QoE configuration received by the second network node from another network node. In some embodiments, configuring the at least one WD is based at least in part on at least one of a characteristic and a capability of the WD. In some embodiments, the received request includes an RVQoE configuration for configuring the at least one WD.

According to yet another aspect, a method in a second network node configured to communicate with a first network node is provided. The first network node is a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node is a centralized unit, CU, or a centralized unit-control plane CU-CP. The method includes receiving from the first network node a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD. The method includes configuring the at least one WD to perform RVQoE measurements according to the request.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. l is a diagram of an NG RAN architecture;

FIG. 2 is a diagram of an NG RAN architecture for separation of control and user plane functions;

FIG. 3 is an illustration of a QoE transfer procedure;

FIG. 4 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure; FIG. 5 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of an example process in a first network node for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unit-user plane (CU-UP); and

FIG. 11 is a flowchart of an example process in a second network node for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unit-user plane (CU-UP).

DETAILED DESCRIPTION

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unituser plane (CU-UP). Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein may be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein may be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

The terms “application layer measurement configuration”, "application measurement configuration”, “QoE measurement configuration”, “QoE configuration”, “QoE measurement and reporting configuration” and “QMC configuration” are used interchangeably. But note that the “QMC configuration file” is not an equivalent term, but instead refers to the part of the QoE configuration including an XML file containing instructions of QoE metrics to be collected, etc.

The terms “QoE report” and “QoE measurement report” are used interchangeably herein. Similarly, the terms “RAN Visible QoE report”, “RAN Visible QoE measurement report”, “RVQoE report” and “RVQoE measurement report” are used interchangeably.

The terms “modem”, “radio layer”, “RRC layer” and “radio network layer” are used interchangeably when referring to a WD.

The terms “access stratum” and “radio layer” are used interchangeably when referring to a WD.

The term “session” is used herein, and it may refer to either a QoE measurement session or an application session or an application session for which QoE measurement is applied. The term “session” is used frequently herein, and it may refer to either a QoE measurement session or an application session or an application session for which QoE measurement is applied.

The term “RVQoE value” may refer to a set of values derived from QoE metrics data through a model/function defined in collaboration with SA4, for example as defined in 3GPP TR 38.890.

The solutions described herein may apply to UMTS, LTE and NR as well as future RATs such as 6G.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.

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. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unit-user plane (CU-UP).

Returning now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 4 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 may be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 may be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 4 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 may be configured to include an RVQoE unit 32 which is configured to determine whether to collect RVQoE measurements based at least in part on communication determination. The network node 16 may be configured to include a configuration unit 34 which is configured to configure the at least one WD to perform RVQoE measurements according to the request.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 5. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include an RVQoE unit 32 which is configured to determine whether to collect RVQoE measurements based at least in part on communication determination. The network node 16 may be configured to include a configuration unit 34 which is configured to configure the at least one WD to perform RVQoE measurements according to the request.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 4. In FIG. 5, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the WD 22, and/or preparing/terminating/ maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/ supporting/ending a transmission to the network node 16, and/or preparing/ terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 4 and 5 show various “units” such as RVQoE unit 32, and configuration unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 4 and 5, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 5. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 4 and 5. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

FIG. 10 is a flowchart of an example process in a first network node 16a for methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration, the first network node 16a being in communication with a second network node, the first network node being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node being one of a centralized unit, CU, and a centralized unit-control plane CU-CP. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the RVQoE unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to determine whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements based at least in part on communication parameters (Block SI 34). The process also includes sending to a second network node 16b a request for RVQoE measurements for at least one wireless device, WD 22, based at least in part on the collection determination (Block SI 36).

In some embodiments, the first network node 16a is According to this aspect, the method includes updating the request for RVQoE measurements based at least in part on the received RVQoE measurements. In some embodiments, the request for RVQoE measurements includes a request to configure the at least one WD 22 with measurements of available RVQoE metrics. In some embodiments, the collection determination is based at least in part on at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node 16a. In some embodiments, the method includes configuring an application layer of the WD 22 to perform application layer measurements. In some embodiments, the method includes determining at least one of RVQoE metric to be measured, a duration of an RVQoE measurement and a periodicity for sending RVQoE reports. In some embodiments, the method includes identifying a group of WDs for RVQoE measurements based at least in part on at least one of whether a WD 22 is in multi-broadcast session, whether a WD 22 is in a particular paging group and whether a WD 22 is in a particular tracking area. In some embodiments, the method includes sending to the second network node 16b at least one of an RVQoE configuration and a list of RVQoE reporting periodicities. In some embodiments, the method includes sending an RVQoE configuration to the WD 22.

FIG. 11 is a flowchart of an example process in a second network node 16b for methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration, the first network node 16a being in communication with a second network node 16b, the first network node 16a being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node 16b being one of a centralized unit, CU, and a centralized unit-control plane CU-CP. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 34), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to receive from the first network node 16a a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD 22 (Block S138). The process also includes configuring the at least one WD 22 to perform RVQoE measurements according to the request (Block S140).

In some embodiments, configuring the at least one WD 22 is based at least in part on a QoE configuration received by the second network node 16b from another network node 16. In some embodiments, configuring the at least one WD 22 is based at least in part on at least one of a characteristic and a capability of the WD 22. In some embodiments, the received request includes an RVQoE configuration for configuring the at least one WD 22.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for methods for radio access network (RAN) visible quality of experience (RVQoE) measurement configuration originating from a distributed unit (DU) or centralized unit-user plane (CU-UP). The DU or the CU-UP may assemble an RVQoE measurement configuration and deliver it to the CU/CP. Then, the CU/CU-CP configures the WD 22 for RVQoE measurements accordingly.

NOTE: in the below embodiments, in accordance with the NG-RAN architecture:

• when the first network node 16a is the DU, the second network node 16b may be the CU or the CU-CP; and

• when the first network node 16a is the CU-UP, the second network node 16b may be the CU-CP.

At least some embodiments may apply to integrated access and backhaul (IAB) nodes. In such cases:

• when the first network node 16a is the IAB-DU, the second network node 16b is the lAB-donor-CU; and

• when the first network node 16a is the lAB-donor-CU-UP, the second network node 16b is the lAB-donor-CU-CP.

The RVQoE measurement configuration may be assembled by a RAN node other than the CU/CU-CP. Such a RAN node is referred to as the first network node 16a. The first network node 16a may be e.g., a DU, IAB-DU, CU-UP, whereas some of the steps below may apply to some or all of the three. The steps may include one or more of the following Steps 100 -110

1. (Step 100) The first network node 16a (e.g., DU or CU-UP) determines that there may be a need for RVQoE measurements to be collected for one or more WDs 22. The determination may be based on, e.g., one or more of:

• AS layer measurements at the WD(s) 22;

• AS layer measurements at the first network node 16a or another network node;

• Layer 1/ Layer 2 mobility;

• Mobility to/from a cell served by the first network node 16a;

• The first network node 16a setting up of bearer context for a WD 22;

• The first network node 16a setting up of DRB / MRB (in the case that a WD 22 is in a multicast and broadcast services (MBS) session) for a WD 22. In particular if the first network node 16a is a DU: the traffic load in a certain cell. For instance, the first network node 16a may choose to request RVQoE measurements if the traffic load is high in a cell. Herein, that the traffic load is high may, for example, be determined by, e.g., one or more of: o the traffic load exceeding a certain threshold; o the average traffic load during a last time period T exceeding a certain threshold; o the sliding average of the traffic load exceeding a certain threshold, where the sliding average may be calculated, e.g., using a sliding time window or as an exponential average; o one or more WD(s) 22 being underserved, e.g., meaning (or defined by) one of or a combination of:

■ the first network node 16a determining or assessing that at least one WD 22 does not (e.g., may not, due to competition for transmission resources between WDs 22) receive its desired resource allocations or does not receive sufficient resource allocations to reach a certain, e.g. minimum, level of service;

■ the first network node 16a determining that it may not accept, and serve, all scheduling requests from one or more WD(s) 22;

■ the first network node 16a determining that it may not provide one or more WD(s) 22 with resources matching the pending traffic sufficiently fast (i.e., data waiting to be transmitted), e.g., as indicated by Buffer Status Report(s) from the WD(s) 22; and/or

• Any of the above combined with indication(s) from the CU-CP (which as described further below will be called a second network node 16b) associated with the first network node 16a that RVQoE metrics are available for measurements for the one or more WD(s) 22 (i.e., that the one or more WD(s) 22 has/have the required prerequisite and support for carrying out RVQoE measurements according to RVQoE configuration(s));

(step 110) The first network node 16a also determines one or more of the following parameters for the RVQoE configuration, such as, e.g.:

• the identifier(s) of the one or more WDs 22 (e.g., the gNB-CU WD F1AP ID, gNB-DU WD F1AP ID, gNB-CU-UP WD El AP ID, gNB-CU-CP WD E1AP ID, C-RNTI, RAN WD ID), i.e., a WD 22 identifier or identifiers of WD associated signaling; • the RVQoE metrics or RVQoE values to be measured;

• the duration of the RVQoE measurement;

• the periodicity for sending the RVQoE reports;

• one or a list of acceptable periodicities for receiving RVQoE reports;

• minimum/maximum/preferred periodicities for receiving RVQoE reports;

• triggering events and conditions to be fulfilled for measurement execution, logging and/or reporting, where determining events/conditions may include determining threshold values, maximal time periods, time to trigger periods, etc.;

• which state(s) (e.g., RRC state(s)) the RVQoE measurements should be performed in;

• which network slice(s) the RVQoE measurements should be performed on (i.e., in practice a restriction of the scope in terms of network slice(s));

• desired area for the RVQoE measurements (which may be fully (or at least partly) included in any area scope associated with the QoE configuration);

• Service type or service types. For instance, if the first network node 16a does not know the (full) QoE configuration and therefore does not know with which service type(s) (if any) the WD is configured to perform QoE measurements, the first network node 16a may indicate one or more service type(s) of interest, which may include instructing the second network node 16b to configure the WD with RVQoE measurements (e.g., RVQoE measurements for the available RVQoE metrics) only if the service type associated with the corresponding QoE configuration is X (where X may e.g. be “streaming”); and/or

• Service delivery modes (in the case of MBS).

2. (step 200) The first network node 16a sends to the CU/CU-CP (herein referred to as the second network node 16b), e.g., via E1AP or F1AP, the request for RVQoE measurements for one or more WDs 22.

The first network node 16a may include in the indication the parameters for the RVQoE configuration(s) described in Step 110, and the identifier(s) of the WD(s) for which the RVQoE measurements are requested. Below follow some variations of this step - note that more than one of these variations may exist in parallel;

• (step 200a) In one variant, pertaining to cases where RVQoE measurements at the WD may be executed only if the corresponding QoE measurements are configured at the WD, if the second network node 16b determines that there is no QoE configuration corresponding to the RVQoE measurements requested by the first network node 16a, the second network node 16b forwards the request from the first network node 16a (with or without further processing) to the third network node (e.g., an 0AM node). The third network node 16c then, as in existing standard specifications, assembles the QoE configuration for the WD and sends to the second network node 16b the QoE configuration and the indication of the available RVQoE metrics. The second network node 16b then configures the WD with RVQoE measurements, according to the parameters in the request received from the first network node 16a (e.g. the parameters described in Step 110);

• (step 200b) In another variant, also pertaining to the case where RVQoE measurements at the WD may be executed only if the corresponding QoE measurements are configured at the WD, the second network node 16b checks whether it has previously received a management-based QoE configuration from the 0AM, whose configuration criteria are satisfied by the WD(s) for which the first network node 16a requests the RVQoE measurements, and which satisfy any configuration criteria indicated by the first network node 16a (for example, the management-based QoE configuration pertains only to WDs 22 in certain cells). In case any such managementbased QoE configurations are found at the second network node 16b, the second network node 16b then configures the WD(s) with RVQoE measurements, according to the parameters in the request received from the first network node 16a, e.g., the parameters described in Step 110);

• (step 200c) In another variant, pertaining to the case where RVQoE measurements at the WD may be executed regardless of whether corresponding QoE measurements are configured at the WD, the second network node 16b configures the WD(s) with RVQoE measurements according to the request received from the first network node 16a in (e.g., using the parameters determined by and described in Step 110).

3. (step 300) The WD(s) execute the RVQoE measurements according to the received configuration(s) and deliver(s) the report(s) to the second network node 16b, which then forwards the report(s) to the first network node 16a.

4. (step 400) At a later point in time, should the first network node 16a see a need to modify a RVQoE configuration, or indicated RVQoE measurements, it has previously requested from the second network node 16b, the first network node 16a assembles an update of the RVQoE configuration, or indicated RVQoE measurements, and delivers the updated RVQoE configuration or indicated RVQoE measurements, to the first network node 16a, which then configures the affected WD(s) accordingly. The updated RVQoE configuration or indicated RVQoE measurements may be sent as deltaconfiguration or delta-indications, i.e. indicating only the change(s) from the previously sent version.

In some embodiments, a need for RVQoE measurements and the corresponding RVQoE configuration are determined by the first network node 16a for a WD. Alternatively, these may be determined by the first network node 16a for a group of WDs 22. In this alternative, when the first network node 16a sends to the second network node 16b a request for RVQoE measurements (see step 200), it does not include in the request the identifiers of the single WD, but it may include an identity identifying a group of WDs 22, or an identity which collectively identify the WDs 22 for which the first network node 16a has determined a need for RVQoE measurements., e.g. The WDs 22 for which RVQoE measurements are needed may be based on any of the following or any combination of the following:

For the case when a WD is in an MBS Session:

• For all WDs 22 in an MBS session;

• For all WDs 22 in any Multicast session;

• For all WDs 22 in a given Multicast session;

• For all WDs 22 in any Broadcast session;

• For all WDs 22 in a given Broadcast session For all WDs 22 with the same MBS Frequency Selection Area (FSA) ID;

• For all WDs 22 associated to a same Paging Group;

• For all WDs 22 associated to a same Temporary Mobile Group

Identity (TMGI);

• For all WDs 22 served by a specific cell of the first network node

16a or any cell of the first network node 16a (e.g. if the first network node 16a is a DU)

• For all WDs 22 connected to, or associated with, a specific reference signal beam or to any reference signal beam served by the first network node 16a;

• For all WDs 22 in a certain tracking area (TA) or list of tracking areas;

For all WDs 22 except WDs 22 in a certain tracking area (TA) or list of tracking areas;

For all WDs 22 in a certain RAN Notification Area or list of RAN

Notification Areas;

• For all WDs 22 except WDs 22 in a certain RAN Notification Area or list of RAN Notification Areas;

• For all WDs 22 in an area defined by a list of cells;

• For all WDs 22 except WDs 22 in an area defined by a list of cells;

• For all WDs 22 in a certain geographical area, defined using area and shape description parameters, e.g. such parameters as the ones specified in 3GPP TS 23.032 version 17.2.0;

• For all WDs 22 except WDs 22 in a certain geographical area, defined using area and shape description parameters, e.g. such parameters as the ones specified in 3GPP TS 23.032 version 17.2.0;

• For all WDs 22 served by the first network node 16a;

• For all WDs 22 moving towards a cell served by the first network node 16a;

• For all WDs 22 for which the first network node 16a set up a bearer context;

• For all WDs 22 which have one or more certain QoS class(es) configured for one or more data flows;

• For all WDs 22 which have a QoS class other than best effort configured for at least one data flow;

• For all WDs 22 whose traffic (e.g. transmitted and/or received data volume) during the latest time period T exceeds a threshold: o This may be indicated per link direction, e.g. one threshold for the uplink and one threshold for the downlink and, as one option, both conditions have to be fulfilled, or, as another option, it suffices that at least one condition is fulfilled; o The threshold may be applied only for downlink traffic; o The threshold may be applied only for uplink traffic;

• For all WDs 22 whose average data rate during the last time period T exceeds a threshold;

For all WDs 22 whose sliding average of the data rate exceeds a threshold, where the sliding average may be calculated, e.g., using a sliding time window or as an exponential average; o The threshold may be applied only for downlink traffic; o The threshold may be applied only for uplink traffic; o This may be indicated per link direction, e.g. one threshold for the uplink and one threshold for the downlink and, as one option, both conditions have to be fulfilled, or, as another option, it suffices that at least one condition is fulfilled;

• For all WDs 22 with signaling -based QoE configuration;

• For all WDs 22 with management-based QoE configuration;

• For all WDs 22 with QoE measurements configured (or to be configured) for a certain service type or certain service types;

• For all WDs 22 using a certain network slice or a set of network slices; and/or

• For all WDs 22 of a certain category, e.g., loT devices or URLLC devices, or certain categories.

In an alternative solution, the first network node 16a does not determine itself the RVQoE configuration to be sent to the WD (or the group of WDs 22). Instead, it assists the second network node 16b in constructing the RVQoE configuration. It does this by sending to the second network node 16b one or more proposed configuration parameters and/or preferences which the second network node 16b may use to determine the final RVQoE configuration for the WD(s). For example, the first network node 16a (e.g., a DU) may indicate to the second network node 16b (e.g., a CU-CP) a list of potential RVQoE reporting periodicities that would be acceptable for the DU, and the second network node 16b may select one of them.

In this alternative solution, some steps are the same as above. The steps are listed below:

Steps that are equivalent to any of or more of Steps 100-110 may be performed for a purpose of determining and/or producing information to be sent to the second network node 16b to assist the second network node 16b in the determination of the RVQoE configuration.

In further alternative embodiments or solution variants, or embodiments complementing any of the embodiments described above, to facilitate an ability of the first network node 16a (e.g. DU or CU-UP) to create the RVQoE configuration (e.g., request the RVQoE measurements, e.g., request the CU-CP to configure the WD with RVQoE measurements according to the request and/or instruction from the first network node 16a (DU or CU-CP), the second network node 16b (CU-CP) sends the QoE configuration, or relevant QoE configuration parameters, to the first network node 16a (e.g. DU or CU-UP) after receiving it/them from the 0AM (for management-based QoE configuration) or the core network (for signaling-based QoE configuration), but before sending the QoE configuration to a WD.

The second network node 16b (CU-CP) awaits a response from the second network node 16b (e.g. DU or CU-UP), containing either a request for RVQoE measurements or an indication of “no interest in RVQoE measurements”, and then sends the QoE configuration and the possible associated RVQoE configuration to a WD. The signaling between the first network node 16a and the second network node 16b may be performed using WD associated Fl AP signaling (if the first network node 16a is a DU) or WD associated E1AP signaling (if the first network node 16a is a CU-UP). This means that for management-based QoE configuration, the second network node 16b (CU-CP) selects the WD(s) to send the QoE configuration to before sending the message to the first network node 16a (e.g. DU or CU-UP). As an alternative for management-based QoE configuration, the second network node 16b (CU-CP) may use non-WD associated F1AP or E1AP signaling (and the message may then be sent before the second network node 16b (CU-CP) selects the WD(s) 22 to receive the QoE configuration) and the first network node 16a (e.g. DU or CU-UP) may request the RVQoE measurements (or create the RVQoE configuration) concerning any WD 22 yet to be selected for the managementbased QoE configuration.

The above mentioned “relevant QoE configuration parameters” may include at least indication(s) of available RVQoE metric(s) and may include an identifier of the QoE configuration (i.e., a QoE Reference or a measConfigAppLayerld).

As an alternative, the second network node 16b (CU-CP) does not withhold a QoE configuration that it has received from the 0AM or the core network to wait for a response (indicating a request, or lack of interest, for RVQoE measurements) from the first network node 16a (e.g. DU or CU-UP), but sends the QoE configuration to the WD immediately (i.e., after selection of the WD in the case of management-based QoE configuration) and/or (before, after, or in parallel with the transmission of the relevant QoE configuration parameter to the first network node 16a (e.g. DU or CU-UP)). In some embodiments, If the first network node 16a (e.g. DU or CU-UP) subsequently responds with a request for RVQoE measurements (or a RVQoE configuration), the second network node 16b (CU- CP) complements the QoE configuration already sent to the WD with an RVQoE configuration matching the request for RVQoE measurements received from the first network node 16a (e.g. DU or CU-UP), Or, if a ready-made RVQoE configuration is received from the first network node 16a (e.g. DU or CU-UP), the second network node 16b forwards the RVQoE configuration received from the first network node 16a (e.g. DU or CU-UP) to the WD.

In some embodiments, e.g., alternative or complementing embodiments, the first network node 16a (e.g., DU or CU-UP) neither configures the RVQoE measurements nor requests specific RVQoE measurements to be performed, but instead sends a request to the second network node 16b (CU-CP) to configure the WD with measurements of all available RVQoE metrics. In some embodiments, this request may be sent using WD associated Fl AP signaling (if the first network node 16a is a DU) or WD associated E1AP signaling (if the first network node 16a is a CU-UP). In some embodiments, the request may be sent using non-UE associated Fl AP or E1AP signaling, as a generic request to the second network node 16b (CU-CP) to always configure RVQoE measurements (for all available RVQoE metrics) for all WDs 22 which are configured for QoE measurements. In some embodiments, the first network node 16a (e.g. DU or CU-UP) may restrict the generic request to a group of WDs 22 or WDs 22 fulfilling a certain criterion or certain criteria., For example, such WDs 22 may include WDs 22 for which the QoE configuration targets a certain service type, WDs 22 for which the QoE configuration may be restricted to a certain network slice (or network slices), WDs 22 using a certain network slice (or network slices), and/or WDs 22 fulfilling any of the previously described criteria for determining WDs 22 for which the RVQoE configuration, or request for RVQoE measurements, should apply. Other restrictions on WDs 22 of the group of WDs 22 fulfilling certain criteria may include that only WDs 22 of a certain type or category (or certain types or categories) should receive the RVQoE configuration, e.g., loT WDs 22 and/or URLLC WDs 22, or that only WDs 22 of other types or categories than certain excluded ones should receive the RVQoE configuration. Yet other restrictions may be related to an area in which RVQoE measurements should be performed (or an aera in which RVQoE measurements should not be performed), where an area may be, e.g., a geographical area defined by shape and area parameter, a list of cell(s), a list of tracking area(s), or a list of RAN Notification Area(s). For instance, an area in which RVQoE measurements should be performed must be fully, or at least partly, included an area scope (if any) associated with the WD’s QoE configuration. Similarly, in some embodiments, an area which may be excluded from RVQoE measurements may not be covered (partially or fully) by an area scope associated with the WD’s QoE configuration.

In some embodiments, the second network node 16b (CU-CP) may modify a RVQoE configuration received from a first network node 16a (e.g., a DU or a CU-UP) before sending the RVQoE configuration to a concerned WD, and/or may add RVQoE measurements to, or remove RVQoE measurements from, the RVQoE measurement(s) requested from a first node (e.g. a DU or a CU-UP) before configuring the WD to perform the RVQoE measurements.

Some embodiments may include one or more of the following:

Embodiment Al . A first network node configured to communicate with a second network node, the first network node being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node being one of a centralized unit, CU, and a centralized unit-control plane CU-CP, the first network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements based at least in part on communication parameters; and send to a second network node a request for RVQoE measurements for at least one wireless device, WD, based at least in part on the collection determination.

Embodiment A2. The first network node of Embodiment Al, wherein the first network node, radio interface and/or processing circuitry are configured to receive RVQoE measurements from the second network node.

Embodiment A3. The first network node of Embodiment A2, wherein the first network node, radio interface and/or processing circuitry are configured to update the request for RVQoE measurements based at least in part on the received RVQoE measurements.

Embodiment A4. The first network node of any of Embodiments A1-A3, wherein the request for RVQoE measurements includes a request to configure the at least one WD with measurements of available RVQoE metrics.

Embodiment A5. The first network node of any of Embodiments A1-A4, wherein the communication parameters include at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node.

Embodiment Bl. A method implemented in a first network node configured to communicate with a second network node, the first network node being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node being one of a centralized unit, CU, and a centralized unit-control plane CU-CP, the method comprising: determining whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements based at least in part on communication parameters; and sending to a second network node a request for RVQoE measurements for at least one wireless device, WD, based at least in part on the collection determination.

Embodiment B2. The method of Embodiment Bl, further comprising receiving RVQoE measurements from the second network node.

Embodiment B3. The method of Embodiment B2, further comprising updating the request for RVQoE measurements based at least in part on the received RVQoE measurements.

Embodiment B4. The method of any of Embodiments B1-B3, wherein the request for RVQoE measurements includes a request to configure the at least one WD with measurements of available RVQoE metrics.

Embodiment B5. The method of any of Embodiments B1-B4, wherein the communication parameters include at least one of antenna system layer measurements, a mobility parameter, traffic load, and scheduling capability of the first network node.

Embodiment Cl. A second network node configured to communicate with a first network node, the first network node being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node being one of a centralized unit, CU, and a centralized unit-control plane CU-CP, the second network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive from the first network node a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD; and configure the at least one WD to perform RVQoE measurements according to the request. Embodiment C2. The second network node of Embodiment Cl, wherein configuring the at least one WD is performed only when corresponding QoE measurements are configured at the at least one WD.

Embodiment C3. The second network node of Embodiment C2, wherein configuring the at least one WD is based at least in part on a QoE configuration received by the second network node from an operations, administrative and management, 0AM, unit.

Embodiment C4. The second network node of any of Embodiments C1-C3, wherein configuring the at least one WD is based at least in part on at least one of a characteristic and a capability of the WD.

Embodiment C5. The second network node of any of Embodiments C1-C4, wherein the received request includes a configuration for configuring the at least one WD.

Embodiment DI . A method in a second network node configured to communicate with a first network node, the first network node being one of a distributed unit, DU, and a centralized unit-user plane, CU-UP, and the second network node being one of a centralized unit, CU, and a centralized unit-control plane CU-CP, the method comprising: receiving from the first network node a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD; and configuring the at least one WD to perform RVQoE measurements according to the request.

Embodiment D2. The method of Embodiment DI, wherein configuring the at least one WD is performed only when corresponding QoE measurements are configured at the at least one WD.

Embodiment D3. The method of Embodiment D2, wherein configuring the at least one WD is based at least in part on a QoE configuration received by the second network node from an operations, administrative and management, 0AM, unit.

Embodiment D4. The method of any of Embodiments D1-D3, wherein configuring the at least one WD is based at least in part on at least one of a characteristic and a capability of the WD.

Embodiment D5. The method of any of Embodiments D1-D4, wherein the received request includes a configuration for configuring the at least one WD. As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include:

3GPP 3^rd Generation Partnership Project

5G 5^th Generation

5GC 5G Core network

5GS 5^th Generation System AMF Access and Mobility Management Function

ASN.1 Abstract Syntax Notation One

AT Attention

AR Augmented Reality

AS Access Stratum

BAP Backhaul Adaptation Protocol

CGI Cell Global Identity

CN Core Network

CP Control Plane

CU Central Unit

CU-CP Central Unit Control Plane

CU-UP Central Unit User Plane

DU Distributed Unit

DASH Dynamic Adaptive Streaming over HTTP

DC Dual Connectivity

DL Downlink

DNS Domain Name System

DU Distributed Unit

E-CGI E-UTRAN CGI eNB Evolved Node B / E-UTRAN Node B en-gNB A gNB acting as a secondary node in an EN-DC scenario (i. . in a

DC scenario with an eNB as the master node and a gNB as the secondary node.

EN E-UTRAN-NR

EPC Evolved Packet Core

EPS Evolved Packet System

E-UTRA Evolved UTRA

E-UTRAN/

Evolved UTRAN gNB Radio base station in NR

HSS Home Subscriber Server

HTTP Hypertext Transfer Protocol

IAB Integrated Access and Backhaul

ID Identifier/Identity

IE Information Element LTE Long Term Evolution

MAC Medium Access Control

MCC Mobile Country Code

MCE Measurement Collection Entity / Measurement Collector Entity

MDT Minimization of Drive Tests

MME Mobility Management Entity

MNC Mobile Network Code

MTSI Multimedia Telephony Service for IMS

N3IWF Non-3GPP Interworking Function

NG Next Generation

NG The interface between an NG-RAN and a 5GC.

NGAP NG Application Protocol

NG-RAN NG Radio Access Network

NID Network identifier

NR New Radio

NWDAF Network Data Analytics Function

O&M Operation and Maintenance

0AM Operation and Maintenance

PDCP Packet Data Convergence Protocol

PDU Protocol Data Unit

PLMN Public Land Mobile Network

QMC QoE Measurement Collection

QoE Quality of Experience

QoS Quality of Service

RAN Radio Access Network

RAT Radio Access Technology

RLC Radio Link Control

RNC Radio Network Controller

RRC Radio Resource Control

RVQoE RAN Visible QoE

SI The interface between the RAN and the CN in LTE.

S1AP SI Application Protocol

S-NSSAI Single Network Slice Selection Assistance Information

SMO Service Management and Orchestration SRB Signaling Radio Bearer

TA Tracking Area

TCE Trace Collection Entity / Trace Collector Entity

TNGF Trusted Non-3GPP Gateway Function

TWIF Trusted WLAN Interworking Function

UDM Unified Data Management

UE User Equipment

UMTS Universal Mobile Telecommunication System

URI Uniform Resource Identifier

URL Uniform Resource Locator Uniform Resource Locator

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WD Wireless Device

WLAN Wireless Local Area Network

Xn The interface between two gNBs in NR.

XnAP Xn Application Protocol

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A method implemented in a first network node (16a) configured to communicate with a second network node (16b), the first network node (16a) being a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node (16b) being one of a centralized unit, CU, or a centralized unit-control plane CU-CP, the method comprising: determining (SI 34) whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements; and sending (S136) to the second network node (16b) a request for RVQoE measurements for at least one wireless device, WD (22), based at least in part on the collection determination.

2. The method of Claim 1, further comprising updating the request for RVQoE measurements based at least in part on the received RVQoE measurements.

3. The method of any of Claims 1 and 2, wherein the request for RVQoE measurements includes a request to configure the at least one WD (22) with measurements of available RVQoE metrics.

4. The method of any of Claims 1-3, wherein the collection determination is based at least in part on at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node (16a).

5. The method of any of Claims 1-4, further comprising configuring an application layer of the WD (22) to perform application layer measurements.

6. The method of any of Claims 1-5, further comprising determining at least one of an RVQoE metric to be measured, a duration of an RVQoE measurement and a periodicity for sending RVQoE reports.

7. The method of any of Claims 1-6, further comprising identifying a group of WDs for RVQoE measurements based at least in part on at least one of whether a WD (22) is in multi-broadcast session, whether a WD (22) is in a particular paging group and whether a WD (22) is in a particular tracking area.

8. The method of any of Claims 1-7, further comprising sending to the second network node (16b) at least one of an RVQoE configuration and a list of RVQoE reporting periodicities.

9. The method of any of Claims 1-8, further comprising sending an RVQoE configuration to the WD (22).

10. A method in a second network node (16b) configured to communicate with a first network node (16a), the first network node (16a) being a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node (16b) being a centralized unit, CU, or a centralized unit-control plane CU-CP, the method comprising: receiving (SI 38) from the first network node (16a) a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD (22); and configuring (S140) the at least one WD (22) to perform RVQoE measurements according to the request.

11. The method of Claim 10, wherein configuring the at least one WD (22) is based at least in part on a QoE configuration received by the second network node (16b) from another network node (16).

12. The method of any of Claims 10 and 11, wherein configuring the at least one WD (22) is based at least in part on at least one of a characteristic and a capability of the WD (22).

13. The method of any of Claims 10-12, wherein the received request includes an RVQoE configuration for configuring the at least one WD (22).

14. A first network node (16a) configured to communicate with a second network node (16b), the first network node (16a) being a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node (16b) being a centralized unit, CU, or a centralized unit-control plane CU-CP, the first network node (16a) configured to: determine whether to collect radio access network, RAN, visible quality of experience, RVQoE, measurements; and send to the second network node (16b) a request for RVQoE measurements for at least one wireless device, WD (22), based at least in part on the collection determination.

15. The first network node (16a) of Claim 14, wherein the first network node (16a) is configured to update the request for RVQoE measurements based at least in part on the received RVQoE measurements.

16. The first network node (16a) of any of Claims 14 and 15, wherein the request for RVQoE measurements includes a request to configure the at least one WD (22) with measurements of available RVQoE metrics.

17. The first network node (16a) of any of Claims 14-16, wherein the collection determination is based at least in part on at least one of access stratum, AS, measurements, a mobility parameter, traffic load, and scheduling capability of the first network node (16a).

18. The first network node (16a) of any of Claims 14-17, wherein the first network node (16a) is configured to configure an application layer of the WD (22) to perform application layer measurements.

19. The first network node (16a) of any of Claims 14-18, wherein the first network node (16a) is configured to determine at least one of an RVQoE metric to be measured, a duration of an RVQoE measurement and a periodicity for sending RVQoE reports.

20. The first network node (16a) of any of Claims 14-19, wherein the first network node (16a) is configured to identify a group of WDs for RVQoE measurements based at least in part on at least one of whether a WD (22) is in multi-broadcast session, whether a WD (22) is in a particular paging group and whether a WD (22) is in a particular tracking area.

21. The first network node (16a) of any of Claims 14-20, wherein the first network node (16a) is configured to send to the second network node (16b) at least one of an RVQoE configuration and a list of RVQoE reporting periodicities.

22. The first network node (16a) of any of Claims 14-21, wherein the first network node (16a) is configured to send an RVQoE configuration to the WD (22).

23. A second network node (16b) configured to communicate with a first network node (16a), the first network node (16a) being a distributed unit, DU, or a centralized unit-user plane, CU-UP, and the second network node (16b) being a centralized unit, CU, or a centralized unit-control plane CU-CP, the second network node (16b) configured to: receive from the first network node (16a) a request for radio access network, RAN, visible quality of experience, RVQoE measurements for at least one wireless device, WD (22); and configure the at least one WD (22) to perform RVQoE measurements according to the request.

24. The second network node (16b) of Claim 23, wherein configuring the at least one WD (22) is based at least in part on a QoE configuration received by the second network node (16b) from another network node (16).

25. The second network node (16b) of any of Claims 23 and 24, wherein configuring the at least one WD (22) is based at least in part on at least one of a characteristic and a capability of the WD (22).

26. The second network node (16b) of any of Claims 23-25, wherein the received request includes an RVQoE configuration for configuring the at least one WD (22).

27. A network node (16) comprising processing circuitry (68) and a radio interface (62) configured to perform a method according to any one of Claims 1-13.

28. A computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of Claims 1-13.

29. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-13.