Ran measurements for UE performance

Abstract

A method in a source network node configured to communicate with a target network node is disclosed. The method includes: sending a request to the target network node to trigger collection of user equipment (UE) performance measurements and to report the UE performance measurements to the source network node or to another target network node; and receiving the UE performance measurements reported by the target network node, the UE performance measurements being included in an assistance information data frame over an F1-U interface or in a data collection update message over an E1 interface.

Description

[0001] RAN MEASUREMENTS FOR UE PERFORMANCE FIELD

[0002] The present disclosure relates to wireless communications, and in particular, to radio access network (RAN) measurements for user equipment (UE) performance.

[0003] BACKGROUND

[0004] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0005] NG-RAN Architecture

[0006] The current 5G RAN (NG-RAN) architecture is depicted and described in 3GPP Technical Standard (TS) 38.401 vl8.0.0 and is reproduced in the example of FIG. 1. The NG-RAN includes of a set of gNBs (network nodes) connected to the 5G core (5GC) through the NG interface.

[0007] As specified in 3GPP TS 38.300 vl8.0.0, the NG-RAN may also include a set of ng-eNBs. An ng-eNB may have an ng-eNB centralized unit (CU) and one or more ng-eNB distributed units (DUs). An ng-eNB-CU and an ng-eNB-DU are connected via the W1 interface. The general principle described here also applies to ng-eNB and the W1 interface, even if not explicitly specified otherwise.

[0008] A gNB may support frequency division duplex (FDD) mode, TDD mode or dual mode operation.

[0009] gNBs may be interconnected through the Xn interface.

[0010] A gNB may have a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU are connected via the Fl interface.

[0011] One gNB-DU is connected to only one gNB-CU.

[0012] NG, Xn, and Fl are logical interfaces.

[0013] For a NG-RAN, the NG and Xn-C interfaces for a gNB having a gNB-CU and gNB-DUs terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNBhaving a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0014] The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in the example of FIG. 2. A gNB may have a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU-UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP.

[0015] The architecture described above is what 3GPP has defined for 5G. Other standardization groups, such as the open radio access network (0-RAN) Alliance, have further extended the described architecture and have, for example, split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU would contain the low-PHY layer and the radio frequency (RF) parts, while the upper node of the split gNB-DU would host the radio link control (RLC), medium access control (MAC), and high-PHY layers. In the 0-RAN architecture, the upper node is called 0-DU, while the lower node is called 0-RU.

[0016] 3GPP Release 19 discussions

[0017] During 3GPP Technical Release 18 (3GPP Rel-18), RAN3 discussed and agreed solutions for artificial intelligence / machine learning (AI / ML) based use cases such as mobility optimization, load balancing, and network energy savings. The solutions pertained to the non-split architecture deployment option, i.e., where the functional components of the gNB are all aggregated and all functions of the RAN are performed by a monolithic function. Under this architecture, the RAN internal interfaces, El, Fl, are internal to the monolith and are not standardized in any form.

[0018] As part of 3GPP Rel-19, RAN3 is discussing solutions for the 3GPP Rel-18 AI / ML-based use-cases, but with the added scope of the solution applying to split architecture deployments as well.

[0019] Data Collection Reporting for collecting feedback

[0020] In 3 GPP Rel-18, RAN3 introduced new XnAP procedures to request and obtain predicted information, namely the Data Collection Reporting Initiation and the Data Collection Reporting procedures. The procedures work in tandem: with the Data Collection Reporting Initiation procedure, an NG-RAN node 1 sends to an NG-RAN node 2 a DATA COLLECTION REQUEST XnAP message, indicating a request for thereporting of information to support, e.g., AI / ML in NG-RAN. The granularity for which a piece of information is requested by NG-RAN node 1 and reported by NG-RAN node 2 is modeled as a “measured object” (for example, a cell, or a gNB, or a UE). For a certain measured object, the NG-RAN node 1 may request to obtain a number of measurements (that may be feedback or input data) or predictions from NG-RAN node 2, for instance the measured UE trajectory or UE Performance.

[0021] The NG-RAN node 2 sends the requested measurements to the NG-RAN node 1 using the DATA COLLECTION UPDATE message specified for the Data Collection Reporting procedure. For feedback related metrics, the Data Collection Initiation procedure configures exit conditions, e.g., UE Trajectory Collection Configuration or UE Performance Collection Configuration, which delimit the amount of time or events which stop collection of feedback data that may be collected in relation to a UE or an AI / ML algorithm derived decision.

[0022] The collected data is then signaled to the NG-RAN node 1 as part of Data Collection Update message, which includes identifiers to identify the UE (UE Assistant Identifier), and the involved nodes in the procedure (NG-RAN Node 1 measurement ID and NG-RAN Node 2 measurement ID).

[0023] QoS monitoring functionality

[0024] Quality of service (QoS) monitoring functionality is a means for an application server, or the core network to monitor at a per-data radio bearer (DRB) level the delivered QoS to a certain UE / application / QoS flow. It is expected that the delivered QoS satisfies the DRB-level QoS requirements of a flow.

[0025] QoS monitoring settings are propagated to the RAN via the access and mobility management function (AMF), whereby a request to monitor and report QoS of flows are signaled at the time of setting up the flows. The RAN node enables collection and reporting of the QoS metrics to the user plane function (UPF) according to the received criteria.

[0026] Delay components

[0027] With split architecture, the gNB-CU-CP, gNB-CU-UP, and the gNB-DU are disaggregated when compared to the non-split architecture, and each network function performs its own role and duties. In the context of delay metrics for UE performance, the different sub-components of the delay are computed by different entities.

