Event-based performance monitoring and report

The UE-based performance monitoring framework addresses the challenges of static reporting in 5G mobility management by enabling context-aware, on-demand reporting with reduced overhead and enhanced diagnostic insights, ensuring compatibility and resilience in AI/ML model management.

WO2026235588A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2026/050280
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-27
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Current 5G mobility management systems face challenges in maintaining high reliability and service continuity, particularly at cell-edge or cell-hole scenarios, due to static reporting intervals that lack contextual adaptability, leading to delayed or inaccurate performance insights, and there is a need for improved event and time-driven performance monitoring and reporting frameworks.

Method used

A UE-based performance monitoring framework is introduced, where the User Equipment (UE) monitors AI/ML inference results in real-time and sends performance monitoring reports only when specific temporal or statistical criteria are met, using enhanced MeasConfig and ReportConfigNR structures, reducing unnecessary signaling overhead and providing detailed diagnostic insights.

Benefits of technology

This solution enables on-demand, context-aware reporting, reduces unnecessary signaling, and provides fine-grained diagnostic insights while ensuring compatibility with existing network stacks, supporting AI/ML model lifecycle management and enhancing resilience and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2026050280_12112026_PF_FP_ABST
    Figure SE2026050280_12112026_PF_FP_ABST
Patent Text Reader

Abstract

In an embodiment, a method performed by a User Equipment (UE) is provided for performing event and / or time-driven performance monitoring. The method can include receiving, from a network node, a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration. The method can also include monitoring a performance of the inference configuration while performing predictions. The method can also include sending, to the network node, a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.
Need to check novelty before this filing date? Find Prior Art

Description

EVENT-BASED PERFORMANCE MONITORING AND REPORT RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 802,023, filed May 8, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to methods and device and network nodes for performing event and / or time driven performance monitoring and reporting in a wireless communications system.BACKGROUNDAl for Mobility

[0003] The Artificial Intelligence / Machine Learning (AI / ML) for Physical Layer (PHY) work in Rel-18 has been limited to lower layer features, such as Beam Management, which is sometimes referred as intra-cell mobility. Other features, such as Layer 3 (L3) handovers, Radio Resource Control (RRC) measurements configuration and reporting of predictions have not been part of the Rel-18.

[0004] Hence, a Rel-19 Study Item to study the usage of Al / ML for L3 Mobility and / or Radio Resource Management (RRM) measurements is considered. The objective of the study item Technical Report (TR) 38.843 v.18.0.0 includes:• Study and evaluate potential benefits and gains of AI / ML aided mobility for network triggered L3-based handover, considering the following aspects:o AI / ML based RRM measurement and event prediction Cell-level measurement prediction including intra and inter-frequency (User Equipment (UE) sided and network (NW) sided model).• Inter-cell Beam-level measurement prediction for L3 Mobility (UE sided and NW sided model).o Handover (HO) failure Radio Link Failure (RLF) prediction (UE sided model). o Measurement events prediction (UE sided model).• Study the need / benefits of any other UE assistance information for the network sidemodel.• The evaluation of the AI / ML aided mobility benefits should consider HO performance Key Performance Indicators (KPIs) and complexity tradeoffs .Performance Monitoring

[0005] For performance monitoring of one AI / ML functionality (or model), if the AI / ML functionality (or model) is at the UE side, the UE can monitor the performance of the functionality (or the model) via comparing the output of this functionality (or this model) and the ground truth based on specific performance metric(s), or the UE can send the calculated performance metric(s) to the network or send both output and ground truth to the network for network-side performance calculation for the purpose of performance monitoring at the network side, according to network. However, if the Al functionality (or model) is at the network side, then the network can monitor the performance by itself via comparing the output of this functionality (or this model) and ground truth based on specific performance metric(s) and thus the performance monitoring is transparent to the UE.

[0006] The performance metric for performance monitoring purpose may be inference accuracy including metrics related to intermediate KPIs, and / or system performance including metrics related to system performance KPIs. Other monitoring solutions include monitoring based on data distribution such as input-based (e.g. Monitoring the validity of the AI / ML input, e.g., out-of-distribution detection, drift detection of input data, or Signal to Noise Ratio (SNR), delay spread, etc) and output-based (e.g. drift detection of output data) and monitoring based on applicable condition.

[0007] In the use case of Al-based Channel State Information (CSI) compression, the performance metrics may be intermediate KPIs (e.g. Squared Generalized Cosine Similarity (SGCS)), eventual KPIs (e.g. throughput, hypothetical Block Error Rate (BLER), BLER, NACK / ACK), legacy CSI based monitoring (i.e. schemes using additional legacy CSI reporting), other monitoring solutions (e.g. input or output data based monitoring such as data drift between training dataset and observed dataset and out-of-distribution detection).

[0008] In the use case of Al-based CSI prediction, the UE may calculate the performance metrics and then report the performance metrics to the network for network-side performance monitoring or the UE may report predicted CSI and / or the corresponding ground-truth to the network for network-side performance metric calculation and network-side performance monitoring. The performance metric may be intermediate KPI (e.g. Normalized Mean Square Error (NMSE) or SGCS).

[0009] In the use case of Al-based beam management, the performance metrics may be beam prediction accuracy related KPIs (e.g. Top-K / 1 beam predication accuracy), and / or link quality related KPIs (e.g. throughput, Layer 1 (LI) Reference Signal Received Power (RSRP), LI Signal to Interference plus Noise Ratio (SINR), hypothetical BLER), and / or performance metric based on input / output data distribution of AI / ML, and / or LI -RSRP difference evaluated by comparing measured RSRP and predicted RSRP.SUMMARY

