UE-assisted performance monitoring for RRM measurement event prediction in ai mobility
The UE-assisted performance monitoring method addresses the inadequacy of existing metrics for RRM measurement event prediction by providing accurate performance metrics for AI mobility, enhancing handover decisions in wireless communication systems.
Patent Information
- Application Number
- PCT/SE2026/050328
- 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 in wireless communication are designed for AI-based beam management and AI-based channel state information prediction, but are unsuitable for RRM measurement event prediction in AI mobility, leading to inadequate performance metrics for mobility management.
A method for UE-assisted performance monitoring that involves predicting RRM measurement events, calculating performance metrics, and reporting these metrics to the network, using explicit or implicit indications of accuracy, confidence, and statistical information to support informed mobility decisions.
Enhances the accuracy of RRM measurement event prediction, enabling the network to make informed mobility decisions based on UE-reported performance metrics, thereby improving handover processes and reducing errors.
Smart Images

Figure SE2026050328_12112026_PF_FP_ABST
Abstract
Description
[0001] UE-ASSISTED PERFORMANCE MONITORING FOR RRM MEASUREMENT EVENT 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 (RRM) measurement event 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 3 GPP NR standardization work, a new release 19 study item (SI) on artificial intelligence (AI) / machine learning (ML) for the NR mobility started in 2024. This study item explored the benefits of augmenting the mobility with features enabling improved support of AI / ML-based algorithms for enhanced performance and / or reduced complexity / overhead in such use cases in mobility as radio resource management (RRM) measurement prediction, RRM measurement event prediction, and radio link failure (RLF) / handover failure (HOF) prediction.
[0007] An RRM measurement event may be one of the following events in terms of given RRM measurement quantity (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference and noise ratio (SINR)), where the RRM measurement quantity may be measured based on SSB or CSLRS:
[0008] • Event Al: Serving cell becomes better than absolute threshold (for a given time duration)
[0009] • Event A2: Serving cell becomes worse than absolute threshold (for a given time duration)
[0010] • Event A3 : A neighbour cell becomes amount of offset better than a special cell (e.g. a primary cell, a primary second cell) (for a given time duration)• Event A4: A neighbour cell becomes better than absolute threshold (for a given time duration)
[0011] • Event A5: A special cell (e.g., a primary cell, a primary second cell) becomes worse than absolute thresholdl and a neighbour cell or a secondary cell becomes better than another absolute threshold2 (for a given time duration)
[0012] • Event A6: A neighbour cell becomes amount of offset better than a secondary cell (for a given time duration)
[0013] • Event B 1 : Inter RAT neighbour becomes better than threshold
[0014] • Event B2: A primary cell becomes worse than thresholdl and an inter-RAT neighbour cell becomes better than threshold2, or a primary cell becomes worse than thresholdl and an inter-RAT neighbour cell becomes better than threshold2 for a given time duration
[0015] • condEvent A3: Conditional reconfiguration candidate cell becomes amount of offset better than a primary cell or a primary secondary cell (for a given time duration) • condEvent A4: Conditional reconfiguration candidate cell becomes better than absolute threshold where condEvent A4 can also be used for current primary secondary cell (i.e., in case it is configured as candidate primary secondary cell for CondEvent A4 evaluation) for conditional handover with candidate secondary cell group(s) case
[0016] • condEvent A5: A primary cell or a primary secondary cell becomes worse than absolute thresholdl and conditional reconfiguration candidate cell becomes better than another absolute threshold2 (for a given time duration)
[0017] In RRM measurement event prediction with UE-side model, one UE may indirectly predict an RRM measurement event based on RRM measurement results predicted by the UE and / or RRM measurement results measured by the UE, or the UE may directly predict an RRM measurement event based on RRM measurement results measured by the UE.
[0018] Performance monitoring
[0019] In UE-assisted performance monitoring for one inference configuration with UE-side model for Al use cases in wireless communication, according to the network configuration, one UE is configured to report the information of performance metric(s) of the inference configuration to the network, where the performance metric(s) is (are) derived by the UE via predicted measurement results and the corresponding ground truths for this inference configuration.SUMMARY
[0020] Existing solutions for UE-assisted performance monitoring with UE-side model in wireless communication are designed for Al-based beam management or Al-based channel state information (CSI) prediction, but not for RRM measurement event prediction in Al mobility. Due to different use cases, the performance metrics designed for Al-based beam management and Al-based CSI prediction are unsuitable for performance metrics in RRM measurement event prediction in Al mobility.
[0021] Some embodiments advantageously provide methods, systems, and apparatuses for UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0022] In some embodiments, one UE receives one configuration from the network, where this configuration indicates the UE to:
[0023] • predict one or more RRM measurement events based on one or more inference configurations;
[0024] • calculate the performance metric information of the RRM measurement event prediction based on one performance monitoring configuration; and / or
[0025] • report the performance metric information to the network, where the performance metric information may be reported with RRM measurement event prediction results to network via one message or more messages.
[0026] In some embodiments, the performance metric information may be one or more of following information:
[0027] • RRM measurement event prediction accuracy which may be one or more of the following information:
[0028] o explicit or implicit indication of whether one RRM measurement event prediction is accurate or not accurate, or whether one RRM measurement event prediction is missed. For example, if, within one confidence time window of the predicted RRM measurement event (or predicted RRM measurement event with the probability higher than one first threshold), there is corresponding real RRM measurement event, then this prediction is counted as one accurate RRM measurement event prediction, otherwise this prediction is counted as one non- accurate RRM measurement event prediction. In another example, if, within one confidence time window of one RRM measurement event which isconfigured for UE-side prediction, the UE does not predict this RRM measurement event (or the UE does not predict this RRM measurement event with the probability higher than one second threshold), then it is counted as missed RRM measurement event prediction;
[0029] o explicit or implicit indication of confidence information of one or more RRM measurement event predictions;
[0030] o statistical performance information of RRM measurement event prediction accuracy (e.g., Fl -score, precision, recall, percentage of accurate RRM measurement event prediction, percentage of missed RRM measurement event prediction);
[0031] o information of difference of the time to predict RRM measurement event within a confidence time window and the time of real RRM measurement event within the confidence time window, where the window may be one or more time instances; and
[0032] o associated RRM measurement prediction accuracy information for RRM measurement event prediction
[0033] • RRM measurement prediction accuracy information
[0034] In some embodiments, each of associated RRM measurement predication accuracy information for RRM measurement event prediction and RRM measurement prediction accuracy information may explicitly or implicitly include one or more following information:
[0035] • one or more RSRP (or RSRQ or SINR) differences within one monitoring window, where one RSRP (or RSRQ or SINR) difference is for one monitoring occasion;
[0036] • Mean square error of RSRP (or RSRQ or SINR) prediction within one monitoring window;
[0037] • mean of RSRP (or RSRQ or SINR) differences within one monitoring window;
[0038] • cumulative distribution function (CDF) information (e.g. 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within one monitoring window; • confidence information of RRM measurement (e.g. RSRP, RSRQ, SINR) prediction;
[0039] • accuracy for Top K strongest beam prediction (e.g., a number of correct prediction, percentage of correct prediction) within one monitoring window;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:
[0040] ■ condition: whether at least one of 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 for monitoring and may be 1 or 2. Monitoring beam set may be same as smaller than prediction beam set; and
[0041] • confidence information of Top K strongest beam prediction;
[0042] In some embodiments, mean square error of RSRP (or RSRQ or SINR) prediction within the monitoring occasions means mean value of the square of RSRP (or RSRQ or SINR) difference(s) of the monitoring occasion(s).
[0043] In some embodiments, one RSRP (or RSRQ or SINR) difference in one monitoring occasion is the difference of one measured RSRP (or RSRQ or SINR) in the monitoring occasion and one predicted RSRP (or RSRQ or SINR) in corresponding prediction occasion (e.g. RSRP (or RSRQ or SINR) difference = predicted RSRP (or RSRQ or SINR) - measured RSRP (or RSRQ or SINR)), where the corresponding prediction occasion means the prediction occasion which is same as monitoring occasion or roughly closed to the monitoring occasion or roughly same as the monitoring occasion.
[0044] In some embodiments, RSRP (or RSRQ or SINR) may be cell-level or may be beam -level.
[0045] In some embodiments, the performance monitoring configuration indicates the monitoring window and the performance metric information is derived by the UE via the prediction information and the real measurement (event) information in the monitoring window.
[0046] In some embodiments, the serving cell of the UE may send the handover request with the received performance metric information for RRM measurement event prediction to one target cell for mobility purpose. According to at least the handover request information and / or the performance metric information, the target cell makes the decision whether to accept this handover request. For example, if the performance metric is not good enough, e.g., it does not meet a desired / target criteria, then the target cell may reject the handover request; otherwise, the target cell may accept the handover request and sendback handover command information to the serving cell for the UE’s mobility from the serving cell to the target cell.
[0047] Advantages of embodiments described herein include support for UE-assisted performance monitoring for RRM measurement event prediction with UE-side model, and the network (e.g., network node, serving cell, target cell) is able to use the received performance metric information of RRM measurement event prediction for mobility decisions.
[0048] According to an aspect of the present disclosure, a method in a UE is provided. The method includes predicting at least one RRM measurement event based on one or more inference configurations. The method includes determining at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration. The method includes reporting the performance metric to the network node.
[0049] According to one or more embodiments of this aspect, the performance monitoring configuration includes an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0050] According to one or more embodiments of this aspect, the performance monitoring configuration includes RRM measurement prediction accuracy information.
[0051] According to one or more embodiments of this aspect, the performance monitoring configuration includes a periodicity for performance monitoring by the UE.
[0052] According to one or more embodiments of this aspect, the performance monitoring configuration includes one or more actions to be performed by the UE during performance monitoring.
[0053] According to one or more embodiments of this aspect, the performance monitoring configuration includes statistical performance information of RRM measurement event prediction accuracy.
[0054] According to one or more embodiments of this aspect, the performance monitoring configuration includes information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window including one or more time instances.According to one or more embodiments of this aspect, the performance monitoring configuration includes associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0055] According to one or more embodiments of this aspect, the performance metric includes accuracy information that includes one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference noise ratio (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF), of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0056] According to another aspect of the present disclosure, a method in a network node is provided. The method includes configuring the UE to predict at least one RRM measurement event based on one or more inference configurations and to determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration. The method includes receiving information associated with the determined performance metric.
[0057] According to one or more embodiments of this aspect, the performance monitoring configuration includes an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0058] According to one or more embodiments of this aspect, the performance monitoring configuration includes RRM measurement prediction accuracy information.
[0059] According to one or more embodiments of this aspect, the performance monitoring configuration includes a periodicity for performance monitoring by the UE.
[0060] According to one or more embodiments of this aspect, the performance monitoring configuration includes one or more actions to be performed by the UE during performance monitoring.
[0061] According to one or more embodiments of this aspect, the performance monitoring configuration includes statistical performance information of RRM measurement event prediction accuracy.
[0062] According to one or more embodiments of this aspect, the performance monitoring configuration includes information associated with difference of a time to predict theRRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window including one or more time instances.
[0063] According to one or more embodiments of this aspect, the performance monitoring configuration includes associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0064] According to one or more embodiments of this aspect, the performance metric includes accuracy information that includes one or more of a difference within a monitoring window with respect to one or more of reference signal received power (RSRP), reference signal received quality (RSRQ), and (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF) of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0065] According to another aspect of the present disclosure, a UE is provided. UE is configured to predict at least one RRM measurement event based on one or more inference configurations. UE is configured to determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration. UE is configured to report the performance metric to the network node.
[0066] According to one or more embodiments of this aspect, the performance monitoring configuration includes an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0067] According to one or more embodiments of this aspect, the performance monitoring configuration includes RRM measurement prediction accuracy information.
[0068] According to one or more embodiments of this aspect, the performance monitoring configuration includes a periodicity for performance monitoring by the UE.
[0069] According to one or more embodiments of this aspect, the performance monitoring configuration includes one or more actions to be performed by the UE during performance monitoring.
[0070] According to one or more embodiments of this aspect, the performance monitoring configuration includes statistical performance information of RRM measurement event prediction accuracy.According to one or more embodiments of this aspect, the performance monitoring configuration includes information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window including one or more time instances.
[0071] According to one or more embodiments of this aspect, the performance monitoring configuration includes associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0072] According to one or more embodiments of this aspect, the performance metric includes accuracy information that includes one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference noise ratio (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF), of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0073] According to another aspect of the present disclosure, a network node is provided. Network node is configured to configure the UE to predict at least one RRM measurement event based on one or more inference configurations and to determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration. Network node is configured to receive information associated with to the determined performance metric.
[0074] According to one or more embodiments of this aspect, the performance monitoring configuration includes an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0075] According to one or more embodiments of this aspect, the performance monitoring configuration includes RRM measurement prediction accuracy information.
[0076] According to one or more embodiments of this aspect, the performance monitoring configuration includes a periodicity for performance monitoring by the UE.
[0077] According to one or more embodiments of this aspect, the performance monitoring configuration includes one or more actions to be performed by the UE during performance monitoring.According to one or more embodiments of this aspect, the performance monitoring configuration includes statistical performance information of RRM measurement event prediction accuracy.
[0078] According to one or more embodiments of this aspect, the performance monitoring configuration includes information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window including one or more time instances.
[0079] According to one or more embodiments of this aspect, the performance monitoring configuration includes associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0080] According to one or more embodiments of this aspect, the performance metric includes accuracy information that includes one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power (RSRP), reference signal received quality (RSRQ), and (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF) of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0081] BRIEF DESCRIPTION OF THE DRAWINGS
[0082] 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:
[0083] FIG. l is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;
[0084] FIG. 2 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;
[0085] FIG. 3 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;FIG. 4 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;
[0086] FIG. 5 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;
[0087] FIG. 6 is a diagram of an example configuration according to some embodiments of the present disclosure;
[0088] FIG. 7 is a diagram of an example configuration according to some embodiments of the present disclosure; and
[0089] FIG. 8 is a diagram of an example configuration according to some embodiments of the present disclosure.
[0090] DETAILED DESCRIPTION
[0091] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to UE-assisted performance monitoring for RRM measurement event prediction in 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.
[0092] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0093] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may beaccomplished 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.
[0094] 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.
[0095] 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.
[0096] 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 core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.
[0097] 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 ofmachine 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.
[0098] 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).
[0099] 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.
[0100] 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.
[0101] 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.Some embodiments are directed to UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0102] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 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.
[0103] 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.
[0104] 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 differentnetwork 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.
[0105] A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to UE-assisted performance monitoring for RRM measurement event prediction in Al mobility. A user equipment 22 is configured to include a implementation unit 26 which is configured to perform one or more UE 22 functions described herein, including functions related to UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0106] 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. 2.
[0107] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.
[0108] 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).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.
[0109] 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 configuration unit 24 which is configured to perform one or more network node 16 functions described herein, including functions related to UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0110] The network node 16 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeB s. 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.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).
[0111] 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.
[0112] 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.
[0113] 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.
[0114] 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 anycombination 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.
[0115] 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).
[0116] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.
[0117] 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 implementation unit 26 which is configured to perform one or more UE 22functions described herein, including functions related to UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0118] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.
[0119] 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.
[0120] Although FIGS. 1 and 2 show various “units” such as configuration unit 24 and implementation 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.
[0121] FIG. 3 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 3 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. 3 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 62b and STA 62c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 1 and 2. In 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.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.
[0122] 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.
[0123] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 3 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.
[0124] FIG. 4 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. 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 is configured to configure the UE 22 to predict at least one radio resource management, RRM, measurement event based on at least one inference configuration and to determine at least one performance metric of the RRM measurement based on a performance monitoring configuration (Block SI 00). Network node 16 is configured to receive information associated with to the determined performance metric (Block SI 02).
[0125] In some embodiments, the performance information comprises one or more of: an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with theprediction of the RRM measurement event; statistical performance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0126] In some embodiments, the predicted RRM measurement event corresponds to one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0127] In some embodiments, the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0128] In some embodiments, the performance monitoring configuration comprises RRM measurement prediction accuracy information.
[0129] In some embodiments, the performance monitoring configuration comprises a periodicity for performance monitoring by the UE 22.
[0130] In some embodiments, the performance monitoring configuration comprises one or more actions to be performed by the UE 22 during performance monitoring.
[0131] In some embodiments, the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
[0132] In some embodiments, the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances.
[0133] In some embodiments, the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.In some embodiments, the performance metric comprises accuracy information that comprises one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power (RSRP), reference signal received quality (RSRQ), and (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF) of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0134] FIG. 5 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 implementation unit 26), processor 52, and / or radio interface 46. User equipment 22 is configured to predict at least one radio resource management, RRM, measurement event based on at least one inference configuration (Block SI 04). User equipment 22 is configured to determine at least one performance metric of the RRM measurement based on a performance monitoring configuration (Block SI 06). User equipment 22 is configured to report the performance metric to the network node (Block SI 08).
[0135] In some embodiments, the performance information comprises one or more of: an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with the prediction of the RRM measurement event; statistical performance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0136] In some embodiments, the predicted RRM measurement event corresponds to one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, andSINR differences within the monitoring window; cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0137] In some embodiments, the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
[0138] In some embodiments, the performance monitoring configuration comprises RRM measurement prediction accuracy information.
[0139] In some embodiments, the performance monitoring configuration comprises a periodicity for performance monitoring by the UE 22.
[0140] In some embodiments, the performance monitoring configuration comprises one or more actions to be performed by the UE 22 during performance monitoring.
[0141] In some embodiments, the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
[0142] In some embodiments, the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances.
[0143] In some embodiments, the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0144] In some embodiments, the performance metric comprises accuracy information that comprises one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference noise ratio (SINR); mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function (CDF), of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0145] 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 examplesof arrangements for UE-assisted performance monitoring for RRM measurement event prediction in Al mobility.
[0146] Indirect RRM measurement event prediction
[0147] In at least one embodiment, a UE 22 is configured by a network (e.g., using network node 16), via an inference configuration from the network to the UE 22, to predict RRM measurement and RRM measurement event. The UE 22 is further configured by the network, via a performance monitoring configuration, to monitor the performance of RRM measurement event prediction and calculate the performance metric of the performance and report the performance metric to the network. The inference configuration may explicitly or implicitly indicate one or more of the following information:
[0148] • RRM measurement event prediction is indirect (i.e., based on RRM measurement prediction);
[0149] o In at least one embodiment, this can implicitly derived if the report Config associated with the measurement object for which the reporting is requested by the network indicates that the UE 22 should use a temporal / spatial or frequency domain predictions instead of performing the measurements.
[0150] • predicted RRM measurement event type and parameters (e.g., offset, hysteresis, timerTotrigger, thresholdl, threshold2, a3-offset, a6-offset, al-Threshold, a2- Threshold, a5-Thresholdl, a5-Threshold2, a4-threshold, reportOnLeave, useAllowedCellList);
[0151] • observation and prediction pattern information (e.g., observation window, prediction window, prediction time occasion information, observation time occasion information, prediction occasion information, observation carrier frequency information, prediction carrier frequency information, observation set (e.g. Set B), prediction set (e.g. Set A), observation beam set, prediction beam set, beam-level or cell-level as inference input, beam -level or cell-level as inference output, L3-RRM as inference output or LI -RRM as inference output, confidence window), where this information may be for both RRM measurement event prediction and RRM measurement prediction, or may be for RRM measurement event prediction and RRM measurement prediction separately, and / or may be for RRM measurement event separately; and
[0152] • other information for RRM measurement prediction and RRM measurement event prediction.
[0153] The performance monitoring configuration may explicitly or implicitly indicate one or more following information:• performance metric information, for example:
[0154] o RRM measurement event prediction accuracy
[0155] ■ Fl -score, precision, recall;
[0156] ■ Information of difference of the time to predict RRM measurement event within a confidence window and the time of real RRM measurement event within the confidence window, where the window may be one or more time instances; and
[0157] ■ associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0158] • RRM measurement prediction accuracy information. The performance monitoring configuration may explicitly configure which event prediction accuracy quantity should be used for the performance monitoring purpose. In at least one embodiment, the configuration configures the UE 22 to use the RSRP difference as performance monitoring quantity and / or the time difference between the prediction predicted event (evaluated fully or partially based on the prediction) and the actual event (evaluated based on the pure measurements) occurrence time.
[0159] • The performance monitoring configuration may also include the periodicity of performance monitoring check by the UE 22. For example, the network may configure for which prediction samples the performance monitoring is needed. In some embodiments, the network (e.g., via network node 16) configures a ratio of the performance monitoring versus the total number of predictions performed by the UE 22. For example, the network may configure X% performance monitoring of the prediction instance meaning that the UE 22 checks the performance of the event only for X% of the prediction samples.
[0160] • The performance monitoring configuration may also include the UE 22 actions upon performing performance monitoring. In some embodiments, the network (e.g., via network node 16) configures the UE 22 to include the performance monitoring information (the value of the performance monitoring metrics), or the network may request the UE 22 to send only the performance monitoring metrics instead of the measurements and predictions of the triggered cells. In some embodiments, the network may configure the UE 22 not to send the measurement report to the network if the performance monitoring shows bad performance, e.g., the value of performance monitoring metric is above / below a configured or predefined (e.g., based on specific performance requirements) threshold.Each of associated RRM measurement prediction accuracy information for RRM measurement event prediction and RRM measurement prediction accuracy information may explicitly or implicitly include one or more of:
[0161] • one or more RSRP (or RSRQ or SINR) differences within one monitoring window, where one RSRP (or RSRQ or SINR) difference for one monitoring occasion;
[0162] • mean square error of RSRP (or RSRQ or SINR) prediction within one monitoring window;
[0163] • mean of RSRP (or RSRQ or SINR) differences within one monitoring window;
[0164] • CDF information (e.g. 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within one monitoring window;
[0165] • accuracy for Top K strongest beam prediction (e.g. number of correct prediction, percentage of correct prediction) within one monitoring window;
[0166] 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
[0167] ■ Condition: whether at least one of 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 for monitoring and may be 1 or 2. Monitoring beam set may be same as smaller than prediction beam set; and
[0168] • time difference between predicted event and the actual event (ground truth)
[0169] The UE 22 reports the requested performance metrics information to the network (e.g., via network node 16), and the network uses the performance metric information to decide whether deactivate inference configuration and performance monitoring configuration for RRM measurement event prediction and / or RRM measurement prediction, and / or whether handover the UE 22 to other cells for mobility purposes. The serving cell of the UE 22 may send the handover request with the received performance metric information for RRM measurement event prediction to the target cell. According to at least handover request information and / or the performance metric information, the target cell decides whether to accept this handover request. For example, if the performance metric is not good enough, e.g., does not meet desired / target criteria, then the target cell may reject the handover request. Otherwise, the target cell may accept thehandover request and send back handover command information to the serving cell for the UE’s 22 mobility from the serving cell to the target cell.
[0170] Direct RRM measurement event prediction
[0171] In at least one embodiment, a UE 22 is configured by a network (e.g., via network node 16), via an inference configuration from the network to the UE 22, to predict RRM measurement event, and is further configured by the network, via a performance monitoring configuration, to monitor the performance of RRM measurement event prediction and calculate the performance metric of the performance and report the performance metric to the network. The inference configuration may explicitly or implicitly indicate one or more following information:
[0172] • RRM measurement event prediction is direct;
[0173] • predicted RRM measurement event type and parameters (e.g. offset, hysteresis, timerTotrigger, thresholdl, threshold2, a3-offset, a6-offset, al-Threshold, a2- Threshold, a5-Thresholdl, a5-Threshold2, a4-threshold, reportOnLeave, useAllowedCellList);
[0174] • observation and prediction pattern information (e.g., observation window, prediction window, prediction time occasion information, observation time occasion information, prediction occasion information, observation carrier frequency information, prediction carrier frequency information, observation set (e.g. Set B), prediction set (e.g. Set A), observation beam set, prediction beam set, beam-level or cell-level as inference input, beam -level or cell-level as inference output, L3-RRM as inference output or LI -RRM as inference output, confidence window); and
[0175] • other information for RRM measurement event prediction
[0176] The performance monitoring configuration may explicitly or implicitly indicate one or more following information:
[0177] • performance metric information, for example:
[0178] o RRM measurement event prediction accuracy
[0179] ■ Fl -score, precision, recall;
[0180] ■ information of difference of the time to predict RRM measurement event within a confidence window and the time of real RRM measurement event within the confidence window, where the window may be one or more time instances; and
[0181] ■ associated RRM measurement prediction accuracy information for RRM measurement event prediction.• The performance monitoring configuration may explicitly configure which event prediction accuracy quantity should be used for the performance monitoring purpose. In at least one embodiment, the configuration configures the UE 22 to use the RSRP difference as performance monitoring quantity and / or the time difference between the prediction predicted event (evaluated fully or partially based on the prediction) and the actual event (evaluated based on the pure measurements) occurrence time.
[0182] • The performance monitoring configuration may also include the periodicity of performance monitoring check by the UE 22. For example, the network (e.g., via network node 16) may configure for which prediction samples the performance monitoring is needed. In some embodiments, the network (e.g., via network node 16) configures a ratio of the performance monitoring versus the total number of predictions performed by the UE 11. For example, the network may configure X% performance monitoring of the prediction instance, meaning that the UE 22 may check the performance of the event only for an X percent of the prediction samples.
[0183] • The performance monitoring configuration may also include the UE 22 actions upon performing performance monitoring. In some embodiments, the network (e.g., via network node 16) configures the UE 22 to include the performance monitoring information (the value of the performance monitoring metrics), or the network may request the UE 22 to send only the performance monitoring metrics instead of the measurements and predictions of the triggered cells. In some embodiments, the network (e.g., via network node 16) may configure the UE 22 not to send the measurement report to the network if the performance monitoring shows bad performance, e.g., the value of performance monitoring metric is above / below a configured or predefined (e.g., based on specific performance requirements) threshold.
[0184] The RRM measurement prediction accuracy information may explicitly or implicitly include:
[0185] • one or more RSRP (or RSRQ or SINR) differences within one monitoring window, where one RSRP (or RSRQ or SINR) difference for one monitoring occasion;
[0186] • mean square error of RSRP (or RSRQ or SINR) prediction within one monitoring window;
[0187] • mean of RSRP (or RSRQ or SINR) differences within one monitoring window• CDF information (e.g. 90% CDF, 85% CDF, 80% CDF, etc.) of RSRP (or RSRQ or SINR) difference within one monitoring window; and
[0188] • accuracy for Top K strongest beam prediction (e.g., number of correct prediction, percentage of correct prediction) within one monitoring window.
[0189] 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.
[0190] ■ Condition: whether at least one of 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 for monitoring and may be 1 or 2. Monitoring beam set may be same as smaller than prediction beam set.
[0191] The UE 22 reports the requested performance metrics information to the network (e.g., via network node 16), and the network uses the performance metric information to decide whether deactivate inference configuration and performance monitoring configuration for RRM measurement event prediction and / or RRM measurement prediction, and whether to handover the UE 22 to other cells for mobility purposes. The serving cell of the UE 22 may send the handover request with the received performance metric information for RRM measurement event prediction to the target cell. Based on at least handover request information and / or the performance metric information, the target cell decides whether to accept this handover request. For example, if the performance metric is not good enough, e.g., does not meet one or more target / desired criteria, then the target cell may reject the handover request; otherwise, the target cell may accept the handover request and send back handover command information to the serving cell for the UE’s 22 mobility from the serving cell to the target cell.
[0192] Association between Inference Configuration and Performance Monitoring configuration
[0193] In some embodiments, the UE 22 receives (e.g., via network node 16) 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 points 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.
[0194] The measObjectld points 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 parameter about radio resources to be predicted.
[0195] The measld identifies the inference configuration.
[0196] In at least one embodiment, in addition to the inference configuration, the UE 22 (e.g., via network node 16) 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 one or more of
[0197] • 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) metrics; and
[0198] • A measObjectld pointing to a measurement object indicating what is to be measured and / or inferred to calculate a PM metric according to what is requested to be reported (in reporting configuration).
[0199] 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.
[0200] 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.
[0201] In some embodiments, the structure of 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).
[0202] Alternatively, even if the same report type is used, the parameters may be quite different, e.g., one may have longer periodicity than the other and / or may have a larger time to trigger. In addition, the performance monitoring configuration includes 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.• In some embodiments option, 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 in its configuration an additional measld associated to an inference configuration.
[0203] An example measurement configuration is shown in FIG. 6. In at least one embodiment, when the UE 22 is triggered to transmit a report including inference(s) according to the inference configuration, the UE 22 includes the measld identifying the inference configuration (e.g., measld=x in the example of FIG. 6). When the UE 22 is triggered (e.g., via network node 16) to transmit a report including the PM metric(s) according to the PM configuration, the UE 22 includes the measld identifying the PM configuration (e.g., measld=y in FIG. 6).
[0204] In at least one embodiment, in addition to the inference configuration, the UE 22 (e.g., via network node 16) 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 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.
[0205] • 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).
[0206] 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.
[0207] o For example, in the case of frequency-domain prediction, the measurement object identifier may point to a measurement object that includes the frequency to be predicted, also indicated in the inference configuration, but it may also include the frequency to be measured.
[0208] 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). Alternatively, 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 performancemonitoring configuration is associated to the inference configuration by the fact that both occupy the same position in a respective list. For example:
[0209] List of inference configurations
[0210] • MeasIdToAddMod, measld=x
[0211] • MeasIdToAddMod, measld=y
[0212] • MeasIdToAddMod, measld=z
[0213] List of PM configurations
[0214] • MeasIdToAddMod, measld=a
[0215] • MeasIdToAddMod, measld=b
[0216] • MeasIdToAddMod, measld=c
[0217] The inference configuration with measld=x is associated with the PM configuration in measld=a (because they are both in the first position in their respective lists). The inference configuration with measld=y is associated with the PM configuration in measld=b (because they are both in the first position in their respective lists). The inference configuration with measld=z is associated with the PM configuration in measld=c (because they are both in the first position in their respective lists).
[0218] In some embodiments, considering 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 configuration shown in FIG. 7). When the UE 22 is triggered to transmit a report including the PM metric(s) according to the PM configuration, the UE 22 includes the measld identifying the PM configuration (e.g. measld=y in the example in FIG. 7).
[0219] In an example embodiment, 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) may 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 may also allow the reporting configuration for PM to be 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.
[0220] In at least one embodiment, considering that a single measld is 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 includes the measld identifying the inference configuration (e.g. measld=x in the example above). And when the UE is triggered to transmit a report including the PM metric(s) according to the PM configuration, the UE includes the same measld, also identifying the PM configuration (e.g. measld=x in the example above). Since they are the same, in one option the UE includes an indication to distinguish between the quantities being reported, and / or the UE simply include different quantities depending on the report which is being triggered.
[0221] In at least one embodiment, 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 frequency (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, i.e., indicating one or more frequencies to be measured, such as MeasObjectldSetB. Then, the received PM configuration associated to the inference configuration, in a different MeasIdToAddMod instance, includes the measld measld pointing to the inference configuration, and in both instances the same measObjectld pointing to set A is included, as shown in the example configuration depicted in FIG. 8.
[0222] In at least one embodiment, 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 frequency (e.g. indicated to the UE 22 via one or more measurement object ID(s) for frequencies to be predicted, such as MeasObjectldSetA. Then, in the PM configuration, in a different MeasIdToAddMod instance, only a measld may be included pointing to the same measurement object that needs to be predicted.
[0223] Example Embodiments:
[0224] Example Al . A method implemented in a UE 22 that is configured to communicate with a network node 16, the method comprising: predicting at least one radio resource management, RRM, measurement event based on an inference configuration; determining at least one performance metric of the RRM measurementbased on a performance monitoring configuration; and reporting the performance metric to the network node 16.
[0225] Example A2. The method of Example Al, wherein the performance information comprises one or more of an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with the prediction of the RRM measurement event; statistical performance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0226] Example A3. The method of Example Al, wherein the predicted RRM measurement event corresponds to one or more of a difference within a monitoring window with respect to one or more of reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0227] Example Bl. A UE 22 configured to communicate with a network node 16, the UE 22 configured to, and / or comprising a radio interface and / or processing circuitry configured to: predict at least one radio resource management, RRM, measurement event based on an inference configuration; determine at least one performance metric of the RRM measurement based on a performance monitoring configuration; and report the performance metric to the network node 16.
[0228] Example B2. The UE 22 of Example Bl, wherein the performance information comprises one or more of an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with the prediction of the RRM measurement event; statisticalperformance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0229] Example B3. The UE 22 of Example B 1 , wherein the predicted RRM measurement event corresponds to one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window
[0230] Example Cl . A method implemented in a network node 16 that is configured to communicate with a user equipment 22, the method comprising: configuring the UE to predict at least one radio resource management, RRM, measurement event based on an inference configuration and to determine at least one performance metric of the RRM measurement based on a performance monitoring configuration; and receiving information associated with to the determined performance metric.
[0231] Example C2. The method of Example Cl, wherein the performance information comprises one or more of: an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with the prediction of the RRM measurement event; statistical performance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.Example C3. The method of Example Cl, wherein the predicted RRM measurement event corresponds to one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window; cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0232] Example DI . A network node 16 configured to communicate with a UE 22, the network node 16 configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: configure the UE to predict at least one radio resource management, RRM, measurement event based on an inference configuration and to determine at least one performance metric of the RRM measurement based on a performance monitoring configuration; and receive information associated with to the determined performance metric.
[0233] Example D2. The network node of Example DI, wherein the performance information comprises one or more of: an explicit or implicit indication of accuracy of the prediction of the RRM measurement event; an explicit or implicit indication of whether the predicted RRM measurement event is missed; an explicit or implicit indication of confidence information associated with the prediction of the RRM measurement event; statistical performance information of RRM measurement event prediction accuracy; information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances; and associated RRM measurement prediction accuracy information for RRM measurement event prediction.
[0234] Example D3. The network node 16 of Example DI, wherein the predicted RRM measurement event corresponds to one or more of: a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR; mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR; mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window;cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window; confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
[0235] 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.
[0236] 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.
[0237] 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.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.
[0238] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
[0239] 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).
[0240] 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.
[0241] Abbreviations that may be used in the preceding description include:Abbreviation Explanation
[0242] Al Artificial Intelligence
[0243] ARFCN Absolute Radio-Frequency Channel Number ARQ Automatic Repeat Request
[0244] BM Beam Management
[0245] CE Control Element
[0246] CSI-RS Channel State Information reference signal CU Control Unit
[0247] CU-CP Central Unit Control Plane
[0248] CU-UP Central Unit User Plane
[0249] DCAF Data Collection Application Function DCI Downlink Control Information
[0250] DRX Discontinuous reception
[0251] DU Distributed Unit
[0252] HARQ Hybrid ARQ
[0253] HOF Handover Failure
[0254] IE Information Element
[0255] L2 Layer-2
[0256] MAC Medium Access Control
[0257] MDT Minimization Drive Test
[0258] MIMO Multiple Input Multiple Output
[0259] ML Machine Learning
[0260] MNO Mobility Network Operator
[0261] NW Network
[0262] NWDAF Network Data Analytics Function
[0263] 0AM Operation Administration and Maintenance OTT Over-the-Top
[0264] PBCH Physical Broadcast Channel
[0265] PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PLMN Public Land Mobile network
[0266] RAN Radio Access Network
[0267] RAN Radio Access Network
[0268] RLE Radio Link FailureRLF Radio Link Failure
[0269] RLM Radio Link Monitoring
[0270] RRC Radio Resource Control
[0271] RRM Radio Resource Management
[0272] RSRP Reference signal received power
[0273] RSRQ Reference signal received quality
[0274] RS SI Received Signal Strength Indicator
[0275] SINR Signal to Interference and noise Ratio
[0276] SSB Synchronization Signal block
[0277] SSB Synchronization Signal Block
[0278] UCI Uplink Control Information
[0279] UE User equipment
[0280] 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 implemented in a user equipment, UE, (22) configured to communicate with a network node (16), the method comprising:predicting (SI 04) at least one radio resource management, RRM, measurement event based on one or more inference configurations;determining (SI 06) at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration; andreporting (S108) the performance metric to the network node (16).
2. The method of Claim 1, wherein the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
3. The method of any of Claims 1-2, wherein the performance monitoring configuration comprises RRM measurement prediction accuracy information.
4. The method of any of Claims 1-3, wherein the performance monitoring configuration comprises a periodicity for performance monitoring by the UE (22).
5. The method of any of Claims 1-4, wherein the performance monitoring configuration comprises one or more actions to be performed by the UE (22) during performance monitoring.
6. The method of any of Claims 1-5, wherein the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
7. The method of any of Claims 1-6, wherein the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances.
8. The method of any of Claims 1-7, wherein the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.
9. The method of any of Claims 1-8, wherein the performance metric comprises accuracy information that comprises one or more of:a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR;mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR;mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window;cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window;confidence information of RRM measurement prediction; andaccuracy for top K number of strongest beam predictions within the monitoring window.
10. A method implemented in a network node (16) configured to communicate with a user equipment (22), the method comprising:configuring (SI 00) the UE (22) to predict at least one radio resource management, RRM, measurement event based on one or more inference configurations and to determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration; andreceiving (SI 02) information associated with to the determined performance metric.
11. The method of Claim 10, wherein the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
12. The method of any of Claims 10-11, wherein the performance monitoring configuration comprises RRM measurement prediction accuracy information.
13. The method of any of Claims 10-12, wherein the performance monitoring configuration comprises a periodicity for performance monitoring by the UE (22).
14. The method of any of Claims 10-13, wherein the performance monitoring configuration comprises one or more actions to be performed by the UE (22) during performance monitoring.
15. The method of any of Claims 10-14, wherein the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
16. The method of any of Claims 10-15, wherein the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances.
17. The method of any of Claims 10-16, wherein the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.
18. The method of any of Claims 10-17, wherein the performance metric comprises accuracy information that comprises one or more of:a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR;mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR;mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window;cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window;confidence information of RRM measurement prediction; and accuracy for top K number of strongest beam predictions within the monitoring window.
19. A user equipment, UE, (22) in communication with a network node (16), the UE (22) comprising processing circuitry (50) configured to:predict at least one radio resource management, RRM, measurement event based on one or more inference configurations;determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration; andreport the performance metric to the network node (16).
20. The UE (22) of Claim 19, wherein the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
21. The UE (22) of any of Claims 19-20, wherein the performance monitoring configuration comprises RRM measurement prediction accuracy information.
22. The UE (22) of any of Claims 19-21, wherein the performance monitoring configuration comprises a periodicity for performance monitoring by the UE (22).
23. The UE (22) of any of Claims 19-22, wherein the performance monitoring configuration comprises one or more actions to be performed by the UE (22) during performance monitoring.
24. The UE (22) of any of Claims 19-23, wherein the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
25. The UE (22) of any of Claims 19-24, wherein the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRMmeasurement event within the confidence time window, the time window comprising one or more time instances.
26. The UE (22) of any of Claims 19-25, wherein the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.
27. The UE (22) of any of Claims 19-26, wherein the performance metric comprises accuracy information that comprises one or more ofa difference within a monitoring window with respect to one or more of reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR;mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR;mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window;cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window;confidence information of RRM measurement prediction; andaccuracy for top K number of strongest beam predictions within the monitoring window.
28. A network node (16) in communication with a user equipment (22), the network node (16) comprising processing circuitry (36) configured to:configure the UE (22) to predict at least one radio resource management, RRM, measurement event based on one or more inference configurations and to determine at least one performance metric of the predicted RRM measurement event based on a performance monitoring configuration; andreceive information associated with to the determined performance metric.
29. The network node (16) of Claim 28, wherein the performance monitoring configuration comprises an explicit or implicit indication of accuracy of the prediction of the RRM measurement event.
30. The network node (16) of any of Claims 28-29, wherein the performance monitoring configuration comprises RRM measurement prediction accuracy information.
31. The network node (16) of any of Claims 28-30, wherein the performance monitoring configuration comprises a periodicity for performance monitoring by the UE (22).
32. The network node (16) of any of Claims 28-31, wherein the performance monitoring configuration comprises one or more actions to be performed by the UE (22) during performance monitoring.
33. The network node (16) of any of Claims 28-32, wherein the performance monitoring configuration comprises statistical performance information of RRM measurement event prediction accuracy.
34. The network node (16) of any of Claims 28-33, wherein the performance monitoring configuration comprises information associated with difference of a time to predict the RRM measurement event within a confidence time window and a time of a real RRM measurement event within the confidence time window, the time window comprising one or more time instances.
35. The network node (16) of any of Claims 28-34, wherein the performance monitoring configuration comprises associated RRM measurement prediction accuracy information for RRM measurement event prediction.
36. The network node (16) of any of Claims 28-35, wherein the performance metric comprises accuracy information that comprises one or more of:a difference within a monitoring window with respect to one or more of: reference signal received power, RSRP, reference signal received quality, RSRQ, and signal-to-interference noise ratio, SINR;mean square error within the monitoring window of one or more of RSRP, RSRQ, and SINR;mean of one or more of RSRP, RSRQ, and SINR differences within the monitoring window;cumulative distribution function, CDF, of one or more of RSRP, RSRQ, and SINR difference within the monitoring window;confidence information of RRM measurement prediction; andaccuracy for top K number of strongest beam predictions within the monitoring window.
