Node-to-node cooperation for reporting visible quality of experience across radio access networks in dual connectivity

Abstract

A method, system, and apparatus are disclosed. A method is described in a first network node configured to communicate with a user equipment (UE) and a second network node. At least the UE is configurable to communicate using multi-radio connectivity with the first network node and the second network node. The method includes coordinating with the second network node to determine which of the first network node and the second network node has a report corresponding to a service type associated with the UE. Furthermore, the method includes determining which of the first network node and the second network node carries data for an application session that is subject to a quality of experience measurement associated with the report, and performing one or more actions to ensure that one of the first network node and the second network node carrying the data obtains the report.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communications, and more particularly to inter-node coordination for reporting in a multi-node connectivity environment. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for fourth-generation (4G) wireless communication systems (also called Long Term Evolution (LTE)) and fifth-generation (5G) wireless communication systems (also called New Radio (NR)). Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipment (UE) (sometimes called wireless devices (WDs)), as well as communication between network nodes and between UEs. 3GPP is also developing standards for sixth-generation (6G) wireless communication systems.

[0003] Furthermore, wireless communication systems, such as 5G and 6G systems, may comprise at least one Radio Access Network (RAN) and / or one or more RAN network nodes. Figure 1 shows an example overall architecture of a Next Generation RAN (NG-RAN). The NG-RAN includes a set of gNBs (i.e., network nodes) connected to a 5G Core (5GC) through an NG interface.

[0004] Note: The NG-RAN may also include a set of next-generation eNodeBs (ng-eNBs), for example, as specified in 3GPP Technical Specification (TS) 38.300 v17.1.0. The ng-eNB may include an ng-eNB centralized unit (NG-eNB-CU) and one or more ng-eNB distributed units (ng-eNB-DU(s)). The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface. Also, the general principles described herein may apply to the ng-eNB and W1 interface, for example, unless explicitly specified otherwise. The gNBs may support frequency division duplex (FDD) mode, time division duplex (TDD) mode, or dual-mode operation. Furthermore, the gNBs may be interconnected through an Xn interface.

[0005] A gNB may also include a gNB-CU and one or more gNB-DUs. The gNB-CU and gNB-DUs may be connected via an F1 interface. One gNB-DU may be connected to one gNB-CU.

[0006] NOTE: In case of network sharing with multiple cell ID broadcast, each cell identity associated with a subset of PLMNs corresponds to a gNB-DU and a gNB-CU to which the gNB-DU is connected, i.e., the corresponding gNB-DUs share the same physical layer cell resources.

[0007] Note: For resiliency, a gNB-DU may be connected to multiple gNB-CUs with appropriate implementation.

[0008] NG, Xn and F1 can be logical interfaces In the case of NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and a gNB-DU terminate at the gNB-CU. In the case of dual connectivity between E-UTRA and NR (EN-DC), the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and a gNB-DU terminate at the gNB-CU. The gNB-CU and connected gNB-DU are visible, e.g., only visible as a gNB to other gNBs and 5GC.

[0009] The node hosting the user plane portion of the NR PDCP (e.g., the gNB-CU, gNB-CU user plane (UP), and in the case of EN-DC, the master eNB (MeNB) or secondary gNB (SgNB) depending on bearer splitting) may perform user inactivity monitoring and further inform the node having the C-plane connection towards the core network (e.g., over E1, X2) of the inactivity or (re)activation. The node hosting the NR RLC (e.g., the gNB-DU) may perform user inactivity monitoring and further inform the node hosting the control plane, e.g., the gNB-CU or gNB-CU control plane (CP), of the inactivity or (re)activation.

[0010] Uplink (UL) Packet Data Control Protocol (PDCP) configuration (i.e., how the UE uses the UL at the supporting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN), and F1-C. Radio link suspension / resumption for downlink (DL) and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN), and F1-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 the interfaces between the NG-RAN logical nodes, are specified as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant Transport Network Layer (TNL) protocols and functions are specified. The TNL provides services for user plane transport and signaling transport.

[0011] In an NG-Flex configuration, each NG-RAN node may be connected to all Access and Mobility Functions (AMFs) of an AMF set within an AMF area that supports at least one slice also supported by the NG-RAN node. The AMF set and AMF area may be those specified in 3GPP TS 23.501 v17.5.0. If security protection for control plane and user plane data on the TNL of the NG-RAN interface must be supported, Network Domain Security / Internet Protocol (NDS / IP) 3GPP TS 33.501 v17.6.0 may be applied.

[0012] Overall architecture for separation of gNB-CU-CP and gNB-CU-UP The overall architecture for the separation of the gNB-CU-CP and gNB-CU-UP is shown in the example of Figure 2 and may be the overall architecture specified in 3GPP TS37.483. As described above, a gNB 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 an F1-C interface. The gNB-CU-UPs are connected to the gNB-DU through an F1-U interface. The gNB-CU-UPs are connected to the gNB-CU-CP through an E1 interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP.

[0013] NOTE 1: For resiliency purposes, a gNB-DU and / or gNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation.

[0014] One gNB-DU may be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP, and one gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP.

[0015] NOTE 2: Connectivity between the gNB-CU-UP and the gNB-DU is established by the gNB-CU-CP using the Bearer Context Management Function.

[0016] NOTE 3: The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested service for the UE. In case of multiple CU-UPs, they belong to the same security domain as specified in 3GPP TS33.210 v17.0.0.

[0017] NOTE 4: Data forwarding between gNB-CU-UP during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

[0018] Dual Connectivity In dual connectivity (DC), a multiple transmit / receive capable UE can be connected to two or more RAN nodes. These RAN nodes can be of the same radio access technology (RAT) (both master and secondary nodes in NR or LTE, respectively) or of different RATs, e.g., one master LTE node and one secondary NR node. Specification 3GPP TS37.340 v17.1.0 describes the principles of multi-radio dual connectivity. ==============Beginning of excerpt from 3GPP TS37.340============== general General MR-DC principle Multi-Radio Dual Connectivity (MR-DC) is a generalization of intra-E-UTRA Dual Connectivity (DC) described in 3GPP TS36.300, in which a multiple Rx / Tx capable UE can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul: one providing NR access and the other providing either E-UTRA or NR access. One node acts as a Master Node (MN) and the other as a Secondary Node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. The MN and / or SN may be operated with shared spectrum channel access. All functions specified for the UE may be used for the IAB-MT unless otherwise stated. As specified for the UE, the IAB-MT can access the network either using one network node or using two different nodes with the EN-DC and NR-DC architectures. In the EN-DC, backhaul traffic over the E-UTRA air interface is not supported. Note 1: MR-DC is designed based on the assumption of non-ideal backhaul between different nodes, but can also be used in the case of ideal backhaul. NOTE 2: All MR-DC normative text and procedures in this version of the specification refer to the case of aggregated nodes. Details regarding non-aggregated nodes for MR-DC operation are described in 3GPP TS 38.401. MR-DC with EPC E-UTRAN supports MR-DC via E-UTRA-NR dual connectivity (EN-DC), in which a UE is connected to one eNB acting as a MN and one en-gNB acting as a SN. An eNB is connected to the EPC via an S1 interface and to an en-gNB via an X2 interface. An en-gNB may also be connected to the EPC via an S1-U interface and to other en-gNBs via an X2-U interface. An exemplary EN-DC overall architecture is shown in Figure 3. 5GC and MR-DC E-UTRA-NR Dual Connectivity NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), where a UE is connected to one ng-eNB acting as a MN and one gNB acting as a SN. NR-E-UTRA Dual Connectivity The NG-RAN supports NR-E-UTRA dual connectivity (NE-DC), where a UE is connected to one gNB acting as an MN and one ng-eNB acting as an SN. NR-NR dual connectivity NG-RAN supports NR-NR dual connectivity (NR-DC), where a UE is connected to one gNB acting as a MN and another gNB acting as a SN. Additionally, NR-DC can also be used when a UE is connected to two gNB-DUs, one serving an MCG and the other serving an SCG, that are connected to the same gNB-CU and act as both an MN and an SN. ============== End of excerpt from 3GPP TS37.340 ==============

[0019] The flow or flows for setting up dual connectivity may be the flow described in Chapter 10 of 3GPP TS37.340, shown in FIG. 4, ie, Second Node Addition Procedure.

[0020] Overview of QoE framework "Normal" QoE Quality of Experience (QoE) measurements, also called "application layer measurements," are specified for LTE and UMTS and are being specified for NR in 3GPP Release 17 (Rel-17). The purpose of application layer measurements is to measure the end-user experience when using several applications. Currently, QoE measurements are supported for streaming services and for mobility telephony service for internet protocol based media systems (MTSI) services. For NR, at least VR may be added to the list of services for which QoE measurements are specified and supported.

[0021] The solutions in LTE and UMTS have similar overall principles: Quality of Experience Measurement Collection (QMC) enables the configuration of application layer measurements in the UE and the transmission of QoE measurement result files (commonly called QoE reports) to the network via RRC signaling; Application layer measurement configurations (also called QoE measurement configurations or QoE settings) received by the RAN from the Operation and Maintenance (OAM) system or CN are encapsulated in transparent containers, which are forwarded to the UE in downlink Radio Resource Control (RRC) messages; Application layer measurement reports (also called QoE reports) received by the UE Access Stratum (UE AS) layer or the UE RRC layer from upper layers (application layers) of the UE are encapsulated in transparent containers and sent to the network in uplink RRC messages; The RAN then forwards the QoE reports to a Measurement Collector Entity (MCE).

[0022] In 3GPP Rel-17, a new research item for NR titled "Study on NR QoE Management and Optimization for Diverse Services" was initiated. The specification work for 3GPP Rel-17 is still ongoing. The purpose of the research item is to study solutions for QoE measurement in NR. QoE management in NR will not only collect quality of experience parameters for streaming services, but also consider the general performance requirements of various services (e.g., Augmented Reality / Virtual Reality (AR / VR) and Ultra-Reliable and Low Latency Communications (URLLC), of which at least VR is expected to be covered in 3GPP Rel-17). Based on service requirements, the NR research also included a more adaptive QoE management scheme that enables network optimization to satisfy user experience for various services.

[0023] The configuration data related to QoE measurements (commonly referred to in the standard as application layer measurements) consists of a service type indication, an indication of the area where the measurements should be performed (denoted as area scope), the IP address of the entity (often called MCE, spelled Measurement Collector Entity or Measurement Collection Entity, but the entity may also be called Trace Collection Entity) to which the collected measurement results (i.e., QoE reports) should be sent, and a set of instructions on what type of measurements should be performed and details on how these measurements should be performed. These instructions are targeted to the UE, e.g., the application layer in the WD, and are placed in a "container" that the network entities handling the instructions, e.g., forwarding the instructions to the UE, and the UE Access Stratum, cannot interpret and do not attempt to read. The currently specified service type is MTSI and Streaming Service (DASH), and at least the service type VR will be added in 3GPP Rel-17. The area scope is specified in terms of cells or network-related areas. In UMTS, the area scope is specified as either a list of cells, a list of routing areas, or a list of tracking areas. In LTE, the area range is defined as either a list of cells or a list of tracking areas. In NR, the area range will be defined as either a list of cells or a list of tracking areas.

[0024] QoE, and in particular QoE configuration, comes in two flavors: management-based QoE configuration and signaling-based QoE configuration. In both cases, QoE configuration occurs in the OAM system or some other management entity that deals with, for example, customer satisfaction. All of these entities are referred to herein as OAM systems (although the OAM system also includes further entities). In the case of management-based QoE (m-based QoE), the OAM system is generally interested in general QoE statistics from a certain area (configured as an area range). The m-based QoE configuration is sent directly from the OAM system to the RAN nodes that control cells within the area range. Each RAN node then selects UEs that are within its area range (and that meet any other relevant conditions, such as supporting the application / service type in question) and sends the m-based QoE configuration to these UEs.

