Inter-node coordination for radio access network visible quality of experience reporting in dual connectivity

Abstract

A method, system, and apparatus are disclosed. A method in a first network node configured to communicate with a user equipment (UE) and a second network node is described. At least the UE is configured to communicate with a first network node and a second network node using a multi-radio connection. 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. Further, the method comprises determining which network node of the first network node and the second network node carries data for an application session to perform a quality of experience measurement associated with the report, and performing one or more actions to ensure that one of the first and second network nodes carrying the data obtains the report.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular, to inter-node coordination for reporting in a multi-node connected environment. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for the 4th (4G) (also known as Long Term Evolution (LTE)) and 5th (5G) (also known as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communications between network nodes (such as base stations) and mobile user equipment (UE) (which may be referred to as wireless devices (WDs)), as well as communications between network nodes and communications between UEs. 3GPP is also developing standards for the 6th (6G) wireless communication systems.

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

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

[0005] In addition, the gNB may include a gNB-CU and one or more gNB-DUs. The gNB-CU and gNB-DU may be connected via the 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 the gNB-CU to which it is connected, i.e., the corresponding gNB-DUs share the same physical layer cell resources.

[0007] NOTE: To achieve resiliency, a gNB-DU can be connected to multiple gNB-CUs with appropriate implementation.

[0008] NG, Xn and F1 can be logical interfaces

[0009] For NG-RAN, the NG and Xn-C interfaces for gNBs (including gNB-CU and gNB-DU) are terminated at the gNB-CU. For dual connectivity between E-UTRA and NR (EN-DC), the S1-U and X2-C interfaces for gNBs (including gNB-CU and gNB-DU) are terminated at the gNB-CU. The gNB-CU and connected gNB-DU appear as gNBs to other gNBs and 5GC (e.g., appear as gNBs only to them).

[0010] The node hosting the user plane part of NR PDCP (e.g. gNB-CU; gNB-CU User Plane (UP); and for EN-DC, e.g. Master eNB (MeNB) or Secondary gNB (SgNB) depending on the bearer split) may perform user inactivity monitoring and also inform the nodes with C-plane connection towards the core network of its inactivity or (re)activation (e.g. via E1, X2). The node hosting NR RLC (e.g. gNB-DU) may perform user inactivity monitoring and further inform the node hosting the control plane (e.g. gNB-CU; or gNB-CU Control Plane (CP)) of its inactivity or (re)activation.

[0011] The uplink (UL) packet data control protocol (PDCP) configuration (i.e. how the UE uses the UL at the secondary node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN), and F1-C. Radio link interruption / recovery for the downlink (DL) and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN), and F1-U. NG-RAN is layered into the Radio Network Layer (RNL) and the Transport Network Layer (TNL). The NG-RAN architecture (i.e., the NG-RAN logical nodes and the interfaces between them) is defined as a part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant Transport Network Layer (TNL) protocols and functions are specified. TNL provides services for user plane transport and signaling transport.

[0012] In NG-Flex configuration, each NG-RAN node can be connected to all AMFs in the AMF Set within the Access and Mobility Function (AMF) area that supports at least one slice that is also supported by the NG-RAN node. The AMF Set and AMF Area can be the AMF Set and AMF Area defined in 3GPP TS 23.501 v17.5.0. If security protection of control plane data 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 can be applied.

[0013] Overall architecture of gNB-CU-CP and gNB-CU-UP separation

[0014] Figure 2 The example of FIG. 3 shows an overall architecture in which the gNB-CU-CP is separated from the gNB-CU-UP, and the overall architecture may be the overall architecture specified in 3GPP TS 37.483. As described above, the gNB may include one gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU via an F1-C interface. The gNB-CU-UP is connected to the gNB-DU via an F1-U interface. The gNB-CU-UP is connected to the gNB-CU-CP via 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.

[0015] NOTE 1: To achieve resiliency, a gNB-DU and / or gNB-CU-UP can be connected to multiple gNB-CU-CPs through appropriate implementation.

[0016] One gNB-DU can be connected to multiple gNB-CU-UPs controlled by the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs controlled by the same gNB-CU-CP.

[0017] NOTE 2: The gNB-CU-CP uses the bearer context management function to establish the connection between the gNB-CU-UP and the gNB-DU.

[0018] NOTE 3: The gNB-CU-CP selects the appropriate gNB-CU-UP for the service requested by the UE. In case of multiple CU-UPs, they belong to the same security domain as defined in 3GPP TS 33.210 v17.0.0.

[0019] NOTE 4: Xn-U can support data forwarding between gNB-CU-UP during intra-gNB-CU-CP handover within a gNB.

[0020] Dual Connection

[0021] In dual connectivity (DC), a UE capable of multiple transmission / reception can be connected to more than one RAN node. These RAN nodes can adopt the same radio access technology (RAT) (primary and secondary nodes are both in NR or both in LTE) or different RATs (for example, one primary LTE node and one secondary NR node). In the specification 3GPP TS 37.340 v17.1.0, the principle of multi-radio dual connectivity is described.

[0022] ===========Beginning of 3GPP TS 37.340 excerpt================

[0023] Overview

[0024] General MR-DC principles

[0025] Multi-Radio Dual Connectivity (MR-DC) is a generalization of dual connectivity (DC) within E-UTRA described in 3GPP TS 36.300, in which a UE with multiple Rx / Tx capabilities can be configured to use resources provided by two different nodes connected via a non-ideal backhaul, where one node provides NR access and the other node provides E-UTRA or NR access. One node acts as a master node (MN) and the other node acts 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.

[0026] The MN and / or SN may operate via shared spectrum channel access.

[0027] Unless otherwise specified, all functions specified for UE can be used for IAB-MT. Similar to the case specified for UE, IAB-MT can access the network using one network node or using two different nodes with EN-DC and NR-DC architectures. In EN-DC, backhaul services over the E-UTRA radio interface are not supported.

[0028] 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.

[0029] NOTE 2: All MR-DC normative text and procedures in this version of the specification show the case of aggregated nodes. Details on non-aggregated nodes for MR-DC operation are described in 3GPP TS 38.401.

[0030] MR-DC with EPC

[0031] E-UTRAN supports MR-DC via E-UTRA-NR dual connectivity (EN-DC), where the UE is connected to one eNB acting as MN and one en-gNB acting as SN. The eNB is connected to the EPC via the S1 interface and to the en-gNB via the X2 interface. The en-gNB may also be connected to the EPC via the S1-U interface and to other en-gNBs via the X2-U interface. Figure 3 The overall architecture of an example EN-DC is shown in FIG.

[0032] MR-DC with 5GC

[0033] E-UTRA-NR Dual Connectivity

[0034] NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), in which the UE is connected to one ng-eNB acting as MN and one gNB acting as SN.

[0035] NR-E-UTRA Dual Connectivity

[0036] NG-RAN supports NR-E-UTRA Dual Connectivity (NE-DC), where the UE is connected to one gNB acting as MN and one ng-eNB acting as SN.

[0037] NR-NR dual connectivity

[0038] NG-RAN supports NR-NR Dual Connectivity (NR-DC), where the UE is connected to one gNB acting as a MN and another gNB acting as a SN. In addition, NR-DC can also be used when the UE is connected to two gNB-DUs (one gNB-DU serves the MCG and the other gNB-DU serves the SCG, both gNB-DUs are connected to the same gNB-CU, acting as both MN and SN).

[0039] ============End of 3GPP TS 37.340 excerpt===============

[0040] The one or more procedures for setting up dual connectivity may be the procedures described in Chapter 10 of 3GPP TS 37.340 (which is described in Figure 4 ), that is, the second node adding process.

[0041] Overview of the QoE Framework

[0042] “Normal” QoE

[0043] Quality of Experience (QoE) measurements (also known as "application layer measurements") have been 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 certain applications. Currently QoE measurements are supported for streaming services and mobile telephony services over Internet Protocol (MTSI) services. For NR, at least VR is likely to be added to the list of services for which QoE measurements are specified and supported.

[0044] The solution in LTE and UMTS is similar, and the general principles are as follows. Quality of Experience Measurement Collection (QMC) enables the configuration of application layer measurements in the UE and the sending of QoE measurement result files (commonly referred to as QoE reports) to the network through RRC signaling. The application layer measurement configuration (also referred to as QoE measurement configuration or QoE configuration) received by the RAN from the Operation and Maintenance (OAM) system or the CN is encapsulated in a transparent container, which is forwarded to the UE in a downlink Radio Resource Control (RRC) message. The application layer measurement report (also referred to as QoE report) received by the UE Access Stratum (UE AS) or UE RRC layer from the higher layer (application layer) of the UE is encapsulated in a transparent container and sent to the network in an uplink RRC message. The RAN then forwards the QoE report to the Measurement Collector Entity (MCE).

[0045] In 3GPP Release 17, a new study project “Study of NR QoE management and optimization for multiple services” was launched for NR. The specification work for 3GPP Release 17 is still in progress. The purpose of this study project 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 typical performance requirements of multiple services (such as augmented reality / virtual reality (AR / VR) and ultra-reliable and low-latency communication (URLLC), of which at least VR seems to be covered in 3GPP Release 17). Based on the requirements of the services, NR studies also include more adaptive QoE management schemes that enable the network to be optimized to meet the user experience of multiple services.

[0046] Configuration data related to QoE measurements (usually referred to as application layer measurements in standard specifications) includes: an indication of the service type, an indication of the area where the measurements are to be performed (denoted as area scope), the IP address of the entity to which the collected measurements (i.e., QoE reports) should be sent (usually referred to as MCE, spelled Measurement Collector Entity or Measurement Collection Entity, but this entity may also sometimes be referred to as Tracking Collection Entity), and a set of instructions on what type of measurements should be performed and the details of how these measurements should be performed. These instructions are intended for the application layer in the UE (e.g., WD) and are placed in a "container" that the network entity that handles the container (e.g., forwards it to the UE) and the UE access layer cannot interpret it and will not try to read it. The service types currently specified are MTSI and streaming services (DASH), and in 3GPP Release 17, at least service type VR will be added. Area scopes are defined in terms of cells or network related areas. In UMTS, area scopes are defined as a list of cells, a list of routing areas, or a list of tracking areas. In LTE, area scopes are defined as a list of cells or a list of tracking areas. In NR, area scopes will be defined as a list of cells or a list of tracking areas.

