Network-side performance monitoring for ai mobility
By configuring wireless devices to perform RRM measurements and predictions at specific time occasions with confidence indicators, the solution addresses the inadequacies of existing network-side monitoring techniques, improving prediction accuracy and resource management in AI/ML-based RRM measurement and event prediction.
Patent Information
- Application Number
- PCT/SE2026/050313
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing network-side performance monitoring techniques for AI/ML-based RRM measurement and event prediction in wireless communications are inadequate, as they do not account for the unique characteristics of RRM measurement prediction and event prediction, which differ significantly from Al-based beam management and CSI prediction, and lack the ability to indicate exact sampling time occasions for reported measurements.
The proposed solution involves configuring wireless devices to perform RRM measurements and predictions at specific time occasions, allowing for network-side performance monitoring by reporting predicted and actual measurement results, with confidence indicators, to adjust inference configurations based on performance metrics.
This approach enables accurate network-side performance monitoring of RRM measurement and event prediction, enhancing mobility decisions by improving prediction accuracy and reducing unnecessary configuration changes, thus optimizing network resources.
Smart Images

Figure SE2026050313_12112026_PF_FP_ABST
Abstract
Description
[0001] NETWORK-SIDE PERFORMANCE MONITORING FOR Al MOBILITY
[0002] TECHNICAL FIELD
[0003] The present document is generally directed to wireless communications, and is more particularly directed to techniques for monitoring performance of artificial-intelligence / machine-learning (AI / ML) predictions performed for mobility purposes in a wireless communications network.
[0004] BACKGROUND
[0005] The 3rd-Generation Partnership Project (3GPP) is currently developing Release 19 (Rel-19) of their industry standards for wireless communications. As part of this development, 3GPP has agreed upon a study item regarding the use of artificial intelligence / machine-learning (AI / ML) for improving mobility for a wireless device (referred to as a “user equipment” or“UE,” in 3GPP terminology) operating in a wireless network. This study item explores the benefits of augmenting mobility functionality in wireless networks with features enabling improved support of AI / ML-based algorithms for enhanced performance and / or reduced complexity / overhead in such use cases in mobility as Radio Resource Management (RRM) measurement prediction, measurement event prediction, and prediction of Radio Link Failure (RLF) and Handover Failure (HOF) events.
[0006] The goal of the study is to focus on mobility enhancements for wireless devices operating in connected mode (formally, “RRC_CONNECTED mode”), i.e., in a mode where the wireless device has an active connection with an access node, e.g., a New Radio (NR) base station, referred to as a “gNB” in 3GPP terminology. More particularly, the study is concerned with following the existing mobility framework for mobility in RRC_CONNECTED mode, i.e., a framework in which the handover decision is always made on the network (NW) side. Mobility use cases in the study focus on standalone NR PCell (Primary Cell) change. In the study, both UE-side and NW-side usage of AI / ML models can be considered.
[0007] The objectives of the study item are to study and evaluate potential benefits and gains of AI / ML -aided mobility for network-triggered Layer 3 (L3)-based handover, considering the following aspects:
[0008] • AI / ML-based Radio Resource Management (RRM) measurement and event prediction o Cell-level measurement prediction including intra and inter-frequency (UE-side and NW-side model).Inter-cell Beam-level measurement prediction for L3 Mobility (UE-side and NW-side model).
[0009] o Handover (HO) failure / Radio Link Failure (RLF) prediction (UE-side model). o Measurement events prediction (UE-side model).
[0010] • Study the need for and / or benefits of any other UE assistance information for the network side model.
[0011] According to the study item:
[0012] • The evaluation of the AI / ML aided mobility benefits should consider HO performance key performance indicators (KPIs) (e.g., Ping-pong HO, HOF / RLF, Time of stay, Handover interruption, prediction accuracy, and measurement reduction) etc.) and complexity tradeoffs.
[0013] • Potential Al mobility specific enhancement should be based on the Rel-19 AI / ML-air interface Work Item Description (WID) general framework (e.g., Life Cycle Management (LCM), performance monitoring, etc.).
[0014] o NOTE: This would only be treated after sufficient progress is made in the Rel-19 AI / ML air interface WID.
[0015] • Potential specification impacts of AI / ML-aided mobility.
[0016] • Evaluate testability, interoperability, and impacts on RRM requirements and performance.
[0017] The following agreement has been taken during the Study Item in Rel-19 -this agreement indicates that the performance monitoring will be part of the study in Rel-19 and Rel-20 as well:
[0018] • The general Life Cycle Management (LCM) framework for beam management can be the baseline (where applicable) for Al mobility, such as the following aspects:
[0019] o Data collection for model training.
[0020] o UE capability.
[0021] o Applicability reporting.
[0022] o Inference configuration and reporting.
[0023] o Performance monitoring and management.
[0024] RRM measurement prediction in this study item includes RRM measurement prediction in the temporal domain, spatial domain and frequency domain. For temporal-domain prediction, an Al model predicts RRM measurement results for future time instances, and / or may predict unavailable RRM measurement results for partial time instances in the past and / or present,based on available RRM results measured by the UE. For spatial-domain prediction, an Al model predicts RRM measurement results for the beams / cells in Set A according to available RRM measurement results of the beams / cells in Set B, or predicts cell-level RRM measurement results based on RRM measurement results of one set of beams. In frequency-domain prediction, one Al model predicts RRM measurement results for the frequency(ies) in Set A according to available RRM measurement results for the frequency(ies) in Set B. Some examples for intra-frequency temporal RRM measurement prediction are shown in each of Figures 1 , 2, and 3.
[0025] SUMMARY
[0026] In various AI / ML-based solutions for RRM measurement prediction and / or event prediction, the AI / ML model or models may be deployed at the UE side or at the network side, or at both UE and network sides. If the AI / ML models are at the UE side, then the network needs to monitor the performance of the inference configuration related to the AI / ML models for functionality management purposes. There are existing solutions for network-side performance monitoring with UE-side model in wireless communication for Al-based beam management and Al-based Channel State Information (CSI) prediction, but not for RRM measurement prediction and RRM measurement event prediction in Al mobility.
[0027] However, RRM measurement and measurement event prediction differs substantially from Al-based beam management and Al-based CSI prediction. Consequently, the solutions of network-side performance monitoring in Al-based beam management and Al-based CSI prediction are not suitable for RRM measurement prediction and RRM measurement event prediction. The various techniques, apparatuses, and systems described herein address these problems.
[0028] These techniques include methods carried out by the wireless terminal (the “user equipment” or “UE,” in 3GPP terminology). An example of such methods, for supporting performance monitoring of artificial-intelligence / machine-learning (AI / ML) predictions performed by the wireless device, comprises the steps of predicting one or more radio resource management (RRM) measurements, according to configuration information provided to the wireless device by the wireless network, and performing corresponding actual measurements for the one or more predicted RRM measurements. This example method further comprises reporting both the predicted RRM measurements and the corresponding actual measurements to the wireless network.Other embodiments described herein include methods carried out in a network node in a wireless network, for monitoring performance of artificial-intelligence / machine-learning (AI / ML) predictions performed by a wireless device operating in the wireless network. An example of these methods comprises the steps of sending, to the wireless device, configuration information comprising performance monitoring parameters, and receiving, from the wireless device, one or more predicted RRM measurement results and corresponding actual measurement results.
[0029] An example wireless device corresponding to the method described above for performance by a wireless device comprises radio circuitry and processing circuitry operatively coupled to the radio circuitry. In various embodiments, the processing circuitry is configured to predict one or more RRM measurements, according to configuration information provided to the wireless device by a wireless network, and perform corresponding actual measurements for the one or more predicted RRM measurements. The processing circuitry is further configured to report both the predicted RRM measurements and the corresponding actual measurements to the wireless network.
[0030] Similarly, an example counterpart network node comprises radio circuitry and processing circuitry operatively coupled to the radio circuitry. In various embodiments, the processing circuitry is configured to send, to a wireless device, configuration information comprising performance monitoring parameters, and receive, from the wireless device, one or more predicted RRM measurement results and corresponding actual measurement results.
[0031] Variants of these and other methods, apparatuses, and systems are described in detail below and illustrated in the attached figures. The solutions described herein can be used to support network-side performance monitoring for RRM measurement prediction with a UE-side model. The RRM measurement is filtering-based and time-domain correlated within a relatively longer time windows, but the legacy RRM measurement framework is not able to indicate the exact sampling time occasions for the reported RRM measurement results and the reported RRM measurement prediction results.
[0032] BRIEF DESCRIPTION OFTHE FIGURES
[0033] Figure 1 , Figure 2, and Figure 3 each illustrate an example of intra-frequency temporal RRM measurement predictions.Figure 4 illustrates examples of inter-frequency RRM measurement prediction.
[0034] Figure 5 illustrates example RRC configuration information relating measurements for performance monitoring to predictions.
[0035] Figure 6 illustrates an example method as carried out by a wireless device, according to some embodiments.
[0036] Figure 7 illustrates an example method as carried out be a network node, according to some embodiments.
[0037] Figure 8 shows a communication system according to various embodiments of the present disclosure.
[0038] Figure 9 shows a UE according to various embodiments of the present disclosure.
[0039] Figure 10 shows a network node according to various embodiments of the present disclosure.
[0040] Figure 11 shows a host computing system according to various embodiments of the present disclosure.
[0041] Figure 12 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
[0042] Figure 13 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
[0043] DETAILED DESCRIPTION
[0044] As noted above, with AI / ML-based solutions for RRM measurement prediction and / or event prediction, the AI / ML model or models may be deployed at the UE side or at the network side, or at both UE and network sides. If the AI / ML models are at the UE side, then the network needs to monitorthe performance of the inference configuration related to the AI / ML models for functionality management purposes. For example, if the performance of the inference configuration becomes worse, the network may wish to deactivate the inference configuration. Information regarding the performance of the inference configuration may be used by the network for other purposes, as well.In network-side performance monitoring for one inference configuration with UE-side model for Al use cases in wireless communication, a UE is configured to report prediction results and measurement results to the network, according to the network configuration, so that the network can use the received prediction results and measurement results to calculate the performance information of the corresponding inference at the UE side.
[0045] While there are existing solutions for network-side performance monitoring with UE-side model in wireless communication for Al-based beam management and Al-based CSI prediction, there are differences between these procedures and RRM measurement prediction and RRM measurement event prediction in Al mobility. In RRM measurement prediction and RRM measurement event prediction, one RRM measurement / prediction in one time occasion may be correlated with other RRM measurements / predictions within one relatively longer time window, compared to measurement / prediction in Al-based beam management and Al-based CSI prediction. Moreover, legacy RRM measurement and report framework only indicates the report periodicity rather than the detailed sampling time for reported RRM measurements.
[0046] Therefore, the solutions of network-side performance monitoring in Al-based beam management and Al-based CSI prediction are not suitable for RRM measurement prediction and RRM measurement event prediction. The various techniques, apparatuses, and systems described herein address these problems.
[0047] These techniques include methods carried out by the wireless terminal (the “user equipment” or “UE,” in 3GPP terminology), wherein the UE receives configuration information, such as a Radio Resource Control (RRC) configuration, from the network, where this configuration information indicates to the UE to predict RRM measurement results for certain first time occasions (prediction occasions, or prediction times / time intervals) based on measuring RRM for certain second time occasions, where the prediction and the measurement are indicated to the wireless device via one inference configuration. In other words, the UE receives an inference configuration, e.g., as part of an RRC configuration, instructing the UE to perform the prediction in one or more of temporal, spatial, or frequency domain over a set of one or more radio resources (frequencies, cells, beams).
[0048] The configuration information may further comprise an indication to the UE to perform actual RRM measurements for third time occasions (or sample RRM measurement results in the third time occasions), where the first time occasions and the third time occasions (performance monitoring time occasions, or actual measurement times or time intervals) may be overlappedor partially overlapped, and where, moreover, the RRM measurements in the third time occasions may be based on at least partial RRM measurement results for the second time occasions and may be based on at least partial RRM prediction results for the first time occasions besides others RRM measurement needed for the calculation of the RRM measurement results in the third time occasions.
[0049] The third time occasions may be determined by the first time occasions (in the inference configuration from the network to the UE) and the monitoring window (in one performance monitoring configuration from the network to the UE). For example, the first time occasions within the monitoring window may be the third time occasions. Alternatively, the third time occasions may be determined by the first time occasions and a percentage of the prediction samples in a time window thatshould be monitored based on the performance monitoring configuration. Note that performance monitoring configuration information provided to the UE by the wireless network may explicitly or implicitly indicate the information for at least one of the monitoring window, the percentage, the third time occasions.
[0050] The configuration information may further indicate to the UE to report predicted RRM measurement results for the first time occasions and corresponding measured RRM measurement results for the third time occasions to the network.
[0051] In other words, the UE may receive a performance monitoring configuration, or performance monitoring configuration information more generally, as part of an RRC configuration instructing the UE to perform monitoring of the performance of one or more of the predictions in one or more of temporal, spatial or frequency domain over a set of one or more radio resources (frequencies, cells, beams)
[0052] Furthermore, the predicted RRM measurement results for the first time occasions and the measured RRM measurement results for the second time occasions may be in the same carrier frequency range or the different carrier frequency ranges. Likewise, the first time occasions may be same as the second time occasions or may be different from the second time occasions. Still further, the first time occasions may be partially overlapped with the second time occasions.
[0053] Still further, the UE may be configured to report the RRM measurement results for the second time occasions to the network. The performance monitoring configuration may explicitly or implicitly indicate the information for the inference configuration. The inference configurationmay explicitly or implicitly indicate (or include) the information for the performance monitoring configuration.
[0054] Furthermore, for network-side performance monitoring of the inference configuration, the network may calculate performance information based on at least the received predicted RRM measurement results for the first time occasions and the received measured RRM measurement results for the third time occasions (performance monitoring occasions). The network may use the performance information to decide whether to use RRM measurement event predications based on RRM measurement predictions of the inference configuration for mobility decision. The network may use the performance information to decide whether to send a deactivation indication and / or a release indication of the inference configuration to the UE.
[0055] The solutions described herein can be used to support network-side performance monitoring for RRM measurement prediction with UE-side model since the RRM measurement is filteringbased and time-domain correlated within a relatively longer time windows but the legacy RRM measurement framework is not able to indicate the exact sampling time occasions for the reported RRM measurement results and the reported RRM measurement prediction results.
[0056] Thus, the present disclosure involves the prediction of various RRM measurements, based on actual measurements taken at different times and / or at different frequencies. Events related to these measurements, such as Radio Link Failure (RLF) or Handover Failure (HOF), may also be predicted, in various embodiments. Various techniques for performing these predictions may be used, with many of these techniques falling within the domain of Machine Learning and Artificial Intelligence, which terms are used interchangeably herein to refer to computerized systems that are able to learn and adapt, without following explicit instructions, by using algorithms and statistical models to analyze and draw inferences from patterns in data. The inferences in the present context are the predicted measurements and / or events.
[0057] The terms “configuration” and “configuration information” are used herein to refer to information provided to a wireless device, by the wireless network, where that information defines elements and / or parameters of a task (or repeated tasks) to be carried out by the wireless devices and / or operational modes to be used by the wireless device. The configurations and configuration information described herein may be provided in formalized configuration messages, which may be modifications of various data structures defined by 3GPP standards for such things as measurement configurations and measurement reporting configurations.Intra-frequency temporal RRM measurement prediction - “Case A”
[0058] Various embodiments described herein may involve intra-frequency temporal RRM measurement predictions, according to scenarios defined by 3GPP as “Case A.” In one embodiment for intra-frequency temporal RRM measurement prediction, one UE is configured by the network to predict RRM measurements in future time instances based on available more RRM measurements in the past and present, for the same downlink reference signal(s) (e.g. SSB, CSI-RS, SSB resource set, CSI-RS resource set, NZP CSI-RS resource set) and same carrier frequency range, where the periodicity of predicted RRM measurements is same as the periodicity of measured RRM for report. In this case, the network uses received predicted RRM measurements and received real RRM measurements to calculate the performance metric(s) of RRM measurement prediction at the UE side. If the performance metric is good, then the network may choose to refrain from changing the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the performance metric is not good enough, then the network may choose to not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network may deactivate or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network and / or may be done by the UE.
[0059] Intra-frequency temporal RRM measurement prediction - “Case B”
[0060] Some embodiments described herein may involve intra-frequency temporal RRM measurement predictions according to scenarios defined by 3GPP as “Case B.” In one embodiment for intra-frequency temporal RRM measurement prediction, via inference configuration from network, for same downlink reference signal(s) (e.g. SSB, CSI-RS, SSB resource set, CSI-RS resource set, NZP CSI-RS resource set), one UE is configured to predict RRM measurement for first time occasions (e.g., prediction set, prediction resources) that are not overlapped with the second time occasions (e.g. measurement set, measurement resources) for configured RRM measurement, but for the same carrier frequency range.
[0061] For the purpose of network-side performance monitoring of this inference configuration for the RRM measurement prediction, the network further configures the UE to measure RRM for the third time occasions (e.g. monitoring set, monitoring resources) and reports RRM measurement results for the third time occasions where the third time occasions may be one subset of thefirst time occasions or may be same as the first time occasions or may be partially overlapped with the first time occasions, and the network may further configure the UE to get the filtered RRM measurement results of the third time occasions via new RRM measurements and / or the RRM measurement results in the second time occasions and / orvia the RRM measurement prediction results in the first time occasions.
[0062] The UE reports the RRM measurement prediction results in the first time occasions and RRM measurement results in the second time occasions and RRM measurement results in the third time occasions to the network. The network uses the received RRM measurement prediction results in the first time occasions and RRM measurement results in the third time occasions to calculate the performance metric(s) for the inference configuration of the intra-frequency temporal RRM measurement prediction case B at the UE side. If the performance metric is good, then the network may choose to refrain from changing the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the performance metric is not good enough, then the network may choose to not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network may deactivate or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network and / or may be done by the UE.
[0063] Inter-frequency RRM measurement prediction
[0064] In inter-frequency RRM measurement prediction, RRM measurement prediction in one carrier frequency is implemented based on RRM measurement results in another one or more carrier frequencies, and consequently, for one inference instance, it is expected that the time instances for these RRM measurements and RRM measurement prediction in different frequencies are very closed to each other as shown in Figure 4. RRM measurement in one carrier frequency is filtering-based results and time-domain correlated, and moreover legacy RRM measurement and report configuration only indicates report periodicity rather than exact measurement time instances for one reported RRM measurement. Therefore, similar to intra-frequency temporal RRM measurement predication case B, the configuration from the network to the UE for RRM measurement and report of monitoring resources is linked with corresponding inference configuration in inter-frequency RRM measurement prediction, especially when partial monitoring occasion is configured.Spatial RRM measurement prediction with cell-level RRM measurement prediction based on partial beam-level RRM measurements.
[0065] In spatial RRM measurement prediction with cell-level RRM measurement prediction based on partial beam-level RRM measurements, ground truth is cell-level RRM measurement based on all beam-level RRM measurements. In this case, for network-side performance monitoring purpose, the network needs to configure UE to measure all beam-level RRM measurements for cell-level RRM measurement results in specific sample time instances (i.e., the third time occasion) aligned with the sample time instances (i.e., the first time occasions) for cell-level RRM measurement prediction.
[0066] After receiving the prediction results and measurement results from the UE, the network uses the received RRM measurement prediction results in the first time occasions and RRM measurement results in the third time occasions to calculate the performance metric(s) for the inference configuration of the spatial RRM measurement prediction at the UE side, and the network may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the performance metric is not good enough, then the network may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network may deactivate or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network and / or may be done by the UE.
[0067] Spatial L3-beam-level RRM measurement prediction
[0068] In spatial L3-beam-level RRM measurement prediction, for one neighbor cell, the UE is configured by the network to measure the beams in Set B in the second time occasions and predict one or more strongest beams (e.g. beam index, SSB index, CSI-RS resource index CSI-RS resource set index) in Set A in the first time occasions and / or predict RRM measurements (e.g. L3-RSRP) of the one or more strongest beams in Set Ain the first time occasions. The first time occasions may be same as the second time occasions. The network further configures the UE to measure the beams in Set A in the third time occasions and report the prediction results in the first time occasions and measurement results in the third time occasions to the network. Note that the network may configure the UE to report the measurement results in the second time occasions to the network too.
[0069] The network uses the received RRM measurement prediction results in the first time occasions and RRM measurement results in the third time occasions to calculate the performancemetric(s) for the inference configuration of the spatial RRM measurement prediction at the UE side, and the network may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose. If the performance metric is not good enough, then the network may not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network may deactivate or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network and / or may be done by the UE.
[0070] Confidence indicators
[0071] In real deployments, the UE might lack sufficient signal strength to measure some resources (beams below detection threshold), or RRM report maybe based on old or filtered data, or certain measurement may be interpolated or averaged, reducing ground-truth fidelity. These scenarios lead to performance scoring bias, where the prediction error looks large, but in reality the measurement is uncertain.
[0072] To address this issue, the UE in some embodiments or instances may include a “validity / confidence indicator” with each report measurement or predicted samples (first and third). For instance, the UE may report one or more of the following:
[0073] ConfidenceLevel: e.g., a value from 0 to 1 , or 0-100%
[0074] ValidityFlag: e.g., TRUE = reliable, FALSE = partial / interpolated
[0075] MeasurementType: e.g., direct sample, filtered, extrapolated
[0076] This solution enables the network to weight predictions accordingly in performance monitoring metrics (e.g., by excluding low-confidence samples from MSE / F1 score computations), which results in a better assessment of UE ML performance and more accurate detection of whether degraded performance is due to model failure or weak measurements. Additionally, it enables the network to adjust LCM logic more intelligently (e.g., by deferring deactivation of an inference configuration). The above three fields (MeasurementConfidenceLevel, ValidityFlag, MeasurementSourceType) could be simply added in an extension of MeasurementResult information element (IE), e.g., as follows:
[0077] Measurementconfidenceinfo : : = SEQUENCE {
[0078] ConfidenceLevel INTEGER ( 0 . . 100 ) ,
[0079] measurementType ENUM { direct , filtered, interpolated } , ValidityFlag BOOLEAN
[0080] }In some embodiments or instances, if the UE could not measure ground truth (third) or inferthe prediction (first) for any of the following reason, the UE may indicate to the network that it failed to report ground truth (third) or prediction (first) or both. Such failures could be due to the UE being in discontinuous receive (DRX ) mode, or because the UE cannot measure a second sample (input to the inference) due to RSRP below certain level, etc. This can be accomplished simply by introducing a field to a report sent by the UE to the wireless network, such as:
[0081] Predictionstatus = NotEvaluated, or
[0082] Validationstatus = NotEvaluated, or
[0083] PredictionValidationStatus = NotEvaluated
[0084] In some embodiments or instances, the UE could report the reason why it could not perform the measurement or prediction (of third or first samples). This could be added to a report by, for instance, introducing the following fields: Reason = 0, Reason = 1 , Reason =2, where, for example:
[0085] DRX = 0
[0086] RSRP below detection = 1
[0087] Not part of measurement set = 2
[0088] The above fields could, for instance, be added by extending the existing MeasurementReport as follows:
[0089] PredictionValidationFeedback : : = SEQUENCE {
[0090] predictionlD INTEGER,
[0091] status ENUM { success , fail , notEvaluated } ,
[0092] failurecause ENUM { notMeasurable, DRX, filteringGap } OPTIONAL
[0093] }
[0094] Link between measurement configuration and inference configuration
[0095] In some embodiments, the UE receives, e.g., in an RRC Reconfiguration, the inference configuration associated with a measurement configuration for network based performance monitoring. Thus, the UE is aware of what needs to be reported in terms of measurement results related to the inference configuration.
[0096] For example, when the inference configuration indicates to the UE to predict a cell quality of cell A in the time-domain (forT time units ahead), the UE is configured to report measurements on that cell A for these occasions in the time units defined byT (but not all, otherwise there would be no point to predict).Or, for example, when the inference configuration indicates to the UE to predict a cell quality for a cell in frequency f1 , the UE is configured to perform measurements and report on that frequency f1.
[0097] In some embodiments, both the inference configuration and the measurement configuration may be configured in the same instance of a configuration (such as the same instance of the IE MeasIdToAddMod). In that case, the same measurement Id configuration applies to both the inference parameters and the measurement parameters. Consequently, both will have the same measld associated to them, even if distinct parameters could be defined, such as reporting periodicity for measurements and reporting periodic for predictions. Then, when the associated report is transmitted, the UE includes that measld.
[0098] For example, the UE may be configured to report both predictions and measurements in a subset of the occasions in which the UE reports the predictions.
[0099] In other embodiments, the inference configuration and the measurement configuration may be configured with different instances of a configuration (such as different instances of the IE MeasIdToAddMod). There may be different measurement Id configurations in this situation. In that case, there must be a clear association between the two different instances, e.g., where this association is indicated by the inference configuration including a pointer to the measurement configuration.
[0100] In one option, the pointer is an additional measurement identifier. In other words, in addition to the measurement identifier (first measld) of the MeasIdToAddMod that identifies the inference configuration, there is also included (e.g., nested in the IE or on top level) an additional measld (Second measld) that points to the associated measurement configuration. Thanks to this, some level of consistency may be guaranteed when the UE needs to perform the measurements associated to the inference configuration, for the purpose of performance monitoring at the network side. Figure 5 illustrates elements of an example RRC configuration that the UE may receive.
[0101] In another option, the pointer is an additional reporting configuration identifier. In that case, the inference configuration would have a first reporting configuration, which indicates how predictions are to be reported, and a second reporting configuration, indicating how the associated measurements are to be performed (e.g. different periodicity value or different criteria for events to report measurements). An example implementation of this in ASN.1 notation is as follows:MeasIDToAddMod : : = SEQUENCE {
[0102] measID Measld,
[0103] measOb j ectld MeasOb j ectld, reportConf igld ReportConf igld reportConf f orPerf ormanceMon ReportConf igld, }
[0104] As an example, the UE may include, in the report of predictions (e.g., in a first RRC Measurement Report) the first measld, while it includes, in the report of measurements (e.g. in a second RRC Measurement Report), the second measld. The network will understand the association since the network has configured with the UE with both these measld(s).
[0105] As another example, the UE may include in the report of predictions the first measld, while in the report of measurement it includes both the first measld and the second measld. Even if the network should otherwise understand the association, this approach may facilitate the interpretation of a report when both prediction and measurement are being included.
[0106] UE implementations
[0107] Embodiments of the presently disclosed techniques include methods carried out by a UE (or wireless device) configured with an inference configuration as well as with a performance monitoring configuration that is associated with the inference configuration. Examples of such methods may comprise one, several, or all of the steps of:
[0108] • receiving from a NW node a configuration comprising performance monitoring parameters.
[0109] • monitoring the performance of the inference configuration while performing predictions rReporting predicted RRM measurement results and measured RRM measurement results performed as part of performance monitoring to the network.
[0110] In some embodiments or instances, the performance monitoring related measurements may be reported later than the predicted RRM measurement results. In such cases, the UE may include the information to link / associate the performance monitoring related measurements with the corresponding predictions which are already sent to the network.
[0111] In some embodiments or instances, the performance monitoring related measurements may be reported together with the predicted RRM measurement results, where “together with” means that both predictions and associated measurement results (e.g., both for the same cell, same frequency and / or same beams of a cell) are included in the same report (e.g., the same measurement report, same RRC Measurement Report, or same Performance Monitoringreport). In a variation of these embodiments or instances, reporting “together with” means that predictions are included in a first measurement report (e.g., an RRC Measurement Report), with a first periodicity and having a first measurement identifier (measld), while measurement results are included in a second measurement report (e.g., RRC Measurement Report), with a second periodicity (e.g. larger than the first periodicity). These reports are associated since the measurements reported in the second measurement report relate to the predictions in the first measurement report.
[0112] In one sub-option of the preceding approach, the second measurement report has the same measurement identifier, but includes an indication indicating that this is a report including measurement results. In another sub-option, the second measurement report has a different measurement identifier (possibly associated with the first measurement identifier), so the network is able to distinguish between a report including predictions and an associated report including measurements.
[0113] In one option, for a given inference configuration (e.g., with a single measld), associated to a configuration of associated measurements for NW-side performance monitoring, the UE may transmit multiple measurement reports, where in a first measurement report including the measld there may be predictions and in a second measurement report including the same measld there may be both prediction(s) and associated measurements, for network based performance monitoring.
[0114] Thanks to both reports, including predictions and including measurement results, the network receiving them is able to monitor the performance for a given inference configuration and determine further actions, if necessary.
[0115] In some embodiments or instances, for intra-frequency temporal RRM measurement prediction, a UE is configured by the network to predict RRM measurements in future time instances based on available more RRM measurements in the past and present for the same downlink reference signal(s) (e.g. SSB, CSI-RS, SSB resource set, CSI-RS resource set, NZP CSI-RS resource set) and the same carrier frequency range, and the periodicity of predicted RRM measurements is same as the periodicity of measured RRM for report.
[0116] In other embodiments or instances, for intra-frequency temporal RRM measurement prediction, via an inference configuration received from the network, for same downlink reference signal(s) (e.g. SSB, CSI-RS, SSB resource set, CSI-RS resource set, NZP CSI-RS resource set), a UE is configured to predict RRM measurement for first time occasions (e.g. prediction set, predictionresources) that are not overlapped with second time occasions (e.g. measurement set, measurement resources) for configured RRM measurements, but for the same carrier frequency range. For the purposes of network-side performance monitoring of this inference configuration for the RRM measurement prediction, the network further configures the UE to measure RRM for the third time occasions (e.g., a monitoring set, monitoring resources) and reports RRM measurement results for the third time occasions, where the third time occasions may be one subset of the first time occasions or may be same as the first time occasions or may be partially overlapped with the first time occasions, and the network may further configure the UE to get the filtered RRM measurement results of the third time occasions via new RRM measurements and / or the RRM measurement results in the second time occasions and / or via the RRM measurement prediction results in the first time occasions.
[0117] For inter-frequency RRM measurement prediction, RRM measurement prediction in one carrier frequency is performed based on RRM measurement results in another one or more carrier frequencies, and consequently, for one inference instance, it is expected that the time instances for these RRM measurements and RRM measurement prediction in different frequencies are very closed to each other as shown in Figure 4. RRM measurement in one carrier frequency is filtering-based results and time-domain correlated, and moreover legacy RRM measurement and report configuration only indicates report periodicity rather than exact measurement time instances for one reported RRM measurement. Therefore, similar to intrafrequency temporal RRM measurement prediction case B, the configuration from the network to the UE for RRM measurement and report of monitoring resources is linked with corresponding inference configuration in inter-frequency RRM measurement prediction, especially when partial monitoring occasion is configured
[0118] For spatial RRM measurement prediction with cell-level RRM measurement prediction based on partial beam-level RRM measurements, ground truth is cell-level RRM measurement based on all beam-level RRM measurements. In this case, for network-side performance monitoring purposes, the network needs to configure UE to measure all beam-level RRM measurements for cell-level RRM measurement results in specific sample time instances (i.e., the third time occasion) aligned with the sample time instances (i.e., the first time occasions) for cell-level RRM measurement prediction.
[0119] For spatial L3-beam-level RRM measurement prediction, for one neighbor cell, the UE is configured by the network to measure the beams in Set B in the second time occasions and predict one or more strongest beams (e.g. beam index, SSB index, CSI-RS resource index CSI-RS resource set index) in Set A in the first time occasions and / or predict RRM measurements (e.g. L3-RSRP) of the one or more strongest beams in Set Ain the first time occasions. The first time occasions may be same as the second time occasions. The network further configures the UE to measure the beams in Set A in the third time occasions and report the prediction results in the first time occasions and measurement results in the third time occasions to the network. Note that the network may configure the UE to report the measurement results in the second time occasions to the network too
[0120] In various embodiments, the UE predicts RRM measurement results for the first time occasions based on RRM measurements performed for the second time occasions. The first time occasions may be temporally separated from (e.g., substantially later than) the second time instances. The UE may perform RRM measurements that correspond to the predicted RRM measurements for performance monitoring purposes, where these measurements are performed on third time occasions. The first time occasions and these third time occasions may be overlapped or partially overlapped, and moreover the RRM measurement in the third time occasions may be based on at least partial RRM measurement results for the second time occasions and may be based on at least partial RRM prediction results for the first time occasions besides others RRM measurement needed for the calculation of the RRM measurement results in the third time occasions.
[0121] In various embodiments or instances, the UE reports predicted RRM measurement results for the first time occasions and measured RRM measurement results (for performance monitoring purposes) for the third time occasions to the network using RRC messages (e.g., RRC MeasureReport message).
[0122] Network-side implementations
[0123] Embodiments of the presently disclosed techniques include methods carried out by a network node (or group of network nodes) operating in a wireless network, where the network node configures a UE with an inference configuration and a performance monitoring configuration. The methods may comprise, in various embodiments or instances:
[0124] • sending, to the UE, a configuration comprising performance monitoring parameters; and / or
[0125] • receiving from the predicted RRM measurement results together with measured RRM measurement results to the network.In some embodiments or instances, the network uses received predicted RRM measurements and received real RRM measurements to calculate the performance metric(s) of RRM measurement prediction at the UE side. If the performance metric is good, then the network may choose to not change the inference configuration for the RRM measurement prediction at the UE side and may use RRM measurement event prediction results based on the RRM measurement prediction for mobility purposes, e.g., for predicting mobility-related events such as RLF or HOF and taking action accordingly (e.g., by triggering a handover). If the performance metric is not good enough, then the network may choose to not use RRM measurement event prediction results based on the RRM measurement prediction for mobility purpose, and / or the network may deactivate or release the inference configuration of the RRM measurement prediction at the UE side and / or the inference configuration of the related RRM measurement event prediction at the UE side. Note that the RRM measurement event prediction may be done by the network and / or may be done by the UE.
[0126] Figure 6 is a process flow diagram illustrating an example method, as carried out by a wireless device operating in a wireless network, for supporting performance monitoring of artificial-intelligence / machine-learning (AI / ML) predictions performed by the wireless device. As shown at block 620, the method comprises predicting one or more radio resource management (RRM) measurements, according to configuration information provided to the wireless device by the wireless network. As shown at block 630, the method further comprises performing corresponding actual measurements for the one or more predicted RRM measurements. Still further, as shown at block 640, the method comprises reporting both the predicted RRM measurements and the corresponding actual measurements to the wireless network.
[0127] Note that the illustrated method is intended to represent a generalization of the various UE-based techniques described in detail above. Accordingly, where there are minor differences between the terminology used to describe the method in Figure 6 and the terminology used in the detailed examples above, it should be understood that the terminology used to describe Figure 6 is intended to at least encompass the similar or clearly related terminology used above, in such a way that the steps and details described for Figure 6 can be mapped to corresponding steps and details in the examples provided above.
[0128] In some embodiments or instances of the method shown in Figure 6, each of the corresponding actual measurements is performed for a measurement time interval that at least partly overlaps with a prediction time or prediction time interval for the respective predicted RRM measurement. In some of these and in some other embodiments, each of the predicted RRMmeasurements is predicted for a respective prediction time or prediction time interval, based on RRM measurements performed prior to and temporally separated from the prediction time or prediction time interval. In some other embodiments, each of the predicted RRM measurements is predicted for a respective prediction time or prediction time interval as well as for a respective prediction frequency or prediction frequency interval, based on RRM measurements performed on an actual frequency or frequency interval differing from the prediction frequency or prediction frequency interval.
[0129] In some embodiments or instances, the method may comprise receiving, prior to said predicting, inference configuration information indicating one or more predictions to be performed by the wireless device and / or defining one or more parameters for reporting the predicted RRM measurements and the corresponding actual measurements to the wireless network. This is shown at block 610 in Figure 6. Note that the “inference configuration information” referred to here may be labeled an “inference configuration” or it may be labeled differently, e.g., referred to as a performance monitoring configuration, or it may form part of a measurement configuration, in various embodiments or instances.
[0130] In some embodiments or instances of the method shown in Figure 6, the corresponding actual measurements are reported to the wireless network separately from the predicted RRM measurements. In some of these embodiments or instances, reporting the corresponding actual measurements comprises including, in a report carrying the actual measurements, a measurement identifier relating the corresponding actual measurements to previously provided predicted RRM measurements. In some cases, the measurement identifier in the report carrying the actual measurements is the same as a measurement identifier included in a report carrying the previously provided predicted RRM measurements. In others, the measurement identifier in the report carrying the actual measurements may be different from a second measurement identifier included in a report carrying the previously provided predicted RRM measurements, both measurement identifiers having been configured for the wireless device by the wireless network.
[0131] In some embodiments or instances, reporting both the predicted RRM measurements and the corresponding actual measurements to the wireless network may comprise reporting an indicator of confidence or validity for each of one or more predicted RRM measurements and / or corresponding actual measurements. Examples of the form or content of this indicator were provided above.Figure 7 is another process flow diagram, this time illustrating an example method, as carried out by a network node in a wireless network, for monitoring performance of artificial-intelligence / machine-learning (AI / ML) predictions performed by a wireless device operating in the wireless network. As shown at block 710, this method comprises sending, to the wireless device, configuration information comprising performance monitoring parameters. As shown at block 720, the method further comprises receiving, from the wireless device, one or more predicted RRM measurement results and corresponding actual measurement results.
[0132] In the same manner described above for Figure 6, the method shown in Figure 7 is intended to represent a generalization of the various network-side techniques described in detail above. Accordingly, where there are minor differences between the terminology used to describe the method in Figure 7 and the terminology used in the detailed examples above, it should be understood that the terminology used to describe Figure 7 is intended to at least encompass the similar or clearly related terminology used above, in such a way that the steps and details described for Figure 7 can be mapped to corresponding steps and details in the examples provided above.
[0133] In some embodiments or instances of the illustrated method, the performance monitoring parameters indicate one or more actual measurements to be performed by the wireless device, for performance monitoring of the predicted RRM measurements results. In some embodiments or instances, the method further comprises calculating a performance metric for the predicted RRM measurement results, based on the actual measurement results. This is shown at block 730. The method may further comprise determining to deactivate an inference configuration for predicting RRM measurement results, based on the performance metric. Alternatively, the method may further comprise determining to use (or continue to use) predicted RRM measurement results for predicting mobility events, based on the performance metric. These alternatives are illustrated at block 740.
[0134] Embodiments of the presently disclosed techniques include apparatuses, such as UE apparatuses and gNB apparatuses, configured to carry out any of the methods describe above. Below is a detailed description of an example wireless system and several of its nodes - it should be understood that the methods described above may be implemented in one or more of these nodes, in various embodiments and instances.
[0135] Figure 8 shows an example of a communication system 800 in accordance with some embodiments. This provides a context for the techniques described herein, which can beimplemented by devices operating in such a communication system 800. In this example, communication system 800 includes telecommunication network 802 that includes access network 804 (e.g., RAN) and a core network 806, which includes one or more core network nodes 808. Access network 804 includes one or more access network nodes, such as network nodes 81 Oa-b (one or more of which may be generally referred to as network nodes 810), or any other similar 3GPP access node or non-3GPP access point. Network nodes 810 facilitate direct or indirect connection of UEs, such as by connecting UEs 812a-d (one or more of which may be generally referred to as UEs 812) to core network 806 over one or more wireless connections.
[0136] 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, communication system 800 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. Communication system 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0137] UEs 812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network nodes 810 and other communication devices. Similarly, network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with UEs 812 and / orwith other network nodes or equipment in telecommunication network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in telecommunication network 802.
[0138] In the depicted example, core network 806 connects network nodes 810 to one or more hosts, such as host 816. These connections may be director indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 806 includes one or more core network nodes (e.g., 808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of core network node 808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access andMobility 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).
[0139] Host 816 may be under the ownership or control of a service provider other than an operator or provider of access network 804 and / or telecommunication network 802, and may be operated by the service provider or on behalf of the service provider. Host 816 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded audio / video content, data collection services such as retrieving 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.
[0140] As a whole, communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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 (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0141] In some examples, telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 802. For example, telecommunication network 802 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.
[0142] In some examples, UEs 812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to accessnetwork 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 804. 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-U MTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0143] In the example, hub 814 communicates with access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and / or 812d) and network nodes (e.g., network node 810b). In some examples, hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 814 may be a broadband router enabling access to core network 806 for the UEs. As another example, hub 814 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 810, or by executable code, script, process, or other instructions in hub 814. As another example, hub 814 may be a data collectorthat acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, hub 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, hub 814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
[0144] Hub 814 may have a constant / persistent or intermittent connection to network node 810b. Hub 814 may also allow for a different communication scheme and / or schedule between hub 814 and UEs (e.g., UE 812c and / or 812d), and between hub 814 and core network 806. In other examples, hub 814 is connected to core network 806 and / or one or more UEs via a wired connection. Moreover, hub 814 may be configured to connect to an M2M service provider over access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 810 while still connected via hub 814 via a wired or wireless connection. In some embodiments, hub 814 may be a dedicated hub -that is, a hub whose primary function is to route communications to / from the UEs from / to network node 810b. In other embodiments, hub 814 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node810b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0145] Figure 9 shows a UE 900 in accordance with some embodiments. UE 900 may be configured to carry out one or more of the methods described in detail above. Examples of a UE 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), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by 3GPP, including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0146] A UE 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, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE 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, a UE may represent a device that is not intended 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).
[0147] UE 900 includes processing circuitry 902 that is operatively coupled via bus 904 to input / output interface 906, power source 908, memory 910, communication interface 912, and possibly other components not explicitly shown. Certain UEs may utilize all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0148] Processing circuitry 902 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 memory 910. Processing circuitry 902 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, processing circuitry 902 may include multiple central processing units (CPUs).
[0149] In the example, input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices.
[0150] 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 UE 900. 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., or any 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.
[0151] In some embodiments, power source 908 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. Power source 908 may further include power circuitry for delivering power from power source 908 itself, and / or an external power source, to the various parts of UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from power source 908 to make the power suitable for the respective components of UE 900 to which power is supplied.
[0152] Memory 910 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 read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or otherapplication, and corresponding data 916. Memory 910 may store, for use by UE 900, any of a variety of various operating systems or combinations of operating systems.
[0153] Memory 910 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 (eUlCC), integrated UICC (iUICC) ora removable UICC commonly known as ‘SIM card.’ Memory 910 may allow UE 900 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in memory 910, which may be or comprise a device-readable storage medium.
[0154] Processing circuitry 902 may be configured to communicate with an access network or other network using communication interface 912. Communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to antenna 922. Communication interface 912 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 UE or a network node in an access network). Each transceiver may include transmitter 918 and / or receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0155] In the illustrated embodiment, communication functions of communication interface 912 may include cellular communication, Wi-Fi communication, 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 inaccordingto one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0156] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 19 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., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0157] As another example, a UE 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, the UE 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.
[0158] A UE, 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, city 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 smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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. A UE in the form of an loT device comprisescircuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to UE 900 shown in Figure 9.
[0159] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE 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, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0160] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE 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 UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0161] Figure 10 shows a network node 1000 in accordance with some embodiments. Network node 1000 may be configured to carry out one or more of the methods described herein with respect to a base station or other network node. Examples of network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).
[0162] Base stations 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. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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).Other examples of network nodes 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), base transceiver 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).
[0163] Network node 1000 includes processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008. Network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components 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, network node 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). Network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, 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 1000.
[0164] Processing circuitry 1002 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 network node 1000 components, such as memory 1004, to provide network node 1000 functionality.
[0165] In some embodiments, processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, RFtransceiver circuitry 1012 and baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
[0166] Memory 1004 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 nonvolatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by processing circuitry 1002. Memory 1004 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 (collectively denoted computer program product 1004a) capable of being executed by processing circuitry 1002 and utilized by network node 1000. Memory 1004 may be used to store any calculations made by processing circuitry 1002 and / or any data received via communication interface 1006. In some embodiments, processing circuitry 1002 and memory 1004 is integrated.
[0167] Communication interface 1006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. Communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. Radio frontend circuitry 1018 may be connected to antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. Radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal may then be transmitted via antenna 1010. Similarly, when receiving data, antenna 1010 may collect radio signals which are then converted into digital data by radio front-end circuitry 1018. The digital data may be passed to processing circuitry 1002. In other embodiments, thecommunication interface may comprise different components and / or different combinations of components.
[0168] In certain alternative embodiments, network node 1000 does not include separate radio frontend circuitry 1018, instead, processing circuitry 1002 includes radio front-end circuitry and is connected to antenna 1010. Similarly, in some embodiments, all or some of RF transceiver circuitry 1012 is part of communication interface 1006. In still other embodiments, communication interface 1006 includes one or more ports or terminals 1016, radio front-end circuitry 1018, and RF transceiver circuitry 1012, as part of a radio unit (not shown), and communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
[0169] Antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 1010 may be coupled to radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, antenna 1010 is separate from network node 1000 and connectable to network node 1000 through an interface or port.
[0170] Antenna 1010, communication interface 1006, and / or processing circuitry 1002 maybe configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, antenna 1010, communication interface 1006, and / or processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0171] Power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1000 with power for performing the functionality described herein. For example, network node 1000 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 power source 1008. As a further example, power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, orintegrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0172] Embodiments of network node 1000 may include additional components beyond those shown in Figure 10 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 matter described herein. For example, network node 1000 may include user interface equipment to allow input of information into network node 1000 and to allow output of information from network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1000.
[0173] Figure 11 is a block diagram of a host 1100, which may be an embodiment of host 816 of Figure 8, in accordance with various aspects described herein. Host 1100 may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. Host 1100 may provide one or more services to one or more UEs.
[0174] Host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input / output interface 1106, a network interface 1108, a power source 1110, and a memory 1112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of host 1100.
[0175] Memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g., data generated by a UE for host 1100 or data generated by host 1100 for a UE. Embodiments of host 1100 may utilize only a subset or all of the components shown. Host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). Host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, host 1100 may select and / or indicate adifferent host for over-the-top services for a UE. Host application programs 1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0176] Figure 12 is a block diagram illustrating a virtualization environment 1200 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 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
[0177] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0178] Hardware 1204 includes processing circuitry, memory that stores software and / or instructions (collectively denoted computer program product 1204a) 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 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208a-b (one or more of which may be generally referred to as VMs 1208), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to VMs 1208.
[0179] VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or moreof VMs 1208, and the implementations may differ. 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.
[0180] In the context of NFV, each VM 1208 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 VMs 1208, and that part of hardware 1204 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of hardware 1204 and corresponds to application 1202.
[0181] Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 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 1210, which, among others, oversees lifecycle management of applications 1202. In some embodiments, hardware 1204 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 control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
[0182] Figure 13 shows a communication diagram of a host 1302 communicating via a network node 1304 with a UE 1306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 812a of Figure 8 and / or UE 900 of Figure 9), network node (such as network node 810a of Figure 8 and / or network node 1000 of Figure 10), and host (such as host 816 of Figure 8 and / or host 1100 of Figure 11) discussed in the preceding paragraphs will now be described with reference to Figure 13.Like host 1100, embodiments of host 1302 include hardware, such as a communication interface, processing circuitry, and memory. Host 1302 also includes software, which is stored in or accessible by host 1302 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as UE 1306 connecting via an over-the-top (OTT) connection 1350 extending between UE 1306 and host 1302. In providing the service to the remote user, a host application may provide user data which is transmitted using OTT connection 1350.
[0183] Network node 1304 includes hardware enabling it to communicate with host 1302 and UE 1306. Connection 1360 may be direct or pass through a core network (like core network 806 of Figure 8) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0184] UE 1306 includes hardware and software, which is stored in or accessible by UE 1306 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1306 with the support of host 1302. In host 1302, an executing host application may communicate with the executing client application via OTT connection 1350 terminating at UE 1306 and host 1302. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. OTT connection 1350 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 1350.
[0185] OTT connection 1350 may extend via a connection 1360 between host 1302 and network node 1304 and via wireless connection 1370 between network node 1304 and UE 1306 to provide the connection between host 1302 and UE 1306. Connection 1360 and wireless connection 1370, over which OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between host 1302 and UE 1306 via network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0186] As an example of transmitting data via OTT connection 1350, in step 1308, host 1302 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 1306. In other embodiments, the user data is associated with a UE 1306 that shares data with host 1302without explicit human interaction. In step 1310, host 1302 initiates a transmission carrying the user data towards UE 1306. Host 1302 may initiate the transmission responsive to a request transmitted by UE 1306. The request may be caused by human interaction with UE 1306 or by operation of the client application executing on UE 1306. The transmission may pass via network node 1304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1312, network node 1304 transmits to UE 1306 the user data that was carried in the transmission that host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1314, UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1306 associated with the host application executed by host 1302.
[0187] In some examples, UE 1306 executes a client application which provides user data to host 1302. The user data may be provided in reaction or response to the data received from host 1302. Accordingly, in step 1316, UE 1306 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of UE 1306. Regardless of the specific manner in which the user data was provided, UE 1306 initiates, in step 1318, transmission of the user data towards host 1302 via network node 1304. In step 1320, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1304 receives user data from UE 1306 and initiates transmission of the received user data towards host 1302. In step 1322, host 1302 receives the user data carried in the transmission initiated by UE 1306.
[0188] One or more of the various embodiments improve the performance of OTT services provided to UE 1306 using OTT connection 1350, in which wireless connection 1370 forms the last segment. More precisely, embodiments can reduce and / or prevent undesired recovery actions by UEs. For example, due to the conditions for considering an LTM cell switch procedure successful (causing UE to stop a supervision timer), undesired recovery actions due to supervision timer expiration are prevented at the UE. This is especially an issue in the scenarios where LTM cell switch needs to be performed without a RA procedure (i.e., “RACH-less”). Preventing undesired recovery actions makes LTM RACH-less solutions more efficient, which reduces the delay to access an LTM candidate cell. Embodiments can facilitate predictable UE behavior in LTM execution failures and can reduce and / or eliminate ambiguity for UE actions in the event of LTM failures that are concurrent other failures such as radio link failure (RLF). By improving operationof UEs and RANs in this manner, embodiments increase the value of OTT services delivered to / from the UE via the RAN, to both end users and service providers.
[0189] In an example scenario, factory status information may be collected and analyzed by host 1302. As another example, host 1302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1302 may store surveillance video uploaded by a UE. As another example, host 1302 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, host 1302 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.
[0190] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1350 between host 1302 and UE 1306, in response to variations in the measurement results. The measurement procedure and / orthe network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 1302 and / or UE 1306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which OTT connection 1350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1304. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 1302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1350 while monitoring propagation times, errors, etc.
[0191] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view ofthe teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
[0192] The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and / or electronic devices and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.
[0193] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.
[0194] As described herein, device and / or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and / or apparatuses, whether functionally incooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
[0195] Furthermore, functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
[0196] In addition, certain terms used in the present disclosure, including the specification, drawings and embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that, while these words and / or other words that can be synonymous to one another, can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously.
[0197] Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.
[0198] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0199] In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and / or other terms that can be synonymous with one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously.
[0200] EXAMPLE EMBODIMENTS
[0201] Embodiments of the techniques, apparatuses, and systems described herein include, but are not limited to, the following enumerated examples:A1. A method, in a wireless device operating in a wireless network, for supporting performance monitoring of artificial-intelligence / machine-learning (AI / ML) predictions performed by the wireless device, the method comprising:
[0202] predicting one or more radio resource management (RRM) measurements, according to configuration information provided to the wireless device by the wireless network;
[0203] performing corresponding actual measurements for the one or more predicted RRM measurements; and
[0204] reporting both the predicted RRM measurements and the corresponding actual measurements to the wireless network.
[0205] A2. The method of example embodiment A1 , wherein each of the corresponding actual measurements is performed for a measurement time interval that at least partly overlaps with a prediction time or prediction time interval for the respective predicted RRM measurement.
[0206] A3. The method of example embodiment A1 or A2, wherein each of the predicted RRM measurements is predicted for a respective prediction time or prediction time interval, based on RRM measurements performed prior to and temporally separated from the prediction time or prediction time interval.
[0207] A4. The method of example embodiment A1 or A2, wherein each of the predicted RRM measurements is predicted for a respective prediction time or prediction time interval as well as for a respective prediction frequency or prediction frequency interval, based on RRM measurements performed on an actual frequency or frequency interval differing from the prediction frequency or prediction frequency interval.
[0208] A5. The method of anyone of example embodiments A1-A4, wherein the method comprises receiving, prior to said predicting, inference configuration information indicating one or more predictions to be performed by the wireless device and / or defining one or more parameters for reporting the predicted RRM measurements and the corresponding actual measurements to the wireless network.A6. The method of anyone of example embodiments A1-A5, wherein the corresponding actual measurements are reported to the wireless network separately from the predicted RRM measurements.
[0209] A7. The method of example embodiment A6, wherein reporting the corresponding actual measurements comprises including, in a report carrying the actual measurements, a measurement identifier relating the corresponding actual measurements to previously provided predicted RRM measurements.
[0210] A8. The method of example embodiment A7, where the measurement identifier in the report carrying the actual measurements is the same as a measurement identifier included in a report carrying the previously provided predicted RRM measurements.
[0211] A9. The method of example embodiment A7, where the measurement identifier in the report carrying the actual measurements is different from a second measurement identifier included in a report carrying the previously provided predicted RRM measurements, both measurement identifiers having been configured for the wireless device by the wireless network.
[0212] A10. The method of any one of example embodiments A1-A9, wherein reporting both the predicted RRM measurements and the corresponding actual measurements to the wireless network comprises reporting an indicator of confidence or validity for each of one or more predicted RRM measurements and / or corresponding actual measurements.
[0213] A11. A wireless device adapted to carryout a method according to anyone of example embodiments A1 -A10.
[0214] A12. A wireless device comprising radio circuitry and processing circuitry operatively coupled to the radio circuitry, the processing circuitry being configured, e.g., with program instructions stored in memory operatively coupled to the processing circuitry, to carry out a method according to any one of example embodiments A1-A11.
[0215] B1. A method, in a network node in a wireless network, for monitoring performance of artificial-intelligence / machine-learning (AI / ML) predictions performed by a wireless device operating in the wireless network, the method comprising:sending, to the wireless device, configuration information comprising performance monitoring parameters; and
[0216] receiving, from the wireless device, one or more predicted RRM measurement results and corresponding actual measurement results.
[0217] B2. The method of example embodiment B1 , wherein the performance monitoring parameters indicate one or more actual measurements to be performed by the wireless device, for performance monitoring of the predicted RRM measurements results.
[0218] B3. The method of example embodiment B1 or B2, further comprising calculating a performance metric for the predicted RRM measurement results, based on the actual measurement results.
[0219] B4. The method of example embodiment B3, further comprising determining to deactivate an inference configuration for predicting RRM measurement results, based on the performance metric.
[0220] B5. The method of example embodiment B3, further comprising determining to use predicted RRM measurement results for predicting mobility events, based on the performance metric.
[0221] B6. A network node adapted to carry out a method according to any one of example embodiments B1-B5.
[0222] B7. A network node comprising radio circuitry and processing circuitry operatively coupled to the radio circuitry, the processing circuitry being configured, e.g., with program instructions stored in memory operatively coupled to the processing circuitry, to carry out a method accordingto any one of example embodiments B1-B5.
[0223] REFERENCES
[0224] 1. RP-242393, Study on Al (Artificial lntelligence) / ML (Machine Learning) for mobility in NR 2. TR 38.843 v.18.0.0, Study on Artificial Intelligence (Al) / Machine Learning (ML) for NR air interface
[0225] 3. TS 38.331 , v.18.5.1 , NR; Radio Resource Control (RRC); Protocol specificationABBREVIATIONS 3GPP 3rd Generation Partnership Project 5GC / 5GCN 5G Core Network
[0226] 5GS 5G System
[0227] AF Application Function
[0228] Al Artificial Intelligence
[0229] AMF Access and Mobility Management Function AN Access Network
[0230] ARQ Automatic Repeat Request
[0231] API Application Programming Interface ARFCN Absolute Radio-Frequency Channel Number ASN.1 Abstract Syntax Notation One
[0232] BM Beam Management
[0233] CA Carrier Aggregation
[0234] CE Control Element
[0235] CGI Cell Global Identity
[0236] CHO Conditional Handover
[0237] CN Core Network
[0238] CP Control Plane
[0239] CPC Conditional PSCell Change
[0240] CSI-RS Channel State Information reference signal CU Central Unit
[0241] CU-UP Central Unit User Plane
[0242] DAPS Dual Active Protocol Stacks
[0243] DC Dual Connectivity
[0244] DCAF Data Collection Application Function
[0245] DCI Downlink Control Information
[0246] DRB Data Radio Bearer
[0247] DRX Discontinuous reception
[0248] DU Distributed Unit
[0249] eNB E-UTRAN NodeB
[0250] EN-DC E-UTRA-NR Dual Connectivity
[0251] E-UTRA Evolved UTRA
[0252] E-UTRAN Evolved UTRANgNB Radio base station in NR
[0253] GNSS Global Navigation Satellite System GPS Global Positioning System
[0254] HARQ Hybrid ARQ
[0255] HOF Handover Failure
[0256] ID Identifier / ldentity
[0257] IE Information Element
[0258] L2 Layer 2
[0259] LCM Life Cycle Management
[0260] LTE Long Term Evolution
[0261] MAC Medium Access Control
[0262] MBS Multicast Broadcast Service
[0263] MCE Measurement Collector Entity
[0264] MCG Master Cell Group
[0265] MDT Minimization of Drive Test
[0266] MIMO Multiple Input Multiple Output
[0267] ML Machine Learning
[0268] MME Mobility Management Entity
[0269] MN Master Node
[0270] MNO Mobility Network Operator
[0271] MR-DC Multi-Radio Dual Connectivity
[0272] NE-DC NR-E-UTRA Dual Connectivity
[0273] NEF Network Exposure Function
[0274] NG Next Generation
[0275] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NG-RAN NG Radio Access Network
[0276] NR New Radio
[0277] NW Network
[0278] NWDAF Network Data Analytics Function OAM / O&M Operation and Maintenance
[0279] OTT Over-the-Top
[0280] PBCH Physical Broadcast Channel
[0281] PCell Primary Cell
[0282] PCF Policy Control FunctionPCI Physical Cell Identity
[0283] PDCCH Physical Downlink Control Channel
[0284] PDCP Packet Data Convergence Protocol
[0285] PDU Protocol Data Unit
[0286] PLMN Public Land Mobile Network
[0287] PSCell Primary Secondary Cell
[0288] PTM Point to Multipoint
[0289] PTP Point to Point
[0290] QCI QoS Class Identifier
[0291] QFI QoS Flow Identifier
[0292] QMC QoE Measurement Collection
[0293] QoE Quality of Experience
[0294] QoS Quality of Service
[0295] RACH Random Access Channel
[0296] RAN Radio Access Network
[0297] RAT Radio Access Technology
[0298] RLF Radio Link Failure
[0299] RLM Radio Link Monitoring
[0300] RRC Radio Resource Control
[0301] RRM Radio Resource Management
[0302] RSRP Reference Signal Received Power
[0303] RSRQ Reference Signal Received Quality
[0304] RSSI Received Signal Strength Indicator
[0305] RV-QOE RAN Visible QoE
[0306] S1 The interface between the RAN and the CN in LTE. S1AP S1 Application Protocol
[0307] SCell Secondary Cell
[0308] SCG Secondary Cell Group
[0309] SDT Small Data Transmission
[0310] SINR Signal to Interference and Noise Ratio
[0311] SMF Session Management Function
[0312] SMO Service Management and Orchestration
[0313] SN Secondary Node
[0314] SNR Signal to Noise RatioSRB Signaling Radio Bearer
[0315] SSB Synchronization Signal Block
[0316] TA Terminal Adaptor
[0317] TCE Trace Collector Entity
[0318] TE Terminal Equipment
[0319] TS Technical Specification
[0320] UCI Uplink Control Information
[0321] UDM User Data Management
[0322] UE User Equipment
[0323] UP User Plane
[0324] URI Uniform Resource Identifier
[0325] URL Uniform Resource Locator
[0326] URLLC Ultra-Reliable Low-Latency Communication VR Virtual Reality
[0327] XML Extensible Markup Language
Claims
CLAIMS1. A method, in a wireless device operating in a wireless network, for supporting performance monitoring of artificial-intelligence / machine-learning, AI / ML, predictions performed by the wireless device, the method comprising:predicting (620) one or more radio resource management, RRM, measurements, according to configuration information provided to the wireless device by the wireless network;performing (630) corresponding actual measurements for the one or more predicted RRM measurements; andreporting (640) both the predicted RRM measurements and the corresponding actual measurements to the wireless network.
2. The method of claim 1 , wherein each of the corresponding actual measurements is performed for a measurement time interval that at least partly overlaps with a prediction time or prediction time interval for the respective predicted RRM measurement.
3. The method of claim 1 or 2, wherein each of the predicted RRM measurements is predicted for a respective prediction time or prediction time interval, based on RRM measurements performed prior to and temporally separated from the prediction time or prediction time interval.
4. The method of claim 1 or 2, wherein each of the predicted RRM measurements is predicted for a respective prediction time or prediction time interval as well as for a respective prediction frequency or prediction frequency interval, based on RRM measurements performed on an actual frequency or frequency interval differing from the prediction frequency or prediction frequency interval.
5. The method of anyone of claims 1-4, wherein the method comprises receiving (610), prior to said predicting, inference configuration information indicating one or more predictions to be performed by the wireless device and / or defining one or more parameters for reporting the predicted RRM measurements and the corresponding actual measurements to the wireless network.
6. The method of anyone of claims 1-5, wherein the corresponding actual measurements are reported to the wireless network separately from the predicted RRM measurements.
7. The method of claim 6, wherein reporting (640) the corresponding actual measurements comprises including, in a report carrying the actual measurements, a measurement identifier relating the corresponding actual measurements to previously provided predicted RRM measurements.
8. The method of claim 7, where the measurement identifier in the report carrying the actual measurements is the same as a measurement identifier included in a report carrying the previously provided predicted RRM measurements.
9. The method of claim 7, where the measurement identifier in the report carrying the actual measurements is different from a second measurement identifier included in a report carrying the previously provided predicted RRM measurements, both measurement identifiers having been configured for the wireless device by the wireless network.
10. The method of any one of claims 1-9, wherein reporting (640) both the predicted RRM measurements and the corresponding actual measurements to the wireless network comprises reporting an indicator of confidence or validity for each of one or more predicted RRM measurements and / or corresponding actual measurements.
11. A wireless device (900) adapted to carryout a method according to any one of claims 1-10.
12. A wireless device (900) comprising radio circuitry (912) and processing circuitry (902) operatively coupled to the radio circuitry (912), the processing circuitry (902) being configured to:predict one or more radio resource management, RRM, measurements, according to configuration information provided to the wireless device by a wireless network; perform corresponding actual measurements for the one or more predicted RRM measurements; andreport both the predicted RRM measurements and the corresponding actual measurements to the wireless network.
13. The wireless device (900) of claim 12, wherein the processing circuitry (902) is configured to perform each of the corresponding actual measurements for a measurement time interval that at least partly overlaps with a prediction time or prediction time interval for the respective predicted RRM measurement.
14. The wireless device (900) of claim 12 or 13, wherein the processing circuitry (902) is configured to predict each of the predicted RRM measurements for a respective prediction time or prediction time interval, based on RRM measurements performed prior to and temporally separated from the prediction time or prediction time interval.
15. The wireless device (900) of claim 12 or 13, wherein the processing circuitry (902) is configured to predict each of the predicted RRM measurements for a respective prediction time or prediction time interval as well as for a respective prediction frequency or prediction frequency interval, based on RRM measurements performed on an actual frequency or frequency interval differing from the prediction frequency or prediction frequency interval.
16. The wireless device (900) of any one of claims 12-15, wherein the processing circuitry (902) is configured to receive, prior to said predicting, inference configuration information indicating one or more predictions to be performed by the wireless device and / or defining one or more parameters for reporting the predicted RRM measurements and the corresponding actual measurements to the wireless network.
17. The wireless device (900) of any one of claims 12-16, wherein the processing circuitry (902) is configured to report the corresponding actual measurements to the wireless network separately from the predicted RRM measurements.
18. The wireless device (900) of claim 17, wherein the processing circuitry (902) is configured to report the corresponding actual measurements by including, in a report carrying the actual measurements, a measurement identifier relating the corresponding actual measurements to previously provided predicted RRM measurements.
19. The wireless device (900) of claim 18, where the measurement identifier in the report carrying the actual measurements is the same as a measurement identifier included in a report carrying the previously provided predicted RRM measurements.
20. The wireless device (900) of claim 18, where the measurement identifier in the report carrying the actual measurements is different from a second measurement identifier included in a report carrying the previously provided predicted RRM measurements, both measurement identifiers having been configured for the wireless device by the wireless network.
21. The wireless device (900) of any one of claims 12-20, wherein the processing circuitry (902) is configured to report an indicator of confidence or validity for each of one or more predicted RRM measurements and / or corresponding actual measurements.
22. A method, in a network node in a wireless network, for monitoring performance of artificial-intelligence / machine-learning, AI / ML, predictions performed by a wireless device operating in the wireless network, the method comprising:sending (710), to the wireless device, configuration information comprising performance monitoring parameters; andreceiving (720), from the wireless device, one or more predicted Radio Resource Management, RRM, measurement results and corresponding actual measurement results.
23. The method of claim 22, wherein the performance monitoring parameters indicate one or more actual measurements to be performed by the wireless device, for performance monitoring of the predicted RRM measurements results.
24. The method of claim 22 or 23, further comprising calculating (730) a performance metric for the predicted RRM measurement results, based on the actual measurement results.
25. The method of claim 24, further comprising determining (740) to deactivate an inference configuration for predicting RRM measurement results, based on the performance metric.
26. The method of claim 24, further comprising determining (740) to use predicted RRM measurement results for predicting mobility events, based on the performance metric.
27. A network node (1000) adapted to carry out a method according to any one of claims 22-26.
28. A network node (1000) comprising radio circuitry (1018) and processing circuitry (1002) operatively coupled to the radio circuitry (1018), the processing circuitry (1002) being configured to:send, to a wireless device, configuration information comprising performance monitoring parameters; andreceive, from the wireless device, one or more predicted Radio Resource Management, RRM, measurement results and corresponding actual measurement results.
29. The network node (1000) of claim 28, wherein the performance monitoring parameters indicate one or more actual measurements to be performed by the wireless device, for performance monitoring of the predicted RRM measurements results.
30. The network node (1000) of claim 28 or 29, wherein the processing circuitry (1002) is further configured to calculate a performance metric for the predicted RRM measurement results, based on the actual measurement results.
31. The network node (1000) of claim 28, wherein the processing circuitry (1002) is further configured to determine to deactivate an inference configuration for predicting RRM measurement results, based on the performance metric.
32. The network node (1000) of claim 28, wherein the processing circuitry (1002) is further configured to determine to use predicted RRM measurement results for predicting mobility events, based on the performance metric.