[0025] In the case of signaling-based QoE (s-based QoE), the OAM system is interested in collecting QoE measurements from a particular UE, for example, because the user of that UE has complained. The OAM system sends the s-based QoE configuration to the HSS (in EPS / LTE) or UDM (in 5GS / NR), which forwards the QoE configuration to the UE's current core network node (CN), for example, the MME in EPS / LTE or the AMF in 5G / NR. The CN then forwards the s-based QoE configuration to the RAN node serving that UE, and the RAN forwards the s-based QoE configuration to the UE.

[0026] The service type indication and a container with the measurement command are forwarded to the UE. The UE is unaware of whether the received QoE setting is m-based or s-based. In legacy systems, the QoE framework is integrated with the trace function, and a trace ID is associated with each QoE setting. In NR, the QoE function will be logically separated from the trace function, but it will still partially reuse the trace signaling mechanism. In NR and LTE, a globally unique QoE reference (formed from the Mobile Country Code (MCC) + Mobile Network Code (MNC) + QMC ID, where the QMC ID is a 24-bit string) will be associated with each QoE setting. The QoE reference is included in the container with the measurement command and is also sent to the RAN (i.e., the gNB in ​​NR). For communication between a gNB and a UE, the QoE reference is replaced by a shorter identifier, denoted as measConfigAppLayerId, which is locally unique within the UE (i.e., there is a one-to-one mapping between measConfigAppLayerId and QoE reference for each QoE configuration provided to the UE). The measConfigAppLayerId is stored in the UE access layer and is also forwarded in AT commands (which are the type of commands used in communication between the modem part of the UE and the application layer of the UE) together with a container with a service type indication and a measurement command.

[0027] Reports with collected QoE measurement results (QoE reports) are sent from the UE application layer to the UE access stratum, which forwards them to the RAN, which forwards them to the MCE. These QoE measurement results are placed in a "container," which is not interpretable by the UE access stratum and the RAN. QoE reports can be configured to be sent periodically or only at the end of an application session. Furthermore, the RAN can instruct the UE to pause QoE reporting, for example, if the cell / gNB is overloaded.

[0028] The RAN is not aware when an application session with an associated QoE measurement session is ongoing, and the UE access stratum is not automatically aware of this either. A relaxation of this session start / stop indication, which would be sent from the application layer in the UE to the UE AS and from the UE AS to the RAN, can be introduced. The session stop indication can be implicit in the form of a QoE report sent when the application session and the associated QoE measurement session are terminated.

[0029] The RAN may decide to release the QoE settings in the UE at any time as an implementation-based decision, typically when the UE moves outside the area configured for QoE measurements, commonly called the area range.

[0030] One opportunity offered by legacy solutions is the possibility to keep QoE measurements for the entire session even during handover situations, and it is discussed that the UE continues to measure QoE for an ongoing application session until the application session is terminated, even if the UE moves outside the configured coverage area in the meantime.

[0031] RAN Visible QoE (RVQoE) In NR, 3GPP Rel-17 introduced RAN-visible QoE measurements. A general description can be found in 3GPP TS38.300 v17.0.0 clause 21.4.

[0032] RAN visible QoE measurements are configured by the NG-RAN node, where a subset of QoE metrics are reported from the UE as explicit information elements (IEs) readable by the NG-RAN node. RAN visible QoE measurements (e.g., RAN visible QoE metrics, RAN visible QoE values) can be utilized by the NG-RAN node for network optimization. RAN visible QoE measurements are supported for DASH streaming services and VR services. The NG-RAN node configures the RAN visible QoE measurements to collect all or a portion of the available RAN visible QoE metrics, where an indication of metric availability is received from the OAM or CN. The set of available RAN visible QoE metrics is a subset of the metrics already configured as part of the QoE measurement configuration, encapsulated in a transparent container. Packet data unit (PDU) session ID(s) corresponding to the service(s) subject to QoE measurements may also be reported by the UE along with the RAN visible QoE measurement results.

[0033] A request to collect QoE measurements that are not visible to the RAN (also called OAM-QoE in R3-223290) is initiated from the OAM and is identified by a QoE reference. The specification for this identifier can be found, for example, in 3GPP TS28.405 v17.1.0, clause 5.2. o The QoE Reference parameter specifies the network request session. The QoE Reference shall be globally unique, and therefore the QoE Reference is constructed as follows: ■ MCC+MNC+QMC ID, where MCC and MNC accompany the 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 operator. ■ QMC ID is used to identify the QoE measurement collection job at the traffic node and at the measurement collection center.

[0034] The UE AS layer can report RAN visible QoE measurements to the gNB in ​​RRC format, and the UE application layer can be configured to perform more application layer measurements simultaneously (up to 16 in NR Rel-17); for example, in 3GPP TS38.331, application layer measurements are identified by the MeasConfigAppLayerId IE.

[0035] In the gNB, the RAN visible QoE information may be transferred from the gNB-CU to the gNB-DU in the procedure described in 3GPP TS38.473 v17.0.0, which is UE-related, i.e., the procedure is specific for the UE.

[0036] 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 UE-related signaling. Figure 5 shows the QoE Transfer procedure. The gNB-CU initiates the procedure by sending a QoE Information Transfer message to the gNB-DU. If a QoE Information List IE is included in the QoE Information Transfer message, the gNB-DU may take the QoE Information List IE into account in accordance with 3GPP TS38.300.

[0037] A message is sent by the gNB-CU to the gNB-DU to indicate information related to RAN visible QoE. Direction: gNB-CU → gNB-DU. Figure 6 shows two tables containing parameters related to QoE information transfer.

[0038] QoE Metrics Figure 7 shows typical QoE metrics. The IE provides RAN-visible QoE measurement reports to the gNB-DU.

[0039] In contribution document R3-223128 to 3GPP TSG-RAN WG3 meeting #116-e, the association of RAN visible QoE reports to references was discussed. In the F1 AP, a list containing the currently agreed RVQoE metrics is transferred over F1 using UE-related signaling. However, the reports are not associated with, for example, any reference or other ID. Therefore, the gNB-DU will not know how many different application sessions provide reports, and therefore the currently specified signaling will not allow the gNB-DU to distinguish between QoE reports coming from different application sessions. Also, the gNB-DU will not be able to group reports that it receives consecutively from a given application session, and therefore will not be able to track trends in the reported data, for example. Candidate references or other IDs that can solve this problem will generally be the QoE Reference or short RRC id (measConfigAppLayerId) assigned by the UE. The F1AP CR submitted to this meeting in R3-223131 proposes to use the QoE Reference, but the final selection may be subject to further evaluation.

[0040] In the same contribution, the following proposals are made following the reported discussions. Proposal 3: RAN3 to discuss and agree on using QoE reference or short RRC id (measConfigAppLayerId) to identify RVQoE reporting information over F1.

[0041] Signaling Radio Bearer (SRB) Signaling radio bearers are configured in the UE for the transmission of control plane messages to and from the UE. In the current specification, five different SRBs can be configured: SRB0 is used for the initial RRC setup before security is activated; SRB1 is used for most RRC messages and SRB2 is used for NAS messages.

[0042] When a UE is configured with dual connectivity (DC), SRB1 is used to communicate with a master node (MN). In addition, in DC, the UE may be configured with SRB3, which is used for direct communication between the UE and a secondary node (SN).

[0043] A dedicated SRB4 is specified for transmitting QoE and RVQoE reports. In Rel-17, SRB4 is used only for transmitting QoE and RVQoE reports in the RRC message MeasurementReportAppLayer to the master node.

[0044] In management-based (m-based) QoE and RVQoE measurement collection, a possible scenario is that both nodes (e.g., MN and SN) serving a UE in NR dual connectivity (NR-DC) will be in the group of RAN nodes that receive the same management-based (m-based) QoE measurement configuration, e.g., because both MN and SN will be in the coverage area of ​​the m-based configuration. Based on the information received with this QoE configuration, the RAN nodes (MN and / or SN) may configure the UE to also perform RVQoE measurements for the same application session.

[0045] In management-based (m-based) QoE and RVQoE measurement collection, a possible scenario is that both nodes (e.g., MN and SN) serving a UE in NR dual connectivity (NR-DC) will be in the group of RAN nodes that receive the same management-based (m-based) QoE measurement configuration, e.g., because both MN and SN will be in the coverage area of ​​the m-based configuration. Based on the information received with this QoE configuration, the RAN nodes (MN and / or SN) may configure the UE to also perform RVQoE measurements for the same application session.

[0046] According to the 3GPP specifications, the UE delivers QoE and RVQoE reports to the network by using SRB4. In that regard, the UE can establish only one SRB of a certain type, which means that the UE cannot establish SRB4 for both nodes serving the UE. Furthermore, a possible scenario is that the application session subject to QoE and RVQoE measurements is carried to a dual-connected UE only via one leg, where the RAN does not know (or at least does not know in advance) which bearer maps to which application session and therefore has no control or direct knowledge of which leg carries this application session. Therefore, the corresponding RVQoE report will only be useful for one of the two RAN nodes serving the UE (the RAN node that carries data about the application session to the UE), and the RVQoE report will be useless for the other RAN node serving the UE, even if this RAN node is the RAN node that configured the UE with the RVQoE measurements.

[0047] In other words, it is unclear how to ensure that the "correct" RAN node (of the two serving the UE in NR-DC) receives the RVQoE report. Note that even if a UE in NR-DC were to be allowed to establish SRB4s towards both RAN nodes serving that UE, problems would exist.

[0048] Furthermore, the RAN node may configure an RVQoE measurement on a UE only if a corresponding QoE measurement is simultaneously configured on the UE, which effectively means that the RAN node may configure an RVQoE measurement on a UE only if the OAM approves it.

[0049] Another aspect to consider is that even if the UE may have only one SRB4 configured, the UE may have received multiple RVQoE configurations corresponding to different service types from different RAN nodes (e.g., the UE receives a first RVQoE configuration for service type 1 from a first node and (later) a second RVQoE configuration for service type 2 from a second node). It is also unclear how to ensure that each node receives the RVQoE report related to the service type(s) for which it issued a corresponding RVQoE configuration to the UE (in this example, how to ensure that the first node receives the RVQoE report related to service type 1 and the second node receives the RVQoE report related to service type 2). Summary of the Invention

[0050] Some embodiments advantageously provide methods, systems, and apparatus for inter-node coordination for reporting in a multi-node connectivity environment. In some embodiments, a mechanism (i.e., a method) is described that enables RAN nodes (i.e., network nodes) serving UEs in an NR-DC or any other multi-radio connectivity setup to coordinate and at least one of: inform each other regarding which of them have configured RVQoE measurements for a particular service type; identify which of them carry data application sessions that are subject to RVQoE measurements related to the particular service type; and forward corresponding RVQoE reports to nodes that carry data for the application sessions that are subject to RVQoE measurements.

[0051] In some other embodiments, the UE is configured to send one or more reports to relevant nodes (i.e., network nodes) or for the UE to indicate which nodes the RVQoE should target. A mechanism is described for a RAN node to obtain UE capabilities (with respect to the solution proposed in this invention).

[0052] In a UE in NR-DC, one or more embodiments ensure that RVQoE reports related to a certain service type are forwarded to the correct location, i.e., to the RAN node that can utilize the report, the node that delivers data to the UE about the application session that is subject to the RVQoE measurement.

[0053] In some embodiments, the UE in the DC and the RAN node are configured to infer which of the serving RAN nodes carries data for the application session that is subject to RVQoE measurement, which allows, for example, forwarding the RVQoE report to the correct node.

