Performance reporting in dual connectivity and split architecture

Abstract

An apparatus, method, and computer program product are provided. According to an embodiment, the method includes: obtaining a performance measurement configuration by a first entity of a first network element of a wireless communication network; sending the performance measurement configuration to a second entity of the first network element in any of a user equipment context-dependent request or a bearer context-dependent request to configure performance measurements in the second entity of the first network element; receiving, at the first entity of the first network element, an acknowledgment message for the user equipment context-dependent request or the bearer context-dependent request from the second entity of the first network element; and receiving, from the second entity of the first network element, a performance report related to the performance measurements performed by the second entity of the first network element.

Description

Technical Field

[0001] This invention relates to reporting user equipment performance measurements on switched user equipment to determine handover performance. Background Technology

[0002] This section is intended to provide background or context for the invention as set forth in the claims. The description herein may include concepts that may be pursued, but are not necessarily concepts that have been previously conceived or pursued. Therefore, unless otherwise stated herein, what is described in this section is not prior art to the specification and claims of this application, and is not acknowledged as prior art by virtue of its inclusion in this section.

[0003] The 5G (fifth generation) specification provides the option to split the internal structure of the access node gNodeB (gNB) into entities called CUs (Centralized Units) and one or more DUs (Distributed Units), which are connected via F1 interfaces. This split gNB architecture allows for distributed radio access network (RAN) deployment (i.e., gNBCU-DU split) and the decomposition of certain RAN network elements. In 5G, the C-plane functionality in this RAN split architecture is also split, with the Centralized Unit Control Plane (CU-CP), Centralized Unit User Plane (CU-UP), and DU components all including C-plane functionality.

[0004] The User Equipment (UE) performance measurements introduced in TS38.423Rel-18 are average UE throughput, average packet delay, and average packet loss DL for both uplink (UL) and downlink (DL). UE performance reporting is configured via the Xn interface during the initiation of a Category 1 non-UE associated data collection report. Actual reporting is similarly completed during the Category 2 data collection reporting process. When the source node indicates a pair of measurement IDs corresponding to the configured UE performance measurements from the source to the target node at the handover request message, the collection of UE performance feedback for a specific UE is triggered. This pair of measurement IDs is also referred to as the data collection ID in TS38.423. UE performance measurements are reported from the target to the source node only for those UEs whose handover request messages include the data collection ID. UE performance can be reported either as a one-time report or periodically.

[0005] However, although gNB-CU-UP can measure UE performance or UL / DL data volume, there is currently no configuration or trigger to enable gNB-CU-UP to report such information to gNB-CU-CP for each received (handover) UE. Summary of the Invention

[0006] Some embodiments provide a method and apparatus for reporting user equipment performance measurements of switched user equipment in order to determine handover performance.

[0007] Therefore, this specification provides a method and apparatus to enable the collection of UE performance measurements from gNB-CU-UP and gNB-DU in dual-connectivity and split-architecture scenarios. In these scenarios, existing triggering methods based on the handover preparation process cannot be used to trigger UE performance measurement collection because the handover request message is not visible to either gNB-CU-UP or gNB-DU. Therefore, according to an embodiment, upon receiving a handover request, gNB-CU-CP sends a UE performance request to at least one of the receiving UE's gNB-CU-UP and gNB-DU. This request includes the requested UE performance measurements and the timing configuration required to collect the UE performance measurements. gNB-CU-UP and gNB-DU do not begin actual measurement collection upon receiving the UE performance request, but rather after the handover is completed, and report configured information to gNB-CU-CP according to the configured timing configuration and the requested measurements.

[0008] The UE performance measurements introduced in TS38.423Rel-18 are visible and can be measured in gNB-CU-UP. UE performance measurements related to UL and DL latency are visible in both gNB-DU and gNB-CU-UP, but ultimately gNB-CU-UP provides overall visibility into UE latency performance. While the current state of affairs in this field considers only UE performance measurements for UEs in a single connection, using gNB-CU-UP for UE performance measurements also allows for simple observation of overall UE performance in specific DC (dual connectivity) scenarios, such as when both MCG and SCG are used for split bearers of data transmission (MN-terminated split bearers, SN-terminated split bearers).

[0009] In some scenarios, additional UE performance measurements can be considered measurable only in the gNB-DU, such as measurements related to the UE's CSI state as an example, or other measurements related to the PHY / MAC / RLC layers, such as those related to HARQ retransmission or the applied modulation and coding scheme (MCS). The gNB-DU has the capability to perform these PHY / MAC / RLC layer measurements per beam, and this information is not available in the gNB-CU-UP.

[0010] The process of configuring, triggering, and reporting UE performance feedback is in Figure 2 As shown in the diagram, UE performance measurements are configured from NG-RAN node 1 to NG-RAN node 2. When a UE switches from NG-RAN node 1 to NG-RAN node 2, the actual collection of UE performance measurements at NG-RAN node 2 is triggered.

[0011] According to the embodiments, one or more of the following aspects will be utilized.

[0012] Some embodiments are implemented in the context of 5G communication systems and relate to UE and / or network implementations for mechanisms to monitor UE measurement limitations during discontinuous reception.

[0013] The subject matter of the independent claims is provided according to several aspects. Additional aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims are to be interpreted as examples useful for understanding this disclosure.

[0014] According to a first aspect, an apparatus is provided, comprising: Components for obtaining performance measurement configurations from a first entity of a first network element in a wireless communication network; A component for sending performance measurement configuration to a second entity of a first network element in any request of a user equipment context-dependent request or a bearer context-dependent request, to configure performance measurement in the second entity of the first network element; A component for receiving, at a first entity of a first network element, an acknowledgment message for a user equipment-related request or a bearer context-related request from a second entity of the first network element; and A component for receiving performance reports related to performance measurements performed by the second entity of the first network element from a second entity of the first network element.

[0015] According to the second aspect, a method is provided, comprising: The performance measurement configuration is obtained from the first entity of the first network element of the wireless communication network; In any of the user equipment context-dependent requests or bearer context-dependent requests, a performance measurement configuration is sent to a second entity of the first network element to configure performance measurement in the second entity of the first network element; At the first entity of the first network element, an acknowledgment message for a user equipment-related request or a bearer context-related request is received from the second entity of the first network element; and Receive a performance report related to the performance measurement performed by the second entity of the first network element.

[0016] According to a third aspect, an apparatus is provided, comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to perform at least the following operations: The performance measurement configuration is obtained from the first entity of the first network element of the wireless communication network; In any of the user equipment context-dependent requests or bearer context-dependent requests, a performance measurement configuration is sent to a second entity of the first network element to configure performance measurement in the second entity of the first network element; At the first entity of the first network element, an acknowledgment message for a user equipment-related request or a bearer context-related request is received from the second entity of the first network element; and Receive a performance report related to the performance measurement performed by the second entity of the first network element.