[0028] In the context of downlink UE delay measurements, the metrics are defined in 3GPP TS 28.558. This corresponds to the following metrics collected at different entities:DI: Average delay in the downlink (DL) over air-interface (available at gNB-DU);

[0029] D2: Average delay in DL in gNB-DU (available at gNB-DU);

[0030] D3: Average DL delay over Fl-U (available at gNB-CU-UP); and D4: Average DL delay in CU-UP (available at gNB-CU-UP).

[0031] In the uplink (UL) direction, the delay components consist of the following, as defined in 3 GPP TS 28.558:

[0032] DI : UL packet data conversion protocol (PDCP) packet average delay (available at the UE and gNB-CU-CP);

[0033] D2.1 : Average over-the-air interface UL packet delay (available at gNB-DU);

[0034] D2.2: Average UL RLC packet delay (available at gNB-DU);

[0035] D2.3: Average UL delay over Fl-U (available at gNB-CU-UP); and D2.4: Average UL PDCP re-ordering delay (available at gNB-CU-UP). The 3 GPP RAN3 group agreed that:

[0036] - Packet delay measured for UE Performance feedback is sent from CU-UP (the delay in DU side is aggregated in the CU-UP) to the CU-CP in the case of CP -UP split architecture; and

[0037] - Packet delay measured for UE Performance feedback is sent from DU to CU via downlink data delivery status (DDDS) in the case of CU-DU split architecture.

[0038] The above consideration implies that the CU-UP will aggregate measurements performed by the DU and the CU-UP, and signal the cumulative measurement to the gNB-CU-CP.

[0039] The existing measurement functionality for performance monitoring of UEs is defined for QoS monitoring purposes. The measurements performed by the gNB-DU and gNB-CU-CP are defined in 3GPP TS 28.558. The gNB-CU, upon receiving a request to perform QoS monitoring from the AMF (as part of PDU session setup), triggers the measurements in the gNB-DU and gNB-CU-UP by setting the QoS Monitoring request Information Element (IE) in the UE CONTEXT SETUP REQUEST message (gNB-DU) and the BEARER CONTEXT SETUP REQUEST message (gNB-CU-UP). The collected measurements are then reported back to the UPF by the CU-UP.

[0040] The drawback with the above approach is the dependence on the QoS monitoring framework, i.e.:The UE performance feedback shall also work when QoS monitoring is not activated by the AMF;

[0041] When the QoS monitoring framework is used, the periodicity and start / stop of measurements are under the control of the AMF / core entities, i.e., the RAN cannot obtain measurements with a different periodicity if required, nor RAN may start measurements unless the AMF starts QoS Monitoring; and

[0042] In the existing functionality, the QoS metrics are reported to the UPF, while for the purpose of UE performance feedback, the collected metrics shall be made available at the gNB-CU-CP.

[0043] SUMMARY

[0044] Some embodiments advantageously provide methods and network nodes for radio access network (RAN) measurements for user equipment (UE) performance.

[0045] Some embodiments provide a RAN-based approach for collecting delay metrics required for UE performance in higher-layer split architecture. The solution leverages the existing QoS monitoring solution for the definition of metrics and parts of the signaling between nodes. In some embodiments, mechanisms are introduced such that the RAN / gNB-CU-CP controls the collection and periodicity of delay measurements, when these measurements are collected for UE performance feedback.

[0046] Some advantages of some embodiments may include one or more of the following:

[0047] The UE performance measurement / reporting is independent of the QoS monitoring solution, i.e., the UE may also operate when QoS monitoring is not activated;

[0048] RAN / gNB-CU-CP may control the periodicity and start / stop of measurements; and / or

[0049] Some embodiments may co-exist with the QoS monitoring solution, i.e., they may be active at the same time or not, and may operate with different measurement / reporting periodicities if required.

[0050] According to one aspect of the present disclosure, a method in a network node is provided. The method includes sending a request to the target network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node. The method includes receiving the UE performance measurements reported by the target network node, the UE performance measurements being comprised in an assistance informationdata frame over an Fl-U interface or in a data collection update message over an El interface.

[0051] According to one or more embodiments of this aspect, the method includes requesting the target network node to cease collection of UE performance measurements.

[0052] According to one or more embodiments of this aspect, the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0053] According to one or more embodiments of this aspect, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0054] According to one or more embodiments of this aspect, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0055] According to one or more embodiments of this aspect, the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0056] According to one or more embodiments of this aspect, sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

[0057] According to one or more embodiments of this aspect, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0058] According to another aspect of the present disclosure, a network node is provided. Network node is configured to send a request to the target network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node. The network node is configured to receive the UE performance measurements reported by the target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

[0059] According to one or more embodiments of this aspect, the network node is further configured to request the target network node to cease collection of UE performance measurements.

[0060] According to one or more embodiments of this aspect, the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.According to one or more embodiments of this aspect, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0061] According to one or more embodiments of this aspect, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0062] According to one or more embodiments of this aspect, the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0063] According to one or more embodiments of this aspect, sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

[0064] According to one or more embodiments of this aspect, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0065] According to another aspect of the present disclosure, a method in a network node is provided. The method includes receiving a request from the source network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node. The method includes reporting the UE performance measurements to the source network node or to the other target network node, the UE performance measurements being included in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

[0066] According to one or more embodiments of this aspect, the method includes receiving a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