[0047] There are two types of QoE (and specifically, QoE configuration): management-based QoE configuration and signaling-based QoE configuration. In both cases, the QoE configuration originates from the OAM system or some other management entity, such as one that handles customer satisfaction. All of these entities are referred to as the OAM system in this document (where the OAM system also contains additional entities). For management-based QoE (m-based QoE), the OAM system is typically interested in general QoE statistics from a specific area (which is configured as area-wide). The m-based QoE configuration is sent directly from the OAM system to the RAN nodes that control the cells within the area. Each RAN node then selects UEs that are within the area (and also meet any other relevant conditions, such as supporting relevant application / service types) and sends the m-based QoE configuration to these UEs.

[0048] For signaling-based QoE (s-based QoE), the OAM system is interested in collecting QoE measurements from a specific UE, for example, because the user of the UE has filed a complaint. 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), such as 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 the relevant UE, and the RAN forwards it to the UE.

[0049] The service type indication and the container with measurement instructions are forwarded to the UE. The UE is unaware whether the received QoE configuration is m-based or s-based. In traditional systems, the QoE framework is integrated with the tracing function and a tracing ID is associated with each QoE configuration. In NR, the QoE function will be logically separated from the tracing function, but the tracing signaling mechanism will still be partially reused. In NR and LTE, a globally unique QoE reference (consisting of 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 configuration. The QoE reference is included in the container with the measurement instructions and is also sent to the RAN (i.e., gNB in ​​NR). For communications between the gNB and the UE, the QoE Reference is replaced by a shorter identifier (denoted measConfigAppLayerId) that 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 stratum and is also forwarded in AT commands (which are the type of instructions used in communications between the modem part of the UE and the application layer of the UE) together with the service type indication and the container with measurement instructions.

[0050] A report with the collected QoE measurements (QoE Report) is sent from the UE Application Layer to the UE Access Layer, which forwards it to the RAN, which forwards it to the MCE. These QoE measurements are placed in a "container" that is unreadable to the UE Access Layer and the RAN. The QoE Report can be configured to be sent periodically or only at the end of an application session. In addition, the RAN can instruct the UE to suspend QoE reporting, for example in the case that the cell / gNB is overloaded.

[0051] The RAN is not aware of when an application session with an associated QoE measurement session is in progress, and the UE access layer is not automatically aware of this. To mitigate this, session start / stop indications can be introduced, which will be sent from the application layer in the UE to the UE AS, and from the UE AS to the RAN. 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 end.

[0052] As an implementation based decision, the RAN may decide to release the QoE configuration in the UE at any time. Typically this is done when the UE has moved out of the area configured for QoE measurements (often referred to as the area scope).

[0053] One opportunity offered by conventional solutions is to maintain QoE measurements for the entire session even in handover situations. It is also discussed to allow the UE to continue QoE measurements for an ongoing application session until the application session ends, even if the UE moves out of the configured area during this period.

[0054] RAN Visible QoE (RVQoE)

[0055] In NR, RAN visible QoE measurements were introduced in 3GPP Release 17. A general description can be found in 3GPP TS 38.300 v17.0.0 clause 21.4.

[0056] 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 used by the NG-RAN node for network optimization. RAN visible QoE measurements are supported for DASH streaming and VR services. The NG-RAN node configures RAN visible QoE measurements to collect all or some of the available RAN visible QoE metrics, where an indication of the availability of the metrics is received from the OAM or CN. The set of available RAN visible QoE metrics is a subset of the metrics that have been configured as part of the QoE measurement configuration encapsulated in a transparent container. Along with reporting the RAN visible QoE measurement results, the UE may also report the packet data unit (PDU) session ID corresponding to the service for which the QoE measurement is to be performed.

[0057] The request for collecting RAN-invisible QoE measurements (also referred to as OAM-QoE in R3-223290) originates from OAM and is identified by the QoE reference. The definition of this identifier can be found, for example, in 3GPP TS 28.405 v17.1.0, clause 5.2:

[0058]  The QoE Reference parameter specifies the network request session. The QoE Reference should be globally unique, so it is composed as follows:

[0059]  MCC+MNC+QMC ID, where MCC and MNC are provided with the QMC activation request from the management system to identify a PLMN containing the management system, and QMC ID is a 3-byte octet string.

[0060]  QMC ID is generated by the management system or operator.

[0061]  It is used to identify the QoE measurement collection jobs in the service nodes and measurement collection centers.

[0062] 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 Release 17), and for example in 3GPP TS 38.331, application layer measurements are identified by the MeasConfigAppLayerId IE.

[0063] In the gNB, RAN visible QoE information can be sent from the gNB-CU to the gNB-DU in the procedure described in 3GPP TS 38.473 v17.0.0. The procedure is UE-associated, i.e. it is specific to the UE.

[0064] QoE information transmission

[0065] The purpose of the QoE Information Transfer procedure is to transfer RAN visible QoE information from the gNB-CU to the gNB-DU. This procedure uses UE associated signaling. Figure 5 The QoE transmission process is shown. The gNB-CU initiates the process by sending a QOE Information Transmission message to the gNB-DU. If the QOE Information Transmission message includes the QoE Information List IE, the gNB-DU can take it into consideration according to 3GPP TS 38.300.

[0066] The gNB-CU sends a message to the gNB-DU to indicate information related to RAN-visible QoE. Direction: gNB-CU  gNB-DU. Figure 6 Two tables including parameters related to QoE information transmission are shown;

[0067] QoE Metrics

[0068] Figure 7 Typical QoE metrics are shown. This IE provides RAN-visible QoE measurement reports to the gNB-DU.

[0069] In document R3-223128 submitted to 3GPP TSG-RAN WG3 meeting #116-e, the association of RAN visible QoE reports with references is discussed:

[0070] In F1AP, a list containing the currently agreed RVQoE metrics is transmitted over F1 using UE-associated signaling. However, these reports are not associated with, for example, any reference or other ID. As a result, the gNB-DU will not be aware of the number of different application sessions providing reports, and the signaling as currently defined will therefore not be able to distinguish between QoE reports from different application sessions. Furthermore, the gNB-DU will not be able to group reports received consecutively from a given application session, and will therefore not be able to track, for example, any trends in the reported data.

[0071] A candidate reference or other ID that could resolve this issue would typically be a QoE reference or short RRC iD (measConfigAppLayerId) assigned by the UE. In the F1AP CR in R3-223131 submitted to this meeting, we recommend using a QoE reference, but the final selection may require further evaluation.

[0072] In the same submission, the following recommendations were made based on the reported discussions:

[0073] Recommendation 3: RAN3 discussed and agreed to use QoE reference or short RRC id (measConfigAppLayerId) to identify RVQoE report information on F1.

[0074] Signalling Radio Bearer (SRB)

[0075] Signaling Radio Bearers are configured in the UE and are used for the transport 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 any security is activated. SRB1 is used for most RRC messages, while SRB2 is used for NAS messages.

[0076] If the UE is configured with Dual Connectivity (DC), SRB1 is used to communicate with the Primary Node (MN). In DC, the UE may also be configured with SRB3, which is used for direct communication between the UE and the Secondary Node (SN).

[0077] For the transmission of QoE and RVQoE reports, a dedicated SRB4 has been defined. In Release 17, SRB4 is only used to send QoE and RVQoE reports to the master node in the RRC message MeasurementReportAppLayer.

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

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

[0080] According to the 3GPP specifications, the UE shall transmit QoE and RVQoE reports to the network by using SRB4. In this regard, the UE may have only established one SRB of a specific type, which means that it cannot establish SRB4 for both nodes serving it. In addition, a possible scenario is that the application session for which QoE and RVQoE measurements are to be performed is transmitted to the dual-connected UE via only one branch, where the RAN cannot control or immediately know which branch carries the application session because it does not know (or at least does not know in advance) which bearer is mapped to which application session. Therefore, the corresponding RVQoE report is only useful for one of the two RAN nodes serving the UE (the RAN node that transmits the data of the application session to the UE), while the RVQoE report will be useless for the other RAN node serving the UE, even if that RAN node is the node that configures RVQoE measurements for the UE.

[0081] In other words, it is unclear how to ensure that the "correct" RAN node (of the two RAN nodes serving the UE in NR-DC) receives the RVQoE report. Note that even if a UE in NR-DC is allowed to establish SRB4 to both RAN nodes serving it, the problem will still exist.

[0082] Furthermore, the RAN node may configure RVQoE measurements for the UE only if the UE is also configured with corresponding QoE measurements, which actually means that the RAN node may configure RVQoE measurements for the UE only if the OAM approves it.

[0083] Another aspect to consider is that although the UE is configured with only one SRB4, it may have received multiple RVQoE configurations corresponding to different service types from different RAN nodes (e.g. it has received 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 corresponding service type for which the RVQoE configuration issued by that node to the UE is intended (in the 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

[0084] Some embodiments advantageously provide methods, systems, and apparatus for inter-node coordination of reporting in a multi-node connection environment. In some embodiments, a mechanism (i.e., method) is described. The method enables RAN nodes (i.e., network nodes) serving UEs in NR-DC or any other multi-radio connection setting to perform at least one of the following operations: coordination; informing each other which of them has configured RVQoE measurements for a particular service type; identifying which of these RAN nodes is carrying a data application session for which RVQoE measurements related to the particular service type are to be performed; and forwarding a corresponding RVQoE report to the data node carrying the application session for which RVQoE measurements are to be performed.

[0085] In some other embodiments, the UE is configured to send one or more reports to the relevant node (ie, the network node), or is configured to let the UE indicate which node is the target recipient of RVQoE. A mechanism for the RAN node to obtain UE capabilities (regarding the solution proposed in the present invention) is described.

[0086] For a UE in NR-DC, one or more embodiments ensure that RVQoE reports related to a specific service type are forwarded to the correct location, i.e., to a RAN node that is able to utilize the reports, i.e., the node that transmits data for an application session to be measured for RVQoE to the UE.

[0087] In some embodiments, the UE and RAN nodes in the DC are configured to infer which serving RAN node carries the data for the application session for which RVQoE measurements are to be made, which makes it possible, for example, to forward RVQoE reports to the correct node.

[0088] According to one aspect, a method in a first network node is described, the first network node being configured to communicate with a user equipment (UE) and a second network node. At least the UE is configured to communicate with the first network node and the second network node using a multi-radio connection. 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 for which a quality of experience measurement associated with the report is to be performed, 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.

[0089] 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.

[0090] 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 network node of the first network node and the second network node carries the data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0091] In some embodiments, the method further comprises receiving the report from the UE.

[0092] In some other embodiments, performing one or more actions includes: sending the report to the second network node when the second network node carries data for the application session. The sent report can be used by the second network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0093] In some embodiments, performing one or more actions includes: receiving the report from the second network node when the first network node carries data for the application session. The received report can be used by the first network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0094] In some other embodiments, the method further comprises causing the UE to be configured to perform one or both of: sending the report to at least one of the first network node and the second network node, and indicating to which network node of the first network node and the second network node the quality of experience is directed.

