UE-assisted performance monitoring for RRM measurement prediction in ai mobility
The UE-assisted performance monitoring method addresses the limitations of existing solutions by predicting RRM measurements and reporting performance metrics, enhancing network mobility decisions and efficiency.
Patent Information
- Application Number
- PCT/SE2026/050331
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing solutions for UE-assisted performance monitoring are not suitable for RRM measurement prediction in AI mobility, as they are designed for Al-based beam management and Al-based CSI prediction, and do not account for the longer time correlations and detailed sampling times required for RRM measurements.
A method where the UE receives an RRC configuration to predict RRM measurements for first time occasions based on RRM measurements for second time occasions, with performance monitoring metrics calculated using RRM measurement differences, mean square error, and cumulative distribution functions, and reports these metrics to the network node.
Enables accurate performance monitoring for RRM measurement prediction, allowing the network node to make informed mobility decisions by utilizing UE-assisted performance metrics, thereby improving network efficiency and reliability.
Smart Images

Figure SE2026050331_12112026_PF_FP_ABST
Abstract
Description
[0001] UE-ASSISTED PERFORMANCE MONITORING FOR RRM MEASUREMENT PREDICTION IN Al MOBILITY
[0002] FIELD
[0003] The present disclosure relates to wireless communications, and in particular, to user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility.
[0004] BACKGROUND
[0005] 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.
[0006] In 3rd Generation Partnership Project (3GPP) New Radio (NR) standardization work, a new 3 GPP Release 19 (3 GPP Rel-19) study item (SI) on artificial intelligence / machine learning (AI / ML) for the NR mobility started in 2024. This study item explored the benefits of augmenting mobility and enabling improved support of AI / ML based algorithms for enhanced performance, reduced complexity and / or overhead. Use cases in mobility may include radio resource management (RRM) measurement prediction, measurement event prediction and radio link failure / handover failure (RLF / HOF) prediction.
[0007] RRM measurement prediction in this SI includes RRM measurement prediction in the time domain, the spatial domain and the frequency domain. For temporal-domain prediction, an Al model predicts RRM measurement results for future time instances, and / or may predict unavailable RRM measurement results for partial time instances in the past and / or present. These predictions may be based on available RRM results measured by the UE. For spatial-domain prediction, an Al model predicts RRM measurement results for the beams or cells in Set A according to available RRM measurement results of the beams or cells in Set B. The Al model may predict cell-level RRM measurement results based on RRM measurement results of a set of beams. In frequency-domain prediction, an Al model predicts RRM measurement results for the frequency(ies) in Set A according toavailable RRM measurement results for the frequency(ies) in Set B. Some examples for intra-frequency temporal RRM measurement prediction are shown in FIGS. 1, 2 and 3.
[0008] Performance monitoring
[0009] In UE-assisted performance monitoring for an inference configuration with a UE-side model for Al use cases in wireless communication, according to the network configuration, a UE is configured to report the information of performance metric(s) of the inference configuration to the network node. The performance metric(s) is (are) derived by the UE via predicted measurement results and the corresponding ground truths for this inference configuration.
[0010] The existing solutions for UE-assisted performance monitoring with a UE-side model in wireless communication are designed for Al-based beam management, Al-based CSI prediction, but not for RRM measurement prediction in Al mobility. As such, the performance metrics designed for Al-based beam management and Al-based CSI prediction are not suitable for performance metrics in RRM measurement prediction in Al mobility. Furthermore, an RRM measurement / prediction in a time occasion may be correlated with other RRM measurements / predictions within a relatively longer time window compared to measurement / prediction in Al-based beam management and AI-based CSI prediction. Moreover, the legacy RRM measurement and report framework only indicates the report periodicity rather than the detailed sampling time for reported RRM measurements. Thus, the UE may not be able to measure the expected ground truth for its performance metric calculation. Consequently, the network node is not able to get the corresponding performance metric information used by the network node for UE-side RRM measurement prediction.
[0011] Therefore, the solutions for UE-assisted performance monitoring in Al-based beam management and Al-based CSI prediction are not suitable for RRM measurement prediction and RRM measurement event prediction.
[0012] SUMMARY
[0013] Some embodiments advantageously provide methods, user equipment (UE) and network nodes for user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility.
[0014] Some embodiments include a method performed by a UE, where the UE receives a radio resource control (RRC) configuration from the network node. The RRC configuration configures the UE to predict RRM measurement results for first timeoccasions via measuring RRM for second time occasions. The prediction and the measurement may be indicated via an inference configuration. The UE may receive this configuration as part of the inference configuration included in the RRC configuration. The inference configuration may instruct the UE to perform prediction in a temporal, spatial or frequency domain for a configured set of resources (frequencies, cells, beams). In some embodiments, the inference configuration is received in a first measurement identifier configuration (e.g., instance of the IE MeasIdToAddMod). The UE may perform RRM measurement for third time occasions (or sample RRM measurement results in the third time occasions), where the first time occasions and the third time occasions may be overlapped or partially overlapped. Moreover, the RRM measurement in the third time occasions may be based on at least partial RRM measurement results for the second time occasions and may be based on at least partial RRM prediction results for the first time occasions. The RRM measurements may include those needed for the calculation of the RRM measurement results in the third time occasions. The UE may receive this instruction as part of the performance monitoring configuration included in the RRC configuration. Such configuration may instruct the UE to perform performance monitoring based on a specific type of performance monitoring metrics described herein. In some embodiments, the performance monitoring configuration is received in a second measurement identifier configuration (e.g., instance of the IE MeasIdToAddMod). In some embodiments, the first and second measurement Identifier configuration(s) are the same i.e. same instance of the IE MeasIdToAddMod for PM and inference configuration(s). In some embodiments, the first and second measurement Identifier configuration(s) are different, but associated i.e. different instances of the IE MeasIdToAddMod for PM and inference configuration(s). In some embodiments, the performance monitoring configuration is associated with the inference configuration. In some embodiments, both the inference configuration and the performance monitoring configuration are associated by being configured as part of the same instance of a measurement identifier configuration (e.g., same MeasIdToAddMod). However, in that case, there may be different parameters for transmitting a report including one or more predictions (s) (inferences) and for transmitting one or more performance monitoring metrics related to the inference configuration. In some embodiments, the inference configuration and the performance monitoring configuration are associated by being configured with different instances of a measurement identifier configuration (e.g., same MeasIdToAddMod), but one including a pointer to the other.The UE may report the performance metric(s) to the network node, where the performance metrics are calculated via measurement results for the third time occasion and partial predicted RRM measurement results for the first time occasion.
[0015] Furthermore, performance monitoring metrics may be one or more of
[0016] • one or more RRM measurement differences where each RRM measurement difference is for a monitoring occasion;
[0017] • mean square error of RRM measurement prediction within the monitoring occasions;
[0018] • mean of RRM measurement differences within the monitoring occasions; and / or
[0019] • cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of an RRM measurement difference within the monitoring occasions. The mean square error of RRM measurement prediction within the monitoring occasions may include a mean value of the square of RRM measurement difference of the monitoring occasions.
[0020] In some embodiments, an RRM measurement difference in a monitoring occasion may be the difference of a measured RRM measurement in the monitoring occasion and a predicted RRM measurement in a corresponding prediction occasion (e.g., RRM measurement difference = predicted RRM measurement - measured RRM measurement). The corresponding prediction occasion means the prediction occasion which is the same as the monitoring occasion or within a specific time distance from the monitoring occasion. Or corresponding prediction occasion may be at a time occasion that is approximated as the same as the monitoring occasion.
[0021] In some embodiments, an RRM measurement may be a reference signal receive power (RSRP) or may be reference signal received quality (RSRQ) or may be signal to interference plus noise (SINR). The RRM measurement may be cell-level or may be beam -level.
[0022] In some embodiments, the predicted RRM measurement results for the first time occasions and the measured RRM measurement results for the second time occasions may be in the same carrier frequency range or may be in different carrier frequency ranges.
[0023] In some embodiments, the first time occasions may be the same as the third time occasions or may be different from the third time occasions. In some embodiments, the first time occasions may partially overlap the third time occasions.In some embodiments, the third time occasions may be determined by the first time occasions and the monitoring window. For example, the third time occasions may be the first time occasions in a monitoring window configured by the network node for performance monitoring of the inference configuration. The monitoring window may be explicitly or implicitly configured by the performance monitoring configuration.
[0024] In some embodiments, the performance monitoring configuration may include a percentage of the prediction samples in a time window that should be monitored.
[0025] In some embodiments, the performance monitoring configuration may include at least one of an inference configuration ID, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information and other measurement information for reporting, monitoring window information, measurement gap information and so on.
[0026] In some embodiments, the monitoring window determining the third time occasions with respect to the first time occasion is calculated by configuring a distance in time from a point in time of the first time occasion (e.g., the start of the first time occasion) and a time window starting at the time identified by the distance in time from the first occasion.
[0027] In some embodiments, the UE may be configured with a percentage value (e.g., X percent) wherein the percentage indicates for what portion of the predictions in a period of time (e.g., monitoring window) the UE should perform the performance monitoring. The UE may be configured with a second time period within the first time period in which the prediction samples performed in such window should be monitored based on the performance monitoring configuration.
[0028] In some embodiments, the UE may be configured with one or more thresholds for the performance monitoring metric and for each threshold with a percentage value indicating for what portion of the predictions in a period of time (e.g., monitoring window) the UE should perform the performance monitoring. If the measured performance metric is above or below a specific threshold, the UE will perform performance monitoring according to the percentage associated to the threshold. Whether each percentage value is associated to performance monitoring measurements above or below the corresponding threshold may be either configured at the UE or pre-defined.
[0029] In some embodiments, the UE may be configured to report the RRM measurement results for the second time occasions to the network node.In some embodiments, for network-side performance monitoring of the inference configuration, the network node calculates the performance information based on at least the received predicted RRM measurement results for the first time occasions and the received measured RRM measurement results for the third time occasions. The network node may use the performance information to decide whether to use the RRM measurement event prediction based on the RRM measurement prediction of the inference configuration for mobility decision. The network node may use the performance information to decide whether to send deactivation indication and / or release indication of the inference configuration to the UE.
[0030] In some embodiments, assuming a split RAN architecture where a Central Unit (CU) is in charge of the RRC protocol and a Distributed Unit (DU) is in charge of the PHY / MAC / RLC layers, the CU, before configuring the UE with measurement occasions one, two and three, requests to the DU to assign measurement gaps for the measurements that need them, e.g., measurement occasion two and / or measurement occasion 3.
[0031] In some embodiments, the CU informs the DU whether each of the requested measurement gaps are needed to derive measurements on the basis of which the UE derives measurement predictions (e.g., measurements collected at second measurement occasion) or if they are needed to derive measurements used to calculate performance metrics (e.g., measurements collected at third measurement occasion). The gNB-DU may decide to prioritize measurement gap allocation for one purpose or another. For example, in case of high loads, the DU may prioritize measurement gap allocation to derive measurements that allow inference of measurement predictions, but not to allocate gaps for measurement that are used to derive performance monitoring measurements.
[0032] In some embodiments, the DU may indicate the timing at which measurement gaps may be allocated. Depending on such indication, the CU may decide to configure the UE with a first, second and third measurement occasion as initially planned or to modify such configuration or to cancel such configuration. In some embodiments, if the DU may allocate measurement gaps for the third measurement occasion that do not overlap in time with the first measurement occasion, the CU may determine that such gaps will not provide a sufficient performance monitoring metric reading and the CU may therefore decide to modify the overall measurement configuration or cancel it.
[0033] In some embodiments, the UE may be configured with performance monitoring configuration including one or more of:• Performance monitoring window to use for monitoring over the performance of the prediction samples in the configured monitoring window;
[0034] • Percentage of the prediction samples in a time window that should be monitored based on the performance monitoring configuration;
[0035] • Performance metric information and associated information;
[0036] • Inference configuration ID;
[0037] • Performance monitoring report configuration (e.g., event information to trigger performance monitoring, event information to trigger performance monitoring reporting, report periodicity information); and / or
[0038] • Measurement gap information
[0039] In some embodiments, disclosed methods may be used to support UE-assisted performance monitoring for RRM measurement prediction with a UE-side model.
[0040] According to one aspect, a method in a network node is provided. The method includes sending the UE a performance monitoring configuration, the performance monitoring configuration configuring the UE to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions. The process includes receiving from the UE, RRM measurement predictions according to the performance monitoring configuration.
[0041] In some embodiments, the method includes determining performance information based at least in part on at least one of the received RRM measurement predictions and the RRM measurements. In some embodiments, the method includes using the performance information to decide whether to use an RRM measurement prediction for a mobility decision. In some embodiments, a central unit, CU, of the network node is configured to request an assignment of measurement gaps from a distributed unit, DU, of the network node. In some embodiments, the CU is configured to inform the DU whether each requested measurement gap is to be used by the UE to derive RRM measurement predictions. In some embodiments, the DU is configured to prioritize measurement gap allocations. In some embodiments, the DU is configured to indicate a timing for which measurement gaps are allocated. In some embodiments, the CU is configured to modify the performance monitoring configuration based at least in part on the indicated timing.
[0042] According to another aspect, a method in a UE is provided. The method includes receiving from the network node a performance monitoring configuration, the performance monitoring configuration configuring the UE to perform radio resourcemanagement, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions. The process includes performing the configured RRM measurement predictions according to the performance monitoring configuration.
[0043] In some embodiments, the performance monitoring configuration configures the UE to perform RRM measurement predictions in at least one of a time domain, a frequency domain and a beam domain. In some embodiments, the method includes performing RRM measurements for a third set of time occasions. In some embodiments, the third set of time occasions are determined based at least in part on a monitoring window configured by the performance monitoring configuration. In some embodiments, the third set of time occasions and the first set of time occasions at least partially overlap. In some embodiments, the RRM measurements for the third set of time occasions are based at least in part on partial RRM measurement predictions for the first set of time occasions. In some embodiments, the method includes reporting performance metrics determined based at least in part on RRM measurement predictions for the third set of time occasions. In some embodiments, the performance metrics include RRM measurement differences, wherein an RRM measurement difference is for one monitoring occasion. In some embodiments, the performance metrics include a mean square error of RRM measurement predictions within monitoring occasions. In some embodiments, the performance metrics include a mean of RRM measurement differences within monitoring occasions. In some embodiments, the performance metrics include cumulative distribution function information for RRM measurement differences within monitoring occasions. In some embodiments, the RRM measurement predictions for the first set of time occasions and the RRM measurements for the second time occasion are in a same carrier frequency range. In some embodiments, the performance monitoring configuration includes at least one of an inference configuration, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information, and monitoring window information. In some embodiments, the performance monitoring configuration indicates a percentage of RRM measurement prediction samples in a time window to be monitored. In some embodiments, the performance monitoring configuration includes at least one threshold to determine a percentage of RRM measurements to be made in a period of time.
[0044] According to yet another aspect, a network node configured to communicate with a user equipment, UE, is provided. The network node includes processing circuitryconfigured to send the UE a performance monitoring configuration, the performance monitoring configuration configuring the UE to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions. The processing circuitry is configured to receive from the UE, RRM measurement predictions according to the performance monitoring configuration.
[0045] According to this aspect, in some embodiments, the processing circuitry is configured to determine performance information based at least in part on at least one of the received RRM measurement predictions and the RRM measurements. In some embodiments, the processing circuitry is configured to use the performance information to decide whether to use an RRM measurement prediction for a mobility decision. In some embodiments, a central unit, CU, of the network node is configured to request an assignment of measurement gaps from a distributed unit, DU, of the network node. In some embodiments, the CU is configured to inform the DU whether each requested measurement gap is to be used by the UE to derive RRM measurement predictions. In some embodiments, the DU is configured to prioritize measurement gap allocations. In some embodiments, the DU is configured to indicate a timing for which measurement gaps are allocated. In some embodiments, the CU is configured to modify the performance monitoring configuration based at least in part on the indicated timing.
[0046] According to another aspect, a user equipment, UE, configured to communicate with a network node is provided. The UE includes processing circuitry configured to: receive from the network node a performance monitoring configuration, the performance monitoring configuration configuring the UE to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions. The processing circuitry is configured to perform the RRM measurement predictions according to the performance monitoring configuration.
[0047] According to this aspect, in some embodiments, the performance monitoring configuration configures the UE to perform RRM measurement predictions in at least one of a time domain, a frequency domain and a beam domain. In some embodiments, the processing circuitry is configured to perform RRM measurements for a third set of time occasions. In some embodiments, the third set of time occasions are determined based at least in part on a monitoring window configured by the performance monitoring configuration. In some embodiments, the third set of time occasions and the first set oftime occasions at least partially overlap. In some embodiments, the RRM measurements for the third set of time occasions are based at least in part on partial RRM measurement predictions for the first set of time occasions. In some embodiments, the processing circuitry is configured to report performance metrics determined based at least in part on RRM measurement predictions for the third set of time occasions. In some embodiments, the performance metrics include RRM measurement differences, wherein an RRM measurement difference is for one monitoring occasion. In some embodiments, the performance metrics include a mean square error of RRM measurement predictions within monitoring occasions. In some embodiments, the performance metrics include a mean of RRM measurement differences within monitoring occasions. In some embodiments, the performance metrics include cumulative distribution function information for RRM measurement differences within monitoring occasions. In some embodiments, the RRM measurement predictions for the first set of time occasions and the RRM measurements for the second time occasion are in a same carrier frequency range. In some embodiments, the performance monitoring configuration includes at least one of an inference configuration, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information, and monitoring window information. In some embodiments, the performance monitoring configuration indicates a percentage of RRM measurement prediction samples in a time window to be monitored. In some embodiments, the performance monitoring configuration includes at least one threshold to determine a percentage of RRM measurements to be made in a period of time.
[0048] BRIEF DESCRIPTION OF THE DRAWINGS
[0049] 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:
[0050] FIG. 1 is an example of intra-frequency temporal RRM measurement prediction case A;
[0051] FIG. 2 is a first example of intra-frequency temporal RRM measurement prediction case B;
[0052] FIG. 3 is a second example of intra-frequency temporal RRM measurement prediction case B;FIG. 4 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;
[0053] FIG. 5 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;
[0054] FIG. 6 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;
[0055] FIG. 7 is a flowchart of an example process in a network node for user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility according to some embodiments of the present disclosure;
[0056] FIG. 8 is a flowchart of an example process in a user equipment for user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility according to some embodiments of the present disclosure;
[0057] FIG. 9 is a flowchart of an example process in a network node for user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility according to some embodiments of the present disclosure;
[0058] FIG. 10 is a flowchart of an example process in a user equipment for user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility according to some embodiments of the present disclosure; and
[0059] FIG. 11 is an example of inter-frequency RRM measurement prediction;
[0060] FIG. 12 is a first example for UE assisted performance monitoring for RRM measurement prediction;
[0061] FIG. 13 is a second example for UE assisted performance monitoring for RRM measurement prediction; and
[0062] FIG. 14 is a third example for UE assisted performance monitoring for RRM measurement prediction.
[0063] DETAILED DESCRIPTION
[0064] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related touser equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility. 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.
[0065] 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, components, and / or groups thereof.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] The term “network node” used herein can 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 corenetwork 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.
[0070] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can 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.
[0071] Also, in some embodiments the generic term “radio network node” is used. It can 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).
[0072] 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.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, can be distributed among several physical devices.
[0073] 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.
[0074] Some embodiments are directed to user equipment (UE) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility.
[0075] Returning to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 4 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G) 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.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.
[0076] Also, it is contemplated that a UE 22 can 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 can 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 can 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.
[0077] A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which may be configured to configure the UE with a radio resource control (RRC) configuration to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration. A user equipment 22 is configured to include a prediction unit 26 which may be configured to perform a set of RRM measurement predictions according to the inference configuration.
[0078] 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. 5.
[0079] 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 RFreceivers, 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.
[0080] 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).
[0081] 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 / or to cause such methods, and / or processes to be performed, e.g., by network node 16.
[0082] 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 configuration unit 24 which may be configured to configure the UE with a radio resource control (RRC) configuration to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration.
[0083] 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 theseparate 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 wireless technologies 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.
[0084] 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).
[0085] 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.
[0086] Network node 15 can 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 can be arranged such that network node 15 can perform various core network functions. Network node 15 can communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.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.
[0087] 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0088] 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).
[0089] 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 beexecutable 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.
[0090] 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 is configured 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. For example, the processing circuitry 50 of the user equipment 22 may include a prediction unit 26 which may be configured to perform a set of RRM measurement predictions according to the inference configuration.
[0091] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 4.
[0092] 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.
[0093] Although FIGS. 4 and 5 show various “units” such as configuration unit 24 and prediction unit 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.
[0094] FIG. 6 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 6 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. 6as 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. 4 and 5. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0095] 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.
[0096] 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.
[0097] 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. 6 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.
[0098] FIG. 7 is a flowchart of an example process in a network node 16 for user equipment (UE) assisted performance monitoring for radio resource managementmeasurement prediction in artificial intelligence (Al) mobility. 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 configuration unit 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 configure the UE 22 with a radio resource control (RRC) configuration to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration (Block S10). The process includes receiving a set of RRM measurement predictions according to the inference configuration (Block S12).
[0099] In some embodiments, the inference configuration configures the UE 22 to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain. In some embodiments, the RRC configuration includes a performance monitoring configuration. In some embodiments, the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier. In some embodiments, performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions. In some embodiments, the performance monitoring metrics include at least one RRM measurement differences and RRM measurement predictions.
[0100] FIG. 8 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the prediction unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive from the network node 16 a radio resource control (RRC) configuration to configure the UE 22 to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration (Block S14). The process includes performing a set of RRM measurement predictions according to the inference configuration (Block SI 6).
[0101] In some embodiments, the inference configuration configures the UE 22 to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain. In some embodiments, the method includes performing RRM measurements for a third set of time occasions. In some embodiments, the first setof time occasions overlap with the third set of time occasions. In some embodiments, the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurements for the second set of time occasions. In some embodiments, the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurement predictions for the first set of time occasions. In some embodiments, performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions. In some embodiments, the performance monitoring metrics include at least one RRM measurement differences and RRM measurement prediction. In some embodiments, the RRC configuration includes a performance monitoring configuration. In some embodiments, the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier.
[0102] FIG. 9 is a flowchart of an example process in a network node 16 for user equipment (UE 22) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility. 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 configuration unit 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 the UE 22 a performance monitoring configuration, the performance monitoring configuration configuring the UE 22 to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions (Block SI 8). The process includes receiving from the UE 22, RRM measurement predictions according to the performance monitoring configuration (Block S20).
[0103] In some embodiments, the method includes determining performance information based at least in part on at least one of the received RRM measurement predictions and the RRM measurements. In some embodiments, the method includes using the performance information to decide whether to use an RRM measurement prediction for a mobility decision. In some embodiments, a central unit, CU, of the network node 16 is configured to request an assignment of measurement gaps from a distributed unit, DU, of the network node 16. In some embodiments, the CU is configured to inform the DU whether each requested measurement gap is to be used by the UE 22 to derive RRM measurement predictions. In some embodiments, the DU is configured to prioritize measurement gap allocations. In some embodiments, the DU is configured to indicate a timing for whichmeasurement gaps are allocated. In some embodiments, the CU is configured to modify the performance monitoring configuration based at least in part on the indicated timing.
[0104] FIG. 10 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the prediction unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive from the network node 16 a performance monitoring configuration, the performance monitoring configuration configuring the UE 22 to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions (Block S22). The process includes performing the configured RRM measurement predictions according to the performance monitoring configuration (Block S24).
[0105] In some embodiments, the performance monitoring configuration configures the UE 22 to perform RRM measurement predictions in at least one of a time domain, a frequency domain and a beam domain. In some embodiments, the method includes performing RRM measurements for a third set of time occasions. In some embodiments, the third set of time occasions are determined based at least in part on a monitoring window configured by the performance monitoring configuration. In some embodiments, the third set of time occasions and the first set of time occasions at least partially overlap. In some embodiments, the RRM measurements for the third set of time occasions are based at least in part on partial RRM measurement predictions for the first set of time occasions. In some embodiments, the method includes reporting performance metrics determined based at least in part on RRM measurement predictions for the third set of time occasions. In some embodiments, the performance metrics include RRM measurement differences, wherein an RRM measurement difference is for one monitoring occasion. In some embodiments, the performance metrics include a mean square error of RRM measurement predictions within monitoring occasions. In some embodiments, the performance metrics include a mean of RRM measurement differences within monitoring occasions. In some embodiments, the performance metrics include cumulative distribution function information for RRM measurement differences within monitoring occasions. In some embodiments, the RRM measurement predictions for the first set of time occasions and the RRM measurements for the second time occasion are in a same carrier frequency range. In some embodiments, the performance monitoring configuration includes at leastone of an inference configuration, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information, and monitoring window information. In some embodiments, the performance monitoring configuration indicates a percentage of RRM measurement prediction samples in a time window to be monitored. In some embodiments, the performance monitoring configuration includes at least one threshold to determine a percentage of RRM measurements to be made in a period of time.
[0106] 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 user equipment (UE 22) assisted performance monitoring for radio resource management measurement prediction in artificial intelligence (Al) mobility. Intra-frequency temporal RRM measurement prediction case A
[0107] In some embodiments, a UE 22 is configured by a network node 16 to predict RRM measurements in future time instances based on one or more available measured RRM measurement results in the past and / or present, for a same downlink reference signal. The downlink reference signal may be for example, a synchronization signal block (SSB), channel state information reference signal (CSI-RS), SSB resource set, CSI-RS resource set, non-zero power (NZP) CSI-RS resource set. The predictions may be in a same carrier frequency range, and the periodicity of predicted RRM measurements may be the same as the periodicity of measured RRM for reporting. The UE 22 may be configured by the network node 16 to report the performance metric information to the network node 16. The performance metrics may be calculated based on the predicted RRM measurements and the corresponding measured ground-truth RRM measurements. The performance metrics may indicate one or more of following information:
[0108] • One or more RSRP (or RSRQ or SINR) differences within a monitoring window, where an RSRP (or RSRQ or SINR) difference is measured for a monitoring occasion;
[0109] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window;
[0110] • Mean of RSRP (or RSRQ or SINR) differences within a monitoring window;
[0111] • Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within a monitoring window;• Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF);
[0112] where:
[0113] • A monitoring window may include one or more monitoring time occasions;
[0114] • An RSRP (or RSRQ or SINR) difference in a monitoring occasion is the difference of a predicted RSRP (or RSRQ or SINR) in the monitoring occasion and a measured RSRP (or RSRQ or SINR) in the monitoring occasion (e.g., RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP (or RSRQ or SINR)), where the RSRP (or RSRQ or SINR) may be L3 filtered RSRP (or RSRQ or SINR) or LI filtered RSRP(or RSRQ or SINR), and may be cell-level RSRP (or RSRQ or SINR) or beam-level RSRP (or RSRQ or SINR);
[0115] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s) of the monitoring window.
[0116] In some embodiments, the UE 22 reports the calculated performance metrics to the network node 16 and may report other associated information to the network node 16, such as via RRM measurement and report framework, or via logged measurement and report framework, or via immediate logged measurement and report framework. If the received performance metric information is good, then the network node 16 may not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the received performance metric information is not good enough, then the network node 16 may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network node 16 may deactivate and / or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network node 16 and / or may be done by the UE 22.
[0117] Intra-frequency temporal RRM measurement prediction case B
[0118] In some embodiments, a UE 22 is configured by a network node 16 to measure RRM for observation time occasions and then use the measurement results to predict RRM measurements for prediction time occasions. This may be done for the same downlink reference signal(s) (e.g., SSB, CSLRS, SSB resource set, CSLRS resource set,NZP CSI-RS resource set) and same carrier frequency range. The observation time occasions and the prediction time occasions may have no overlap. The UE 22 may be configured by the network node 16 to measure RRM for monitoring time occasions. To get the RRM measurement results for monitoring time occasions, the UE 22 may use some RRM measurement results for observation time occasions and may need to use some RRM measurement prediction results for prediction time occasions. In some embodiments, the UE 22 may use new RRM measurement results which are not used to get RRM measurement results for observation time occasions. This may be so because an RRM measurement results in a monitoring time occasion may be a filtered measurement result based on historical RRM measurement information and / or present RRM measurement information. The prediction time occasions and the monitoring time occasions may be partially overlapped or totally overlapped. The UE 22 may be configured by the network node 16 to report the performance metric information to the network node 16, where the performance metric(s) are calculated based on the predicted RRM measurements and the corresponding measured ground-truth RRM measurements. The performance metric information may indicate one or more of following:
[0119] • one or more RSRP (or RSRQ or SINR) differences within a monitoring window, where an RSRP (or RSRQ or SINR) difference for a monitoring occasion;
[0120] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window;
[0121] • Mean of RSRP (or RSRQ or SINR) differences within a monitoring window;
[0122] • Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within a monitoring window; and / or
[0123] • Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF), where:
[0124] • one monitoring window may include one or more monitoring time occasions;
[0125] • one RSRP (or RSRQ or SINR) difference in a monitoring occasion is the difference of a predicted RSRP (or RSRQ or SINR) in the monitoring occasion and a measured RSRP (or RSRQ or SINR) in the monitoring occasion (e.g., RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP(or RSRQ or SINR)), where the RSRP (or RSRQ or SINR) may be L3 filteredRSRP (or RSRQ or SINR) or LI filtered RSRP (or RSRQ or SINR), and may be cell-level RSRP (or RSRQ or SINR) or beam-level RSRP (or RSRQ or SINR); and / or
[0126] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s) of the monitoring window.
[0127] In some embodiments, the UE 22 reports the calculated performance metric(s) to the network node 16 and may report other associated information to the network node 16, such as via RRM measurement and report framework, or via logged measurement and report framework, or via immediate logged measurement and report framework. If the received performance metric information is good, then the network node 16 may not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the received performance metric information is not good enough, then the network node 16 may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network node 16 may deactivate and / or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network node 16 and / or may be done by the UE 22.
[0128] Inter-frequency RRM measurement prediction
[0129] Referring to FIG. 11, in some embodiments, a UE 22 is configured by a network node 16 to predict RRM measurement results in a first carrier frequency and in one or more prediction time occasions via at least RRM measurement results in another one or more second carrier frequencies in one or more observation time occasions. Also, or in the alternative, the UE 22 may be configured to perform RRM measurement results in the first carrier frequency in one or more observation time occasions, where the prediction time occasions and the observation time occasions in different carrier frequencies may be partially overlapped or totally overlapped. In some embodiments, the UE 22 is configured by the network node 16 to measure RRM in the first carrier frequency and in one or more monitoring time occasions, where the monitoring time occasions may be a subset of the prediction time occasions or may be the same as the prediction time occasions. To get the RRM measurement results for monitoring time occasions, the UE 22 may use some RRM measurement results for observation time occasions. The UE 22 may need to use some RRM measurement prediction results for prediction time occasions and may use newRRM measurement results which are not used to get RRM measurement results for observation time occasions. They may not be used because an RRM measurement result in a monitoring time occasion may be a filtered measurement result based on historical RRM measurement information and / or present RRM measurement information. The UE 22 is further configured by the network node 16 to report the performance metric information to the network node 16. In some embodiments, the performance metric(s) are calculated based on the measured RRM results in monitoring time occasions and the corresponding predicted RRM measurements in prediction time occasions and may indicate one or more of following:
[0130] • one or more RSRP (or RSRQ or SINR) differences within a monitoring window, where an RSRP (or RSRQ or SINR) difference for a monitoring occasion;
[0131] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window;
[0132] • Mean of RSRP (or RSRQ or SINR) differences within a monitoring window; and / or
[0133] • Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within a monitoring window, where:
[0134] • A monitoring window may include one or more monitoring time occasions;
[0135] • An RSRP (or RSRQ or SINR) difference in a monitoring occasion is the difference of a predicted RSRP (or RSRQ or SINR) in the monitoring occasion and a measured RSRP (or RSRQ or SINR) in the monitoring occasion (e.g., RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP(or RSRQ or SINR)), where the RSRP (or RSRQ or SINR) may be L3 filtered RSRP (or RSRQ or SINR) or LI filtered RSRP (or RSRQ or SINR), and may be cell-level RSRP (or RSRQ or SINR) or beam-level RSRP (or RSRQ or SINR); and / or
[0136] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s) of the monitoring window.
[0137] In some embodiments, the UE 22 reports the calculated performance metric(s) to the network node 16 and may report other associated information to the network node 16 such as via RRM measurement and report framework, or via logged measurement and report framework, or via immediate logged measurement and report framework. If thereceived performance metric information is good, then the network node 16 may not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the received performance metric information is not good enough, then the network node 16 may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network node 16 may deactivate and / or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network node 16 and / or may be done by the UE 22.
[0138] Spatial RRM measurement prediction with cell-level RRM measurement prediction based on partial beam-level RRM measurements
[0139] In some embodiments, via inference configuration, a UE 22 is configured by a network node 16 to measure beam -level RRM of partial beams of a cell and then use the measurement results to predict cell-level RRM for this cell. The UE 22 is further configured by the network node 16, via monitoring configuration, to measure cell-level RRM based on RRM measurement results of all beams of the cell. In some embodiments, the monitoring configuration from the network node 16 to the UE 22 is associated with the inference configuration from the network node 16 to the UE 22. The UE 22 may use partial or all beam-level (or cell-level) RRM measurement results, which are measured due to the inference configuration, and may use new beam-level (or cell-level) RRM measurements, to get beam-level (or cell-level) RRM measurement results requested for measurement in monitoring configuration. In some embodiments, the UE 22 may be configured by the network node 16 to report the performance metric information to the network node 16, where the performance metric(s) are calculated based on the measured RRM measurements in monitoring time occasions and the corresponding predicted RRM measurements in prediction time occasions. The performance metric information may indicate one or more of following information:
[0140] • one or more RSRP (or RSRQ or SINR) differences within a monitoring window, where an RSRP difference for a monitoring occasion;
[0141] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window;
[0142] • Mean of RSRP (or RSRQ or SINR) differences within a monitoring window; and / or• Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within a monitoring window, where:
[0143] • A monitoring window may include one or more monitoring time occasions;
[0144] • An RSRP (or RSRQ or SINR) difference in a monitoring occasion is the difference of a predicted RSRP (or RSRQ or SINR) in the monitoring occasion and a measured RSRP (or RSRQ or SINR) in the monitoring occasion (e.g., RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP (or RSRQ or SINR)), where the RSRP (or RSRQ or SINR) may be L3 filtered RSRP (or RSRQ or SINR) or LI filtered RSRP (or RSRQ or SINR), and may be cell-level RSRP (or RSRQ or SINR) or beam-level RSRP (or RSRQ or SINR); and / or
[0145] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s) of the monitoring window.
[0146] In some embodiments, the UE 22 reports the calculated performance metric(s) to the network node 16 and may report other associated information to the network node 16, such as via RRM measurement and report framework, or via logged measurement and report framework, or via immediate logged measurement and report framework. If the received performance metric information is good, then the network node 16 may not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the received performance metric information is not good enough, then the network node 16 may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network node 16 may deactivate and / or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network node 16 and / or may be done by the UE 22.
[0147] Spatial L3 -beam -level RRM measurement prediction
[0148] In spatial L3 -beam -level RRM measurement prediction, for a neighbor cell, the UE 22 may be configured by the network node 16 to measure the beams in Set B in one or more observation time occasions and predict one or more strongest beams (e.g., beam index, SSB index, CSLRS resource index CSLRS resource set index) in Set A in one ormore prediction time occasions. The UE 22 may be configured to predict RRM measurements (e.g., L3-RSRP) of the one or more strongest beams in Set A in the prediction time occasions, where the configuration is done via inference configuration. In some embodiments, the network node 16 configures the UE 22 to measure the beams in Set A in one or more monitoring occasions and report the performance metrics derived based on the measured RRM in monitoring occasions and the predicted RRM in prediction occasions. In some embodiments, the monitoring occasions may be a subset of the prediction occasions or the same as the prediction occasions. The configuration may be by via a performance monitoring configuration that is associated with inference configuration information. The performance metric(s) may indicate one or more of following:
[0149] • One or more RSRP (or RSRQ or SINR) differences within a monitoring window, where an RSRP difference for a monitoring occasion;
[0150] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window;
[0151] • Mean of RSRP (or RSRQ or SINR) differences within a monitoring window;
[0152] • Cumulative distribution function (CDF) information (e.g., 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within a monitoring window; and / or
[0153] • Accuracy for Top K strongest beam prediction (e.g., number of correct prediction, percentage of correct prediction) within a monitoring window:
[0154] o If the condition below is met, the transmission occasion is counted as an accurate reference signal prediction instance, otherwise it is not counted as an accurate reference signal prediction instance:
[0155] ■ Condition: whether at least one of a Top M beam(s) of resource set(s) for monitoring is among Top-K predicted beams of Set A, where K is number of predicted beam(s) in the corresponding inference report per time instance for the inference configuration, M is configured by the network node 16 for monitoring and may be 1 or 2. The monitoring beam set may be same as or smaller than the prediction beam set;
[0156] where:
[0157] • A monitoring window may include one or more monitoring time occasions;
[0158] • An RSRP (or RSRQ or SINR) difference in a monitoring occasion is the difference of a predicted RSRP (or RSRQ or SINR) in the monitoring occasion and a measured RSRP (or RSRQ or SINR) in the monitoring occasion (e.g.,RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP(or RSRQ or SINR)), where the RSRP (or RSRQ or SINR) may be L3 filtered RSRP (or RSRQ or SINR) or LI filtered RSRP (or RSRQ or SINR), and may be cell-level RSRP (or RSRQ or SINR) or beam-level RSRP (or RSRQ or SINR); and / or
[0159] • Mean square error of RSRP (or RSRQ or SINR) prediction within a monitoring window means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s) of the monitoring window.
[0160] In some embodiments, the UE 22 reports the calculated performance metric(s) to the network node 16 and may report other associated information to the network node 16 such as via RRM measurement and report framework, or via logged measurement and report framework, or via immediate logged measurement and report framework. If the received performance metric information is good, then the network node 16 may not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the received performance metric information is not good enough, then the network node 16 may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network node 16 may deactivate and / or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network node 16 and / or may be done by the UE 22.
[0161] Association between Inference Configuration and Performance Monitoring configuration In some embodiments, the UE 22 receives an inference configuration in an instance of the IE MeasIdToAddMod (or equivalent), in which the UE 22 is indicated a measld, a reporting configuration identifier (reportConfigld) and a measurement object identifier (measObjectld). The reportConfigld may point to a reporting configuration including one or more parameters indicating to the UE 22 how the UE 22 is to report the one or more inferences, e.g., time domain, spatial domain and / or frequency domain predictions. The measObjectld may point to a measurement object configuration including one or more parameters indicating to the UE 22 what is to be predicted, e.g., a cell, cells in a frequency, beams, and further parameters about radio resources to be predicted. The measld identifies the inference configuration.
[0162] In some embodiments, in addition to the inference configuration, the UE 22 receives (e.g., in the same message or in a different message) an associated or relatedperformance monitoring configuration, in a different instance of the IE MeasIdToAddMod, which may include one or more of:
[0163] A reportConfigld pointing to a reporting configuration including one or more parameters indicating to the UE 22 how the UE 22 is to report the one or more Performance Monitoring (PM) metric; and / or
[0164] A measObjectld pointing to a measurement object indicating what is to be measured and / or inferred in order to calculate a PM metric according to what is requested to be reported (in reporting configuration):
[0165] o For example, in the case of time-domain prediction, the measurement object identifier may point to the same measurement object as the inference configuration; and / or
[0166] o For example, in the case of frequency-domain prediction, the measurement object identifier may point to a measurement object which includes the frequency to be predicted, which is also indicated in the inference configuration, and may also include the frequency to be measured.
[0167] Owing to the structure, the reporting configuration for PM could be completely different compared to the reporting configuration for the inferences. For example, the PM may be reported periodically, while the inferences could be reported based on the fulfillment of an event (i.e. there may be different report types). Or, even if the same report type is used the parameters may be quite different, e.g., one may have longer periodicity than the other, have larger time to trigger, etc. In addition, the performance monitoring configuration may include a pointer to the associated inference configuration, so that the UE 22 knows that a given PM reporting is for a given inference configuration. That pointer may be the measld which identifies the associated inference configuration.
[0168] In some embodiments, the UE 22 determines that a measurement configuration identifier (e.g., instance of the IE MeasIdToAddMod) is associated to PM (and not to a measurement configuration and / or inference configuration) by the fact that the measurement configuration identifier includes an additional measld associated to an inference configuration. An example is shown in FIG. 12.
[0169] In some embodiments, when the UE 22 is triggered to transmit a report that includes inference(s) according to the inference configuration, the UE 22 includes the measld identifying the inference configuration (e.g., measld=x in the example above). When the UE 22 is triggered to transmit a report including the PM metric(s) according tothe PM configuration, the UE 22 may include the measld identifying the PM configuration (e.g., measld=y in the example above).
[0170] In some embodiments, in addition to the inference configuration, the UE 22 receives (e.g., in the same message or in a different message) an associated or related performance monitoring configuration, in a different instance of the IE MeasIdToAddMod, including a reportConfigld pointing to a reporting configuration. This may include one or more parameters indicating to the UE 22 how the UE 22 is to report the one or more Performance Monitoring (PM) metrics which may include or be associated with:
[0171] A measObjectld pointing to a measurement object indicating what is to be measured and / or inferred in order to calculate a PM metric according to what is requested to be reported (in reporting configuration):
[0172] o For example, in the case of time-domain prediction, the measurement object identifier may point to the same measurement object as the inference configuration; and / or
[0173] o For example, in the case of frequency-domain prediction, the measurement object identifier may point to a measurement object which includes the frequency to be predicted, also indicated in the inference configuration, but it may also include the frequency to be measured.
[0174] Due to the structure, the reporting configuration for PM could be completely different compared to the reporting configuration for the inferences. For example, the PM may be reported periodically, while the inferences could be reported based on the fulfillment of an event (i.e., there may be different report types). Or, even if the same report type is used the parameters may be quite different, e.g., one may have longer periodicity than the other, have larger time to trigger, etc. In addition, the performance monitoring configuration may be associated to the inference configuration by the fact that both occupy the same position in a respective list. For example:
[0175] List of inference configurations
[0176] MeasIdToAddMod, measld=x
[0177] MeasIdToAddMod, measld=y
[0178] MeasIdToAddMod, measld=z
[0179] List of PM configurations
[0180] MeasIdToAddMod, measld=a
[0181] MeasIdToAddMod, measld=bMeasIdToAddMod, measld=c
[0182] The inference configuration with measld=x may be associated with the PM configuration in measdld=a (because they are both in the first position in their respective lists). The inference configuration with measld=y may be associated with the PM configuration in measdld=b (because they are both in the first position in their respective lists). The inference configuration with measld=z may be associated with the PM configuration in measdld=c (because they are both in the first position in their respective lists).
[0183] In some embodiments, when there are still different measld(s), when the UE 22 is triggered to transmit a report include inference(s) according to the inference configuration, the UE 22 includes the measld identifying the inference configuration (e.g., measld=x in the example above). When the UE 22 is triggered to transmit a report including the PM metric(s) according to the PM configuration, the UE 22 may include the measld identifying the PM configuration (e.g., measld=y in the example above).
[0184] In some embodiments, within the inference configuration, the UE 22 receives (e.g., in the same message or in a different message) an associated / or related performance monitoring configuration, i.e., within the same instance of the IE MeasIdToAddMod for the inference configuration. According to this embodiment, the instance of the IE MeasIdToAddMod (or IES nested within) would include an additional reportConfigld pointing to a reporting configuration including one or more parameters indicating to the UE 22 how the UE 22 is to report the one or more Performance Monitoring (PM) metric (or a whole ReportConfig itself). That would also allow the reporting configuration for PM could be completely different compared to the reporting configuration for the inferences, even if both are configured as part of the inference configuration. For example, the PM may be reported periodically, while the inferences could be reported based on the fulfillment of an event (i.e. there may be different report types). Or, even if the same report type is used, the parameters may be quite different e.g., one may have longer periodicity than the other, have larger time to trigger, etc. An example is shown in FIG. 13.
[0185] In some embodiments, considering that a single measld may be defined for both the inference and the PM, when the UE 22 is triggered to transmit a report include inference(s) according to the inference configuration, the UE 22 may include the measld identifying the inference configuration (e.g., measld=x in the example above). When the UE 22 is triggered to transmit a report including the PM metric(s) according to the PMconfiguration, the UE 22 may include the same measld, also identifying the PM configuration (e.g., measld=x in the example above). When they are the same, the UE 22 may include an indication to distinguish between the quantities being reported, and / or the UE 22 may simply include different quantities depending on the report which is being triggered.
[0186] In some embodiments related to an inference configuration for frequency domain predict! on(s) of RRM measurements, the inference configuration includes an explicit configuration of a set A of frequencies (e.g., indicated to the UE 22 via one or more measurement object ID(s) for frequencies to be predicted, like MeasObjectldSetA) and an explicit indication of set B of frequencies, i.e. indicating one or more frequencies to be measured, like MeasObjectldSetB. Then, the received PM configuration associated to the inference configuration, in a different MeasIdToAddMod instance, may include the measld pointing to the inference configuration, and in both instances the same measObjectld pointing to set A may be included, as shown in FIG. 14.
[0187] In some embodiments related to an inference configuration for frequency domain predict! on(s) of RRM measurements, the inference configuration includes an explicit configuration of only a set A of one or more frequencies (e.g., indicated to the UE 22 via one or more measurement object ID(s) for frequencies to be predicted, like MeasObjectldSetA.) Then, in some embodiments, in the PM configuration, in a different MeasIdToAddMod instance, only a measld is included and pointing to the same measurement object that needs to be predicted.
[0188] Intra RAN node signaling support
[0189] Assuming that the RAN serving the UE 22 is split between a CU serving the RRC layer and a DU serving PHY / MAC / RLC layers, the CU may signal to the DU information concerning the measurement configuration that enables the UE 22 to collect measurement allowing inference of predicted measurements (such as inference input measurements - for the first measurement occasion) as well as measurements allowing for the calculation of performance metrics (for the third measurement occasion). By taking the 5G split RAN architecture as an example, the examples below show how the Fl interface between the gNB-CU and the gNB-DU may be enhanced with new information informing the gNB-DU about the purpose of the configured measurement and enabling the gNB-CU to determine whether the measurement configuration (such as the measurement gap allocation) derived by the gNB-DU are suitable for the measurement process the gNB-CU needs to configure at the UE 22.It should be noted that the CU to DU RRC Information IE is signaled by the gNB- CU to the gNB-DU on a per UE basis and to configure specific measurement configurations for the UE 22. The IE indicates to the gNB-DU the measurement process the gNB-CU wants to configure and enables the gNB-DU to derive lower layers configurations, such as measurement gaps, to support the measurement configuration. CU to DU RRC Information
[0190] The following information element (IE) contains the RRC Information that are sent from gNB-CU to gNB-DU.
[0191] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality CG-Configlnfo 0 OCTET Includes the
[0192] STRING CG- Configlnfo
[0193] message, as
[0194] defined in TS
[0195] 38.331 [8],
[0196] UE- 0 OCTET This IE is
[0197] CapabilityRAT- STRING used in the
[0198] ContainerList NG-RAN
[0199] and it
[0200] includes the
[0201] UE- CapabilityRA
[0202] T- ContainerLis
[0203] t IE, as
[0204] defined in TS
[0205] 38.331 [8],
[0206] MeasConfig 0 OCTET Includes the
[0207] STRING MeasConfig
[0208] IE, as
[0209] defined in TS
[0210] 38.331 [8]
[0211] (without the
[0212]
[0213] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality MeasGapCo
[0214] nfig IE).
[0215] For EN- DC / NGEN- DC
[0216] operation,
[0217] includes the
[0218] list ofFR2
[0219] frequencies
[0220] for which the
[0221] gNB-CU
[0222] requests the
[0223] gNB-DU to
[0224] generate
[0225] gaps.
[0226] For NG- RAN, NE- DC and MN
[0227] for NR-NR
[0228] DC, includes
[0229] the list of
[0230] FR1 and / or
[0231] FR2
[0232] frequencies,
[0233] for which the
[0234] gNB-CU
[0235] requests the
[0236] gNB-DU to
[0237] generate gaps
[0238] and the gap
[0239] type (per-UE
[0240] or per-FR).
[0241]
[0242] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality Handover 0 OCTET Includes the YES ignore Preparation STRING HandoverPre
[0243] Information parationlnfor
[0244] mation
[0245] message, as
[0246] defined in TS
[0247] 38.331 [8],
[0248] CellGroupConfi 0 OCTET Includes the YES ignore g STRING CellGroupCo
[0249] nfig IE, as
[0250] defined in TS
[0251] 38.331 [8],
[0252] Measurement 0 OCTET Contains the YES ignore Timing STRING Measurement
[0253] Configuration TimingConfi
[0254] guration
[0255] inter-node
[0256] message
[0257] defined in TS
[0258] 38.331 [8],
[0259] In EN- DC / NGEN- DC, it is
[0260] included
[0261] when the
[0262] gaps for FR2
[0263] are requested
[0264] to be
[0265] configured
[0266] by the
[0267] MeNB. For
[0268] MN in NR-
[0269]
[0270] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality NR DC, it is
[0271] included
[0272] when the
[0273] gaps for FR2
[0274] and / or FR1
[0275] are requested
[0276] by the SgNB
[0277] UE Assistancein 0 OCTET Includes the YES ignore formation STRING UEAssistanc
[0278] eInformation
[0279] message, as
[0280] defined in TS
[0281] 38.331 [8],
[0282] CG-Config 0 OCTET Includes the YES ignore STRING CG-Config
[0283] message, as
[0284] defined in TS
[0285] 38.331 [8],
[0286] UE Assistancein 0 OCTET Includes the YES ignore formationEUTR STRING UEAssistanc
[0287] A eInformation
[0288] message, as
[0289] defined in TS
[0290] 36.331
[0041] ,
[0291] Location 0 OCTET Includes the YES ignore Measurement STRING LocationMea
[0292] Information surementlnfo
[0293] IE, as
[0294] defined in TS
[0295] 38.331[8]
[0296] MUSIM- 0 OCTET Includes the YES reject GapConfig STRING MUSIM-
[0297]
[0298] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality GapConfig
[0299] IE as defined
[0300] in TS 38.331
[0301] [8].
[0302] SDT-MAC- 0 OCTET Includes the YES ignore PHY-CG- STRING SDT-MAC- Config PHY-CG- Config IE, as
[0303] defined in TS
[0304] 38.331 [8],
[0305] MBSInterestlndi 0 OCTET Includes the YES ignore cation STRING MBSInterestI
[0306] ndication
[0307] message as
[0308] defined in TS
[0309] 38.331 [8],
[0310] NeedForGapsInf 0 OCTET Includes the YES ignore oNR STRING NeedForGap
[0311] slnfoNR IE,
[0312] as defined in
[0313] TS 38.331
[0314] [8].
[0315] NeedForGapNC 0 OCTET Includes the YES ignore SG-InfoNR STRING NeedForGap
[0316] NCSG- InfoNR IE, as
[0317] defined in TS
[0318] 38.331 [8],
[0319] NeedForGapNC 0 OCTET Includes the YES ignore SG-InfoEUTRA STRING NeedForGap
[0320] NCSG- InfoEUTRA
[0321]
[0322] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality IE, as
[0323] defined in TS
[0324] 38.331 [8],
[0325] ConfigRestrictln 0 OCTET Includes the YES ignore foDAPS STRING ConfigRestri
[0326] ctlnfoDAPS- rl6 IE as
[0327] defined in TS
[0328] 38.331 [8],
[0329] This IE is
[0330] used at the
[0331] source node
[0332] if DAPS HO
[0333] is
[0334] configured.
[0335] Preconfigured 0 ENUMERA YES ignore measurement TED(true,
[0336] GAP Request •••)
[0337] NeedForlnterrup 0 OCTET Includes the YES ignore tionlnfoNR STRING NeedForlnte
[0338] rruptionlnfo
[0339] NR IE, as
[0340] defined in TS
[0341] 38.331 [8],
[0342] musim- 0 ENUMERA Corresponds YES ignore CapabilityRestri TED (true, to the musim- ctionlndi cation •••) CapRestricti
[0343] onlnd
[0344] contained in
[0345] the
[0346] RRCSetupCo
[0347] mplete
[0348]
[0349] lE / Group Name Presence Range IE type and Semantics Criticality Assigned reference description Criticality message or
[0350] the
[0351] RRCResume
[0352] Complete
[0353] message as
[0354] defined in TS
[0355] 38.331 [8],
[0356] musim- 0 OCTET Includes the YES ignore CandidateBand STRING musim- List CandidateBa
[0357] ndList
[0358] contained in
[0359] the
[0360] OtherConfig
[0361] IE, as
[0362] defined in TS
[0363] 38.331 [8],
[0364] Measurement 0 ENUMERA It indicates YES ignore Purpose TED the purpose
[0365] (mobility of the
[0366] measuremen measurement
[0367] t, inference
[0368] input
[0369] measuremen
[0370] t,
[0371] performance
[0372] monitoring
[0373] measuremen
[0374] t, ...)
[0375]
[0376] The newly added Measurement Purpose IE may take different values. As an example, the IE may have three values: mobility measurement, inference inputmeasurement and performance monitoring measurement. “Mobility measurement” indicates that the purpose of the measurement is to perform mobility actions, e.g., to determine if any mobility events are fulfilled and to trigger a handover for the UE 22. The “Inference Input Measurement” indicates that the measurement purpose is to enable the RAN and / or the UE 22 to collect information that enable inference of mobility measurements. The value “performance monitoring measurement” indicates that the measurement purpose is to enable the UE 22 and / or the RAN to derive measurements that are used to derive the performance of specific predictions.
[0377] The actual values of the Measurement Purpose IE may be different and more granular. For example there could be values that indicate a combined purpose for the measurements, e.g., mobility and inference input measurements.
[0378] The gNB-DU may take the measurement purpose into account to decide how to handle the measurement configuration and whether to apply the required configuration, e.g., measurement gap allocation, to support the measurement.
[0379] Some embodiments may include one or more of the following:
[0380] Embodiment Al . A user equipment (UE) configured to communicate with a network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to:
[0381] receive from the network node a radio resource control (RRC) configuration to configure the UE to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration; and
[0382] perform a set of RRM measurement predictions according to the inference configuration.
[0383] Embodiment A2. The UE of Embodiment Al, wherein the inference configuration configures the UE to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain.
[0384] Embodiment A3. The UE of any of Embodiments Al and A2, wherein the UE, radio interface and / or processing circuitry are configured to perform RRM measurements for a third set of time occasions.
[0385] Embodiment A4. The UE of Embodiment A3, wherein the first set of time occasions overlap with the third set of time occasions.Embodiment A5. The UE of any of Embodiments A3 and A4, wherein the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurements for the second set of time occasions.
[0386] Embodiment A6. The UE of Embodiment A5, wherein the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurement predictions for the first set of time occasions.
[0387] Embodiment A7. The UE of any of Embodiments A1-A6, wherein performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions.
[0388] Embodiment A8. The UE of Embodiment A7, wherein the performance monitoring metrics include at least one RRM measurement differences and RRM measurement prediction.
[0389] Embodiment A9. The UE of any of Embodiments A1-A8, wherein the RRC configuration includes a performance monitoring configuration.
[0390] Embodiment A10. The UE of Embodiment A9, wherein the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier.
[0391] Embodiment Bl. A method implemented in a user equipment (UE) that is configured to communicate with a network node, the method comprising:
[0392] receiving from the network node a radio resource control (RRC) configuration to configure the UE to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration; and
[0393] performing a set of RRM measurement predictions according to the inference configuration.
[0394] Embodiment B2. The method of Embodiment Bl, wherein the inference configuration configures the UE to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain.
[0395] Embodiment B3. The method of any of Embodiments Bl and B2, comprising performing RRM measurements for a third set of time occasions.
[0396] Embodiment B4. The method of Embodiment B3, wherein the first set of time occasions overlap with the third set of time occasions.Embodiment B5. The method of any of Embodiments B3 and B4, wherein the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurements for the second set of time occasions.
[0397] Embodiment B6. The method of Embodiment B5, wherein the RRM measurements performed for the third set of time occasions are based at least in part on RRM measurement predictions for the first set of time occasions.
[0398] Embodiment B7. The method of any of Embodiments B1-B6, wherein performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions.
[0399] Embodiment B8. The method of Embodiment B7, wherein the performance monitoring metrics include at least one RRM measurement differences and RRM measurement prediction.
[0400] Embodiment B9. The method of any of Embodiments B1-B8, wherein the RRC configuration includes a performance monitoring configuration.
[0401] Embodiment BIO. The method of Embodiment B9, wherein the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier.
[0402] Embodiment Cl. A network node configured to communicate with a user equipment (UE), the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to:
[0403] configure the UE with a radio resource control (RRC) configuration to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration; and
[0404] receive a set of RRM measurement predictions according to the inference configuration.
[0405] Embodiment C2. The network node of Embodiment Cl, wherein the inference configuration configures the UE to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain.
[0406] Embodiment C3. The network node of any of Embodiments Cl and C2, wherein the RRC configuration includes a performance monitoring configuration.
[0407] Embodiment C4. The network node of Embodiment C3, wherein the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier.Embodiment C5. The network node of any of Embodiments C1-C4, wherein performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions.
[0408] Embodiment C6. The network node of Embodiment C5, wherein the performance monitoring metrics include at least one RRM measurement differences and RRM measurement predictions.
[0409] Embodiment DI . A method implemented in a network node that is configured to communicate with a user equipment, the method comprising:
[0410] configuring the UE with a radio resource control (RRC) configuration to predict radio resource management (RRM) measurements for a first set of time occasions via RRM measurements for a second set of time occasions, the RRC configuration including an inference configuration; and
[0411] receiving a set of RRM measurement predictions according to the inference configuration.
[0412] Embodiment D2. The method of Embodiment DI, wherein the inference configuration configures the UE to perform the set of RRM measurement predictions in one of a time domain, a frequency domain and a spatial domain.
[0413] Embodiment D3. The method of any of Embodiments DI and D2, wherein the RRC configuration includes a performance monitoring configuration.
[0414] Embodiment D4. The method of Embodiment D3, wherein the inference configuration and the performance monitoring configuration are associated by at least one instance of an identifier.
[0415] Embodiment D5. The method of any of Embodiments D1-D4, wherein performance monitoring metrics are determined based at least in part on RRM measurements for a third set of time occasions.
[0416] Embodiment D6. The method of Embodiment D5, wherein the performance monitoring metrics include at least one RRM measurement differences and RRM measurement predictions.
[0417] 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 can 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.
[0418] 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, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.
[0419] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.
[0420] 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.
[0421] 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 / actsinvolved. 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.
[0422] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
[0423] 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 can 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.
[0424] Abbreviations that may be used in the preceding description include:
[0425] Abbreviation Explanation
[0426] Al Artificial Intelligence ARFCN Absolute Radio-Frequency Channel Number ARQ Automatic Repeat Request BM Beam Management CE Control Element CSI-RS Channel State Information reference signal CU Central Unit
[0427] CU-CP Central Unit Control Plane CU-UP Central Unit User PlaneDCAF Data Collection Application Function DCI Downlink Control Information DRX Discontinuous reception
[0428] DU Distributed Unit HARQ Hybrid ARQ
[0429] HOF Handover Failure
[0430] IE Information Element
[0431] L2 Layer-2
[0432] MAC Medium Access Control MDT Minimization Drive Test MIMO Multiple Input Multiple Output ML Machine Learning
[0433] MNO Mobility Network Operator NW Network
[0434] NWDAF Network Data Analytics Function OAM Operation Administration and Maintenance OTT Over-the-Top
[0435] PBCH Physical Broadcast Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PLMN Public Land Mobile network RAN Radio Access Network
[0436] RLF Radio Link Failure
[0437] RLM Radio Link Monitoring RRC Radio Resource Control RRM Radio Resource Management RSRP Reference signal received power RSRQ Reference signal received quality RS SI Received Signal Strength Indicator SINR Signal to Interference and noise Ratio SSB Synchronization Signal Block SSB Synchronization Signal BlockUCI Uplink Control Information
[0438] UE User equipment
[0439] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.
Claims
What is claimed is:
1. A method in a user equipment, UE (22), configured to communicate with a network node (16), the method comprising:receiving (S22) from the network node (16) a performance monitoring configuration, the performance monitoring configuration configuring the UE (22) to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions; and performing (S24) the configured RRM measurement predictions according to the performance monitoring configuration.
2. The method of Claim 1, wherein the performance monitoring configuration configures the UE (22) to perform RRM measurement predictions in at least one of a time domain, a frequency domain and a beam domain.
3. The method of any one of Claims 1 and 2, further comprising performing RRM measurements for a third set of time occasions.
4. The method of Claim 3, wherein the third set of time occasions are determined based at least in part on a monitoring window configured by the performance monitoring configuration.
5. The method of any one of Claims 3 and 4, wherein the third set of time occasions and the first set of time occasions at least partially overlap.
6. The method of any one of Claims 3-5, wherein the RRM measurements for the third set of time occasions are based at least in part on partial RRM measurement predictions for the first set of time occasions.
7. The method of any one of Claims 3-6, further comprising reporting performance metrics determined based at least in part on RRM measurement predictions for the third set of time occasions.
8. The method of Claim 7, wherein the performance metrics include RRM measurement differences, wherein an RRM measurement difference is for one monitoring occasion.
9. The method of any one of Claims 7 and 8, wherein the performance metrics include a mean square error of RRM measurement predictions within monitoring occasions.
10. The method of any one of Claims 7-9, wherein the performance metrics include a mean of RRM measurement differences within monitoring occasions.
11. The method of any one of Claims 7-10, wherein the performance metrics include cumulative distribution function information for RRM measurement differences within monitoring occasions.
12. The method of any one of Claims 1-11, wherein the RRM measurement predictions for the first set of time occasions and the RRM measurements for the second time occasion are in a same carrier frequency range.
13. The method of any one of Claims 1-12, wherein the performance monitoring configuration includes at least one of an inference configuration, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information, and monitoring window information.
14. The method of any one of Claims 1-13, wherein the performance monitoring configuration indicates a percentage of RRM measurement prediction samples in a time window to be monitored.
15. The method of any one of Claims 1-14, wherein the performance monitoring configuration includes at least one threshold to determine a percentage of RRM measurements to be made in a period of time.
16. A method in a network node (16) configured to communicate with a user equipment, UE (22), the method comprising:sending (SI 8) the UE (22) a performance monitoring configuration, the performance monitoring configuration configuring the UE (22) to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions; andreceiving (S20) from the UE (22), RRM measurement predictions according to the performance monitoring configuration.
17. The method of Claim 16, further comprising determining performance information based at least in part on at least one of the received RRM measurement predictions and the RRM measurements.
18. The method of Claim 17, further comprising using the performance information to decide whether to use an RRM measurement prediction for a mobility decision.
19. The method of any one of Claims 16-18, wherein a central unit, CU, of the network node (16) is configured to request an assignment of measurement gaps from a distributed unit, DU, of the network node (16).
20. The method of Claim 19, wherein the CU is configured to inform the DU whether each requested measurement gap is to be used by the UE (22) to derive RRM measurement predictions.
21. The method of any one of Claims 19 and 20, wherein the DU is configured to prioritize measurement gap allocations.
22. The method of any one of Claims 19-21, wherein the DU is configured to indicate a timing for which measurement gaps are allocated.
23. The method of Claim 22, wherein the CU is configured to modify the performance monitoring configuration based at least in part on the indicated timing.
24. A user equipment, UE (22), configured to communicate with a network node (16), the UE (22) comprising processing circuitry configured to:receive from the network node (16) a performance monitoring configuration, the performance monitoring configuration configuring the UE (22) to perform radio resource management, RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions; andperform the RRM measurement predictions according to the performance monitoring configuration.
25. The UE (22) of Claim 24, wherein the performance monitoring configuration configures the UE (22) to perform RRM measurement predictions in at least one of a time domain, a frequency domain and a beam domain.
26. The UE (22) of any one of Claims 24 and 25, wherein the processing circuitry is configured to perform RRM measurements for a third set of time occasions.
27. The UE (22) of Claim 26, wherein the third set of time occasions are determined based at least in part on a monitoring window configured by the performance monitoring configuration.
28. The UE (22) of any one of Claims 26 and 27, wherein the third set of time occasions and the first set of time occasions at least partially overlap.
29. The UE (22) of any one of Claims 26-28, wherein the RRM measurements for the third set of time occasions are based at least in part on partial RRM measurement predictions for the first set of time occasions.
30. The UE (22) of any one of Claims 26-29, wherein the processing circuitry is configured to report performance metrics determined based at least in part on RRM measurement predictions for the third set of time occasions.
31. The UE (22) of Claim 30, wherein the performance metrics include RRM measurement differences, wherein an RRM measurement difference is for one monitoring occasion.
32. The UE (22) of any one of Claims 30 and 31, wherein the performance metrics include a mean square error of RRM measurement predictions within monitoring occasions.
33. The UE (22) of any one of Claims 30 and 32, wherein the performance metrics include a mean of RRM measurement differences within monitoring occasions.
34. The UE (22) of any one of Claims 30-33, wherein the performance metrics include cumulative distribution function information for RRM measurement differences within monitoring occasions.
35. The UE (22) of any one of Claims 24-34, wherein the RRM measurement predictions for the first set of time occasions and the RRM measurements for the second time occasion are in a same carrier frequency range.
36. The UE (22) of any one of Claims 24-35, wherein the performance monitoring configuration includes at least one of an inference configuration, event information to trigger performance monitoring, event information to trigger a performance monitoring report, report periodicity information, performance metric information, and monitoring window information.
37. The UE (22) of any one of Claims 24-36, wherein the performance monitoring configuration indicates a percentage of RRM measurement prediction samples in a time window to be monitored.
38. The UE (22) of any one of Claims 24-37, wherein the performance monitoring configuration includes at least one threshold to determine a percentage of RRM measurements to be made in a period of time.
39. A network node (16) configured to communicate with a user equipment, UE (22), the network node (16) comprising processing circuitry configured to:send the UE (22) a performance monitoring configuration, the performance monitoring configuration configuring the UE (22) to perform radio resource management,RRM, measurement predictions for a first set of time occasions based on RRM measurements on a second set of time occasions; andreceive from the UE (22), RRM measurement predictions according to the performance monitoring configuration.
40. The network node (16) of Claim 39, wherein the processing circuitry is configured to determine performance information based at least in part on at least one of the received RRM measurement predictions and the RRM measurements.
41. The network node (16) of Claim 40, wherein the processing circuitry is configured to use the performance information to decide whether to use an RRM measurement prediction for a mobility decision.
42. The network node (16) of any one of Claims 39-41, wherein a central unit, CU, of the network node (16) is configured to request an assignment of measurement gaps from a distributed unit, DU, of the network node (16).
43. The network node (16) of Claim 42, wherein the CU is configured to inform the DU whether each requested measurement gap is to be used by the UE (22) to derive RRM measurement predictions.
44. The network node (16) of any one of Claims 42 and 43, wherein the DU is configured to prioritize measurement gap allocations.
45. The network node (16) of any one of Claims 42-44, wherein the DU is configured to indicate a timing for which measurement gaps are allocated.
46. The network node (16) of Claim 45, wherein the CU is configured to modify the performance monitoring configuration based at least in part on the indicated timing.
