Techniques for dynamically triggered CSI reporting carrying time domain beam prediction

Abstract

Techniques may support dynamically triggered channel state information (CSI) reporting carrying time domain beam prediction. A user equipment (UE) may receive, from a network entity, a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report and a second control message requesting the UE to send a CSI report indicating predicted CSI measurements based on a parameter set of the one or more parameter sets. The UE may send the CSI report to the network entity in response to the second control message. The CSI report may indicate the predicted CSI measurement for the set of beams based on the set of parameters.

Description

Technical Field

[0001] The following relates to wireless communications, including techniques for dynamically triggered channel state measurement (CSI) reporting that carries time-domain beam prediction. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting technologies for dynamically triggered channel state information (CSI) reporting that carries time domain beam prediction. For example, a network entity may configure a user equipment (UE) with one or more parameters for predicting CSI measurements and reporting the predicted CSI measurements in a CSI report. The network entity may send a control message that includes a configuration for the UE to generate a CSI report based on beam prediction. The configuration may include a trigger state configuration, a CSI report setting, or both for a CSI report generated based on predicted future channel characteristics. The configuration may indicate parameters for the UE to perform beam prediction for future beams and report the predicted measurements via a CSI report. The network entity may send a request message (e.g., a trigger message or an activation message) to the UE, which requests the UE to send a CSI report with predicted measurements generated based on one or more configurations. The UE may send a report including predictive beam measurements to the network entity based on the indicated configuration. The UE may be configured to report predicted CSI measurements via aperiodic CSI reports, periodic CSI reports, or semi-periodic CSI reports. The UE may indicate to the network entity UE capabilities for CSI prediction, such as a first supported timing gap between triggering predictive CSI reporting and sending the predictive CSI report or a second supported timing gap between triggering the predictive CSI report and a time slot or time instance for generating the predicted measurement.

[0004] A method for wireless communication at a UE is described. The method may include: receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and sending the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor; a memory coupled to the processor, the memory having instructions stored therein, the instructions executable by the processor to cause the apparatus to: receive a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; receive a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and send the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report, means for receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets, and means for sending the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; receive a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and send the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0008] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a capability message indicating the UE's ability to perform the beam prediction, wherein the predicted CSI measurement for the set of beams may be based on the capability message.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates a first supported time domain gap between a first time slot in which the second control message may be received and a start symbol or an end symbol for the predicted CSI measurement, a second supported time domain gap between the first time slot in which the second control message may be received and a second time slot in which the CSI report may be sent, a third supported time domain gap between a first symbol in which the CSI report may be sent and the start symbol for the predicted CSI measurement, or any combination thereof.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capabilities message indicates one or more values ​​for the first supported time domain slot, the second supported time domain slot, or the third supported time domain slot, or any combination thereof.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates a first capability of the UE to perform the beam prediction based on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based on a second number of measured resources or a second number of reported reference signals.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control message may include operations, features, components, or instructions for receiving the first control message indicating, for each of the one or more parameter sets, a time gap between the second control message and a future instance or future window of the predicted CSI measurement for the set of beams.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control message may include operations, features, components, or instructions for receiving the first control message indicating, for each parameter set of the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted CSI measurement for the set of beams.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the CSI report may include operations, features, components, or instructions for sending the CSI report indicating a future instance or future window of the predicted CSI measurement for the set of beams.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for predicting CSI measurements for the set of beams at a future time instance, during a future time window, or during a future scheduled transmission opportunity associated with one or more channel measurement resources or one or more interference measurement resources.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the second control message may include operations, features, components, or instructions for: receiving a downlink control information message that triggers a non-periodic CSI report based on the parameter set, wherein the non-periodic CSI report may be the CSI report.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the second control message may include operations, features, components, or instructions for: receiving a medium access control message that activates a semi-persistent CSI report based on the parameter set, wherein the semi-persistent CSI report may be the CSI report.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control message may include operations, features, components, or instructions for receiving the first control message indicating the one or more parameter sets and a second set of parameter sets, wherein the one or more parameter sets may be associated with CSI predictions and the second set of parameter sets may be associated with historical CSI measurements.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the second control message may include operations, features, components, or instructions for receiving the second control message based on a radio network temporary identifier associated with the CSI prediction.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the field of the second control message indicating the one or more parameter sets may be associated with CSI prediction.

[0021] A method for wireless communication at a network entity is described. The method may include: sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; sending a second control message requesting a UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and receiving the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0022] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor; a memory coupled to the processor, the memory having instructions stored therein, the instructions executable by the processor to cause the apparatus to: send a first control message, the first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; send a second control message, the second control message requesting a UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and receive the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0023] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report, means for sending a second control message requesting a UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets, and means for receiving the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; send a second control message requesting a UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in the one or more parameter sets; and receive the CSI report in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based on the parameter set.

[0025] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a capability message indicating the UE's ability to perform the beam prediction, wherein the predicted CSI measurement for the set of beams may be based on the capability message.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates a first supported time domain gap between a first time slot in which the second control message may be sent and a start symbol or an end symbol for the predicted CSI measurement, a second supported time domain gap between the first time slot in which the second control message may be sent and a second time slot in which the CSI report may be received, a third supported time domain gap between a first symbol in which the CSI report may be received and the start symbol for the predicted CSI measurement, or any combination thereof.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capabilities message indicates one or more values ​​for the first supported time domain slot, the second supported time domain slot, or the third supported time domain slot, or any combination thereof.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability message indicates a first capability of the UE to perform the beam prediction based on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based on a second number of measured resources or a second number of reported reference signals.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for sending the first control message indicating, for each of the one or more parameter sets, a time gap between the second control message and a future instance or future window of the predicted CSI measurement for the set of beams.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for sending the first control message indicating, for each of the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted CSI measurement for the set of beams.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the CSI report may include operations, features, components, or instructions for receiving the CSI report indicating a future instance or future window of the predicted CSI measurement for the set of beams.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the predicted CSI measurement for the set of beams corresponds to a future time instance, a future time window period, or a future scheduled transmission opportunity period associated with one or more channel measurement resources or one or more interference measurement resources.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control message may include operations, features, components, or instructions for sending a downlink control information message that triggers a non-periodic CSI report based on the parameter set, wherein the non-periodic CSI report may be the CSI report.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control message may include operations, features, components, or instructions for sending a medium access control message that activates a semi-persistent CSI report based on the parameter set, wherein the semi-persistent CSI report may be the CSI report.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for sending the first control message indicating the one or more parameter sets and a second set of parameter sets, wherein the one or more parameter sets may be associated with CSI predictions and the second set of parameter sets may be associated with historical CSI measurements.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control message may include operations, features, components, or instructions for sending the second control message using a radio network temporary identifier associated with a CSI prediction.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the field of the second control message indicating the one or more parameter sets may be associated with CSI prediction. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An example of a wireless communication system supporting techniques for dynamically triggered channel state measurement (CSI) reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 2 An example of a wireless communication system supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 3 An example of a timeline of techniques supporting dynamically triggered CSI reporting for carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 4 An example of a process flow diagram of a technique supporting dynamically triggered CSI reporting for carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figure 5 and Figure 6 A block diagram of a device supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown.

[0043] Figure 7 A block diagram of a communications manager supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction is shown in accordance with one or more aspects of the present disclosure.

[0044] Figure 8 A diagram of a system including devices supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig. 9 and Fig.10 A block diagram of a device supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig.11 A block diagram of a communications manager supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.12 A diagram of a system including devices supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction is shown in accordance with one or more aspects of the present disclosure.

[0048] Figures 13 to 16 A flow chart illustrating a method of supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0049] A wireless communication system may support time-domain beam prediction based on machine learning. Predictive beam management at a network entity may reduce overhead while improving accuracy and throughput compared to measurement-based beam management. The network entity may receive beam information from a user equipment (UE) and input the beam information into a machine learning model to output a beam prediction. In some examples, the network entity may determine a confidence level for one or more beam predictions. If the beam confidence prediction of a beam prediction is too low (e.g., below a threshold), the network entity may not implement beam management based on the beam prediction. For example, the network entity may request additional information to increase the confidence of the beam prediction.

[0050] A wireless communication system may support technology for dynamically triggered channel state information (CSI) reports that carry time domain beam prediction. A network entity may send a control message indicating one or more configurations or parameter sets for generating CSI reports based on beam prediction. The control message may include a CSI triggering state configuration, a CSI report setting, or both. The configuration for generating CSI reports based on beam prediction may include parameters for predicting future beams or predicting future channel characteristics and reporting the predictions via a CSI report. In some examples, the network entity may send a control message indicating a configuration for beam prediction via a radio resource control (RRC) message. The network entity may send another control message (e.g., a request message) requesting a CSI report from a UE, and the request message may indicate one of the configurations for beam prediction.