[0095] In some embodiments, one or both of 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 measurement (QoE) measurement and a RAN visible quality of experience (RVQoE) measurement.

[0096] 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.

[0097] In some embodiments, the method further comprises receiving a capability indication from the UE, the capability indication indicating which of the first network node and the second network node hosts the application session.

[0098] According to another aspect, a first network node configured to communicate with a user equipment (UE) and a second network node is described. At least the UE is configured to communicate with the first network node and the second network node using a multi-radio connection. 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 for which a quality of experience measurement associated with the report is to be made, and 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.

[0099] 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.

[0100] 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 network node of the first network node and the second network node carries the data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

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

[0102] In some other embodiments, performing one or more actions includes: sending the report to the second network node when the second network node carries data for the application session. The sent report can be used by the second network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0103] In some embodiments, performing one or more actions includes: receiving the report from the second network node when the first network node carries data for the application session. The received report can be used by the first network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0104] In some other embodiments, the first network node is further configured to cause the UE to be configured to perform one or both of: sending the report to at least one of the first network node and the second network node, and indicating which network node of the first network node and the second network node the quality of experience is for.

[0105] In some embodiments, one or both of 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 measurement (QoE) measurement and a RAN visible quality of experience (RVQoE) measurement.

[0106] 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.

[0107] In some embodiments, the first network node is further configured to receive a capability indication from the UE, the capability indication indicating which of the first network node and the second network node is to host the application session.

[0108] According to one aspect, a method in a user equipment (UE) configured to communicate with a first network node and a second network node using a multi-radio connection is described. The method includes sending 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. Based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID, it is determined which network node of the first network node and the second network node carries data for an application session.

[0109] In some embodiments, the method further comprises determining a capability indication that can be used 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 for which a quality of experience measurement associated with the report is to be made and performing one or more actions to ensure that the one of the first network node and the second network node carrying the data obtains the report. The method further comprises sending the capability indication to one or both of the first network node and the second network node.

[0110] In some other embodiments, when the report is sent to the first network node, the one or more actions include: when the second network node carries data of the application session, the first network node sends the report to the second network node. The sent report can be used by the second network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0111] In some embodiments, the one or more actions include: when the first network node carries data for the application session, the first network node receives the report from the second network node. The received report can be used by the first network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

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

[0113] In some embodiments, the method further comprises indicating to which network node of the first network node and the second network node the quality of experience is directed.

[0114] In some other embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes.

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

[0116] In some other embodiments, the report comprises a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

[0117] In some embodiments, the method further comprises determining the report 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.

[0118] According to another aspect, a user equipment (UE) is configured to communicate with a first network node and a second network node using a multi-radio connection. The UE is configured to cause a report corresponding to a service type associated with the UE to be sent 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. Based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID, it is determined which network node of the first network node and the second network node carries data for an application session.

[0119] In some embodiments, the UE is further configured to determine a capability indication that can be used 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 for which quality of experience measurement associated with the report is to be made 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 the capability indication to be sent to one or both of the first network node and the second network node.

[0120] In some other embodiments, when the report is sent to the first network node, the one or more actions include: when the second network node carries data of the application session, the first network node sends the report to the second network node. The sent report can be used by the second network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0121] In some embodiments, the one or more actions include: when the first network node carries data for the application session, the first network node receives the report from the second network node. The received report can be used by the first network node to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

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

[0123] In some embodiments, the UE is further configured to indicate which network node of the first network node and the second network node the quality of experience is for.

[0124] In some other embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes.

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

[0126] In some other embodiments, the report comprises a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

[0127] In some embodiments, the UE is further configured to determine the report 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. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0129] Figure 1 shows the overall architecture of NG-RAN;

[0130] Figure 2 The overall architecture of the separation of gNB-CU-CP and gNB-CU-UP is shown;

[0131] Figure 3 The overall architecture of EN-DC is shown;

[0132] Figure 4 The second node adding process is shown;

[0133] Figure 5 The QoE transmission process is shown;

[0134] Figure 6 Two tables including parameters related to QoE information transmission are shown;

[0135] Figure 7 Typical QoE metrics are shown;

[0136] Figure 8 is a schematic diagram illustrating an example network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0137] Fig. 9 is a block diagram of a host computer communicating with a user device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0138] Fig.10 is a flow chart illustrating an example method for executing a client application at a user device implemented in a communication system including a host computer, a network node, and a user device according to some embodiments of the present disclosure;

[0139] Fig.11is a flow chart illustrating an example method for receiving user data at a user equipment implemented in a communication system including a host computer, a network node, and a UE according to some embodiments of the present disclosure;

[0140] Fig.12 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a user device for receiving user data from a user device at a host computer according to some embodiments of the present disclosure;

[0141] Fig.13 is a flow chart illustrating an example method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a user device according to some embodiments of the present disclosure;

[0142] Fig.14 is a flow chart of an example process in a network node according to some embodiments of the present disclosure;

[0143] Fig.15 is a flow chart of an example process in a user device according to some embodiments of the present disclosure;

[0144] Fig.16 is a flowchart of another example process in a network node according to some embodiments of the present disclosure; and

[0145] Fig.17 is a flow chart of another example process in a user device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0146] Before describing the example embodiments in detail, it is noted that the embodiments reside primarily in a combination of device components and processing steps related to inter-node coordination (e.g., inter-node coordination for reporting in a multi-node connection environment). Therefore, components are appropriately 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 are obvious to those of ordinary skill in the art having the benefit of the description herein. Throughout the specification, similar numerals refer to similar elements.

[0147] The relational terms used herein (such as "first" and "second", "top" and "bottom", etc.) may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between these entities or elements. The terms used herein are only for the purpose of describing specific embodiments, not for limiting the concepts described herein. Unless the context clearly indicates the contrary, the singular forms "one", "an" and "said" as used herein are intended to also include plural forms. It will also be understood that the terms "including", "having" and / or "comprising" when used herein indicate 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 combinations thereof.

[0148] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical communication or data communication, which 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 may be implemented for electrical and data communications.

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

[0150] The term "network node" used herein may be any type of network node (and / or node) included in a radio network, and the network node may also include any of a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a g-node B (gNB), an evolved node B (eNB or eNodeB), a node B, a multi-standard radio (MSR) radio node (such as an MSR BS), a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlled relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobility management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. 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.

[0151] In some embodiments, the non-limiting terms user equipment (UE) or wireless device (WD) may be 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 radio signals, such as a user equipment (UE). A UE may also be a radio 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 with a UE, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter or 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 is not limited to a specific type of wireless device.

[0152] In addition, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, including any of 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), and a remote radio head (RRH).

[0153] In one or more embodiments, one or more of the following may apply:

[0154]  The solution in this paper is described using two RAN nodes serving UE in NR-DC as an example, but it can be generalized to any number of nodes serving UE simultaneously.

[0155] The solution in this article is described using NR-DC as an example, but it can also be generalized to Multi-Radio Dual Connectivity (MR-DC) or connectivity options with more than two RAN nodes.

[0156]  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, note that "QMC configuration file" is not an equivalent term, but refers to the part of the QoE configuration that consists of an XML file containing instructions for the QoE metrics to be collected, etc.

[0157]  All references to the application layer are to the UE’s application layer (since the RAN node does not have an application layer).

[0158]  The term “service” is often used as shorthand for “type of service.” So, for example, “service” and “type of service” are used interchangeably unless explicitly stated otherwise.

[0159] The solution proposed in this invention can be applicable to both signaling-based QoE measurement and management-based QoE measurement (but can also be optionally restricted to only apply to one of them).

[0160]  The terms “QoE report” and “QoE measurement report” are used interchangeably. Similarly, the terms “RAN seen QoE report”, “RAN seen QoE measurement report”, “RVQoE report” and “RVQoE measurement report” are used interchangeably.

[0161]  The terms "access stratum" and "radio layer" are used interchangeably when referring to the UE.

[0162]  The term "session" can refer to a QoE measurement session or an application session or an application session to which QoE measurement is applied.

[0163]  The term "session" can refer to a QoE measurement session or an application session or an application session to which QoE measurement is applied.

[0164]  The solution proposed in this invention is applicable to UMTS, LTE and NR as well as future RATs (such as 6G).

[0165]  This solution is described using management-based QoE measurements (ie, their corresponding RVQoE measurements) as an example, but it is equally applicable to both management-based QoE measurements and signaling-based QoE measurements and their corresponding RVQoE measurements.

[0166] Note that although terminology from one particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in the present disclosure, this should not be viewed as limiting the scope of the present 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 concepts encompassed within the present disclosure.

[0167] It should also be noted that the functions described herein as being performed by a user equipment or network node may be distributed across multiple user equipments (UEs) and / or network nodes. In other words, it is contemplated that the functions of the network nodes and user equipment described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.

[0168] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. It will be understood that the terms used herein should be interpreted as being consistent with their meanings in the context of this specification and the relevant art, and not interpreted as ideal or overly formal meanings, unless so explicitly defined herein.

[0169] Referring again to the drawings, in which like elements are referred to by like reference numerals, Figure 8 , a schematic diagram of a communication system 10 according to an embodiment is shown, for example, a 3GPP type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network (such as a radio access network) 12 and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of radio access points, each of which defines 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 via a wired or wireless connection 20. A first user equipment (UE) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16a or to be paged by the corresponding network node 16a. A second UE 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16b. Although multiple UEs 22a, 22b (collectively referred to as UE 22) are shown in this example, the disclosed embodiments are also applicable to the case where a single UE is within the coverage area or a single UE is connected to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include more UEs 22 and network nodes 16.

[0170] Additionally, it is contemplated that the UE 22 may communicate simultaneously with more than one network node 16 and more than one type of network node 16 and / or be configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, the UE 22 may have dual connectivity with a network node 16 supporting LTE and the same or different network nodes 16 supporting NR. For example, the UE 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0171] The communication system 10 itself may be connected to a host computer 24, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the telecommunications network 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 a public network, a private network, or a combination of one or more of a servo network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more sub-networks (not shown).

[0172] Figure 8 The communication system as a whole implements a connection between one of the connected UEs 22a, 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected UEs 22a, 22b are configured to send data and / or signaling via the OTT connection using the access network 12, the core network 14, any intermediate networks 30, and possible other intermediate infrastructures (not shown). At least some of the participating communication devices through which the OTT connection passes do not know the routing of the uplink and downlink communications, and in this sense, the OTT connection can be transparent. For example, the network node 16 may not be informed or need not be informed of the past routing of incoming downlink communications, which have data originating from the host computer 24 and to be forwarded (e.g., handed over) to the connected UE 22a. Similarly, the network node 16 does not need to know the future routing of the outgoing uplink communications originating from the UE22a and toward the host computer 24.

