Overhead reduction for feedback on beam prediction results

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can transmit a first report comprising a set of measurements and a set of predicted measurements, the first report further comprising an indication of one or more differences between a first set of beam identifiers associated with the set of measurements and a second set of beam identifiers associated with the set of predicted measurements. The UE can receive a grant to schedule transmission of a second report based at least in part on the indication of the one or more differences. The UE can send the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

Description

Technical Field

[0001] The following relates to wireless communication, including overhead reduction for feedback regarding beam prediction results. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (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 multi-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses that support overhead reduction for feedback regarding beam prediction results. For example, the described techniques allow a User Equipment (UE) to set a bit or flag in a first Channel State Information (CSI) report to indicate whether there is any difference (e.g., different or out of order) between beam identifiers (e.g., Channel Measurement Result Identifier (CMR-ID)) in actual channel measurement results and predicted channel measurement results at one or more prediction instances. When this bit or flag is set to indicate a difference, this may trigger the scheduling of a second CSI report to identify such a difference. For example, the UE may send a first report (e.g., the first CSI report) to a network entity. The first report may carry or otherwise convey an indication of a set of measurement results (e.g., actual channel measurement results) and a set of predicted measurement results (e.g., predicted channel measurement results for one or more future prediction instances). The first report may also include a bit, flag, or field with a value set to convey an indication that there is a difference between a first set of beam identifiers (e.g., one or more CMR-IDs) of the set of measurement results and a second set of beam identifiers of the set of predicted measurement results. Examples of such differences include, but are not limited to, that the CMR-ID of the predicted measurement results is different or out of order with respect to the CMR-ID of the actual measurement results indicated in the first report (e.g., the CMR-ID in the second set is the same as the CMR-ID in the first set but in a different order).

[0004] Based on the indicated differences, the network entity receiving the first report may send a grant to the UE that transmits the second report. The UE may send the second report according to the grant and indicate in the second report or otherwise identify the mapping of the differences between the first set and the second set of beam identifiers (e.g., identify the differences or the unordered CMR-IDs). For example, the second report may include the beam identifiers included in the second set of beam identifiers (e.g., a complete list of all CMR-IDs showing the predicted results indicated in the first report), or include the beam identifiers in the second set that are different from the corresponding beam identifiers in the first set (e.g., a partial list showing only the differences). Thus, the UE can avoid the overhead of signaling the second set of beam identifiers (e.g., CMR-IDs of predicted measurement results) in the first report and still maintain consistency with the network entity regarding the channel performance measurement and reporting process.

[0005] A method for wireless communication at a UE is described. The method may include: sending a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; receiving a grant for transmitting the second report based on the indication of the one or more differences; and transmitting the second report according to the grant, the second report identifying the mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include at least one processor and a memory coupled to the at least one processor. The memory stores instructions that can be executed by the at least one processor to cause the UE to perform the following operations: send a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; receive a grant for transmitting the second report based on the indication of the one or more differences; and transmit the second report according to the grant, the second report identifying the mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0007] Describes another apparatus for wireless communication at a UE. The apparatus may include: means for transmitting a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; means for receiving a grant for scheduling the transmission of a second report based on the indication of the one or more differences; and means for transmitting the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0008] A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by at least one processor to: transmit a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; receive a grant for scheduling the transmission of a second report based on the indication of the one or more differences; and transmit the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for performing the following actions: performing a set of channel performance measurements to obtain the set of measurement results of the first set of beam identifiers; determining a set of predicted channel performance measurements to obtain the set of measurement results of the second set of beam identifiers; and identifying the one or more differences between the first set of beam identifiers and the second set of beam identifiers, wherein a bit or flag in the first report may be set to a value indicating that the one or more differences may have been identified. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for performing the following actions: determining that one or more beam identifiers in the second set of beam identifiers may be different from beam identifiers in the first set of beam identifiers, wherein the one or more differences may be based on the difference of the one or more beam identifiers.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that beam identifiers in the second set of beam identifiers may be in a different order in the first set of beam identifiers, wherein the one or more differences may be based on the different order. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying a report identifier associated with the first report; and including the report identifier in the second report based on the one or more differences, wherein the second report includes a dynamically-triggered CSI report.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying a report identifier associated with the second report; and including the report identifier in the first report based on the one or more differences, wherein the second report includes a dynamically-triggered CSI report.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying each beam identifier in the second set of beam identifiers; and including an indication of each beam identifier in the second report based on the one or more differences, wherein the second report includes a media access control - control element (MAC-CE) report.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying each difference between the first set of beam identifiers and the second set of beam identifiers; and including an indication of each difference in the second report based on the one or more differences, wherein the second report includes a MAC-CE report.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying the report identifier of the first report and the transmission time slot of the first report; and including an indication of the report identifier, the transmission time slot, or both in the second report.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a UE capability message indicating support for indicating the one or more differences.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving, from a network entity, a signal indicating support for indicating the one or more differences.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: applying one or more quantization schemes to the set of measurement results, the set of beam identifiers associated with the set of measurement results, or both, in the first report.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying a quantization table associated with reporting the one or more differences; and applying at least a portion of the quantization table to the set of measurement results, the set of beam identifiers associated with the set of measurement results, or both, in the first report.

[0019] A method for wireless communication at a network entity is described. The method may include: receiving a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; sending, based on the indication of the one or more differences, a grant for transmitting a second report; and receiving, according to the grant, the second report that identifies a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0020] Describes an apparatus for wireless communication at a network entity. The apparatus may include at least one processor and a memory coupled to the at least one processor, the memory storing instructions that can be executed by the at least one processor to cause the network entity to perform the following operations: receive a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; send a grant for transmitting a second report based on the indication of the one or more differences; and receive the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0021] Describes another apparatus for wireless communication at a network entity. The apparatus may include: means for receiving a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; means for sending a grant for transmitting a second report based on the indication of the one or more differences; and means for receiving the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0022] A non-transitory computer-readable medium storing code for wireless communication, the code including instructions that can be executed by at least one processor to perform the following operations: receive a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; send a grant for transmitting a second report based on the indication of the one or more differences; and receive the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that one or more beam identifiers in the second set of beam identifiers may be different from the beam identifiers in the first set of beam identifiers based on the indication of the one or more differences, where the one or more differences may be based on the differences of the one or more beam identifiers. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that the beam identifiers in the second set of beam identifiers may be in a different order in the first set of beam identifiers based on the indication of the one or more differences, where the one or more differences may be based on the different order.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that a report identifier associated with the first report may be included in the second report based on the one or more differences, where the second report includes a dynamically-triggered CSI report. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that a report identifier associated with the second report may be included in the second report based on the one or more differences, where the second report includes a dynamically-triggered CSI report.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that an indication of each beam identifier in the second set of beam identifiers may be included in the second report based on the one or more differences, where the second report includes a MAC-CE report. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining that an indication of each difference between the first set of beam identifiers and the second set of beam identifiers may be included in the second report based on the one or more differences, where the second report includes a MAC-CE report.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the report identifier of the first report, the transmission time slot of the first report, or both are identified based on the second report. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a UE capability message indicating support for indicating the one or more differences. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: transmitting a signal indicating support for indicating the one or more differences.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: applying one or more quantization schemes to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: identifying a quantization table associated with reporting the one or more differences; and applying at least a portion of the quantization table to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 Examples of wireless communication systems that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated.

[0029] Figure 2 Examples of wireless communication systems that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated.

[0030] Figure 3 Examples of report configurations that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated.

[0031] Figure 4A and Figure 4B Examples of report configurations that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated.

[0032] Figures 5A to 5C Examples of report configurations that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated.

[0033] Figure 6 and Figure 7Block diagram of a device supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0034] Figure 8 Block diagram of a communication manager supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0035] Figure 9 Diagram of a system including a device supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0036] Figure 10 and Figure 11 Block diagram of a device supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0037] Figure 12 Block diagram of a communication manager supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0038] Figure 13 Diagram of a system including a device supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure.

[0039] Figures 14 to 18 Flowchart illustrating a method supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. Detailed Description

[0040] Wireless networks can use channel measurement and reporting procedures (e.g., channel state information (CSI) reporting) to monitor the performance of wireless channels that are being used or potentially will be used for wireless communication. Such techniques can improve allocation and configuration decisions associated with wireless communication and mobility within the network (e.g., handovers). This can include a user equipment (UE) sending the results of channel measurements (e.g., measuring signals transmitted over the channel and reporting the results of those measurements, such as reference signal received power (RSRP)) that the UE has performed using reference signals, synchronization signals, tracking signals, or other signals sent by network entities, as well as measurement reports predicting measurement results. The predicted results can generally identify (e.g., based on past measurements, expected mobility, expected communication, or other considerations) what performance the UE expects the channel to provide during the prediction opportunity. However, the predicted measurements are typically signaled with complete identification information (e.g., beam identifiers, such as channel measurement result identifiers (CMR-ID) for each reported RSRP) for both the actual measurement results and the predicted measurement results. The overhead for signaling identification information to support both the actual measurement results and the predicted measurement results is significant and may be unnecessary in some cases.

[0041] Accordingly, the techniques described allow a UE to set a bit or flag in a first CSI report to indicate whether there is any difference (e.g., different or out of order) between beam identifiers (e.g., CMR-ID) in the actual channel measurement results and the predicted channel measurement results at one or more prediction opportunities. When the bit or flag is set to indicate a difference, this can trigger scheduling of a second CSI report to identify such a difference. For example, the UE can send a first report (e.g., a first CSI report) to a network entity. The first report can carry or otherwise convey an indication of a set of measurement results (e.g., actual channel measurement results) and a set of predicted measurement results (e.g., predicted channel measurement results for one or more future prediction opportunities). The first report can also include a bit, flag, or field set to a value that conveys an indication that there is a difference between a first set of beam identifiers (e.g., one or more CMR-ID) of the set of measurement results and a second set of beam identifiers of the set of predicted measurement results. Examples of such differences include, but are not limited to, the CMR-ID of the predicted measurement results being different or out of order relative to the CMR-ID of the actual measurement results indicated in the first report (e.g., the CMR-ID in the second set is the same as the CMR-ID in the first set but in a different order).

[0042] Based on the indicated differences, a network entity that receives the first report may send a grant to the UE that transmits the second report. The UE may send the second report according to the grant and indicate in the second report or otherwise identify the mapping of the differences between the first set and the second set of beam identifiers (e.g., identify the differences or the out-of-order CMR-IDs). For example, the second report may include the beam identifiers included in the second set of beam identifiers (e.g., a complete list of all CMR-IDs showing the predicted results indicated in the first report), or include the beam identifiers in the second set that are different from the corresponding beam identifiers in the first set (e.g., a partial list showing only the differences). Thus, the UE may avoid the overhead of signaling the second set of beam identifiers (e.g., the CMR-IDs of the predicted measurement results) in the first report and still maintain consistency with the network entity regarding the channel performance measurement and reporting process.

[0043] 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 by way of and with reference to apparatus diagrams, system diagrams, and flowcharts related to the reduction of overhead for feedback regarding beam prediction results.

[0044] Figure 1 An example of a wireless communication system 100 that supports reduction of overhead for feedback regarding beam prediction results 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.