[0051] The UE may perform CSI measurement prediction based on the indicated configuration and send a report including the predicted CSI measurement to the network entity. The UE may be requested to report the predicted CSI measurement via an aperiodic CSI report, a periodic CSI report, or a semi-periodic CSI report. In some examples, the UE may indicate to the network entity UE capabilities for CSI prediction, such as a threshold difference (e.g., a maximum or minimum time difference) between transmissions or a time instance for prediction. For example, the UE may indicate a minimum duration between receiving a request for a CSI report including a CSI prediction and sending a CSI report with a CSI prediction, or a maximum duration between receiving a request for a CSI report and a time instance for generating a CSI prediction.

[0052] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to wireless communication systems, timelines, and process flow diagrams. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams involving techniques for dynamically triggered CSI reporting carrying time domain beam prediction.

[0053] Figure 1 An example of a wireless communication system 100 that supports techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0054] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0055] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0056] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0057] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0058] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a gigabit NodeB (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home NodeB, a home eNodeB, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0059] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0061] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0062] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0063] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay for transmissions to UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0064] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0065] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support the techniques described herein for dynamically triggered CSI reporting carrying time-domain beam prediction. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0066] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0067] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0068] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0069] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0070] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0071] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, a BWP) or all of the carrier bandwidth.

[0072] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to any combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0073] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be constrained to one or more active BWPs.

[0074] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0075] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0076] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0077] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0078] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0079] A macro cell generally covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) compared to macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0080] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0081] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0082] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0083] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0084] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other energy-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or any combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0085] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms "ultra-reliable", "low latency", and "ultra-reliable low latency" are used interchangeably herein.

[0086] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0087] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0088] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0090] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0091] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0092] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0093] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0094] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0095] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0096] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0097] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use any combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), CSI reference signals (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described herein with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0098] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0099] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection for a radio bearer supporting user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

[0100] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include any combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0101] In some examples of the wireless communication system 100, beam management may be calculated via historical measurements (e.g., the last beam measurement). However, calculating beam quality and failures only via measurements may result in high power consumption or overhead. Additionally, if power and overhead consumption are limited, beam accuracy may be limited. To prevent these problems, the wireless communication system 100 may use artificial intelligence (AI) or machine learning models to implement predictive beam management. In some examples, predicting unmeasured beam quality may reduce power consumption and overhead, and predicting future beam blocking and failures may reduce latency and increase throughput.

[0102] In some examples, the prediction measurements may be highly nonlinear because the beam prediction may be based on the speed or trajectory of the UE 115, the number of receive beams used or to be used, interference, or other qualities. For example, as an input to the machine learning model, there may be a time series of L1-RSRP. In some cases, the input may be based on inferences from the network entity 105, which may be based on L1-RSRP or receive beams reported by different UEs 115, or side information (e.g., UE 115 location information). In some other cases, the input may be based on inferences from the UE 115, which may be based on L1-RSRP measured by the UE 115, the receive beams used at the UE 115, or side information (e.g., location, other UE 115 predictions) signaled from the network entity 105 via downlink communications.

[0103] In some examples, there may be some tradeoffs for basing inputs on inferences from the network entity 105 or UE 115. For example, when predicting future downlink transmit beam quality, the UE 115 may have more observations via measurements than a network entity 105 whose observations are determined based on feedback from the UE 115. Therefore, the predictions at the UE 115 may outperform those of the network entity 105, but the UE 115 may consume more power for the inference work than the network entity 105. Additionally, training a machine learning model at the network entity 105 or UE 115 may have some additional tradeoffs. For example, to train a model at the network entity 105, data may be collected via an air interface or via an application layer approach, however, this may result in additional data collection work that may increase power consumption or latency. However, training a model at the UE 115 may also result in increased power consumption or latency because model training may require additional computation and buffering work. Additionally, additional data storage may be required at the UE 115. Thus, while both the UE 115 and the network entity 105 may have increased power consumption or latency as a result of training the model, the power consumption or latency of the UE 115 or the network entity 105 may be compensated by the other device being used for beam prediction. For example, in some cases, the network entity 105 may train the model and the UE 115 may perform beam prediction for the model (or vice versa) so that neither the network entity 105 nor the UE 115 continuously experiences increased power or consumption for a given amount of time.

[0104] After being trained and receiving input from the network entity 105 or UE 115, the machine learning model may output various beam predictions. In some cases, the model may output a predicted L1-RSRP and a corresponding confidence level (e.g., facilitated by additional RSRP mean and deviation predictions) as well as a predicted beam identifier and a corresponding confidence level. The confidence levels (e.g., ranging from a lowest confidence of 0 to a highest confidence of 1) generated along with the predicted output enable the network entity 105 and UE 115 to determine whether to use the predicted beam. For example, a high confidence level (e.g., 0.9) may signal that the predicted measurement is accurate and reliable, while a low confidence level (e.g., 0.1) may signal that the predicted measurement should not be used and should be regenerated after more data has been collected to calculate the predicted measurement.

[0105] In some cases, there may be a threshold for the confidence level, where if the prediction has a confidence level below a predetermined threshold (e.g., 0.5), the prediction should not be used and should be re-determined with more information. In some examples, predicting L1-RSRP and beam identifiers may support service beam refinement and link quality (e.g., CQI / PMI) and interference adaptation. In some other examples of model outputs, the model may generate predictions about beam failures and blockages. These predictions may support the generation of beam failure or blockage predictions or radio link failure predictions. In such examples, the machine learning model may benefit the UE 115 by supporting lower power consumption or lower UE 115-specific reference signal overhead compared to other statistical signal processing methods, and may allow lower latency and increased throughput.

[0106] The techniques described herein may support dynamically triggered CSI reporting that carries time domain beam prediction. The network entity 105 may configure the UE 115 with a configuration for CSI reporting. The configuration may include parameters for performing dynamic beam prediction and reporting predicted measurements via CSI reporting. The network entity 105 may send a control message indicating the configuration for beam measurement and CSI reporting, and may send a trigger message requesting a report. The UE 115 may send a report including predictive beam measurements to the network entity based on the indicated configuration. The UE 115 may be configured to report predicted CSI measurements via aperiodic CSI reporting, periodic CSI reporting, or semi-periodic CSI reporting. The UE 115 may indicate to the network entity the UE 15 capabilities for CSI prediction, such as a threshold difference (e.g., a maximum or minimum time difference) between transmissions.

[0107] Figure 2 An example of a wireless communication system 200 that supports techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated.

[0108] The wireless communication system 200 describes a network entity 105-a (which may be as described herein with reference to Figure 1 105) and UE 115-a (which may be an example of a network entity 105 as described herein) Figure 1 The network entity 105-a and the UE 115-a may send various messages via the downlink 210, the uplink 205, or both.

[0109] The wireless communication system 200 may support predictive beam management and measurement-based beam management. For measurement-based beam management, the network entity 105-a or the UE 115-a or both may select a beam based on measurements of channel conditions. For predictive beam management, the network entity 105-a or the UE 115-a or both may perform predictions of future beams or channel characteristics, and the network entity 105-a and the UE 115-a may use beams to communicate based on these predictions. Predictive beam management may reduce power consumption and resource overhead for beam management. In some examples, beam predictions may have corresponding confidence levels. For example, if the beam prediction has sufficient data to make a reliable prediction, the beam prediction may have a high confidence level. If the beam measurement has a low confidence level, the network entity 105-a may not perform beam management based on the beam measurement with the low confidence level.

[0110] The wireless communication system 200 may support techniques for providing additional information for predictive beam management based on UE-side predictions. For example, the network entity 105-a may configure a set of parameters (e.g., a configuration) to the UE 115-a to perform CSI measurement predictions. The network entity 105-a may request the UE 115-a to send a CSI report and indicate, with the request, one of the configurations for CSI measurement predictions. The network entity 105-a may receive a CSI report with a CSI measurement prediction and may supplement the network-side beam prediction with the additional information, or may otherwise implement beam management based on the CSI measurement predictions from the UE 115-a.