[0054] According to one aspect, a method is described in a first network node configured to communicate with a user equipment (UE) and a second network node. The UE is configurable to communicate using multi-radio connectivity with at least the first network node and the second network node. The method includes coordinating with the second network node to determine which of the first network node and the second network node has a report corresponding to a service type associated with the UE, determining which of the first network node and the second network node carries data for an application session subject to a quality of experience measurement associated with the report, and performing one or more actions to ensure that one of the first network node and the second network node carrying the data obtains the report.

[0055] In some embodiments, the coordination includes sending a first indication to the second network node indicating that the first network node has received the report from the UE, or receiving a second indication from the second network node indicating that the second network node has received the report from the UE.

[0056] In some other embodiments, the report includes one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID. Determining which of the first network node and the second network node carry data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0057] In some embodiments, the method further includes receiving a report from the UE.

[0058] In some other embodiments, performing the one or more actions includes transmitting a report to the second network node when the second network node carries data for the application session, the transmitted report being usable by the second network node to transmit and / or receive signaling to and from the UE related to the service type.

[0059] In some embodiments, performing the one or more actions includes receiving a report from the second network node when the first network node carries data about the application session, the received report being usable by the first network node to send and / or receive signaling to and from the UE related to the service type.

[0060] In some other embodiments, the method further includes causing the UE to be configured to one or both of: send a report to at least one of the first network node and the second network node; and indicate which of the first network node and the second network node the quality of experience is targeted to.

[0061] In some embodiments, the first network node and the second network node are Radio Access Network (RAN) nodes, and the quality of experience measurement is one or both of a Quality of Experience (QoE) measurement and a RAN Visible Quality of Experience (RVQoE) measurement.

[0062] In some other embodiments, the report includes one or more of a Quality of Experience (QoE) report and a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

[0063] In some embodiments, the method further includes receiving a capability indication from the UE indicating one of the first network node and the second network node that carries the application session.

[0064] According to another aspect, a first network node configured to communicate with a user equipment (UE) and a second network node is described. The UE is configurable to communicate using multi-radio connectivity with at least the first network node and the second network node. The first network node is configured to: coordinate with the second network node to determine which of the first network node and the second network node has a report corresponding to a service type associated with the UE; determine which of the first network node and the second network node carries data for an application session subject to a quality of experience measurement associated with the report; and perform one or more actions to ensure that one of the first network node and the second network node carrying the data obtains the report.

[0065] In some embodiments, the coordination includes sending a first indication to the second network node indicating that the first network node has received the report from the UE, or receiving a second indication from the second network node indicating that the second network node has received the report from the UE.

[0066] In some other embodiments, the report includes one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID. Determining which of the first network node and the second network node carry data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0067] In some embodiments, the first network node is further configured to receive a report from the UE.

[0068] In some other embodiments, performing the one or more actions includes transmitting a report to the second network node when the second network node carries data for the application session, the transmitted report being usable by the second network node to transmit and / or receive signaling to and from the UE related to the service type.

[0069] In some embodiments, performing the one or more actions includes receiving a report from the second network node when the first network node carries data about the application session, the received report being usable by the first network node to send and / or receive signaling to and from the UE related to the service type.

[0070] In some other embodiments, the first network node is further configured to cause the UE to be configured to one or both of: send a report to at least one of the first network node and the second network node; and indicate which of the first network node and the second network node the quality of experience is targeted to.

[0071] In some embodiments, the first network node and the second network node are Radio Access Network (RAN) nodes, and the quality of experience measurement is one or both of a Quality of Experience (QoE) measurement and a RAN Visible Quality of Experience (RVQoE) measurement.

[0072] In some other embodiments, the report includes one or more of a Quality of Experience (QoE) report and a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

[0073] In some embodiments, the first network node is further configured to receive a capability indication from the UE indicating one of the first network node and the second network node that carries the application session.

[0074] According to one aspect, a method is described in a user equipment (UE) configured to communicate using multi-radio connectivity with a first network node and a second network node. The method includes transmitting a report corresponding to a service type associated with the UE to one of the first network node and the second network node. The report includes one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID. Which of the first network node and the second network node carries data for the application session is determined based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0075] In some embodiments, the method further includes determining a capability indication usable by one or both of the first network node and the second network node to determine which of the first network node and the second network node carries data for an application session that is subject to a quality of experience measurement associated with the report, and performing one or more actions to ensure that the one of the first network node and the second network node that carries the data obtains the report. The method further includes transmitting the capability indication to one or both of the first network node and the second network node.

[0076] In some other embodiments, when the report is transmitted to the first network node, the one or more actions include transmitting, by the first network node, a report to the second network node when the second network node carries data about the application session, the transmitted report being usable by the second network node to transmit and / or receive signaling to and from the UE related to the service type.

[0077] In some embodiments, the one or more actions include receiving, by the first network node, a report from the second network node when the first network node carries data for the application session, the received report usable by the first network node to send and / or receive signaling to and from the UE related to the service type.

[0078] In some other embodiments, the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a radio access network (RAN) visible quality of experience (RVQoE) measurement.

[0079] In some embodiments, the method further includes indicating whether the quality of experience is targeted to the first network node or the second network node.

[0080] In some other embodiments, the first network node 16a and the second network node 16b are radio access network (RAN) nodes.

[0081] In some embodiments, the report comprises a Quality of Experience (QoE) report.

[0082] In some other embodiments, the report includes a Radio Access Network (RAN) Visual Quality of Experience (RVQoE) report.

[0083] In some embodiments, the method further includes determining the reporting based on one or both of the first configuration and the second configuration received from one or both of the first network node and the second network node.

[0084] According to another aspect, a user equipment (UE) configured to communicate using multi-radio connectivity with a first network node and a second network node is configured to cause transmission of a report corresponding to a service type associated with the UE to one of the first network node and the second network node. The report includes one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID. Which of the first network node and the second network node carries data for the application session is determined based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0085] In some embodiments, the UE is further configured to determine capability indications usable by one or both of the first network node and the second network node to determine which of the first network node and the second network node carries data for an application session that is subject to a quality of experience measurement associated with the report, and to perform one or more actions to ensure that the one of the first network node and the second network node that carries the data obtains the report. The UE is further configured to cause transmission of the capability indications to one or both of the first network node and the second network node.

[0086] In some other embodiments, when the report is transmitted to the first network node, the one or more actions include transmitting, by the first network node, a report to the second network node when the second network node carries data about the application session, the transmitted report being usable by the second network node to transmit and / or receive signaling to and from the UE related to the service type.

[0087] In some embodiments, the one or more actions include receiving, by the first network node, a report from the second network node when the first network node carries data for the application session, the received report usable by the first network node to send and / or receive signaling to and from the UE related to the service type.

[0088] In some other embodiments, the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a radio access network (RAN) visible quality of experience (RVQoE) measurement.

[0089] In some embodiments, the UE is further configured to indicate whether the quality of experience is targeted to the first network node or the second network node.

[0090] In some other embodiments, the first network node (16a) and the second network node (16b) are radio access network (RAN) nodes.

[0091] In some embodiments, the report comprises a Quality of Experience (QoE) report.

[0092] In some other embodiments, the report includes a Radio Access Network (RAN) Visual Quality of Experience (RVQoE) report.

[0093] In some embodiments, the UE is further configured to determine the reporting based on one or both of a first configuration and a second configuration received from one or both of the first network node and the second network node.

[0094] A more complete understanding of the present embodiments, and their attendant advantages and features, will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which: [Brief explanation of the drawings]

[0095] [Figure 1] FIG. 1 illustrates the overall architecture of NG-RAN. [Figure 2] FIG. 1 illustrates the overall architecture for separation of gNB-CU-CP and gNB-CU-UP. [Figure 3] FIG. 1 illustrates the EN-DC overall architecture. [Figure 4] FIG. 10 illustrates a procedure for adding a second node. [Figure 5] FIG. 1 illustrates a QoE transfer procedure. [Figure 6] FIG. 2 shows two tables containing parameters related to QoE information transfer. [Figure 7] FIG. 1 illustrates common QoE metrics. [Figure 8] 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer through an intermediate network in accordance with principles of the present disclosure; [Figure 9] FIG. 1 is a block diagram of a host computer communicating with user equipment via a network node over at least a partially wireless connection, according to some embodiments of the present disclosure. [Figure 10]1 is a flowchart illustrating an exemplary method implemented in a communication system including a host computer, a network node, and user equipment for executing a client application on user equipment, according to some embodiments of the present disclosure. [Figure 11] 1 is a flowchart illustrating an example method implemented in a communication system including a host computer, a network node, and a UE for receiving user data at a user equipment, in accordance with some embodiments of the present disclosure. [Figure 12] 1 is a flowchart illustrating an exemplary method implemented in a communications system including a host computer, a network node, and user equipment for receiving user data at a host computer from user equipment, in accordance with some embodiments of the present disclosure. [Figure 13] 1 is a flowchart illustrating an exemplary method implemented in a communications system including a host computer, a network node, and user equipment for receiving user data at a host computer, in accordance with some embodiments of the present disclosure. [Figure 14] 1 is a flowchart of an example process in a network node, in accordance with some embodiments of the present disclosure. [Figure 15] 1 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure. [Figure 16] 10 is a flowchart of another example process in a network node, in accordance with some embodiments of the present disclosure. [Figure 17] 10 is a flowchart of another example process in user equipment, according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0096] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in a combination of apparatus components and processing steps related to, for example, inter-node coordination for reporting in a multi-node connectivity environment. Accordingly, where appropriate, components are represented in the drawings by conventional symbols and only those specific details relevant to understanding the embodiments are shown, so as not to obscure the present disclosure with details that will be readily apparent to those skilled in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0097] As used herein, relational terms such as “first” and “second,” “upper” and “lower,” etc., may be used merely to distinguish one entity or element from another, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is merely for the purpose of describing particular embodiments and is not intended to limit the concepts described herein. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly dictates otherwise. Furthermore, as used herein, the terms “comprises,” “comprising,” “includes,” and / or “including” will be understood to specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0098] In the embodiments described herein, joining terms such as "in communication with" may be used to indicate electrical or data communication that may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations are possible in achieving electrical and data communication.

[0099] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, although not necessarily a direct connection, and may include a wired and / or wireless connection.

[0100] The term "network node" as used herein may be any kind of network node (and / or nodes) provided in a wireless network, which may further comprise any of a base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gNodeB (gNB), evolved node B (eNB or eNodeB), Node B, MSR radio node such as a multi-standard radio (MSR) BS, multi-cell / multicast coordination entity (MCE), integrated radio access backhaul (IAB) node, relay node, donor node controlled relay, radio access point (AP), transmission point, transmitting node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third party node, node outside the current network), node in a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. The network node may also comprise test equipment. As used herein, the term "radio node" may also be used to refer to a UE (such as a wireless device (WD) or a radio network node).

[0101] In some embodiments, the non-limiting terms user equipment (UE) or wireless device (WD) are used interchangeably. A UE herein may be any type of user equipment (e.g., wireless device) capable of communicating with a network node or another UE via wireless signals, such as a user equipment (UE). A UE may also be a wireless communication device, a target device, a device to device (D2D) UE, a machine-type UE or a UE capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity UE, a sensor equipped UE, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc. Although a UE is described, any WD may be implemented. Furthermore, a UE may be considered the same as a WD and not limited to a particular type of wireless device.

[0102] Also, in some embodiments, the general term "radio network node" is used. The radio network node may be any type of radio network node, which may comprise a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an RNC, an evolved Node B (eNB), a Node B, a gNB, a multi-cell / multicast coordination entity (MCE), an IAB node, a relay node, an access point, a radio access point, a remote radio unit (RRU), or a remote radio head (RRH).