[0045] 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 having 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 names. In some examples, the network entities 105 and the UEs 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 UEs 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 UEs 115 may support signal communication according to one or more radio access technologies (RATs).

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

[0047] As described herein, a node of the wireless communication system 100 (which can be referred to as a network node or a wireless node) can be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, a device, an equipment, 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 can be a UE 115. As another example, the node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different from these examples. Similarly, references to UEs 115, network entities 105, devices, equipment, computing systems, etc. can include the disclosure of UEs 115, network entities 105, devices, equipment, computing systems, etc. as nodes. For example, the disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0048] In some examples, network entity 105 may communicate with core network 130, or with each other, or both. For example, network entity 105 may communicate with 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, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to a midhaul interface protocol) or fronthaul communication link 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic 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.

[0049] One or more of the network entities 105 described herein may include or may be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an integrated (e.g., monolithic, stand-alone) base station architecture that 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 base station 140).

[0050] In some examples, network entity 105 may be implemented in a split architecture (e.g., split base station architecture, split RAN architecture), which may be configured to utilize a protocol stack 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, 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, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of network entity 105 in the split RAN architecture may be co-located, or one or more components of 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 split RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0051] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU 160 and the DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can 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) functions and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be adopted between the DU 165 and the RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via these communication links.

[0052] In some wireless communication systems (e.g., wireless communication system 100), the 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 node 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 partially controlled 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 the supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include a separate antenna set for relaying communications with the UE 115, or may share the same antenna (e.g., of the RU 170) of the IAB node 104 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 nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the split 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.

[0053] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor may facilitate the connection 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 an RU 170), where 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 that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a part of the backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a part of the backhaul link).

[0054] The IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for the UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node towards the child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards the parent node associated with the IAB node 104. That is, the 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 transmissions for the UE 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 a child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and a DU interface (e.g., the DU 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or the UE 115.

[0055] For example, the IAB node 104 may be referred to as a parent node that supports communication 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., a fronthaul communication link 120) to the core network 130 and may act as a parent node for the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may signal transmissions directly to the UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions 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 over the NR Uu interface to the MT of the IAB node 104. Communication with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communication with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104.

[0056] In the case where the techniques described herein are applied in the context of a split RAN architecture, one or more components of the split RAN architecture may be configured to support overhead reduction for feedback regarding beam prediction results as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0057] The UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, station, terminal, or client, etc. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), multimedia / entertainment device (e.g., radio, MP3 player, or video device), camera, gaming device, navigation / location device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), Beidou system, GLONASS, or Galileo system, terrestrial devices, etc.), tablet computer, laptop computer, netbook, smartbook, personal computer, smart device, wearable device (e.g., smartwatch, smart clothing, smart glasses, virtual reality goggles, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), drone, robot / robotic device, vehicle, vehicle device, meter (e.g., parking meter, electricity meter, gas meter, water meter), monitor, air pump, electrical appliance (e.g., kitchen appliance, washing machine, dryer), location tag, medical / health device, implant, sensor / actuator, display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, the UE 115 may include or may be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances, vehicles, meters, etc.

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

[0059] UE 115 and 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 set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectrum band operating 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 operation, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, 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 network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of network entity 105. For example, the terms "transmit", "receive", or "communicate" when referring to network entity 105 may refer to any part of network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0060] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., 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 an independent mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-independent mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

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

[0063] The signal waveform transmitted via a carrier can 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 an MCM technique, a resource element can refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing can be inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources can refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data integrity for communication with the UE 115.

[0064] One or more parameter sets can be supported for a carrier, and the parameter set can include subcarrier spacing (Δf) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of the UE 115 can be restricted to one or more active BWPs.

[0065] The time interval for the network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which can refer to, for example, the sampling period T s = 1 / (Δf max ·N f) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) size. The time intervals of the communication resources may be organized according to radio frames each 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).

[0066] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, 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 to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-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 ones) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0067] A subframe, time slot, mini-slot, or 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 shortened TTIs (sTTIs)).

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

[0069] The network entity 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" can refer to a logical communication entity for communicating with the network entity 105 (e.g., using a carrier) and can be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), or other cell identifier) for distinguishing adjacent cells. In some examples, a cell can also refer to the coverage area 110 or a portion of the 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), the scope of such a cell can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or can include a building, a subset of a building, or an external space between or overlapping the coverage areas 110, etc.

[0070] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access to UEs 115 having a service subscription with the network provider that supports the macro cell. Compared to macro cells, small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140), 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 having a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

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

[0072] In some examples, network entity 105 (e.g., base station 140, RU 170) may be movable and thus provide communication coverage for a mobile coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but 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 use the same or different radio access technologies to provide coverage for respective coverage areas 110.

[0073] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, network entity 105 (e.g., base station 140) may have similar frame timings, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, network entity 105 may have different frame timings, 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 operation or asynchronous operation.

[0074] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow 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 can include communication from devices with integrated sensors or meters to measure or obtain 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 can be designed to collect information or enable 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 geographical event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the techniques disclosed herein can be applicable to MTC or IoT UEs. MTC or IoT UEs can include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. eMTC and NB-IoT can refer to future technologies that can evolve from or be based on these technologies. For example, eMTC can include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), and mMTC (massive MTC), while NB-IoT can include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0075] Some UEs 115 can be configured to operate in a power consumption-reducing mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other energy-saving techniques for UEs 115 include: entering a power-saving deep sleep mode when not participating in active communication, operating using limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can 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 the carrier, or outside the carrier.

[0076] 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). The 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 may be used interchangeably herein.

[0077] In some examples, the UE 115 may be configured to communicate 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 performing D2D communication in a group may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the network entity may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. 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, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

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

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

[0080] The wireless communication system 100 can operate using one or more frequency bands that can be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is from approximately one decimeter to one meter. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clutter), but these waves can be sufficient to penetrate structures so that a macro cell can serve a UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

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

[0082] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), long term evolution unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, the operation using the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in combination with a component carrier operating using a licensed band. The operation using the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, device-to-device (D2D) transmissions, and so on.

[0083] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which may be used to employ techniques 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 within one or more antenna arrays or antenna panels, which may support MIMO operation 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 at an antenna tower. In some examples, the 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 set of antenna ports in multiple rows and columns that the network entity 105 may use for beamforming to support communication 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 transmitted via the antenna ports.

[0084] The network entity 105 or UE 115 may use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may be transmitted, 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 techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0085] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals communicated via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of these antenna elements can 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).

[0086] Network entity 105 or UE 115 can use beam scanning techniques as part of a beamforming operation. For example, network entity 105 (e.g., base station 140, RU 170) can 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) can be sent by network entity 105 multiple times in different directions. For example, network entity 105 can send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions can be used to identify (e.g., by a transmitting device such as network entity 105, or by a receiving device such as UE115) beam directions for later transmission or reception by network entity 105.

[0087] Some signals (such as data signals associated with a particular receiving device) can 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, the beam direction associated with a transmission along a single beam direction can be determined based on signals transmitted along one or more beam directions. For example, UE 115 can receive one or more of the signals sent by network entity 105 in different directions and can report to network entity 105 an indication of the signal that UE 115 receives with the highest signal quality or other acceptable signal quality.

[0088] In some examples, transmissions performed by a device (e.g., by network entity 105 or UE 115) may be carried out using multiple beam directions, and the device may use a 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 the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)), which may or may not be 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 with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions used by UE 115 for subsequent transmission or reception), or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0089] 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 receiving according to multiple receiving directions by: receiving via different antenna sub-arrays, processing the received signals according to different antenna sub-arrays, receiving according to different sets of receive beamforming weights (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 sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, where any of these may refer to "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). The single receiving configuration may be aligned along a beam direction determined based on listening according to different receiving 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).

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

[0091] The UE 115 and the network entity 105 can support the retransmission of data to increase the likelihood that the data is 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 can include a 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 can support same-slot HARQ feedback, in which case the device can provide HARQ feedback for data received via previous symbols in a particular slot in that slot. In some other examples, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0092] The UE 115 can send a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The UE 115 can receive a grant for transmitting a second report at least partially based on the indication of the one or more differences. The UE 115 can send the second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0093] The network entity 105 may receive a first report that includes a set of measurement results and a set of predicted measurement results. The first report may further include an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The network entity 105 may send a grant for transmitting a second report at least partially based on the indication of the one or more differences. The network entity 105 may receive a second report according to the grant, and the second report identifies a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0094] Figure 2 An example of a wireless communication system 200 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 205 and a network entity 210, which may be examples of the corresponding devices described herein.

[0095] A wireless communication system uses channel measurement and reporting procedures (e.g., CSI reporting, L1 reporting, L2 reporting, or L3 reporting) to monitor channel performance. The reporting procedures typically include the UE 205 measuring reference signals transmitted by the network entity 210, or vice versa. These measurements may include measuring, identifying, or otherwise determining the RSRP, reference signal strength indicator (RSSI), interference level, or throughput of the channel. The UE 205 may modify one or more allocation decisions, configurations, or other parameters for wireless communication based on the measurement results. The UE 205 may also send or otherwise provide an indication of the measurement results to the network entity 210, which may also modify one or more allocation decisions, configurations, or other parameters.

[0096] In some aspects, CSI reporting may be used for beam management within a wireless network. The UE 205 and / or the network entity 210 may use beamforming or directional communication to direct a beam wirelessly in a particular direction (such as towards a receiving device). While beamforming communication is a useful technique for improving communication, the management of the beams being used is important due to mobility, interference, blockage, user actions, etc. Beamforming communication may include a transmitting device using a transmit beam to transmit towards a receiving device; and the receiving device using a receive beam to receive these transmissions. Thus, a beam pair may include a transmit beam of the transmitting device and a receive beam of the receiving device.

[0097] Beam management techniques, which can be considered part of the CSI reporting process, have evolved during the development of wireless networks. For example, when the UE 205 is operating in the radio resource control (RRC) idle or inactive state or during initial network access by the UE 205 (e.g., using beam scanning techniques for synchronization signal block (SSB) transmission), the wireless network can support beam management. When operating in the RRC connected state, beam management techniques are also implemented for the UE 205, which can include provisions for detecting beam failures and recovering from beam failures.

[0098] Wireless communication systems can support advanced CSI reporting techniques, such as improved beam management techniques using artificial intelligence (AI) and / or machine learning techniques. This can support improved beam prediction in the time domain and / or spatial domain based on modeling predicted beam performance. Such beam modeling techniques typically provide spatial or temporal beam predictions for a beam set based on current and / or historical beam measurements for different beam sets. In some examples, the predicted beam set can have narrower beams relative to the measured beams.

[0099] However, such techniques are typically limited in scope and add significant overhead to the wireless network. For example, such techniques are typically limited to reporting predicted beam results for a single time instance (e.g., one prediction occasion), which may not provide enough information to accurately predict future channel / beam performance over time. Additionally, such techniques increase the latency of prediction-based beam management because the network waits for multiple CSI reports to collect enough prediction occasions to accurately model the channel / beam performance. Additionally, since such techniques report a single predicted beam measurement for a single prediction occasion, the wireless network may not support or otherwise define how predicted beam measurements for multiple prediction occasions will be reported, such as what information will be reported for each prediction measurement and how each prediction measurement will be reported relative to other prediction measurements (e.g., absolute value, reference value, quantization, etc.).