[0010] In an embodiment, a method is performed by a User Equipment (UE) for performing event and / or time-driven performance monitoring, the method includes receiving , from a network node, a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration, monitoring a performance of the inference configuration while performing predictions; and sending, to the network node, a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0011] In an embodiment, the event-based performance monitoring configuration is received in an RRCReconfiguration message.

[0012] In an embodiment, the UE, for every inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

[0013] In an embodiment, the UE, at a predefined number of occurrences of an inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

[0014] In an embodiment, the predefined number is configured by the network node.

[0015] In an embodiment, inference occasions for performance monitoring are the inference occasions in inference configuration but within the monitoring occasions window in the performance monitoring configuration.

[0016] In an embodiment, a condition of the one or more conditions is an event.

[0017] In an embodiment, Performance Monitoring Events (PME) that trigger performance monitoring are related to Performance Monitoring Report Events (PMRE) that trigger a performance monitoring report.

[0018] In an embodiment, one or more of the following are true: PME are the same as PMRE, PME are a subset of PMRE, or PMRE are a subset of PME.

[0019] In an embodiment, PMREs are evaluated every triggered PME or PMREs are evaluated every xth triggered PME.

[0020] In an embodiment, PME conditions are applied directly on inference or predicted Reference Signal Received Power, RSRP, samples, and PMRE conditions are applied on an outcome of PME.

[0021] In an embodiment, fulfillment of an event triggers periodical reporting to the network node.

[0022] In an embodiment, the performance monitoring report is configured to be sent periodically.

[0023] In an embodiment, the performance monitoring report is configured to be sent every T time period, or Y% of the performance monitoring occasions.

[0024] In an embodiment, performance monitoring is configured to be conducted periodically.

[0025] In an embodiment, the performance monitoring is configured to be conducted every T time period or Z% of inference occasions.

[0026] In an embodiment, non-fulfillment of an event for performing monitoring of predictions, triggers sending the performance monitoring report to the network node.

[0027] In an embodiment, the receiving the performance monitoring configuration comprises receiving rules for monitoring inference performance, wherein the rules comprise one or more of thresholds, time to trigger, window lengths, IDs of applicable triggers, and prediction setup references.

[0028] In an embodiment, the event-based performance monitoring report comprises events comprising one or more of the following conditions prediction statistic trigger; temporal trigger; handover proximity; prediction drift; and observation window.

[0029] In an embodiment, for each inference occasion or group of N inference occasions, the UE checks a prediction against an actual measurement.

[0030] In an embodiment, once one or more event-based performance monitoring report triggers are satisfied, the UE generates the performance monitoring report and an inference configuration identity.

[0031] In an embodiment, once one or more event-based performance monitoring report triggers are satisfied the UE sends, to the network node, the performance monitoring report and an inference configuration identity.

[0032] In an embodiment, the method further includes aligning inference values and ground truth values in time given variable delays filter or normalize a comparison to allow valid performance scoring.

[0033] In an embodiment, the method further includes after a performance monitoring report is sent, waiting for a timer before reevaluating or reporting again.

[0034] In an embodiment, sending the performance monitoring report comprises sending a version identification of an Artificial Intelligence / Machine Learning (AI / ML) model associated with the performance monitoring report.

[0035] In an embodiment, the UE follows a configured fallback mechanism if inference or prediction fails and the UE does not evaluation model performance monitoring.

[0036] In an embodiment, in response to sending the performance monitoring report to the network node, wait for at least one of a feedback signal, inference configuration update, performance monitoring configuration update or functionality deactivation.

[0037] In an embodiment, a UE is provided for performing event and / or time-driven performance monitoring and can be configured to perform any of the embodiments described above.

[0038] In an embodiment, a method performed by a network node is provided for configuring event and / or time-driven performance monitoring for receiving security information. The method includes providing to a UE a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration and receiving a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0039] In an embodiment, the performance monitoring configuration is included in an RRCReconfiguration message.

[0040] In an embodiment, the performance monitoring report includes one or more of the following an event trigger identifier, a prediction error metric; a timestamp; a confidence statistic; inference failure cause; and information about affected cells or beams.

[0041] In an embodiment, in response to receiving the performance monitoring report, the method further includes sending a reconfiguration message to update performance monitoring report triggers, update the performance monitoring configuration, update the inference configuration, or deactivate functionality.

[0042] In an embodiment, a network node is provided for configuring event and / or time-driven performance monitoring for receiving security information. The network node is configured to perform any of the embodiments above.BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0044] Figure 1 shows an exemplary message sequence chart of a method for performing event and / or time driven performance monitoring in accordance with some embodiments of the present disclosure.

[0045] Figure 2 shows an example of a communication system in accordance with some embodiments of the present disclosure.

[0046] Figure 3 is another example of a communication system according to some embodiments of the present disclosure.

[0047] Figure 4 shows a wireless device, which may be configured to operate in the communication system of Figure 2 or in the communication system of Figure 3.

[0048] Figure 5 shows a network node in accordance with some embodiments of the present disclosure.

[0049] Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0050] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0051] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0052] There currently exist certain challenge(s). In current Fifth Generation (5G) mobility management, particularly at cell-edge or cell-hole scenarios, it is crucial for the network to maintain high reliability and service continuity. If relying on static reporting intervals, which lack contextual adaptability and may result in delayed or inaccurate performance insight. In this context, the following challenges remain:• Timely evaluation of prediction model performance;• Triggering reports only when a certain condition is satisfied, e.g., performance deteriorates;• Reducing overhead while increasing insight precision; and• Ensuring compatibility with multiple performance monitoring options (e.g. UE-assisted performance monitoring, network-side performance monitoring, UE-side performance monitoring).