[0103] In one or more embodiments, one or more of the following may apply. ● Although the solution herein is described with respect to an example of two RAN nodes serving a UE in NR-DC, the solution herein may be generalized to any number of nodes simultaneously serving a UE. ● Although the solutions herein are described with respect to the example of NR-DC, the solutions herein may be generalized to Multi-Radio Dual Connectivity (MR-DC) or similarly to connectivity options with more than two RAN nodes. ● 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. However, it should be noted that "QMC configuration file" is not an equivalent term and instead refers to the part of the QoE configuration that consists, for example, of an XML file containing instructions for the QoE metrics to be collected. ● All references to the application layer relate to the application layer of the UE (as the RAN node does not have an application layer). The term "service" is often used as a shorthand for "service type." Thus, "service" and "service type" may, for example, be interchangeable unless explicitly stated otherwise. The solution proposed in this invention can be applied to both signaling-based and management-based QoE measurements (although it can be optionally constrained to apply to only one of them). ● The terms "QoE report" and "QoE measurement report" are used interchangeably. Similarly, the terms "RAN visible QoE report", "RAN visible QoE measurement report", "RVQoE report" and "RVQoE measurement report" are used interchangeably. ● The terms "access stratum" and "radio layer" are used interchangeably when referring to a UE. ● The term "session" can refer either to a QoE measurement session or an application session, or to an application session to which QoE measurements are applied. ● The term "session" can refer either to a QoE measurement session or an application session, or to an application session to which QoE measurements are applied. ● The solution proposed in this invention applies to UMTS, LTE and NR as well as future RATs such as 6G. ● Although the present solution is described with respect to the example of management-based QoE measurements (i.e., their corresponding RVQoE measurements), the present solution is equally applicable to both management-based and signaling-based QoE measurements, as well as their corresponding RVQoE measurements.

[0104] It should be noted that while terminology from one particular wireless system, such as 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be considered to limit the scope of this disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband 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 utilizing the ideas covered within this disclosure.

[0105] Furthermore, it should be noted that functionality described herein as being performed by a user equipment or a network node may be distributed over multiple user equipments (UEs) and / or network nodes. In other words, it is contemplated that the network node and user equipment functionality described herein is not limited to being performed by a single physical device, but may in fact be distributed among several physical devices.

[0106] Unless otherwise specified, 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 the terms used herein should be interpreted as having a meaning in accordance with the meaning of those terms in the context of this specification and related art, and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0107] Referring again to the drawings, where like elements are referred to by like reference numerals, FIG. 8 shows a schematic diagram of a communication system 10, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), comprising an access network 12, such as a wireless access network, and a core network 14, according to one embodiment. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (collectively referred to 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 (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in the coverage area 18a is configured to wirelessly connect to or be paged by the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to corresponding network node 16b. Although multiple UEs 22a, 22b (collectively referred to as UEs 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or connects to the corresponding network node 16. For convenience, only two UEs 22 and three network nodes 16 are shown, but it should be noted that a communications system may include many more UEs 22 and network nodes 16.

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

[0109] The communication system 10 may itself be connected to a host computer 24, which may be embodied in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. 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 through an optional intermediate network 30. The intermediate network 30 may be one of a public network, a private network, or a hosted network, or a combination of two or more thereof. The intermediate network 30, if present, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).

[0110] The communication system of FIG. 8 as a whole enables connectivity between one of the connected UEs 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 UEs 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 networks 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 the routing of the uplink and downlink communications. For example, the network node 16 may not, or need not, be informed regarding the past routing of an incoming downlink communication involving data originating from the host computer 24 that is to be forwarded (e.g., handed over) to the connected UE 22a. Similarly, the network node 16 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 22 a and destined for the host computer 24 .

[0111] The network node 16 is configured to include an NN coordination unit 32 configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, e.g., to send information to the second network node regarding which of the first network node and the second network node configured quality of experience measurements for a predetermined service type associated with the UE, and / or to determine which of the first network node and the second network node carries data for an application session that is subject to quality of experience measurements for a predetermined service type, and / or, when the second network node carries data for the application session that is subject to quality of experience measurements, forward a quality of experience report corresponding to the application session to the second network node. The user equipment 22 is configured to include a UE coordination unit 34 configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, to determine that data for an application session undergoing quality of experience measurements for a predetermined service type associated with the UE 22 is carried by a second network node and / or to send an indication to at least the first network node 16a, where the indication indicates that data for the application session undergoing quality of experience measurements for the predetermined service type is carried by the second network node, and the indication is usable by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0112] An exemplary implementation of the UE 22, network node 16, and host computer 24 described in the previous paragraph, according to one embodiment, will now be described with reference to FIG. 9. In the communication system 10, the host computer 24 comprises hardware (HW) 38, including a communication interface 40 configured to set up and maintain wired or wireless connections with interfaces of different communication devices 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 a memory 46. In particular, in addition to or instead of a processor and memory, such as a central processing unit, the processing circuitry 42 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits), adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) the memory 46, which may include any type of volatile and / or non-volatile memory, such as 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).

[0113] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed by, for example, host computer 24. Processor 44 corresponds to one or more processors 44 for performing the host computer 24 functions described herein. Host computer 24 includes memory 46 configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause 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 host computer 24.

[0114] Software 48 may be executable by processing circuitry 42. Software 48 includes host application 50. Host application 50 may be operable to provide services to a remote user, such as UE 22, connecting via an OTT connection 52 that terminates at UE 22 and host computer 24. In providing services to the remote user, host application 50 may provide user data to be transmitted using OTT connection 52. "User data" may be data and information, as described herein as implementing described functionality. In one embodiment, host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. Processing circuitry 42 of host computer 24 may enable host computer 24 to observe, monitor, control, send to, and / or receive from network node 16 and / or user equipment 22. The processing circuitry 42 of the host computer 24 may include a host collaboration unit 54 configured to enable the service provider to perform any steps and / or tasks and / or processes and / or methods and / or features described in this disclosure, e.g., observe / monitor / control / transmit to / receive from the network node 16 and / or user equipment 22.

[0115] The communication system 10 further includes a network node 16 provided therein, the network node 16 including hardware 58 that enables the network node 16 to communicate with the host computer 24 and the UE 22. The hardware 58 may include a communication interface 60 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a radio connection 64 with the UE 22 located within the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or 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 the connection 66 may pass through the core network 14 of the communication system 10 and / or one or more intermediate networks 30 outside the communication system 10.

[0116] 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 and memory, such as a central processing unit, the processing circuitry 68 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits), 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 include any type of volatile and / or non-volatile 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).

[0117] Thus, network node 16 further has software 74 stored, for example, internally in memory 72 or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 may be executable by processing circuitry 68. Processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. Memory 72 is configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform processes described herein with respect to network node 16. For example, the processing circuitry 68 of the network node 16 may include a UE coordination unit 34 configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, e.g., to send information to the second network node regarding which of the first network node and the second network node configured quality of experience measurements for a predetermined service type associated with the UE, and / or to determine which of the first network node and the second network node carries data for an application session that is subject to quality of experience measurements for a predetermined service type, and / or, when the second network node carries data for the application session that is subject to quality of experience measurements, forward a quality of experience report corresponding to the application session to the second network node.

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

[0119] The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and a memory 88. In particular, in addition to or instead of a processor and memory, such as a central processing unit, the processing circuitry 84 may comprise integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, which may include any type of volatile and / or non-volatile 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).

[0120] Accordingly, the UE 22 may further comprise software 90, which may be stored, for example, in memory 88 in the UE 22 or in an external memory accessible by the UE 22 (e.g., a database, a storage array, a network storage device, etc.). 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, with the support of the host computer 24, to provide services to a human or non-human user via the UE 22. On the host computer 24, a running host application 50 may communicate with the running client application 92 via an OTT connection 52 that terminates at the UE 22 and the host computer 24. In providing services 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 the client application 92 provides.

[0121] 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, for example, by the UE 22. The processor 86 corresponds to one or more processors 86 for performing the UE 22 functions described herein. The UE 22 includes a memory 88 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 the processing circuitry 84, cause the processor 86 and / or the processing circuitry 84 to perform the processes described herein with respect to the UE 22. For example, the processing circuitry 84 of the user equipment 22 may include a UE coordination unit 34 configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, e.g., determine that data for an application session undergoing quality of experience measurements for a predetermined service type associated with the UE is carried by a second network node and / or send an indication to at least a first network node, where the indication indicates that data for an application session undergoing quality of experience measurements for the predetermined service type is carried by the second network node, and where the indication is usable by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0122] In some embodiments, the internal workings of the network node 16, the UE 22, and the host computer 24 may be as shown in FIG. 9, and separately, the surrounding network topology may be that of FIG.

[0123] 9, OTT connection 52 is depicted abstractly to show communication between host computer 24 and user equipment 22 via network nodes 16, without explicit reference to intermediary devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from UE 22, the service provider operating host computer 24, or both. While OTT connection 52 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0124] The wireless connection 64 between the UE 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 22 using the OTT connection 52, of which the wireless connection 64 may form the final segment. More precisely, the teachings of some of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed limits on file sizes, better responsiveness, extended battery life, etc.

[0125] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and the UE 22 in response to fluctuations in the measurement results. The measurement procedures 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 UE 22, or both. In embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 52 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above or other physical quantities from which the software 48, 90 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include changes in message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the network node 16, and the reconfiguration may be unknown or imperceptible to the network node 16. Some such procedures and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 24 measurements of throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages, particularly empty or "dummy" messages, to be sent using the OTT connection 52 while the software 48, 90 monitors propagation time, errors, etc.

[0126] Thus, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and a communications interface 40 configured to forward the user data to a cellular network for transmission to UE 22. In some embodiments, the cellular network also includes network node 16 having a radio interface 62. In some embodiments, network node 16 is configured to implement, and / or processing circuitry 68 of network node 16 is configured to implement, the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to UE 22 and / or preparing / terminating / maintaining / supporting / terminating in receipt of transmissions from UE 22.

[0127] In some embodiments, host computer 24 includes processing circuitry 42 and a communications interface 40 configured to receive user data originating from transmissions from UE 22 to network node 16. In some embodiments, UE 22 comprises a wireless interface 82 and / or processing circuitry 84 configured to implement and / or to implement the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16 and / or preparing / terminating / maintaining / supporting / terminating in reception of transmissions from network node 16.

[0128] 8 and 9 show various "units," such as NN coordination unit 32 and UE coordination unit 34, as being within respective processors, it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, the units may be implemented in hardware or a combination of hardware and software within the processing circuitry.

[0129] 10 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication systems of FIGS. 8 and 9, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a UE 22, which may be as described with reference to FIG. 9. In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides the user data by executing a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the UE 22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the UE 22 (block S106), in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step, the UE 22 executes a client application, such as, for example, client application 92, that is associated with the host application 50 executed by the host computer 24 (block S108).

[0130] 11 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 8, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a UE 22, which may be as described with reference to FIGS. 8 and 9. In a first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides the user data by executing a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the UE 22 (block S112). The transmission may proceed via the network node 16 in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the UE 22 receives the user data carried in the transmission (block S114).

[0131] 12 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 8, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a UE 22, which may be those described with reference to FIGS. 8 and 9. In an optional first step of the method, the UE 22 receives input data provided by the host computer 24 (block S116). In an optional sub-step of the first step, the UE 22 executes a client application 92, which provides user data in response to the received input data provided by the host computer 24 (block S118). Additionally or alternatively, in an optional second step, the UE 22 provides the user data (block S120). In an optional sub-step of the second step, the UE provides the user data by executing a client application, such as the client application 92 (block S122). In providing the user data, the executed client application 92 may further take into account user input received from a user. Regardless of the particular manner in which the user data was provided, the UE 22 may, in an optional third substep, initiate 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 UE 22 (block S126) in accordance with the teachings of the embodiments described throughout this disclosure.

[0132] 13 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of FIG. 8, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a UE 22, which may be as described with reference to FIGS. 8 and 9. In an optional first step of the method, the network node 16 receives user data from the UE 22 (block S128), in accordance with the teachings of embodiments described throughout this disclosure. In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in a transmission initiated by the network node 16 (block S132).

