Beam pair prediction at network entity using coordinate-based matrix reporting

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may transmit historical beam pair information including actual measurement information for one or more historical beam pairs. Each of the one or more historical beam pairs may include a transmit beam of the network entity and a historical receive beam of the UE. The historical beam pair information may indicate azimuth angle information and elevation angle information for each historical beam pair, wherein the azimuth angle information and the elevation angle information are based on a coordinate system of the UE. The UE may receive predicted beam pair information based on historical beam pair information, where each predicted beam pair has a predicted transmit beam and a predicted receive beam. The predicted receive beam may be based on a coordinate system of the UE.

Description

Background Art

[0001] The following relates to wireless communications, including beam pair prediction at a network entity using coordinate-based matrix reporting.

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

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting beam pair prediction at a network entity using coordinate-based matrix reporting. For example, the described techniques support a user equipment (UE) indicating receive beam information to support network-side beam pair prediction. The UE may divide the angular space from the UE into a grid or coordinate system, where the grid or coordinate system is divided into both azimuth and elevation angles. Each angular region from the UE (e.g., corresponding to elevation and azimuth angles) may be assigned an identifier. The UE may use one or more receive beams to receive signals from a network entity, which may use one or more transmit beams of the network entity to transmit signals. The UE may perform signal measurements to obtain beam pair measurements between the one or more receive beams and the one or more transmit beams. The UE may report historical beam pair information having actual measurement information for each of one or more historical beam pairs to the network entity. The historical beam pair information may indicate azimuth information and elevation information for the receive beam of each historical beam pair. The azimuth information and elevation information may be based on the UE's grid or coordinate system.

[0004] The network entity may receive historical beam pair information and use the historical beam pair information to identify a predicted beam pair. For example, the network entity may input the historical beam pair information into a machine learning model to obtain a predicted beam pair including a predicted transmit beam and a predicted receive beam with the highest prediction quality or prediction measurement. The network entity may send predicted beam pair information indicating one or more predicted beam pairs to the UE. In some aspects, the UE and the network entity may (e.g., at a later point in time) communicate using the predicted transmit beam and the predicted receive beam of one of the predicted beam pairs.

[0005] A method for wireless communication at a first network node is described. The method may include: receiving a set of multiple signals via a set of multiple receive beams; transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of a second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; and receiving predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

[0006] An apparatus for wireless communication at a first network node is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executable by the processor to cause the device to: receive a set of multiple signals via a set of multiple receive beams; send historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of the second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on the coordinate system of the first network node; and receive predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

[0007] Another apparatus for wireless communication at a first network node is described. The apparatus may include: means for receiving a set of multiple signals via a set of multiple receive beams; means for transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of a second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; and means for receiving predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first network node is described. The code may include instructions executable by a processor to: receive a set of multiple signals via a set of multiple receive beams; transmit historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of a second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; and receive predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information that may indicate the corresponding azimuth information and the corresponding elevation information relative to the coordinate system.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates an identifier associated with each pair between the elevation information and the azimuth information of the coordinate system.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates an identifier of a set of multiple angular regions of the coordinate system.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control information indicating a number of the one or more historical beam pairs for inclusion in the historical beam pair information.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more historical beam pairs include a respective historical beam pair for each combination of the set of multiple transmit beams and the set of multiple receive beams.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes a matrix having a set of multiple elements, wherein each respective element in the set of multiple elements corresponds to respective actual measurement information of a respective historical beam pair in the one or more respective beam pairs.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the respective azimuth information and the respective elevation information of each respective historical receive beam may be based on an orientation of the first network node and a receive beam identifier corresponding to the respective historical receive beam.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more historical beam pairs include a threshold number of historical beam pairs.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes a bitmap indicating coordinates of the coordinate system and corresponding historical measurements of the one or more historical beam pairs, the bitmap having a length corresponding to the total number of coordinates of the coordinate system.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmit beam, and actual measurement values ​​associated with the first identifier and the second identifier.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the historical beam pair information may include operations, features, components, or instructions for sending the historical beam pair information via uplink control information, channel state information (CSI) reports, medium access control (MAC) control elements, or radio resource control (RRC) messages.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a receive beam for communicating with the second network node based on the predicted beam pair information.

[0023] A method for wireless communication at a first network node is described. The method may include: transmitting a set of multiple signals via a set of multiple transmit beams; receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from a set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; and transmitting predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

[0024] An apparatus for wireless communication at a first network node is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executable by the processor to cause the device to: transmit a set of multiple signals via a set of multiple transmit beams; receive historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from a set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; and transmit predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

[0025] Another apparatus for wireless communication at a first network node is described. The apparatus may include: means for transmitting a set of multiple signals via a set of multiple transmit beams; means for receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from a set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; and means for transmitting predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a first network node is described. The code may include instructions executable by a processor to: transmit a set of multiple signals via a set of multiple transmit beams; receive historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from a set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; and transmit predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control information that may indicate the corresponding azimuth information and the corresponding elevation information relative to the coordinate system.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates an identifier associated with each pair between the elevation information and the azimuth information of the coordinate system.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control information indicates an identifier of a set of multiple angular regions from the second network node relative to the coordinate system.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control information indicating a number of the one or more historical beam pairs for inclusion in the historical beam pair information.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more historical beam pairs include a respective historical beam pair for each combination of the set of multiple transmit beams and the set of multiple receive beams.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes a matrix having a set of multiple elements, wherein each respective element in the set of multiple elements corresponds to respective actual measurement information of a respective historical beam pair in the one or more respective beam pairs.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of multiple elements includes one or more empty entries that lack actual measurement information.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more historical beam pairs include a threshold number of historical beam pairs.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes a bitmap indicating coordinates of the coordinate system and corresponding historical measurements of the one or more historical beam pairs, the bitmap having a length corresponding to the total number of coordinates of the coordinate system.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmit beam, and actual measurement values ​​associated with the first identifier and the second identifier.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the historical beam pair information may include operations, features, components, or instructions for receiving the historical beam pair information via uplink control information, a CSI report, a MAC control element, or an RRC message.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the corresponding actual measurement information includes a reference signal received power measurement, a signal-to-noise-plus-interference measurement, or both. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1An aspect of a wireless communication system supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figure 2 An aspect of a wireless communication system supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figure 3 An aspect of a historical beam pair reporting scheme supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 4 An aspect of a process flow supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0045] Figure 5 and Figure 6 A block diagram illustrating an apparatus supporting beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 7 A block diagram illustrating a communication manager at a network entity supporting beam pair prediction using coordinate-based matrix reporting in accordance with one or more aspects of the present disclosure is illustrated.

[0047] Figure 8 A diagram illustrating a system including a device supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0048] Figure 9 and Figure 10 A block diagram illustrating an apparatus supporting beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure is illustrated.

[0049] Figure 11 A block diagram illustrating a communication manager at a network entity supporting beam pair prediction using coordinate-based matrix reporting in accordance with one or more aspects of the present disclosure is illustrated.

[0050] Figure 12 A diagram illustrating a system including a device supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated.

[0051] Figures 13 to 16Illustrated is a flow chart illustrating a method for supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0052] A wireless communication system may use artificial intelligence or machine learning to support wireless communication. For example, a network node of a wireless communication system, such as a user equipment (UE) or a network entity, may use artificial intelligence or machine learning to perform beam prediction. In some aspects, the network node may perform downlink transmit beam prediction, downlink receive beam prediction, or beam pair prediction, where a beam pair includes a downlink transmit beam (e.g., of a network entity) and a downlink receive beam (e.g., of a UE). Beam pair prediction may be performed by the UE or the network entity. For UE-side beam pair prediction, the UE may receive and measure signals from the network entity and predict which downlink receive beams and downlink transmit beams (e.g., as a pair) may have the highest measurement or strongest quality. For network-side beam pair prediction, the network entity may need some information related to the UE-side receive beam to perform beam pair prediction. However, the current system does not support the UE indicating sufficient UE-side receive beam information for the network entity to perform beam pair prediction.

[0053] The present disclosure provides techniques for network-side beam pair prediction, and more specifically, provides techniques for UE to indicate receive beam information to support network-side beam pair prediction. The UE may divide the angular space from the UE into a grid or a coordinate system, which is divided into both azimuth and elevation. Each angular region from the UE (e.g., corresponding to elevation and azimuth) may be assigned an identifier. In some aspects, the UE may have receive beam identifiers for different receive beams at the UE. Thus, the combination of the receive beam identifier and the UE orientation may correspond to an identifier on a grid. The UE may report an identifier associated with the grid to support network-side beam pair prediction.