[0067] According to one or more embodiments of this aspect, the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0068] According to one or more embodiments of this aspect, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0069] According to one or more embodiments of this aspect, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0070] According to one or more embodiments of this aspect, performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0071] According to one or more embodiments of this aspect, receiving the request includes receiving the request on one of a per-s-network slice selection assistanceinformation level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

[0072] According to one or more embodiments of this aspect, the UE performance measurements include an aggregation of first measurements from the target network node and second measurements from the other target network node.

[0073] According to one or more embodiments of this aspect, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0074] According to another aspect of the present disclosure, a network node is provided. The network node is configured to receive a request from the source network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node. The network node is configured to report the UE performance measurements to the source network node or to the other target network node, the UE performance measurements being included in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

[0075] According to one or more embodiments of this aspect, the network node is configured to receive a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

[0076] According to one or more embodiments of this aspect, the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0077] According to one or more embodiments of this aspect, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0078] According to one or more embodiments of this aspect, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0079] According to one or more embodiments of this aspect, performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0080] According to one or more embodiments of this aspect, receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.According to one or more embodiments of this aspect, the UE performance measurements include an aggregation of first measurements from the target network node and second measurements from the other target network node.

[0081] According to one or more embodiments of this aspect, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0082] BRIEF DESCRIPTION OF THE DRAWINGS

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

[0084] FIG. 1 is an example NG-RAN architecture;

[0085] FIG. 2 is an example architecture for separation of gNB-CU-CP and gNB-CU-UP; FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0086] FIG. 4 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0087] FIG. 5 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0088] FIG. 6 is a flowchart of an example process in a network node for radio access network (RAN) measurements for user equipment (UE) performance according to some embodiments of the present disclosure;

[0089] FIG. 7 is a flowchart of another example process in a network node for radio access network (RAN) measurements for user equipment (UE) performance according to some embodiments of the present disclosure;

[0090] FIG. 8 is a flowchart of another example process in a network node for radio access network (RAN) measurements for user equipment (UE) performance according to some embodiments of the present disclosure;

[0091] FIG. 9 is a flowchart of another example process in a user equipment for radio access network (RAN) measurements for user equipment (UE) performance according to some embodiments of the present disclosure;

[0092] FIG. 10 is a block diagram illustrating a virtualization environmentFIG. 11 is an example configuration of UE performance metrics collection between split RAN architecture nodes; and

[0093] FIG. 12 is an example of signaling exchange between gNB-CU-CP, gNB-DU and gNB-CU-UP.

[0094] DETAILED DESCRIPTION

[0095] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to radio access network (RAN) measurements for user equipment (UE) performance. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

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

[0097] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0098] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

[0100] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein may be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi -cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0101] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

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

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

[0104] Some embodiments are directed to radio access network (RAN) measurements for user equipment (UE) performance.

[0105] Returning to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that maysupport standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting 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 many more UEs 22 and network nodes 16.

[0106] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0107] Also, it is contemplated that a UE 22 may be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 may be in communication with an eNB for LTEZE-UTRAN, a gNB for NR / NG-RAN (i.e. being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.A network node 16 (eNB or gNB) is configured to include a CU 24 which is configured to send a request to a DU 26 to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the CU 24. The CU 24 may include a CP 24a and a UP 24b. A network node 16 may include a DU 26 which is configured to receive a request from the CU 24 to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the CU 24.

[0108] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 4.

[0109] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 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 radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

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

[0111] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / orto cause such methods, and / or processes to be performed, e.g., by network node 16.

[0112] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include a CU 24 which is configured to send a request to a DU 26 to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the CU 24. A network node 16 may include a DU 26 which is configured to receive a request from the source network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node. Note that the CU 24 may located in the same network node 16 as the DU 26 or the CU 24 and the DU 26 may be located in different network nodes 16. Also, the CP 24a and the UP 24b may be located in the same network node 16 or may be located in different network nodes 16. Although FIG. 4 shows CU 24 and DU 26 as part of processor 38, it is understood that different implementation arrangements are possible and that CU 24 and DU 26 may be implemented as part of processing circuitry 36, which includes memory 40 and processor 38. In other words, showing CU 24 and DU 26 only as part of processor 38 is done for ease of understanding and the sake of expediency, and not because implementations of CU 24 and DU 26 will always be only in processor 38.

[0113] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wirelesstechnologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.

[0114] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna 34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0115] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.

[0116] Network node 15 may include one or more components described above with respect to network node 16, e.g., communication interface 29, radio interface 30, antenna 34, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of network node 15 may be arranged such that network node 15 may perform various core network functions. Network node 15 may communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.

[0117] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 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 radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

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

[0119] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0120] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that isconfigured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22.

[0121] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

[0122] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0123] Although FIGS. 3 and 4 show various “units” such as CU 24 and DU 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0124] FIG. 5 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 5 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 5 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 1 and 2. In otherwords, in some embodiment, STA 62 is a UE 22. Further, stations 62 may, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0125] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0126] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0127] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 3 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0128] FIG. 6 is a flowchart of an example process in a source network node 16 for radio access network (RAN) measurements for user equipment (UE) performance. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the CU 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to send a request to the target network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node (Block S10). The process includes receiving the UE performance measurements reported by the target network node (Block S12).In some embodiments, the process includes requesting the target network node to cease collection of UE performance measurements. In some embodiments, the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure. In some embodiments, the request specifies at least one data radio bearer for which UE performance measurements are to be collected. In some embodiments, the request specifies performance metrics to be collected by the target network node for delay monitoring. In some embodiments, the performance metrics include a reporting periodicity for reporting the UE performance measurements. In some embodiments, sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.