[0053] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The proposed solution introduces an Event and time driven Performance Monitoring and Reporting framework integrated into the User Equipment (UE) via enhancements to the existing MeasConfig, ReportConfigNR, structure defined in Third Generation Partnership Program (3GPP) Technical Specification (TS) 38.331 vl 8.5.1 “NR; Radio Resource Control (RRC); Protocol Specification” 2025-03-21. The gNB configures the UE with a set of inference evaluation criteria, such as temporal or sample % criteria, prediction error, confidence degradation, drift, or inference gaps, through a new CondTriggerConfig-rXX structure. The User Equipment (UE) monitors its Artificial Intelligence / Machine Learning (AI / ML) inference results in real-time and, upon satisfying any configured temporal, statistical criteria or trigger conditions, generates and transmits a performance monitoring Measurement Report containing relevant inference metrics, failure causes, and performance degradation indicators. This method ensures on-demand, context-aware reporting while reducing unnecessary signaling overhead.

[0054] The disclosure introduces a transformative architecture where the UE is capable of locally monitoring, evaluating, and validating its own inference performance — based on AI / ML models used for predictive tasks (i.e., Radio Resource Management (RRM) prediction for mobility). The evaluation is both periodical (time-driven) and condition-driven: the UE triggers performance monitoring and sends reports when 1) a certain temporal criterion is met (e.g., x% of inference or monitoring occasion occurs, or every x second, then UE reports the monitored performance) 2) specific degradation or anomaly conditions are met. These include statisticalprediction errors, confidence drops, handover proximity failures, or continues drifts, all configured dynamically by the network via a standards-aligned enhancement to ReportConfigNR.

[0055] Certain embodiments may provide one or more of the following technical advantage(s).• Event-Driven Intelligence: Enables the UE to autonomously evaluate when reporting is necessary, improving responsiveness to localized degradation.• Reporting Efficiency: Reduces unnecessary periodic reporting by sending Performance Monitoring Reports (PMRs) only when inference quality deteriorates — lowering signaling load.• Fine-Grained Diagnostic Insight: Reports include detailed indicators such as confidence drops, prediction drift, etc, offering deeper root cause visibility.• Standards-Compatible Extension: Leverages and extends 3GPP’s ReportConfigNR structure, ensuring backward compatibility and ease of integration into existing network stacks.• Al Lifecycle Support: By including functionality VersionlD and feedback hooks, the solution supports model lifecycle management and retraining workflows.• Resilience and Reliability: Includes mechanisms for inference-ground truth synchronization, fallback behavior, cooldown timers, and invalidation checks, enhancing robustness and avoiding report storms or misaligned metrics.

[0056] As used herein, Event and / or time-driven Performance Monitoring Report refers to a Measurement Report triggered by an event for performance monitoring of predictions. Hereafter, Event-Based performance monitoring report is used for both event and time driven performance monitoring report and their triggers.

[0057] Figure 1 shows an exemplary message sequence chart of a method for performing event and / or time driven performance monitoring in accordance with some embodiments of the present disclosure.

[0058] The method can begin at step 106 where the network node 104 sends to the UE 102 a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration. In an embodiment, the configuration can be sent in an RRCReconfiguration message (e.g. in a new Information Element included in the ReportConfigNR IE, e.g., CondTriggerConfig)

[0059] The UE at step 108 can parse the inference configuration and determine the CondTriggerConfig parameters and at step 110 start the inference.

[0060] At step 112, in a loop, (e.g., per inference occurred) the UE 102 can monitor a performance of the inference configuration while performing predictions. This can include for example checking prediction errors, confidence, and drift at step 114, and buffering the prediction results at step 116. Alternatively, if the ground truth is available (e.g., performed measurements) at step 118 the UE can buffer the actual measurements, at step 120 align timestamps, compute error code (e.g., Normalized Mean Square Error - NMSE) and discard stale predictions at step 122.

[0061] Next, the UE can then evaluate trigger conditions at step 124, where the trigger conditions include different types such as statistical, drift, temporal, handover proximity, etc.

[0062] If conditions are met, the UE 102 can send to the network node 104 at step 126 a performance monitoring report (PMR) when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled. The PMR report can include inference metrics, trigger type information, ReportConfigID, a model version ID, and a time stamp. The PMR report can also include one or more of the following, Event trigger ID (which rule fired), Prediction error metrics (e.g., NMSE, % Cumulative Distribution Function (CDF), Reference Signal Received Power (RSRP) difference), Timestamp, Confidence stats, Inference failure cause, Affected cells / beams (Set A / B distinction).

[0063] After sending the PMR report, the UE can start a cooldown timer at step 128 (e.g., reportCool do wnTimer), and then after expiration of the timer, the UE 102 can continued monitoring at step 130.

[0064] The network node 104 may then, at step 132 send an RRCReconfiguration message that includes updates to CondTriggerConfig, and the UE 102 at step 134 can apply the updated config or deactivate. The network node 104 based on the received Performance Monitor Report can send a reconfiguration message at step 132 to update to the Event-based performance monitoring report triggers, to update the PM configuration, or to deactivate the functionality.

[0065] In an embodiment, the UE, for every inference occasion, checks if inference outcome meets one or more conditions defined in the Event-Based Performance Monitoring Report criteria.

[0066] In an embodiment, the UE, at a subset of the inference occasions, e.g. every xthinference occasion, checks if inference outcome meets one or more conditions defined in theEvent-Based Performance Monitoring Report criteria. In an embodiment, the x is configured by the network node.

[0067] In an embodiment, the inference occasions for performance monitoring are the inference occasions in inference configuration but within the monitoring occasions (or monitoring window) in performance monitoring configuration. In an embodiment, one condition may be one event.

[0068] In an embodiment, Performance Monitoring Events (PME) which are UE received events that trigger performance monitoring can be related to Performance Monitoring Report Events (PMRE) which are UE received events that trigger performance monitoring reports. In an embodiment, the PME are exactly the same as PMRE. In another embodiment, the PME are subset of PMRE or the PMRE are subset of PME. In another embodiment, the PMREs are evaluated every triggered PME. In another embodiment, the PMREs are evaluated every xth triggered PME.