[0054] For example, the UE may use one or more receive beams to receive a signal from a network entity, and the network entity may use one or more transmit beams of the network entity to transmit a signal. The UE may perform signal measurement to obtain measurements of beam pairs between the one or more receive beams and the one or more transmit beams. The UE may report historical beam pair information having actual measurement information for each of the one or more historical beam pairs to the network entity. The historical beam pair information may indicate azimuth information and elevation information for the receive beam of each historical beam pair. The azimuth information and elevation information may be based on a grid or coordinate system of the UE. For example, the historical beam pair information may include a matrix in which each row corresponds to a different receive beam (e.g., using an identifier of a grid) and each column corresponds to a different transmit beam (e.g., using a transmit beam identifier or index). The value of each entry of the matrix may be measurement information for a beam pair corresponding to a receive beam (e.g., a row) and a transmit beam (e.g., a column). In some aspects, the historical beam pair information may indicate a measurement value for a beam pair, an identifier of a receive beam for the beam pair, and an identifier of a transmit beam for the beam pair. For example, the UE may report measurement information for a configured number of historical beam pairs, such as the K beam pairs with the strongest or highest measurements.

[0055] The network entity may receive historical beam pair information and use the historical beam pair information to identify a predicted beam pair. For example, the network entity may input the historical beam pair information into a machine learning model to obtain a predicted beam pair having the highest quality including a predicted transmit beam and a predicted receive beam. The network entity may send predicted beam pair information indicating one or more predicted beam pairs to the UE. In some aspects, the UE and the network entity may (e.g., at a later point in time) communicate using the predicted transmit beam and the predicted receive beam of one of the predicted beam pairs.

[0056] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to beam pair prediction using coordinate-based matrix reporting at a network entity.

[0057] Figure 1 An aspect of a wireless communication system 100 that supports beam pair prediction using coordinate-based matrix reporting at a network entity 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 aspects, 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.

[0058] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various aspects, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, network equipment, and the like. In some aspects, 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 entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an aspect of a geographic area over which the network entities 105 and the UEs 115 may support communication of signals according to one or more radio access technologies (RATs).

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

[0060] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, a device, an apparatus, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc., may include disclosure of the UE, base station, apparatus, device, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded upon according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of the narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more components, or a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0061] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of the other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this aspect, and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0062] In some aspects, the network entities 105 may communicate with the core network 130, with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some aspects, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), either directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some aspects, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 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 .

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

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

[0065] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at the CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between the CU 160 and 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 aspects, the CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). 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 the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the 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 CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some aspects, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via such communication links.

[0066] 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 the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. 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., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some aspects, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0067] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between the IAB node 104 and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case 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 F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a 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 part of a backhaul link).

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

[0069] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, 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 to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal the transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. That is, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0070] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support beam pair prediction using coordinate-based matrix reporting at a network entity as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

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

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

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

[0077] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may 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 may increase the data rate or data integrity used for communication with UE 115.

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

[0079] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of 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., in the range of 0 to 1023).

[0080] 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 aspects, 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 the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0081] A subframe, 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 Transmit Time Interval (TTI). In some aspects, 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 bursts of shortened TTIs (sTTIs)).

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

[0083] The network entity 105 may 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" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish between adjacent cells. In some aspects, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors, such as the capabilities of the network entity 105, such cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, etc.

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

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

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

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

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

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

[0090] 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 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 functionality 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.

[0091] In some aspects, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some aspects, one or more UEs 115 in a group performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication as configured (e.g., scheduled) by the network entity 105. In some aspects, one or more UEs 115 in such a group may be outside of 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 aspects, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some aspects, the network entity 105 may facilitate scheduling of resources for D2D communications. In some other aspects, D2D communications may be performed between UEs 115 without involving the network entity 105.

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

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

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

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

[0096] The wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may utilize an unlicensed band (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ License Assisted Access (LAA), LTE 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 conflict detection and avoidance. In some aspects, operations using the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using a licensed band. Operations using the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0097] A network entity 105 (e.g., a base station 140, a RU 170) or a UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, 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 operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some aspects, 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 multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

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

[0099] 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., a network entity 105, a 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 antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments 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).

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

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

[0102] In some aspects, transmission by a device (e.g., by a network entity 105 or a UE 115) may be performed 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 the network entity 105 to the UE 115). The 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 subbands. The network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port-selective codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

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

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

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

[0106] A wireless communication system, such as wireless communication system 100, may use artificial intelligence or machine learning to support wireless communication. For example, a network node of the wireless communication system, such as UE 115 or network entity 105, may use artificial intelligence or machine learning to perform beam prediction. In some aspects, the network node may perform downlink transmit beam prediction, downlink receive beam prediction, or beam pair prediction, where a beam pair includes a downlink transmit beam (e.g., of network entity 105) and a downlink receive beam (e.g., of UE 115). Beam pair prediction may be performed by UE 115 or network entity 105. For UE-side beam pair prediction, UE 115 may receive and measure signals from network entity 105 and predict which downlink receive beam and downlink transmit beam (e.g., as a pair) may have the highest measurement or strongest quality. For network-side beam pair prediction, network entity 105 may require some information related to the UE-side receive beam to perform beam pair prediction. However, some systems may not support signaling for the UE 115 to indicate sufficient UE-side receive beam information for the network entity 105 to perform beam pair prediction.

[0107] In some aspects, or in some systems, to support network-side beam prediction, the UE 115 may indicate a receiver-side beam identifier to the network entity 105. However, in some aspects, the receiver-side beam identifier may not objectively correspond to a physical direction or shape and may be relative to the UE 115 or the orientation of the UE 115. In some aspects, the UE 115 may indicate a receive beam angle. However, the receive beam at the UE 115 may have a complex beam shape and may not follow a DFT-like structure and, therefore, may not support definable indications of beam properties such as boresight direction, beamwidth, etc. Additionally, reporting the receive beam angle may require significant overhead at the UE 115. For example, if the local beam boresight direction relative to the antenna panels of the UE 115 is reported, the UE 115 may also report the angle faced relative to each antenna panel, the number and relative placement of the antenna panels, and the UE orientation information.

[0108] Wireless communication systems described herein, such as wireless communication system 100, support techniques for reporting UE-side receive beam information and historical beam pair information using an angle grid based on a global coordinate system (GCS). These techniques can reduce the complexity and overhead of reporting receive beam information because the reported information can be unaccompanied by UE panel information or orientation information. In some aspects, UE 115 can map a combination of a receive beam identifier and the UE's orientation to a point in a GCS-based grid.

[0109] UE 115 may divide the angular space (e.g., around UE 115) into a grid or coordinate system. For example, the grid may be divided in both azimuth and elevation. In one example, if a grid has 10 different elevations and 20 different azimuths (e.g., each azimuth covers 18 degrees of azimuth), there may be 200 different angular regions from the UE. In some aspects, each angular region of the grid may be assigned an identifier. If the center of a receive beam points to the middle of an angular region, the receive beam may be associated with the identifier of the angular region. In some aspects, based on the azimuth and elevation granularity, there may be multiple receive beams corresponding to one angular region. However, each receive beam may correspond to one angular region (e.g., rather than one receive beam corresponding to two separate angular regions). In some aspects, the divided angular space from UE 115 may be referred to interchangeably as a grid or a coordinate system.

[0110] In some aspects, the characteristics of the grid may be configured by the network entity 105. For example, the network entity 105 may send control information to the UE 115 that configures the characteristics of the grid or angular region from the UE 115. In some aspects, the network entity 105 may configure the resolution or granularity of the azimuth or elevation angles or both. In some aspects, the network entity 105 may configure an identifier for each angular region in the grid.

[0111] The combination of the receive beam identifier and the UE orientation may correspond to or result in a given identifier in a grid. For example, UE 115 may have receive beam identifiers or information for different receive beams at UE 115, and UE 115 may use the receive beam identifiers together with the orientation of UE 115 to determine a grid identifier corresponding to the receive beam identifier. For example, UE 115 may perform a transformation or mapping between the receive beam of UE 115 and an identifier of a grid or a point on the grid. In the case of a GCS-based approach, the UE receive beam identifier, receive beam boresight direction, UE panel information, UE orientation information, and other UE-specific information may be transparent to network entity 105.