[0111] For example, the network entity 105-a may request the UE to report historically measured beams or predicted future beams in a CSI report. The network entity 105-a may send a control message 220 indicating a configuration for the UE 115-a to perform CSI measurement predictions or beam predictions and report these predictions in a CSI report 230. The UE 115-a may determine whether the number of reports associated with the CSI report 230 relates to historical measurements or predicted future channel characteristics. The UE 115-a may determine whether the number of reports is for historical measurements or predictions based on signaling from the network entity 105-a, such as a control message 220 for configuring a CSI report configuration or a request message 225 for triggering or activating a CSI report 230. In some examples, the reported quantities of CSI report 230 may include layer 1 (L1) reference signal received power (RSRP), L1 signal to interference plus noise ratio (SINR), rank indicator (RI), precoding matrix indicator (PMI), layer indicator (LI), channel quality indicator (CQI), CSI-RS resource indicator (CRI), synchronization signal block indicator (SSBI), beam blocking, or any combination thereof.

[0112] The historical measurements may be associated with a channel measurement resource (CMR) or an interference measurement resource (IMR), or both a CMR and an IMR, corresponding to CSI report 230. Predicted future channel characteristics may also be associated with a CMR or an IMR, or both a CMR and an IMR, corresponding to CSI report 230, but the predicted future channel characteristics may be determined for a time instance or resource opportunity that did not occur when UE 115-a generated the prediction. If CSI report 230 includes a measurement prediction, the report quantity may include a confidence level for the measurement prediction.

[0113] In some examples, the network entity 105-a may indicate a future time instance or window, and the UE 115-a may predict the channel characteristics of the indicated future time instance or window. For example, if the number of reports of the CSI report 230 corresponds to the predicted future channel characteristics, the configuration for the CSI report 230 may indicate the future time instance or window for prediction. In some examples, the control message 220 indicating the parameter set or configuration may indicate a future time opportunity or window, or the request message 225 may indicate a future time opportunity or window. In some examples, the UE 115-a may perform prediction for a time instance later than when the request message 225 is received or a time instance offset from the time instance. For example, the time instance for prediction may be offset from the request message 225 by a certain number of milliseconds, time slots, or subframes. In some examples, the control message 220 may include a time offset for the UE 115-a to identify the time instance. In some examples, the time instance may be offset from the time slot used to send the CSI report 230. For example, UE 115-a may apply the configured time offset to the time slot allocated for CSI reporting to identify a time instance for determining a CSI measurement prediction.

[0114] In some examples, the UE 115-a may perform predictions for a future time window. For example, the future time window may have a starting point that is offset by a certain amount of time (e.g., milliseconds), symbols, time slots, subframes from the request message 225, or may have a starting point that is offset by that amount of time from the CSI report 230. In some cases, the control message 220 may indicate a time offset or duration of a window for generating a CSI measurement prediction, or both a time offset and duration for a CSI report configuration associated with a predictive measurement. In some examples, the UE 115-a may perform predictions for one or more specific future transmission opportunities. For example, when the UE 115-a sends a CSI report 230 including a predictive measurement of a CMR / IMR associated with the CSI report 230, the UE 115-a may not have received signaling via the future transmission opportunity. In some examples, the UE 115-a may select a time instance or time window for generating a measurement prediction, and the UE 115-a may indicate the time instance or window for generating the prediction in the CSI report 230.

[0115] In some examples, the CSI report 230 may be an aperiodic CSI report and may trigger the UE 115-a to send a CSI report 230 that includes a CSI measurement prediction. The network entity 105-a may send one or more control signals indicating one or more control information elements to configure parameters for predictive CSI reporting or trigger an aperiodic CSI report associated with a measurement prediction. For example, the network entity 105-a may send a control message 220 indicating one or more parameters for one or more CSI report settings. In some cases, each CSI report setting may include a flag (e.g., a predictive flag) that indicates whether the CSI report setting is associated with a historical measurement or a predicted measurement. In some examples, the predictive flag for the CSI report setting may be configured to be associated with a predicted measurement, and the CSI report setting may include additional parameters for future time instances of the predicted measurement (e.g., a window or time instance associated with the prediction).

[0116] In some examples, control message 220 may indicate parameters for an aperiodic trigger state configuration associated with a corresponding CSI reporting setting and a predictive CSI measurement to be reported via an aperiodic CSI report. In some examples, the aperiodic trigger state configuration may include information for future time instances or windows for CSI measurement prediction or additional parameters for UE 115-a to use to generate CSI measurement predictions.

[0117] If the CSI report 230 is an aperiodic CSI report, an aperiodic CSI report associated with an aperiodic trigger state may be triggered via a DCI. A parameter (e.g., CSI-AssociatedReportConfigInfo) indicated by the DCI may include a flag set to indicate that the aperiodic CSI report is associated with a CSI measurement prediction, and the parameter may include information associated with a future time instance for CSI measurement prediction (e.g., an indication parameter).

[0118] In some examples, the network entity 105-a may use a hybrid indication to trigger an aperiodic CSI report for CSI measurement prediction. For example, a CSI report setting included in the control message 220 may include a portion of parameters for aperiodic CSI measurement prediction, while an aperiodic trigger state configuration associated with the CSI report 230 setting may include another portion of parameters for aperiodic CSI measurement prediction. For example, the CSI report setting may indicate whether the report quantity is about historical measurements or predicted future channel characteristics (e.g., via a flag in an information element of the CSI report setting). The aperiodic trigger state configuration may indicate more details about the time instance used for CSI measurement prediction. If the flag in the CSI report corresponds to a predictive measurement, information for future time instances may be included in one or more indications, fields, parameters, or information elements (e.g., a CSI-AssociatedReportConfigInfo field, which may be included as part of a CSI-AperiodicTriggerState field, which may be included as part of a CSI-AperiodicTriggerStateList field).

[0119] In some examples, the network entity 105-a may trigger an aperiodic CSI report for CSI measurement prediction via a DCI having a separate aperiodic CSI trigger state list. In some cases, the separate aperiodic CSI trigger state list may be dedicated to or specific to CSI measurements for beam prediction. The CSI trigger state list associated with an aperiodic CSI report having a number of reports based on predicted future channel characteristics may be configured separately from the CSI trigger state list for historical measurements. For example, the DCI may include a first CSI trigger state list associated with historical measurements or a second CSI trigger state list associated with beam prediction, or both. In some examples, the DCI including the CSI trigger state list for beam prediction may be formatted according to a DCI format based on beam prediction. In some examples, the DCI with the CSI trigger state list for beam prediction may include an RNTI based on beam prediction. In some cases, the DCI may include a CSI request field specific to beam prediction to indicate the CSI trigger state list for aperiodic beam prediction. In some examples, the CSI request field may include a field for aperiodic triggering (e.g., CSI-AperiodicTriggerStateList-BeamPrediction). The request message 225 or the DCI that triggers predictive aperiodic CSI reporting (e.g., CSI-AperiodicTriggerStateList) may be based on the DCI format or RNTI, or a CSI request field included as part of the DCI and dedicated to a separate aperiodic CSI trigger state list.

[0120] In some examples, UE 115-a may send capability message 215 to network entity 105-a based on the CSI measurement prediction. For example, capability message 215 may include information indicating one or more capabilities of UE 115-a for performing CSI measurement prediction. In some examples, the capability message may indicate a timeline capability or requirement for UE 115-a to perform CSI measurement prediction.

[0121] In some cases, UE 115-a may be configured to report CSI measurement predictions via periodic or semi-periodic (e.g., semi-persistent) CSI reporting. For example, UE 115-a may be configured with a set of parameters for a periodic CSI reporting setup or a semi-periodic CSI reporting setup to send a periodic CSI report or a semi-periodic CSI report that includes a CSI measurement prediction. In some examples, for semi-periodic CSI reporting, request message 225 may be an activation message, such as a MAC message or a MAC control element. The activation message may similarly indicate one or more CSI reporting settings associated with beam prediction, and indicate parameters for UE 115-a to perform and report CSI measurement predictions via semi-periodic CSI reporting.

[0122] Figure 3 An example of timeline 300, timeline 301, and timeline 302 are illustrated to support techniques for dynamically triggered CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure. Timeline 300, timeline 301, and timeline 302 may correspond to a timeline capability of UE 115 for beam reporting via aperiodic CSI reporting, semi-persistent CSI reporting, or periodic CSI reporting, respectively.

[0123] Timeline 300 corresponds to dynamically triggered CSI reporting with time domain beam prediction according to one or more aspects of the present disclosure. Timeline 300 illustrates different timing gaps for aperiodic predictive CSI reporting from UE 115 based on the capabilities of UE 115. UE 115 may report the timeline capabilities as described herein with reference to Figure 2 The capability may be related to a CSI parameter indication signaled by the network entity 105 via a control message. For example, the network entity 105 may configure the CSI reporting settings or associated information for the CSI reporting configuration based on the capability information of the UE 115.