[0100] Furthermore, such techniques may not support or otherwise define how the difference between actual measurement results and predicted measurement results will be reported. For example, the wireless network does not provide a mechanism or otherwise define the correspondence between actual measurement results and predicted measurement results. As understood in the art, a one-to-one correspondence requirement can be helpful in some scenarios but limits CSI reporting such that potentially better channel / beam performance candidates can be identified and reported. Alternatively, the absence of any correspondence requirement between measurement results and prediction results can lead to a significant increase in overhead because the details of each predicted measurement result for each prediction occasion would need to be reported.

[0101] More specifically, UE 205 may use layer one (L1) reports to periodically feedback predicted RSRP and measured RSRP (e.g., measuring each anchor point at 80 ms intervals, while predicting the RSRP at predicted intervals of 20 ms between anchor point intervals, thus assuming the same number of beams are addressed for each predicted / measured interval pair). In some aspects, considering beam change prediction for some scenarios, the overhead may potentially be reduced. As a non-limiting example, for pedestrian walking speeds without frequent UE rotation, it is more likely that the beam reported for the most recent measurement cycle may be the top (e.g., the same) beam for subsequent predicted intervals. The overhead of reporting beam IDs for prediction cycles may potentially be reduced (e.g., if 64 beams are included in the CMR set, reporting a certain CMR-ID requests 6 bits for each predicted beam). In other cases, the opposite may occur (e.g., the UE may be moving at a high mobility rate or otherwise experiencing frequency channel performance changes). Such techniques may not allow UE 205 to efficiently report such occasional payloads (e.g., different predicted intervals and / or prediction information).

[0102] Accordingly, aspects of the techniques described herein provide various mechanisms for supporting the reporting of actual measurement results (e.g., a set of measurement results) and a set of predicted measurement results. The set of predicted measurement results may include multiple predicted intervals (e.g., for k predicted intervals). The report may also include a bit, flag, field, or parameter that is set to a value that carries or otherwise conveys an indication of whether there is a difference between the currently reported measurement and the predicted measurement. That is, UE 205 may determine that there is a difference between the beam identifiers indicated for the actual measurement results (indicating a CMR-ID and associated measurement results) and the predicted measurement results (indicating a prediction result but not the CMR-ID of the prediction result). UE 205 may provide an indication that there is a difference, but does not necessarily provide an indication of what the difference is. In other cases, UE 205 may use two or more bits to convey at least some information about the difference. For example, the bit may be set to a first value (e.g., "00") to indicate no difference, set to a second value (e.g., "01") to indicate a difference in ordering, or set to a third value (e.g., "10") to indicate a difference in the beam identifiers in the set.

[0103] In some aspects, this may include persistent or semi-persistent L1 reports that include RSRP (e.g., measurement results) on top beam measurements at associated measurement occasions, plus k time-domain prediction occasions (after the measurement occasion) for predicting RSRP, with each predicted RSRP also associated with the top beam. Additional bits may be included in the L1 report. In some examples, when "0" is indicated in the first report, this may indicate that the beam addressed for the prediction occasion (e.g., beam identifier, such as the CMR-ID associated with the predicted RSRP) should be exactly the same as (e.g., identical to) the beam included in the measurement occasion. When "1" is indicated in the first report, this may indicate that the beam addressed for the prediction occasion should be different (for at least one prediction occasion). This may signal to the network entity 210 that the UE 205 expects to trigger with a dynamic CSI report or use a Medium Access Control - Control Element (MAC-CE) to report the beam ID for this (these) differences. A quantization scheme for the proposed reporting framework is also described herein.