[0129] FIG. 7 is a flowchart of an example process in a target network node 16 for radio access network (RAN) measurements for user equipment (UE) performance. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the DU 26), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to receive a request from the source network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node (Block S14). The process includes reporting the UE performance measurements to the target network node (Block SI 6).

[0130] In some embodiments, the process includes receiving a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request. In some embodiments, the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure. In some embodiments, the request specifies at least one data radio bearer for which UE performance measurements are to be collected. In some embodiments, the request specifies performance metrics to be collected by the target network node for delay monitoring. In some embodiments, the performance metrics include a reporting periodicity for reporting the UE performance measurements. In some embodiments, receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.For example, in some embodiments, the telecommunication system 10 includes one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication system 10, including one or more network nodes 16 in the access network 12 and / or core network nodes 14.

[0131] Examples of an ORAN network node 16 include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and UE 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.

[0132] FIG. 8 is a flowchart of an example process in a source network node 16 for radio access network (RAN) measurements for user equipment (UE) performance. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the CU 24), processor 38, and / or radio interface 30. Network node 16 is configured to send a request to the target network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node (Block SI 8). Network node 16 is configured to receive the UE performance measurements reported by the target network node, the UE performance measurements being comprisedin an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface (Block S20).

[0133] In some embodiments, the network node 16 is further configured to request the target network node to cease collection of UE performance measurements.

[0134] In some embodiments, the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0135] In some embodiments, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0136] In some embodiments, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0137] In some embodiments, the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0138] In some embodiments, sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit service level and a per-UE-level.

[0139] In some embodiments, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0140] FIG. 9 is a flowchart of an example process in a target network node 16 for radio access network (RAN) measurements for user equipment (UE) performance. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the DU 26), processor 38, and / or radio interface 30. Network node 16 is configured to receive a request from the source network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node or to another target network node (Block S22). Network node 16 is configured to report the UE performance measurements to the source network node or to the other target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface (Block S24).

[0141] In some embodiments, the network node 16 is further configured to receive a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

[0142] In some embodiments, the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.In some embodiments, the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0143] In some embodiments, the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0144] In some embodiments, performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0145] In some embodiments, receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit service level and a per-UE-level.

[0146] In some embodiments, the UE performance measurements comprise an aggregation of first measurements from the target network node and second measurements from the other target network node.

[0147] In some embodiments, the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

[0148] FIG. 10 is a block diagram illustrating a virtualization environment 94 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization may be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 94 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 94 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0149] Applications 96 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 94 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.Hardware 98 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth.

[0150] Software may be executed by the processing circuitry to instantiate one or more virtualization layers 100 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 102a and 102b (one or more of which may be generally referred to as VMs 102), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 100 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0151] The VMs 102 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 100. Different embodiments of the instance of a virtual appliance 96 may be implemented on one or more of VMs 102, and the implementations may be made in different ways.

[0152] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which may be located in data centers, and customer premise equipment.

[0153] In the context of NFV, a VM 102 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 102, and that part of hardware 98 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 102 on top of the hardware 98 and corresponds to the application 96.

[0154] Hardware 98 may be implemented in a standalone network node with generic or specific components. Hardware 98 may implement some functions via virtualization. Alternatively, hardware 98 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 104, which, among others, oversees lifecycle management of applications 96. In some embodiments, hardware 98 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used incombination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling may be provided with the use of a control system 106 which may alternatively be used for communication between hardware nodes and radio units.

[0155] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for radio access network (RAN) measurements for user equipment (UE) performance.

[0156] Some embodiments are described in the context of the 5G network architecture, i.e., where the RAN function is split into gNB-CU-CP 24a, gNB-CU-UP 24b, and the gNB-DU 26. However, such embodiments may not be limited to the 5G architecture or interfaces and equally apply to a different network architecture that may be adopted for a future network standard where the RAN function may be aggregated or disaggregated with a different logical split.

[0157] The detailed description of the embodiments is provided below based on the usecase of UE performance feedback. However, note that the solutions described herein may apply to use-cases / procedures other than those described below.

[0158] Some embodiments include a method executed by a first network node 16 to request, from a second network node 16, measurements for a UE (e.g., delay measurements) required for UE performance when the second network node 16 has a disaggregated architecture, the method comprising one or more of the following:

[0159] The two RAN nodes 16 involved in a procedure for UE performance reporting may establish a subscription-based reporting procedure (e.g., a DATA COLLECTION REPORTING procedure) where the reporting of measured UE performance is configured;

[0160] The source RAN network node (first node) 16, may provide to the target RAN network node (second node) 16 a reference to the above reporting procedure, e.g., DATA COLLECTION REPORTING procedure, using which the second node interprets a request to report measured UE performance as feedback:

[0161] o In some embodiments, the reference is provided in a message used to initiate a mobility procedure (e.g., a HANDOVER REQUEST XnAP message). In some embodiments, the reference if provided in a message used to initiate a dual connectivity procedure (e.g., in an S-NODE ADDITION REQUEST XnAP message, or in an S-NODEMODIFICATION REQUEST XnAP message or an in an S-NODE MODIFICATION REQUIRED XnAP message, or an S-NODE CHANGE REQUIRED XnAP message). In some embodiments, the reference is provided in a message used to inform a RAN node of updates in coverage for cells and / or beams (e.g., in an NG-RAN NODE CONFIGURATION UPDATE XnAP message);