[0017] According to a fourth aspect, a computer program product including computer-readable program code is provided, which, when executed by at least one processor, causes the device to perform at least the following operations: The performance measurement configuration is obtained from the first entity of the first network element of the wireless communication network; In any of the user equipment context-dependent requests or bearer context-dependent requests, a performance measurement configuration is sent to a second entity of the first network element to configure performance measurement in the second entity of the first network element; At the first entity of the first network element, an acknowledgment message for a user equipment-related request or a bearer context-related request is received from the second entity of the first network element; and Receive a performance report related to the performance measurement performed by the second entity of the first network element. Attached Figure Description

[0018] To gain a more complete understanding of exemplary embodiments of the invention, reference is now made to the following description taken in conjunction with the accompanying drawings, in which: Figure 1 A block diagram is shown as one possible and non-limiting example of which can be practiced; Figure 2 The signaling diagram for UE performance configuration, triggering, and reporting is shown; Figure 3 The overall architecture for the separation of gNB-CU-CP and gNB-CU-UP is shown; Figure 4 The solution in the split architecture according to the embodiment is shown as a signaling diagram; Figure 5 A signaling diagram of a solution in a dual-connectivity scenario according to an example embodiment is shown; Figure 6 A signaling diagram is shown for triggering UE performance measurements from CU-UP and gNB-DU in a gNB-DU handover scenario according to an example embodiment; Figure 7A signaling diagram illustrating another example embodiment for triggering UE performance measurements from CU-UP and gNB-DU in an intra-gNB handover scenario is shown; and Figure 8 A flowchart of a method according to an embodiment is shown. Detailed Implementation

[0019] The following embodiments are exemplary. Although the specification may refer to "a," "an," or "some" (or more) embodiments in several places, this does not necessarily mean that each such reference refers to the same (or more) embodiments, or that the feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments.

[0020] It should be noted here that, in this specification, the term "base station" refers to a logical element that includes logical communication system layers (e.g., L1, L2, L3). Base stations of different RATs can be implemented in the same hardware or separate hardware. It should also be mentioned that although the expressions "each base station," "each mobile station," or "each user equipment" may be used, these terms do not necessarily refer to every existing base station, mobile station, or user equipment, but rather to base stations, mobile stations, or user equipment in a specific area or set. For example, each base station may mean all base stations within a specific geographical area, or all base stations of an operator of a wireless communication network, or a subset of base stations of an operator of a wireless communication network.

[0021] Figure 1 A block diagram of one possible, non-limiting example of an example in which practices are illustrated is shown. User equipment (UE) 110, radio access network (RAN) node 170, and network elements(s) 190 are shown. Figure 1In the example, user equipment 110 wirelessly communicates with wireless network 100. User equipment is a wireless device that can access wireless network 100. User equipment 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx 132, and a transmitter, Tx 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cable, or other optical communication device. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. User equipment 110 includes a module 140, which can be implemented in various ways. Module 140 may be implemented in hardware as module 140-1, such as being implemented as part of one or more processors 120. Module 140-1 may also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, module 140 can be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 can be configured to perform one or more operations as described herein with user equipment 110 using one or more processors 120. User equipment 110 communicates with RAN node 170 via wireless link 111. Modules 140-1 and 140-2 can be configured to implement the functions of the user equipment as described herein.

[0022] In this example, RAN node 170 is a base station that provides access to wireless network 100 for wireless devices such as user equipment 110. Therefore, RAN node 170 (and the base station) can also be referred to as an access point of the wireless communication network. RAN node 170 can be, for example, a base station for 5G (also known as New Radio (NR)). In 5G, RAN node 170 can be an NG-RAN node, defined as a gNB (Next Generation NodeB) or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (such as, for example, multiple network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node can include multiple gNBs, and can also include centralized unit (CU) (gNB-CU) 196 and distributed unit (DU) (gNB-DU), where DU 195 is shown. Note that DU 195 can include or be coupled to and control a radio unit (RU). gNB-CU196 is a logical node implemented in the hardware and software of, for example, RAN node 170, which hosts the Radio Resource Control (RRC), SDAP, and PDCP protocols of the gNB or the RRC and PDCP protocols of the en-gNB that control the operation of one or more gNB-DUs. gNB-CU196 terminates the F1 interface connected to gNB-DU195. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows the link between remote elements of RAN node 170 and centralized elements of RAN node 170 (such as between gNB-CU196 and gNB-DU195). gNB-DU195 is a logical node that hosts the RLC, MAC, and PHY layers of the gNB or en-gNB, and its operation is partially controlled by gNB-CU196. One gNB-CU196 supports one or more cells. A cell is supported by only one gNB-DU195. gNB-DU195 terminates the F1 interface 198 connected to gNB-CU196. Note that gNB-DU195 is considered to include transceiver 160, for example, as part of an RU; however, some examples may have transceiver 160 as part of a separate RU, for example, under the control of and connected to gNB-DU195. RAN node 170 may also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution) or any other suitable base station or node.

[0023] RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / W (multiple) I / F) 161, and one or more transceivers 160 interconnected via one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx 162, and a transmitter, Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. gNB-CU196 may include (multiple) processors 152, (multiple) memories 155, and network interfaces 161. Note that gNB-DU195 may also include its own memories and (multiple) processors and / or other hardware, but these are not shown.

[0024] RAN node 170 includes module 150, which includes one or both of portions 150-1 and / or 150-2, and can be implemented in various ways. Module 150 can be implemented in hardware as module 150-1, such as being implemented as part of one or more processors 152. Module 150-1 can also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 150 can be implemented as module 150-2, which is implemented as computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 are configured, together with one or more processors 152, to cause RAN node 170 to perform one or more operations as described herein. Note that the functionality of module 150 can be distributed, such as distributed between gNB-DU195 and gNB-CU196, or implemented only in gNB-DU195. Modules 150-1 and 150-2 can be configured to implement the functionality of the base station described herein.

[0025] One or more network interfaces 161 communicate via a network, such as via links 176 and 131. Two or more gNBs 170 can communicate using, for example, link 176. Link 176 can be wired, wireless, or both, and can implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0026] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for a gNB implementation of 5G, wherein other elements of the RAN node 170 may be physically located differently from the RRH / gNB-DU 195, and one or more buses 157 may be partially implemented as, for example, fiber optic cables or other suitable network connections to connect other elements of the RAN node 170 (e.g., centralized unit (CU), gNB-CU) to the RRH / gNB-DU 195. Reference numeral 198 also indicates those suitable network links(s).

[0027] Note that the description in this document indicates that a "cell" performs a function; however, it should be clear that the equipment forming a cell can perform functions. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, for a single carrier frequency and associated bandwidth, there can be three cells, each covering one-third of a 360-degree area, such that the coverage area of ​​a single base station is approximately elliptical or circular. Furthermore, each cell can correspond to a single carrier, and a base station can use multiple carriers. Therefore, if each carrier has three 120-degree cells and two carriers, the base station has a total of six cells.