[0104] Thus, at 215, the UE 205 may send or otherwise provide to the network entity 210 a first report that carries or otherwise conveys an indication of a set of measurement results and a set of predicted measurement results. The set of measurement results may generally refer to measurements determined during a measurement occasion using signals transmitted by the network entity 210 over a wireless channel. For example, the UE 205 may perform a set of channel performance measurements to measure, identify, or otherwise obtain a set of measurement results for a first set of beam identifiers. This may include the UE 205 measuring each measurement resource (e.g., each measurement resource shown as RSRP#0 to RSRP#3) to determine the RSRP of that resource. The UE 205 may measure each measurement resource during the measurement occasion.

[0105] The set of measurement results may include both the measurement results 230 and the beam identifiers 235 corresponding to the measurement results 230. That is, each measurement occasion may generally be associated with a time, frequency, space, or code resource (e.g., measurement resource) that the UE 205 is to monitor for measuring a signal. The measurement occasion may have a corresponding identifier (e.g., CMR-ID) that identifies the measurement occasion and / or resource and is used to identify the measurement results reported by the UE 205. The resource may include one or more beams associated with a channel measurement, where each beam has a corresponding beam identifier. Thus, the CMR-ID may correspond to the beam identifier associated with the reported measurement results 230 (e.g., the reported RSRP). In Figure 2 the non-limiting example shown, four measurement results are included in the measurement set for the measurement occasion (e.g., corresponding to RSRP 0 to RSRP 3), although different numbers may be measured and reported.

[0106] The set of predicted measurement results (or simply referred to as predicted results or predicted RSRP) may include predicted measurement results for multiple prediction instances. UE 205 may identify or otherwise determine the set of predicted measurement results based on a corresponding set of predicted channel performance metrics for a second set of beam identifiers (e.g., the expected RSRP of resources during a prediction instance). The predicted channel performance metrics may be based on current measurements, historical measurements (previously reported or unreported), the expected movement of UE 205, or a set of expected communications of UE 205. UE 205 may use one or more AI or machine learning protocols to determine the set of predicted measurement results for each prediction instance.

[0107] For example, for a total of k prediction instances, the set of predicted measurement results may include the predicted result 240 for the first prediction instance, the predicted result 245 for the second prediction instance, and the predicted result 250 for the final prediction instance. Each predicted result may typically carry or otherwise convey an indication of the predicted RSRP or other channel performance metric during the prediction instance. Four predicted results (e.g., for RSRP#0 to RSRP#3) during each prediction instance are also shown by way of non-limiting example.

[0108] The first report may indicate the set of predicted measurement results for a prediction instance, but may not necessarily indicate the corresponding beam identifiers for each predicted result. That is, different from the set of measurement results in which the measurement results and the corresponding beam identifiers (e.g., CMR-ID, which may be associated with the beam identifiers of the RSRP measurement resources) are included in the first report, there is no indication of the second set of beam identifiers associated with the set of predicted measurement results in the first report. Instead, the first report may carry or otherwise convey an indication of whether there is a difference between the first set of beam identifiers associated with the set of measurement results and the second set of beam identifiers associated with the set of predicted measurement results.

[0109] For example, UE 205 may identify or otherwise determine whether there is a difference between the first set of beam identifiers associated with the set of measurement results and indicated for the set of measurement results (e.g., one or more beam identifiers 235) and the second set of beam identifiers of the set of predicted measurement results. For example, UE 205 may identify or otherwise determine whether the first set of beam identifiers is the same as or different from the second set of beam identifiers.

[0110] The difference may be based on a difference in beam identifiers between a first set and a second set of beam identifiers. For example, the CMR-ID and / or associated beam identifiers in the first set of beam identifiers may be different from the CMR-ID and / or associated beam identifiers in the second set of beam identifiers. This may indicate that the prediction result of the prediction timing is associated with at least one beam identifier that is different from the CMR-ID reported in the first report and / or the beam identifier associated with the CMR-ID.

[0111] The difference may be based on a different ordering of the beam identifiers in the first set and the second set of beam identifiers. For example, UE 205 may identify or otherwise determine that the beam identifiers in the second set of beam identifiers may be in a different order in the first set of beam identifiers. That is, the beam identifiers in the first set and the second set of beam identifiers may be the same (e.g., all for RSRP#0 to RSRP#3), but the order of the prediction results of the beam identifiers is different from that in the first set of measurement results.

[0112] Accordingly, UE 205 may use one or more bits, flags, fields, and / or parameters that are set to values that carry or otherwise convey an indication of whether there is a difference between the first set of beam identifiers and the second set of beam identifiers. In some examples, this may include the first report indicating "0" to convey no difference, or indicating "1" to convey that there is a difference between the first set of beam identifiers and the second set of beam identifiers. Accordingly, UE 205 may send the first report indicating the measurement results 230 of the measurement result set and the corresponding beam identifiers 235 together with the prediction results (e.g., predicted measurement result set) of multiple prediction timings, but does not indicate the second set of beam identifiers of the predicted measurement result set.

[0113] In response, at 220, the network entity 210 may send or otherwise provide a grant for scheduling the transmission of a second report (e.g., a dynamic CSI report and / or a MAC-CE-based report) to UE 205. In some aspects, the grant may be sent when the first report indicates that there is a difference between the first set of beam identifiers and the second set of beam identifiers. That is, the first report indicating the difference may trigger the scheduling of the second report.

[0114] Accordingly, at 225, UE 205 may send or otherwise provide a second report (e.g., a second CSI report) to the network entity 210. The second report may carry or otherwise convey an indication of a mapping of the difference between the first set of beam identifiers in the measurement result set and the second set of beam identifiers associated with the predicted measurement result set.

[0115] Thus, the wireless communication system 200 provides joint measurement and prediction L1 reporting without beam IDs for the prediction cycle. This can be based on a first CSI report, where the UE 205 reports L1-RSRP / L1 signal-to-interference-plus-noise ratio (SINR) for N CMRs (where, in Figure 2 , N = 4, corresponding to RSRP#0 to RSRP#3), and these CMRs are associated with CSI report settings for (k + 1) time-domain opportunities (e.g., prediction opportunities), where additional bits are included in the CSI report. The L1-RSRP / L1-SINR for the first time-domain opportunity (e.g., measurement opportunity) is based on actual measurement, and its CSI reference resource is not later than the time slot carrying the first CSI report. The CMR-ID (e.g., the first set of beam identifiers) associated with the L1-RSRP / L1-SINR of the first time-domain opportunity is also included in the first CSI report. The L1-RSRP / L1-SINR (e.g., the set of measurement results) for k time-domain opportunities (prediction opportunities) can be predicted by the UE 205, where such k time-domain opportunities are at least after the time slot carrying the CSI report. The first CSI report can carry or otherwise convey additional bits for indicating whether there is a difference between the first set of beam identifiers (e.g., CMR-ID associated with L1-RSRP / L1-SINR) and the second set of beam identifiers for k time-domain prediction opportunities (e.g., for the set of prediction measurement results).

[0116] If "0" is reported in the first CSI report, then the L1-RSRP / L1-SINR for the k prediction opportunities is associated with the same CMRs as those based on actual measurement in the first time-domain opportunity, and their CMR-ID order is also the same as the CMR order associated with the first time-domain opportunity. If "1" is reported in the first CSI report, then this can indicate that there is at least one prediction opportunity among the k prediction opportunities, where the L1-RSRP / L1-SINR of such a prediction opportunity is associated with a CMR not addressed by the first time-domain opportunity, or the CMR-ID order of such a prediction opportunity is different from the CMR-ID order associated with the first time-domain opportunity.

[0117] If a "1" is reported in the first CSI report, this may trigger a second CSI report that carries or otherwise conveys an indication of a mapping that identifies differences. The mapping may be a full mapping of a second set of beam identifiers or a partial mapping that shows different beam identifiers in the second set of beam identifiers. Thus, this may provide an efficient mechanism for the UE 205 to report RSRP / SINR for multiple prediction instances, along with current RSRP / SINR measurement results, and also indicate whether there are any differences (e.g., different or out of order) between the beam identifiers of the predicted results and the corresponding current measurement results. If a "0" is reported in the first CSI report, the second CSI report may be unnecessary (e.g., at least with respect to reporting the mapping of differences).

[0118] Figure 3 An example of a reporting configuration 300 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure is illustrated. The reporting configuration 300 may implement aspects of the wireless communication system 100 and / or 200. Aspects of the reporting configuration 300 may be implemented at or by a UE and / or a network entity, which may be examples of the corresponding devices described herein. The reporting configuration 300 illustrates a non-limiting example of a second CSI report that identifies a mapping of differences between a first set of beam identifiers and a second set of beam identifiers. In some aspects, the reporting configuration 300 illustrates an example in which the second report is a dynamically triggered CSI report (e.g., an aperiodic CSI report).

[0119] As discussed herein, the described techniques provide an efficient technique for a UE to report a first set of associated measurement results (e.g., L1-RSRP / SINR) and beam identifiers (e.g., CMR-ID) of the set of measurement results in a first CSI report transmitted to a network entity, along with a predicted set of measurement results. The first CSI report may also include one or more bits, flags, fields, and / or parameters that are set to indicate whether there is any difference between a first set of beam identifiers (e.g., as reported in the first CSI report) and a second set of beam identifiers (e.g., CMR-ID) of the predicted set of measurement results, without reporting the values of the second set of beam identifiers. As a non-limiting example, if "0" is reported in the first CSI report, this may indicate no difference, while if "1" is reported in the first CSI report, this may indicate a difference. If there is a difference, this may trigger a grant for a second CSI report that identifies the mapping of the difference. That is, if "1" is reported for an additional bit in the first CSI report, this may indicate that at least one of the CMR-IDs (or their relative order) is different from the corresponding CMR-ID at a first time domain occasion (e.g., the measurement occasion of the set of measurement results). Reporting configuration 300 illustrates a non-limiting example of a second CSI report that identifies the mapping of the difference between a first set of beam identifiers and a second set of beam identifiers.

[0120] Specifically, reporting configuration 300 illustrates an example second CSI report that identifies the mapping of the difference. When "1" is reported, it is desired (e.g., based on indicating "1" in the first CSI report) to trigger the UE (e.g., via a grant) with a second non-periodic or dynamic CSI report to feedback (e.g., identify the mapping) the CMR-IDs (e.g., the second set of beam identifiers) for k time domain occasions (e.g., k predicted occasions). In some aspects, the second CSI report may have a fixed payload size, such as to support providing a list of the second set of beam identifiers.

[0121] For example, it is desirable to trigger the UE with a second aperiodic CSI report, where the number of reports of the second CSI report should at least include the CMR-ID associated with the L1-RSRP / L1-SINR (predicted measurement result set) of k predicted occasions (e.g., for the first CSI report indicating the measurement result set when the additional bit is indicated as "1" for the most recent UE report). Thus, the second CSI report in this example may include the beam identifier 305 of the first predicted occasion, the beam identifier 310 of the second predicted occasion, and the beam identifier 315 of the third predicted occasion, and four beam identifiers are reported for each previously reported predicted occasion in a non-limiting example manner. That is, each beam identifier of the predicted measurement results in the predicted measurement result set can be identified in the second CSI report. The network entity may compare the second set of beam identifiers (e.g., CMR-ID) of the measurement result set indicated in the first CSI report with the second set of beam identifiers (e.g., CMR-ID) of the second CSI report reporting the predicted measurement result set indicated in the first CSI report to determine or otherwise identify such differences. As discussed above, the differences can be different beam identifiers (e.g., CMR-ID) and / or can lie in that one or more of the beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers.

[0122] In some examples, the first CSI report and the second CSI report may be bound together or otherwise associated with each other based on a report identifier (e.g., CSI report ID). For example, the UE may identify or otherwise determine the report identifier of the first report and include the report identifier of the first report in the second report. For example, the CSI report setting ID of the first CSI report may be included in the CSI report setting of the second CSI report or included in the CSI-AssociatedReportConfigInfo of the second AP CSI report.

[0123] Additionally or alternatively, the UE may identify or otherwise determine the report identifier of the second report and include the report identifier of the second report in the first report. For example, the CSI report setting ID of the second CSI report (e.g., the second aperiodic or dynamically-triggered CSI report) is included in the CSI report setting of the first CSI report, or the {CSI-AssociatedReportConfigInfo ID, CSI-AperiodicTriggerState ID} of the second CSI report is included in the CSI report setting of the first CSI report. Through this link, when the UE is triggered with the second CSI report, the UE knows which first CSI report it should refer to. The network entity may also use this link to know which first CSI report it should refer to when receiving the second CSI report to determine the difference between beam identifiers.

[0124] In some examples, the report identifier of the first CSI report and other information (e.g., the transmission time slot) may be indicated in the second CSI report. That is, the CSI report setting ID of the first CSI report and / or the time slot / subframe / frame ID associated with the time slot / subframe / frame carrying the first CSI report may also optionally be included in the second CSI report (e.g., to avoid ambiguity when there are multiple first CSI reports with a reported "1" or when there is a first CSI report that has been missed by the network entity).

[0125] In some examples, how to configure the second CSI report may be based on the UE capability report and / or configured separately by the network. For example, the UE may send or otherwise provide a UE capability message indicating support for indicating differences (e.g., in the second CSI report conveyed in a dynamically-triggered CSI report and / or in a MAC-CE report). In the case where there is a difference between the measured measurement result beam identifier and the predicted measurement result beam identifier, the network entity may use the UE capability for CSI reporting. Additionally or alternatively, the network entity may send or otherwise provide a configuration or otherwise indicate a signal supporting indication of differences according to the techniques described herein.

[0126] Figure 4A and Figure 4B Examples of report configurations 400-a and 400-b that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated. Report configurations 400-a and 400-b may implement aspects of the wireless communication system 100 and / or 200 and / or aspects of the report configuration 300. Aspects of report configurations 400-a and 400-b may be implemented at or by a UE and / or a network entity, which may be examples of the corresponding devices described herein.

[0127] Report configurations 400-a and 400-b illustrate non-limiting examples of a second CSI report that maps the differences between a first set of beam identifiers and a second set of beam identifiers. In some aspects, report configurations 400-a and 400-b illustrate examples where the second report is a MAC-CE report. Specifically, Figure 4A report configuration 400-a illustrates an example of a complete report that indicates each beam identifier in the second set of beam identifiers, where Figure 4B report configuration 400-b illustrates an example of a partial report that indicates only the different beam identifiers in the second set of beam identifiers relative to the first set of beam identifiers.

[0128] As discussed herein, the described techniques provide an efficient technique for a UE to report a first set of associated measurement results (e.g., L1-RSRP / SINR) and beam identifiers (e.g., CMR-ID) of the measurement results set in a first CSI report transmitted to a network entity, along with a predicted measurement results set for multiple prediction occasions. The first CSI report may also include one or more bits, flags, fields, and / or parameters that are set to indicate whether there are any differences between the first set of beam identifiers (e.g., as reported in the first CSI report) and a second set of beam identifiers (e.g., CMR-ID) of the predicted measurement results set, without reporting the values of the second set of beam identifiers in the first CSI report. If there are differences, this may trigger a grant to schedule a second CSI report that maps the identified differences. That is, if a “1” is reported for an additional bit in the first CSI report, this may indicate that at least one of the CMR-IDs (or their relative order) is different from the corresponding CMR-ID at a first time domain occasion (e.g., the measurement occasion of the measurement results set). Report configurations 400-a and 400-b illustrate non-limiting examples of a second CSI report that maps the differences between a first set of beam identifiers and a second set of beam identifiers.

[0129] Specifically, report configurations 400-a and 400-b illustrate example second CSI reports that map the identified differences. When a “1” is reported and the UE does not have an uplink grant for delivering the second report, the “1” indicated in the first CSI report may act as a scheduling request (SR) that notifies the network entity that the UE has data to send (e.g., the second CSI report). In response, the network entity may receive an “indication” of the SR from the UE and respond with a grant to schedule the second report.

[0130] For example, it is desirable to trigger the UE with a second aperiodic CSI report, where the number of reports of the second CSI report should at least include the CMR-ID associated with the L1-RSRP / L1-SINR (predicted measurement result set) of k prediction occasions (e.g., for the first CSI report indicating the measurement result set when the additional bit is indicated as "1" in the most recent UE report). Thus, the second CSI report in this example may include a MAC-CE report, where the second report is carried or otherwise conveyed in the MAC-CE sent to the network entity.

[0131] In some examples, the report identifier of the first CSI report and other information (e.g., the transmission time slot) may be indicated in the second CSI report. That is, the CSI report setting ID of the first CSI report and / or the time slot / subframe / frame ID associated with the time slot / subframe / frame carrying the first CSI report may also optionally be included in the second CSI report (e.g., to avoid ambiguity when there are multiple first CSI reports with "1" reported or when there is a first CSI report that has been missed by the network entity).

[0132] Therefore and turning first to Figure 4A the reporting configuration 400-a, the second report may include or otherwise convey an indication of each beam identifier (e.g., CMR-ID) in the second set of beam identifiers. For example, the second report may include the report ID 405 of the first CSI report, the beam identifiers 410 for each prediction occasion reported in the first CSI report, the beam identifier 415, and the beam identifier 420. Again, four beam identifiers are shown for each prediction occasion by way of non-limiting example only. This complete reporting mechanism stipulates that all the corresponding CMR-IDs for all the corresponding prediction occasions are included in the MAC-CE report carrying the second report. Thus, the UE may identify or otherwise determine each beam identifier in the second set of beam identifiers and include an indication of each beam identifier in the second report (e.g., included in the MAC-CE report). In some examples, the MAC-CE report carrying or otherwise conveying the second report may be a fixed-length MAC-CE (e.g., based on the expected number of CMR-IDs to be reported in the second report according to the first report).

[0133] Next turning to Figure 4BFor the report configuration 400-b, the second report may carry or otherwise convey an indication (e.g., a partial report) of each difference (e.g., each different beam identifier) between the first set of beam identifiers and the second set of beam identifiers. For example, the second report may include a report identifier 425 of the first CSI report, beam identifiers 430, timing identifiers 435, and RSRP IDs 440 of each beam identifier in the second set of beam identifiers, where each beam identifier is different (or out of order) from the corresponding predicted result indicated in the first report. That is, in this example, a complete list of the second set of beam identifiers is not conveyed. Instead, the second report may include a variable-length MAC-Ce that includes a flexible number (e.g., based on how many differences there are) of CMR-IDs. Each CMR-ID (e.g., beam identifier) of each report is accompanied by a predicted timing identifier of the associated predicted timing and an L1-RSRP / L1-SINR order identifier. This information can be used to map the predicted results reported as a set of predicted measurement results in the first report, where the predicted results are different from the corresponding beam identifiers in the first set of beam identifiers of the set of measurement results. This method can improve the efficiency of the second report by reporting a reduced amount of information in the second report (e.g., a partial report that only identifies each difference relative to the first report).

[0134] In some aspects, which MAC-CE report format (e.g., fixed or flexible length) may be based on the number of differences between the first set of beam identifiers and the second set of beam identifiers. That is, the UE may determine the number of differences and include an indication of the amount of information to be conveyed in the second report via the SR (e.g., a large amount of data for a full report or a small data indicator when only a partial report is authorized). Thus, the network entity may more efficiently allocate resources for the second report based on the number of differences between the first set and the second set of beam identifiers.

[0135] Similarly, how the second CSI report is configured may be based on the UE capability report and / or configured separately by the network. For example, the UE may send or otherwise provide a UE capability message indicating support for indicating differences (e.g., in a dynamically triggered CSI report and / or in the second CSI report conveyed in a MAC-CE report). In the case where there are differences between the measured measurement result beam identifiers and the predicted measurement result beam identifiers, the network entity may use the UE capability for CSI reporting. Additionally or alternatively, the network entity may send or otherwise provide a signal that configures or otherwise indicates support for indicating differences according to the techniques described herein.

[0136] Accordingly, reporting configurations 400-a and 400-b illustrate non-limiting examples of how a UE may use uplink MAC-CEs to feedback CMR-IDs for k time-domain opportunities (e.g., predicted opportunities). In reporting configuration 400-a, the second report (e.g., MAC-CE report) includes an indication of all CMR-IDs for each of the k time-domain predicted opportunities. In reporting configuration 400-b, flexible payload MAC-CEs may be used to indicate each CMR-ID accompanied by its opportunity identifier and RSRP rank identifier.

[0137] Figures 5A to 5C Examples of reporting configurations 500-a, 500-b, and 500-c that support reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure are illustrated. Reporting configurations 500-a, 500-b, and 500-c may implement aspects of wireless communication systems 100 and / or 200 and / or aspects of reporting configurations 300, 400-a, and / or 400-b. Aspects of reporting configurations 500-a, 500-b, and 500-c may be implemented at or by a UE and / or a network entity, which may be an example of the corresponding devices described herein.

[0138] Figure 5A reporting configuration 500-a, Figure 5B reporting configuration 500-b, and Figure 5C reporting configuration 500-c illustrate non-limiting examples of differential quantization techniques that may be applied to a first CSI report that indicates a set of measurement results and a set of predicted measurement results for k prediction opportunities.

[0139] The techniques described herein provide an efficient technique for a UE to report a first set of associated measurement results (e.g., L1-RSRP / SINR, shown by way of non-limiting example as RSRP#0 to RSRP#3) and beam identifiers (e.g., CMR-ID) of the set of measurement results in a first CSI report transmitted to a network entity, along with a set of predicted measurement results for a plurality of prediction instances. The first CSI report may also include one or more bits, flags, fields, and / or parameters that are set to indicate whether there is any difference between a first set of beam identifiers (e.g., as reported in the first CSI report) and a second set of beam identifiers (e.g., CMR-ID) of the set of predicted measurement results, without reporting the values of the second set of beam identifiers in the first CSI report. If there is a difference, this may trigger the grant of a second CSI report that maps the identified difference. That is, if a "1" is reported for an additional bit in the first CSI report, this may indicate that at least one of the CMR-IDs (or their relative order) is different from the corresponding CMR-ID at a first time domain instance (e.g., the measurement instance of the set of measurement results). Indicating a "1" in the first CSI report may trigger the transmission of a grant for scheduling the second report. The UE may transmit the second report according to the grant and include in the second report a mapping of the difference between the first set of beam identifiers (e.g., CMR-ID for the measurement results and indicated in the first report) and the second set of beam identifiers (e.g., CMR-ID for the predicted results but not indicated in the first report).

[0140] When transmitting the first report, the UE may apply different quantization techniques for the measurement results and the predicted results. That is, the set of measurement results may include measurement results 505 and beam identifiers 510 corresponding to each measurement result 505. The beam identifiers 510 may include the CMR-ID (e.g., beam identifier) corresponding to the respective measurement result 505 (e.g., providing identification information of the measurement result 505, such as the beam identifier). The set of predicted measurement results may include predicted results 515 for a first prediction instance, predicted results 520 for a second prediction instance, and predicted results 525 for a final prediction instance (e.g., based on k). The UE may apply one or more quantization schemes in the quantization scheme to the measurement and / or predicted results (e.g., to improve efficiency). Quantization techniques generally provide a method of mapping values or numbers from a first larger or (pre-)selected set of individuals or values or numbers to a second smaller (pre-)selected set of individuals or values or numbers. Rounding, truncation, and similar techniques may be applied to the second set relative to the first set and may be applied to reduce the number of bits used to convey information.

[0141] As a non-limiting example and referring first to Figure 5AReport configuration 500-a, for each prediction / measurement occasion, may report, via M1 bits (e.g., 7 bits), the strongest L1-RSRP / L1-SINR of the considered occasion absolutely, and report the remaining L1-RSRP / L1-SINR differentially with reference to the strongest L1-RSRP / L1-SINR via M2 bits (e.g., 4 bits). That is, a first quantity of bits (e.g., seven bits) may be used to report the measurement result (e.g., RSRP and / or SINR) having the strongest value (e.g., RSRP#0 in this example) of the measurement occasion. A second quantity of bits (e.g., four bits) may be used to differentially report each additional measurement result of the measurement occasion having a lower value relative to RSRP#0. Similarly, for the prediction results reported during each prediction occasion, a first quantity of bits (e.g., seven bits) may be used to report the prediction result having the strongest value (e.g., also RSRP#0 in this example). A second quantity of bits (e.g., four bits) may be used to differentially report each additional prediction result of the prediction occasion having a lower value relative to RSRP#0. Differential reporting may include reporting the difference between RSRP#0 and the other RSRPs of the occasion, rather than the absolute values of those other RSRPs. Reporting the difference may reduce the number of bits required to convey the measurement and / or prediction results in the first report. In some examples, positive dB values may be used for differential quantization, which may be associated with the quantization table applied when sending the first report.

[0142] Reference Figure 5BReport configuration 500-b, which illustrates another example of a quantization scheme that can be applied in the first report. Report configuration 500-b illustrates an example differential quantization framework, in which a specific L1-RSRP / L1-SINR in a prediction occasion is differentially quantized with reference to the L1-RSRP / L1-SINR associated with the same CMR-ID order in the first time domain measurement occasion. For the first measurement occasion, all absolute quantization of L1-RSRP / L1-SINR can be performed using the same number of bits (e.g., 7 bits), or the strongest L1-RSRP / L1-SINR can be absolutely quantized via M1 bits (e.g., 7 bits), while the remaining L1-RSRP / L1-SINR are differentially reported with reference to the strongest L1-RSRP / L1-SINR via M2 bits (e.g., 4 bits). That is, report configuration 500-b illustrates an example in which each measurement result can be absolutely quantized in the first report (e.g., reporting the actual RSRP value), or the first (e.g., strongest) RSRP (e.g., RSRP#0 in this example) can be absolutely quantized, while the remaining measurement results are differentially reported relative to RSRP#0. However, each prediction result in each prediction occasion can be differentially reported relative to the corresponding measurement result (e.g., the predicted RSRP#0 during each prediction occasion is differentially reported relative to the measured RSRP#0).

[0143] Reference Figure 5CReport configuration 500-c, which illustrates another example of a quantization scheme that can be applied in the first report. Report configuration 500-c illustrates an example differential quantization framework, where the specific L1-RSRP / L1-SINR in the prediction occasion is differentially quantized with reference to the L1-RSRP / L1-SINR associated with the same CMR-ID order in the time-domain measurement before the considered prediction occasion and in the prediction occasion. For the first measurement occasion, all absolute quantization of L1-RSRP / L1-SINR can be performed using the same number of bits (e.g., 7 bits), or the strongest L1-RSRP / L1-SINR can be absolutely quantized via M1 bits (e.g., 7 bits), while the remaining L1-RSRP / L1-SINR are differentially reported via M2 bits (e.g., 4 bits) with reference to the strongest L1-RSRP / L1-SINR. That is, report configuration 500-c illustrates an example where each measurement result can be absolutely quantized in the first report (e.g., reporting the actual RSRP value), or the first (e.g., strongest) RSRP (e.g., RSRP#0 in this example) can be absolutely quantized, while the remaining measurement results are differentially reported relative to RSRP#0. However, each prediction result in each prediction occasion can be differentially reported relative to the previous prediction occasion, and for the first prediction occasion, it is differentially reported relative to the measurement result. That is, the prediction result of RSRP#0 in the second prediction occasion can be differentially reported relative to the prediction result of RSRP#0 during the first prediction occasion.

[0144] In some aspects, an L1-RSRP / L1-SINR quantization table can be applied to the described quantization scheme. At least a portion of the quantization table (e.g., one or more entries in the table) can be applied to the set of measurement results and / or the set of predicted measurement results in the first report. The differential quantization of L1-RSRP / L1-SINR in the prediction occasion can be based on a newly introduced L1-RSRP / L1-SINR differential quantization table. The quantization table can include two differential dB values that are stronger or weaker than the reference L1-RSRP / L1-SINR.

[0145] Figure 6 Block diagram 600 illustrates a device 605 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure. Device 605 can be an example of aspects of UE 115 as described herein. Device 605 can include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0146] The receiver 610 may provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to overhead reduction for feedback on beam prediction results) such as packets, user data, control information, or any combination thereof. The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or an array of multiple antennas.

[0147] The transmitter 615 may provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to overhead reduction for feedback on beam prediction results) such as packets, user data, control information, or any combination thereof. 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 an array of multiple antennas.

[0148] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or their various components may be examples of components for performing various aspects of overhead reduction for feedback on beam prediction results as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or their components may support methods for performing one or more of the functions described herein.

[0149] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and the memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0150] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supporting the performance of the functions described in this disclosure).

[0151] In some examples, the communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in conjunction with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 may receive information from the receiver 610, convey information to the transmitter 615, or integrate in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0152] In accordance with examples disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured to or otherwise support components for transmitting a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The communication manager 620 may be configured to or otherwise support components for receiving a grant for scheduling transmission of a second report based on the indication of the one or more differences. The communication manager 620 may be configured to or otherwise support components for transmitting a second report in accordance with the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0153] By including or configuring a communication manager 620 in accordance with examples described herein, a device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or combinations thereof or otherwise coupled thereto) may support techniques for improved CSI reporting that uses reduced overhead to signal differences between measured and predicted measurement results.