[0112] UE 115 may receive signals from network entity 105 and obtain beam pair measurements based on the signals. For example, network entity 105 may transmit a set of signals using a set of transmit beams of network entity 105. UE 115 may receive signals using a set of receive beams of UE 115, and UE 115 may determine beam pair information including measurement values ​​for one or more beam pairs (e.g., including transmit beams in the set of transmit beams and receive beams in the set of receive beams). UE 115 may send historical beam pair information including actual measurement information for the one or more beam pairs to network entity 105. For at least each beam pair having actual measurement information, UE 115 may indicate (e.g., implicitly or explicitly) an identifier corresponding to the receive beam in the beam pair on a grid. The network entity 105 may receive the historical beam pair information and, based on an identifier associated with the grid, may obtain measurement information for the historical beam pairs, the measurement information including information associated with a receive beam used by the UE 115 to obtain measurement information for each historical beam pair. The network entity 105 may use the historical beam pair information (such as by inputting the historical beam pair information into a machine learning model) to perform network-side beam pair prediction. In some aspects, the network entity 105 may send an indication of a predicted beam pair including a predicted transmit beam and a predicted receive beam to the UE 115.

[0113] Figure 2An aspect of a wireless communication system 200 that supports beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be respective examples of a UE 115 and a network entity 105 as described herein. In some aspects, the UE 115-a or the network entity 105-a may be an example of a network node, such as a first network node or a second network node.

[0114] The wireless communication system 200 may support the use of artificial intelligence or machine learning for various aspects of wireless communication. For example, the UE 115-a or the network entity 105-a, or both, may use artificial intelligence or machine learning to perform beam prediction. In some aspects, the UE 115-a or the network entity 105-a may perform downlink transmit beam prediction, downlink receive beam prediction, or beam pair prediction, where a beam pair includes a downlink transmit beam 205 (e.g., of the network entity 105-a) and a downlink receive beam 210 (e.g., of the UE 115-a).

[0115] The wireless communication system 200 may support techniques for reporting UE-side receive beam information and historical beam pair information using a GCS-based angular grid or coordinate system. The UE 115-a may divide the angular space 215 (e.g., around the UE 115) into a grid or coordinate system. For example, the grid may be divided into both azimuth and elevation. If the grid has 10 different elevation angles and 20 different azimuth angles (e.g., each azimuth angle covers 18 degrees of azimuth), there may be 200 different angular regions from the UE 115-a. In one example, the angular region 230-a may have an azimuth angle 220 and an elevation angle 225. Other portions of the angular space 215 around the UE 115-a may be similarly divided into other angular regions, each angular region being associated with an azimuth angle and an elevation angle.

[0116] In some aspects, each angular region of the grid may be assigned an identifier. For example, angular region 230-a may be associated with a first identifier, and a different angular region may be associated with a second identifier. In some aspects, each angular region may be associated with an objective direction that may not be based on the UE orientation.

[0117] In some aspects, there may be multiple receive beams corresponding to one angular region based on azimuth and elevation granularity. However, each receive beam may correspond to one angular region (e.g., rather than one receive beam corresponding to two separate angular regions). In some aspects, the divided angular space from UE 115-a may be interchangeably referred to as a grid or a coordinate system.

[0118] In some aspects, the characteristics of the grid may be configured by the network entity 105-a. For example, the network entity 105-a may send control information to the UE 115-a that configures the characteristics of the grid or angular region from the UE 115-a. In some aspects, the network entity 105-a may configure the resolution or granularity of the azimuth or elevation angles, or both. In some aspects, the network entity 105 may configure an identifier for each angular region in the grid. The network entity 105-a may send the control information via a control message, such as a downlink control information message, a MAC message or MAC control element, or an RRC message.

[0119] The combination of the receive beam identifier and the UE orientation may correspond to or result in a given identifier in a grid. For example, UE 115-a may have receive beam identifiers or information for different receive beams at UE 115-a, and UE 115-a may use the receive beam identifier together with the orientation of UE 115-a to determine a grid identifier corresponding to the receive beam identifier. For example, UE 115-a may perform a transformation or mapping between the receive beam of UE 115-a and an identifier of a grid or a point on the grid. In the case of a GCS-based approach, the UE receive beam identifier, receive beam boresight direction, UE panel information, UE orientation information, and other information specific to UE 115-a may be transparent to network entity 105.

[0120] If the center of a receive beam spot is within an angular region, then based on the orientation of UE 115-a, the receive beam may be associated with an identifier for the angular region. For example, given the orientation of UE 115-a, receive beam 210-a may be directed toward angular region 230-a. When UE 115-a is at that orientation and receive beam 210-a is directed toward angular region 230-a, receive beam 210-a may be associated with angular region 230. In some aspects, the grid or coordinate system may be objectively configured based on azimuth and elevation. For example, if UE 115-a rotates, receive beam 210-a may no longer be directed toward angular region 230-a, but may be directed toward a different angular region.

[0121] UE 115-a may report historical beam pair information to network entity 105-a, and the historical beam pair information may indicate a receive beam of UE 115-a based on a grid or coordinate system. For example, UE 115-a may receive signals from network entity 105-a and obtain beam pair measurements based on these signals. In some aspects, CSI-RS or SSB may be examples of signals. Network entity 105 may transmit a set of signals using a set of transmit beams 205 of network entity 105-a. UE 115-a may receive signals using a set of receive beams 210 of UE 115-a, and UE 115-a may determine beam pair information including measurement values ​​for one or more beam pairs (e.g., including transmit beams in the set of transmit beams and receive beams in the set of receive beams). In one example, UE 115 - a may use receive beam 210 - a to receive and measure a reference signal sent by network entity 105 - a using transmit beam 205 - a .

[0122] UE 115-a may send historical beam pair information including actual measurement information of one or more beam pairs to network entity 105. For at least each beam pair having actual measurement information, UE 115-a may indicate (e.g., implicitly or explicitly) an identifier of an angular region associated with a receive beam in the beam pair on a grid. For example, UE 115-a may have measurement values ​​for at least a first beam pair including receive beam 210-a and transmit beam 205-a. UE 115-a may send historical beam pair information including the measurement value of the first beam pair, an identifier of angular region 230-a, and an identifier of transmit beam 205-a.

[0123] In some aspects, UE 115-a may form a matrix of beam pair measurements, and the historical beam pair information may be based on the matrix. The number of rows in the matrix may be based on the quantized size of the grid at UE 115-a, such as corresponding to the number of angular regions 230 in the grid. For example, the rows of the matrix may correspond to identifiers on the grid, with each row associated with a different angular region having a corresponding azimuth (e.g., azimuth information) and a corresponding elevation (e.g., elevation information). The columns of the matrix may correspond to different transmit beam identifiers. Thus, the entries of the matrix may represent all possible beam pairs between the transmit beam 205 of the network entity 105-a and the angular regions 230 of the grid or coordinate system of the UE 115-a.

[0124] The entries of the matrix may include measurement values ​​for beam pairs corresponding to the grid identifier and the transmit beam identifier. For example, in the row of the matrix associated with the identifier of the angular region 230-a, and at the column of the matrix associated with the identifier of the transmit beam 205-a, the UE 115-a may store measurement values ​​for the beam pair of the receive beam 210-a (or the angular region 230-a) and the transmit beam 205-a. In some aspects, the matrix may be a sparse matrix. For example, in some cases, the UE 115-a may obtain measurement information for fewer than all possible beam pairs. Reference Figure 3 This matrix and additional examples of historical beam pair reports are described in more detail.

[0125] In some aspects, the UE 115-a may report measurement values ​​for a configured number of historical beam pairs. For example, the UE 115-a may report or may be configured to report measurement values ​​for the top K beam pairs. That is, the UE 115-a may report measurement values ​​for K beam pairs, where each of the K beam pairs has the highest measurement value (e.g., the highest reference signal received power (RSRP) or signal to interference plus noise ratio (SINR) measurement) among the measured beam pairs. In some aspects, the network entity 105-a may configure the value of K. For example, the network entity 105-a may configure the UE 115-a to report measurement values ​​for the top K beam pairs via control signaling.

[0126] In some aspects, such as if the UE 115-a is to report measurements for a configured number of beam pairs, the UE 115-a may report some information of the matrix without reporting the entire matrix. For example, the UE 115-a may report the K entries of the matrix with the highest measurement values. The UE 115-a may indicate the measurement value, a row identifier associated with the measurement value, and a column identifier associated with the measurement value. For example, the row identifier may correspond to an identifier of an angular region 230 on a grid or azimuth information and elevation information associated with the angular region 230 on the grid. The column identifier may correspond to a transmit beam 205 of the network entity 105-a. Using the measurement value, row identifier, and column identifier, the UE 115-a may report measurements of the beam pair, as well as indicate the transmit beam and receive beam in the beam pair. The UE 115-a may use this information for multiple different beam pairs to report historical beam pair information.