[0028] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to another network (such as a telephone network and / or a data communication network (e.g., the Internet)) via one or more links 181. Such core network functions for 5G may include location management functions (multiple LMFs) and / or access and mobility management functions (multiple AMFs) and / or user plane functions (multiple UPFs) and / or session management functions (multiple SMFs). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely example functions that can be supported by the network elements 190, and note that both 5G and LTE functions can be supported. RAN node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175 interconnected via one or more buses 185, one or more memories 171, and one or more network interfaces (N / W I / F) 180. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, together with the one or more processors 175, cause network element 190 to perform one or more operations.

[0029] Wireless network 100 can implement network virtualization, which is the process of combining hardware and software network resources and network functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as external, combining many networks or parts of networks into virtual units, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and such virtualized entities also produce technical effects.

[0030] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed storage, and removable storage. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. As a non-limiting example, processors 120, 152, and 175 can be of any type suitable for the local technical environment and can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 can be components for performing functions such as controlling UE 110, RAN node 170, network element(s) 190, and other functions as described herein.

[0031] Typically, various embodiments of user equipment 110 may include, but are not limited to, cellular phones such as smartphones, tablet computers, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices such as digital cameras with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals that include a combination of these functions.

[0032] The 5G specification provides the option to divide the internal structure of an access node (gNodeB) into entities called CUs (Centralized Units) and one or more DUs (Distributed Units), which are connected via F1 interfaces. This split gNB architecture allows for the deployment of distributed radio access networks (RAN) (i.e., gNBCU-DU split) and the decomposition of certain RAN network elements. This results in the Radio Resource Control Protocol (RRC) control plane (C-plane) being anchored in the CU (as in 4G), but its functions (such as lower-layer configuration management) are split between the CU and DU. In this specification, we use the terms gNB-CU-CP and NG-RAN Node CU-CP interchangeably, which can also be understood to cover ng-eNB-CU-CP. Similarly, we use the terms gNB-CU-UP and NG-RAN Node CU-UP interchangeably, which can also be understood to cover ng-eNB-CU-UP. Likewise, we use the terms gNB-DU and NG-RAN Node DU interchangeably, which can also be understood to cover ng-eNB-DU.

[0033] In 5G, the C-plane function in this RAN split architecture is also split, with the Central Unit Control Plane (CU-CP), Central Unit User Plane (CU-UP), and DU components all including C-plane functions. One purpose of the split architecture is to be able to utilize central resources of the data center type.

[0034] In a split gNB architecture, network components have defined tasks, and each component possesses its own data. For example, in the 5G architecture, 3GPP has defined gNB-DU and gNB-CU tasks. A gNB-CU task, for example, handles RRC and also has the required security context. Therefore, only the correct gNB-CU with the UE context can open the RRC message and authenticate the UE. This is not truly a cloud-native approach. In a cloud-native solution, algorithms and storage are decomposed, and UE requests should be processed in the optimal resource location.

[0035] Figure 3 The document describes a 5G 3-split architecture.

[0036] A gNB can include a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The 2-partition 5G architecture considers the splitting between gNB-DU and gNB-CU, where CU-UP and CU-CP are considered as a single entity. The 3-partition 5G architecture considers the splitting between gNB-DU, gNB-CU-CP, and gNB-CU-UP.

[0037] TS38.401 provides a scenario for gNB handover involving gNB-CU-UP changes.

[0038] Similarly, TS37.340 describes the following inter-master node handover with or without secondary node changes. For the EN-DC case, inter-master node handover with / without MN-initiated secondary node changes is used to transfer context data from the source MN to the target MN, while the context at the SN is either maintained or moved to another SN. During the inter-master node handover, the target MN decides whether to maintain or change the SN (or release the SN). Figure 4 ).

[0039] In the case of an MR-DC with 5GC, inter-MN handover with or without MN-initiated SN change is used to transfer UE context data from the source MN to the target MN, while the UE context at the SN is maintained or moved to another SN. During inter-master node handover, the target MN decides whether to maintain or change the SN (or release the SN). Only intra-RAT inter-master node handovers with / without SN change are supported (e.g., no transition from NGEN-DC to NR-DC).

[0040] The MR-DC data usage report contains MR-DC data usage information (IE). This IE includes, depending on the configuration, the amount of UL / DL data aggregated for all QoS flows within a PDU session, or, individually for each PDU session within a UE's PDU session, the amount of UL / DL data aggregated for each QoS flow. Each report can be split into two time periods, allowing measurements to be divided within the report to indicate usage occurring before and after an operator-configurable absolute time (e.g., midnight).

[0041] The TS38.423Rel-18 solution considers non-split architectures and scenarios involving gNB handover. When NG-RAN node 1 configures UE performance measurements to NG-RAN node 2, and the UE successfully hands over from the source node (NG-RAN node 1) to the target node (NG-RAN node 2) via a handover request, the actual UE performance measurement collection is triggered from gNB-CU-CP. UE performance measurements can be performed by gNB-CU-UP and gNB-DU. In a non-split architecture, gNB-CU-UP and gNB-DU are received internally within the NG-RAN node (handover) to initiate the measurement collection process. However, there are certain scenarios where this is not possible.

[0042] In dual connectivity (DC), the source MN sends a handover request to the target MN, but the target MN can choose a different target secondary node (SN) or can release the SN. If the UE is served in the DC after the handover, UE performance information will need to be reported from the target SN to the target MN. However, in this case, the target SN lacks a handover trigger, so the target SN does not know when to start collecting measurements related to UE performance.

[0043] Furthermore, in the split architecture, when a UE switches from an NG-RAN node to another node, the gNB-CU-UP does not have UE-related information. Even if the gNB-CU-CP receives a trigger for UE performance measurement collection via a handover request message, the gNB-CU-UP is unaware of the event.

[0044] In some scenarios, gNB-CU-UP can be configured to report the UL / DL data volume of each UE to gNB-CU-CP. However, in the current specification, there is no configuration or trigger that allows gNB-CU-UP to report the UE performance information of each UE to gNB-CU-CP.

[0045] Even though energy saving, load balancing, and mobility enhancement use cases consider inter-gNB handover, intra-gNB handover can be optimized through UE performance feedback collection. In the case of intra-gNB mobility in a split architecture, the gNB-CU-CP cannot access UE performance measurements measured by the gNB-CU-UP. Similarly, there is no handover trigger to initiate the collection of UE performance information from the gNB-CU-UP. Note that this also applies when UE performance measurements that can be measured by the gNB-DU (such as latency measurements as an example) are involved. Even though the gNB-DU can be configured to measure UE performance information, there is currently no configuration or trigger that enables the gNB-DU to provide UE performance information for each UE to the gNB-CU-CP. Therefore, UE performance measurements cannot be used for AI / ML-based optimization of intra-gNB mobility in a split architecture.