[0133] 14 is a flowchart of an example process in a network node 16 (e.g., a first network node 16a). One or more blocks described herein may be implemented by one or more elements of the network node 16, such as by one or more of the processing circuitry 68 (including the NN coordination unit 32), the processor 70, the wireless interface 62, and / or the communication interface 60. The network node 16, via the processing circuitry 68 and / or the processor 70 and / or the wireless interface 62 and / or the communication interface 60, etc., is configured to send information to the second network node 16b regarding which of the first network node 16a and the second network node 16b has configured a quality of experience measurement for a predetermined service type associated with the UE 22 (block S134), determine which of the first network node 16a and the second network node 16b carries data for the application session that is subject to the quality of experience measurement for the predetermined service type (block S136), and, when the second network node 16b carries data for the application session that is subject to the quality of experience measurement, forward a quality of experience report corresponding to the application session to the second network node 16b (block S138).

[0134] In some embodiments, the method further includes configuring the UE 22 to at least one of: send a quality of experience report to at least one of the first network node 16a and the second network node 16b; and indicate whether the quality of experience is targeted to the first network node 16a or the second network node 16b.

[0135] In some other embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes, the UE 22 is configurable to send a capability indication to at least one of the first network node 16a and the second network node 16b, the quality of experience measurement is a RAN Visible Quality of Experience (RVQoE) measurement, and the quality of experience report is an RVQoE report.

[0136] 15 is a flowchart of an example process in the user equipment 22, in accordance with some embodiments of the present disclosure. One or more blocks described herein may be implemented by one or more elements of the user equipment 22, such as by one or more of the processing circuitry 84 (including the UE coordination unit 34), the processor 86, the air interface 82, and / or the communication interface 60. The user equipment 22, e.g., via the processing circuitry 84 and / or the processor 86 and / or the air interface 82, is configured to determine (block S140) that data for an application session undergoing quality of experience measurements for a predetermined service type associated with the UE 22 is carried by the second network node 16b and to send an indication to at least the first network node 16a (block S142). The indication indicates that data for the application session undergoing quality of experience measurements for the predetermined service type is carried by the second network node 16b. The indication is usable by the first network node 16a to forward a quality of experience report corresponding to the application session to the second network node 16b.

[0137] In some embodiments, the UE 22 is configured by at least one of the first network node 16a and the second network node 16b to send a quality of experience report to at least one of the first network node 16a and the second network node 16b.

[0138] In some other embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes, the UE 22 is configurable to send a capability indication to at least one of the first network node 16a and the second network node 16b, the quality of experience measurement is a RAN Visible Quality of Experience (RVQoE) measurement, and the quality of experience report is an RVQoE report.

[0139] 16 is a flowchart of an example process in a network node 16 (e.g., the first network node 16a). One or more blocks described herein may be implemented by one or more elements of the network node 16, such as by one or more of the processing circuitry 68 (including the NN coordination unit 32), the processor 70, the air interface 62, and / or the communication interface 60. The network node 16 (e.g., the first network node 16a), via the processing circuitry 68 and / or the processor 70 and / or the air interface 62 and / or the communication interface 60, etc., is configured to: coordinate with the second network node 16b to determine which of the first network node 16a and the second network node 16b has a report corresponding to a service type associated with the UE 22 (block S144); and determine which of the first network node 16a and the second network node 16b carries data for an application session subject to a quality of experience measurement associated with the report (block S142). The network node 16 (e.g., the first network node 16a) is further configured to perform one or more actions to ensure that one of the first network node 16a and the second network node 16b carrying the data obtains the report.

[0140] In some embodiments, the coordination includes the first network node 16a sending a first indication to the second network node 16b indicating that the first network node 16a has received a report from the UE, or receiving a second indication from the second network node 16b indicating that the second network node 16b has received a report from the UE.

[0141] In some other embodiments, the report includes one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID. Determining which of the first network node 16a and the second network node 16b carries data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0142] In some embodiments, the method further includes receiving a report from the UE.

[0143] In some other embodiments, performing the one or more actions includes transmitting a report to the second network node 16b when the second network node 16b carries data for the application session, the transmitted report being usable by the second network node 16b to transmit and / or receive signaling to and from the UE related to the service type.

[0144] In some embodiments, performing the one or more actions includes receiving a report from the second network node 16b when the first network node 16a carries data about the application session, the received report being usable by the first network node 16a to send and / or receive signaling to and from the UE related to the service type.

[0145] In some other embodiments, the method further includes causing the UE to be configured to do one or both of sending a report to at least one of the first network node 16a and the second network node 16b and indicating which of the first network node 16a and the second network node 16b the quality of experience is targeted to.

[0146] In some embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes, and the quality of experience measurements are one or both of Quality of Experience (QoE) measurements and RAN Visible Quality of Experience (RVQoE) measurements.

[0147] In some other embodiments, the report includes one or more of a Quality of Experience (QoE) report and a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

[0148] In some embodiments, the method further includes receiving a capability indication from the UE indicating one of the first network node 16a and the second network node 16b that carries the application session.

[0149] 17 is a flowchart of an example process in user equipment 22, according to some embodiments of the present disclosure. One or more blocks described herein may be implemented by one or more elements of user equipment 22, such as by one or more of processing circuitry 84 (including UE coordination unit 34), processor 86, radio interface 82, and / or communication interface 60. The user equipment 22, via the processing circuitry 84 and / or the processor 86 and / or the wireless interface 82, etc., is configured to send to one of the first network node 16a and the second network node 16b a report corresponding to a service type associated with the UE 22 (block S150), the report comprising one or more of a data radio bearer (DRB) identifier (ID), a quality of service (QoS) flow ID, and a packet data unit (PDU) session ID, and which of the first network node 16a and the second network node 16b carries data for the application session is determined based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0150] In some embodiments, the method further includes determining a capability indication usable by one or both of the first network node 16 a and the second network node 16 b to determine which of the first network node 16 a and the second network node 16 b carries data for the application session that is subject to the quality of experience measurement associated with the report, and performing one or more actions to ensure that the one of the first network node 16 a and the second network node 16 b that carries the data obtains the report. The method further includes transmitting the capability indication to one or both of the first network node 16 a and the second network node 16 b.

[0151] In some other embodiments, when the report is transmitted to the first network node 16 a, the one or more actions include transmitting a report by the first network node 16 a to the second network node 16 b when the second network node 16 b carries data about the application session, the transmitted report being usable by the second network node 16 b to transmit and / or receive signaling to and from the UE 22 related to the service type.

[0152] In some embodiments, the one or more actions include receiving, by the first network node 16 a, a report from the second network node 16 b when the first network node 16 a carries data for the application session, the received report being usable by the first network node 16 a to send and / or receive signaling to and from the UE 22 related to the service type.

[0153] In some other embodiments, the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a radio access network (RAN) visible quality of experience (RVQoE) measurement.

[0154] In some embodiments, the method further includes indicating whether the quality of experience is targeted to the first network node 16a or the second network node 16b.

[0155] In some other embodiments, the first network node 16a and the second network node 16b are radio access network (RAN) nodes.

[0156] In some embodiments, the report comprises a Quality of Experience (QoE) report.

[0157] In some other embodiments, the report includes a Radio Access Network (RAN) Visual Quality of Experience (RVQoE) report.

[0158] In some embodiments, the method further includes determining the reporting based on one or both of a first configuration and a second configuration received from one or both of the first network node 16a and the second network node 16b.

[0159] Having described the general process flow of the configurations of the present disclosure and provided example hardware and software configurations for implementing the processes and functionality of the present disclosure, the following sections provide configuration details and examples for inter-node collaboration, e.g., for reporting in a multi-node connectivity environment.

[0160] Some embodiments provide a UE 22 (eg, a WD), a first network node 16a (eg, a first node), and a second network node 16b (eg, a second node).

[0161] First Exemplary Solution: UE-Based Solution The first solution includes at least one of the following steps: 1. The UE 22 establishes NR-DC to a first network node 16a and a second network node 16b, which act as an MN and an SN, respectively, or an SN and an MN, respectively.

[0162] 2. A network entity, e.g., OAM, assembles a management-based QoE measurement configuration (referred to herein as a first configuration) and distributes the management-based QoE measurement configuration to several RAN nodes in an area, among which are a first network node 16 a and a second network node 16 b. The first network node 16 a configures the UE 22 with QoE measurements for a service, e.g., a first service, according to the first configuration, and the first network node 16 a configures the UE 22 with RVQoE measurements according to the second configuration and sets up an SRB 4 towards the UE 22. It should be noted that the UE 22 can establish only one SRB of each type towards the network, which means that in the scenario in question, unless reconfigured, an SRB 4 is always established towards either the first network node 16 a or the second network node 16 b, but not towards both. The UE 22 activates an application session for a service, for example the first service, which triggers QoE and RVQoE measurements at the UE 22 and their reporting. a. In the case of signaling-based (s-based) QoE, the QoE configuration is distributed from the OAM to the MN via the core network. b. In the case of management-based (m-based) QoE, it may happen that both the first network node 16a and the second network node 16b have received the first configuration (directly from OAM), for example because they are both within the area range of the first configuration or the configured PLMN(s).

[0163] 3. The first node 16a and the second node 16b inform each other whether they have both received the first configuration and whether they plan to configure the first configuration to the UE 22. The nodes may also indicate to each other whether they are interested in receiving RVQoE reports related to each measurement configuration. Each node may also inform the other node whether it has established an SRB4 towards the UE 22.

[0164] In one solution, one node (typically the master node) decides to configure an SRB4 as a split bearer, which means that the UE 22 splits transmission between the first network node 16a and the second network node 16b. In existing solutions, the split is based on the amount of data to be transmitted. Now, some new criteria for how the UE 22 splits transmission may be defined. As an example, the split may be based on whether the data is for a service of the first network node 16a or a service of the second network node 16b. If the data is for a service of the first network node 16a, the UE 22 sends the data to the first network node 16a on the leg, and if the data is for a service of the second network node 16b, the UE 22 sends the data to the second network node 16b on the leg. An example of split transmission may be when data related to VoNR services is sent to the first network node 16a and data related to streaming is sent to the second network node 16b according to a configuration provided to at least one of the first node 16a or the second node 16b. An additional criterion is that one of the legs is preferred or always used instead of the other until an overload (or near-overload) situation is detected by the node corresponding to the preferred leg. For example, SRB4 is configured as a split bearer, and the preferred leg corresponds to the node that configured SRB4 (e.g., the MN). According to the provided configuration, the UE 22 sends data using the MN leg. When the MN detects an overload (e.g., the MN detects that too much data has arrived via SRB4 in a given time period), the MN reconfigures SRB4 so that the UE 22 will now send data related to QoE / RVQoE reporting via another leg.

[0165] In another solution, one node (typically the master node) decides to set up the SRB4 as a replicated bearer, which means that data is sent to both the first network node 16a and the second network node 16b. Each node can then decide whether the data is for that particular node's service or the other node's service and take the relevant data for its own node.

[0166] In an alternative solution, messages carrying RVQoE reports, e.g., MeasurementReportAppLayer, are allowed to be transmitted on different SRBs in the first network node 16a and the second network node 16b, i.e., different SRBs are defined. This may include using SRB4 in the first network node 16a and SRB1, SRB3, or a new SRB5 in the second network node 16b. One of the SRBs may be defined as a master node bearer and the other SRB may be defined as a secondary node bearer, or both may be defined as master node bearers or both may be defined as secondary node bearers.