[0127] In some aspects, the UE 115-a may index the matrix based on a row index and a column index. For example, for each of the first K elements, the format of the reported index and value in the historical beam pair information may follow (row index, column index, measurement value). The format may indicate an identifier of the angular region 230 associated with the beam pair on the grid, an identifier of the transmit beam 205 associated with the beam pair, and a measurement value for the beam pair (e.g., an RSRP measurement value or an SINR measurement value). In some aspects, the UE 115-a may report differential measurement values ​​(e.g., differential RSRP values) of the first K elements of the matrix to reduce overhead. For example, in some cases, the historical beam pair information may include a first measurement value for a first beam pair, and the measurement value for the additional beam pair may be a differential or difference from the first measurement of the first beam pair.

[0128] In some aspects, the UE 115-a may index the matrix using row-first indexing or column-first indexing. For example, for each of the first K elements, the format of the reported index and value in the historical beam pair information may be (row-first / column-first matrix index, measurement value), such that the UE uses one identifier to indicate both the row and column of the matrix. In the example of a matrix with eight rows and six columns, to indicate the matrix entry in the first row and third column (e.g., using zero-based numbering), the UE 115-a may use row-first indexing to indicate the identifier "8" or use column-first indexing to indicate the identifier "17."

[0129] In some aspects, UE 115-a may include a bitmap in the historical beam pair information. The bitmap may have a number of bit entries that matches the number of entries in the matrix. The indices with the first K elements in the matrix may be set to "1" in the bitmap, and the corresponding measurement values ​​may be included in a predefined or configured order.

[0130] In some aspects, to populate the matrix, the UE 115-a may map the receive beams 210 to a grid of angular regions 230 surrounding the UE 115-a. For example, the UE 115-a may map the receive beams 210 to a GCS quantized angular grid. In some aspects, the UE 115-a may convert the beam boresight direction of the used receive beams into an identifier of the grid surrounding the UE 115-a. For example, the UE 115-a may convert the beam boresight of the used receive beams into a grid identifier and enter the measured RSRP for the corresponding UE receive beam in the associated matrix element. In some cases, it may be a one-to-one mapping between UE receive beams and grid identifiers.

[0131] The network entity 105-a may receive historical beam pair information from the UE 115-a. In some examples, the UE 115-a may send the historical beam pair information via an uplink control information message, a CSI report, or both. In some examples, to reduce overhead, the UE 115-a may only report beam pair identifiers of historical beam pairs, such as beam pair identifiers of the top K historical beam pairs. Additionally or alternatively, the UE 115-a may report historical beam pair information via a MAC message, a MAC control element, or an RRC message. In some cases, the network entity 105-a may input the historical beam pair information into a machine learning model to perform network-side beam pair prediction. Based on the historical beam pair information, the network entity 105-a may identify the receive beam of the beam pair, or the angular region 230 associated with the beam pair, the transmit beam of the beam pair, and corresponding measurements of the beam pair.

[0132] In some aspects, the network entity 105-a may send an indication of the predicted beam pairs to the UE 115. For example, the network entity 105-a may indicate one or more predicted beam pairs, each predicted beam pair including a predicted transmit beam and a corresponding predicted receive beam. For example, based on a matrix used by the UE 115-a for historical beam pair information, the network entity 105-a may indicate entries of the matrix associated with predicted receive beams and predicted transmit beams. For example, the rows of the entries may correspond to the predicted receive beams, and the columns of the entries may correspond to the predicted transmit beams. Based on the predicted identifiers of the grid at the UE 115-a, the UE 115-a may determine an appropriate receive beam 210 to be used in a future time slot (e.g., a future time slot).

[0133] The UE 115-a may convert an identifier of a grid for a predicted beam pair indication into a UE receive beam based on a mapping between the grid identifier and the UE receive beam. For example, after the UE 115-a receives an indication of a predicted beam pair, the UE 115-a may convert the grid identifier into a receive beam 210 for each predicted beam pair in one or more predicted beam pairs. The mapping between the grid identifier and the receive beam 210 may be a one-to-many mapping because the grid identifier may correspond to all receive beams 210 having beam boresight directions in the indicated angular region of the quantized grid. In some aspects, the network entity 105-a may configure the granularity or resolution of the grid (e.g., in azimuth and elevation) to limit the number of possible mappings.

[0134] Figure 3 Illustrated is an aspect of a historical beam pair reporting scheme 300 supporting beam pair prediction using coordinate-based matrix reporting at a network entity in accordance with one or more aspects of the present disclosure.

[0135] The UE 115 may send historical beam pair information to the network entity 105 to assist the network entity 105 in performing network-side beam pair prediction. For example, the UE 115 may send one or more historical beam pair reports 305. Each historical beam pair report may include actual measurement information of one or more historical beam pairs having a corresponding receive beam (e.g., of the UE 115) and a corresponding transmit beam (e.g., of the network entity 105).

[0136] In some aspects, UE 115 may generate a matrix of measurement values ​​for historical beam pairs. For example, the rows in the matrix may correspond to receive grid identifiers 310, and the columns in the matrix may correspond to transmit beam identifiers 315. In some aspects, receive grid identifier 310 may be an example of an identifier for an angle grid at UE 115, with each angular region of the angle grid being associated with azimuth information and elevation information. Each entry of the matrix may have measurement information, such as an RSRP measurement or an SINR measurement, for a beam pair corresponding to the grid identifier and the transmit beam identifier.

[0137] In some aspects, the UE 115 may send historical beam pair information indicating the values ​​of the entire matrix or all entries of the matrix. In some cases, the matrix may be a sparse matrix such that one or more entries of the matrix do not have data or one or more entries are null entries.

[0138] In some aspects, the UE 115 may report actual measurement information for a configured number of historical beam pairs. For example, the UE 115 may report elements 320 of the K historical beam pairs with the highest measurements. The UE 115 may use the reference Figure 2 The UE 115-a may report historical beam pair information using techniques described in more detail herein. For example, the UE 115 may report, for each reported historical beam pair, a row index, a column index, and a measurement value for each reported historical beam pair. In some other examples, the UE 115-a may report, for each reported historical beam pair, a single identifier and a measurement value for the historical beam pair to indicate both the transmit beam and the receive beam of the historical beam pair (e.g., using row-first indexing or column-first indexing). In some aspects, the UE 115-a may indicate a bitmap corresponding to different possible historical beam pairs and the measurement values ​​corresponding to the bitmap in a configured or known order.

[0139] The network entity 105 may receive one or more historical beam pair reports 305 and input information from the historical beam pair reports into the machine learning model 325. The machine learning model 325 may output one or more predicted beam pairs based on the one or more historical beam pair reports 305. In some aspects, the machine learning model may output a predicted beam pair matrix 330. Elements of the predicted beam pair matrix may correspond to beam pairs with predicted high quality or signal strength. For example, columns of matrix entries with high values ​​may correspond to predicted transmit beams in a predicted beam pair, and rows of matrix entries may correspond to predicted receive beams in a predicted beam pair.

[0140] In some aspects, the network entity 105 may indicate the predicted beam pairs to the UE 115. For example, the network entity 105 may send an indication of the predicted beam pair matrix 330 to the UE 115. The UE 115 may receive information associated with the predicted beam pairs and identify the predicted receive beam to be used in a later time slot. In some cases, the network entity 105 may indicate the row and column of the entries in the predicted beam pair matrix 330 to the UE 115, and the UE 115 may identify which receive beam to use based on the indicated row. For example, the UE 115 may identify the predicted beam pair with the highest predicted measurement and transform the row or grid identifier of the predicted beam pair into a receive beam at the UE 115.

[0141] Figure 4 An aspect of a process flow 400 for supporting beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure is illustrated. The process flow 400 may be implemented by a UE 115-b or a network entity 105-b, or both. The UE 115-b may be a Figures 1 to 3 The example of UE 115 described, and the network entity 105-b may be as shown in reference Figures 1 to 3 In some aspects, the UE 115-b or the network entity 105-b may be an example of a network node such as a first network node or a second network node. In some aspects, some of the processes or signaling of the process flow 400 may be as described above. Figure 4 In some cases, some additional processes or signaling may occur, or some of the processes or signaling shown may not occur, or both.