[0046] Therefore, in these scenarios, it is currently impossible to trigger the collection of UE performance measurements at gNB-CU-UP and gNB-DU. Furthermore, in these scenarios, gNB-CU-UP does not always know when the handover is successful to actually begin collecting UE performance measurements for a given UE.

[0047] Furthermore, in these scenarios, it is not possible to configure gNB-CU-UP or gNB-DU to collect UE performance measurements. A simple solution is to introduce the data collection report initiation (Category 1) and data collection report (Category 2) procedures introduced in Rel-18 via Xn to E1, and make the existing Xn signaling procedures applicable to dual connectivity between MN and SN. However, this approach would be expensive in terms of signaling load. Note that for each gNB-CU-CP, there can be more than one gNB-CU-UP. Similarly, for each MN, there can be multiple candidate SN nodes, for example, in scenarios where the MN controls large coverage cells, where a potentially large number of smaller cells are used for capacity enhancement within that wide coverage area. Therefore, configuring the data collection report initiation procedure from gNB-CU-CP to each gNB-CU-UP that may serve the UE could be very expensive, especially because of the uncertainty regarding the entity that will serve the UE.

[0048] In the following text, the abbreviation gNB (gNB1, gNB2, ...) will be used to refer to network elements of wireless communication networks capable of serving user equipment. Other examples of such suitable network elements are the eNB defined for E-UTRAN and the ng-eNB defined for NG-RAN. It should be noted that although the following description uses the terms user equipment performance measurement configuration, UE performance measurement configuration, UE performance measurement configuration modification, UE performance measurement, UE performance report, etc., similar principles can also be applied to other performance measurement configurations, performance measurements, and performance reports; that is, these principles are not necessarily related only to user equipment.

[0049] Figure 4 The diagram illustrates a solution in a split architecture according to an embodiment. In this figure, before the source network element gNB1 initiates a handover to the target network element gNB2, the source network element gNB1 sends a 401 request for UE performance measurements to the target network element gNB2. In this message, UE performance measurements are configured for the target network element gNB2, such as UL / DL throughput, DL packet loss, average packet delay, CSI status, etc.

[0050] The measurement configuration may include at least one of the following: a) the requested UE performance measurement, such as UL / DL throughput, DL packet loss, average packet delay, CSI, status, etc.; b) the collection duration, which is a time window that begins upon successful handover and during which the measurements need to be collected; c) the reporting period, indicating the period at which reports are sent if measurements should be sent periodically; and d) the reporting granularity, indicating whether UE performance measurements should be collected on a per PDU session, per UE, per QoS flow, or per DRB basis, to provide several examples.

[0051] The target network element gNB2 sends a 402 Data Collection Response to the source network element gNB1 in response. When a 403 handover from gNB1 to gNB2 is triggered by sending a 404 Handover Request to gNB2, gNB2-CU-CP will further configure the received UE performance measurement request by sending a 405 Bearer Context Establishment Request to gNB2-CU-UP, and gNB2-CU-UP will respond by sending a 406 Bearer Context Establishment Response to gNB2-CU-CP. Additionally or alternatively, gNB2-CU-CP will further configure the received request for UE performance measurements by sending a 407 UE Context Establishment Request to gNB2-DU, and gNB2-DU will respond by sending a 408 UE Context Establishment Response to gNB2-CU-CP. The requested UE performance measurements depend on the entity from which those measurements are requested. For example, if the request for UE performance is sent to gNB-CU-UP, UL / DL throughput, DL packet loss, and average packet delay could be requested. If a request for UE performance is sent to the gNB-DU, CSI information can be requested. In some cases, UE performance can be measured by both the gNB-CU-UP and the gNB-DU. In those cases, the gNB-CU-CP can decide to configure UE performance reports to both the gNB-CU-UP and the gNB-DU to obtain, for example, additional granularity regarding latency, because they measure different aspects of latency. UE performance measurements can be configured to the gNB-CU-UP in the bearer context establishment request message and to the gNB-DU in the UE context establishment request message.

[0052] gNB-CU-UP and gNB-DU may already have UE performance measurements configured, but gNB-CU-CP may need to reconfigure them. This can happen, for example, if a neighboring gNB has requested a modification to the UE performance measurements. This UE performance measurement configuration modification can be accomplished through a bearer context modification procedure for gNB-CU-UP (initiated by gNB-CU-CP) or a UE context modification procedure for gNB-DU (initiated by gNB-CU-CP).

[0053] Even if UE performance can be configured for gNB-CU-UP and gNB-DU before successful handover completion, actual measurements are collected (410) after successful handover completion (409). If the UE performance request information element (IE) is included in the bearer context establishment request message or the bearer context modification request message from gNB-CU-CP to gNB-CU-UP, it triggers the collection of UE performance measurements from CU-UP and reporting via Category 2 procedures in UE performance report message (411).

[0054] Similarly, if the UE performance request information element is included in the UE context establishment request message or the UE context modification request message from gNB-CU-CP to gNB-DU, it triggers the collection of UE performance measurements from gNB-DU and reporting via Category 2 procedures of UE performance report message 412.

[0055] Based on the UE performance configuration included in the bearer context establishment request or bearer context modification request message, UE performance reports from gNB-CU-UP to gNB-CU-CP can be sent periodically or once.

[0056] Similarly, based on the UE performance configuration included in the UE context establishment request or UE context modification request message, UE performance reports from gNB-DU to gNB-CU-CP can be sent periodically or once.

[0057] Similarly, UE performance reports can include measurements at different granularities, such as per PDU session, per DRB, or aggregated UE performance, depending on the configuration in the request message.

[0058] After the gNB-CU-CP in the target gNB (gNB2) merges the UE performance measurements received from gNB-CU-UP and / or gNB-DU, it can report 413 UE performance information to gNB1-CU-CP (source node).

[0059] Figure 5 A solution for a dual-connectivity scenario according to an embodiment is illustrated. In this case, the source gNB sends a 501 request for UE performance measurements to the target gNB before initiating a handover to the target gNB. It should be noted that the data collection report initiation process (arrows 501, 502) can be configured for multiple candidate target gNBs because, at configuration time, the source node may not be able to determine which target gNB the handover will occur to. The target gNB (target primary NG-RAN node) initiates dual connectivity with the target secondary NG-RAN node. Figure 4Similar to the previous implementation, UE performance measurements are configured for the target primary NG-RAN node, such as those related to UL / DL throughput, DL packet loss, average packet delay, CSI status, etc. When a handover from the source gNB to the target primary NG-RAN node (to the gNB-CU-CP) is triggered (503) and the source gNB sends a (504) handover request, the target primary NG-RAN node sends a (505) secondary node add request with a request for UE performance measurements to the target secondary NG-RAN node. This request may include, for example, the requested UE performance measurements, the collection duration for which these measurements need to be collected, the reporting period if measurements should be sent periodically, and the reporting granularity indicating whether UE performance is collected on a per PDU, per UE, per QoS flow, or per DRB basis. If measurements have already been configured for the CU-UP and this is a reconfiguration for updating UE performance measurements, the target secondary NG-RAN node CU-CP will subsequently configure the UE performance measurements for its CU-UP in a bearer context establishment request (506) message or in a bearer context modification request message in an alternative initiated by the gNB-CU-CP. Note that even though this has been omitted for the sake of simplifying the accompanying figures, the target secondary NG-RAN node CU-CP may additionally configure UE performance measurements to its DU in the UE context establishment request message or the UE context modification request message.