[0069] In an embodiment, the PME condition are applied directly on inference / prediction RSRP samples, whereas, the PMRE conditions are applied on the outcome of PME. For instance, PME is triggered when predicted RSRP is below a certain value, whereas PMRE is triggered when the PME e.g., difference between predicted RSRP and ground truth RSRP, is higher than a threshold.

[0070] In an embodiment, the performance monitoring report are configured to be sent every T second or Y% of the performance monitoring occasions.

[0071] In an embodiment, the performance monitoring are configured to be conducted every T second or Z% of the inference occasions.In an embodiment, the fulfillment of an event triggers periodical reporting, i.e. if an event for performance monitoring of predictions is fulfilled, the UE starts sending periodical reports to the network node.

[0072] In an embodiment, the non-fulfillment of an event for performance monitoring of predictions, after the event having been fulfilled, triggers the UE to send a report to the network node.

[0073] In an embodiment, the UE receives (from gNB) rules for monitoring inference performance. The configuration may include thresholds, time-to-trigger, window lengths, IDs of applicable triggers, and prediction setup references. These rules can be delivered during RRCReconfiguration, likely via ReportConfigNR message.

[0074] In an embodiment, the events received by UE in the Event-Based Performance Monitoring Report message contains one or more of the following conditions:• Prediction Statistical triggera. This trigger occurs when the performance of the inference configuration (or model or functionality) drops on the basis average, e.g., average prediction error > configured threshold, or prediction confidence. This trigger is useful when tracking prediction quality overtime, frequency, or different samples, (e.g., Normalized mean absolute error (NMAE), Normalized Mean Square Error NMSE, % of CDF, confidence). Confidence can be defined as a measure of how certain a machine learning model is about its output. In the context of a UE (User Equipment) performing AI / ML-based RSRP prediction, prediction confidence indicates how strongly the model believes its own prediction is correct, e.g., model’s softmax output drops below a threshold. This trigger is good for both Temporal, Spatial and Frequency domain prediction. In other words, the network configures the UE with an event and a triggering condition based to the statistical performance monitoring parameter to trigger a report when the statistical value of the performance metric fulfils one or more inequality condition(s) exemplified above.b. In another example, this trigger occurs when the performance metric of the inference configuration (or model or functionality) below to a first threshold for a given time duration, where the time duration may be one or more time instances. The performance metric may be MSE, NMSE, mean, CDF value, confidence, Fl- score, precision, recall, number of correct beam prediction, percentage of number of correct beam prediction and so on.c. In another example, this trigger occurs when the performance metric of the inference configuration (or model or functionality) below to a first threshold but not higher than a second threshold after below to the first threshold, for a given time duration, where the time duration may be one or more time instances. The performance metric may be MSE, NMSE, mean, CDF value, confidence, Fl- score, precision, recall, number of correct beam prediction, percentage of number of correct beam prediction and so on.i. Example of fields: predErr or Threshold, confldenceThreshold• Temporal triggera. It aims to Catch short-term bursts of prediction errors that may not be visible in long-term statistics. UE keeps a rolling buffer (sliding window) of recent inference results. It counts the number of failures (e.g., error above threshold, confidence below limit). If the number exceeds minEventsToTrigger in driftWindowLength, the condition is trigger.• Handover proximitya. It aims to detect when inference failures occurs just before or near a handover (HO) trigger condition, which could impact mobility robustness.• Prediction drifta. It aims to track systematic degradation in prediction quality over a multi-step forecast horizon. UE compares predicted values vs. actuals over time, then it calculates metrics like drift = |avg(prediction - ground truth). If drift exceeds driftDelta over driftWindowLength, trigger activates.• Observation Windowa. It aims to evaluate if the underlying environment is too volatile for predictions to remain valid or stable. In the trigger, the UE tracks statistical changes (e.g., RSRP variance, SINR jitter, Doppler spread) within the observationWindowLength. If the variance exceeds defined tolerances, it may indicate unstable inference context.

[0075] In an embodiment, for each inference occasion (e.g., predicted RSRP), or group of N inference occasions, the UE checks prediction vs. ground truth (when available), the UE checks (conditions sent via network for model performance monitoring) and evaluates drift, error margin, confidence, or inference validity. Evaluation approaches can be:• periodical, i.e., check performance after every N predictions or T seconds or every x inference occasion.• Event-driven: Trigger check immediately after certain output conditions (e.g., misprediction).

[0076] To enable such mechanism, UE stores intermediate inference results and ground truths (if delayed) for evaluation. It requires some buffering logic, resource management, and possibly simple ML performance scoring logic (e.g., moving average NMSE, confidence histograms).

[0077] In an embodiment, once one or more Event-based performance monitoring report triggers are satisfied, the UE generates a Performance Monitoring Report, including theInference configuration identity (e.g., Inference Objectld, measld and / or reportConfigld). The Report content could include one or more of the following, Condition trigger ID (which rule fired), Prediction error metrics (e.g., RSRP difference, NMSE, %CDF), Timestamp , Confidence stats, Inference failure cause, Affected cells / beams (Set A / B distinction). In an option of this method, the UE may send the performance monitoring information as part of the next report including the inference information e.g., next Measurement Report.

[0078] In an embodiment, once one or more Event-based performance monitoring report triggers are satisfied, UE sends one or more Performance Monitoring Report, including the Inference configuration identity (e.g., Inference Objectld and / or reportConfigld). In an option the Report content could include the absolute errors and (in)accuracy information concerning the last prediction. The UE may send successive reports including further (in)accuracy information associated to the subsequent predictions. In this embodiment the network configures the UE for how many subsequent predictions the UE should include the accuracy information in the report. In an option of this method, the UE reports (in)accuracy information as part of the inference report.