[0124] The capabilities may include a first capability and a second capability corresponding to different timing gaps or durations between different signaling or measurements for aperiodic CSI reporting. Based on the capabilities of the UE 115, the network entity 105 may configure the timing gaps for aperiodic CSI reporting for time domain beam prediction. For example, the network entity 105 may configure the timing gap 320-a based on the first capability and configure the timing gap 325-a based on the second capability. The timing gap may correspond to the period between the UE being triggered to generate and report the aperiodic CSI report, such as a threshold time difference between the time slot 305 in which the aperiodic CSI report is triggered, the report transmission start symbol 310, and the future time instance 315-a.

[0125] The timing gap 320-a may correspond to a threshold time difference (e.g., a minimum difference) between the time slot 305 or the first symbol of the time slot 305 in which the aperiodic CSI is triggered and the start symbol of the time slot in which the aperiodic CSI report carrying the predicted measurement is sent. For example, the UE 115 may report a first capability indicating a minimum distance between the symbol in which the aperiodic CSI report is triggered and the start symbol in which the aperiodic CSI report is sent. The UE 115 may generate a prediction between triggering the aperiodic CSI report and sending the aperiodic CSI report and encapsulate the prediction into the aperiodic CSI report. The UE 115 may send information indicating a first capability for indicating a minimum amount of time for the UE 115 to prepare an aperiodic CSI report with the predicted measurement.

[0126] The network entity 105 may schedule the UE 115 for aperiodic CSI reporting for time domain beam prediction based on the capability. For example, when the network entity 105 triggers aperiodic CSI reporting for time domain beam prediction at the UE 115, the network entity may schedule the aperiodic CSI reporting with at least a minimum time gap between a symbol in which the aperiodic CSI reporting is triggered and a start symbol in which the aperiodic CSI reporting is sent.

[0127] The timing gap 325-a may correspond to a threshold difference (e.g., a maximum difference) between the time slot in which the aperiodic CSI report is triggered and the future time instance 315-a signaled by the network entity 105. In some examples, the timing gap 325-a may be based on a start or end time domain point of the future time domain window signaled by the network entity 105. In some examples, the timing gap 325-a may be based on the time slot in which the aperiodic CSI report is sent (e.g., in addition to or instead of the time slot in which the aperiodic CSI report is triggered).

[0128] UE 115 may perform prediction for a future time instance 315-a, but the quality of the prediction for the future time instance 315-a may be based on how far in the future the future time instance 315-a is. For example, UE 115 may be able to generate a higher quality prediction for a time instance closer to when UE 115 generates the prediction. If the prediction is too far in the future, UE 115 may not be able to generate a reliable prediction. Therefore, UE 115 may indicate a second capability that limits the scope of the prediction (e.g., in time). When network entity 105 schedules or configures UE 115 for aperiodic CSI for time domain beam prediction, network entity 105 may configure aperiodic CSI according to the second capability. For example, UE 115 may be scheduled to perform prediction in a case where there is a maximum time difference between triggering an aperiodic CSI report (or sending an aperiodic CSI report) and a future time instance. In some examples, UE 115 may not expect to be configured with an aperiodic CSI scheduling timeline that exceeds the capability indicated by UE 115.

[0129] UE 115 may report multiple combined pairs of the first capability and the second capability. For example, UE 115 may indicate a first set of capability parameters including a shorter duration for the first capability and a longer duration for the second capability and a second set of capability parameters including a longer duration for the first capability and a shorter duration for the second capability. In some examples, the timeline capabilities may be preconfigured, such as preconfigured or predefined for a wireless communication system including UE 115, and UE 115 may be configured with CSI reporting settings according to the predefined timeline capabilities.

[0130] In some examples, the UE may report capabilities based on the number of resources associated with the CSI report. For example, the UE may report different capabilities for different numbers of CMRs / IMRs associated with the CSI report or based on the number of SSBRIs / CRIs to be addressed in the CSI report. For example, the UE 115 may indicate the ability to support predictions up to a time threshold after an aperiodic CSI trigger (or a time slot carrying an aperiodic CSI report) based on the number of CMRs associated with the CSI report. For example, if the total number of CMRs is small (e.g., 4, 8), the threshold may be a longer time (e.g., 200ms). In another example, if the total number of CMRs is large (e.g., 64), the threshold may be a relatively short time (e.g., 40ms). Similarly, the UE may report different capabilities or thresholds for different numbers of reported reference signals. For example, if the number of reported reference signals associated with the CSI report is 4, the UE may support predictions up to 200ms later than the trigger for the aperiodic CSI report. The UE may support prediction up to 40 ms later than the trigger for aperiodic CSI reporting if the number of reported reference signals associated with the CSI report is 64. In some cases, such as if the UE 115 is preconfigured with a capability for predictive CSI reporting or a threshold for predictive CSI reporting, the timeline for predictive CSI reporting may similarly be based on the number of CMRs or IMRs associated with the CSI report or the number of reported reference signals associated with the CSI report, or both.

[0131] Timeline 301 corresponds to periodic CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure. In some examples, network entity 105 may configure UE 115 to send periodic CSI reports including measurement predictions according to timeline 301 based on the UE's reported capabilities.

[0132] Timing gap 335 may correspond to a time between time slot 330, or a first symbol of time slot 330, in which a periodic CSI report is sent, and a start of future time instance 315-b. Future time instances may be defined based on timing gap 335. For example, future time instance 315-b, or a time instance for which UE 115 predicts CSI measurements, may be configured or defined based on a time difference between time slot 330, in which a periodic CSI report is sent, and a time slot in which future time instance 315-b is captured or in which future time instance 315-b starts.

[0133] UE 115 may report a capability indicating a time domain difference threshold (e.g., a maximum time domain difference) for timing slot 335. For example, UE 115 may support generating CSI predictions for time instances that are separated in time from time slot 330 by up to the indicated time domain difference threshold.

[0134] Similar to the techniques described herein for aperiodic CSI reporting, the network entity 105 may configure one or more parameters (e.g., via CSI reporting settings) to the UE 115 for predictive periodic CSI reporting via RRC messages or RRC configurations. For example, the network entity 105 may send an RRC message to configure parameters to the UE 115 for periodic CSI reporting for time-domain beam prediction. The network entity 105 may configure one or more CSI reporting settings for periodic CSI reporting associated with beam prediction.

[0135] Timeline 302 corresponds to a semi-persistent CSI report carrying time domain beam prediction according to one or more aspects of the present disclosure. In some examples, network entity 105 may configure UE 115 to send a semi-persistent CSI report including measurement prediction according to timeline 301 based on the UE's reported capabilities.

[0136] The timing gap 320 - b may correspond to the time difference between the time slot 340 or the first symbol of the time slot 340 in which the semi-persistent CSI report is activated and the first symbol of the time slot 340 or the time slot 345 in which the predictive semi-persistent CSI report including the predicted CSI measurement is sent.

[0137] The timing gap 325-b may be based on the time difference between the time slot 340 in which the activation message is received and the time slot in which the future time instance 315-c is captured or started. In some examples, the future time instance 315-c of the semi-persistent CSI report for time domain beam prediction may be configured or defined based on the timing gap 325-b.

[0138] The UE 115 may report thresholds, such as minimum and maximum values, respectively, for the timing gap 320-b and the timing gap 325-b. The network entity 105 may send control signaling to configure one or more CSI reporting settings for semi-persistent CSI reporting for CSI measurement prediction based on the capabilities of the UE, wherein the timing gaps for the one or more CSI reports are within the indicated threshold capabilities of the UE.

[0139] For example, the network entity 105 may configure parameters for semi-persistent CSI reporting for beam prediction via one or more CSI report settings via an activation message (e.g., a MAC control element) that activates semi-persistent CSI reporting. In some examples, the CSI report may be based on a hybrid indication of joint parameters from the CSI report settings and the activation message. For example, the CSI report settings may indicate whether the report quantity is about historical measurements or predicted future channel characteristics (e.g., via a flag of an information element of the CSI report settings). The semi-persistent CSI reporting activation MAC-CE may indicate additional parameters or information about future time instances 315-c.

[0140] Figure 4 An example of a process flow 400 for supporting techniques for dynamically triggered CSI reporting with time domain beam prediction in accordance with one or more aspects of the present disclosure is illustrated. The process flow 400 describes communications between a network entity 105-b and a UE 115-b, which may be as described herein with reference to Figure 1 Corresponding examples of network entity 105 and UE 115 are described.

[0141] At 405, the UE 115-b may send a capability message to the network entity 105-b. The capability message may indicate a capability of the UE 115-b to perform beam prediction, wherein predicted CSI measurements for a set of beams are based on the capability message.