[0162] In the network node 16 that has a disaggregated architecture, the gNB-CU-CP 24a may be in charge of collecting the measured UE performance measured by one or more logical functions (e.g., one gNB-CU-UP 24b and one gNB-DU 26) of the disaggregated node and reporting it to the first node 16 in accordance with the requested periodicity and requested metrics;

[0163] The first RAN node 16 based on the received request and reporting criteria may configure or signal to other RAN nodes 16, e.g., gNB-DU 26 (second node) and / or gNB-CU-UP 24b (third node) either:

[0164] o a request to collect and report the collected metrics at the certain periodicity to the third node; or

[0165] o a request to collect measurements at the third node 16 and to aggregate the collected measurements with metrics received from a second node 16 and report the aggregated value back to the first node 16 with a certain periodicity;

[0166] The first RAN node 16 may signal at a later point in time a request to stop the reporting of UE performance metrics; and / or

[0167] in the above, the request to collect and the periodicity with which the collection / reporting may happen may not the same as the request to perform QoS monitoring.

[0168] Currently, QoS monitoring is triggered by the AMF. As a result, when QoS monitoring is not enabled by the AMF, there is no way to trigger the RAN node to compute delay or other performance metrics. With the addition of UE performance however, the RAN needs to independently be able to configure, collect, and report such measurements to the neighbor node. A method to enable a RAN node 16 to request the configuration and reporting of delay measurements to another RAN node 16 is provided.

[0169] FIG. 11 is an example of high-level signaling to request and report UE performance metrics. The sequence may be triggered by the target gNB-CU-CP 24a when, for example, it receives and executes a handover request for a UE 22 or when it receives an S-Node Addition Request. The configuration according to which the target RAN node 16 collects UE performance may be specified either as part of the request received fromthe source node or as a part of other existing procedures, e.g., the UE performance collection may be configured as part of the Data Collection procedure.

[0170] Fl interface enhancements

[0171] In some embodiments, the gNB-CU-CP 24a requests the gNB-DU 26 to trigger collection of UE performance metrics (e.g., delay metrics) at the gNB-DU 26 and reporting of the collected metrics to the gNB-CU-UP 24b. This request may be part of any (UE associated or non-UE associated) Fl-C signal from the gNB-CU-CP 24a to the gNB-DU 26. Following the request, the gNB-DU 26 may perform the corresponding measurements and signals the results to gNB-CU-UP 24b.

[0172] In some embodiments, the gNB-CU-CP 24a requests the gNB-DU 26 to stop a previously initiated collection of UE performance at the gNB-DU 26 (e.g., delay metrics) at the gNB-DU 26. Following the request, the gNB-DU 26 may stop performing the corresponding measurements and signals the results to gNB-CU-UP 24b.

[0173] The request may be part of an existing or new signal from the gNB-CU-CP 24a to the gNB-DU 26 that is sent:

[0174] during the handover preparation or execution;

[0175] during the setup of resources for the UE 22 as part of, or following the handover preparation or execution;

[0176] during the S-Node addition procedure, where the gNB-DU 26 is selected as the node serving the primary secondary cell (PSCell) chosen for the dual connectivity configuration for the UE 22; and / or

[0177] another instance in time over an existing or new signal when the gNB-CU-CP 24a determines that the collection of UE performance at the gNB-DU 26 (e.g. collection of delay metrics for UE performance reasons) is required.

[0178] The request to the gNB-DU 26 may specify one or more of the following:

[0179] the one or more DRB established for a UE 22 for which delay measurements are to be collected;

[0180] the metrics to be collected by the gNB-DU 26 for delay monitoring purposes, e.g., uplink delay, downlink delay, or both. In some embodiments, the gNB-DU 26 receives information concerning the delay components it has to measure and report. For example, the gNB-DU 26 may be instructed to measure and report the UL / DL over the air delay, but none of the other delay components;

[0181] reporting periodicity of the collected metrics. In some embodiments, the reporting periodicity may implicitly control both the measurement collection periodicityand measurement reporting periodicity. In some embodiments, there may be dedicated configuration parameters for each of the criteria;

[0182] In some embodiments, the configuration may be signaled to the gNB-DU 26 at a per-s-network slice selection assistance information (NSSAI) level, whereby the gNB-DU 26 implicitly understands that all data radio bearers (DRBs) corresponding to the s-NSSAI may be monitored for the purpose of monitoring the UE performance (e.g., for delay monitoring purpose) for the specific network slice identified by the S-NSSAI;

[0183] In some embodiments, the configuration may be signaled to the gNB-DU 26 at a per-QoS flow level, whereby the gNB-DU 26 implicitly understands that all DRBs mapped to a certain QoS flow (e.g., as identified by a certain QoS Flow Identifier, QFI) may be monitored for the purpose of monitoring the UE performance (e.g., for delay monitoring purpose) for the specific QoS flow(s) identified;

[0184] In some embodiments, the configuration may be signaled to the gNB-DU 26 at a per-PDU session, whereby the gNB-DU 26 implicitly understands that all DRBs mapped to a certain packet data unit (PDU) session may be monitored for the purpose of monitoring the UE performance (e.g., for delay monitoring purpose) for the specific PDU session;

[0185] In some embodiments, the configuration may be signaled to the gNB-DU 26 at a per-PDU set, whereby the gNB-DU 26 implicitly understands that all DRBs mapped to a certain PDU set may be monitored for the purpose of monitoring the UE performance (e.g., for delay monitoring purpose) for the specific PDU set; and / or