[0167] In yet another exemplary solution, the same SRB is used for RVQoE reporting for both the primary and secondary nodes, possibly with an indication from the UE 22 as to which node the reports are directed to. See step 4. a. The first network node 16a and the second network node 16b may inform each other whether they have received a first configuration and whether they plan to configure the UE 22 with the first configuration during the execution of one of the procedures related to multi-connectivity operations, where the UE 22 is reconfigured from single connectivity to multi-connectivity (e.g., secondary node addition) or the UE 22 is reconfigured from a first configuration in multi-connectivity to a second configuration in multi-connectivity (e.g., secondary node modification - MN initiated or SN initiated, secondary node change - MN initiated or SN initiated, inter-MN handover with / without SN change). b. One of the nodes involved in the NR-DC (or MR-DC) instructs / requests the other node to forward RVQoE reports related to services for which they have provided corresponding RVQoE settings to UE22, and the instruction / request is carried over a new or existing procedure. i. In some cases, the first network node 16a and the second network node 16b are already used in MR-DC and only one of the nodes is included in the area coverage. The node receiving the m-based configuration (either the MN node or the SN node) can configure the UE 22 for RVQoE and instruct / request the other node (SN or MN, respectively) to forward the RVQoE report to the node receiving the m-based configuration. ii. In another case, one of the nodes (generally the MN node) configures the UE 22 to collect RVQoE for a first service according to the s-based QoE configuration. In this case, the MN is not included in the area range related to the m-based QoE configuration, but the other node (SN) is included in the area range related to the m-based QoE configuration. The other node (SN) configures the UE 22 to collect RVQoE for a second service. The MN instructs / requests the SN to forward the RVQoE report related to the first service to the MN, and the SN instructs / requests the MN to forward the RVQoE report related to the second service to the SN. iii. In another case, at least one of the first network node 16a and / or the second network node 16b receives an m-based QoE configuration to be sent to the UE 22 and / or decides to prepare an RVQoE configuration for the UE 22. For example, if it is the first network node 16a, the first network node 16a can inform the second network node 16b that it has configured the UE 22 for RVQoE and that it is interested in receiving RVQoE reports. The second network node 16b then notices that future RVQoE reports received for the UE 22 at the second network node 16b need to be sent to the first network node 16a. There is a possible race condition in which both the first network node 16a and the second network node 16b can attempt to configure the UE 22 with the same RVQoE configuration. In this case, one subcase is that the most recent setting overrides the older setting (RVQoE setting modifications are not allowed). In another subcase, each of the nodes will receive an indication that the other is interested in receiving RVQoE reports from the other. In another subcase, the node that was the last of the two to send an RVQoE setting to the UE 22 is the node that should receive the RVQoE report. In yet another subcase, the node that sent an RVQoE setting before the other is the node that should receive the RVQoE report. c. When one of the nodes is removed from the NR-DC (or MR-DC) configuration, it instructs / requests the other node to receive RVQoE reports related to services for which it provided corresponding RVQoE configurations to UE22, the instruction / request being conveyed over a new or existing procedure.

[0168] It may be assumed that the first network node 16a has configured the UE 22 for QoE measurements and RVQoE measurements and established an SRB4 towards the UE 22. This is a non-limiting example, as it may happen, for example, that the second network node 16b has configured the first and second configurations towards the UE 22. At this point, neither of the two nodes is aware which of them carries data for the application session for the first service.

[0169] 4. The UE 22 understands that data for the first service will be carried via the second network node 16b. This can be done by the UE Access Stratum (AS) layer based on knowledge of the DRB ID, QoS flow ID or PDU session ID of the application session, and the corresponding connectivity leg. Note that as part of the DC setup procedure, the MN indicates to the SN an available DRB ID to be used by the SN for the SCG-terminated DRB, ensuring the uniqueness of the DRB ID set up towards the UE 22 in the DC. Alternatively, or in combination with this, the UE 22 can also use one of the methods described below (in the section "How the UE Identifies the Leg Carrying the Application Data Flow") to identify the connectivity leg. The UE 22 already knows that an SRB 4 will be established towards the first network node 16a. Therefore, the UE 22 sends an indication to the first network node 16a that data for the application session is carried via the second network node 16b, which means that the second network node 16b should have received the RVQoE report carried from the UE 22 to the first network node 16a via SRB4.

[0170] Alternatively, the UE 22 may send along with the RVQoE report an indication of which node the report is directed to. This indication may be sent always or only in certain circumstances, such as when the report targets the other node, when the target node has changed since the last report, etc.

[0171] 5. Based on the indication received from the UE 22 in step 4, the first network node 16a sends an indication to the second network node 16b, which indication informs the second network node 16b that the RVQoE reporting according to the second configuration relates to the leg between the UE 22 and the second network node 16b. a. In one variant, the instruction from the first network node to the second network node 16b may be a notification of the above (Instruction A). b. In another variant, the instruction may be a query (interest poll) to the second network node 16b as to whether the second network node 16b is interested in receiving an RVQoE report from the UE 22 via the first network node 16a (Instruction B). c. In another variant, the instruction may be a query "asking" the second network node 16b to provide parameters for RVQoE measurements at the UE 22 (Instruction C). d. Any of the instructions may include a request to the second network node 16b that the second network node 16b set up an SRB4 towards the UE 22. e. Note that the above is independent of whether both the first network node and the second network node 16b are within the area range of the first and second configurations. f. Note that the above is also valid if one of the nodes used for NR-DC (or MR-DC) connectivity and that configured UE22 for RVQoE is later removed from the UE22 configuration (e.g., UE22 is reconfigured from multi-connectivity to single connectivity, or UE22 is reconfigured with a different NR-DC (or MR-DC) configuration).

[0172] 6. The second network node 16b responds to the indication received from the first network node 16a in step 5. a. When the second network node 16b receives the indication A, the second network node 16b may acknowledge receipt. b. If the second network node 16b receives the indication B, the second network node 16b may reply whether the second network node 16b is interested in receiving an RVQoE report from the first network node 16a relating to the second setting received from the UE 22. i. If the second network node 16b is interested in receiving the RVQoE report, the second network node 16b may also instruct the first network node 16a whether the second network node 16b requests that an SRB4 be set up between the UE 22 and the second network node 16b instead of being set up between the first network node 16a and the UE 22. ii. If the second network node 16b is not interested in receiving RVQoE reports from the UE 22 via the first network node 16a, the first network node 16a may deactivate RVQoE measurements related to the second configuration. c. When the second network node 16b receives the indication C, the second network node 16b may indicate the desired RVQoE configuration parameters.

[0173] 7. Based on the response received from the second network node 16b in step 6, the first network node 16a takes one or more of the following actions (any meaningful combination of the following actions is possible): a. If the second network node 16b acknowledges receipt of the instruction A, the first network node 16a may forward RVQoE reports relating to the second configuration received from the UE 22 to the second network node 16b in the future. Alternatively, the first network node 16a may decide to request the second network node 16b to set up an SRB4 towards the UE 22, which may deconfigure the SRB4 currently existing between the first network node 16a and the UE 22. This means that from now on, RVQoE reports will be sent directly from the UE 22 to the second network node 16b. In another variant, the first network node 16a may keep the SRB4 with the UE 22, but may instruct the UE 22 to send RVQoE reports to the second network node 16b via the already established SRB, for example SRB3. b. If the second network node 16b replies, based on the received instruction B, that the second network node 16b is interested in receiving the RVQoE report, the first network node 16a may perform one or more of the actions described at point a. of this step (step 7). c. If the second network node 16b replies with a desired RVQoE measurement configuration that differs from the current second configuration based on the received instruction C, the first network node 16a may modify the second configuration accordingly.

[0174] The RVQoE report may be delivered to the second network node 16b based on the actions taken in at least one of steps 1-7.

[0175] Second Exemplary Solution: Network-Based Solution The second solution may include at least one of the following steps: 1. Same as (or similar to) the first solution.

[0176] 2. Same as (or similar to) the first solution.

[0177] 3. Same as (or similar to) the first solution.

[0178] Hereafter, it may be assumed that the first network node 16a has configured the UE 22 for QoE and RVQoE measurements and established SRB4 (and / or another SRB to which the UE 22 may send RVQoE reports) towards the UE 22. This is a non-limiting example, as it could, for example, have instead been the second network node 16b that configured the first and second configurations for the UE 22. At this point, neither of the two nodes is aware which of them carries data for the application session for the first service.

[0179] 4. The first network node 16a receives an RVQoE report related to the second configuration from the UE 22. The RVQoE report may include a DRB ID and / or a QoS flow ID and / or a PDU session ID of the application session that is subject to the RVQoE measurement. When the contents of the RVQoE report are visible to the first network node 16a, based on the service type to which the RVQoE measurement refers, the DRB ID and / or the QoS flow ID and / or the PDU session ID therein, the first network node 16a understands that data about the application session that is subject to the RVQoE measurement is delivered to the UE 22 via the second network node 16b. For example, the first network node 16a may infer based on the DRB ID in the RVQoE report that the session will be carried via the second network node 16b, since as part of the DC setup procedure, the MN instructs the SN what available DRB IDs should be used by the SN for SCG-terminated DRBs, ensuring the uniqueness of the DRB IDs set up towards the UE 22 in the DC. Alternatively, or in combination with this, the method described in section "How the UE Identifies the Leg Carrying Application Data Flow(s)," where the application includes socket information in the RVQoE report that can be used to identify the connectivity leg, may be used. Thus, the first network node 16a understands that the second network node 16b should have received the RVQoE report carried from the UE 22 to the first network node 16a via SRB4.

[0180] Alternatively, the UE 22 may send along with the RVQoE report an indication of which node the report is directed to. This indication may be sent always or only in certain circumstances, such as when the report targets the other node, when the target node has changed since the last report, etc. a. In one option, the first network node 16a may determine that data for an application session subject to RVQoE measurements is delivered entirely to the UE 22 via the second network node 16b by using one or more of the following indications: service type, DRB ID associated with the application session, QoS flow ID, PDU session ID, timestamp received within or with the RVQoE report, an indication (or absence of an indication) indicating no user plane activity for the UE 22 with the first network node 16a during the time period referenced by the RVQoE report. b. The first network node 16a may further determine that data for the application session subject to the RVQoE measurement has been partially delivered to the UE 22 via the first network node 16a (e.g., based on a timestamp sent within or along with the RVQoE report and an indication collected at the first network node 16a indicating user plane activity for the UE 22 involving the first network node 16a) and may retain the RVQoE measurement for optimization at the first network node 16a.

[0181] 5. Same as (or similar to) the first solution.

[0182] 6. Same as (or similar to) the first solution.

[0183] 7. Same as (or similar to) the first solution.

[0184] 8. Same as (or similar to) the first solution.

[0185] In one embodiment, the first network node 16a and the second network node 16b can agree on sending RVQoE measurements received from the UE 22 to the node that configured the UE 22 for RVQoE before the RVQoE configuration is issued to the UE 22. This coordination can be achieved, for example, during one of the procedures related to multi-connectivity operations, where the UE 22 is reconfigured from single connectivity to multi-connectivity (e.g., secondary node addition). The UE 22 can be reconfigured from a first configuration in multi-connectivity to a second configuration in multi-connectivity (e.g., secondary node modification—MN-initiated or SN-initiated, secondary node change—MN-initiated or SN-initiated, inter-MN handover with / without SN change). A node (e.g., MN) that is interested in receiving RVQoE reports may signal a flag to the other node (e.g., SN) to indicate a request to obtain RVQoE reports that the UE 22 may send to the other node (the request may be general, i.e., applicable to RVQoE reports, or may be more granular, e.g., indicating that the MN is interested in receiving RVQoE reports only for a particular service).

[0186] In another embodiment, the first network node 16a (second network node 16b) may have agreed with the second network node 16b (first network node 16a) to send to the second network node 16b (first network node 16a) RVQoE measurements related to data delivered to the UE 22 via the first network node 16a (second network node 16b) before the RVQoE configuration is issued to the UE 22. This may be implemented if both the first network node 16a and the second network node 16b are used in NR-DC (or any other form of MR-DC) if the second network node 16b hosts (or is connected to) an AI / ML training function where the RVQoE measurements are used as input data and has requested to receive such RVQoE measurements.