[0079] In an embodiment, where in the UE in order to conduct performance monitoring must align the inference values and ground truth values in time (or their domain) given variable delays, filter or normalize the comparison to allow valid performance scoring. This is critical because ML model quality can’t be validated unless you have both predicted and actual values available and correctly aligned. Proposed is a Synchronization mechanism, where UE should:• Log Inference output: For each inference, UE stores predicted value, beam / cell ID, timestamp, prediction horizon, etc. Alongside the Inference Objectld.• Buffer truth Measurement: UE should maintain a ring buffer of physical measurements with timestamps, RSRP, RSRQ, SINR, beam IDs, etc.• Match Logic: When ground truth measurements becomes available, UE should find the corresponding predicted value by matching targetCellld or beamld (or inference Id). Aligning is based on timestamp + horizon. Then, UE computes Error = actual - predicted, and store errorSample in the model evaluation statistics buffer.• Staleness I Validity Check: UE must discard any predictions where no matching actual found within a defined window (e.g., ±0ms strict, or ±T ms relaxed), target cell becomes inactive, or signal is out of valid range (e.g., < -130 dBm).

[0080] In an embodiment, once a performance monitor report is sent, , UE waits for a timer (e.g., reportcooldownTimer) before it starts re-evaluating or reporting again. This will prevent report storms, a suppression timer should be included.

[0081] In an embodiment, the UE should report the version of the AI / ML functionality (model) that was associated with such PMR. This is critical for LCM proposes. Include a e.g., functionality VersionlD in Inference Config object and reports.

[0082] In an embodiment, the UE should follow a configured fallback mechanism if inference (or prediction) fails (or the ground truth collection fails), hence UE cannot evaluate model performance monitoring.

[0083] In an embodiment, once UE sent PMR to gNB, UE can expect a feedback signal indicating some update to the triggers, or PM configuration update, or functionality deactivation.

[0084] ReportConfigNR (defined in TS 38.331) is extended with a new field:CondTriggerConfig-rXX, which holds the parameters for Event-based performance monitoring report triggers. Triggers are then bound to prediction object (or group of prediction objects). Such methodology maintains backward compatibility and aligns with how periodic and eventbased measurement reporting is configured today. It also enables flexibility via parameterization (e.g., thresholds, confidence, drift lengths, etc.).

[0085] This list defines how and when reports are triggered. Hence included is the proposed CondTriggerConfig-rXX: as a proposed additional element in the ReportConfigNR, where the underlined is the new addition to TS 38.331 :START EXCERPTReportConfigNR ::= SEQUENCE {reportType ENUM (periodical, eventTriggered, ...)EventTriggerConfig OPTIONALPeriodicalReportConfig OPTIONALCondTriggerConfig-rXX OPTIONALEND EXCERPT

[0086] The extended field like CondTriggerConfig-rXX is proposed to include the following new underlined text in TS 38.331:START EXCERPT-rXX ::= SEQUENCE {INTEGERconfidenceThreshold INTEGER (0..100).driftWindowLeneth INTEGER.minEventsToTrieeer INTEGER.driftDelta INTEGER.EventTriggerlD INTEGER.END EXCERPT

[0087] Figure 2 shows an example of a communication system 200 in accordance with some embodiments.

[0088] In the example, the communication system 200 includes a telecommunications network 202 that includes an access network 204, such as a radio access network (RAN), and a core network 206, which includes one or more core network nodes 208. The access network 204 includes one or more access network nodes or base stations of various types, access network nodes 210A and 210B are depicted (which may be collectively referred to as network nodes 210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 204 may include more than one access network technology. The network nodes 210 of access network 204 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections. In an embodiment, the access network nodes 210 can implement the functionality of the network node 104 from Figure 1, and the UEs 212 can implement the functionality of UE 102 from Figure 1.

[0089] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 202, including one or more access network nodes 210 and / or core network nodes 208.

[0090] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0091] The network nodes 210 facilitate direct or indirect connection of one or more UEs 212 to the core network 206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0092] The UEs 212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 210 and other communication devices. Similarly, the network nodes 208, 210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 202) with the UEs 212 and / or with other network nodes or equipment in the telecommunications network 202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 202. More specifically, UEs 212 may sendmessages, data, and / or other signals to network nodes 208, 210 or other elements of the telecommunications network 202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 208, 210 may send messages, data, and other signals to UEs 2122, other network nodes 208, 210, and other devices in telecommunications network 202 directly or indirectly. As one specific example, a core network node 208 may transmit a particular message to a UE 212 by transmitting the message to an access network node 210 that will then transmit the message to the intended UE 212.Similarly, a core network node 208 may receive a particular message from a UE 212 by receiving the message from an access network node 210 that itself received the message from the UE 212.

[0093] In the depicted example, the core network 206 connects elements of the access network 204 (e.g., one or more of the network nodes 210) to one or more host computing systems, such as host 216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 206 includes one or more core network nodes (e.g., core network node 208) of various types, one or more of which may be generally referred to as network nodes 208. Network nodes 208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 208. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0094] The host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and / or the telecommunications network 202. The host 216 may be operated by the service provider or on behalf of the service provider. The host 216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such asretrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0095] As a whole, the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 200 supporting different standards, protocols, or rule sets.

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

[0097] Telecommunications network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 202. For example, the telecommunications network 202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband(eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0098] In some examples, one or more of the UEs 212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204.Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0099] In the example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and / or 212D) and network nodes (e.g., network node 210B). In some examples, the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 214 may be a broadband router enabling access to the core network 206 for the UEs. As another example, the hub 214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 210, or by executable code, script, process, or other instructions in the hub 214.