[0142] In some examples, the capability message may indicate one or more time slots supported by UE 115-b. For example, the capability message may indicate a first supported time domain slot between a first time slot in which a second control message (e.g., a CSI request that triggers aperiodic CSI reporting or activates semi-persistent CSI reporting) is received and a start symbol or an end symbol for a predicted CSI measurement. Additionally or alternatively, the capability message may indicate a second supported time domain slot between a first time slot in which the second control message is received and a second time slot in which the CSI report is sent. Additionally or alternatively, the capability message may indicate a third supported time domain slot between a first symbol in which the CSI report is sent and a start symbol for a predicted CSI measurement.

[0143] For example, for aperiodic CSI reporting for time domain beam prediction, the capability message may indicate one or more values ​​for a first supported time domain slot and one or more values ​​for a second time domain slot. Additionally or alternatively, for periodic CSI reporting, the capability message may indicate one or more values ​​for a third time domain slot. Additionally or alternatively, for semi-persistent CSI reporting, the capability message may indicate one or more values ​​for a first supported time domain slot and one or more values ​​for a second supported time domain slot.

[0144] In some examples, the capability message may indicate one or more values ​​for a first supported time domain gap, a second supported time domain gap, a third supported time domain gap, or any combination thereof. The capability message may indicate a first capability of UE 115-b to perform beam prediction based on a first number of measurement resources or a first number of reported reference signals, and may indicate a second capability of UE 115-b to perform beam prediction based on a second number of measurement resources or a second number of reported reference signals. For example, UE 115-b may support different durations for a first time domain gap, a second time domain gap, or a third time domain gap based on the number of measurement resources or the number of reported reference signals for CSI reporting.

[0145] At 410, network entity 105-b may send a first control message to UE 115-b. The first control message may be based on the capability message or the capabilities of UE 115-b. The first control message may indicate one or more parameter sets for beam prediction via a predictive CSI report. For example, the first control message may configure one or more CSI report settings at UE 115-b for a CSI report that is used to convey a predicted CSI measurement. In some examples, the first control message may configure the CSI report settings for one or more aperiodic CSI reports, periodic CSI reports, semi-persistent CSI reports, or any combination thereof.

[0146] In some examples, the control message may indicate, for each of the one or more parameter sets, a time gap between the second control message and a future instance or future window for predicted CSI measurement for the set of beams. For example, the control message may indicate, for each of the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for predicted CSI measurement for the set of beams. In some examples, the first control message may indicate one or more parameter sets and a second set of the parameter sets, wherein the one or more parameter sets are associated with CSI prediction and the second set of the parameter sets is associated with historical CSI measurement.

[0147] At 415, the network entity 105-b may send a trigger message to the UE 115-b. The trigger message, which may be a second control message, may trigger the UE 115-b to send a CSI report at 420. The trigger message or the second control message may request the UE 115-b to send a CSI report that indicates a predicted CSI measurement based on a parameter set in one or more parameter sets.

[0148] The trigger message may be a DCI message that triggers an aperiodic CSI report based on a parameter set, wherein the aperiodic CSI report is a CSI report. In some examples, the trigger message may be a MAC message that activates a semi-persistent CSI report based on a parameter set, wherein the semi-persistent CSI report is a CSI report.

[0149] UE 115-b may receive a trigger message (eg, a second control message) based on the RNTI associated with the CSI prediction. A field of the second control message may indicate one or more parameter sets associated with the CSI prediction.

[0150] At 420, the UE 115-b may predict beam measurements based on the control message and the trigger message. The UE 115-b may predict CSI measurements for a set of beams at a future time instance, during a future time window, or during a future scheduled transmission opportunity associated with one or more channel measurement resources or one or more interference measurement resources.

[0151] At 425, UE 115-b may send a CSI report to network entity 105-a. UE 115-b may send a CSI report in response to a trigger message (e.g., a second control message) that indicates a predicted CSI measurement for the set of beams based on the parameter set. The CSI report may indicate a future instance or future window for the predicted CSI measurement for the set of beams.

[0152] Figure 5 A block diagram 500 of a device 505 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor (not shown). Each of these components may communicate with each other (e.g., via one or more buses).

[0153] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for carrying dynamically triggered CSI reports for time domain beam prediction). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0154] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for carrying dynamically triggered CSI reports for time-domain beam prediction). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0155] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0156] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0157] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0158] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0159] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. For example, the communication manager 520 may be configured to or otherwise support components for receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The communication manager 520 may be configured to or otherwise support components for receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The communication manager 520 may be configured to or otherwise support components for sending a CSI report indicating a predicted CSI measurement for a set of beams based on a parameter set in response to the second control message.

[0160] By including or configuring a communication manager 520 according to the examples described herein, the device 505 (e.g., a processor that controls or otherwise couples with the receiver 510, the transmitter 515, the communication manager 520, or any combination thereof) may support techniques for dynamically triggered CSI reports that carry time domain beam predictions, which may improve the reliability of beam predictions and beam management based on beam predictions. For example, if the network-side beam prediction has a low confidence level, these techniques may support dynamically triggering the UE to provide additional measurement predictions via CSI reports, which may improve the confidence of prediction-based beam management at the network. Prediction-based beam management may use less resource overhead and power consumption than measurement-based beam management, as well as reduce latency and improve throughput by predicting future beam blocking or failures. Therefore, by increasing reliability or confidence in beam management based on beam predictions, the device 505 may experience reduced resource overhead and power consumption as well as reduced latency and improved throughput.

[0161] Figure 6A block diagram 600 of a device 605 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor (not shown). Each of these components may communicate with each other (e.g., via one or more buses).

[0162] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for carrying dynamically triggered CSI reports for time domain beam prediction). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0163] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for carrying dynamically triggered CSI reports for time-domain beam prediction). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0164] The device 605 or its various components may be examples of components for performing various aspects of the technology for dynamically triggered CSI reporting carrying time domain beam prediction as described herein. For example, the communication manager 620 may include a parameter set configuration component 625, a CSI request component 630, a CSI reporting component 635, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0165] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. The parameter set configuration component 625 may be configured to or otherwise support components for receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The CSI request component 630 may be configured to or otherwise support components for receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The CSI reporting component 635 may be configured to or otherwise support components for sending a CSI report indicating a predicted CSI measurement for a set of beams based on the parameter set in response to the second control message.

[0166] Figure 7 A block diagram 700 of a communication manager 720 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein. For example, the communication manager 720 may include a parameter set configuration component 725, a CSI request component 730, a CSI reporting component 735, a capability message component 740, a measurement prediction component 745, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0167] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The parameter set configuration component 725 may be configured to or otherwise support components for receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The CSI request component 730 may be configured to or otherwise support components for receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The CSI reporting component 735 may be configured to or otherwise support components for sending a CSI report indicating a predicted CSI measurement for a set of beams based on the parameter set in response to the second control message.

[0168] In some examples, capability message component 740 may be configured as or otherwise support components for sending a capability message indicating the UE's ability to perform beam prediction, wherein predicted CSI measurements for a set of beams are based at least in part on the capability message.

[0169] In some examples, the capability message indicates a first supported time domain gap between a first time slot in which a second control message is received and a start symbol or an end symbol for a predicted CSI measurement, a second supported time domain gap between a first time slot in which the second control message is received and a second time slot in which a CSI report is sent, a third supported time domain gap between a first symbol in which a CSI report is sent and a start symbol for a predicted CSI measurement, or any combination thereof.

[0170] In some examples, the capability message indicates one or more values ​​for a first supported time domain gap, a second supported time domain gap, or a third supported time domain gap, or any combination thereof.

[0171] In some examples, the capability message indicates a first capability of the UE to perform beam prediction based on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform beam prediction based on a second number of measured resources or a second number of reported reference signals.

[0172] In some examples, to support receiving a first control message, the parameter set configuration component 725 may be configured as or otherwise support components for receiving a first control message indicating, for each parameter set in one or more parameter sets, a time gap between a second control message and a future instance or future window of predicted CSI measurements for a set of beams.

[0173] In some examples, to support receiving a first control message, the parameter set configuration component 725 may be configured as or otherwise support components for receiving a first control message indicating, for each parameter set in one or more parameter sets, a time gap between a second control message and a future transmission opportunity for a predicted CSI measurement for a set of beams.

[0174] In some examples, to support sending CSI reports, CSI reporting component 735 may be configured as or otherwise support components for sending CSI reports indicating future instances or future windows of predicted CSI measurements for a set of beams.

[0175] In some examples, the measurement prediction component 745 may be configured as or otherwise support components for predicting CSI measurements for a set of beams at future time instances, during future time windows, or during future scheduled transmission opportunities associated with one or more channel measurement resources or one or more interference measurement resources.