[0187] How the UE identifies the leg(s) carrying the application data flow(s). To determine on which connectivity leg (towards the MN or towards the SN) the data flow subject to RVQoE measurements is carried, the UE 22 may rely on inherent knowledge in the application.

[0188] An application creates a network socket for its application data flows, and the socket may have several associated parameters that can be used to identify the socket and the application data flow(s) through it. These parameters may include at least one of the following: - Local IP addresses (i.e., source IP addresses for outgoing data flows and destination IP addresses for incoming data flows) - Remote IP address (i.e., source IP address for incoming data flows and destination IP address for outgoing data flows) - local transport protocol ports (i.e., source transport protocol ports for outgoing data flows and destination transport protocol ports for incoming data flows); - Remote transport protocol ports (i.e., source transport protocol ports for incoming data flows and destination transport protocol ports for outgoing data flows) - Transport protocols (e.g., Transport Control Protocol (TCP), Stream Control Transport Protocol (SCTP), Real Time Protocol (RTP))

[0189] Of the above, the local IP address is potentially also known by the UE AS, since it is the IP address allocated to the UE 22 .

[0190] To enable the UE AS to identify the DRB(s) and connectivity legs that carry a certain application data flow(s), the application (in the UE application layer) informs the AS of the UE 22 of all or a subset of the above-listed socket parameters (e.g., optionally excluding the local IP address) for each incoming and outgoing data flow. The UE AS can use this information (hereafter referred to as socket information) to check on which DRB(s) and connectivity legs packets matching this information are sent and received.

[0191] The socket information from the UE application layer can be forwarded upon request from the UE AS, either as a one-time request (e.g., upon receiving an RVQoE report from the UE application layer) or as a more general request (e.g., when an RVQoE configuration is sent to the UE application layer or when a session start indication is received from the UE application layer). Such a more general request would cause the application to send the socket information at the start of each application session that undergoes RVQoE measurement (and send updated information during the session if the information changes). Alternatively, the application could send the socket information to the UE AS each time the application creates a socket, as a result of a general request from the UE AS. As another alternative, such a more general request would cause the application to send the socket information with each RVQoE report.

[0192] Another option would be to indicate in the RVQoE configuration that the application should send this information to the UE AS at the start of each application session (with mid-session updates if necessary), at socket creation, and / or with each RVQoE report, instead of relying on a request from the UE AS.

[0193] Yet another possible option could be to bypass the UE AS entirely and instead have the application (at the UE application layer) include the socket information in the RVQoE report (governed by the RVQoE configuration), in which case it would be up to the RAN node receiving the RVQoE report to decide on which DRB(s) (and therefore which connectivity leg) the application data flow(s) are carried.

[0194] For communication of socket information between the application and the UE AS, AT commands (which are part of the AT command framework), AT command responses and / or unsolicited result codes may be used.

[0195] Additional Considerations The 3GPP specifications allow the UE 22 to establish only one SRB of a certain type, and this was the assumption taken in the present invention. However, the solution presented herein is also applicable when the UE 22 is allowed to set up SRBs 4 towards both the first network node 16a and the second network node 16b. In this case, the first network node 16a may not need to request the second network node 16b to set up an SRB 4, since the SRB 4 may already be set up between the UE 22 and both nodes. In this case, ● The first network node 16a may instruct the second network node 16b that RVQoE reports relating to the second configuration will henceforth be delivered directly from the UE 22 to the second network node 16b via SRB4. ● Upon understanding that data about the session subject to RVQoE measurements is delivered to the UE 22 via the second network node 16b (Solution 2) or upon receiving such an indication from the UE 22 (Solution 1), the first network node 16a may instruct the UE 22 to send an RVQoE report relating to the second configuration directly to the second network node 16b. Alternatively, the UE 22 may decide on its own to send the RVQoE report directly to the second network node 16b and may inform the first network node 16a about this.

[0196] CG-Config The message is used to transfer the SCG radio configuration generated by the SgNB or SeNB, and can also be used by the CU to request the DU to perform some action, for example, to request the DU to perform new lower layer configuration.

[0197] Direction: Secondary gNB or eNB to master gNB or eNB, alternatively, CU to DU.

[0198] A non-limiting example of a CG-Config message is as follows: TIFF2025529710000002.tif31170TIFF2025529710000003.tif255170TIFF2025529710000004.tif106170

[0199] Non-limiting examples of CG-ConfigInfo field descriptions are included in the table below. TIFF2025529710000005.tif62170 Table 1: CG-ConfigInfo field description.

[0200] UE ability indication The UE 22 may be configured (e.g., may need to) indicate to the network its capabilities to perform actions related to the described solutions. As part of UE capability signaling (either enhanced existing signaling or newly defined signaling), the UE 22 indicates to the network its capabilities to act in accordance with embodiments of the present disclosure, i.e., to send an indication to the network of the nodes that carry application sessions, that the aforementioned SRB configurations are configured, forward RVQoE reports directly to the appropriate network nodes, etc.

[0201] The following is a non-limiting list of exemplary embodiments: Embodiment A1. A first network node configured to communicate with a user equipment (UE) and a second network node, where at least the UE is configurable to communicate using multi-radio connectivity, and the first network node: transmitting to the second network node information regarding which of the first network node and the second network node configured quality of experience measurements for a given service type associated with the UE; determining which of the first network node and the second network node carries data for an application session subject to quality of experience measurements for a predetermined service type; forwarding a quality of experience report corresponding to the application session to the second network node when the second network node carries data for the application session subject to quality of experience measurement; a first network node configured to perform the above and / or comprising a wireless interface and / or comprising processing circuitry configured to perform the above.

[0202] Embodiment A2. The processing circuit comprises: a first network node; sending a quality of experience report to at least one of the first network node and the second network node; indicating whether the quality of experience is targeted to the first network node or the second network node; causing the UE to configure itself to perform at least one of the following: The first network node of embodiment A1 is configured to:

[0203] Embodiment A3. the first network node and the second network node are radio access network (RAN) nodes; the UE is configurable to send a capability indication to at least one of the first network node and the second network node; The quality of experience measurement is a RAN visible quality of experience (RVQoE) measurement; and The quality of experience report is an RVQoE report, The first network node of embodiment A1 or A2, wherein the first network node is at least one of:

[0204] Embodiment B1. A method in a first network node configured to communicate with a user equipment (UE) and a second network node, where at least the UE is configurable to communicate using multi-radio connectivity, the method comprising: transmitting to the second network node information regarding which of the first network node and the second network node configured quality of experience measurements for a given service type associated with the UE; determining which of the first network node and the second network node carries data for an application session subject to quality of experience measurements for a predetermined service type; forwarding a quality of experience report corresponding to the application session to the second network node when the second network node carries data for the application session subject to quality of experience measurement; A method comprising:

[0205] Embodiment B2. The method comprises: sending a quality of experience report to at least one of the first network node and the second network node; indicating whether the quality of experience is targeted to the first network node or the second network node; configuring the UE to perform at least one of The method of embodiment B1, further comprising:

[0206] Embodiment B3. the first network node and the second network node are radio access network (RAN) nodes; the UE is configurable to send a capability indication to at least one of the first network node and the second network node; The quality of experience measurement is a RAN visible quality of experience (RVQoE) measurement; and The quality of experience report is an RVQoE report, The method of embodiment B1 or B2, wherein at least one of:

[0207] Embodiment C1. A user equipment (UE) configured to communicate with a first network node and a second network node, wherein at least the UE is configurable to communicate using multi-radio connectivity, the UE comprising: determining that data for an application session subject to quality of experience measurements for a predetermined service type associated with the UE is carried by a second network node; sending an indication to at least a first network node, the indication instructing that data for an application session subject to quality of experience measurements for a predetermined service type be carried by a second network node, the indication usable by the first network node to forward a quality of experience report corresponding to the application session to the second network node; and / or a user equipment (UE) configured to perform the above and / or comprising a radio interface and / or processing circuitry configured to perform the above.

[0208] Embodiment C2. The UE: transmitting a quality of experience report to at least one of the first network node and the second network node; The UE of embodiment C1, configured by at least one of the first network node and the second network node to perform the following:

[0209] Embodiment C3. the first network node and the second network node are radio access network (RAN) nodes; the UE is configurable to send a capability indication to at least one of the first network node and the second network node; The quality of experience measurement is a RAN visible quality of experience (RVQoE) measurement; and The quality of experience report is an RVQoE report, The UE of embodiment C1 or C2, wherein the UE is at least one of:

[0210] Embodiment D1. A method in a user equipment (UE) configured to communicate with a first network node and a second network node, where at least the UE is configurable to communicate using multi-radio connectivity, the method comprising: determining that data for an application session subject to quality of experience measurements for a predetermined service type associated with the UE is carried by a second network node; sending an indication to at least a first network node, the indication instructing that data for an application session subject to quality of experience measurements for a predetermined service type be carried by a second network node, the indication usable by the first network node to forward a quality of experience report corresponding to the application session to the second network node; A method comprising:

[0211] Embodiment D2. The UE: transmitting a quality of experience report to at least one of the first network node and the second network node; The method of embodiment D1, wherein at least one of the first network node and the second network node is configured to perform the following:

[0212] Embodiment D3. the first network node and the second network node are radio access network (RAN) nodes; the UE is configurable to send a capability indication to at least one of the first network node and the second network node; The quality of experience measurement is a RAN visible quality of experience (RVQoE) measurement; and The quality of experience report is an RVQoE report, The method of embodiment D1 or D2, wherein at least one of:

[0213] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Accordingly, the concepts described herein may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects, all of which may be generally referred to herein as “circuits” or “modules.” Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the present 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 can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including hard disks, CD-ROMs, electronic, optical, or magnetic storage devices.

[0214] Some embodiments have been 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, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (to thereby create a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to create a machine, such that the instructions, executing via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0215] These computer program instructions may also be stored in a computer-readable memory or storage medium that can 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 create an article of manufacture that includes instruction means that implement the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0216] Computer program instructions may also be loaded into 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 create a computer-implemented process, whereby the instructions executing on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0217] It should 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 on the functions / acts involved. While some of the figures include arrows on communication paths to indicate the primary direction of communication, it should be understood that communication may occur in the opposite direction to that of the illustrated arrows.

[0218] Computer program code for performing operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java, or C++. However, computer program code for performing operations of the present 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, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or wide area network (WAN), or the connection may be to an external computer (e.g., through the Internet using an Internet Service Provider).

[0219] Many different embodiments have been disclosed herein with reference to the above description and drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and unclear. Accordingly, all embodiments may be combined in any manner and / or combination, and the specification, including the drawings, should be construed as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, and of all combinations and subcombinations of the modes and processes for making and using them, and is intended to support any claim to any such combination or subcombination.