[0100] As another example, the hub 214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0101] The hub 214 may have a constant / persistent or intermittent connection to the network node 210B. The hub 214 may also allow for a different communication scheme and / or schedule between the hub 214 and UEs (e.g., UE 212C and / or 212D), and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Moreover, the hub 214 may be configured to connect toan M2M service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 210B. In other embodiments, the hub 214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 21 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0102] Figure 3 is another example of a communication system 300 according to some embodiments. As used herein, the communication system 300 includes multiple access points (APs) 310 (with four exemplary APs 310A, 310B, 310C, and 310D being depicted) and multiple wireless devices, referred to in the context of communication system 300 as stations (STAs) 312 (referred to individually as STA 312A, STA 312B, STA 312C, STA 312D, and STA 312E). STA 312A is served by AP 310A in a first basic service set (BSS) 320A. STA 310B and STA 310C are served by AP 310B in a second BSS, BSS 320B. STA 312D is served by AP 310C in athird BSS, BSS 320C. STA 312E is served by AP 310D in a fourth BSS, BSS 320D. Stations 312 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. Further, stations 312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0103] Each of STAs 312 may connect through a radio link to one of APs 310. For example, depending on location or channel conditions experienced by a given STA 312, 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.

[0104] Each AP 310 may provide data connectivity to STAs 312 connected to a particular AP 310. As illustrated, APs 310 may be connected to a data network 330. In this way, APs 310 may also provide data connectivity between STAs 312 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, theradio link established between a given STA 312 and its serving AP 310 may be used for providing various kinds of services to STA 312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 312 and / or on a device linked to STA 312. By way of example, Figure 3 illustrates an application service platform 332 provided in data network 330. The application(s) executed on STA 312 and / or on one or more other devices linked to STA 312 may use the radio link for data communication with one or more other STA 312 and / or the application service platform 332, thereby enabling utilization of the corresponding service(s) at STA 312.

[0105] Figure 4 shows a wireless device 400, which may be configured to operate in communication system 200 of Figure 2 or in communication system 300 of Figure 3. The wireless device 400 may be alternatively referred to as a UE 400, like a UE 212 within the context of communication system 200, or as a station (STA) 400 or as a non-access-point station (non-AP STA) 400, like a STA 312 within the context of the communication system 300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0106] A wireless device 400 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 400 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 400 may represent a device that is notintended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0107] In particular embodiments, wireless device 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain embodiments of wireless device 400 may include all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one embodiment of wireless device 400 to another. In general, in a particular embodiment of wireless device 400, processing circuitry 402, input / output interface 406, power source 408, memory 410, and communication interface 412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 400. Further, certain embodiments of wireless devices 400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0108] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410. The processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 402 may include multiple central processing units (CPUs).

[0109] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., orany combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0110] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of wireless device 400 via input circuitry or an interface such as an electrical power cable. Power source 408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 400 to which power is supplied.[OHl] The memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by wireless device 400, any of a variety of various operating systems or combinations of operating systems.

[0112] The memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 410 may allow wireless device 400 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0113] The processing circuitry 402 may be configured to communicate with an access network or other network via or using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0114] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0115] In particular embodiments, wireless device 400 may provide an output of data captured via a sensor, through its communication interface 412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 400 can be communicated through a wireless connection to a network node via another wireless device 400. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert issent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0116] As another example, wireless device 400 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 400 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0117] Wireless device 400, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 400 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 400 shown in Figure 4.

[0118] As yet another specific example, in an loT scenario, wireless device 400 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 400 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 400 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 400 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable ofmonitoring and / or reporting on its operational status or other functions associated with its operation.

[0119] In practice, any number of wireless devices 400 may be used together with respect to a single use case. For example, a first wireless device 400 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 400 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 400 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 400 can also include more than one of the functionalities described above. For example, wireless device 400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0120] Figure 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 500 may be configured to operate in communication system 200 of Figure 2, like network nodes 208 or 210, or in communication system 300 of Figure 3, like an AP 310 or a station 312. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0121] Network nodes 500 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 500 may be a relay node or a relay donor node controlling a relay. Network nodes 500 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0122] Other examples of network nodes 500 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), basetransceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0123] In particular embodiments, network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. In general, in a particular embodiment of network node 500, processing circuitry 502, memory 504, communication interface 506, and power source 508 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 500.

[0124] The network node 500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an 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 500 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 504 or portions of memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, 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 500.

[0125] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 504, to provide network node 500 functionality.

[0126] In some embodiments, the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radiofrequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0127] The memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0128] The communication interface 506 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 506 may also include radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, an antenna 510. Particular embodiments of radio front-end circuitry 518 include filter(s) 520 and amplifier(s) 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 518 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal(s) may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are thenconverted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0129] In certain alternative embodiments, network node 500 may be capable of wireless communication but does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

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

[0131] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0132] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508may comprise a source of power in the form of a batery or batery pack which is connected to, or integrated in, power circuitry. The batery may provide backup power should the external power source fail.

[0133] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject mater described herein. For example, the network node 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

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

[0135] Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0136] Hardware 604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 606 (alsoreferred to as hypervisors or virtual machine monitors (VMMs)), provide VM 608A and VM 608B (which may be collectively referred to as VMs 608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 608.

[0137] The VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 606. Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

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

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

[0140] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein.Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0141] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0142] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0143] Some of the embodiments of the disclosure include:

[0144] Embodiment 1: A method performed by a User Equipment, UE, (102) for performing event and / or time-driven performance monitoring, the method comprising: receiving (106), from a network node (104), a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; monitoring (112) a performance of the inference configuration while performing predictions; sending (126), to the network node (104), a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0145] Embodiment 2: The method of embodiment 1, wherein the event-based performance monitoring report is received in an RRCReconfiguration message.

[0146] Embodiment 3: The method of any of embodiments 1 to 2, wherein the UE (102), for every inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