[0154] Figure 7Block diagram 700 illustrates a device 705 that supports reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0155] The receiver 710 may provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to reduced overhead for feedback regarding beam prediction results), such as packets, user data, control information, or any combination thereof. The information may be passed to other components of device 705. The receiver 710 may utilize a single antenna or an array of multiple antennas.

[0156] The transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to reduced overhead for feedback regarding beam prediction results), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or an array of multiple antennas.

[0157] Device 705 or its various components may be examples of components for performing various aspects of reduced overhead for feedback regarding beam prediction results as described herein. For example, the communication manager 720 may include a reporting manager 725, a grant manager 730, a mapping manager 735, or any combination thereof. The communication manager 720 may be an example of aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in conjunction with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, convey information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0158] According to examples as disclosed herein, a communication manager 720 may support wireless communication at a UE. A reporting manager 725 may be configured to or otherwise support components for sending a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. A grant manager 730 may be configured to or otherwise support components for receiving a grant for scheduling transmission of a second report based on the indication of one or more differences. A mapping manager 735 may be configured to or otherwise support components for sending a second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0159] Figure 8 Block diagram 800 illustrates a communication manager 820 supporting reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of reduced overhead for feedback regarding beam prediction results as described herein. For example, the communication manager 820 may include a reporting manager 825, a grant manager 830, a mapping manager 835, a difference mapping manager 840, a report ID manager 845, a full mapping manager 850, a partial mapping manager 855, a capabilities manager 860, a quantization manager 865, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses).