[0142] In some examples, the network entity 105-b may send control information at 405 to configure the grid or coordinate system of the UE 115-b. Figure 2The characteristics of the described grid of the coordinate system may be configured by network entity 105-b. In some examples, network entity 105-b may transmit control information indicating corresponding azimuth information and corresponding elevation information relative to the coordinate system. For example, the control information may indicate an identifier associated with each pair of elevation information and azimuth information for the coordinate system. In some examples, the control information may indicate an identifier for each of a plurality of angular regions of the grid or coordinate system. In some examples, the control information may indicate a resolution or granularity of the corresponding azimuth and elevation information for the grid or coordinate system.

[0143] At 410, the network entity 105-b may transmit a set of multiple signals to the UE 115-b via a set of multiple transmit beams. The UE 115-b may receive the set of multiple signals via a set of multiple receive beams. In some aspects, the set of multiple signals may include a set of multiple CSI-RSs. In some aspects, the set of multiple signals may include a set of multiple SSBs.

[0144] UE 115-b may measure the signal and obtain actual measurement information for one or more beam pairs. Each of the one or more beam pairs may include a receive beam of UE 115-b and a transmit beam of network entity 105-b.

[0145] In some aspects, UE 115-b may divide the angular space from UE 115-b into a grid or coordinate system. For example, the angular space from UE 115-b may be split into a plurality of angular regions, each angular region having a corresponding azimuth and elevation angle. In some aspects, UE 115-b may map or transform the receive beam of UE 115-b to the angular regions of the grid or coordinate system based on the orientation of UE 115-b and the receive beam of UE 115-b.

[0146] In some aspects, the network entity 105-b may configure a coordinate system or grid at the UE 115-b. For example, the network entity 105-b may send control information indicating corresponding azimuth information and corresponding elevation information relative to the coordinate system. In some aspects, the network entity 105-b may configure an identifier, such as a grid identifier, for each pair of elevation information and azimuth information of the coordinate system. For example, the network entity 105-b may configure an identifier for each angular region of the grid or coordinate system. Additionally or alternatively, the network entity 105-b may configure the granularity or resolution of the azimuth information and elevation information of the grid or coordinate system.

[0147] At 415, UE 115-b may send historical beam pair information, which includes corresponding actual measurement information corresponding to each historical beam pair in one or more historical beam pairs. Each historical beam pair in the one or more historical beam pairs may include a corresponding transmit beam from a set of multiple transmit beams of network entity 105-b and a corresponding historical receive beam from a set of multiple receive beams of UE 115-b. The historical beam pair information may indicate corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs. For example, the corresponding azimuth information and the corresponding elevation information may be based on a coordinate system of the first network node. In some aspects, the corresponding azimuth information and the corresponding elevation information for each corresponding historical receive beam are based on an orientation of the first network node and a receive beam identifier corresponding to the corresponding historical receive beam.

[0148] In some aspects, the one or more historical beam pairs may include a corresponding historical beam pair for each combination of a plurality of transmit beams and a plurality of receive beams. For example, the historical beam pair information may include measurement information for each combination of a transmit beam and a receive beam. In some aspects, the UE 115-b may generate a matrix of historical beam pair measurements, and the UE 115-b may report the matrix or information of the matrix to the network entity 105-b. For example, the historical beam pair information may include a matrix having a plurality of elements (e.g., entries of the matrix), wherein each respective element of the plurality of elements corresponds to respective actual measurement information for a respective historical beam pair in the one or more respective beam pairs.

[0149] In some cases, the one or more historical beam pairs include a threshold number of historical beam pairs. For example, UE 115-b may report the top K measurements to reduce the overhead of reporting historical beam pair information. In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam. For example, UE 115-b may indicate a column-first identifier or a row-first identifier for a matrix entry for each historical beam pair.

[0150] In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmit beam, and actual measurement values ​​associated with the first identifier and the second identifier. For example, UE 115-b may report a row identifier, a column identifier, and the measurement value for each historical beam pair. In some aspects, the historical beam pair information includes a bitmap indicating coordinates of a coordinate system and corresponding historical measurement values ​​for the one or more historical beam pairs, the bitmap having a length corresponding to the total number of coordinates of the coordinate system.

[0151] At 420, the network entity 105-b may perform beam pair prediction based on the historical beam pair information. For example, the network entity 105-b may input the historical beam pair information into a machine learning model to obtain predicted beam pair information. In some aspects, the machine learning model may output a predicted beam pair matrix indicating one or more predicted strong beam pairs for a later time slot.

[0152] At 425, the network entity 105-b may send predicted beam pair information based on the historical beam pair information to the UE 115-b. The predicted beam pair information indicates one or more predicted beam pairs, each including a predicted transmit beam and a predicted receive beam. In some aspects, the predicted receive beam may be associated with a coordinate system at the UE 115-b. For example, the predicted beam pair information may indicate an identifier of a grid or coordinate system corresponding to an angular region from the UE 115-b. The UE 115-b may identify one or more receive beams corresponding to the indicated identifier of the grid or coordinate system and use one of the corresponding receive beams to communicate in a later time slot.

[0153] Figure 5 A block diagram 500 illustrates a device 505 that supports beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure. The device 505 can be an example of aspects of the UE 115 as described herein. The device 505 can include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0154] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to beam pair prediction using coordinate-based matrix reporting at a network entity). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0155] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction using coordinate-based matrix reporting at a network entity, data channels, information channels). In some aspects, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0156] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0160] According to examples disclosed herein, a communication manager 520 may support wireless communications at a first network node. For example, the communication manager 520 may be configured to or otherwise support components for receiving a set of multiple signals via a set of multiple receive beams. The communication manager 520 may be configured to or otherwise support components for transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams of a second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The communication manager 520 may be configured to or otherwise support components for receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node.

[0161] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof or otherwise coupled thereto) can support techniques for reducing processing by supporting network-side beam prediction. Additionally, these techniques can reduce overhead and power consumption by efficiently reporting UE receive beam information.

[0162] Figure 6 A block diagram 600 illustrates a device 605 that supports beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure. The device 605 can be an example of aspects of the device 505 or UE 115 as described herein. The device 605 can include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0163] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to beam pair prediction using coordinate-based matrix reporting at a network entity). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0164] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction using coordinate-based matrix reporting at a network entity, data channels, information channels). In some aspects, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0165] Device 605 or its various components may be examples of means for performing various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein. For example, communication manager 620 may include a signal receiving component 625, a beam pair information indicating component 630, a predicted beam pair information component 635, or any combination thereof. Communication manager 620 may be an example of aspects of communication manager 520 as described herein. In some aspects, communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0166] According to examples disclosed herein, a communication manager 620 can support wireless communications at a first network node. A signal receiving component 625 can be configured to or otherwise support means for receiving a set of multiple signals via a set of multiple receive beams. A beam pair information indicating component 630 can be configured to or otherwise support means for transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of a second network node and a corresponding historical receive beam from a set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The predicted beam pair information component 635 may be configured as or otherwise support a component for receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node.

[0167] Figure 7 A block diagram 700 illustrates a communication manager 720 that supports beam pair prediction using coordinate-based matrix reporting at a network entity, in accordance with one or more aspects of the present disclosure. The communication manager 720 can be an example of aspects of the communication manager 520, the communication manager 620, or both, as described herein. The communication manager 720 or its various components can be examples of means for performing various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity, as described herein. For example, the communication manager 720 can include a signal receiving component 725, a beam pair information indicating component 730, a predicted beam pair information component 735, a coordinate system configuration component 740, a beam pair report configuration component 745, or any combination thereof. Each of these components can communicate with each other, directly or indirectly (e.g., via one or more buses).

[0168] According to examples disclosed herein, a communication manager 720 can support wireless communications at a first network node. A signal receiving component 725 can be configured to or otherwise support means for receiving a set of multiple signals via a set of multiple receive beams. A beam pair information indicating component 730 can be configured to or otherwise support means for transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of a second network node and a corresponding historical receive beam from a set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The predicted beam pair information component 735 may be configured as or otherwise support a component for receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node.

[0169] In some aspects, coordinate system configuration component 740 may be configured as or otherwise support means for receiving control information indicative of respective azimuth information and respective elevation information relative to a coordinate system.

[0170] In some aspects, the control information indicates an identifier associated with each pair between elevation information and azimuth information of the coordinate system.

[0171] In some aspects, the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0172] In some aspects, the control information indicates an identifier of a set of multiple angular regions of the coordinate system.

[0173] In some aspects, beam pair reporting configuration component 745 may be configured as or otherwise support means for receiving control information indicating a number of one or more historical beam pairs for inclusion in the historical beam pair information.