[0060] The target secondary NG-RAN node CU-UP will respond by sending a 507 Bearer Context Establishment Response Message or Bearer Context Modification Response Message to the gNB-CU-CP of the secondary NG-RAN node.

[0061] In addition, the gNB-CU-CP of the target primary NG-RAN node can also configure UE performance measurements to its CU-UP in a Bearer Context Establishment Request 508 message or a Bearer Context Modification Request message. The CU-UP of the target primary NG-RAN node then responds by sending a 509 Bearer Context Establishment Response to the gNB-CU-CP of the target primary NG-RAN node.

[0062] The gNB-CU-CP of the target secondary NG-RAN node sends a 510 secondary node add request confirmation message to the gNB-CU-CP of the target primary NG-RAN node.

[0063] As before Figure 4In this embodiment, even if UE performance is configured to the target secondary node gNB-CU-UP before successful handover completion (SN addition completion), actual measurements are collected after successful handover completion 511 512, 513. If the UE performance request IE is included in the bearer context establishment request message 506 or the bearer context modification request message from the target secondary node gNB-CU-CP to gNB-CU-UP, it triggers the collection of UE performance measurements from the CU-UP and reporting via a Category 2 procedure of the UE performance report message.

[0064] Depending on the UE performance configuration included in the bearer context establishment request or bearer context modification request message, a UE performance report (514) can be sent periodically or once from the target secondary node's gNB-CU-UP to the target secondary node's gNB-CU-CP. It should be noted that, although... Figure 5 Only UE performance configuration and triggering reports from gNB-CU-UP are shown, but similarly, one can follow... Figure 4 The principle of gNB-DU is considered. For simplicity, details are omitted in this diagram.

[0065] After the gNB-CU-CP in the target secondary node merges the UE performance measurements received from the gNB-CU-UP, it can report 515 UE performance information to the target primary NG-RAN node (CU-CP).

[0066] Similarly, if the gNB-CU-UP in the target master node is already configured to perform 512 UE performance measurements, the gNB-CU-UP in the target master node sends the 516 UE performance measurement results to the gNB-CU-CP of the target master node. The target master NG-RAN node (CU-CP) combines these measurement results with those received from its own(multiple) gNB-CU-UP(s) and the gNB-DU serving the UE (e.g., related to different QoS flows or DRBs), and further reports them to the source gNB in ​​an XnAP data collection update message (517). Note that, with Figure 4 Similarly, gNB-CU-UP and gNB-DU may already have UE performance measurements configured, but the gNB-CU-CP of the target primary NG-RAN node or the gNB-CU-CP of the target secondary NG-RAN node may need to be reconfigured. This may happen, for example, if a neighboring gNB has already requested a modification to the UE performance measurements. This UE performance measurement configuration modification can be accomplished through a bearer context modification procedure (initiated by gNB-CU-CP) for gNB-CU-UP or through a UE context modification procedure (initiated by gNB-CU-CP) for gNB-DU. Figure 6A solution for a handover scenario within a gNB according to an embodiment is illustrated. The UE can hand over to the same gNB-DU it is connected to or to a new gNB-DU under the same gNB, i.e., the gNB-CU-CP can trigger a 602 handover within one of its gNB-DUs. The UE performance measurement configuration is determined by the gNB (CU-CP) based on the performance it wishes to measure (higher-layer performance measured in the gNB-CU-UP and lower-layer performance of PHY / MAC operation measured in the gNB-DU) 601. Once it determines which measurements it wishes to collect and the measurement configuration regarding: a) the collection period during which UE performance is collected, b) whether the collected UE performance is collected periodically or all at once, and c) the reporting period if UE performance is reported periodically, the gNB-CU-CP sends a context establishment / modification request with the requested UE performance measurement configuration to the entity that should request UE performance measurements from it (e.g., the gNB-DU and gNB-CU-UP). If the UE performance corresponds to PHY / MAC / RLC measurements, the gNB-CU-CP sends a 605 UE Context Establishment Request if the handover occurs in a new gNB-DU within the gNB, or a 605 UE Context Modification Request if the handover occurs in the same gNB-DU serving the UE. The gNB-DU can respond by sending a 606 UE Context Modification Response or a UE Context Establishment Response to the gNB-CU-CP. In the case of a handover within a gNB-DU, the source gNB-DU and the destination gNB-DU are identical. If the UE performance corresponds to higher-layer measurements related to SDAP or PDCP, the gNB-CU-CP sends a 603 Bearer Context Modification Request with the requested UE performance measurement configuration to one or more gNB-CU-UPs serving the UE. The gNB-CU-UP can respond by sending a 604 Bearer Context Modification Response to the gNB-CU-CP.

[0067] When a UE successfully transfers 607 to a new cell or beam within a cell, UE performance measurements configured 609, 610 are collected from gNB-CU-UP and gNB-DU. A successful handover is always visible to gNB-DU. However, it may not be visible to gNB-CU-UP, for example, when gNB-DU does not change during a handover within the gNB; in this case, gNB-CU-UP may not know the handover was successful. In these scenarios, gNB-CU-CP can send a handover success message 608 to gNB-CU-UP via the E1 interface. Based on the UE performance configuration initially determined by gNB-CU-CP, the collected UE performance measurements 611, 612 are reported to CU-CP in the UE performance report. In the case of a handover between gNB-DUs, gNB-CU-UP can infer successful handover completion from existing procedures. According to TS38.425, when gNB-DU detects successful RACH access of a UE, gNB-DU sends an initial DLDATADELIVERYSTATUS frame to gNB-CU-UP. The gNB-CU-UP can then infer that the handover was successful. In the presence of UL service, the gNB-CU-UP can infer that the handover was successful when it received UL data. According to TS38.425, in the presence of DL service, the gNB-CU-UP can set the ReportPolling field in DLUSERDATA(PDUType0) to 1 to request a DL data delivery status report from the gNB-DU. If ReportPollingFlag is set to 1, the gNB-DU will send DLDATADELIVERYSTATUS unless an overload occurs at the corresponding node. By receiving the DL data delivery status report, the gNB-CU-UP can determine, for example, by looking at the second bit "HighestdeliveredNRPDCPSNInd" to determine whether DL service received by the gNB-DU exists. If this is set to 0, it means there is no DL service. If it is set to 1, this indicates that the gNB-DU has received the DL service, meaning the handover was successful. Note that in another embodiment, once the gNB-DU detects successful RACH access of the UE to the corresponding data radio bearer(s), the gNB-DU sends a DLDATADELIVERYSTATUS frame without polling.