[0173] The network node 16 is configured to include a NN coordination unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, sending information to the second network node about which of the first network node and the second network node has configured experience quality measurement of a predetermined service type associated with the UE; and / or determining which of the first network node and the second network node carries data of an application session for which experience quality measurement of the predetermined service type is to be performed; and / or when the second network node carries data of an application session for which experience quality measurement is to be performed, forwarding an experience quality report corresponding to the application session to the second network node. The user equipment 22 is configured to include a UE coordination unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining that data of an application session for which quality of experience measurement of a predetermined service type associated with the UE 22 is to be performed is carried by the second network node; and / or at least sending an indication to the first network node 16a, the indication indicating that data of an application session for which quality of experience measurement of a predetermined service type is to be performed is carried by the second network node, and the indication can be used by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0174] Now refer to Fig. 9 An example implementation according to an embodiment of the UE 22, the network node 16, and the host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. Specifically, as a supplement or alternative to a processor (such as a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to or read from) a 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).

[0175] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein, and / or cause these methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, program 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. These instructions may be software associated with host computer 24.

[0176] The software 48 can be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 can be operated to provide services to a remote user, such as a UE 22 connected via an OTT connection 52, which is terminated at the UE 22 and the host computer 24. When providing services to the remote user, the host application 50 can provide user data sent using the OTT connection 52. "User data" can be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 can be configured to provide control and functionality to a service provider and can be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control, send to and / or receive from the network node 16 and / or the user device 22. The processing circuitry 42 of the host computer 24 may include a host coordination unit 54 configured to enable a service provider to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as observing / monitoring / controlling the network nodes 16 and / or user devices 22, sending to / receiving from the network nodes 16 and / or user devices 22.

[0177] The communication system 10 also includes a network node 16 disposed in the communication system 10, the network node 16 including hardware 58 that enables it to communicate with the host computer 24 and the UE 22. The hardware 58 may include: a communication interface 60 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 10; and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the UE 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 with the host computer 24. The connection 66 may be direct, or it may be through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0178] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. Specifically, as a supplement or alternative to a processor (such as a central processing unit) and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 70 may be configured to access (e.g., write to or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0179] Therefore, the network node 16 also has software 74 stored internally, for example, in the memory 72 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any method and / or process described herein, and / or cause these methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the process described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a UE coordination unit 34 that performs any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as sending information to the second network node about which of the first network node and the second network node has configured experience quality measurement of a predetermined service type associated with the UE; and / or determining which of the first network node and the second network node carries data for an application session for which experience quality measurement of the predetermined service type is to be performed; and / or when the second network node carries data for an application session for which experience quality measurement is to be performed, forwarding an experience quality report corresponding to the application session to the second network node.

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

[0181] The hardware 80 of the UE 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. Specifically, as a supplement or alternative to a processor (such as a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access (e.g., write to or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0182] Therefore, the UE 22 may also include software 90, which is stored in a memory 88 at, for example, the UE 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the UE 22. The software 90 may be executed by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operated to provide services to human or non-human users via the UE 22 with the support of the host computer 24. In the host computer 24, the executing host application 50 may communicate with the executing client application 92 via the OTT connection 52, which is terminated at the UE 22 and the host computer 24. When 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 send both request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0183] The processing circuit 84 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 the UE 22. The processor 86 corresponds to one or more processors 86 for performing the functions of the UE 22 described herein. The UE 22 includes a memory 88 configured to store data, program 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 circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein with respect to the UE 22. For example, the processing circuit 84 of the user equipment 22 may include a UE coordination unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining that data of an application session for which quality of experience measurement of a predetermined service type associated with the UE 22 is to be performed is carried by the second network node; and / or at least sending an indication to the first network node, the indication indicating that data of an application session for which quality of experience measurement of a predetermined service type is to be performed is carried by the second network node, and the indication may be used by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0184] In some embodiments, the internal workings of the network node 16, UE 22, and host computer 24 may be as follows: Fig. 9 shown, and independently, the surrounding network topology can be Figure 8 network topology.

[0185] exist Fig. 9 , an OTT connection 52 is abstractly depicted to illustrate communications between a host computer 24 and a user device 22 via a network node 16, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 22 or the service provider operating the host computer 24, or both. When the OTT connection 52 is active, the network infrastructure may further make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0186] The wireless connection 64 between the UE 22 and the network node 16 follows the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 may form the final part. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, extended battery life, and the like.

[0187] In some embodiments, a measurement process may be provided for monitoring data rate, latency, and other factors that are the subject of improvement of one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 52 between the host computer 24 and the UE 22 in response to changes in the measurement results. The measurement process and / or the network function 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 in both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above, or providing the values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and the network node 16 may be unknown or imperceptible to this. Some of these processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 24 to measure throughput, propagation time, latency, etc. In some embodiments, the measurements may be accomplished by the software 48, 90 sending messages (particularly empty or "dummy" messages) using the OTT connection 52 while monitoring propagation time, errors, etc.

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

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

[0190] although Figure 8and Fig. 9 Various "units" such as NN coordination unit 32 and UE coordination unit 34 are shown as being within respective processors, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or a combination of hardware and software.