[0174] In some aspects, the one or more historical beam pairs include a respective historical beam pair for each combination of a set of multiple transmit beams and a set of multiple receive beams.

[0175] In some aspects, the historical beam pair information comprises a matrix having a set of multiple elements, wherein each respective element in the set of multiple elements corresponds to respective actual measurement information of a respective historical beam pair of the one or more respective beam pairs.

[0176] In some aspects, the respective azimuth information and the respective elevation information for each respective historical receive beam are based on an orientation of the first network node and a receive beam identifier corresponding to the respective historical receive beam.

[0177] In some aspects, the one or more historical beam pairs include a threshold number of historical beam pairs.

[0178] In some aspects, the historical beam pair information includes a bitmap indicating coordinates of the coordinate system and corresponding historical measurements of one or more historical beam pairs, the bitmap having a length corresponding to a total number of coordinates of the coordinate system.

[0179] In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, actual measurement values ​​and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0180] In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmit beam, and an actual measurement value associated with the first identifier and the second identifier.

[0181] In some aspects, to support sending historical beam pair information, the beam pair information indicating component 730 may be configured to or otherwise support means for sending historical beam pair information via uplink control information, CSI reports, MAC CEs, or RRC messages.

[0182] In some aspects, predicted beam pair information component 735 may be configured to or otherwise support means for selecting a receive beam for communicating with the second network node based on the predicted beam pair information.

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

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

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

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

[0187] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting beam pair prediction using coordinate-based matrix reporting at a network entity). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, the processor 840 and the memory 830 being configured to perform the various functions described herein.

[0188] According to examples disclosed herein, the communication manager 820 may support wireless communications at a first network node. For example, the communication manager 820 may be configured to or otherwise support components for receiving a set of multiple signals via a set of multiple receive beams. The communication manager 820 may be configured to or otherwise support components for transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams of a second network node and a corresponding historical receive beam from the set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The communication manager 820 may be configured to or otherwise support components for receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node.

[0189] By including or configuring the communication manager 820 according to the examples described herein, the device 805 can support techniques for reducing processing by supporting network-side beam prediction. Additionally, these techniques can reduce overhead and power consumption by efficiently reporting UE receive beam information.

[0190] In some aspects, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0191] Figure 9A block diagram 900 illustrates a device 905 at a network entity that supports beam pair prediction using coordinate-based matrix reporting according to one or more aspects of the present disclosure. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0194] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0198] According to examples disclosed herein, a communication manager 920 may support wireless communications at a first network node. For example, the communication manager 920 may be configured to or otherwise support components for transmitting a set of multiple signals via a set of multiple transmit beams. The communication manager 920 may be configured to or otherwise support components for receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from the set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The communication manager 920 may be configured to or otherwise support components for sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node.

[0199] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or otherwise coupled thereto) can support techniques for reducing processing by supporting network-side beam prediction. For example, by performing network-side beam prediction, measurement procedures and signaling can be reduced. Additionally, these techniques can reduce overhead and power consumption by efficiently reporting UE receive beam information.

[0200] Figure 10 A block diagram 1000 illustrates a device 1005 that supports beam pair prediction using coordinate-based matrix reporting at a network entity according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the device 905 or 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 each other (e.g., via one or more buses).

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

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

[0203] The device 1005 or its various components may be examples of means for performing various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein. For example, the communication manager 1020 may include a signaling component 1025, a historical beam pair information component 1030, a beam pair prediction component 1035, or any combination thereof. The communication manager 1020 may be an example of aspects of the communication manager 920 as described herein. In some aspects, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in conjunction with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0204] According to examples disclosed herein, a communication manager 1020 can support wireless communications at a first network node. A signal transmission component 1025 can be configured to or otherwise support means for transmitting a set of multiple signals via a set of multiple transmit beams. A historical beam pair information component 1030 can be configured to or otherwise support means for receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from the set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The beam pair prediction component 1035 can be configured as or otherwise support a component for sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node.

[0205] Figure 11 A block diagram 1100 illustrates a communication manager 1120 that supports beam pair prediction at a network entity using coordinate-based matrix reporting, in accordance with one or more aspects of the present disclosure. The communication manager 1120 can be an example of aspects of the communication manager 920, the communication manager 1020, or both, as described herein. The communication manager 1120 or its various components can be examples of means for performing various aspects of beam pair prediction at a network entity using coordinate-based matrix reporting, as described herein. For example, the communication manager 1120 can include a signaling component 1125, a historical beam pair information component 1130, a beam pair prediction component 1135, a coordinate system configuration component 1140, a historical beam pair configuration component 1145, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0206] According to examples disclosed herein, a communication manager 1120 can support wireless communications at a first network node. A signal transmission component 1125 can be configured to or otherwise support means for transmitting a set of multiple signals via a set of multiple transmit beams. A historical beam pair information component 1130 can be configured to or otherwise support means for receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from the set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The beam pair prediction component 1135 can be configured as or otherwise support components for sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node.

[0207] In some aspects, coordinate system configuration component 1140 may be configured to or otherwise support means for transmitting control information indicating respective azimuth information and respective elevation information relative to a coordinate system.

[0208] In some aspects, the control information indicates an identifier associated with each pair between elevation information and azimuth information of the coordinate system.

[0209] In some aspects, the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0210] In some aspects, the control information indicates an identifier of a set of a plurality of angular regions from the second network node relative to the coordinate system.

[0211] In some aspects, historical beam pair configuration component 1145 may be configured or otherwise support means for sending control information indicating a number of one or more historical beam pairs for inclusion in the historical beam pair information.

[0212] In some aspects, the one or more historical beam pairs include a respective historical beam pair for each combination of a set of multiple transmit beams and a set of multiple receive beams.

[0213] In some aspects, the historical beam pair information comprises a matrix having a set of multiple elements, wherein each respective element in the set of multiple elements corresponds to respective actual measurement information of a respective historical beam pair of the one or more respective beam pairs.

[0214] In some aspects, the set of multiple elements includes one or more empty entries that lack actual measurement information.

[0215] In some aspects, the one or more historical beam pairs include a threshold number of historical beam pairs.

[0216] In some aspects, the historical beam pair information includes a bitmap indicating coordinates of the coordinate system and corresponding historical measurements of one or more historical beam pairs, the bitmap having a length corresponding to a total number of coordinates of the coordinate system.

[0217] In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, actual measurement values ​​and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0218] In some aspects, the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmit beam, and an actual measurement value associated with the first identifier and the second identifier.

[0219] In some aspects, to support receiving historical beam pair information, the historical beam pair information component 1130 may be configured or otherwise support means for receiving historical beam pair information via uplink control information, CSI reports, MAC CEs, or RRC messages.

[0220] In some aspects, the corresponding actual measurement information includes a reference signal received power measurement, a signal-to-noise-plus-interference measurement, or both.

[0221] Figure 12A diagram illustrates a system 1200 including a device 1205 supporting beam pair prediction at a network entity using coordinate-based matrix reporting, in accordance with one or more aspects of the present disclosure. Device 1205 may be an example of device 905, device 1005, or network entity 105, as described herein, or include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, including communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1205 may include components that support outgoing and incoming communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0222] The transceiver 1210 may support bidirectional communication as described herein via a wired link, a wireless link, or both. In some aspects, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some aspects, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some aspects, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components 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 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip assembly installed in the device 1205. In some aspects, 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).

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

[0224] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting beam pair prediction using coordinate-based matrix reporting at a network entity). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, the processor 1235 and the memory 1225 being configured to perform the various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing the functions of device 1205 (e.g., by executing code 1230). Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within memory 1225). In some implementations, processor 1235 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs (which may be passed to, for example, other systems or components of device 1205). For example, a processing system of device 1205 may refer to a system that includes various other components or subcomponents of device 1205 (such as processor 1235, transceiver 1210, communications manager 1220, or other components or combinations of components of device 1205). The processing system of device 1205 can interface with other components of device 1205 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1205 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, 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 1205 can obtain information or signal input and pass the information to the processing system. A person skilled in the art will readily recognize that a first interface can also obtain information or signal input, and a second interface can also output information or signal output.

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

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

[0227] According to examples disclosed herein, the communication manager 1220 may support wireless communications at a first network node. For example, the communication manager 1220 may be configured to or otherwise support components for transmitting a set of multiple signals via a set of multiple transmit beams. The communication manager 1220 may be configured to or otherwise support components for receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from the set of multiple transmit beams and a corresponding historical receive beam from the set of multiple receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The communication manager 1220 may be configured as or otherwise support components for sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node.