[0160] According to examples as disclosed herein, a communication manager 820 may support wireless communication at a UE. A reporting manager 825 may be configured to or otherwise support components for sending a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. A grant manager 830 may be configured to or otherwise support components for receiving a grant for scheduling transmission of a second report based on the indication of one or more differences. A mapping manager 835 may be configured to or otherwise support components for sending a second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0161] In some examples, the differential mapping manager 840 may be configured to or otherwise support components for performing a set of channel performance measurements to obtain a set of measurement results for a first set of beam identifiers. In some examples, the differential mapping manager 840 may be configured to or otherwise support components for determining a set of predicted channel performance measurements to obtain a set of measurement results for a second set of beam identifiers. In some examples, the differential mapping manager 840 may be configured to or otherwise support components for identifying one or more differences between the first set of beam identifiers and the second set of beam identifiers, where a bit or flag in a first report is set to a value indicating that one or more differences have been identified.

[0162] In some examples, the differential mapping manager 840 may be configured to or otherwise support components for determining that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers, where the one or more differences are based on differences in the one or more beam identifiers. In some examples, the differential mapping manager 840 may be configured to or otherwise support components for determining that beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers, where the one or more differences are based on the different order. In some examples, the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

[0163] In some examples, the report ID manager 845 may be configured to or otherwise support components for identifying a report identifier associated with the first report. In some examples, the report ID manager 845 may be configured to or otherwise support components for including the report identifier in a second report based on one or more differences, where the second report includes a dynamically triggered CSI report.

[0164] In some examples, the report ID manager 845 may be configured to or otherwise support components for identifying a report identifier associated with the second report. In some examples, the report ID manager 845 may be configured to or otherwise support components for including the report identifier in the first report based on one or more differences, where the second report includes a dynamically triggered CSI report.

[0165] In some examples, the full mapping manager 850 may be configured to or otherwise support components for identifying each beam identifier in the second set of beam identifiers. In some examples, the full mapping manager 850 may be configured to or otherwise support components for including an indication of each beam identifier in a second report based on one or more differences, where the second report includes a MAC-CE report.

[0166] In some examples, the partial mapping manager 855 may be configured to or otherwise support components for identifying each difference between a first set of beam identifiers and a second set of beam identifiers. In some examples, the partial mapping manager 855 may be configured to or otherwise support components for including an indication of each difference in a second report based on one or more differences, where the second report includes a MAC-CE report.

[0167] In some examples, the report ID manager 845 may be configured to or otherwise support components for identifying a report identifier of a first report and a transmission time slot of the first report. In some examples, the report ID manager 845 may be configured to or otherwise support components for including an indication of the report identifier, the transmission time slot, or both in a second report.

[0168] In some examples, the capability manager 860 may be configured to or otherwise support components for sending a UE capability message indicating support for indicating one or more differences. In some examples, the capability manager 860 may be configured to or otherwise support components for receiving, from a network entity, a signal indicating support for indicating one or more differences.

[0169] In some examples, the quantization manager 865 may be configured to or otherwise support components for applying one or more quantization schemes to a set of measurement results in a first report, a set of beam identifiers associated with the set of measurement results, or both. In some examples, the quantization manager 865 may be configured to or otherwise support components for identifying a quantization table associated with reporting one or more differences. In some examples, the quantization manager 865 may be configured to or otherwise support components for applying at least a portion of the quantization table to a set of measurement results in a first report, a set of beam identifiers associated with the set of measurement results, or both.

[0170] Figure 9FIG. 900 illustrates a system 900 including a device 905 that supports reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. The device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

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

[0172] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, and the more than one antenna may be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 915 may communicate bi-directionally via one or more antennas 925, a wired or wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating a packet; providing the modulated packet to one or more antennas 925 for transmission; and demodulating a packet received from one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be examples of the transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof, or components thereof, as described herein.

[0173] Memory 930 may include random access memory (RAM) and read-only memory (ROM). Memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by processor 940 but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, among other things, memory 930 may also contain a basic input / output system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0174] Processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks that support overhead reduction for feedback regarding beam prediction results). For example, device 905 or components of device 905 may include processor 940 and memory 930 coupled or coupled to processor 940, and processor 940 and memory 930 are configured to perform the various functions described herein.

[0175] According to an example as disclosed herein, communication manager 920 may support wireless communication at a UE. For example, communication manager 920 may be configured to or otherwise support components for sending a first report including a set of measurement results and a set of predicted measurement results, the first report also including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. Communication manager 920 may be configured to or otherwise support components for receiving a grant for scheduling the transmission of a second report based on the indication of one or more differences. Communication manager 920 may be configured to or otherwise support components for sending a second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0176] By including or configuring a communication manager 920 according to examples as described herein, the device 905 may support techniques for improved CSI reporting that uses reduced overhead to signal the difference between measured and predicted measurement results.

[0177] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in concert with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that, when executed by the processor 940, cause the device 905 to perform various aspects of reduced overhead for feedback regarding beam prediction results as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0178] Figure 10 Block diagram 1000 illustrates a device 1005 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the 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. Each of these components may communicate with one another (e.g., via one or more buses).

[0179] The receiver 1010 may provide components 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, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0180] Transmitter 1015 may provide a component for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of device 1005. For example, 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, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0181] Communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or their various components may be examples of components for performing various aspects of overhead reduction for feedback regarding beam prediction results as described herein. For example, communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or their components may support methods for performing one or more of the functions described herein.

[0182] In some examples, communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or components may be implemented in hardware, software (e.g., executable by a processor), or any combination thereof. The hardware may include a processor, DSP, CPU, GPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise supporting components for performing the functions described in this 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 the processor executing instructions stored in the memory).

[0183] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software). If implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, a GPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., components configured or otherwise supporting the performance of the functions described in this disclosure).

[0184] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, convey information to the transmitter 1015, or integrate in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0185] According to examples disclosed herein, the communication manager 1020 may support wireless communication at a network entity. For example, the communication manager 1020 may be configured or otherwise support components for receiving a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The communication manager 1020 may be configured or otherwise support components for sending a grant for scheduling transmission of a second report based on the indication of the one or more differences. The communication manager 1020 may be configured or otherwise support components for receiving a second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0186] By including or configuring the communication manager 1020 according to examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or combinations thereof or otherwise coupled thereto) may support techniques for improved CSI reporting that uses reduced overhead to signal differences between measured and predicted measurement results.

[0187] Figure 11Block diagram 1100 illustrates device 1105, which supports reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 1110 may provide components 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 device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0189] The transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of device 1105. For example, the transmitter 1115 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 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0190] Device 1105 or its various components may be examples of components for performing various aspects of overhead reduction for feedback regarding beam prediction results as described herein. For example, communication manager 1120 may include a reporting manager 1125, a grant manager 1130, a mapping manager 1135, or any combination thereof. Communication manager 1120 may be an example of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, convey information to transmitter 1115, or integrate in combination with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0191] According to examples disclosed herein, communication manager 1120 may support wireless communication at a network entity. Reporting manager 1125 may be configured to or otherwise support components for receiving a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. Grant manager 1130 may be configured to or otherwise support components for sending a grant for scheduling a second report based on the indication of one or more differences. Mapping manager 1135 may be configured to or otherwise support components for receiving a second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0192] Figure 12FIG. 1200 is a block diagram of a communication manager 1220 that illustrates reduced overhead support for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of reduced overhead for feedback regarding beam prediction results as described herein. For example, the communication manager 1220 may include a reporting manager 1225, a grant manager 1230, a mapping manager 1235, a reporting ID manager 1240, a full mapping manager 1245, a partial mapping manager 1250, a capabilities manager 1255, a quantization manager 1260, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses), and such communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualized components associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0193] In accordance with examples as disclosed herein, the communication manager 1220 may support wireless communication at a network entity. The reporting manager 1225 may be configured to or otherwise support components for receiving a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The grant manager 1230 may be configured to or otherwise support components for sending a grant for scheduling a second report based on the indication of the one or more differences. The mapping manager 1235 may be configured to or otherwise support components for receiving a second report in accordance with the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0194] In some examples, the reporting ID manager 1240 may be configured to or otherwise support components for determining that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers based on the indication of the one or more differences, where the one or more differences are based on differences in one or more beam identifiers.

[0195] In some examples, the reporting ID manager 1240 may be configured to or otherwise support components for determining that beam identifiers in a second set of beam identifiers are in a different order in a first set of beam identifiers based on an indication of one or more differences, where the one or more differences are based on the different order. In some examples, a first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

[0196] In some examples, the reporting ID manager 1240 may be configured to or otherwise support components for determining that a report identifier associated with a first report is included in a second report based on one or more differences, where the second report includes a dynamically triggered CSI report. In some examples, the reporting ID manager 1240 may be configured to or otherwise support components for determining that a report identifier associated with a second report is included in the second report based on one or more differences, where the second report includes a dynamically triggered CSI report.

[0197] In some examples, the full mapping manager 1245 may be configured to or otherwise support components for determining that an indication of each beam identifier in a second set of beam identifiers is included in a second report based on one or more differences, where the second report includes a MAC-CE report.

[0198] In some examples, the partial mapping manager 1250 may be configured to or otherwise support components for determining that an indication of each difference between a first set of beam identifiers and a second set of beam identifiers is included in a second report based on one or more differences, where the second report includes a MAC-CE report.

[0199] In some examples, the reporting ID manager 1240 may be configured to or otherwise support components for identifying the report identifier of a first report, the transmission time slot of the first report, or both based on a second report.

[0200] In some examples, the capability manager 1255 may be configured to or otherwise support components for receiving a UE capability message indicating support for indicating one or more differences. In some examples, the capability manager 1255 may be configured to or otherwise support components for sending a signal indicating support for indicating one or more differences.

[0201] In some examples, the quantization manager 1260 may be configured to or otherwise support components for applying one or more quantization schemes to a set of measurement results indicated in a first report, a set of beam identifiers associated with the set of measurement results, or both.