[0176] In some examples, to support receiving the second control message, CSI request component 730 may be configured or otherwise support means for receiving a DCI message that triggers an aperiodic CSI report based on a parameter set, where the aperiodic CSI report is a CSI report.

[0177] In some examples, to support receiving a second control message, CSI request component 730 may be configured or otherwise support components for receiving a medium access control message that activates a semi-persistent CSI report based on a parameter set, where the semi-persistent CSI report is a CSI report.

[0178] In some examples, to support receiving a first control message, parameter set configuration component 725 may be configured as or otherwise support components for receiving a first control message indicating one or more parameter sets and a second set of parameter sets, wherein the one or more parameter sets are associated with CSI predictions and the second set of parameter sets is associated with historical channel state information measurements.

[0179] In some examples, to support receiving the second control message, CSI request component 730 may be configured or otherwise support means for receiving the second control message based on a radio network temporary identifier associated with the CSI prediction.

[0180] In some examples, a field of the second control message indicating one or more parameter sets is associated with CSI prediction.

[0181] Figure 8 A diagram of a system 800 including a device 805 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending communications and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0182] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor, such as processor 840. In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0183] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired or wireless link, as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

[0184] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 830 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0185] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks of supporting techniques for dynamically triggered CSI reports carrying time-domain beam prediction). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0186] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support components for receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The communication manager 820 may be configured to or otherwise support components for receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The communication manager 820 may be configured to or otherwise support components for sending a CSI report indicating a predicted CSI measurement for a set of beams based on a parameter set in response to the second control message.

[0187] By including or configuring a communication manager 820 according to the examples described herein, the device 805 may support techniques for dynamically triggered CSI reports carrying time domain beam predictions, which may result in improved communication reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power, among other advantages.

[0188] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0189] Fig. 9 A block diagram 900 of a device 905 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor (not shown). Each of these components may communicate with each other (e.g., via one or more buses).

[0190] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0191] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0192] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0193] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0194] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0195] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0196] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support components for sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The communication manager 920 may be configured to or otherwise support components for sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The communication manager 920 may be configured to or otherwise support components for receiving a CSI report indicating a predicted CSI measurement for a set of beams based on a parameter set in response to the second control message.

[0197] By including or configuring a communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or otherwise coupled thereto) may support techniques for dynamically triggered CSI reports carrying time-domain beam predictions, which may result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0198] Fig.10 A block diagram 1000 of a device 1005 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor (not shown). Each of these components may communicate with each other (e.g., via one or more buses).

[0199] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0200] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0201] The device 1005 or its various components may be examples of components for performing various aspects of the technology for dynamically triggered CSI reporting carrying time domain beam prediction as described herein. For example, the communication manager 1020 may include a parameter set configuration component 1025, a CSI request component 1030, a CSI reporting component 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0202] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The parameter set configuration component 1025 may be configured to or otherwise support components for sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The CSI request component 1030 may be configured to or otherwise support components for sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The CSI reporting component 1035 may be configured to or otherwise support components for receiving a CSI report indicating a predicted CSI measurement for a set of beams based on the parameter set in response to the second control message.

[0203] Fig.11 A block diagram 1100 of a communication manager 1120 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein. For example, the communication manager 1120 may include a parameter set configuration component 1125, a CSI request component 1130, a CSI report component 1135, a capability message component 1140, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0204] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The parameter set configuration component 1125 may be configured to or otherwise support components for sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The CSI request component 1130 may be configured to or otherwise support components for sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The CSI reporting component 1135 may be configured to or otherwise support components for receiving a CSI report indicating a predicted CSI measurement for a set of beams based on a parameter set in response to the second control message.

[0205] In some examples, capability message component 1140 may be configured to or otherwise support components for receiving a capability message indicating the UE's ability to perform beam prediction, wherein predicted CSI measurements for a set of beams are based on the capability message.

[0206] In some examples, the capability message indicates a first supported time domain gap between a first time slot in which a second control message is received and a start symbol or an end symbol for a predicted CSI measurement, a second supported time domain gap between a first time slot in which the second control message is received and a second time slot in which a CSI report is sent, a third supported time domain gap between a first symbol in which a CSI report is sent and a start symbol for a predicted CSI measurement, or any combination thereof.

[0207] In some examples, the capability message indicates one or more values ​​for a first supported time domain gap, a second supported time domain gap, or a third supported time domain gap, or any combination thereof.

[0208] In some examples, the capability message indicates a first capability of the UE to perform beam prediction based on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform beam prediction based on a second number of measured resources or a second number of reported reference signals.

[0209] In some examples, to support sending a first control message, parameter set configuration component 1125 may be configured as or otherwise support components for sending a first control message indicating, for each parameter set in one or more parameter sets, a time gap between a second control message and a future instance or future window of predicted CSI measurements for a set of beams.

[0210] In some examples, to support sending a first control message, parameter set configuration component 1125 may be configured as or otherwise support components for sending a first control message indicating, for each parameter set in one or more parameter sets, a time gap between a second control message and a future transmission opportunity for a predicted CSI measurement for a set of beams.

[0211] In some examples, to support receiving CSI reports, CSI reporting component 1135 may be configured as or otherwise support components for receiving CSI reports indicating future instances or future windows of predicted CSI measurements for a set of beams.

[0212] In some examples, the predicted CSI measurements for a set of beams correspond to a future time instance, a future time window period, or a future scheduled transmission opportunity period associated with one or more channel measurement resources or one or more interference measurement resources.

[0213] In some examples, to support sending the second control message, CSI request component 1130 may be configured or otherwise support components for sending a DCI message that triggers an aperiodic CSI report based on a parameter set, where the aperiodic CSI report is a CSI report.

[0214] In some examples, to support sending a second control message, CSI request component 1130 may be configured or otherwise support components for sending a medium access control message that activates a semi-persistent CSI report based on a parameter set, where the semi-persistent CSI report is a CSI report.

[0215] In some examples, to support sending a first control message, parameter set configuration component 1125 may be configured as or otherwise support components for sending a first control message indicating one or more parameter sets and a second set of parameter sets, wherein the one or more parameter sets are associated with CSI predictions and the second set of parameter sets is associated with historical CSI measurements.

[0216] In some examples, to support sending the second control message, CSI requesting component 1130 may be configured or otherwise support means for sending the second control message using a radio network temporary identifier associated with the CSI prediction.

[0217] In some examples, a field of the second control message indicating one or more parameter sets is associated with CSI prediction.

[0218] Fig.12A diagram of a system 1200 including a device 1205 supporting techniques for dynamically triggered CSI reporting carrying time-domain beam prediction in accordance with one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0219] As described herein, the transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating a signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or any combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components that are operable to: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235, or memory 1225, or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0220] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1225 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0221] Processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting techniques for dynamically triggered CSI reports carrying time-domain beam prediction). For example, device 1205 or a component of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, the processor 1235 and memory 1225 being configured to perform the various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing the functions of the device 1205 (e.g., by executing the code 1230). The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as in the memory 1225). In some specific implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components (e.g., the device 1205)). For example, the processing system of the device 1205 may refer to a system including various other components or subcomponents of the device 1205, such as the processor 1235, or the transceiver 1210, or the communication manager 1220, or other components or combinations of components of the device 1205. The processing system of device 1205 may interface with other components of device 1205 and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1205 can send information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system and a receiver of a chip or modem, such that the device 1205 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0222] In some examples, bus 1240 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1205, or communications performed between different components of device 1205 that may be co-located or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

[0223] In some examples, the communication manager 1220 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1220 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0224] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support components for sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The communication manager 1220 may be configured to or otherwise support components for sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based on a parameter set in one or more parameter sets. The communication manager 1220 may be configured to or otherwise support components for receiving a CSI report indicating a predicted CSI measurement for a set of beams based on a parameter set in response to the second control message.

[0225] By including or configuring a communications manager 1220 according to examples as described herein, the device 1205 may support techniques for dynamically triggered CSI reporting that carries time domain beam predictions, which may result in improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communications resources, improved coordination between devices, longer battery life, and improved utilization of processing power, among other advantages.

[0226] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of the techniques for dynamically triggered CSI reporting carrying time-domain beam prediction as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0227] Fig.13 A flow chart illustrating a method 1300 for supporting a technique for dynamically triggered CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0228] At 1305, the method may include receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described parameter set configures component 725 to execute.

[0229] At 1310, the method may include receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in one or more parameter sets. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The described CSI request component 730 is performed.

[0230] At 1315, the method may include sending, in response to the second control message, a CSI report indicating a predicted CSI measurement for a set of beams based at least in part on the set of parameters. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The described CSI reporting component 735 is performed.