[0228] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 can support techniques for reducing processing by supporting network-side beam prediction. For example, by performing network-side beam prediction, measurement procedures and signaling can be reduced. Additionally, these techniques can reduce overhead and power consumption by efficiently reporting UE receive beam information.

[0229] In some aspects, the communication manager 1220 may be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise coordinating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of beam pair prediction using coordinate-based matrix reporting at a network entity as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0230] Figure 13A flowchart illustrating a method 1300 for beam pair prediction using coordinate-based matrix reporting at a supporting network entity according to one or more aspects of the present disclosure is illustrated. The operations of the method 1300 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE as described in reference to Figures 1 to 8 The described functions may be performed by the UE 115. In some aspects, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0231] At 1305, the method may include receiving a set of multiple signals via a set of multiple receive beams. The operations of 1305 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The signal receiving component 725 described is executed.

[0232] At 1310, the method may include: transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of multiple transmit beams of the second network node and a corresponding historical receive beam from a set of multiple receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The operations of 1310 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1310 may be performed by reference to Figure 7 The beam pair information is described to be performed by component 730 .

[0233] At 1315, the method may include receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node. The operations of 1315 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The described prediction beam pair information component 735 is performed.

[0234] Figure 14 A flowchart illustrating a method 1400 for beam pair prediction using coordinate-based matrix reporting at a supporting network entity according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE as described in reference to Figures 1 to 8 The described functions may be performed by the UE 115. In some aspects, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0235] At 1405, the method may include receiving control information indicating corresponding azimuth information and corresponding elevation information relative to a coordinate system. The operations of 1405 may be performed according to examples disclosed herein. In some aspects, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described coordinate system configuration component 740 is executed.

[0236] At 1410, the method may include receiving a set of multiple signals via a set of multiple receive beams. The operations of 1410 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The signal receiving component 725 described is executed.

[0237] At 1415, the method may include: transmitting historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs includes a corresponding transmit beam from a set of a plurality of transmit beams of the second network node and a corresponding historical receive beam from a set of a plurality of receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node. The operations of 1415 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1415 may be performed by the referenced Figure 7 The beam pair information is described to be performed by component 730 .

[0238] At 1420, the method may include receiving predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the first network node. The operations of 1420 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The described prediction beam pair information component 735 is performed.

[0239] Figure 15A flow chart illustrating a method 1500 for beam pair prediction using coordinate-based matrix reporting at a supporting network entity according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a network entity or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or components thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 In some aspects, 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 various aspects of the described functions.

[0240] At 1505, the method may include transmitting a set of multiple signals via a set of multiple transmit beams. The operations of 1505 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1505 may be performed as described in reference to Figure 11 The signal sending component 1125 is described to perform.

[0241] At 1510, the method may include receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs includes a corresponding transmit beam from a set of a plurality of transmit beams and a corresponding historical receive beam from a set of a plurality of receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The operations of 1510 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1510 may be performed by, for example, a method as described with reference to Figure 11 The described historical beam pair information component 1130 is performed.

[0242] At 1515, the method may include: sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node. The operations of 1515 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1515 may be performed as described in reference to Figure 11 The described beam pair prediction component 1135 is performed.

[0243] Figure 16A flowchart illustrating a method 1600 for beam pair prediction using coordinate-based matrix reporting at a supporting network entity according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 In some aspects, 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 various aspects of the described functions.

[0244] At 1605, the method may include sending control information indicating the number of one or more historical beam pairs included in the historical beam pair information. The operations of 1605 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1605 may be performed as described in reference to Figure 11 The described historical beam pair configuration component 1145 is performed.

[0245] At 1610, the method may include transmitting a set of multiple signals via a set of multiple transmit beams. The operations of 1610 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1610 may be performed as described in reference to Figure 11 The signal sending component 1125 is described to perform.

[0246] At 1615, the method may include receiving historical beam pair information, the historical beam pair information including corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs includes a corresponding transmit beam from a set of a plurality of transmit beams and a corresponding historical receive beam from a set of a plurality of receive beams of the second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node. The operations of 1615 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1615 may be performed by, for example, a method as described with reference to Figure 11 The described historical beam pair information component 1130 is performed.

[0247] At 1620, the method may include: sending predicted beam pair information based on historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on a coordinate system of the second network node. The operations of 1620 may be performed according to the examples disclosed herein. In some aspects, aspects of the operations of 1620 may be performed as described in reference to Figure 11 The described beam pair prediction component 1135 is performed.

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

[0249] Aspect 1: A method for wireless communication at a first network node, the method comprising: receiving multiple signals via multiple receive beams; sending historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs comprises a corresponding transmit beam of a plurality of transmit beams from a second network node and a corresponding historical receive beam from the plurality of receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; and receiving predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each comprising a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

[0250] Aspect 2: The method according to aspect 1, further comprising: receiving control information indicating the corresponding azimuth angle information and the corresponding elevation angle information relative to the coordinate system.

[0251] Aspect 3: The method according to aspect 2, wherein the control information indicates an identifier associated with each pair between the elevation angle information and the azimuth angle information of the coordinate system.

[0252] Aspect 4: The method according to any one of aspects 2 to 3, wherein the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0253] Aspect 5: The method according to any one of aspects 2 to 4, wherein the control information indicates identifiers of a plurality of angular regions of the coordinate system.

[0254] Aspect 6: The method according to any one of aspects 1 to 5, further comprising: receiving control information indicating the number of the one or more historical beam pairs included in the historical beam pair information.

[0255] Aspect 7: The method according to any one of aspects 1 to 6, wherein the one or more historical beam pairs include a corresponding historical beam pair for each combination of the plurality of transmit beams and the plurality of receive beams.

[0256] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the historical beam pair information comprises a matrix having a plurality of elements, wherein each corresponding element of the plurality of elements corresponds to corresponding actual measurement information of a corresponding historical beam pair in the one or more corresponding beam pairs.

[0257] Aspect 9: The method according to any one of aspects 1 to 8, wherein the corresponding azimuth information and the corresponding elevation information of each corresponding historical reception beam are based on the orientation of the first network node and a reception beam identifier corresponding to the corresponding historical reception beam.

[0258] Aspect 10: The method according to any one of aspects 1 to 9, wherein the one or more historical beam pairs include a threshold number of historical beam pairs.

[0259] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the historical beam pair information includes a bitmap indicating the coordinates of the coordinate system and the corresponding historical measurement values ​​of the one or more historical beam pairs, and the bitmap has a length corresponding to the total number of coordinates of the coordinate system.

[0260] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0261] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmitted beam, and an actual measurement value associated with the first identifier and the second identifier.

[0262] Aspect 14: A method according to any one of Aspects 1 to 13, wherein sending the historical beam pair information further comprises: sending the historical beam pair information via uplink control information, channel state information report, medium access control control element or radio resource control message.

[0263] Aspect 15: The method according to any one of aspects 1 to 14, further comprising: selecting a receive beam for communicating with the second network node based on the predicted beam pair information.

[0264] Aspect 16: A method for wireless communication at a first network node, the method comprising: transmitting multiple signals via multiple transmit beams; receiving historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair in one or more historical beam pairs, wherein each historical beam pair in the one or more historical beam pairs comprises a corresponding transmit beam from the multiple transmit beams and a corresponding historical receive beam from a plurality of receive beams of a second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information for each corresponding historical beam pair in the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; and sending predicted beam pair information based on the historical beam pair information, wherein the predicted beam pair information indicates one or more predicted beam pairs each comprising a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

[0265] Aspect 17: The method according to Aspect 16, further comprising: sending control information indicating the corresponding azimuth angle information and the corresponding elevation angle information relative to the coordinate system.

[0266] Aspect 18: The method according to aspect 17, wherein the control information indicates an identifier associated with each pair between the elevation angle information and the azimuth angle information of the coordinate system.

[0267] Aspect 19: The method according to any one of aspects 17 to 18, wherein the control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

[0268] Aspect 20: The method according to any one of aspects 17 to 19, wherein the control information indicates identifiers of a plurality of angular regions from the second network node relative to the coordinate system.

[0269] Aspect 21: The method according to any one of aspects 16 to 20, further comprising: sending control information indicating the number of the one or more historical beam pairs included in the historical beam pair information.

[0270] Aspect 22: The method according to any one of aspects 16 to 21, wherein the one or more historical beam pairs include a corresponding historical beam pair for each combination of the plurality of transmit beams and the plurality of receive beams.