[0147] Embodiment 4: The method of any of embodiments 1 to 2, wherein the UE (102), at a predefined number of occurrences of an inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

[0148] Embodiment 5: The method of embodiment 4, wherein the predefined number is configured by the network node (104).

[0149] Embodiment 6: The method of embodiment 3, wherein inference occasions for performance monitoring are the inference occasions in inference configuration but within the monitoring occasions in the performance monitoring configuration.

[0150] Embodiment 7 : The method of any of embodiments 3 to 6, wherein a condition of the one or more conditions is an event.

[0151] Embodiment 8: The method of any of embodiments 1 to 7, wherein Performance Monitoring Events, PME, that trigger performance monitoring are related to Performance Monitoring Report Events, PMRE, that trigger a performance monitoring report.

[0152] Embodiment 9: The method of embodiment 8, wherein one or more of the following are true: PME are the same as PMRE; PME are a subset of PMRE; or PMRE are a subset of PME.

[0153] Embodiment 10: The method of embodiment 8, wherein: PMREs are evaluated every triggered PME; or PMREs are evaluated every xth triggered PME.

[0154] Embodiment 11 : The method of embodiment 8, wherein PME conditions are applied directly on inference or predicted Reference Signal Received Power, RSRP, samples, and PMRE conditions are applied on an outcome of PME.

[0155] Embodiment 12: The method of embodiment 8, wherein the performance monitoring report is configured to be sent every T seconds or Y% of the performance monitoring occasions.

[0156] Embodiment 13: The method of embodiment 8, wherein the performance monitoring is configured to be conducted every T seconds or Z% of the inference occasions.

[0157] Embodiment 14: The method of any of embodiments 1 to 13, wherein fulfillment of an event triggers periodical reporting to the network node (104).

[0158] Embodiment 15: The method of any of embodiments 1 to 14, wherein nonfulfillment of an event for performing monitoring of predictions, triggers sending the performance monitoring report to the network node (104).

[0159] Embodiment 16: The method of any of embodiments 1 to 15, wherein the receiving the performance monitoring configuration comprises receiving rules for monitoring inference performance, wherein the rules comprise one or more of thresholds, time to trigger, window lengths, IDs of applicable triggers, and prediction setup references.

[0160] Embodiment 17: The method of any of embodiments 1 to 16, wherein the eventbased performance monitoring report comprises events comprising one or more of the following conditions: prediction statistic trigger; temporal trigger; handover proximity; prediction drift; and observation window.

[0161] Embodiment 18: The method of any of embodiments 1 to 17, wherein for each inference occasion or group of N inference occasions, the UE (102) checks a prediction against an actual measurement.

[0162] Embodiment 19: The method of embodiment 17, wherein once one or more eventbased performance monitoring report triggers are satisfied, the UE (102) generates the performance monitoring report and an inference configuration identity.

[0163] Embodiment 20: The method of embodiment 17, wherein once one or more eventbased performance monitoring report triggers are satisfied the UE (102) sends, to the network node (104), the performance monitoring report and an inference configuration identity.

[0164] Embodiment 21: The method of any of embodiments 1 to 20, further comprising: aligning (120, 122) inference values and ground truth values in time given variable delays filter or normalize a comparison to allow valid performance scoring.

[0165] Embodiment 22:The method of any of embodiments 1 to 21, further comprising: after a performance monitoring report is sent, waiting (128) for a timer before reevaluating or reporting again.

[0166] Embodiment 23 : The method of any of embodiments of 1 to 22, wherein the sending the performance monitoring report comprises sending a version of an Artificial Intelligence / Machine Learning, AI / ML, model associated with the performance monitoring report.

[0167] Embodiment 24: The method of any of embodiments 1 to 23, wherein the UE (102) follows a configured fallback mechanism if inference or prediction fails and the UE (102) does not evaluation model performance monitoring.

[0168] Embodiment 25: The method of any of embodiments 1 to 24, wherein in response to sending the performance monitoring report to the network node (104), wait for at least one of a feedback signal, performance monitoring configuration update or functionality deactivation.

[0169] Embodiment 26: A User Equipment, UE, (102) for performing event and / or time-driven performance monitoring, the UE (102) configured to: receive (106), from a network node (104), a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; monitor (112) a performance of the inference configuration while performing predictions; send (126), to the network node (104), a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0170] Embodiment 27: The UE (102) of embodiment 26, further configured to perform any of embodiments 2 to 25.

[0171] Embodiment 28:A method performed by a network node (104) for configuring event and / or time-driven performance monitoring for receiving security information, the method comprising: providing (106), to a User Equipment, UE, (102) a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; and receiving (126) a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0172] Embodiment 29:The method of embodiment 28, wherein the performance monitoring configuration is included in an RRCReconfiguration message.

[0173] Embodiment 30: The method of embodiment 28, wherein the performance monitoring report includes one or more of the following: an event trigger identifier, a predictionerror metric; a timestamp; a confidence statistic; inference failure cause; and information about affected cells or beams.

[0174] Embodiment 31: The method of embodiment 28, further comprising: in response to receiving the performance monitoring report, sending (132) a reconfiguration message to update performance monitoring report triggers, update the PM configuration, or deactivate functionality.

[0175] Embodiment 32: A network node (104) for configuring event and / or time-driven performance monitoring for receiving security information, the network node (104) configured to: provide (106), to a User Equipment, UE, (102) a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; and receive (126) a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

[0176] Embodiment 33: The network node (104) of embodiment 32, further configured to perform any of embodiments 29 to 31.REFERENCES1. RP-242393, Study on Al (Artificial Intelligence) / ML (Machine Learning) for mobility in NR2. TR 38.843 v.18.0.0, Study on Artificial Intelligence (AI) / Machine Learning (ML) for NR air interface3. TS 38.331, v.18.5.1, NR; Radio Resource Control (RRC); Protocol specification