[0191] Fig.10 is a diagram showing a communication system (eg, Figure 8 and Fig. 9 The communication system may include a host computer 24, a network node 16, and a UE 22, which may be a reference Fig. 9 The host computer 24, the network node 16 and the UE 22 described in the present disclosure are described. 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 (e.g., the host application 50) (block S102). In a second step, the host computer 24 initiates a transmission to the UE 22, the transmission carrying the user data (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the UE 22 (block S106). In an optional fourth step, the UE 22 executes a client application (e.g., the client application 92) associated with the host application 50 executed by the host computer 24 (block S108).

[0192] Fig.11 is a diagram showing a communication system (eg, Figure 8 The communication system may include a host computer 24, a network node 16, and a UE 22, which may be a reference Figure 8 and Fig. 9 The host computer 24, the network node 16 and the UE 22 described in the embodiment of the present disclosure are described. In the 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 (e.g., the host application 50). In the second step, the host computer 24 initiates a transmission to the UE 22, the transmission carrying the user data (block S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can be transmitted via the network node 16. In the optional third step, the UE 22 receives the user data carried in the transmission (block S114).

[0193] Fig.12is a diagram showing a communication system (eg, Figure 7 The communication system may include a host computer 24, a network node 16, and a UE 22, which may be a reference Figure 8 and Fig. 9 The host computer 24, the network node 16 and the UE 22 described in the embodiment of the present invention are described. In the optional first step of the method, the UE 22 receives input data provided by the host computer 24 (box S116). In the optional sub-step of the first step, the UE 22 executes the client application 92, which provides user data in response to the received input data provided by the host computer 24 (box S118). Additionally or alternatively, in the optional second step, the UE 22 provides user data (box S120). In the optional sub-step of the second step, the UE provides user data by executing a client application (e.g., the client application 92) (box S122). When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE 22 may initiate a user data transmission to the host computer 24 in the optional third sub-step (box S124). In the fourth step of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer 24 receives the user data sent from the UE 22 (box S126).

[0194] Fig.13 is a diagram showing a communication system (eg, Figure 3 The communication system may include a host computer 24, a network node 16, and a UE 22, which may be a reference Figure 8 and Fig. 9 1 . The host computer 24, the network node 16 and the UE 22 described herein are described. In an optional first step of the method, the network node 16 receives user data from the UE 22 in accordance with the teachings of the embodiments described throughout the present disclosure (block S128). 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 the transmission initiated by the network node 16 (block S132).

[0195] Fig.141 is a flow chart of an example process in a network node 16 (e.g., a first network node 16a). One or more blocks described herein may be performed by one or more units of the network node 16, such as by one or more of the processing circuit 68 (including the NN coordination unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 (such as via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60) is configured to send (block S134) to the second network node 16b information about which of the first network node 16a and the second network node 16b has configured the experience quality measurement of the predetermined service type associated with the UE 22; determine (block S136) which of the first network node 16a and the second network node 16b carries data of an application session for which the experience quality measurement of the predetermined service type is to be performed; and when the second network node 16b carries data of the application session for which the experience quality measurement is to be performed, forward (block S138) the experience quality report corresponding to the application session to the second network node 16b.

[0196] In some embodiments, the method further comprises configuring the UE 22 to perform at least one of: sending a quality of experience report to at least one of the first network node 16a and the second network node 16b; and indicating to which network node the quality of experience is directed.

[0197] In some other embodiments, at least one of the following exists: the first network node 16a and the second network node 16b are radio access network (RAN) nodes; the UE 22 may be configured 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 a RVQoE report.

[0198] Fig.15is a flow chart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more units of the user equipment 22, such as by one or more of the processing circuit 84 (including the UE coordination unit 34), the processor 86, the radio interface 82 and / or the communication interface 60. The user equipment 22 (such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82) is configured to determine (block S140) that data of an application session for which quality of experience measurement of a predetermined service type associated with the UE 22 is to be performed is carried by the second network node 16b; and to send (block S142) an indication to at least the first network node 16a. The indication indicates that data of the application session for which quality of experience measurement of the predetermined service type is to be performed is carried by the second network node 16b. The indication may be used by the first network node 16a to forward a quality of experience report corresponding to the application session to the second network node 16b.

[0199] 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.

[0200] In some other embodiments, at least one of the following exists: the first network node 16a and the second network node 16b are radio access network (RAN) nodes; the UE 22 may be configured 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 a RVQoE report.

[0201] Fig.1614 is a flow diagram of an example process in a network node 16 (e.g., a first network node 16a). One or more blocks described herein may be performed by one or more units of the network node 16, such as by one or more of the processing circuit 68 (including the NN coordination unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 (e.g., the first network node 16a) (e.g., via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60) is configured to coordinate (block 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, and to determine (block S142) which of the first network node 16a and the second network node 16b carries data for an application session for which quality of experience measurement associated with the report is to be performed. The network node 16 (eg, the first network node 16a) is further configured to perform 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.

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

[0203] 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 network node of the first network node 16a and the second network node 16b carries the data for the application session is based on one or more of the DRB ID, the QoS flow ID, and the PDU session ID.

[0204] In some embodiments, the method further comprises receiving the report from the UE.

[0205] In some other embodiments, performing one or more actions includes: sending the report to the second network node 16b when the second network node 16b carries data for the application session. The sent report can be used by the second network node 16b to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

[0206] In some embodiments, performing one or more actions includes: receiving the report from the second network node 16b when the first network node 16a carries data for the application session. The received report can be used by the first network node 16b to send signaling associated with the service type to the UE and / or receive signaling associated with the service type from the UE.

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

[0208] In some embodiments, one or both of 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.

[0209] 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.

[0210] In some embodiments, the method further comprises receiving a capability indication from the UE, the capability indication indicating which of the first network node 16a and the second network node 16b hosts the application session.

[0211] Fig.17 1 is a flow chart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more units of the user equipment 22, such as by one or more of the processing circuit 84 (including the UE coordination unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The user equipment 22 (such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82) is configured to send (block S150) a report corresponding to a service type associated with the UE 22 to one of the first network node 16a and the second network node 16b, the report including 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, wherein which network node 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.

[0212] In some embodiments, the method further comprises determining a capability indication that can be used 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 data for an application session for which a quality of experience measurement associated with the report is to be made and performing one or more actions to ensure that the one of the first network node 16a and the second network node 16b carrying the data obtains the report. The method further comprises sending the capability indication to one or both of the first network node 16a and the second network node 16b.

[0213] In some other embodiments, in the case where the report is sent to the first network node 16a, the one or more actions include: when the second network node 16b carries data for the application session, the first network node 16a sends the report to the second network node 16b. The sent report can be used by the second network node 16b to send signaling associated with the service type to the UE 22 and / or receive signaling associated with the service type from the UE 22.

[0214] In some embodiments, the one or more actions include: when the first network node 16a carries data for the application session, receiving the report from the second network node 16b by the first network node 16a. The received report can be used by the first network node 16b to send signaling associated with the service type to the UE 22 and / or receive signaling associated with the service type from the UE 22.

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

[0216] In some embodiments, the method further comprises indicating to which network node of the first network node 16a and the second network node 16b the quality of experience is directed.

[0217] In some other embodiments, the first network node 16a and the second network node 16b are Radio Access Network (RAN) nodes.

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

[0219] In some other embodiments, the report comprises a Radio Access Network (RAN) Visible Quality of Experience (RVQoE) report.

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

[0221] Having described the general processing flow of the arrangements of the present disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following sections provide details and examples of arrangements for inter-node coordination (e.g., inter-node coordination for reporting in a multi-node connected environment).

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

[0223] First example solution: UE-based solution

[0224] The first approach includes at least one of the following steps:

[0225] 1. The UE 22 establishes an NR-DC to the first network node 16a and the second network node 16b, which play the roles of MN and SN, respectively, or play the roles of SN and MN, respectively.

[0226] 2. A network entity (e.g., OAM) assembles a management-based QoE measurement configuration (referred to herein as the first configuration) and transmits it to multiple RAN nodes in the area, including the first network node 16a and the second network node 16b. The first network node 16a configures QoE measurements for a service (i.e., the first service) for the UE 22 according to the first configuration, configures RVQoE measurements at the UE 22 according to the second configuration, and sets up SRB4 towards the UE 22. Note that the UE 22 can only establish one SRB towards the network for each SRB type, which means that in the scenario discussed, unless reconfigured, SRB4 is always established towards either the first network node 16a or the second network node 16b, but not both at the same time. The UE 22 activates an application session for the service (i.e., the first service), which triggers QoE and RVQoE measurements at the UE 22 and their reporting.

[0227] a. In case of signaling-based (s-based) QoE, the QoE configuration is delivered from the OAM to the MN via the core network.

[0228] b. In 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 the OAM), for example because they are both within the area scope of the first configuration or the configured PLMN.

[0229] 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 use it to configure 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 SRB4 towards the UE 22.

[0230] In one solution, one node (usually the master node) decides to configure SRB4 as a split bearer. This means that the UE 22 splits the transmission between the first network node 16a and the second network node 16b. In existing solutions, the splitting is based on the amount of data to be sent. Here, some new criteria can be defined on how the UE 22 splits the transmission. As an example, the splitting can be based on whether the data is for the service of the first network node 16a or for the service of the second network node 16b. If the data is for the service of the first network node 16a, the UE 22 sends the data on the branch to the first network node 16a, and if the data is for the service of the second network node 16b, the UE 22 sends the data on the branch to the second network node 16b. The case of split transmission can be that data related to the VoNR service is sent to the first network node 16a, and data related to the streaming transmission is sent to the second network node 16b according to the configuration provided to at least one of the first node 16a or the second node 16b. An additional criterion is that one of the branches is prioritized, or always used instead of the other branch, until the node corresponding to the prioritized branch detects an overload (or near overload) condition. For example, SRB4 is configured to split the bearer, and the prioritized branch corresponds to the node (e.g., MN) for which SRB4 is configured. According to the configuration provided, the UE 22 uses the MN branch to send data. When the MN detects an overload (e.g., the MN detects that too much data has arrived over SRB4 in a given time period), the MN reconfigures SRB4 so that the UE 22 will now send data associated with the QoE / RVQoE report via another branch.

[0231] In another solution, one node (usually the master node) decides to configure SRB4 as a duplicate bearer. This means that data is sent to both the first network node 16a and the second network node 16b. Each node can then determine whether the data is for the service of that particular node or for the service of other nodes, and obtain the relevant data for its own node.

[0232] In an alternative solution, the first network node 16a and the second network node 16b are allowed to send messages carrying RVQoE reports (e.g., MeasurementReportAppLayer) through different SRBs, that is, different SRBs are defined. This may include: using SRB4 in the first network node 16a, and using SRB1, SRB3, or a new SRB5 in the second network node 16b. One of the SRBs may be defined as a primary node bearer, and the other SRB may be defined as a secondary node bearer, or both may be defined as primary node bearers or both may be defined as secondary node bearers.

[0233] In another example solution, the same SRB is used for RVQoE reporting for both the first node and the second node, but possibly with an indication from the UE 22 indicating which node the report is for, see step 4.

[0234] a. During performance of one of the procedures related to multi-connectivity operation, the first network node 16a and the second network node 16b may inform each other whether they have received the first configuration and whether they plan to configure the UE 22 with it, in which one of the procedures, the UE 22 is reconfigured from a single connection to multiple connections (e.g., secondary node addition), or the UE 22 is reconfigured from a first configuration in multiple connections to a second configuration in multiple connections (e.g., secondary node modification - MN initiated or SN initiated secondary node modification, secondary node change - MN initiated or SN initiated secondary node change, inter-MN handover with / without SN change).

[0235] b. One of the nodes involved in NR-DC (or MR-DC) instructs / requests another node to forward RVQoE reports related to the services they have provided corresponding RVQoE configurations to UE22, and the instruction / request is performed through new or existing procedures.

[0236] i. In one case, 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 scope. The node (MN node or SN node) that receives the m-based configuration can configure the UE 22 for RVQoE and instruct / request the other node (SN or MN, respectively) to forward the RVQoE report to it.

[0237] ii. In another case, one of the nodes (usually the MN node) has configured the UE 22 to collect RVQoE for the first service according to the s-based QoE configuration. In this case, the MN is not included in the area range associated with the m-based QoE configuration, while the other node (SN) is included in the area range associated with the m-based QoE configuration. The other node (SN) configures the UE 22 to collect RVQoE for the second service. The MN instructs / requests the SN to forward the RVQoE report associated with the first service to it; the SN instructs / requests the MN to forward the RVQoE report associated with the second service to it.

[0238] 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 determines to prepare a RVQoE configuration for the UE 22. For example, in the case of the first network node 16a, the first network node 16a may inform the second network node 16b that it has configured the UE 22 for RVQoE and is interested in receiving RVQoE reports. In this way, the second network node 16b will know that future RVQoE reports of the UE 22 received at the second network node 16b need to be sent to the first network node 16a. There may be a race condition where both the first network node 16a and the second network node 16b may attempt to configure the UE 22 with the same RVQoE configuration. In this case, one sub-case is that the latest configuration overwrites the old configuration (no RVQoE configuration modification is allowed). In another sub-case, each node will receive an indication from the other node that the other node is interested in receiving RVQoE reports. In another sub-case, the node that is the last of the two nodes to send the RVQoE configuration to the UE 22 is the node that receives the RVQoE report. In another sub-case, the node that sends the RVQoE configuration before the other node is the node that receives the RVQoE report.

[0239] c. One or more nodes, when removed from the NR-DC (or MR-DC) configuration, instruct / request another node to receive RVQoE reports related to the services for which they have provided the corresponding RVQoE configuration to the UE 22, and the instruction / request is made through a new or existing procedure.

[0240] It may be assumed that the first network node 16a has configured QoE measurements and RVQoE measurements for the UE 22, and has established SRB4 towards the UE 22. This is a non-limiting example, for example, because there may be a situation where the second network node 16b has configured the first configuration and the second configuration towards the UE 22. At this point, both nodes do not know which of them carries the data for the application session for the first service.

[0241] 4. The UE 22 is aware that the data for the first service is carried via the second network node 16b. This may be done by the UE access stratum (AS) layer based on the knowledge of the DRB ID, QoS flow ID, or PDU session ID of the application session and the corresponding connection leg. Note that as part of the DC setup process, the MN indicates to the SN the available DRB IDs that the SN can use for SCG-terminated DRBs, thereby ensuring the uniqueness of the DRB IDs established in the DC towards the UE 22. Alternatively or in combination therewith, the UE 22 may also use one of the following methods (one of the methods described in the section “How the UE identifies the leg carrying the application data flow”) to identify the connection leg. The UE 22 previously knew that the SRB4 was established towards the first network node 16a. Therefore, the UE 22 sends an indication to the first network node 16a that the data for the application session is carried via the second network node 16b, which means that the second network node 16b should receive the RVQoE report carried from the UE 22 to the first network node 16a via the SRB4.

[0242] Alternatively, the UE 22 may send an indication along with the RVQoE report about which node the report is for. The indication may be sent all the time, or only in certain circumstances, such as when the report is for another node, when the target node has been changed since the last report, and so on.

[0243] 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 informing it that the RVQoE report according to the second configuration is related to the leg between the UE 22 and the second network node 16b.

[0244] a. In one variant, the indication from the first network node 16a to the second network node 16b may be a notification of the above (indication A).

[0245] b. In another variant, the indication may be a query (intention survey) to the second network node 16b as to whether the second network node 16b is interested in receiving RVQoE reports from the UE 22 via the first network node 16a (indication B).

[0246] c. In another variant, the indication may be a query “asking” the second network node 16b to provide RVQoE measurement parameters at the UE 22 (indication C).

[0247] d. Any indication may include a request to the second network node 16b to set up the SRB4 towards the UE 22.

[0248] e. Note that the above does not depend on whether both the first network node and the second network node 16b are within the area scope of the first configuration and the second configuration.

[0249] f. Note that the above is also valid for the case where one of the nodes used for the NR-DC (or MR-DC) connection and configured RVQoE for UE 22 is later removed from the UE 22 configuration (e.g., UE 22 is reconfigured from multiple connections to single connection, or UE 22 is reconfigured with a different NR-DC (or MR-DC) configuration).

[0250] 6. The second network node 16b responds to the indication received in step 5 from the first network node 16a.

[0251] a. In case the second network node 16b receives indication A, the second network node 16b may acknowledge the receipt.

[0252] b. In case the second network node 16b receives indication B, the second network node 16b may reply whether it is interested in receiving the RVQoE report received from the UE 22 related to the second configuration from the first network node 16a.

[0253] i. In case the second network node 16b is interested in receiving RVQoE reports, it may also indicate to the first network node 16a whether it requests that SRB4 be set up between the UE 22 and the second network node 16b, rather than between the first network node 16a and the UE 22. i.

[0254] ii. In the event that 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.

[0255] c. In case the second network node 16b receives indication C, the second network node 16b may indicate the desired RVQoE configuration parameters.

[0256] 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):

[0257] a. If the second network node 16b acknowledges receipt of indication A, the first network node 16a may from now on forward RVQoE reports related to the second configuration received from the UE 22 to the second network node 16b. Alternatively, the first network node 16a may decide to request the second network node 16b to establish an SRB4 towards the UE 22, and 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 retain the SRB4 with the UE 22, but may instruct the UE 22 to send RVQoE reports to the second network node 16b via an already established SRB (e.g., SRB3).

[0258] b. If the second network node 16b replies that it is interested in receiving the RVQoE report based on the received indication B, the first network node 16a may perform one or more actions described in point a of this step (step 7).

[0259] c. In the event that the second network node 16b replies with a desired RVQoE measurement configuration different from the current second configuration based on the received indication C, the first network node 16a may modify the second configuration accordingly.

[0260] The RVQoE report may be transmitted to the second network node 16b based on the actions performed in at least one of steps 1 to 7 .

[0261] Second example solution: Network-based solution

[0262] The second solution may include at least one of the following steps:

[0263] 1. Same (or similar) as the first solution.

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

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

[0266] Thereafter, it may be assumed that the first network node 16a has configured QoE measurements and RVQoE measurements for the UE 22 and has established SRB 4 (and / or another SRB to which the UE 22 can send RVQoE reports) towards the UE 22. This is a non-limiting example, for example, because alternatively there may be a situation where the second network node 16b has configured the first configuration and the second configuration towards the UE 22. At this point, both nodes do not know which of them carries the data for the application session for the first service.

[0267] 4. The first network node 16a receives a RVQoE report related to the second configuration from the UE 22. The RVQoE report may contain the DRB ID and / or QoS flow ID and / or PDU session ID of the application session for which the RVQoE measurement is to be performed. Since the content of the RVQoE report is visible to the first network node 16a, based on the service type to which the RVQoE measurement is directed, the DRB ID and / or QoS flow ID and / or PDU session ID therein, the first network node 16a is aware that the data of the application session for which the RVQoE measurement is to be performed is transmitted to the UE 22 via the second network node 16b. For example, the first network node 16a may infer that the session is performed via the second network node 16b based on the DRB ID in the RVQoE report, because as part of the DC establishment process, the MN indicates to the SN which DRB IDs are available for the SN to use for SCG-terminated DRBs, thereby ensuring the uniqueness of the DRB ID established in the DC towards the UE 22. As an alternative or in combination, the connection leg may also be identified using the method described in the section "How the UE identifies the leg carrying the application data flow" (where the application includes the socket information in the RVQoE report). Thus, the first network node 16a is aware that the second network node 16b should receive the RVQoE report transmitted from the UE 22 to the first network node 16a via SRB4.

[0268] Alternatively, the UE 22 may send an indication along with the RVQoE report about which node the report is for. The indication may be sent all the time, or only in certain circumstances, such as when the report is for another node, when the target node has been changed since the last report, and so on.

[0269] a. In one option, the first network node 16a may determine that data for an application session for which RVQoE measurements are to be made is transmitted entirely to the UE 22 via the second network node 16b by using one or more of the following indications: a service type; a DRB ID, a QoS flow ID, a PDU session ID associated with the application session; a timestamp received within or with the RVQoE report; an indication (or a lack of indication) that there was no user plane activity between the UE 22 and the first network node 16a during the time period indicated by the RVQoE report.

[0270] b. The first network node 16a may also determine (e.g., based on a timestamp sent within or with the RVQoE report and an indication collected at the first network node 16a indicating user plane activity between the UE 22 and the first network node 16a) that data for the application session for which RVQoE measurements are to be performed is partially transmitted to the UE 22 via the first network node 16a, and that the RVQoE measurements are retained at the first network node 16a for optimization.

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

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

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

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

[0275] In one embodiment, the first network node 16a and the second network node 16b (before issuing any RVQoE configuration to any UE 22) may agree to send RVQoE measurements received from the UE 22 to the node configuring RVQoE for the UE 22. This coordination may be achieved during the execution of one of the procedures related to multi-connectivity operation, wherein the UE 22 is reconfigured from a single connection to multiple connections (e.g., secondary node addition). The UE 22 may be reconfigured from a first configuration in multiple connections to a second configuration in multiple connections (e.g., secondary node modification - MN initiated or SN initiated secondary node modification, secondary node change - MN initiated or SN initiated secondary node change, inter-MN handover with / without SN change). A node (e.g., a MN) that is interested in receiving RVQoE reports may signal a flag to another node (e.g., a SN) to indicate a request to obtain RVQoE reports that the UE 22 may send to the other node (the request may be generic, i.e., applicable to any RVQoE report, or may be more fine-grained, e.g., indicating that the MN is interested in receiving RVQoE reports only for a specific service).

[0276] 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 transmitted to the UE 22 via the first network node 16a (second network node 16b) before issuing any RVQoE configuration to any UE 22. For the case where both the first network node 16a and the second network node 16b are used for NR-DC (or any other form of MR-DC), the above operation may be performed assuming that the second network node 16b hosts (or is connected to) an AI / ML training function (which uses RVQoE measurements as input data) and has requested to receive such RVQoE measurements.

[0277] How does the UE identify the branch carrying the application data flow?

[0278] To determine on which connection leg (towards the MN or towards the SN) the data flow for which RVQoE measurement is to be performed is carried, the UE 22 may rely on inherent knowledge in the application.

[0279] An application creates a network socket for its application data flow, and the socket may have several associated parameters that can be used to identify the socket and the application data flow through it. These parameters may include at least one of the following:

[0280] - Local IP address (that is, the source IP address for outgoing data flow and the destination IP address for incoming data flow)

[0281] - Remote IP address (that is, the source IP address for incoming data flow and the destination IP address for outgoing data flow)

[0282] - Local transport protocol ports (that is, the source transport protocol port for outgoing data flows and the destination transport protocol port for incoming data flows)

[0283] - Remote transport protocol port (that is, the source transport protocol port for incoming data flows and the destination transport protocol port for outgoing data flows)

[0284] - Transport protocols (e.g., Transmission Control Protocol (TCP), Stream Control Transmission Protocol (SCTP), Real-Time Protocol (RTP)).

[0285] In the above protocol, the UE AS may also know the local IP address because it is the IP address assigned to the UE 22.

[0286] In order to enable the UE AS to identify the DRB and connection leg that carries a specific application data flow, the application (located in the UE application layer) informs the UE 22 AS of all or a subset of the socket parameters listed above for each incoming and outgoing data flow (for example, optionally excluding the local IP address). The UE AS can use this information (hereinafter referred to as socket information) to check on which DRB (and connection leg) the packets matching the information are sent and received.

[0287] The socket information from the UE application layer may be transmitted upon a 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). This more general request would cause the application to send the socket information at the start of each application session for which RVQoE measurements are to be made (and, if the information changes, to send updated information during the session). Alternatively, as a result of a general request from the UE AS, the application may send the socket information to the UE AS each time the application creates a socket. As another alternative, this more general request would cause the application to send the socket information with each RVQoE report.

[0288] Another option would be to not rely on a request from the UE AS, but to indicate in the RVQoE configuration that the application should send this information to the UE AS at the start of each application session (and, if necessary, updated during the session), at socket creation, and / or with each RVQoE report.

[0289] Yet another possible option could be to bypass the UE AS completely and instead have the application (at the UE application layer) include the socket information in the RVQoE report (controlled by the RVQoE configuration), and then the RAN node receiving the RVQoE report would determine on which DRB (and therefore on which connection leg) the application data flow is carried.

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

[0291] Other considerations

[0292] The 3GPP specification allows that the UE 22 can only establish one SRB for a specific SRB type, and this is the assumption adopted in the present invention. However, if the UE 22 is allowed to set up SRB4 towards both the first network node 16a and the second network node 16b, then the solution proposed herein also applies. In this case, the first network node 16a may not need to request the second network node 16b to establish SRB4, because SRB4 may have already been set up between the UE 22 and both nodes. In this case:

[0293]  The first network node 16a may indicate to the second network node 16b that from now on, RVQoE reports related to the second configuration will be transmitted from the UE 22 directly to the second network node 16b via SRB4.

[0294] Upon becoming aware that data for the session for which RVQoE measurements are to be performed is transmitted to UE 22 via second network node 16b (solution 2), or upon receiving such an indication from UE 22 (solution 1), first network node 16a may instruct UE 22 to send an RVQoE report associated with the second configuration directly to second network node 16b.

[0295] ° Alternatively, the UE 22 may decide at its own discretion to send the RVQoE report directly to the second network node 16b and may inform the first network node 16a of this.

[0296] CG-Config

[0297] The message is used to transfer the SCG radio configuration generated by the SgNB or SeNB. The CU can also use it to request the DU to perform specific actions, such as requesting the DU to perform a new low-layer configuration.

[0298] Direction: secondary gNB or eNB to primary gNB or eNB, alternatively CU to DU.

[0299] A non-limiting example of a CG-Config message is as follows:

[0300] --ASN1START

[0301] --TAG-CG-CONFIG-INFO-START

[0302] CG-ConfigInfo ::= SEQUENCE {

[0303] criticalExtensions CHOICE {

[0304] c1 CHOICE{

[0305] cg-ConfigInfo CG-ConfigInfo-IEs,

[0306] spare3 NULL, spare2 NULL, spare1 NULL

[0307] },

[0308] criticalExtensionsFuture SEQUENCE {}

[0309] }

[0310] }

[0311] CG-ConfigInfo-IEs ::= SEQUENCE {

[0312] ue-CapabilityInfo OCTET STRING (CONTAINING UE-CapabilityRAT-ContainerList) OPTIONAL,-- Cond SN-AddMod

[0313] candidateCellInfoListMN MeasResultList2NR OPTIONAL,

[0314] candidateCellInfoListSN OCTET STRING (CONTAININGMeasResultList2NR) OPTIONAL,

[0315] measResultCellListSFTD-NR MeasResultCellListSFTD-NROPTIONAL,

[0316] scgFailureInfo SEQUENCE {

[0317] failureType ENUMERATED { t310-Expiry,randomAccessProblem,

[0318] rlc-MaxNumRetx, synchReconfigFailure-SCG,

[0319] scg-reconfigFailure,

[0320] srb3-IntegrityFailure},

[0321] measResultSCG OCTET STRING (CONTAININGMeasResultSCG-Failure)

[0322] } OPTIONAL,

[0323] configRestrictInfo ConfigRestrictInfoSCG OPTIONAL,

[0324] drx-InfoMCG DRX-Info OPTIONAL,

[0325] measConfigMN MeasConfigMN OPTIONAL,

[0326] sourceConfigSCG OCTET STRING (CONTAININGRRCReconfiguration) OPTIONAL,

[0327] scg-RB-Config OCTET STRING (CONTAININGRadioBearerConfig) OPTIONAL,

[0328] mcg-RB-Config OCTET STRING (CONTAININGRadioBearerConfig) OPTIONAL,

[0329] mrdc-AssistanceInfo MRDC-AssistanceInfo OPTIONAL,

[0330] nonCriticalExtension CG-ConfigInfo-v1540-IEs OPTIONAL

[0331] }

[0332] CG-ConfigInfo-v1700-IEs ::= SEQUENCE {

[0333] candidateCellListCPC-r17 CandidateCellListCPC-r17OPTIONAL,

[0334] twoPHRModeSCG-r17 ENUMERATED {enabled} OPTIONAL,

[0335] lowMobilityEvaluationConnectedInPCell-r17 ENUMERATED {enabled}OPTIONAL,

[0336] The following table includes non-limiting examples of CG-ConfigInfo field descriptions:

[0337]

[0338] Table 1: CG-ConfigInfo field description.

[0339] UE capability indication

[0340] The UE 22 may be configured (e.g., may need to) indicate to the network its ability to perform actions related to the described solution. As part of UE capability signaling (either enhanced existing signaling or newly defined signaling), the UE 22 indicates to the network its ability to act according to embodiments of the present disclosure (i.e., send an indication to the network about the node carrying the application session, configure with the mentioned SRB configuration, forward RVQoE reports directly to the appropriate network node, etc.).

[0341] The following is a non-limiting list of example embodiments:

[0342] Embodiment A1. A first network node is configured to communicate with a user equipment UE and a second network node, at least the UE may be configured to communicate using a multi-radio connection, the first network node is configured as follows and / or comprises a radio interface and / or a processing circuit configured as follows:

[0343] sending, to the second network node, information regarding which of the first network node and the second network node has configured quality of experience measurements for a predetermined service type associated with the UE;

[0344] determining which of the first network node and the second network node carries data for an application session for which quality of experience measurement of a predetermined service type is to be performed; and

[0345] When the second network node carries data of an application session for which quality of experience measurement is to be performed, a quality of experience report corresponding to the application session is forwarded to the second network node.

[0346] Embodiment A2. The first network node of embodiment A1, wherein the processing circuit is configured to:

[0347] causing the first network node to configure the UE to at least one of:

[0348] sending a quality of experience report to at least one of the first network node and the second network node; and

[0349] The indication is for which network node of the first network node and the second network node the quality of experience is directed.

[0350] Embodiment A3. The first network node of any of embodiments A1 and A2, wherein at least one of the following items is present:

[0351] The first network node and the second network node are Radio Access Network (RAN) nodes;

[0352] The UE may be configured to send a capability indication to at least one of the first network node and the second network node;

[0353] The quality of experience measurement is a RAN visible quality of experience RVQoE measurement; and

[0354] The quality of experience report is the RVQoE report.

[0355] Embodiment B1. A method in a first network node, the first network node being configured to communicate with a user equipment UE and a second network node, at least the UE being configured to communicate using a multi-radio connection, the method comprising:

[0356] sending, to the second network node, information regarding which of the first network node and the second network node has configured quality of experience measurements for a predetermined service type associated with the UE;

[0357] determining which of the first network node and the second network node carries data for an application session for which quality of experience measurement of a predetermined service type is to be performed; and

[0358] When the second network node carries data of an application session for which quality of experience measurement is to be performed, a quality of experience report corresponding to the application session is forwarded to the second network node.

[0359] Embodiment B2. The method according to embodiment B1, wherein the method further comprises:

[0360] The UE is configured to perform at least one of the following operations:

[0361] sending a quality of experience report to at least one of the first network node and the second network node; and

[0362] The indication is for which network node of the first network node and the second network node the quality of experience is directed.

[0363] Embodiment B3. The method of any one of Embodiments B1 and B2, wherein at least one of the following is present:

[0364] The first network node and the second network node are Radio Access Network (RAN) nodes;

[0365] The UE may be configured to send a capability indication to at least one of the first network node and the second network node;

[0366] The quality of experience measurement is a RAN visible quality of experience RVQoE measurement; and

[0367] The quality of experience report is the RVQoE report.

[0368] Embodiment C1. A user equipment UE configured to communicate with a first network node and a second network node, at least the UE may be configured to communicate using a multi-radio connection, the UE being configured as follows and / or comprising a radio interface and / or a processing circuit configured as follows:

[0369] Determining that data of an application session for which quality of experience measurement of a predetermined service type associated with the UE is to be performed is carried by the second network node; and

[0370] At least an indication is sent to the first network node, indicating that data of the application session for which the quality of experience measurement of the predetermined service type is to be performed is carried by the second network node, and the indication can be used by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0371] Embodiment C2. The UE of embodiment C1, wherein the UE is configured by at least one of the first network node and the second network node to:

[0372] A quality of experience report is sent to at least one of the first network node and the second network node.

[0373] Embodiment C3. The UE of any of embodiments C1 and C2, wherein at least one of the following is present:

[0374] The first network node and the second network node are Radio Access Network (RAN) nodes;

[0375] The UE may be configured to send a capability indication to at least one of the first network node and the second network node;

[0376] The quality of experience measurement is a RAN visible quality of experience RVQoE measurement; and

[0377] The quality of experience report is the RVQoE report.

[0378] Embodiment D1. A method in a user equipment UE, configured to communicate with a first network node and a second network node, at least the UE may be configured to communicate using a multi-radio connection, the method comprising:

[0379] Determining that data of an application session for which quality of experience measurement of a predetermined service type associated with the UE is to be performed is carried by the second network node; and

[0380] At least an indication is sent to the first network node, indicating that data of the application session for which the quality of experience measurement of the predetermined service type is to be performed is carried by the second network node, and the indication can be used by the first network node to forward a quality of experience report corresponding to the application session to the second network node.

[0381] Embodiment D2. The method of embodiment D1, wherein the UE is configured by at least one of the first network node and the second network node as:

[0382] A quality of experience report is sent to at least one of the first network node and the second network node.

[0383] Embodiment D3. The method of any of embodiments D1 and D2, wherein at least one of the following is present:

[0384] The first network node and the second network node are Radio Access Network (RAN) nodes;

[0385] The UE may be configured to send a capability indication to at least one of the first network node and the second network node;

[0386] The quality of experience measurement is a RAN visible quality of experience RVQoE measurement; and

[0387] The quality of experience report is the RVQoE report.

[0388] As will be appreciated by those skilled in the art: the concepts described herein may be embodied as methods, data processing systems and / or computer program products and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of all-hardware embodiments, all-software embodiments, or embodiments combining hardware and software aspects, all of which are collectively 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. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having computer program code contained in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electrical storage device, an optical storage device, or a magnetic storage device.

[0389] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block shown in the flowcharts and / or block diagrams, and combinations of multiple blocks shown in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing device for producing a machine, so that the instructions (executed via the processor of the computer or other programmable data processing device) create a computer program for implementing the flowcharts and / or block diagrams. Figure 1 means for performing the functions / actions specified in one or more boxes.

[0390] These computer program instructions may also be stored in a computer-readable memory or storage medium that instructs a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory generate instructions including implementing the flowcharts and / or block diagrams. Figure 1 An article of manufacture that instructs means for performing the functions / actions specified in one or more blocks.

[0391] The computer program instructions may also be loaded into a computer or other programmable data processing device to cause a series of operable steps to be executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the flowchart and / or block diagram. Figure 1 One or more boxes specifying the steps of a function / action.

[0392] It should be understood that the functions and / or actions marked in the blocks may not occur in the order marked in the operating instructions. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the opposite order. Although some figures include arrows on the communication paths to indicate the primary direction of communication, it will be understood that communication may occur in the opposite direction of the indicated arrows.

[0393] The computer program code for performing the operations of the concept described herein can be written in an object-oriented programming language such as Python, Java® or C++. However, the computer program code for performing the operations of the present disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on the remote computer. In the latter case, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or an external computer can be connected (e.g., via the Internet using an Internet service provider).

[0394] In conjunction with the above description and the accompanying drawings, many different embodiments are disclosed herein. It will be understood that it would be unduly repetitive and confusing to describe and illustrate verbatim every combination and subcombination of these embodiments. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the accompanying drawings will be construed to construct a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and will support the rights and interests claiming any such combination or subcombination.

[0395] Abbreviations that may be used in the preceding description include:

[0396] 3GPP Third Generation Partnership Project

[0397] 5G Fifth Generation

[0398] 5GC 5G Core Network

[0399] 5GS Fifth Generation System

[0400] AS Access Layer

[0401] AMF Access and Mobility Management Function

[0402] ASN.1 Abstract Syntax Notation One

[0403] AT Note

[0404] AR Augmented Reality

[0405] AS Access Layer

[0406] BAP Backhaul Adaptation Protocol

[0407] CGI Cell Global Identifier

[0408] CN Core Network

[0409] CP Control Plane

[0410] CU Centralized Unit

[0411] CU-CP Centralized Unit Control Plane

[0412] CU-UP Centralized Unit User Plane

[0413] DU Distributed Unit

[0414] DASH Dynamic Adaptive Streaming over HTTP

[0415] DC Dual Connection

[0416] DL Downlink

[0417] DNS Domain Name System

[0418] E-CGI

[0419] E-UTRAN CGI: eNB Evolved Node B / E-UTRAN Node Ben-gNB. A gNB that acts as a secondary node in an EN-DC scenario (i.e., in a DC scenario with eNB as primary node and gNB as secondary node).

[0420] EN E-UTRAN-NR

[0421] EPC Evolved Packet Core

[0422] EPS Evolved Packet System

[0423] E-UTRA Evolved UTRA

[0424] E-UTRAN /

[0425] EUTRAN Evolved UTRAN

[0426] Radio base stations in gNBNR

[0427] HSS Home Subscriber Server

[0428] HTTP Hypertext Transfer Protocol

[0429] IAB Integrated Access and Backhaul

[0430] ID Identifier / Identification

[0431] IE Cell

[0432] LTE Long Term Evolution

[0433] MAC Media Access Control

[0434] MCC Mobile Country Code

[0435] MCE Measurement Collection Entity / Measurement Collector Entity

[0436] MDT Minimized Drive Test

[0437] MME Mobility Management Entity

[0438] MN Master Node

[0439] MNC Mobile Network Code

[0440] MTSI IMS Multimedia Telephone Service

[0441] N3IWF Non-3GPP Interworking Function

[0442] NG Next Generation

[0443] NG Interface between NG-RAN and 5GC.

[0444] NGAP NG Application Protocol

[0445] NG-RAN NG Radio Access Network

[0446] NID Network Identifier

[0447] NR New Radio

[0448] NWDAF network data analysis function

[0449] O&M Operation and Maintenance

[0450] OAM Operation and Maintenance

[0451] PDCP Packet Data Convergence Protocol

[0452] PDU Protocol Data Unit

[0453] PLMN Public Land Mobile Network

[0454] QMC QoE Measurement Collection

[0455] QoE Quality of Experience

[0456] QoS Quality of Service

[0457] RAN Radio Access Network

[0458] RAT Radio Access Technology

[0459] RLC Radio Link Control

[0460] RNC Radio Network Controller

[0461] RRC Radio Resource Control

[0462] RVQoE RAN Visible QoE

[0463] S1 Interface between RAN and CN in LTE.

[0464] S1APS1 Application Protocol

[0465] S-NSSAI Single Network Slice Selection Auxiliary Information

[0466] SMO Service Management and Orchestration

[0467] SN Secondary Node

[0468] SRB Signalling Radio Bearer

[0469] TA Tracking Area

[0470] TCE Trace Collection Entity / Trace Collector Entity

[0471] TNGF Trusted Non-3GPP Gateway Function

[0472] TWIF Trusted WLAN Intercommunication Function

[0473] UDM Unified Data Management

[0474] UE User Equipment

[0475] UMTS Universal Mobile Telecommunications System

[0476] URI Uniform Resource Identifier

[0477] URL Uniform Resource Locator

[0478] UTRA Universal Terrestrial Radio Access

[0479] UTRAN Universal Terrestrial Radio Access Network

[0480] WLAN Wireless Local Area Network

[0481] Xn Interface between two gNBs in NR.

[0482] XnAP Xn Application Protocol

[0483] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. Various modifications and changes are possible in view of the above teachings without departing from the scope of the appended claims.

Claims

1. A method in a first network node (16a), the first network node (16a) being configured to communicate with a user equipment UE (22) and a second network node (16b), at least the UE (22) being configured to communicate with the first network node (16a) and the second network node (16b) using a multi-radio connection, the method comprising: coordinating (S144) with a 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 of an application session for which a quality of experience measurement associated with the report is to be performed; as well as One or more actions are performed (S148) to ensure that the one of the first network node (16a) and the second network node (16b) carrying the data obtains the report.

2. The method according to claim 1, wherein: The coordination includes one of the following: sending a first indication to the second network node (16b), the first indication indicating that the first network node (16a) has received the report from the UE (22); as well as A second indication is received from the second network node (16b), the second indication indicating that the second network node (16b) has received the report from the UE (22).

3. The method according to any one of claims 1 and 2, wherein: 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; and 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.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: The report is received from the UE (22).

5. The method according to claim 4, wherein: Performing the one or more actions includes: When the second network node (16b) carries data of the application session, the report is sent to the second network node (16b), and the sent report can be used by the second network node (16b) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

6. The method according to any one of claims 1 to 3, wherein: Performing the one or more actions includes: When the first network node (16a) carries data of the application session, the report is received from the second network node (16b), and the received report can be used by the first network node (16a) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: The UE (22) is configured to perform one or both of the following: sending the report to at least one of the first network node (16a) and the second network node (16a); and Indicating which network node of the first network node (16a) and the second network node (16b) the quality of experience is for.

8. The method according to any one of claims 1 to 7, wherein: One or both of the following exist: The first network node (16a) and the second network node (16a) are Radio Access Network (RAN) nodes; and The quality of experience measurement is one or both of a quality of experience measurement (QoE) measurement and a RAN visible quality of experience (RVQoE) measurement.

9. The method according to any one of claims 1 to 8, wherein: The report 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 according to any one of claims 1 to 9, wherein: The method further comprises: A capability indication is received from the UE (22), the capability indication indicating which of the first network node (16a) and the second network node (16b) hosts the application session.

11. A first network node (16a) configured to communicate with a user equipment UE (22) and a second network node (16b), at least the UE (22) being configurable to communicate with the first network node (16a) and the second network node (16b) using a multi-radio connection, the first network node (16a) being configured to: 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 for which a quality of experience measurement associated with the report is to be made; as well as One or more actions are performed to ensure that the one of the first network node (16a) and the second network node (16b) that carries the data obtains the report.

12. The first network node (16a) according to claim 11, wherein: The coordination includes one of the following: sending a first indication to the second network node (16b), the first indication indicating that the first network node (16a) has received the report from the UE (22); as well as A second indication is received from the second network node (16b), the second indication indicating that the second network node (16b) has received the report from the UE (22).

13. The first network node (16a) according to any one of claims 11 and 12, wherein: 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; as well as 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.

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

15. The first network node (16a) according to claim 14, wherein Performing the one or more actions includes: When the second network node (16b) carries data of the application session, the report is sent to the second network node (16b), and the sent report can be used by the second network node (16b) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

16. The first network node (16a) according to any one of claims 11 to 13, wherein: Performing the one or more actions includes: When the first network node (16a) carries data of the application session, the report is received from the second network node (16b), and the received report can be used by the first network node (16a) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

17. The first network node (16a) according to any one of claims 11 to 16, wherein: The first network node (16a) is further configured to: The UE (22) is configured to perform one or both of the following: sending the report to at least one of the first network node (16a) and the second network node (16a); and Indicating which network node of the first network node (16a) and the second network node (16b) the quality of experience is for.

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

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

20. The first network node (16a) according to any one of claims 11 to 19, wherein: The first network node (16a) is further configured to: A capability indication is received from the UE (22), the capability indication indicating which of the first network node (16a) and the second network node (16b) hosts the application session.

21. A method in a user equipment UE (22), the user equipment UE (22) being configured to communicate with a first network node (16a) and a second network node (16b) using a multi-radio connection, the method comprising: A report corresponding to a service type associated with the UE (22) is sent (S150) to one of the first network node (16a) and the second network node (16b), wherein 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, wherein which of the first network node (16a) and the second network node (16b) 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.

22. The method according to claim 21, wherein: The method further comprises: determining a capability indication that can be used 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 data for an application session for which a quality of experience measurement associated with the report is to be made, and performing one or more actions to ensure that the one of the first network node (16a) and the second network node (16b) carrying the data obtains the report; and The capability indication is sent to one or both of the first network node (16a) and the second network node (16b).

23. The method according to claim 22, wherein: In case of sending the report to the first network node (16a), the one or more actions include: When the second network node (16b) carries data of the application session, the first network node (16a) sends the report to the second network node (16b), and the sent report can be used by the second network node (16b) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

24. The method according to claim 22, wherein: The one or more actions include: When the first network node (16a) carries data of the application session, the report is received by the first network node (16a) from the second network node (16b), and the received report can be used by the first network node (16a) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

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

26. The method according to any one of claims 21 to 25, wherein: The method further comprises: Indicating which network node of the first network node (16a) and the second network node (16b) the quality of experience is for.

27. The method according to any one of claims 21 to 26, wherein: The first network node and the second network node (16a, 16b) are Radio Access Network RAN ​​nodes.

28. The method according to any one of claims 21 to 27, wherein: The reports include Quality of Experience (QoE) reports.

29. The method according to any one of claims 21 to 28, wherein: The reports include Radio Access Network RAN ​​Visible Quality of Experience RVQoE reports.

30. The method according to any one of claims 21 to 29, wherein: The method further comprises: The report is determined 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).

31. A user equipment UE (22) configured to communicate with a first network node (16a) and a second network node (16b) using a multi-radio connection, the UE (22) being configured to: causing a report corresponding to a service type associated with the UE (22) to be sent to one of the first network node (16a) and the second network node (16b), wherein: 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, wherein which of the first network node (16a) and the second network node (16b) 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.

32. The UE (22) according to claim 31, wherein: The UE (22) is further configured to: determining a capability indication, the capability indication being 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 data for an application session for which a quality of experience measurement associated with the report is to be made, and performing one or more actions to ensure that the one of the first network node (16a) and the second network node (16b) carrying the data obtains the report; as well as The capability indication is caused to be sent to one or both of the first network node (16a) and the second network node (16b).

33. The UE (22) according to claim 32, wherein: In case of sending the report to the first network node (16a), the one or more actions include: When the second network node (16b) carries data of the application session, the first network node (16a) sends the report to the second network node (16b), and the sent report can be used by the second network node (16b) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

34. The UE (22) according to claim 32, wherein: The one or more actions include: When the first network node (16a) carries data of the application session, the report is received by the first network node (16a) from the second network node (16b), and the received report can be used by the first network node (16a) to send signaling associated with the service type to the UE (22) and / or receive signaling associated with the service type from the UE (22).

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

36. The UE (22) according to any one of claims 31 to 35, wherein: The UE (22) is further configured to: Indicating which network node of the first network node (16a) and the second network node (16b) the quality of experience is for.

37. The UE (22) according to any one of claims 31 to 36, wherein: The first network node and the second network node (16a, 16b) are Radio Access Network RAN ​​nodes.

38. The UE (22) according to any one of claims 31 to 37, wherein: The reports include Quality of Experience (QoE) reports.

39. The UE (22) according to any one of claims 31 to 38, wherein: The reports include Radio Access Network RAN ​​Visible Quality of Experience RVQoE reports.

40. The UE (22) according to any one of claims 31 to 39, wherein: The UE (22) is further configured to: The report is determined 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).

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

42. A computer readable medium comprising a computer program product according to claim 41.

Images