[0202] In some examples, the quantization manager 1260 may be configured to or otherwise support components for identifying quantization tables associated with reporting one or more differences. In some examples, the quantization manager 1260 may be configured to or otherwise support components for applying at least a portion of a quantization table to a set of measurement results indicated in a first report, a set of beam identifiers associated with the set of measurement results, or both.

[0203] Figure 13 Illustrated is a diagram of a system 1300 including a device 1305 that supports reduced overhead for feedback regarding beam prediction results, in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of the device 1005, the device 1105, or the network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support outputting and obtaining communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0204] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335, or memory 1325, or both) may be included in a chip or chip assembly installed in the device 1305. 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).

[0205] The memory 1325 may include RAM and ROM. The memory 1325 may store computer-readable, computer-executable code 1330 that includes instructions which, when executed by the processor 1335, cause the device 1305 to perform the various functions described herein. The code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1330 may not be directly executable by the processor 1335 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 1325 may also contain a BIOS that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0206] The processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, GPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks that support overhead reduction for feedback regarding beam prediction results). For example, the device 1305 or components of the device 1305 may include the processor 1335 and the memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions for performing the functions of the device 1305 (e.g., by executing code 1330). The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as within the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system generally may refer to a system or 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 of, for example, the device 1305). For example, the processing system of the device 1305 may refer to a system that includes various other components or sub-components of the device 1305 (such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or a combination of other components or components of the device 1305). The processing system of the device 1305 may interface with other components of the device 1305 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. 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, and other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that the device 1305 may transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1305 can obtain information or signal inputs, and the information can 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 inputs, and the second interface may also output information or signal outputs.

[0207] In some examples, the bus 1340 may support communication within a protocol layer of a protocol stack (e.g., within a protocol layer). In some examples, the bus 1340 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communication performed within components of the device 1305, or communication performed between different components of the device 1305 that may be co-located or located at different locations (e.g., where the device 1305 may refer to a system in which one or more of the communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component or divided between different components).

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

[0209] According to examples disclosed herein, the communication manager 1320 may support wireless communication at a network entity. For example, the communication manager 1320 may be configured or otherwise support components for receiving a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The communication manager 1320 may be configured or otherwise support components for sending a grant for scheduling the transmission of a second report based on the indication of the one or more differences. The communication manager 1320 may be configured or otherwise support components for receiving a second report according to the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0210] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 may support techniques for improved CSI reporting for signaling a difference between measured measurement results and predicted measurement results using reduced overhead.

[0211] In some examples, communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in conjunction with transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to communication manager 1320 may be supported or performed by transceiver 1310, processor 1335, memory 1325, code 1330, or any combination thereof. For example, code 1330 may include instructions that, when executed by processor 1335, cause device 1305 to perform various aspects of reduced overhead for feedback regarding beam prediction results as described herein, or processor 1335 and memory 1325 may otherwise be configured to perform or support such operations.

[0212] Figure 14 A flowchart illustrating a method 1400 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure is shown. The operations of method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1400 may be performed by a UE 115 as described with reference to Figures 1 to 9 above. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0213] At 1405, the method may include: transmitting a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The operation of 1405 may be performed in accordance with an example as disclosed herein. In some examples, aspects of the operation of 1405 may be performed by a report manager 825 as described with reference to Figure 8 above.

[0214] At 1410, the method may include: receiving a grant for scheduling transmission of a second report based on the indication of one or more differences. The operation of 1410 may be performed in accordance with an example as disclosed herein. In some examples, aspects of the operation of 1410 may be performed by a grant manager 830 as described with reference to Figure 8 above.

[0215] At 1415, the method may include: sending a second report according to a grant, the second report identifying a mapping of one or more differences between a first set of beam identifiers and a second set of beam identifiers. The operations at 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1415 may be performed by a mapping manager 835 as described with reference to Figure 8 the mapping manager 835 described above.

[0216] Figure 15 FIG. illustrates a flow chart of a method 1500 that supports reduced overhead for feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a UE or its components as described herein. For example, the operations of method 1500 may be performed by a UE 115 as described with reference to Figures 1 to 9 the UE 115 described above. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0217] At 1505, the method may include: performing a set of channel performance measurements to obtain a set of measurement results for a first set of beam identifiers. The operations at 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1505 may be performed by a difference mapping manager 840 as described with reference to Figure 8 the difference mapping manager 840 described above.

[0218] At 1510, the method may include: determining a set of predicted channel performance measurements to obtain a set of measurement results for a second set of beam identifiers. The operations at 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1510 may be performed by a difference mapping manager 840 as described with reference to Figure 8 the difference mapping manager 840 described above.

[0219] At 1515, the method may include: identifying one or more differences between a first set of beam identifiers and a second set of beam identifiers, wherein a bit or flag in a first report is set to a value indicating that one or more differences have been identified. The operations at 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1515 may be performed by a difference mapping manager 840 as described with reference to Figure 8 the difference mapping manager 840 described above.

[0220] At 1520, the method may include: sending a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The operations at 1520 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1520 may be performed by a reporting manager 825 as referenced Figure 8 as described.

[0221] At 1525, the method may include: receiving a grant to schedule the transmission of a second report based on the indication of one or more differences. The operations at 1525 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1525 may be performed by a grant manager 830 as referenced Figure 8 as described.

[0222] At 1530, the method may include: sending a second report in accordance with the grant, the second report identifying a mapping of one or more differences between the first set of beam identifiers and the second set of beam identifiers. The operations at 1530 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1530 may be performed by a mapping manager 835 as referenced Figure 8 as described.

[0223] Figure 16 Illustrates a flowchart of a method 1600 that illustrates reduced overhead in support of feedback regarding beam prediction results in accordance with one or more aspects of the present disclosure. The operations of method 1600 may be implemented by a UE or its components as described herein. For example, the operations of method 1600 may be performed by a UE 115 as referenced Figures 1 to 9 as described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0224] At 1605, the method may include: sending a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The operations at 1605 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1605 may be performed by a reporting manager 825 as referenced Figure 8 as described.

[0225] At 1610, the method may include: determining that one or more beam identifiers in a second set of beam identifiers are different from beam identifiers in a first set of beam identifiers, wherein the one or more differences are based on differences in the one or more beam identifiers. The operations at 1610 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1610 may be performed by a difference mapping manager 840 as referenced Figure 8 as described.

[0226] At 1615, the method may include: receiving a grant for transmitting a second report based on an indication of the one or more differences. The operations at 1615 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1615 may be performed by a grant manager 830 as referenced Figure 8 as described.

[0227] At 1620, the method may include: transmitting a second report according to the grant, the second report identifying a mapping of one or more differences between a first set of beam identifiers associated with a measurement result set and a second set of beam identifiers associated with a predicted measurement result set. The operations at 1620 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1620 may be performed by a mapping manager 835 as referenced Figure 8 as described.

[0228] Figure 17 Illustrates a flowchart of a method 1700 that illustrates overhead reduction in support of feedback regarding beam prediction results according to one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of method 1700 may be performed by a network entity as referenced Figure 1 to FIG. 5 and Figures 10 to 13 as described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the functions.

[0229] At 1705, the method may include: receiving a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The operations at 1705 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1705 may be performed by a report manager 1225 as referenced Figure 12 as described.

[0230] At 1710, the method may include: sending a grant for sending a second report based on an indication of one or more differences. The operation of 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1710 may be performed by a grant manager 1230 as referenced Figure 12 as described.

[0231] At 1715, the method may include: receiving a second report according to the grant, the second report identifying a mapping of one or more differences between a first set of beam identifiers and a second set of beam identifiers. The operation of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1715 may be performed by a mapping manager 1235 as referenced Figure 12 as described.

[0232] Figure 18 Illustrates a flowchart of a method 1800 that supports reduced overhead for feedback regarding beam prediction results according to one or more aspects of the present disclosure. The operations of method 1800 may be implemented by a network entity or its components as described herein. For example, the operations of method 1800 may be performed by a network entity as referenced Figure 1 to FIG. 5 and Figures 10 to 13 as described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0233] At 1805, the method may include: receiving a first report that includes a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be performed by a report manager 1225 as referenced Figure 12 as described.

[0234] At 1810, the method may include: sending a grant for sending a second report based on an indication of one or more differences. The operation of 1810 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1810 may be performed by a grant manager 1230 as referenced Figure 12 as described.

[0235] At 1815, the method may include: receiving a second report according to a grant, the second report identifying a mapping of one or more differences between a first set of beam identifiers and a second set of beam identifiers. The operations at 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1815 may be performed by a mapping manager 1235 as referred to in Figure 12 as described.

[0236] At 1820, the method may include: determining, based on the one or more differences, that a report identifier associated with a first report is included in the second report, where the second report includes a dynamically triggered channel state information report. The operations at 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1820 may be performed by a report ID manager 1240 as referred to in Figure 12 as described.

[0237] An overview of aspects of the present disclosure is provided below:

[0238] Aspect 1: A method for wireless communication at a UE, the method including: transmitting a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; receiving a grant for scheduling transmission of a second report at least in part based on the indication of the one or more differences; and transmitting the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0239] Aspect 2: The method according to aspect 1, the method further including: performing a set of channel performance measurements to obtain the set of measurement results for the first set of beam identifiers; determining a set of predicted channel performance measurements to obtain the set of measurement results for the second set of beam identifiers; and identifying the one or more differences between the first set of beam identifiers and the second set of beam identifiers, where a bit or flag in the first report is set to a value indicating that the one or more differences have been identified.

[0240] Aspect 3: The method according to any one of aspects 1 to 2, the method further including: determining that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers, where the one or more differences are at least in part based on the differences of the one or more beam identifiers.

[0241] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: determining that beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers, wherein the one or more differences are at least partially based on the different order.

[0242] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

[0243] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: identifying a report identifier associated with the first report; and including the report identifier in the second report at least partially based on the one or more differences, wherein the second report includes a dynamically triggered CSI report.

[0244] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: identifying a report identifier associated with the second report; and including the report identifier in the first report at least partially based on the one or more differences, wherein the second report includes a dynamically triggered CSI report.

[0245] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: identifying each beam identifier in the second set of beam identifiers; and including an indication of each beam identifier in the second report at least partially based on the one or more differences, wherein the second report includes a MAC-CE report.

[0246] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: identifying each difference between the first set of beam identifiers and the second set of beam identifiers; and including an indication of each difference in the second report at least partially based on the one or more differences, wherein the second report includes a MAC-CE report.

[0247] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: identifying the report identifier of the first report and the transmission time slot of the first report; and including an indication of the report identifier, the transmission time slot, or both in the second report.

[0248] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: transmitting a UE capability message indicating support for indicating the one or more differences.

[0249] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: receiving, from a network entity, a signal indicating support for indicating the one or more differences.

[0250] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: applying one or more quantization schemes to the set of measurement results in the first report, the set of beam identifiers associated with the set of measurement results, or both.

[0251] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: identifying a quantization table associated with reporting the one or more differences; and applying at least a portion of the quantization table to the set of measurement results in the first report, the set of beam identifiers associated with the set of measurement results, or both.