[0231] Fig.14 A flow chart illustrating a method 1400 for supporting a technique for dynamically triggered CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0232] At 1405, the method may include sending a capability message indicating the UE's capability to perform beam prediction, wherein the predicted CSI measurement for the set of beams is based at least in part on the capability message. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described capability message component 740 is executed.

[0233] At 1410, the method may include receiving a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The described parameter set configures component 725 to execute.

[0234] At 1415, the method may include receiving a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in one or more parameter sets. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The described CSI request component 730 is performed.

[0235] At 1420, the method may include sending, in response to the second control message, a CSI report indicating a predicted CSI measurement for a set of beams based at least in part on the set of parameters. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The described CSI reporting component 735 is performed.

[0236] Fig.15 A flow chart illustrating a method 1500 for supporting a technique for dynamically triggered CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 and Figures 9 to 12 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0237] At 1505, the method may include sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The described parameter set configures component 1125 to execute.

[0238] At 1510, the method may include sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in one or more parameter sets. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The described CSI request component 1130 is performed.

[0239] At 1515, the method may include receiving, in response to the second control message, a CSI report indicating a predicted CSI measurement for a set of beams based at least in part on the set of parameters. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The described CSI reporting component 1135 is performed.

[0240] Fig.16 A flow chart illustrating a method 1600 for supporting a technique for dynamically triggered CSI reporting carrying time domain beam prediction according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 and Figures 9 to 12 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0241] At 1605, the method may include receiving a capability message indicating the UE's capability to perform beam prediction, wherein the predicted CSI measurement for the set of beams is based at least in part on the capability message. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described capability message component 1140 is executed.

[0242] At 1610, the method may include sending a first control message indicating one or more parameter sets for beam prediction via a predictive CSI report. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The described parameter collection component 1125 is performed.

[0243] At 1615, the method may include sending a second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in one or more parameter sets. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The described CSI request component 1130 is performed.

[0244] At 1620, the method may include receiving, in response to the second control message, a CSI report indicating a predicted CSI measurement for a set of beams based at least in part on the set of parameters. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.11 The described CSI reporting component 1135 is performed.

[0245] The following provides an overview of various aspects of the disclosure:

[0246] Aspect 1: A method for wireless communication at a UE, comprising: receiving a first control message, the first control message indicating one or more parameter sets for beam prediction via a predictive CSI report; receiving a second control message, the second control message requesting the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in the one or more parameter sets; and sending the CSI report indicating the predicted CSI measurement for a set of beams based at least in part on the parameter set in response to the second control message.

[0247] Aspect 2: The method according to Aspect 1 also includes: sending a capability message indicating the UE's ability to perform the beam prediction, wherein the predicted CSI measurement for the set of beams is at least partially based on the capability message.

[0248] Aspect 3: A method according to Aspect 2, wherein the capability message indicates a first supported time domain gap between a first time slot in which the second control message is received and a start symbol or an end symbol for the predicted CSI measurement, a second supported time domain gap between the first time slot in which the second control message is received and a second time slot in which the CSI report is sent, a third supported time domain gap between a first symbol in which the CSI report is sent and the start symbol for the predicted CSI measurement, or any combination thereof.

[0249] Aspect 4: The method according to aspect 3, wherein the capability message indicates one or more values ​​for the first supported time domain gap, the second supported time domain gap, or the third supported time domain gap, or any combination thereof.

[0250] Aspect 5: A method according to any one of Aspects 2 to 4, wherein the capability message indicates a first capability of the UE to perform the beam prediction based at least in part on a first number of measurement resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based at least in part on a second number of measurement resources or a second number of reported reference signals.

[0251] Aspect 6: A method according to any one of Aspects 1 to 5, wherein receiving the first control message includes: receiving the first control message indicating, for each parameter set in the one or more parameter sets, a time gap between the second control message and a future instance or future window for the predicted CSI measurement for the set of beams.

[0252] Aspect 7: A method according to any one of Aspects 1 to 6, wherein receiving the first control message includes: receiving the first control message indicating, for each parameter set in the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted CSI measurement for the set of beams.

[0253] Aspect 8: The method according to any one of Aspects 1 to 7, wherein sending the CSI report comprises: sending the CSI report indicating a future instance or a future window of the predicted CSI measurement for the set of beams.

[0254] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: predicting CSI measurements for the set of beams at a future time instance, during a future time window, or during a future scheduled transmission opportunity associated with one or more channel measurement resources or one or more interference measurement resources.

[0255] Aspect 10: A method according to any one of Aspects 1 to 9, wherein receiving the second control message includes: receiving a downlink control information message that triggers a non-periodic CSI report based at least in part on the parameter set, wherein the non-periodic CSI report is the CSI report.

[0256] Aspect 11: A method according to any one of Aspects 1 to 10, wherein receiving the second control message includes: receiving a medium access control message that activates a semi-persistent CSI report based at least in part on the parameter set, wherein the semi-persistent CSI report is the CSI report.

[0257] Aspect 12: A method according to any one of Aspects 1 to 11, wherein receiving the first control message includes: receiving the first control message indicating the one or more parameter sets and a second set in the parameter sets, wherein the one or more parameter sets are associated with CSI prediction, and the second set in the parameter set is associated with historical CSI measurements.

[0258] Aspect 13: The method according to any one of aspects 1 to 12, wherein receiving the second control message comprises: receiving the second control message based at least in part on a radio network temporary identifier associated with the CSI prediction.

[0259] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the field of the second control message indicating the one or more parameter sets is associated with CSI prediction.

[0260] Aspect 15: A method for wireless communication at a network entity, comprising: sending a first control message, wherein the first control message indicates one or more parameter sets for beam prediction via a predictive CSI report; sending a second control message, wherein the second control message requests the UE to send a CSI report indicating a predicted CSI measurement based at least in part on a parameter set in the one or more parameter sets; and receiving, in response to the second control message, the CSI report indicating the predicted CSI measurement for a set of beams based at least in part on the parameter set.

[0261] Aspect 16: The method according to Aspect 15 also includes: receiving a capability message indicating the UE's ability to perform the beam prediction, wherein the predicted CSI measurement for the set of beams is at least partially based on the capability message.

[0262] Aspect 17: A method according to Aspect 16, wherein the capability message indicates a first supported time domain gap between a first time slot in which the second control message is received and a start symbol or an end symbol for the predicted CSI measurement, a second supported time domain gap between the first time slot in which the second control message is received and a second time slot in which the CSI report is sent, a third supported time domain gap between a first symbol in which the CSI report is sent and the start symbol for the predicted CSI measurement, or any combination thereof.

[0263] Aspect 18: The method according to aspect 17, wherein the capability message indicates one or more values ​​for the first supported time domain gap, the second supported time domain gap, or the third supported time domain gap, or any combination thereof.

[0264] Aspect 19: A method according to any one of Aspects 16 to 18, wherein the capability message indicates a first capability of the UE to perform the beam prediction based at least in part on a first number of measurement resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based at least in part on a second number of measurement resources or a second number of reported reference signals.

[0265] Aspect 20: A method according to any one of Aspects 15 to 19, wherein sending the first control message includes: sending the first control message indicating, for each parameter set in the one or more parameter sets, a time gap between the second control message and a future instance or future window of the predicted CSI measurement for the set of beams.

[0266] Aspect 21: A method according to any one of Aspects 15 to 20, wherein sending the first control message includes: sending the first control message indicating, for each parameter set in the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted CSI measurement for the set of beams.

[0267] Aspect 22: The method according to any one of Aspects 15 to 21, wherein receiving the CSI report comprises: receiving the CSI report indicating a future instance or a future window of the predicted CSI measurement for the set of beams.

[0268] Aspect 23: A method according to any one of Aspects 15 to 22, wherein the predicted CSI measurement for the set of beams corresponds to a future time instance, a future time window period, or a future scheduled transmission opportunity period associated with one or more channel measurement resources or one or more interference measurement resources.

[0269] Aspect 24: A method according to any one of Aspects 15 to 23, wherein sending the second control message includes: sending a downlink control information message that triggers a non-periodic CSI report based at least in part on the parameter set, wherein the non-periodic CSI report is the CSI report.

[0270] Aspect 25: A method according to any one of Aspects 15 to 24, wherein sending the second control message includes: sending a medium access control message that activates a semi-persistent CSI report based at least in part on the parameter set, wherein the semi-persistent CSI report is the CSI report.

[0271] Aspect 26: A method according to any one of Aspects 15 to 25, wherein sending the first control message includes: sending the first control message indicating the one or more parameter sets and a second set in the parameter sets, wherein the one or more parameter sets are associated with CSI prediction, and the second set in the parameter set is associated with historical CSI measurements.