Claims

CLAIMS1. A method performed by a User Equipment, UE, (102) for performing event and / or time-driven performance monitoring, the method comprising:receiving (106), from a network node (104), a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration;monitoring (112) a performance of the inference configuration while performing predictions; andsending (126), to the network node (104), a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

2. The method of claim 1, wherein the event-based performance monitoring configuration is received in an RRCReconfiguration message.

3. The method of any of claims 1 to 2, wherein the UE (102), for every inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

4. The method of any of claims 1 to 2, wherein the UE (102), at a predefined number of occurrences of an inference occasion, checks if an inference outcome meets one or more conditions defined in the event-based performance monitoring report criteria.

5. The method of claim 4, wherein the predefined number is configured by the network node (104).

6. The method of claim 3, wherein inference occasions for performance monitoring are the inference occasions in inference configuration but within the monitoring occasions window in the performance monitoring configuration.

7. The method of any of claims 3 to 6, wherein a condition of the one or more conditions is an event.

8. The method of any of claims 1 to 7, wherein Performance Monitoring Events, PME, that trigger performance monitoring are related to Performance Monitoring Report Events, PMRE, that trigger a performance monitoring report.

9. The method of claim 8, wherein one or more of the following are true:PME are the same as PMRE;PME are a subset of PMRE; orPMRE are a subset of PME.

10. The method of claim 8, wherein:PMREs are evaluated every triggered PME; orPMREs are evaluated every xth triggered PME.

11. The method of claim 8, wherein PME conditions are applied directly on inference or predicted Reference Signal Received Power, RSRP, samples, and PMRE conditions are applied on an outcome of PME.

12. The method of any of claims 1 to 11, wherein fulfillment of an event triggers periodical reporting to the network node (104).

13. The method of claim 12, wherein the performance monitoring report is configured to be sent periodically.

14. The method of claim 13, wherein the performance monitoring report is configured to be sent every T time period, or Y% of the performance monitoring occasions.

15. The method of claim 12, wherein the performance monitoring is configured to be conducted periodically.

16. The method of claim 14, wherein the performance monitoring is configured to be conducted every T time period or Z% of inference occasions.

17. The method of any of claims 1 to 16, wherein non-fulfillment of an event for performingmonitoring of predictions, triggers sending the performance monitoring report to the network node (104).

18. The method of any of claims 1 to 17, wherein the receiving the performance monitoring configuration comprises receiving rules for monitoring inference performance, wherein the rules comprise one or more of thresholds, time to trigger, window lengths, IDs of applicable triggers, and prediction setup references.

19. The method of any of claims 1 to 18, wherein the event-based performance monitoring report comprises events comprising one or more of the following conditions:prediction statistic trigger;temporal trigger;handover proximity;prediction drift; andobservation window.

20. The method of any of claims 1 to 19, wherein for each inference occasion or group of N inference occasions, the UE (102) checks a prediction against an actual measurement.

21. The method of claim 19, wherein once one or more event-based performance monitoring report triggers are satisfied, the UE (102) generates the performance monitoring report and an inference configuration identity.

22. The method of claim 19, wherein once one or more event-based performance monitoring report triggers are satisfied the UE (102) sends, to the network node (104), the performance monitoring report and an inference configuration identity.

23. The method of any of claims 1 to 22, further comprising:aligning (120, 122) inference values and ground truth values in time given variable delays filter or normalize a comparison to allow valid performance scoring.

24. The method of any of claims 1 to 23, further comprising:after a performance monitoring report is sent, waiting (128) for a timer before reevaluatingor reporting again.

25. The method of any of claims of 1 to 24, wherein sending the performance monitoring report comprises sending a version identification of an Artificial Intelligence / Machine Learning, AI / ML, model associated with the performance monitoring report.

26. The method of any of claims 1 to 25, wherein the UE (102) follows a configured fallback mechanism if inference or prediction fails and the UE (102) does not evaluation model performance monitoring.

27. The method of any of claims 1 to 26, wherein in response to sending the performance monitoring report to the network node (104), the UE (102) waits for at least one of a feedback signal, inference configuration update, performance monitoring configuration update or functionality deactivation.

28. A User Equipment, UE, (102) for performing event and / or time-driven performance monitoring, the UE (102) configured to:receive (106), from a network node (104), a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration;monitor (112) a performance of the inference configuration while performing predictions; andsend (126), to the network node (104), a performance monitoring report when an eventbased performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

29. The UE (102) of claim 28, further configured to perform any of claims 2 to 27.

30. A method performed by a network node (104) for configuring event and / or time-driven performance monitoring for receiving security information, the method comprising:providing (106), to a User Equipment, UE, (102) a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; and receiving (126) a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report isfulfilled.

31. The method of claim 30, wherein the performance monitoring configuration is included in an RRCReconfiguration message.

32. The method of claim 30, wherein the performance monitoring report includes one or more of the following:an event trigger identifier,a prediction error metric;a timestamp;a confidence statistic;inference failure cause; andinformation about affected cells or beams.

33. The method of claim 30, further comprising:in response to receiving the performance monitoring report, sending (132) a reconfiguration message to update performance monitoring report triggers, update the performance monitoring configuration, update the inference configuration, or deactivate functionality.

34. A network node (104) for configuring event and / or time-driven performance monitoring for receiving security information, the network node (104) configured to:provide (106), to a User Equipment, UE, (102) a performance monitoring configuration comprising an event-based performance monitoring report and an inference configuration; and receive (126) a performance monitoring report when an event-based performance monitoring report criteria associated with the event-based performance monitoring report is fulfilled.

35. The network node (104) of claim 32, further configured to perform any of claims 31 to 33.