[0186] In some embodiments, the configuration may be signaled at a per-UE-level, and the gNB-DU 26 monitors and reports the UE performance (e.g., the delay measurements) for all DRBs or network slices corresponding to that UE 22.

[0187] An example of how this signaling exchange may be achieved by using the UE Context Setup Request for the per-DRB case is shown below:

[0188]

[0189]

[0190]

[0191] The above-disclosed embodiments demonstrate the configuration for delay monitoring using the UE Context Setup Request procedure as a non-limiting example. Other existing messages, such as the UE Context Modification Request, or other(completely new) procedures may also be used to signal the configuration to the gNB-DU 26.

[0192] The collected metrics may be signaled by the gNB-DU 26 to the gNB-CU-UP 24b using the Fl-U Transfer of Assistance Information procedure. In some embodiments, the collected delay measurements may be signaled to the gNB-CU-UP 24b using the Transfer of Assistance Information over the Fl-U interface message in its unmodified form.

[0193] In some embodiments, as an extension to the above, the message containing the collected metrics may also include an identifier indicating that the reported measurement is for Delay monitoring for UE performance feedback or for QoS monitoring purposes. The indication may either be a enumerated value with QoS monitoring, RAN UE performance and both as the values. Or it may be two different information elements (IES) that may be set to true or false independent of one another. The above indication may be useful in the case when both QoS flow monitoring and delay monitoring for UE performance feedback are simultaneously active. The reporting period of both the requests may or may not be the same and the additional indication may aid the gNB-CU-UP 24b in associating the received metric with the appropriate procedure.

[0194] In some embodiments, the gNB-DU 26 may sequence number or timestamp the measurements it signals to the gNB-CU-UP 24b. The gNB-CU-UP 24b may use the sequence number or the timestamp to correlate the correct measurement generated at the gNB-CU-UP 24b to that received from the gNB-DU 26.

[0195] El interface enhancements

[0196] Request for measurements

[0197] The RAN delay of a UE 22, as described in earlier sections, may be computed as different sub-components in the gNB-DU 26 and the gNB-CU-UP 24b regardless of the granularity of the measurement, e.g., at a per-slice-level or per-DRB -level. Below, mechanisms are disclosed to activate collection of such measurements at the gNB-CU-UP 24b.

[0198] In some embodiments, the gNB-CU-CP 24a requests the gNB-CU-UP 24b to: trigger the collection of UE performance metrics (e.g., delay metrics) at the gNB-CU-UP 24b; be prepared to receive and aggregate the received measurements from the gNB-DU 26 together with the metrics collected at gNB-CU-UP 24b; and report it to the gNB-CU-CP 24a. This request may be part of any (UE associated or non-UE associated) El access point (AP) signal from the gNB-CU-CP 24a to the gNB-CU-UP 24b. Following the request, the gNB-CU-UP 24b may perform the corresponding measurements andaggregate the collected measurements with the measurements received from the gNB-DU 26, while ensuring that the measurement timings of the aggregated measurements are aligned. The gNB-CU-UP 24b may signal the results to gNB-CU-CP 24a.

[0199] In some embodiments, the gNB-CU-CP 24a may send to the gNB-CU-UP 24b one or more reporting configuration parameters (e.g., a reporting periodicity, or a reporting duration, or a reporting amount) that the gNB-CU-CP 24a has signaled (or is about to signal) to a gNB-DU 26, to indicate to the gNB-CU-UP 24b when, or for how long, or at which reporting periodicity, or how many reporting instances the gNB-CU-UP 24b may expect to receive for UE performance metrics collected at the gNB-DU 26. Optionally, the gNB-CU-CP 24a also sends to the gNB-CU-UP 24b a gNB-DU 26 identity (or a list of gNB-DU 26 identities) from which the gNB-CU-UP 24b may expect to receive UE performance metrics.

[0200] In some embodiments, the gNB-CU-CP 24a requests the gNB-CU-UP 24b to trigger the collection of UE performance metrics (e.g., delay metrics) at the gNB-CU-UP 24b without necessarily expecting delay measurement reporting from the gNB-DU 26. This might be the case where the gNB-CU-UP 24b is involved in serving a secondary node (SN) terminated master cell group (MCG) bearer. In this case, the gNB-CU may not aggregate delay component measurements from the gNB-DU 26 with the delay component measurements collected at the gNB-CU-UP 24b. Rather, the gNB-CU-UP 24b may measure the delay components under its own observability scope, such as the Average UL / DL delay over Fl -U and Average UL / DL delay in CU-UP 24b. The gNB-CU-UP 24b may report them to the gNB-CU-CP 24a. The request may be part of an existing or new signal from the gNB-CU-CP 24a to the gNB-CU-UP 24b that is sent, for example:

[0201] during the handover preparation or execution;

[0202] during the setup of resources for the UE 22 as part of, or following the handover preparation or execution;

[0203] during the S-Node addition procedure, where the gNB-CU is selected as the node serving the SN terminated bearers for the UE 22; and / or

[0204] another instance in time when the gNB-CU-CP 24a determines that the collection of delay metrics for UE performance reasons is required.

[0205] The request to the gNB-CU-UP 24b may specify one or more of the following: the DRBs of a UE 22 for which delay measurements are to be collected; the metrics to be collected by the gNB-CU-UP 24b for delay monitoring purposes, e.g., uplink delay, downlink delay, or both. In some embodiments, the gNB-CU-UP 24b receives information concerning the delay components it has to measure and report. For example, the gNB-CU-UP 24b may be instructed to measure and report the Average UL / DL delay over Fl-U delay, but none of the other delay components;