[0272] Aspect 27: The method according to any one of aspects 15 to 26, wherein sending the second control message comprises sending the second control message using a radio network temporary identifier associated with a CSI prediction.

[0273] Aspect 28: The method according to any one of aspects 15 to 27, wherein the field of the second control message indicating the one or more parameter sets is associated with CSI prediction.

[0274] Aspect 29: An apparatus for performing wireless communications at a UE, comprising: a processor; and a memory, the memory being coupled to the processor, the memory storing instructions, the instructions being executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 14.

[0275] Aspect 30: An apparatus for wireless communication at a UE, comprising: at least one component for performing a method according to any one of aspects 1 to 14.

[0276] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 14.

[0277] Aspect 32: An apparatus for performing wireless communications at a network entity, comprising: a processor; and a memory, the memory being coupled to the processor, the memory storing instructions, the instructions being executable by the processor to cause the apparatus to perform a method according to any one of Aspects 15 to 28.

[0278] Aspect 33: An apparatus for wireless communication at a network entity, comprising: at least one component for performing a method according to any one of aspects 15 to 28.

[0279] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 15 to 28.

[0280] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0281] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0282] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0283] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0284] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0285] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0286] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0287] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Also, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0288] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0289] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0290] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving a first control message indicating one or more sets of parameters for beam prediction via a predictive channel state information report; receiving a second control message requesting the UE to send a channel state information report indicating a predicted channel state information measurement based at least in part on a set of parameters in the one or more sets of parameters; as well as The channel state information report indicating the predicted channel state information measurement for a set of beams based at least in part on the set of parameters is sent in response to the second control message.

2. The method according to claim 1, further comprising: A capability message is sent indicating the capability of the UE to perform the beam prediction, wherein the predicted channel state information measurement for the set of beams is based at least in part on the capability message.

3. The method of claim 2, wherein the capability message indicates a first supported time domain gap between a first time slot in which the second control message is received and a start symbol or an end symbol for the predicted channel state information measurement, a second supported time domain gap between the first time slot in which the second control message is received and a second time slot in which the channel state information report is sent, a third supported time domain gap between a first symbol in which the channel state information report is sent and the start symbol for the predicted channel state information measurement, or any combination thereof.

4. The method of claim 3, wherein the capability message indicates one or more values ​​for the first supported time domain gap, the second supported time domain gap, or the third supported time domain gap, or any combination thereof.

5. A method according to claim 2, wherein the capability message indicates a first capability of the UE to perform the beam prediction based at least in part on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based at least in part on a second number of measured resources or a second number of reported reference signals.

6. The method of claim 1 , wherein receiving the first control message comprises: The first control message is received indicating, for each of the one or more parameter sets, a time gap between the second control message and a future instance or future window for the predicted channel state information measurement for the set of beams.

7. The method of claim 1 , wherein receiving the first control message comprises: The first control message is received indicating, for each of the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted channel state information measurement for the set of beams.

8. The method of claim 1, wherein sending the channel state information report comprises: The channel state information report is sent indicating a future instance or future window of the predicted channel state information measurement for the set of beams.

9. The method according to claim 1, further comprising: Channel state information measurements are predicted for the set of beams at a future time instance, during a future time window, or during a future scheduled transmission opportunity associated with one or more channel measurement resources or one or more interference measurement resources.

10. The method of claim 1, wherein receiving the second control message comprises: A downlink control information message is received that triggers an aperiodic channel state information report based at least in part on the set of parameters, wherein the aperiodic channel state information report is the channel state information report.

11. The method of claim 1 , wherein receiving the second control message comprises: A medium access control message is received that activates a semi-persistent channel state information report based at least in part on the set of parameters, wherein the semi-persistent channel state information report is the channel state information report.

12. The method of claim 1 , wherein receiving the first control message comprises: The first control message is received indicating the one or more sets of parameters and a second set of parameter sets, wherein the one or more sets of parameters are associated with channel state information prediction and the second set of parameter sets is associated with historical channel state information measurements.

13. The method of claim 1 , wherein receiving the second control message comprises: The second control message is received based at least in part on a radio network temporary identifier associated with a channel state information prediction.

14. The method of claim 1, wherein the field of the second control message indicating the one or more parameter sets is associated with channel state information prediction.

15. A method for wireless communication at a network entity, comprising: sending a first control message, the first control message indicating one or more sets of parameters for beam prediction via a predictive channel state information report; sending a second control message requesting a user equipment (UE) to send a channel state information report indicating a predicted channel state information measurement based at least in part on a set of parameters in the one or more sets of parameters; as well as The channel state information report indicating the predicted channel state information measurements for a set of beams based at least in part on the set of parameters is received in response to the second control message.

16. The method according to claim 15, further comprising: Receiving a capability message indicating the capability of the UE to perform the beam prediction, wherein the predicted channel state information measurement for the set of beams is based at least in part on the capability message.

17. A method according to claim 16, wherein the capability message indicates a first supported time domain gap between a first time slot in which the second control message is sent and a start symbol or an end symbol for the predicted channel state information measurement, a second supported time domain gap between the first time slot in which the second control message is sent and a second time slot in which the channel state information report is received, a third supported time domain gap between a first symbol in which the channel state information report is received and the start symbol for the predicted channel state information measurement, or any combination thereof.

18. The method of claim 17, wherein the capability message indicates one or more values ​​for the first supported time domain gap, the second supported time domain gap, or the third supported time domain gap, or any combination thereof.

19. A method according to claim 16, wherein the capability message indicates a first capability of the UE to perform the beam prediction based at least in part on a first number of measured resources or a first number of reported reference signals, and a second capability of the UE to perform the beam prediction based at least in part on a second number of measured resources or a second number of reported reference signals.

20. The method of claim 15, wherein sending the first control message comprises: The first control message is sent indicating, for each of the one or more parameter sets, a time gap between the second control message and a future instance or future window for the predicted channel state information measurement for the set of beams.

21. The method of claim 15, wherein sending the first control message comprises: The first control message is sent indicating, for each of the one or more parameter sets, a time gap between the second control message and a future transmission opportunity for the predicted channel state information measurement for the set of beams.

22. The method of claim 15, wherein receiving the channel state information report comprises: The channel state information report is received indicating a future instance or future window of the predicted channel state information measurement for the set of beams.

23. The method of claim 15, wherein the predicted channel state information measurements for the set of beams correspond to a future time instance, a future time window period, or a future scheduled transmission opportunity period associated with one or more channel measurement resources or one or more interference measurement resources.

24. The method of claim 15, wherein sending the second control message comprises: A downlink control information message is sent that triggers an aperiodic channel state information report based at least in part on the set of parameters, wherein the aperiodic channel state information report is the channel state information report.

25. The method of claim 15, wherein sending the second control message comprises: A medium access control message is sent that activates a semi-persistent channel state information report based at least in part on the set of parameters, wherein the semi-persistent channel state information report is the channel state information report.

26. The method of claim 15, wherein sending the first control message comprises: The first control message is sent indicating the one or more sets of parameters and a second set of parameter sets, wherein the one or more sets of parameters are associated with channel state information prediction and the second set of parameter sets is associated with historical channel state information measurements.

27. The method of claim 15, wherein sending the second control message comprises: The second control message is sent using a radio network temporary identifier associated with a channel state information prediction.

28. The method of claim 15, wherein the field of the second control message indicating the one or more parameter sets is associated with channel state information prediction.

29. An apparatus for wireless communication at a user equipment (UE), comprising: processor; and a memory coupled to the processor, wherein instructions are stored in the memory, and the instructions are executable by the processor to cause the apparatus to: receiving a first control message indicating one or more sets of parameters for beam prediction via a predictive channel state information report; receiving a second control message requesting the UE to send a channel state information report indicating a predicted channel state information measurement based at least in part on a set of parameters in the one or more sets of parameters; as well as The channel state information report indicating the predicted channel state information measurement for a set of beams based at least in part on the set of parameters is sent in response to the second control message.

30. An apparatus for wireless communication at a network entity, comprising: processor; and a memory coupled to the processor, wherein instructions are stored in the memory, and the instructions are executable by the processor to cause the apparatus to: sending a first control message, the first control message indicating one or more sets of parameters for beam prediction via a predictive channel state information report; sending a second control message requesting a user equipment (UE) to send a channel state information report indicating a predicted channel state information measurement based at least in part on a set of parameters in the one or more sets of parameters; as well as The channel state information report indicating the predicted channel state information measurements for a set of beams based at least in part on the set of parameters is received in response to the second control message.

Images