[0252] Aspect 15: A method for wireless communication at a network entity, the method comprising: receiving a first report comprising a set of measurement results and a set of predicted measurement results, the first report further comprising an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; sending, at least in part based on the indication of the one or more differences, a grant for transmitting a second report; and receiving, according to the grant, the second report, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

[0253] Aspect 16: The method according to Aspect 15, the method further comprising: determining, at least in part based on the indication of the one or more differences, that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers, wherein the one or more differences are at least in part based on the differences of the one or more beam identifiers.

[0254] Aspect 17: The method according to any one of Aspects 15 to 16, the method further comprising: determining, at least in part based on the indication of the one or more differences, that the beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers, wherein the one or more differences are at least in part based on the different order.

[0255] Aspect 18: The method according to any one of Aspects 15 to 17, wherein the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

[0256] Aspect 19: The method according to any one of aspects 15 to 18, the method further comprising: determining, at least in part based on the one or more differences, that a report identifier associated with the first report is included in the second report, wherein the second report comprises a dynamically triggered CSI report.

[0257] Aspect 20: The method according to any one of aspects 15 to 19, the method further comprising: determining, at least in part based on the one or more differences, that a report identifier associated with the second report is included in the second report, wherein the second report comprises a dynamically triggered CSI report.

[0258] Aspect 21: The method according to any one of aspects 15 to 20, the method further comprising: determining, at least in part based on the one or more differences, that an indication of each beam identifier in the second set of beam identifiers is included in the second report, wherein the second report comprises a MAC-CE report.

[0259] Aspect 22: The method according to any one of aspects 15 to 21, the method further comprising: determining, at least in part based on the one or more differences, that an indication of each difference between the first set of beam identifiers and the second set of beam identifiers is included in the second report, wherein the second report comprises a MAC-CE report.

[0260] Aspect 23: The method according to any one of aspects 15 to 22, the method further comprising: identifying, at least in part based on the second report, the report identifier of the first report, the transmission time slot of the first report, or both.

[0261] Aspect 24: The method according to any one of aspects 15 to 23, the method further comprising: receiving a UE capability message indicating support for indicating the one or more differences.

[0262] Aspect 25: The method according to any one of aspects 15 to 24, the method further comprising: transmitting a signal indicating support for indicating the one or more differences.

[0263] Aspect 26: The method according to any one of aspects 15 to 25, the method further comprising: applying one or more quantization schemes to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both.

[0264] Aspect 27: The method according to any one of aspects 15 to 26, the method further comprising: identifying a quantization table associated with reporting the one or more differences; and applying at least a portion of the quantization table to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both.

[0265] Aspect 28: An apparatus for wireless communication at a UE, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the UE to perform the method according to any one of aspects 1 to 14.

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

[0267] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of aspects 1 to 14.

[0268] Aspect 31: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the network entity to perform the method according to any one of aspects 15 to 27.

[0269] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 15 to 27.

[0270] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of aspects 15 to 27.

[0271] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified and other specific implementations are also possible. Additionally, aspects from two or more methods can be combined.

[0272] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein may also apply to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may apply to a variety of 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. Components within a wireless communication system may be coupled to each other (e.g., operatively coupled, communicatively coupled, functionally coupled, electronically coupled, and / or electrically coupled).

[0273] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to 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.

[0274] The various illustrative blocks and components described in connection 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 the 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).

[0275] The functions described herein can be implemented in hardware, software executed by a processor, or any combination thereof. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, regardless of whether they are referred to in software, firmware, middleware, microcode, hardware description language, or other terms. If implemented using software executed by a processor, these functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on 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 can be implemented using software executed by a processor, hardware, hardwiring, or any combination thereof. The features implementing the functions can also be physically located in different positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0276] Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media can be any available media that can be accessed by a general or special purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general or special purpose computer or a general or special purpose processor. Also, any connection is properly termed a computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disk can magnetically reproduce data, and disc can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0277] As used herein, including in the claims, the "or" used in a list of items (e.g., a list of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing 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). Additionally, as used herein, the phrase "based on" should not be construed 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 "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items can be taken alone, or any combination of two or more of the listed items can be taken. For example, if a composition is described as containing components A, B, and / or C, the composition can contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.

[0278] The term "determine" encompasses a variety of actions and, thus, "determine" can include computing, calculating, processing, deriving, researching, looking up (such as looking up in a table, database, or other data structure), or ascertaining. Additionally, "determine" can include receiving (e.g., receiving information) or accessing (e.g., accessing data stored in a memory). Further, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such like actions.

[0279] In the figures, similar components or features may have the same reference numeral. Additionally, various components of the same type can be distinguished by adding a dash and a second numeral used to differentiate between similar components after the reference numeral. If only the first reference numeral is used in the specification, the description can apply to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or any subsequent reference numerals.

[0280] The description set forth herein in conjunction with the figures describes example configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0281] The description provided herein enables a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure are obvious to a person of ordinary skill in the art, and the general principles defined herein can 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 accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that can be executed by the at least one processor to cause the UE to: send a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; receive a grant for sending a second report at least in part based on the indication of the one or more differences; and send the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

2. The apparatus according to claim 1, wherein the instructions can be further executed by the at least one processor to cause the UE to: perform a set of channel performance measurements to obtain the set of measurement results for the first set of beam identifiers; determine a set of predicted channel performance measurements to obtain the set of measurement results for the second set of beam identifiers; and identify the one or more differences between the first set of beam identifiers and the second set of beam identifiers, wherein a bit or flag in the first report is set to a value indicating that the one or more differences have been identified.

3. The apparatus according to claim 1, wherein the instructions can be further executed by the at least one processor to cause the UE to: determine that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers, wherein the one or more differences are at least in part based on the differences of the one or more beam identifiers.

4. The apparatus according to claim 1, wherein the instructions can be further executed by the at least one processor to cause the UE to: determine that the beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers, wherein the one or more differences are at least in part based on the different order.

5. The apparatus according to claim 1, wherein the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

6. The apparatus according to claim 1, wherein the instructions can be further executed by the at least one processor to cause the UE to: identify a report identifier associated with the first report; and include the report identifier in the second report at least in part based on the one or more differences, wherein the second report includes a dynamically triggered channel state information report.

7. The apparatus according to claim 1, wherein the instructions can be further executed by the at least one processor to cause the UE to: identify a report identifier associated with the second report; and Include the report identifier in the first report based at least in part on the one or more differences, wherein the second report includes a dynamically triggered channel state information report.

8. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Identify each beam identifier in the second set of beam identifiers; and Include an indication of each beam identifier in the second report based at least in part on the one or more differences, wherein the second report includes a medium access control - control element (MAC - CE) report.

9. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Identify each difference between the first set of beam identifiers and the second set of beam identifiers; and Include an indication of each difference in the second report based at least in part on the one or more differences, wherein the second report includes a medium access control - control element (MAC - CE) report.

10. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Identify the report identifier of the first report and the transmission time slot of the first report; and Include an indication of the report identifier, the transmission time slot, or both in the second report.

11. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Transmit a UE capability message indicating support for indicating the one or more differences.

12. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Receive a signal from a network entity indicating support for indicating the one or more differences.

13. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Apply one or more quantization schemes to the set of measurement results in the first report, the set of beam identifiers associated with the set of measurement results, or both.

14. The apparatus according to claim 1, wherein the instructions are further executable by the at least one processor to cause the UE to: Identify a quantization table associated with reporting the one or more differences; and Apply at least a portion of the quantization table to the set of measurement results in the first report, the set of beam identifiers associated with the set of measurement results, or both.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one processor; And A memory coupled to the at least one processor, the memory storing instructions that are executable by the at least one processor to cause the network entity to: Receive a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; Send a grant for transmitting a second report at least in part based on the indication of the one or more differences; And Receive the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

16. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity to: Determine that one or more beam identifiers in the second set of beam identifiers are different from beam identifiers in the first set of beam identifiers at least in part based on the indication of the one or more differences, wherein the one or more differences are at least in part based on the differences of the one or more beam identifiers.

17. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity to: Determine that the beam identifiers in the second set of beam identifiers are in a different order in the first set of beam identifiers at least in part based on the indication of the one or more differences, wherein the one or more differences are at least in part based on the different order.

18. The apparatus according to claim 15, wherein the first report indicates the first set of beam identifiers and does not indicate the second set of beam identifiers.

19. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity to: Determine that a report identifier associated with the first report is included in the second report at least in part based on the one or more differences, wherein the second report includes a dynamically triggered channel state information report.

20. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity to: Determine that a report identifier associated with the second report is included in the second report at least in part based on the one or more differences, wherein the second report includes a dynamically triggered channel state information report.

21. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity to: Determine that an indication of each beam identifier in the second set of beam identifiers is included in the second report at least in part based on the one or more differences, wherein the second report includes a media access control - control element (MAC-CE) report.

22. The apparatus according to claim 15, wherein the instructions can be further executed by the at least one processor to cause the network entity: An indication of each difference between the first set of beam identifiers and the second set of beam identifiers is determined at least in part based on the one or more differences and is included in the second report, where the second report includes a Medium Access Control - Control Element (MAC-CE) report.

23. The apparatus according to claim 15, wherein the instructions are further executable by the at least one processor to cause the network entity to: Identify the report identifier of the first report, the transmission time slot of the first report, or both, at least in part based on the second report.

24. The apparatus according to claim 15, wherein the instructions are further executable by the at least one processor to cause the network entity to: Receive a UE capability message indicating support for indicating the one or more differences.

25. The apparatus according to claim 15, wherein the instructions are further executable by the at least one processor to cause the network entity to: Transmit a signal indicating support for indicating the one or more differences.

26. The apparatus according to claim 15, wherein the instructions are further executable by the at least one processor to cause the network entity to: Apply one or more quantization schemes to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both.

27. The apparatus according to claim 15, wherein the instructions are further executable by the at least one processor to cause the network entity to: Identify a quantization table associated with reporting the one or more differences; and Apply at least a portion of the quantization table to the set of measurement results indicated in the first report, the set of beam identifiers associated with the set of measurement results, or both.

28. A method for wireless communication at a User Equipment (UE), the method comprising: Transmitting a first report including a set of measurement results and a set of predicted measurement results, the first report further including an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; Receiving a grant scheduling transmission of a second report at least in part based on the indication of the one or more differences; And Transmitting the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

29. The method according to claim 28, the method further comprising: Performing a set of channel performance measurements to obtain the set of measurement results for the first set of beam identifiers; Determining a set of predicted channel performance measurements to obtain the set of measurement results for the second set of beam identifiers; And Identifying the one or more differences between the first set of beam identifiers and the second set of beam identifiers, where a bit or flag in the first report is set to a value indicating that the one or more differences have been identified.

30. A method for wireless communication at a network entity, the method comprising: Receiving a first report comprising a set of measurement results and a set of predicted measurement results, the first report further comprising an indication of one or more differences between a first set of beam identifiers associated with the set of measurement results and a second set of beam identifiers associated with the set of predicted measurement results; Sending a grant for transmission of a second report at least partially based on the indication of the one or more differences; And Receiving the second report according to the grant, the second report identifying a mapping of the one or more differences between the first set of beam identifiers and the second set of beam identifiers.

Images