[0206] reporting periodicity of the collected metrics. In some embodiments, the reporting periodicity may implicitly control both the measurement collection periodicity and measurement reporting periodicity. In some embodiments, there may be dedicated configuration parameters for each of the criteria;

[0207] In some embodiments, the configuration may be signaled to the gNB-CU-UP 24b at a per-s-NSSAI level, whereby the gNB-CU-UP 24b implicitly understands that all DRBs corresponding to the s-NSSAI may be monitored for delay monitoring;

[0208] In some embodiments, the configuration may be signaled at a per-UE-level, and the gNB-CU-UP 24b may monitors and report delay measurements for all DRBs or slices corresponding to that UE 22;

[0209] In some embodiments, the configuration signaled to the gNB-CU-UP 24b may request reporting of UE delay at a per-slice-level granularity or at a per-UE-level granularity while the configuration to collect the metrics may be at a per-DRB-level or at a different granularity when compared to the reporting granularity. This may also imply that the gNB-DU 26 will report delay components to the gNB-CU-UP 24b with a different granularity when compared to the reported granularity to the gNB-CU-CP 24a; and / or The identity of the gNB-DU 26 from which the gNB-CU-UP 24b may expect to receive the metrics.

[0210] An example of how this signaling exchange may be achieved by using the Bearer Context Setup Request for the per-DRB case is shown below:

[0211]

[0212]

[0213]

[0214]

[0215]

[0216]

[0217] Embodiments disclosed above are related to the configuration for delay monitoring using the Bearer Context Setup Request procedure as a non-limiting example. Other existing messages, such as the Bearer Context Modification Request, or other (completely new) procedures may also be used to signal the configuration to the gNB-CU-UP 24b. Measurement reporting

[0218] In some embodiments, the gNB-CU-UP 24b aggregates the received measurement from the gNB-DU 26 together with the collected measurements at the gNB-CU-UP 24b and signals the metrics to the gNB-CU-CP 24a.

[0219] The reporting of the metrics to the gNB-CU-CP 24a may be performed over an existing or new El AP procedure.

[0220] In some embodiments, the reporting of the measured delay for UE performance may be signaled as an extension to the Resource Status procedure where:

[0221] the Resource Status Request is extended with a provision to report packet delay (as a report characteristic); and / orthe Resource Status Update is enhanced with reporting of measured delays for UE performance at different granularities.

[0222] Signaling enhancements to signal the collected delay measurements over the Resource Status procedure are disclosed.

[0223] RESOURCE STATUS REQUEST

[0224] This message may be sent by an gNB-CU-CP 24a to gNB-CU-UP 24b to initiate the requested measurement according to the parameters given in the message.

[0225] Direction: gNB-CU-CP 24a to gNB-CU-UP 24b.

[0226]

[0227]

[0228]

[0229]

[0230] UE Performance Collection Configuration

[0231] This IE indicates the configuration for UE performance measurement collection.

[0232]

[0233] RESOURCE STATUS UPDATE

[0234] This message may be sent by gNB-CU-UP 24b to gNB-CU-CP 24a to report the results of the requested measurements.

[0235] Direction: gNB-CU-UP 24b to gNB-CU-CP 24a.

[0236]

[0237]

[0238]

[0239] Delay measurements for UE performance

[0240]

[0241] In some embodiments, a different procedure may be used to report the collected measurements to the gNB-CU-CP 24a, e.g., Data Collection Reporting, or another preexisting or new procedure. See FIG. 12 as an example of such a different reporting embodiment.

[0242] Additional embodiments

[0243] In some embodiments, configuration parameters for QoS monitoring initiated by a Core Network node may be reused for RAN initiated collection of UE feedback. For example, the AMF may have already initiated QoS monitoring to collect delay for a UE 22 and indicated to a first RAN node a QoS Monitoring Reporting Frequency IE in the QoS Flow Level QoS Parameters IE contained in the PDU SESSION RESOURCE SETUP REQUEST message. The first RAN node may also receive from a second RAN node a request to provide UE performance including delay for a UE 22 being handed over (or handed over) to the first RAN node, and may determine to reuse the same value of the QoS Monitoring Reporting Frequency IE received from the AMF.

[0244] In some embodiments, a first RAN node receives from a second RAN node a configuration parameter indicating an amount (number) of reporting of delay measurement for the UE 22.

[0245] Example Embodiments:

[0246] Embodiment 1. A method in a source network node configured to communicate with a target network node, the method comprising: sending a request to the target network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node; and receiving the UE performance measurements reported by the target network node.

[0247] Embodiment 2. The method of Embodiment 1, further comprising requesting the target network node to cease collection of UE performance measurements.

[0248] Embodiment 3. The method of any of Embodiments 1 and 2, wherein the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0249] Embodiment 4. The method of any of Embodiments 1-3, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.Embodiment 5. The method of any Embodiments 1-4, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0250] Embodiment 6. The method of Embodiment 5, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0251] Embodiment 7. The method of any of Embodiments 1-6, wherein sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.

[0252] Embodiment 8. A source network node configured to communicate with a target network node, the source network comprising processing circuitry configured to: send a request to the target network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node; and receive the UE performance measurements reported by the target network node.

[0253] Embodiment 9. The source network node of Embodiment 8, wherein the processing circuitry is configured to request the target network node to cease collection of UE performance measurements.