[0068] The following section describes the collection of UE performance measurements at the gNB-DU in a specific DC bearer scenario.

[0069] Figure 5 and Figure 6 The signaling flow combinations shown cover the available bearer configurations: - MCG bearer terminated by MN - SCG bearer terminated by SN - SCG bearer terminated by MN - SN terminated MCG bearer - MN termination split bearer (data transmission can use both MCG and SCG resources) - SN-terminated split bearer (data transmission can use both MCG and SCG) In the case of an MCG bearer terminated by the SN and a split bearer terminated by the SN, the target MNCU-CP can also request gNB-DU measurements within the MN for the bearer terminated by the SN. In the case of an SCG bearer terminated by the MN and a split bearer terminated by the MN, the target MN can also request gNB-DU measurements within the SN for the bearer terminated by the MN.

[0070] Figure 7 It shows Figure 5 Dual-connection scenarios and Figure 6 The signaling diagram for the combination of scenarios within the gNB. A UE can switch to the same gNB-DU (serving NG-RAN node) it is connected to, or to a new gNB-DU under the gNB; that is, the gNB-CU-CP can trigger a 702 handover within one of its gNB-DUs. The UE performance measurement configuration is determined by the gNB (CU-CP) based on the performance it wishes to measure (higher-layer performance measured in the gNB-CU-UP and lower-layer performance of PHY / MAC operations measured in the gNB-DU) 701. Once it determines which measurements it wishes to collect and the measurement configuration regarding: a) the duration of UE performance collection, b) whether the collected UE performance is collected periodically or all at once, c) the reporting period if UE performance is reported periodically, and d) the granularity of UE performance, i.e., whether it is per PDU session, per UE, per QoS flow, or per DRB, for example, the gNB-CU-CP serving the NG-RAN node sends a 703 Secondary Node Add Request to the target secondary NG-RAN node, indicating that UE performance measurements are requested. If the measurement has already been configured to the CU-UP and this is a reconfiguration for updating the UE performance measurement, the target secondary NG-RAN node CU-CP will then configure the UE performance measurement to its CU-UP in a Bearer Context Establishment Request 704 message or in a Bearer Context Modification Request message in an alternative initiated by the gNB-CU-CP.

[0071] The target secondary NG-RAN node CU-UP will respond by sending a 705 Bearer Context Establishment Response Message or a Bearer Context Modification Response Message to the gNB-CU-CP of the target secondary NG-RAN node.

[0072] In addition, the gNB-CU-CP serving the NG-RAN node can also configure UE performance measurements to its CU-UP in a Bearer Context Establishment Request 706 message or a Bearer Context Modification Request message. The CU-UP serving the NG-RAN node then responds by sending a 707 Bearer Context Establishment Response to the gNB-CU-CP serving the NG-RAN node.

[0073] The gNB-CU-CP of the target secondary NG-RAN node sends a 708 secondary node add request confirmation message to the gNB-CU-CP of the serving NG-RAN node.

[0074] The configured UE performance measurements are collected from the gNB-CU-UP of the serving NG-RAN node and the gNB-CU-UP of the target secondary NG-RAN node (710, 711). The collected UE performance measurements are reported by the gNB-CU-UP of the target secondary NG-RAN node (712) to the gNB-CU-CP of the target secondary NG-RAN node, and by the gNB-CU-UP of the serving NG-RAN node (713) to the gNB-CU-CP of the serving NG-RAN node. The gNB-CU-CP of the target secondary NG-RAN node reports (714) the UE performance measurements it has collected from the gNB-CU-UP of the target secondary NG-RAN node to the gNB-CU-CP of the serving NG-RAN node.

[0075] The following section provides some examples of tables describing information elements (IEs).

[0076] Table 1 provides an example of the description of information elements for UE performance configuration information (UE performance request) for CU-UP (E1 interface). In the table, the first column (field name) describes the name of the field, the second column (existence) indicates whether the field is mandatory (M) or optional, the third column (scope) indicates the scope of the information element, the fourth column (IE type and reference) indicates the type and reference of the information element, and the fifth column (semantic description) indicates the semantics of the fields of the information element.

[0077] According to this example, the information element includes an indication of the maximum duration of UE performance collection time (the collection duration of UE performance), which can have a value between 1 and 5000 (measured in milliseconds). The collection time is calculated starting from a successful handover execution. The information element also includes a bit stream, such as 32 bits, where some bit positions indicate certain information, such as average UE throughput to the downlink, average UE throughput to the uplink, average packet delay, and average packet loss DL. Other bits can be ignored. There is also an optional field indicating the reporting period. If this field exists, a UE performance report is sent to the gNB-CU-CP according to the indicated period. If this field does not exist, the performance report is sent to the gNB-CU-CP in a single message. The reporting granularity field indicates the reporting granularity of the UE performance measurement.

[0078]

[0079] Table 1 Table 2 describes an example of the information element for a UE performance request entry for the gNB-DU (F1 interface). This information element includes fields similar to those described above for the IE, except that the requested UE performance measurements for the gNB-DU and their reporting granularity will differ from those requested from the gNB-CU-UP.

[0080]

[0081] Table 2 Table 3 describes an example of the information element for a UE performance request entry sent between the primary node and the secondary node (Xn): IE / Group Name. This information element includes fields similar to those presented in Table 1 above.

[0082]

[0083] Table 3 Table 4 describes an example of an information element included in the UE performance request confirmation (Xn, E1, F1 interfaces) as a response to a UE performance request. In this example, the information element includes information on whether all measurement objects were successfully started. A value set to "unsuccessful" can indicate that at least one of the requested measurement objects was not successfully started. In some examples, a value set to "unsuccessful" may mean that none of the requested measurement objects were successfully started. This depends on whether partial success is supported in the report. If the value of this field is set to "unsuccessful," there is also a field that includes a list of measurement objects that failed to start and more detailed information about the failed measurement(s) associated with the cause value that triggered the failure. The UE performance measurement failure report feature is a bit string, where each position in the bitmap indicates the object requested to be reported by NG-RAN Node 2, for example, as shown below: The first bit = average UE throughput DL. The second bit = average UE throughput UL. The third bit = average packet delay. Fourth bit = Average packet loss DL The fifth bit = CSI information Ignore other bits.

[0084] The Reason field carries information about the cause of the failure of the measurement object that could not initiate the measurement. The parameter maxFailedUEPerfMeasObjects indicates the maximum number of measurement objects that may fail for each measurement. According to an example embodiment, this value is 32. Table 4 provides an example where all measurement objects need to successfully initiate the request in order for the measurement request to succeed.

[0085]

[0086] Table 4 Table 5 below provides a table description of an example of an E1APUE performance report message.

[0087] In this example, the message is sent by gNB-CU-UP to report UE performance measurements, i.e., in the direction from gNB-CU-UP to gNB-CU-CP.

[0088]

[0089] Table 5 The numbers in the IE type and reference columns refer to the following numbered portions.