[0271] Aspect 23: The method according to any one of aspects 16 to 22, wherein the historical beam pair information comprises a matrix having a plurality of elements, wherein each corresponding element of the plurality of elements corresponds to corresponding actual measurement information of a corresponding historical beam pair in the one or more corresponding beam pairs

[0272] Aspect 24: The method according to aspect 23, wherein the plurality of elements includes one or more empty entries lacking actual measurement information.

[0273] Aspect 25: The method according to any one of aspects 16 to 24, wherein the one or more historical beam pairs include a threshold number of historical beam pairs.

[0274] Aspect 26: A method according to any one of Aspects 16 to 25, wherein the historical beam pair information includes a bitmap indicating the coordinates of the coordinate system and the corresponding historical measurement values ​​of the one or more historical beam pairs, and the bitmap has a length corresponding to the total number of coordinates of the coordinate system.

[0275] Aspect 27: A method according to any one of Aspects 16 to 26, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

[0276] Aspect 28: A method according to any one of Aspects 16 to 27, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmitted beam, and an actual measurement value associated with the first identifier and the second identifier.

[0277] Aspect 29: A method according to any one of Aspects 16 to 28, wherein receiving the historical beam pair information further comprises: receiving the historical beam pair information via uplink control information, channel state information report, medium access control control element or radio resource control message.

[0278] Aspect 30: The method according to any one of aspects 16 to 29, wherein the corresponding actual measurement information includes reference signal received power measurement, signal-to-noise-plus-interference measurement, or both.

[0279] Aspect 31: An apparatus for wireless communication at a first network node, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 1 to 15.

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

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

[0282] Aspect 34: An apparatus for wireless communication at a first network node, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 16 to 30.

[0283] Aspect 35: An apparatus for wireless communication at a first network node, the apparatus comprising: at least one component for performing the method according to any one of aspects 16 to 30.

[0284] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 30.

[0285] The above methods describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

[0287] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0288] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an 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. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

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

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

[0291] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to listed alternatives. For example, reference to "X is based on A or B" should be interpreted to include within its scope X is based on A, X is based on B, and X is based on A and B. In this regard, reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, reference to "X is based on A, B, or C" should be interpreted to include within its scope X is based on A, X is based on B, X is based on C, X is based on A and B, X is based on A and C, X is based on B and C, and X is based on A, B, and C. In this regard, reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based only on one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated otherwise. Similarly, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one."

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

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

[0294] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or within the scope of the claims. The terms "aspect" or "example" used herein mean "serving as an aspect, example, instance, or illustration," rather than "preferred" or "having advantages over other aspects." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving a plurality of signals via a plurality of receive beams; transmitting historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs comprises a corresponding transmit beam of a plurality of transmit beams from a second network node and a corresponding historical receive beam from the plurality of receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information of each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; as well as Predicted beam pair information based on the historical beam pair information is received, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

2. The first network node of claim 1 , wherein the at least one processor is further configured to: Control information indicating the corresponding azimuth information and the corresponding elevation information relative to the coordinate system is received.

3. The first network node according to claim 2, wherein: The control information indicates an identifier associated with each pair between elevation angle information and azimuth angle information of the coordinate system.

4. The first network node according to claim 2, wherein: The control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

5. The first network node according to claim 2, wherein: The control information indicates identifiers of a plurality of angular regions of the coordinate system.

6. The first network node of claim 1 , wherein the at least one processor is further configured to: Control information indicating a number of the one or more historical beam pairs included in the historical beam pair information is received.

7. The first network node according to claim 1, wherein: The one or more historical beam pairs include a corresponding historical beam pair for each combination of the plurality of transmit beams and the plurality of receive beams.

8. The first network node according to claim 1, wherein: The historical beam pair information includes a matrix having a plurality of elements, wherein each respective element of the plurality of elements corresponds to respective actual measurement information of a respective historical beam pair among the one or more respective beam pairs.

9. The first network node according to claim 1, wherein: The respective azimuth angle information and the respective elevation angle information of each respective historical receive beam are based on an orientation of the first network node and a receive beam identifier corresponding to the respective historical receive beam.

10. The first network node according to claim 1, wherein: The one or more historical beam pairs include a threshold number of historical beam pairs.

11. The first network node according to claim 1, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, actual measurement values ​​and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

12. The first network node according to claim 1, wherein the historical beam pair information comprises a bitmap indicating the coordinates of the coordinate system and the corresponding historical measurement values ​​of the one or more historical beam pairs, the bitmap having a length corresponding to the total number of coordinates of the coordinate system.

13. A first network node according to claim 1, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmitted beam, and an actual measurement value associated with the first identifier and the second identifier.

14. The first network node of claim 1 , wherein to transmit the historical beam pair information, the at least one processor is configured to: The historical beam pair information is sent via uplink control information, a channel state information report, a medium access control control element, or a radio resource control message.

15. The first network node of claim 1 , wherein the at least one processor is further configured to: A receive beam for communicating with the second network node is selected based on the predicted beam pair information.

16. A first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: transmitting a plurality of signals via a plurality of transmit beams; receiving historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs comprises a corresponding transmit beam from the plurality of transmit beams and a corresponding historical receive beam from the plurality of receive beams of the second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information of each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; as well as Predicted beam pair information based on the historical beam pair information is transmitted, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

17. The first network node of claim 16, wherein the at least one processor is further configured to: Control information indicating the corresponding azimuth information and the corresponding elevation information relative to the coordinate system is transmitted.

18. The first network node according to claim 17, wherein: The control information indicates an identifier associated with each pair between elevation angle information and azimuth angle information of the coordinate system.

19. The first network node according to claim 17, wherein: The control information indicates a resolution or granularity of the corresponding azimuth information and the corresponding elevation information of the coordinate system.

20. The first network node according to claim 17, wherein: The control information indicates identifiers of a plurality of angular regions from the second network node relative to the coordinate system.

21. The first network node of claim 16, wherein the at least one processor is further configured to: Control information indicating a number of the one or more historical beam pairs included in the historical beam pair information is transmitted.

22. The first network node according to claim 16, wherein: The one or more historical beam pairs include a corresponding historical beam pair for each combination of the plurality of transmit beams and the plurality of receive beams.

23. The first network node according to claim 16, wherein: The historical beam pair information includes a matrix having a plurality of elements, wherein each respective element of the plurality of elements corresponds to respective actual measurement information of a respective historical beam pair among the one or more respective beam pairs.

24. The first network node according to claim 16, wherein: The one or more historical beam pairs include a threshold number of historical beam pairs.

25. The first network node according to claim 16, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, an actual measurement value and an identifier corresponding to the corresponding azimuth information, the corresponding elevation information, and the corresponding transmit beam.

26. The first network node of claim 16, wherein the historical beam pair information comprises a bitmap indicating coordinates of the coordinate system and corresponding historical measurement values ​​of the one or more historical beam pairs, the bitmap having a length corresponding to a total number of coordinates of the coordinate system.

27. A first network node according to claim 16, wherein the historical beam pair information includes, for each of the one or more historical beam pairs, a first identifier corresponding to the corresponding azimuth information and the corresponding elevation information, a second identifier corresponding to the corresponding transmitted beam, and an actual measurement value associated with the first identifier and the second identifier.

28. The first network node of claim 16, wherein: The corresponding actual measurement information includes reference signal received power measurement, signal and noise plus interference measurement, or both.

29. A method of wireless communication performed by a first network node, the method comprising: receiving a plurality of signals via a plurality of receive beams; transmitting historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs comprises a corresponding transmit beam of a plurality of transmit beams from a second network node and a corresponding historical receive beam from the plurality of receive beams, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information of each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the first network node; as well as Predicted beam pair information based on the historical beam pair information is received, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the first network node.

30. A method of wireless communication performed by a first network node, the method comprising: transmitting a plurality of signals via a plurality of transmit beams; receiving historical beam pair information, the historical beam pair information comprising corresponding actual measurement information corresponding to each corresponding historical beam pair of one or more historical beam pairs, wherein each historical beam pair of the one or more historical beam pairs comprises a corresponding transmit beam from the plurality of transmit beams and a corresponding historical receive beam from the plurality of receive beams of the second network node, and wherein the historical beam pair information indicates corresponding azimuth information and corresponding elevation information of each corresponding historical beam pair of the one or more historical beam pairs, wherein the corresponding azimuth information and the corresponding elevation information are based on a coordinate system of the second network node; as well as Predicted beam pair information based on the historical beam pair information is transmitted, wherein the predicted beam pair information indicates one or more predicted beam pairs each including a predicted transmit beam and a predicted receive beam, wherein the predicted receive beam is based on the coordinate system of the second network node.

Images