[0220] Abbreviations that may be used in the foregoing description include the following: 3GPP 3rd Generation Partnership Project 5G (5th Generation) 5GC 5G Core Network 5GS 5th Generation System AS Access Hierarchy AMF Access and Mobility Management Functions ASN.1 Abstract Syntax Notation 1 AT attention AR Augmented Reality AS Access Hierarchy BAP Backhaul Adaptation Protocol CGI Cell Global Identification Information 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 E-CGI E-UTRAN CGI: eNB Evolved Node B / E-UTRAN Node B-gNB. A gNB acting as a secondary node in an EN-DC scenario (i.e., 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 Extended UTRA E-UTRAN / EUTRAN Extended UTRAN gNB NR radio base station HSS Home Subscriber Server HTTP Hypertext Transfer Protocol IAB Wireless Access Backhaul Integrated Transmission ID Identifier / Identification Information IE Information Elements LTE Long Term Evolution MAC Media Access Control MCC Mobile Country Code MCE Measurement Collection Entity / Measurement Collector Entity MDT Drive Test Minimization MME Mobility Management Entity MN Master Node MNC Mobile Network Code MTSI IMS Multimedia Telephony Services N3IWF Non-3GPP Interworking Function NG Next generation NG Interface between NG-RAN and 5GC. NGAP NG Application Protocol NG-RAN NG Radio Access Network NID Network Identifier NR new radio NWDAF Network Data Analysis Function O&M operation and maintenance OAM 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 S1 The interface between RAN and CN in LTE. S1AP S1 Application Protocol S-NSSAI Single Network Slice Selection Assistance Information SMO Service Management and Orchestration SN Secondary Node 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 UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WLAN Wireless Local Area Network Interface between two gNBs in Xn NR XnAP Xn Application Protocol

[0221] It will be appreciated by those skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. Further, unless otherwise noted above, it should be noted that all of the accompanying drawings are not to scale. Various modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. 1. A method in a user equipment (UE) (22) and a first network node (16a) configured to communicate with a second network node (16b), wherein at least the UE (22) is configurable to communicate using multi-radio connectivity with the first network node (16a) and the second network node (16b), the method comprising: coordinating (S144) with the second network node (16b) to determine which of the first network node (16a) and the second network node (16b) has a report corresponding to a service type associated with the UE (22); determining (S146) which of the first network node (16a) and the second network node (16b) carries data for an application session that is subject to a quality of experience measurement associated with the report; performing one or more actions to ensure that one of the first network node (16a) and the second network node (16b) carrying the data receives the report (S148); A method comprising:

2. The cooperation is sending a first indication to the second network node (16b) indicating that the first network node (16a) has received the report from the UE (22); receiving a second indication from the second network node (16b) indicating that the second network node (16b) has received the report from the UE (22); The method of claim 1 , comprising one of:

3. the report comprises one or more of a Data Radio Bearer (DRB) Identifier (ID), a Quality of Service (QoS) Flow ID, and a Packet Data Unit (PDU) Session ID; determining which of the first network node (16a) and the second network node (16b) carries the data for the application session based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID; The method according to claim 1 or 2.

4. The method comprises: receiving the report from the UE (22); The method of any one of claims 1 to 3, further comprising:

5. performing the one or more actions transmitting the report to the second network node (16b) when the second network node (16b) carries the data for the application session, the transmitted report being usable by the second network node (16b) to transmit and / or receive signaling related to the service type to and from the UE (22). The method of claim 4, comprising:

6. performing the one or more actions receiving the report from the second network node (16b) when the first network node (16a) carries the data for the application session, the received report being usable by the first network node (16a) to send and / or receive signaling related to the service type to and from the UE (22); 4. The method of claim 1, comprising:

7. The method comprises: The UE (22), transmitting said report to at least one of said first network node (16a) and said second network node (16b); indicating whether the quality of experience is targeted to the first network node (16a) or the second network node (16b); causing the device to be configured to do one or both of the following:

7. The method of claim 1, further comprising:

8. the first network node (16a) and the second network node (16b) are radio access network (RAN) nodes; and the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a RAN visible quality of experience (RVQoE) measurement; 8. The method of claim 1, wherein the first or second hydroxyl group is one or both of the following:

9. The method of claim 1 , wherein the reporting comprises one or more of a Quality of Experience (QoE) report and a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

10. The method comprises: receiving a capability indication from the UE (22) indicating one of the first network node (16a) and the second network node (16b) that carries the application session; 10. The method of claim 1, further comprising:

11. A first network node (16a) configured to communicate with a user equipment (UE) (22) and a second network node (16b), wherein at least the UE (22) is configurable to communicate with the first network node (16a) and the second network node (16b) using multi-radio connectivity, the first network node (16a) comprising: coordinating with the second network node (16b) to determine which of the first network node (16a) and the second network node (16b) has a report corresponding to a service type associated with the UE (22); determining which of the first network node (16a) and the second network node (16b) carries data for an application session that is subject to a quality of experience measurement associated with the report; performing one or more actions to ensure that one of the first network node (16a) and the second network node (16b) carrying the data obtains the report; and a first network node (16a) configured to:

12. The cooperation is sending a first indication to the second network node (16b) indicating that the first network node (16a) has received the report from the UE (22); receiving a second indication from the second network node (16b) indicating that the second network node (16b) has received the report from the UE (22); 12. The first network node (16a) of claim 11, comprising one of:

13. the report comprises one or more of a Data Radio Bearer (DRB) Identifier (ID), a Quality of Service (QoS) Flow ID, and a Packet Data Unit (PDU) Session ID; determining which of the first network node (16a) and the second network node (16b) carries the data for the application session based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID; A first network node (16a) according to claim 11 or 12.

14. said first network node (16a) receiving the report from the UE (22); 14. The first network node (16a) according to any one of claims 11 to 13, further configured to:

15. performing the one or more actions transmitting the report to the second network node (16b) when the second network node (16b) carries the data for the application session, the transmitted report being usable by the second network node (16b) to transmit and / or receive signaling related to the service type to and from the UE (22).

15. The first network node (16a) of claim 14, comprising:

16. performing the one or more actions receiving the report from the second network node (16b) when the first network node (16a) carries the data for the application session, the received report being usable by the first network node (16a) to send and / or receive signaling related to the service type to and from the UE (22); 14. The first network node (16a) according to any one of claims 11 to 13, comprising:

17. The first network node (16a) The UE (22), transmitting said report to at least one of said first network node (16a) and said second network node (16b); indicating whether the quality of experience is targeted to the first network node (16a) or the second network node (16b); causing the device to be configured to do one or both of the following:

17. The first network node (16a) according to any one of claims 11 to 16, further configured to:

18. the first network node (16a) and the second network node (16b) are radio access network (RAN) nodes; and the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a RAN visible quality of experience (RVQoE) measurement; 18. The first network node (16a) according to any one of claims 11 to 17, wherein the first network node (16a) is one or both of:

19. 19. The first network node (16a) of any one of claims 11 to 18, wherein the reports include one or more of a Quality of Experience (QoE) report and a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

20. said first network node (16a) receiving a capability indication from the UE (22) indicating one of the first network node (16a) and the second network node (16b) that carries the application session; 20. The first network node (16a) according to any one of claims 11 to 19, further configured to:

21. 1. A method in a user equipment (UE) (22) configured to communicate using multi-radio connectivity with a first network node (16a) and a second network node (16b), the method comprising: transmitting (S150) to one of the first network node (16 a) and the second network node (16 b) a report corresponding to a service type associated with the UE (22), the report comprising one or more of a Data Radio Bearer (DRB) Identifier (ID), a Quality of Service (QoS) flow ID, and a Packet Data Unit (PDU) Session ID, and which of the first network node (16 a) and the second network node (16 b) carries data for an application session is determined based on one or more of the DRB ID, the QoS flow ID, and the PDU Session ID; A method comprising:

22. The method comprises: determining capability indications usable by one or both of the first network node (16a) and the second network node (16b) to determine which of the first network node (16a) and the second network node (16b) carries the data for the application session that is subject to a quality of experience measurement associated with the report, and performing one or more actions to ensure that the one of the first network node (16a) and the second network node (16b) that carries the data obtains the report; sending said capability indication to one or both of said first network node (16a) and said second network node (16b); 22. The method of claim 21 further comprising:

23. When the report is sent to the first network node (16a), the one or more actions are: transmitting, by the first network node (16a), the report to the second network node (16b) when the second network node (16b) carries the data for the application session, the transmitted report being usable by the second network node (16b) to send and / or receive signaling related to the service type to and from the UE (22).

23. The method of claim 22, comprising:

24. The one or more actions include: receiving, by the first network node (16a), the report from the second network node (16b) when the first network node (16a) carries the data for the application session, the received report being usable by the first network node (16a) to send to and / or receive from the UE (22) signaling related to the service type.

23. The method of claim 22, comprising:

25. 25. The method of any one of claims 22 to 24, wherein the quality of experience measurement is one or both of a quality of experience (QoE) measurement and a radio access network (RAN) visible quality of experience (RVQoE) measurement.

26. The method comprises: Indicating whether the quality of experience is targeted to the first network node (16a) or the second network node (16b).

26. The method of any one of claims 21 to 25, further comprising:

27. 27. The method of any one of claims 21 to 26, wherein the first network node (16a) and the second network node (16b) are radio access network (RAN) nodes.

28. 28. The method of any one of claims 21 to 27, wherein the reporting comprises a Quality of Experience (QoE) report.

29. 29. The method of any one of claims 21 to 28, wherein the report comprises a Radio Access Network (RAN) Visual Quality of Experience (RVQoE) report.

30. The method comprises: determining said reporting based on one or both of a first configuration and a second configuration received from one or both of said first network node (16a) and said second network node (16b); 30. The method of any one of claims 21 to 29, further comprising:

31. A user equipment (UE) (22) configured to communicate using multi-radio connectivity with a first network node (16a) and a second network node (16b), the UE (22) comprising: causing transmission of a report corresponding to a service type associated with the UE (22) to one of the first network node (16 a) and the second network node (16 b), the report comprising one or more of a Data Radio Bearer (DRB) Identifier (ID), a Quality of Service (QoS) flow ID, and a Packet Data Unit (PDU) Session ID, and which of the first network node (16 a) and the second network node (16 b) carries data for an application session is determined based on one or more of the DRB ID, the QoS flow ID, and the PDU Session ID. A user equipment (UE) (22) configured to:

32. The UE (22) determining capability indications usable by one or both of the first network node (16a) and the second network node (16b) to determine which of the first network node (16a) and the second network node (16b) carries the data for the application session that is subject to a quality of experience measurement associated with the report, and performing one or more actions to ensure that the one of the first network node (16a) and the second network node (16b) that carries the data obtains the report; causing transmission of said capability indication to one or both of said first network node (16a) and said second network node (16b); 32. The UE (22) of claim 31, further configured to:

33. When the report is sent to the first network node (16a), the one or more actions are: transmitting, by the first network node (16a), the report to the second network node (16b) when the second network node (16b) carries the data for the application session, the transmitted report being usable by the second network node (16b) to send and / or receive signaling related to the service type to and from the UE (22).

33. The UE (22) of claim 32, comprising:

34. The one or more actions include: receiving, by the first network node (16a), the report from the second network node (16b) when the first network node (16a) carries the data for the application session, the received report being usable by the first network node (16a) to send to and / or receive from the UE (22) signaling related to the service type.

33. The UE (22) of claim 32, comprising:

35. 35. The UE (22) of any one of claims 32 to 34, wherein the quality of experience measurements are one or both of a quality of experience (QoE) measurement and a radio access network (RAN) visible quality of experience (RVQoE) measurement.

36. The UE (22) Indicating whether the quality of experience is targeted to the first network node (16a) or the second network node (16b).

36. The UE (22) of any one of claims 31 to 35, further configured to:

37. 37. The UE (22) of any one of claims 31 to 36, wherein the first network node (16a) and the second network node (16b) are radio access network (RAN) nodes.

38. 38. The UE (22) of any one of claims 31 to 37, wherein said report comprises a Quality of Experience (QoE) report.

39. 39. The UE (22) of any one of claims 31 to 38, wherein the report comprises a Radio Access Network (RAN) Visual Quality of Experience (RVQoE) report.

40. The UE (22), determining said reporting based on one or both of a first configuration and a second configuration received from one or both of said first network node (16a) and said second network node (16b); 40. The UE (22) of any one of claims 31 to 39, further configured to:

41. 31. A computer program product comprising computer program instructions for execution on a processor, said computer program instructions configured to cause said processor to perform a method according to any one of claims 1 to 10 and 21 to 30.

42. 42. A computer readable medium comprising the computer program product of claim 41.

Images