[0090] The parameter `maxnoofPDUsessions` indicates the maximum number of PDU sessions. According to an embodiment, this parameter has a value of 256. The parameter `maxnoofDRBs` indicates the maximum number of DRBs used for the UE. According to an embodiment, this parameter has a value of 32.

[0091] 9.3.1.x1 UE Performance Measurement Information This IE (Table 6) provides information about the measured UE performance.

[0092]

[0093] Table 6 The parameter `maxnoofPDUsessions` indicates the maximum number of PDU sessions directed to the UE. According to an embodiment, this parameter has a value of 8. The parameter `maxnoofQoSFlows` indicates the maximum number of QoS flows allowed within a single PDU session. According to an embodiment, this parameter has a value of 64.

[0094] 9.3.1.x2E1 APUE performance This IE (Table 7) indicates the UE performance measurement metrics.

[0095]

[0096] Table 7 Table 8 below provides a tabular description of an example F1APUE performance report message sent from gNB-DU to gNB-CU.

[0097] This message is sent by the gNB-DU to report UE performance measurements, i.e., in the direction from the gNB-DU to the gNB-CU.

[0098]

[0099] Table 8 The parameter maxnoofDRBs indicates the maximum number of DRBs allowed toward a UE. According to an embodiment, the value of this parameter is 64.

[0100] x3F1APUE performance This IE (Table 9) indicates the UE performance measurement metrics.

[0101]

[0102] Table 9 Table 10 below provides a tabular description of an example of the XnAPUE performance report message.

[0103] This message is sent by the S-NG-RAN node to report UE performance measurements, i.e., in the direction from the S-NG-RAN node to the M-NG-RAN node.

[0104]

[0105] Table 10 The parameter `maxnoofPDUsessions` indicates the maximum number of PDU sessions. According to an embodiment, this parameter has a value of 256. The parameter `maxnoofDRBs` indicates the maximum number of DRBs used for the UE. According to an embodiment, this parameter has a value of 32.

[0106] x5DRBUE performance This IE (Table 11) indicates the UE performance measurement metrics.

[0107]

[0108] Table 11 Table 12 below provides a tabular description of examples of XnAP data collection update messages, modified based on some embodiments of this application.

[0109] The message is sent from NG-RAN node 2 to NG-RAN node 1 to report the requested information.

[0110]

[0111] Table 12 The parameter maxnoofUEReports indicates the maximum number of UEs whose information an NG-RAN node can report. According to an embodiment, the value of this parameter is 16.

[0112] 9.2.3.xx1 Detailed UE performance This IE (Table 13) provides information about the measured UE performance.

[0113]

[0114] Table 13 The parameter `maxnoofQoSFlows` indicates the maximum number of QoS flows allowed within a PDU session. According to an embodiment, the value of this parameter is 64. The parameter `maxnoofPDUsessions` indicates the maximum number of PDU sessions allowed for a UE. According to an embodiment, the value of this parameter is 8. The parameter `maxnoofDRBs` indicates the maximum number of DRBs allowed for a UE. According to an embodiment, the value of this parameter is 32.

[0115] Figure 8 A flowchart of a method according to an embodiment is shown. According to a second aspect, a method is provided comprising: obtaining 801 a performance measurement configuration by a first entity of a first network element of a wireless communication network; sending 802 the performance measurement configuration to a second entity of the first network element in any of a user equipment context-dependent request or a bearer context-dependent request to configure performance measurements in the second entity of the first network element; receiving, at the first entity of the first network element, an 803 acknowledgment message for the user equipment context-dependent request or the bearer context-dependent request from the second entity of the first network element; and receiving, 804, a performance report related to the performance measurements performed by the second entity of the first network element from the second entity of the first network element.

[0116] A communication system typically includes more than one gNB, in which case the gNBs may also be configured to communicate with each other via wired or wireless links designed for this purpose. These links can be used for signaling purposes. A gNB is a computing device configured to control the radio resources of the communication system to which it is coupled. A gNB may also be referred to as a base station, access point, or any other type of interface device, including relay stations capable of operating in a wireless environment. A gNB includes or is coupled to a transceiver. From the gNB's transceiver, a connection is provided to antenna elements that establish a bidirectional radio link to the user equipment. The antenna elements may include multiple antennas or antenna elements. The gNB is also connected to the core network 190 (CN or 5GC or NGC). Depending on the system, the CN-side counterpart may be a Serving Gateway (S-GW, for routing and forwarding user data packets), a Packet Data Network Gateway (P-GW) for providing connectivity from the user equipment (UE) to an external packet data network, or a Mobility Management Entity (MME), etc. The CN may include network entities or nodes that may be referred to as management entities. Examples of network entities include at least an Access Management Function (AMF).

[0117] User equipment (also referred to as user equipment, user terminal, terminal equipment, radio equipment, mobile station (MS), etc.) represents a type of device to which resources on the air interface are allocated and assigned, and thus any features described herein with respect to user equipment can be implemented by corresponding network devices such as relay nodes, eNBs, ng-eNBs, and gNBs. An example of such a relay node is a Layer 3 relay (self-backhaul relay) directed toward a base station.

[0118] User equipment (UAE) generally refers to a portable computing device that includes wireless mobile communication devices with or without a Subscriber Identity Module (SIM), including but not limited to the following types of devices: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), cell phones, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, laptops, and multimedia devices. It should be understood that UAE can also be a device used almost exclusively for uplink purposes, an example being a camera or camcorder that uploads images or video clips to a network. UAE can also be a device capable of operating in an Internet of Things (IoT) network, a scenario in which the ability to transmit data over a network to objects is provided without human-to-human or human-to-computer interaction is required. UAE can also utilize the cloud. In some applications, UAE may include a small portable device with radio components (such as a watch, earphones, or glasses), and computation is performed in the cloud. UAE (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more UAE functions. User equipment can also be referred to as user unit, mobile station, remote terminal, access terminal, user terminal, or user equipment (UE), with only a few names or devices mentioned.

[0119] The memory can be a non-transitory computer-readable medium. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. As a non-limiting example, the data processor can be of any type suitable for the local technical environment and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures.

[0120] Implementations may be carried out in the form of software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside on memory or any computer medium. In example embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "memory" or "computer-readable medium" can be any medium or component that can contain, store, communicate, propagate, or transmit instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0121] In relevant contexts, references to “computer-readable storage medium,” “computer program product,” “tangible computer program,” or “processor” or “processing circuitry” should be understood to encompass not only computers with different architectures (such as single / multiprocessor architectures and sequencer / parallel architectures) but also special-purpose circuits (such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other devices). References to computer-readable program code components, computer programs, computer instructions, computer code, etc., should be understood to express software (such as programmable content of hardware devices) used for programmable processor firmware as instructions for a processor or as configuration or configuration settings for fixed-function devices, gate arrays, programmable logic devices, etc.