[0254] Embodiment 10. The source network node of any of Embodiments 8 and 9, wherein the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0255] Embodiment 11. The source network node of any of Embodiments 8-10, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0256] Embodiment 12. The source network node of any Embodiments 8-11, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0257] Embodiment 13. The source network node of Embodiment 12, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0258] Embodiment 14. The source network node of any of Embodiments 8-13, wherein sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.Embodiment 15. A method in a target network node configured to communicate with a source network node, the method comprising: receiving a request from the source network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node; and reporting the UE performance measurements to the target network node.

[0259] Embodiment 16. The method of Embodiment 15, further comprising receiving a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

[0260] Embodiment 17. The method of any of Embodiments 15 and 16, wherein the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0261] Embodiment 18. The method of any of Embodiments 15-17, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0262] Embodiment 19. The method of any Embodiments 15-18, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0263] Embodiment 20. The method of Embodiment 19, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0264] Embodiment 21. The method of any of Embodiments 15-20, wherein receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.

[0265] Embodiment 22. A target network node configured to communicate with a source network node, the target network node comprising processing circuitry configured to: receive a request from the source network node to trigger collection of UE performance measurements and to report the UE performance measurements to the source network node; and report the UE performance measurements to the target network node.

[0266] Embodiment 23. The target network node of Embodiment 22, wherein the processing circuitry is configured to receive a stop request to cease collection of UE performance measurements and to cease collection of UE performance measurements in response to the stop request.Embodiment 24. The target network node of any of Embodiments 22 and 23, wherein the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

[0267] Embodiment 25. The target network node of any of Embodiments 22-24, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

[0268] Embodiment 26. The target network node of any Embodiments 22-25, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

[0269] Embodiment 27. The target network node of Embodiment 26, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

[0270] Embodiment 28. The target network node of any of Embodiments 22-27, wherein receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit level and a per-UE-level.

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

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

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

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

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

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

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

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

Claims

CLAIMS1. A method in a source network node (16) configured to communicate with a target network node, the method comprising:sending (SI 8) a request to the target network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node or to another target network node; and receiving (S20) the UE performance measurements reported by the target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

2. The method of Claim 1, further comprising requesting the target network node to cease collection of UE performance measurements.

3. The method of any of Claims 1 and 2, wherein the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

4. The method of any of Claims 1-3, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

5. The method of any Claims 1-4, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

6. The method of Claim 5, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

7. The method of any of Claims 1-6, wherein sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

8. The method of any of Claims 1-7, wherein the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

9. A source network node (16) configured to communicate with a target network node, the source network node comprising processing circuitry (36) configured to:send a request to the target network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node or to another target network node; andreceive the UE performance measurements reported by the target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

10. The source network node (16) of Claim 9, wherein the processing circuitry (36) is further configured to request the target network node to cease collection of UE performance measurements.

11. The source network node (16) of any of Claims 9 and 10, wherein the request is sent during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

12. The source network node (16) of any of Claims 9-11, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

13. The source network node (16) of any Claims 9-12, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

14. The source network node (16) of Claim 13, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

15. The source network node (16) of any of Claims 9-14, wherein sending the request includes sending the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

16. The source network node (16) of any of Claims 9-15, wherein the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

17. A method in a target network node (16) configured to communicate with a source network node, the method comprising:receiving (S22) a request from the source network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node or to another target network node; and reporting (S24) the UE performance measurements to the source network node or to the other target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

18. The method of Claim 17, further comprising receiving a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

19. The method of any of Claims 17 and 18, wherein the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

20. The method of any of Claims 17-19, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

21. The method of any Claims 17-20, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

22. The method of Claim 21, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

23. The method of any of Claims 17-22, wherein receiving the request includes receiving the request on one of a per-s-network slice selection assistance informationlevel, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

24. The method of any of Claims 17-23, wherein the UE performance measurements comprise an aggregation of first measurements from the target network node and second measurements from the other target network node.

25. The method of any of Claims 17-24, wherein the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

26. A target network node (16) configured to communicate with a source network node, the target network node comprising processing circuitry (36) configured to:receive a request from the source network node to trigger collection of user equipment, UE, performance measurements and to report the UE performance measurements to the source network node or to another target network node; and report the UE performance measurements to the source network node or to the other target network node, the UE performance measurements being comprised in an assistance information data frame over an Fl-U interface or in a data collection update message over an El interface.

27. The target network node (16) of Claim 26, wherein the processing circuitry (36) is further configured to receive a stop request to cease collection of UE performance measurements and ceasing collection of UE performance measurements in response to the stop request.

28. The target network node (16) of any of Claims 26 and 27, wherein the request is received during one of a handover procedure, a resource setup procedure and an S-node addition procedure.

29. The target network node (16) of any of Claims 26-28, wherein the request specifies at least one data radio bearer for which UE performance measurements are to be collected.

30. The target network node (16) of any Claims 26-29, wherein the request specifies performance metrics to be collected by the target network node for delay monitoring.

31. The target network node (16) of Claim 30, wherein the performance metrics include a reporting periodicity for reporting the UE performance measurements.

32. The target network node (16) of any of Claims 26-31, wherein receiving the request includes receiving the request on one of a per-s-network slice selection assistance information level, a per-quality of service flow level, a per-packet data unit session level and a per-UE-level.

33. The target network node (16) of any of Claims 26-32, wherein the UE performance measurements comprise an aggregation of first measurements from the target network node and second measurements from the other target network node.

34. The target network node (16) of any of Claims 26-33, wherein the request corresponds to a stop / start indication for delay measurements, the indication being sent over an Fl interface.

Images