[0122] Although the foregoing examples describe embodiments of the invention operating within a wireless device or gNB, it should be understood that the invention as described above can be implemented as part of any apparatus including circuitry for transmitting and / or receiving radio frequency signals. Therefore, for example, embodiments of the invention can be implemented in mobile phones, in base stations, in computers such as desktop computers or tablet computers that include radio frequency communication components (e.g., wireless LAN, cellular radio, etc.).

[0123] Generally, various embodiments of the present invention can be implemented in hardware or dedicated circuitry or any combination thereof. While various aspects of the invention may be illustrated and described as block diagrams or using some other graphical representation, it should be understood that, by way of non-limiting example, the blocks, devices, systems, techniques or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices or some combination thereof.

[0124] Embodiments of the present invention can be practiced in various components such as integrated circuit modules, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), microcontrollers, microprocessors, and combinations of these modules. As used herein, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device such as a mobile phone or server to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may not exist when the software is not required to operate.

[0125] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term "circuit" also encompasses only hardware circuitry or a processor (or multiple processors) or a portion thereof and its accompanying software and / or firmware implementation. The term "circuit" also encompasses, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0126] According to an embodiment, a network element is provided, comprising: Components for obtaining performance measurement configurations from a first entity of a first network element in a wireless communication network; A component for sending performance measurement configuration to a second entity of a first network element in any request of a user equipment context-dependent request or a bearer context-dependent request, to configure performance measurement in the second entity of the first network element; A component for receiving confirmation messages from a second entity of a first network element regarding user equipment-related requests or bearer context-related requests; as well as A component for receiving performance reports related to performance measurements performed by the second entity of the first network element from a second entity of the first network element.

[0127] According to an embodiment, the network element is a base station of a mobile communication network.

[0128] According to an embodiment, an apparatus is provided, comprising: The first circuit is configured to obtain performance measurement configuration from a first entity of a first network element of a wireless communication network. The second circuit is configured to send a performance measurement configuration to a second entity of the first network element in any request, either a user equipment context-dependent request or a bearer context-dependent request, to configure performance measurements in the second entity of the first network element; and The third circuit is configured to receive from the second entity a performance report related to performance measurements performed by the second entity of the first network element.

[0129] The foregoing description has provided a complete and informative description of exemplary embodiments of the invention through exemplary and non-limiting examples. However, various modifications and adjustments may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of the invention will still fall within the scope of the invention.

Claims

1. A method comprising: The performance measurement configuration is obtained from the first entity of the first network element of the wireless communication network; In any of the user equipment context-dependent requests or bearer context-dependent requests, the performance measurement configuration is sent to the second entity of the first network element to configure the performance measurement in the second entity of the first network element; At the first entity of the first network element, an acknowledgment message for the user equipment-related request or the bearer context-related request is received from the second entity of the first network element; as well as Receive a performance report related to the performance measurement performed by the second entity of the first network element from the second entity of the first network element.

2. The method according to claim 1, comprising: The performance measurement configuration is obtained by the first entity through receiving from a source network element, wherein the user equipment is served by the source network element, and the first network element is a target network element for handover.

3. The method according to claim 2, comprising: The performance measurement configuration is sent from the first entity to the second entity, wherein the second entity includes at least one of the following: The user plane of the centralized unit of the target network element, wherein the performance measurement configuration is sent in a bearer context establishment request or a bearer context modification request. The distribution unit of the target network element, wherein the performance measurement configuration is sent in the user equipment context establishment request.

4. The method according to claim 2 or 3, comprising: The performance report received at the first entity of the first network element is sent to the source network element.

5. The method according to any one of claims 1 to 4, comprising: The performance report is received in multiple messages.

6. The method according to any one of claims 1 to 4, comprising: The performance report is received in a single message.

7. The method of claim 1, wherein the first network element is a target auxiliary network element, the first entity of the first network element is the control plane of the centralized unit of the target auxiliary network element, and the second entity of the first network element is the user plane of the centralized unit of the same target auxiliary network element, the method comprising: The performance measurement configuration is obtained from the source network element by the target master network element; In the secondary node addition request, the performance measurement configuration is forwarded to the first entity of the target secondary network element; In the bearer context establishment add request, the performance measurement configuration is sent to the user plane of the centralized unit of the target secondary network element; The performance report is received at the first entity of the first network element from the second entity of the first network element.

8. The method according to claim 7, further comprising: The performance report is received at the target master network element from the first entity of the first network element; as well as The performance report is received from the target master network element at the source network element.

9. The method according to claim 7 or 8, further comprising: In a bearer context establishment request, the user equipment performance measurement configuration is sent from the control plane of the centralized unit of the target main network element to the user plane of the centralized unit of the target main network element.

10. The method according to claim 1, comprising: The performance measurement configuration is obtained from the control plane of the centralized unit of the first network element; The performance measurement configuration is sent from the control of the centralized unit of the first network element to the user plane of the centralized unit of the first network element; as well as The performance report is received from the user plane of the centralized unit of the first network element.

11. The method of claim 10, comprising: The performance measurement configuration is sent from the centralized unit of the first network element to the distributed unit of the first network element.

12. The method according to claim 10 or 11, comprising: The switch was confirmed to be successful; as well as Send a successful handover indication to the control plane of the centralized unit of the first network element, and instruct the control plane of the centralized unit of the first network element to begin the performance measurement.

13. The method according to any one of claims 1 to 12, comprising: The network nodes of the wireless communication network determine the user equipment performance measurement configuration, and the network nodes provide the connection between the user equipment and the wireless communication network.

14. The method according to any one of claims 1 to 13, comprising: The performance measurement configuration includes one or more of the following parameters: Uplink throughput Downlink throughput Downlink packet loss Average grouping delay, Energy measurement, such as energy cost metrics, Channel state information.

15. The method according to any one of claims 1 to 14, comprising: For any of the user equipment context-dependent requests or bearer context-dependent requests, use one of the following bearer configurations: The primary cell group bearer terminated by the primary node; The secondary cell group carrying the secondary node terminates; The secondary cell group carrying the primary node terminated; The primary cell group bearer terminated by the secondary node; Split load when the master node terminates; Split-bearer termination of auxiliary nodes.

16. The method according to any one of claims 1 to 15, comprising: Use the received performance report to evaluate the performance of the switch.

17. The method according to any one of claims 1 to 16, wherein, The performance configuration is the user equipment performance configuration, and the performance report is the user equipment performance report.

18. An apparatus comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The performance measurement configuration is obtained from the first entity of the first network element of the wireless communication network; In any of the user equipment context-dependent requests or bearer context-dependent requests, the performance measurement configuration is sent to the second entity of the first network element to configure the performance measurement in the second entity of the first network element; as well as Receive a performance report from the second entity related to the performance measurement performed by the second entity of the first network element.

19. The apparatus according to claim 18, wherein, The at least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the method according to any one of claims 2 to 15.

20. The apparatus according to claim 18 or 19, wherein, The device is a base station of the mobile communication network.

Images