Beam pair information reporting

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment may transmit a report indicating receive beam information for the UE, where a first dimension of the report is associated with one or more transmit resources of a network entity and a second dimension of the report is associated with one or more receive beam pointing directions at the UE. The UE may receive, from a network entity, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for a downlink message for the UE based on the report, wherein the first receive beam pointing direction is associated with a first transmission resource. The UE may receive the downlink message using a receive beam associated with the first receive beam pointing direction based on the received indication from the network entity.

Description

Background Art

[0001] The following relates to wireless communications, and more particularly to managing beam pair information.

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

[0003] A method for wireless communication at a user equipment (UE) is described. In some examples, the method may include sending a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. In some examples, the method may further include: receiving an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. Additionally, in some examples, the method may include: receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0004] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. In some examples, the apparatus may receive an indication of a first receive beam pointing direction among the one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources. Additionally, in some examples, the apparatus may receive a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0005] Another apparatus for wireless communication at a UE is described. In some examples, the apparatus may include components for sending a report indicating receive beam information for the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. Additionally, in some examples, the apparatus may have components for receiving an indication of a first receive beam pointing direction among one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources. Additionally, in some examples, the apparatus may have components for receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0006] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. In some examples, the code may include instructions executable by a processor to perform the following operations: send a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. In some examples, the code may also include instructions executable by the processor to perform the following operations: receive an indication of a first receive beam pointing direction among one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources. Additionally, in some examples, the code may include instructions executable by the processor to receive a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0007] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving an indication of a total number of entries associated with a first dimension of the report and a total number of entries associated with a second dimension of the report, wherein the report may be based on the indication.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the total number of entries associated with the first dimension may be based on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending an indication of a capability of the UE to report the report, the capability indicating a number of entries associated with a second dimension of the report, a number of non-zero values ​​associated with one or more receive beam pointing directions in the report, a number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource, or a combination thereof.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for transmitting one or more non-zero values ​​associated with one or more receive beam pointing directions in a report, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with one or more transmit resources of a network entity.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending an indication of a location of each of one or more non-zero values ​​in a report, where the location may be indicated via one of: a bitmap, a combination index, an index associated with each of one or more receive beam pointing directions, or a combination thereof.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more non-zero values ​​indicate a beamwidth associated with one or more preferred receive beam pointing directions, a beamforming gain associated with one or more preferred receive beam pointing directions, or both.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of non-zero values ​​associated with one or more receive beam pointing directions may be fixed per transmit resource.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a number of non-zero values ​​associated with one or more receive beam pointing directions may be fixed for reporting.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions in a report.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for transmitting, via a first channel state information (CSI) message, a number of one or more receive beam pointing directions at a UE, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, a number of non-zero values ​​associated with one or more receive beam pointing directions in a report, or any combination thereof. In some examples, the method may further include transmitting, via a second CSI message and based on the first CSI message, the one or more non-zero values ​​in the report, an index associated with each of the one or more non-zero values, or both, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction at the UE associated with a transmit resource of the network entity.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving, via an indication, a multidimensional index associated with a report, wherein a first dimension of the multidimensional index indicates a first transmit resource among one or more transmit resources of a network entity, and a second dimension of the multidimensional index indicates a first receive beam pointing direction among one or more receive beam pointing directions at a UE.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for transmitting, for a single transmit resource of a network entity, one or more non-zero values ​​associated with one or more receive beam pointing directions at a UE based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the first receive beam pointing direction includes a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the first receive beam pointing direction includes a CSI report setting identifier, a time slot identifier associated with a reported transmit time slot, or both.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the report includes a multi-dimensional report.

[0023] A method is described. The method may include obtaining a report indicating receive beam information of a UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE. In some examples, the method may further include outputting an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message of the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. In some examples, the method may include outputting a downlink message using a first transmit resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0024] A device is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. In some examples, the instructions may be executable by the processor to cause the device to: obtain a report indicating receive beam information of a UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE. In some examples, the device may output an indication of a first receive beam pointing direction of one or more receive beam pointing directions for use in a downlink message for the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. Additionally, in some examples, the device may output a downlink message using a first transmit resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0025] Another apparatus is described. In some examples, the apparatus may include components for obtaining a report indicating receive beam information for a UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE. In some examples, the apparatus may include components for outputting an indication of a first receive beam pointing direction of one or more receive beam pointing directions for use in a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. In some examples, the apparatus may include components for outputting a downlink message using a first transmit resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0026] A non-transitory computer-readable medium storing code is described. In some examples, the code may include instructions capable of being executed by a processor to perform the following operations: obtain a report indicating receive beam information of a UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE. In some examples, the code may include instructions capable of being executed by the processor to perform the following operations: output an indication of a first receive beam pointing direction of one or more receive beam pointing directions for use in a downlink message for the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. In some examples, the code may include instructions capable of being executed by the processor to output a downlink message using a first transmit resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining a first receive beam pointing direction based on a beam prediction process and a report, wherein the output indication of the first receive beam pointing direction may be based on the obtained first receive beam pointing direction.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a beam prediction process may be based on a machine learning model.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting an indication of a total number of entries associated with a first dimension of the report and a total number of entries associated with a second dimension of the report, wherein the report may be based on the indication.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the total number of entries associated with the first dimension may be based on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining an indication of a capability of the UE to report the report, wherein the capability indicates a number of entries associated with a second dimension of the report, a number of non-zero values ​​associated with one or more receive beam pointing directions in the report, a number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource, or a combination thereof.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining one or more non-zero values ​​associated with one or more receive beam pointing directions in a report, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with one or more transmit resources of a network entity.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining an indication of a location of each of one or more non-zero values ​​in a report, wherein the location may be indicated via one of: a bitmap, a combined index, an index associated with each of one or more receive beam pointing directions, or a combination thereof.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more non-zero values ​​indicate a beamwidth associated with one or more preferred receive beam pointing directions, a beamforming gain associated with one or more preferred receive beam pointing directions, or both.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of non-zero values ​​associated with one or more receive beam pointing directions may be fixed per transmit resource.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a number of non-zero values ​​associated with one or more receive beam pointing directions may be fixed for reporting.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for outputting an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions in the report.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining, via a first CSI message, a number of one or more receive beam pointing directions at a UE, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, a number of non-zero values ​​associated with one or more receive beam pointing directions in a report, or any combination thereof. In some examples, the methods, apparatuses, and non-transitory computer-readable media may include obtaining, via a second CSI message and based on the first CSI message, one or more non-zero values ​​in the report, an index associated with each of the one or more non-zero values, or both, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions at the UE associated with a transmit resource of a network entity.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a multidimensional index associated with a report is output via an indication, wherein a first dimension of the multidimensional index indicates a first transmit resource among one or more transmit resources of a network entity and a second dimension of the multidimensional index indicates a first receive beam pointing direction among one or more receive beam pointing directions at a UE.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for obtaining, for a single transmit resource of a network entity, one or more non-zero values ​​associated with one or more receive beam pointing directions at a UE based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the first receive beam pointing direction includes a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the first receive beam pointing direction includes a CSI report setting identifier, a time slot identifier associated with a reported transmit time slot, or both.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the report includes a multi-dimensional report. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 An example of a wireless communication system supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 2 An example of a network architecture supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 3 An example of a wireless communication system supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0048] Figure 4A and Figure 4B An example of a reporting diagram supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0049] Figure 5 An example of a report supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0050] Figure 6 An example of a machine learning graph supporting beam pair information reporting in accordance with one or more aspects of the present disclosure is illustrated.

[0051] Figure 7 An example of a process flow supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0052] Figure 8 and Figure 9 A block diagram illustrating a device supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0053] Figure 10 A block diagram illustrating a communication manager supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0054] Figure 11 A diagram illustrating a system including a device supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0055] Figure 12 and Figure 13A block diagram illustrating a device supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0056] Figure 14 A block diagram illustrating a communication manager supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0057] Figure 15 A diagram illustrating a system including a device supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated.

[0058] Figures 16 to 19 A flow chart illustrating a method of supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0059] In some wireless communication systems, a network entity may perform beam pair prediction to predict a pairing between a transmit beam of the network entity (e.g., associated with a transmit resource) and a receive beam (or a pair of a transmit beam and a receive beam) of a user equipment (UE) (e.g., associated with a transmit configuration indicator (TCI) state). For example, the network entity 105 may obtain one or more measurements associated with spatial downsampled measurements of a beam pair from the UE 115. The network entity 105 may use these measurements to predict measurements for other beam pairs via an artificial intelligence or machine learning model. To facilitate beam pair prediction at the network entity, the UE may send receive beam information (e.g., UE receive beam information) to the network entity, the receive beam information including a direction associated with each receive beam at the UE, a width of each receive beam at the UE, or other information. The network entity may receive and use the receive beam information associated with each UE receive beam to predict a beam pair and send an indication to the UE regarding which receive beam(s) the UE is to use or which beam pair(s) it is to use (e.g., a pair of a UE receive beam and a network entity transmit beam) for subsequent communication. For example, the network entity may send an indication of a corresponding beam identifier, a corresponding beam direction, or both for a UE receive beam or a network entity transmit beam (e.g., or a transmit resource corresponding to the network entity transmit beam), so that the UE may combine the first receive beam with the transmit resource for communication with the network entity.

[0060] However, the receive beam information associated with each receive beam of the UE (e.g., the direction of each receive beam, the width of each receive beam) may disclose proprietary information about the UE to the network entity. Specifically, based on the receive beam information associated with each receive beam at the UE, the network entity may determine proprietary information about the UE, such as the UE's beam codebook, the UE's antenna panel structure, the UE's antenna panel position, the UE's pointing direction, and so on. This information may be proprietary to the UE or proprietary to the manufacturer of a component of the UE, where such proprietary information may be used as a competitive advantage over other manufacturers of UEs. Therefore, each manufacturer may wish to protect (e.g., not disclose) such proprietary information. Furthermore, in order for the network entity to accurately predict beam pairs, the UE may transmit receive beam information relatively frequently, thereby increasing the amount of overhead in the wireless communication system. For example, the UE may transmit receive beam information each time it moves or changes position due to changes in the receive beam information associated with each receive beam. Therefore, if the UE is in a mobility state, the UE may transmit receive beam information for each receive beam relatively frequently.

[0061] The techniques, methods, and devices described herein may enable a UE to send receive beam information associated with a subset of receive beams. For example, according to one or more aspects, a UE may send a report (e.g., a matrix, a two-dimensional report, a multi-dimensional report, etc.) including receive beam information associated with the UE. In one example, a first dimension of the report (e.g., a column of the matrix) may be associated with a corresponding transmit resource (e.g., a transmit beam) of a network entity, and a second dimension of the report (e.g., a row of the matrix) may be associated with a corresponding pointing direction of the receive beam at the UE. In one example, the UE may populate the report with a fixed number of entries corresponding to the receive beams (e.g., preferred receive beams) at the UE (e.g., so that the UE does not disclose proprietary information and does not incur additional overhead). For example, the UE may populate one or more entries (e.g., such as the first column, the second row) of the report with a non-zero value (e.g., such as "1") to indicate one or more preferred beam pairs. Thus, the UE may send at least the non-zero value of the report, including the location of the non-zero value entries (e.g., entries with a value of "1"), to the network entity, where such non-zero value may indicate a preferred beam pair, beam width, beam gain, etc. associated with the corresponding receive beam pointing direction of the UE. In some examples, the UE may transmit only the non-zero value, a complete report including zero and non-zero values, or a partial report including one or more non-zero values ​​or one or more zero values. The network entity may use the beam pair information to perform beam pair prediction. For example, the network entity may use the corresponding beam pointing direction, beam width, beam gain, etc. indicated in the report to predict measurements and beam pairs between the network entity's transmit resources and the UE's receive beam. In response to performing beam pair prediction, the network entity may output an indication of which beam pair the UE is to use. For example, the network entity may send an index associated with the report, where the index identifies the corresponding receive beam pointing direction and transmit resource pair for the UE to use in order to receive downlink messages.

[0062] As described herein, receive beam information may refer to or otherwise include a receive beam, beam pointing direction, beam width, beam gain, or a combination thereof of the UE. In addition, the report may be an example of a two-dimensional matrix, a multi-dimensional matrix (e.g., more than two dimensions), etc. The first dimension of the report may be referred to as a column, where each column may be associated with a transmit resource of a network entity. Transmit resources may refer to a transmit beam, a set of time and frequency resources associated with a transmission from a network entity, a virtual resource, or both. A virtual resource may be one or more time and frequency resources indicated to a UE without transmitting information via such time and frequency resources. That is, the network entity may output an indication of a virtual resource (e.g., a time and frequency position) to the UE without transmitting information on such time and frequency resources. Therefore, the UE may perform channel measurement on a virtual resource (e.g., a time and frequency resource) without receiving a reference signal, data, etc. via the virtual resource. For example, the one or more transmit resources of the first dimension of the report may be based on the virtual resources of the network entity.

[0063] The second dimension of the report may refer to rows, where each row may be associated with a receive beam pointing direction at the UE. The receive beam pointing direction may refer to the direction in which the UE's receive beam is pointing or being directed. Such directions may be referenced to a global coordinate system (GCS). The corresponding entry of the report may include receive beam information associated with the corresponding receive beam of the UE. The receive beam of the UE may be a beam generated by one or more antennas of the UE so that the UE can receive one or more downlink or sidelink messages. For example, an entry associated with the first row and the first column (e.g., a first receive beam pointing direction associated with a first transmit resource of the network entity) may indicate a beam width, beam gain, beam direction, or preference associated with the first receive beam. One or more locations reported may refer to a location or entry in the report. As an illustrative example, a location in the report may refer to an entry in the first column and the second row of the report.

[0064] The techniques described herein may enable a UE to provide receive beam information for one or more receive beams of the UE to a network entity without disclosing proprietary information and while reducing overhead. For example, since receive beam information associated with a subset of receive beams at the UE is reported, the network entity may obtain sufficient information to accurately perform beam pair prediction without accessing or being informed of proprietary information about the UE. That is, the UE may report receive beam information associated with a subset of receive beams at the UE, so that the UE does not disclose receive beam information associated with each receive beam at the UE, thereby reducing the likelihood that the UE's proprietary information will be disclosed. In addition, the UE, the network entity, or both may be configured to communicate the periodicity of the report, configure the number of fixed entries in the report, and the like. Therefore, relative to reporting receive beam information for each receive beam at the UE, the overhead associated with sending the receive beam information may be reduced.

[0065] Aspects of the present disclosure are initially described in the context of a wireless communication system according to one or more aspects of the present disclosure. Aspects of the present disclosure are further described in the context of reporting diagrams and process flows according to one or more aspects of the present disclosure. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to beam pair information reporting according to one or more aspects of the present disclosure.

[0066] Figure 1 An example of a wireless communication system 100 supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0067] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices that take different forms or have different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the 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 example of a geographic area within which the network entities 105 and the UEs 115 may support communication of signals based on one or more radio access technologies (RATs). The network entities 105 may include a network entity communication manager 102 to facilitate communication between the UEs 115 and the network entities 105.

[0068] 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 1. The UE 115 may communicate with other UEs 115 or network entity 105 as shown. The UE 115 may include a UE communication manager 101 to facilitate communication between the UE 115 and the network entity 105, between the UE 115 and one or more additional UEs 115 via sidelinks, or a combination thereof.

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

[0070] In some examples, network entities 105 can communicate with core network 130, or with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), either directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can 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. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can 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 .

[0071] 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, a NR base station, an access point, a radio transceiver, a Node B, an eNodeB (eNB), a next-generation Node B, 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 eNode B, or other suitable terminology) or a network transmission entity 145. In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, standalone) 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).

[0072] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can 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, smart radio head, remote radio head (RRH), remote radio unit (RRU), or 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 examples, 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)).

[0073] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165 such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, 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) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the 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 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

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

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

[0076] 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 examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0077] 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.

[0078] The UE 115 and the network entity 105 can 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" can 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 can 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 can 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 can support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can 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).

[0079] 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 of the 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.

[0080] 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., ranging from 0 to 1023).

[0081] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in 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.

[0082] 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 examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0083] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling over downlink carriers, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. 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 the system 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 .

[0084] In some examples, 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 examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can 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.

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

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

[0087] 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 delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP 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.

[0088] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). The region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately 1 decimeter to 1 meter. 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 lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0089] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating using licensed bands. Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0090] A network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ 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 examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0091] 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).

[0092] 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 output signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as 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.

[0093] 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 examples, 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.

[0094] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across the system bandwidth or one or more subbands. Network entity 105 may output reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection 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).

[0095] 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 receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0096] In addition to or instead of being performed between the UE 115 and the network entity 105, the techniques described herein may also be implemented via additional or alternative wireless devices, including the IAB node 104, the distributed unit (DU) 165, the centralized unit (CU) 160, the radio unit (RU) 170, and the like. For example, in some implementations, the various aspects described herein may be implemented in the context of a disaggregated radio access network (RAN) architecture (e.g., an open RAN architecture). In a disaggregated architecture, the RAN may be split into three functional areas, corresponding to the CU 160, the DU 165, and the RU 170. The functional split between the CU 160, the DU 165, and the RU 175 is flexible and, therefore, results in many permutations of different functionality depending on which functions (e.g., MAC functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU 160, the DU 165, and the RU 175. For example, a functional split of the protocol stack may be employed between the DU 165 and the RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.

[0097] Some wireless communication systems (e.g., wireless communication system 100), infrastructure for NR access, and spectrum resources may additionally support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture. One or more network entities 105 may include a CU 160, a DU 165, and a RU 170, and may be referred to as a donor network entity 105 or an IAB donor. One or more DUs 165 (e.g., and / or RUs 170) associated with the donor network entity 105 may be controlled in part by the CU 160 associated with the donor network entity 105. One or more donor network entities 105 (e.g., an IAB donor) may communicate with one or more additional network entities 105 (e.g., an IAB node 104) via supported access and backhaul links. The IAB node 104 may support mobile terminal (MT) functionality controlled and / or scheduled by the DU 165 of the coupled IAB donor. Additionally, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115, etc.) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the disaggregated 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.

[0098] In some examples, wireless communication system 100 may include core network 130 (e.g., a next generation core network (NGC)), one or more IAB donors, IAB nodes 104, and UE 115, where IAB nodes 104 may be controlled in part by each other and / or the IAB donor. The IAB donor node and IAB node 104 may be examples of aspects of network entity 105. The IAB donor and one or more IAB nodes 104 may be configured as (e.g., or communicate according to) a relay chain.

[0099] For example, an access network (AN) or RAN may refer to communications between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node 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), wherein the CU 160 may communicate with the core network 130 via an NG interface (e.g., some backhaul link). The CU 160 may host Layer 3 (L3) functionality and signaling (e.g., RRC, Service Data Adaptation Protocol (SDAP), PDCP, etc.). At least one DU 165 and / or RU 170 may be responsible for lower layer functionality and signaling, such as Layer 1 (L1) and Layer 2 (L2) (e.g., RLC, MAC, physical (PHY), etc.), and may each be controlled at least in part by a CU 160. A DU 165 may support one or more different cells. The IAB donor and the IAB node 104 may communicate over an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally, the CU 160 may communicate with the core network over an NG interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) over an Xn-C interface (which may be an example of a portion of a backhaul link).

[0100] 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.). An IAB node 104 may include a DU 165 and a MT. The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the MT may act as a scheduled node toward 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 transmissions for UEs through one or more other IAB nodes 104). Additionally, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or a child node of other IAB nodes 104. Thus, the MT entity (e.g., MT) of IAB node 104 may provide a Uu interface for child nodes to receive signaling from parent IAB node 104, and a DU interface (e.g., DU 165) may provide a Uu interface for parent nodes to signal to child IAB nodes 104 or UE 115.

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

[0102] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to support techniques for large round trip times in random access channel procedures, as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 may additionally or alternatively be performed by components of the disaggregated RAN architecture (e.g., IAB nodes, DUs, CUs, etc.).

[0103] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0104] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0105] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0106] As described herein, a node, which may be referred to as a node, a network node, a network entity 105, or a wireless node, may be a base station (e.g., any base station described herein), a UE 115 (e.g., any UE 115 described herein), a network controller, an apparatus, a device, a computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE 115. As another example, the network node may be a network entity 105. As 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 115, the second network node may be a network entity 105, and the third network node may be a UE 115. In another aspect of this example, the first network node may be a UE 115, the second network node may be a network entity 105, and the third network node may be a network entity 105. In still other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE 115, network entity 105, devices, equipment, computing systems, etc. may include disclosure that UE 115, network entity 105, devices, equipment, computing systems, etc. are network nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 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 in accordance with the present disclosure (e.g., UE 115 is configured to receive information from network entity 105 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 the UE 115 configured to receive information from the network entity 105 also discloses that the first network node is configured to receive information from the second network node, the first network node may refer to a first UE 115 configured to receive information, a first network entity 105, a first device, a first equipment, a first computing system, a first one or more components, or a first processing entity, etc.; and the second network node may refer to a second UE 115, a second network entity 105, a second device, a second equipment, a second computing system, a second one or more components, a second processing entity, etc.

[0107] 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 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 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.

[0108] UE 115 and network entity 105 may communicate data via various beams. For example, UE 115 may operate in an inactive or idle mode (e.g., RRC inactive or idle mode). When UE 115 operates in such a mode, network entity 105 may output one or more tracking reference signals (TRS) to UE 115. UE 115 may use such TRS to perform measurements and track one or more beams of network entity 105. When UE 115 has data to send, UE 115 may perform an initial access procedure to gain access to network entity 105. For example, UE 115 may perform a contention-based random access (CBRA) procedure, in which UE 115 may select a random access preamble to use in order to gain access to the network. Additionally, UE 115 may receive one or more synchronization signal blocks (SSBs), perform a beam scanning procedure, and determine a beam to use for communication with the network entity.

[0109] In response to performing the CBRA procedure, UE 115 may gain access to the network and perform beam management to maintain a connected state (e.g., RRC_CONNECTED state). For example, UE 115 may perform a clear-sky beam management procedure for both uplink and downlink beam management. In downlink beam management (e.g., P1 / P2 / P3 downlink beam management procedure), UE 115 may receive one or more reference signals (e.g., SSB or CSI-RS) to perform channel measurement and report it to network entity 105. In this way, UE 115 and network entity 105 may perform beam management in the downlink.

[0110] For uplink beam management (e.g., U1 / U2 / U3 uplink beam management procedures), UE 115 may transmit one or more sounding reference signals (SRSs) so that network entity 105 can perform channel measurements on such SRSs. In this way, UE 115 and network entity 105 can perform beam management in the uplink. In addition, UE 115 may report L1 reference signal received power (RSRP) (L1-RSRP), and network entity 105 may output a transmit configuration indicator (TCI) state configuration.

[0111] In some examples, when operating in connected mode, UE 115 may report the L1 signal-to-noise ratio (L1-SINR) of one or more reference signals. In some examples, UE 115 or network entity 105 may use one or more procedures to reduce latency and overhead. For example, component carrier group beam updates, relatively faster uplink beam updates, unified TCI states, L1 and L2-centric mobility, dynamic TCI updates, uplink multi-panel selection, maximum power extrapolation reduction, beam management delay reduction, etc. may be implemented to reduce latency in beam management. In some cases, UE 115 and network entities may perform beam management for multiple transmit and receive points (mTRPs) in the wireless system.

[0112] When operating in connected mode, the UE 115 or the network entity 105 may experience a beam failure. For example, based on measurements of SSB or CSI-RS in the downlink or SRS in the uplink, the UE 115 may perform a beam failure recovery procedure to reconnect to the network. For example, the UE 115 may implement beam failure detection and beam failure recovery procedures (e.g., for the primary cell and secondary cell of the network entity) to reduce the latency associated with the beam failure. For example, the UE may detect the beam failure based on measurements of a beam failure detection reference signal and downlink control channel block error rate monitoring. Based on detecting the beam failure, the UE 115 may use a contention-free random access (CFRA) beam recovery procedure, send a link recovery request, or perform a MAC control element (MAC-CE) beam failure recovery procedure. In some examples, the UE 115 may be unable to perform beam failure recovery, which may result in a radio link failure.

[0113] In some examples of wireless communication system 100, network entity 105, UE 115, or both may employ artificial intelligence, machine learning, or both for air interface correspondence to target one or more use cases, improve performance, reduce complexity, and provide enhancements to NR systems. An initial set of use cases may include beam management, such as beam prediction in the time and spatial domains for overhead and latency reduction, improved beam selection accuracy, or a combination thereof. For each use case, representative sub-use cases may be completed using artificial intelligence and machine learning for characterization and baseline performance evaluation. Such methods (e.g., artificial intelligence and machine learning) for selected sub-use cases may be sufficiently diverse to support various requirements for the level of coordination between network entity 105 and UE 115 (e.g., gNB to UE). Furthermore, artificial intelligence and machine learning models and descriptions may identify common and specific features for framework research, such as characterizing the lifecycle management of artificial intelligence or machine learning models. That is, by employing artificial intelligence or machine learning in such use cases, model training, model deployment, model inference, model monitoring, model updates, or a combination thereof, may be studied and implemented in such communication systems.

[0114] For example, multiple beam management techniques based on artificial intelligence and machine learning can be supported in various scenarios. In a first beam management case (e.g., beam management case 1), machine learning and artificial intelligence can be used on the network or UE side to perform spatial domain downlink beam prediction for a first set of beams (e.g., set A of beams or a set of prediction resources) based on measurement results of a second set of beams (e.g., set B of beams or channel measurement resources). In a second beam management case (e.g., beam management case 2), artificial intelligence or machine learning can be used for temporal downlink beam prediction for the first set of beams based on historical measurement results of the second set of beams. For either case (e.g., the first beam management case or the second beam management case), the first set of beams and the second set of beams can be in the same frequency range (e.g., such as FR1, FR2, etc.).

[0115] Additionally, artificial intelligence or machine learning may be used for a sub-use case of the first beam management case, where, in one example, the second set of beams is a subset of the first set of beams. In such a case, the UE 115 or network entity 105 may identify the number of beams in both the first set of beams and the second set of beams, which may be known, and identify the second set of beams from the first set of beams (e.g., via a fixed pattern, a random pattern, etc.). In another sub-use case of the first beam management case, artificial intelligence or machine learning may be used when the first set of beams and the second set of beams are different (e.g., the first set of beams includes narrow beams and the second set of beams includes wide beams). In such a sub-use case, the UE 115 or network entity 105 may identify the number of beams in the first set of beams and the second set of beams, as well as the quasi-co-location (QCL) relationship between the first set of beams and the second set of beams. In such a case, the first set of beams may be used for downlink beam prediction, and the second set of beams may be used for beam measurement. Additionally, in either beam management case, codebook configurations for the first set of beams and the second set of beams may be identified.

[0116] In some cases, for the first beam management case, the UE 115 may operate an artificial intelligence or machine learning model (e.g., a UE-side model). In such cases, the UE 115 may send L1 signaling to report information inferred by the AI / ML model to the network entity 105. For example, the UE 115 may report one or more beams based on the output of the artificial intelligence or machine learning model inference, a predicted L1-RSRP corresponding to each of the one or more beams, and other information. Similarly, for beam management case 2, the UE 115 may operate an artificial intelligence or machine learning model. In such cases, the UE may send L1 signaling to report information associated with the artificial intelligence and machine learning model inference to the network entity 105. This information may include one or more beams for N future time instances, where each beam and time instance is based on the output of the model inference. The UE 115 may also report the value of N, the predicted L1-RSRP corresponding to each of the one or more beams, a timestamp corresponding to each of the one or more reported beams (e.g., such information may be explicitly indicated or implicitly determined), and other information via L1 signaling.

[0117] For any beam management case where the UE 115 operates an artificial intelligence or machine learning model, the UE 115, the network entity 105, or both may perform model monitoring with potential down-selection. In one example, the UE 115 may perform model monitoring to monitor performance metrics and perform determinations associated with model selection, activation, deactivation, switching, fallback operations, and the like. In some other cases, the network entity 105 may perform model monitoring to monitor performance metrics and perform determinations for model selection, activation, deactivation, switching, fallback operations, and the like. Additionally or alternatively, both the network entity 105 and the UE 115 may monitor models (e.g., hybrid model monitoring), wherein the UE 115 may monitor performance metrics and the network entity 105 may perform determinations for model selection, activation, deactivation, switching, fallback operations, and the like.

[0118] Alternatively, for any beam management case, the network entity 105 (e.g., or some network function) may operate an artificial intelligence or machine learning model, wherein the network entity 105 may perform model monitoring. For example, the network entity 105 may monitor performance metrics and perform determinations for model selection, activation, deactivation, switching, fallback operations, etc. Additionally, in instances where the network entity 105 operates the model and performs model monitoring, the network entity 105 may control beam measurements and reporting for model monitoring. For example, if the network entity 105 operates in any beam management case in addition to operating the model, the UE 115 may report measurement results for four or more beams in one reporting instance, wherein such information may be used by the network entity 105 (e.g., via the model) to perform beam prediction.

[0119] For sub-use cases in both the first beam management case and the second beam management case (e.g., spatial or temporal prediction for a first set of beams based on measurements of a second set of beams), UE 115 and network entity 105 may support model training and inference at least when the second set of beams is a subset of the first set of beams or when the first set of beams and the second set of beams are different. For example, if the second set of beams is a subset of the first set of beams, network entity 105 may perform model training and inference. Alternatively, if the first set of beams and the second set of beams are different, UE 115 may perform model training and inference. In some examples, UE 115 and network entity 105 may support model transfer between UE 115 and network entity 105. For example, network entity 105 may perform model training, while UE 115 may perform model inference. In the case where network entity 105 operates the model in either the first beam management case or the second beam management case, UE 115 may report measurement results for more than four beams in one reporting instance via L1 signaling.

[0120] In terms of data collection for artificial intelligence or machine learning model training at the UE 115 side, the UE 115 or the network entity 105 may determine whether and how to initiate data collection, determine the configuration related to the first set and the second set of beams, and determine and share information associated with mapping the first set and the second set of beams. In the example of data collection, the network entity 105 may output assistance information to the UE 115. In the case where the network entity 105 operates and monitors the model in any beam management case, the UE may report beam measurements based on the set of beams indicated by the network entity 105. Such reporting may be performed through radio resource control messaging, L1 signaling, etc. In such cases, the performance, complexity, and power consumption of the UE 115 may be considered.

[0121] In some examples of the wireless communication system 100, the network entity 105 may perform beam pair prediction between the transmit beams (e.g., transmit resources) of the network entity 105 and the receive beams of the UE 115. To facilitate beam pair prediction at the network entity 105, the UE 115 may send receive beam information to the network entity 105, the receive beam information including a direction associated with each receive beam at the UE 115, a width of each receive beam at the UE 115, etc. The network entity 105 may use the receive beam information to predict beam pairs and send an indication to the UE 115 of which receive beam to use. However, the receive beam information (e.g., the direction of each receive beam, the width of each receive beam) may disclose proprietary information about the UE 115 to the network entity 105. That is, based on the receive beam information associated with each receive beam at UE 115, network entity 105 may determine specific information of UE 115, such as the beam codebook of UE 115, the antenna panel structure of UE 115, the antenna panel position of UE 115, the pointing direction of UE 115, etc., in which case it may be undesirable to disclose such specific information. In addition, in order for network entity 105 to accurately predict beam pairs, UE 115 may send receive beam information relatively frequently, thereby introducing an increased amount of overhead in the wireless communication system.

[0122] The techniques, methods, and devices described herein may enable a UE 115 to transmit receive beam information associated with a subset of receive beams. For example, the UE 115 may transmit receive beam information comprising a report (e.g., a matrix), wherein a first dimension of the report (e.g., a column of the matrix) is each associated with a corresponding transmit resource (e.g., a transmit beam) of the network entity 105, and a second dimension of the report (e.g., a row of the matrix) is each associated with a corresponding pointing direction of the receive beam at the UE 115. Thus, the UE 115 may populate the report with a fixed number of entries corresponding to preferred receive beams at the UE 115. For example, the UE 115 may populate the entries (e.g., such as the first column, the second row) with "1" to indicate that such a beam pair may be preferred. The network entity 105 may obtain and use the beam pair information to perform beam pair prediction. In response to performing the beam pair prediction, the network entity 105 may output an indication of which beam pair the UE 115 is to use. For example, the network entity 105 may output an index associated with the report, where the index identifies a corresponding receive beam pointing direction and transmit resource pair for the UE 115 to use in order to receive the downlink message.

[0123] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both). The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a can be associated with a corresponding coverage area 110-a and can communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a can be served by multiple RUs 170-a simultaneously.

[0124] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include a network entity communication manager 102 that includes one or more interfaces or is coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, the network entities 105 may include a wired interface configured to receive signals or transmit signals to one or more of the other network entities 105 via the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals over a wireless transmission medium or to transmit signals to one or more of the other network entities 105, or both.

[0125] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0126] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on functional partitioning, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0127] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0128] The SMO 180-a can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 can include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some implementations, the SMO 180-a can communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an 01 interface.The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0129] The non-RT RIC 175-a may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or in communication with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b (e.g., via an E2 interface).

[0130] In some examples, non-RT RIC 175-a may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in near-RT RIC 175-b. Such information may be utilized by near-RT RIC 175-b and may be received at SMO 180-a or non-RT RIC 175-a from a non-network data source or from a network function. In some examples, non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions through SMO 180-a (e.g., via reconfiguration of O1) or via generation of RAN management policies (such as A1 policies).

[0131] In some examples, each UE 115-a may include a corresponding UE communication manager 101-a, which may be an example of a UE communication manager as described herein. The UE communication manager 101-a may include or be coupled with one or more components (e.g., such as a processor, an antenna, a transmitter, a receiver, etc.) that enable the UE 115-a to communicate one or more packets of data with the RU 170-a, the DU 165-a, the CU 160-a, and the O-eNB 210.

[0132] In some examples of the network architecture 200, the network entity 105 may perform beam pair prediction between the transmit beams (e.g., transmit resources) of the network entity 105 and the receive beams of the UE 115. To facilitate the beam pair prediction at the network entity 105, the UE 115 may send receive beam information to the network entity 105, the receive beam information including the direction associated with each receive beam at the UE 115, the width of each receive beam at the UE 115, etc. The network entity 105 may use the receive beam information to predict the beam pair and send an indication to the UE 115 of which receive beam to use. However, the receive beam information (e.g., the direction of each receive beam, the width of each receive beam) may disclose proprietary information about the UE 115 to the network entity 105. That is, based on the receive beam information associated with each receive beam at UE 115, network entity 105 may determine specific information of UE 115, such as the beam codebook of UE 115, the antenna panel structure of UE 115, the antenna panel position of UE 115, the pointing direction of UE 115, etc., in which case it may be undesirable to disclose such specific information. In addition, in order for network entity 105 to accurately predict beam pairs, UE 115 may send receive beam information relatively frequently, thereby introducing an increased amount of overhead in the wireless communication system.

[0133] The techniques, methods, and devices described herein may enable a UE 115 to transmit receive beam information associated with a subset of receive beams, thereby preventing the reporting of receive beam information associated with every receive beam of the UE, thereby protecting proprietary information and reducing signaling overhead. For example, the UE 115 may transmit receive beam information comprising a report (e.g., a matrix), wherein a first dimension of the report (e.g., a column of the matrix) is each associated with a corresponding transmit resource (e.g., a transmit beam) of the network entity 105, and a second dimension of the report (e.g., a row of the matrix) is each associated with a corresponding pointing direction of the receive beam at the UE 115. Thus, the UE 115 may populate the report with one or more non-zero values ​​(e.g., a fixed number of entries) corresponding to the preferred receive beams at the UE 115. For example, the UE 115 may populate entries (e.g., such as the first column, the second row) with non-zero values ​​(e.g., such as "1") to indicate that such a beam pair may be preferred. The network entity 105 may receive and use the beam pair information to perform beam pair prediction. In response to performing beam pair prediction, network entity 105 may output an indication of which beam pair to use for UE 115. For example, network entity 105 may output an index associated with the report, where the index identifies a corresponding entry in the report. That is, the index may identify a receive beam pointing direction and transmit resource pair for UE 115 to use in order to receive downlink messages.

[0134] Figure 3 An example of a wireless communication system 300 supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may implement reference Figure 1 and Figure 2 Aspects of the described wireless communication system 100 and network architecture 200 may be implemented by or as a result of the wireless communication system 100 and network architecture 200. For example, the wireless communication system 300 may include a network entity 105-b and a UE 115-b, which may be examples of the network entity 105 and UE 115 described herein. Additionally, the UE 115-b may include a capabilities and reporting component 301, and the network entity 105-b may include a beam prediction component 302.

[0135] In some cases of the wireless communication system 300, the network entity 105-b may use an artificial intelligence or machine learning model to predict beam pair quality (e.g., a prediction of a pair of transmit resources 325 of the network entity 105-b and receive beams of the UE 115-b). That is, the network entity 105-b may use a beam prediction component 302 that includes an artificial intelligence or machine learning model to perform beam pair prediction. For example, the network entity 105-b may obtain the L1-RSRP associated with the spatial downsampled measurement of the beam pair from the UE 115-b. The network entity 105-b may use the L1-RSRP to predict the L1-RSRP of other beam pairs via the artificial intelligence or machine learning model. By having the network entity 105-b operate the model and perform such beam prediction, the UE 115-b may experience reduced power consumption.

[0136] To facilitate beam pair prediction at network entity 105-b, UE 115-b may transmit receive beam information for each receive beam at UE 115-b. However, in such cases, the transmission of receive beam information may disclose proprietary information associated with UE 115-b. That is, to facilitate network-side beam pair prediction, UE 115-b may transmit information including receive beam direction, receive beam width, and the like for each receive beam at UE 115-b. Based on the receive beam information, network entity 105-b may determine proprietary information, such as a beam codebook for UE 115-b, an antenna panel structure for UE 115-b, an antenna panel position for UE 115-b, a pointing direction for UE 115-b, and the like, in which case disclosure of such proprietary information may be undesirable.

[0137] In addition, the transmission of receive beam information of UE 115-b may generate a relatively large reporting overhead in the wireless communication system 300, wherein such overhead may be further increased when UE 115-b is rotating or moving. For example, due to the rotation or movement of UE 115-b, UE 115-b may send (e.g., update) receive beam information relatively frequently (e.g., relative to operating in a fixed position), which may consume a relatively large portion of uplink overhead. Therefore, one or more candidate receive beams at UE 115-b may dynamically change based on the rotation and movement of UE 115-b, such that the receive beam information reported by UE 115-b may be insufficient and unsuitable for network entity 105-b. As an illustrative example, UE 115-b may include at least 120 candidate receive beams. Therefore, if UE 115-b sends receive beam information associated with each of 120 candidate receive beams and retransmits such information based on the rotation or movement of UE 115-b, UE 115-b and network entity 105-b may experience increased overhead, increased latency, and reduced communication quality.

[0138] In accordance with the techniques described herein, UE 115-b may use capabilities and reporting component 301 to send reports 305 (e.g., beam pair matrix reports, multi-dimensional reports) to reduce disclosure of proprietary information about UE 115-b (e.g., reduced disclosure of receive beam specific implementations of UE 115-b) and further reduce uplink overhead associated with indicating receive beam information about UE 115-b. For example, capabilities and reporting component 301 may include one or more components (e.g., such as a processor, an antenna, a transmitter, a receiver, etc.) that enable UE 115-b to send reports 305 indicating capabilities of UE 115-b, receive beam information about UE 115-b, or both.

[0139] The report 305 (e.g., which may be referred to as a sparse matrix, a two-dimensional matrix, etc.) may include receive beam information and include multiple dimensions, including a first dimension 310 and a second dimension 315, where the first dimension 310 (e.g., columns of the matrix) are associated with one or more transmit resources 325 of the network entity 105-b (e.g., transmit beams of the network entity 105-b), and the second dimension 315 (e.g., rows of the matrix) are associated with one or more receive beam pointing directions 330 of the UE 115-b. The report 305 may include one or more non-zero values ​​320, where such non-zero values ​​320 may indicate a preferred beam pair between the first receive beam pointing direction 330-a and the first transmit resource 325-a.

[0140] The report 305 may include a number of transmit resources 325 and a number of receive beam pointing directions 330, where such dimensions of the report 305 (e.g., number of columns and rows) and the definition of each entry (e.g., in terms of associated transmit resources and corresponding receive beam pointing directions) may be based on predefinition of a standards body (e.g., such as a 3GPP standard) or technical specification under which the wireless communication system 300 operates, signaling from the network entity 105-b, reporting by the UE 115-b, or a combination thereof.

[0141] In some examples, network entity 105-b may output, via control signaling 335, the number of transmit resources 325 (e.g., the number of entries, the number of columns) in first dimension 310 of report 305. That is, network entity 105-b may output an explicit indication of the number of transmit resources 325 associated with first dimension 310. Additionally or alternatively, the number of transmit resources 325 may be based on channel measurement resources or virtual resources indicated by network entity 105-b and received by UE 115-b (e.g., the number of channel measurement or virtual resources implicitly indicates the number of transmit resources). In such examples, the channel measurement resources or virtual resources may include associated pointing directions, beamwidth information, etc. In a case where UE 115-b is to send report 305 via a CSI report in uplink control information (UCI), the network entity 105-b may configure channel measurement resources or virtual resources via an associated CSI report setting, an associated MAC-CE that activates semi-persistent CSI reporting, or via a CSI-AssociatedReportConfigInfo element for aperiodic CSI reporting.

[0142] Additionally, the definition of the pointing direction associated with each receive beam pointing direction 330 (e.g., each entry) in first dimension 310 may be predefined by a standards body (e.g., such as a 3GPP standard), configured by network entity 105-b, based on a capability report from UE 115-b, or a combination thereof. In one example, receive beam pointing directions 330 may be defined relative to a GCS and an azimuth angle expressed in 360 degrees, where different entries in a column (e.g., a row) uniformly quantize the two-dimensional space. In such an example, the degree value associated with the entry in the first row of report 305 may be pre-assigned. As an illustrative example, if there are eight entries (e.g., rows) per column of report 305 (e.g., eight receive beam pointing directions per transmit resource), the first row of report 305 may be associated with a receive beam pointing direction 330 of zero degrees, the second row may be associated with a receive beam pointing direction 330 of 45 degrees, the third row may be associated with a receive beam pointing direction 330 of 90 degrees, and so on (e.g., 0, 45, 90, 135, 180, 225, 270, 315). In this manner, each respective transmit resource 325 (e.g., column) may be associated with a receive beam pointing direction 330 that quantizes two-dimensional space.

[0143] In another example, receive beam pointing directions 330 can be defined relative to the GCS, expressed as 360 degrees in azimuth and 180 degrees in elevation, where different entries in a column (e.g., rows) uniformly quantize the three-dimensional space. In such an example, the degree values ​​and resolution of the azimuth and elevation angles associated with the first component (e.g., row) can be pre-specified. As an illustrative example, if there are 16 receive beam pointing directions 330 (e.g., rows) per transmit resource 325 (e.g., per column), the first row of report 305 can be associated with receive beam pointing directions 330 with an azimuth of zero degrees and an elevation of -45 degrees (e.g., 0 / -45). This ordering can increase the resolution by 45 degrees in azimuth and 90 degrees in elevation per row. (e.g., 0 / -45, 0 / +45, 45 / -45, 45 / +45, 90 / -45, 90 / +45, 135 / -45, 135 / +45, 180 / -45, 180 / +45, 225 / -45, 225 / +45, 270 / -45, 270 / +45, 315 / -45, 315 / +45).

[0144] In such examples (e.g., receive beam pointing directions 330 quantize two or three dimensions), the definition of receive beam pointing directions 330 may be standardized (e.g., such as in a 3GPP standard). Additionally or alternatively, network entity 105-b may output control signaling 335 indicating the definition of receive beam pointing directions 330, or UE 115-b may use capabilities and reporting component 301 to send a UE capabilities message 340 indicating the definition. In some examples, the definition of receive beam pointing directions 330 (e.g., how they are quantized) may be referred to as the third dimension of report 305.

[0145] Additionally, the total number of receive beam pointing directions 330 (e.g., the number of entries) in the second dimension 315 may be based on a report from the UE 115-b, configured by the network entity 105-b, or defined by a standards body (e.g., such as a 3GPP standard). For example, prior to or concurrently with sending the report 305, the UE 115-b may send a UE capabilities message 340 indicating the total number of possible receive beam pointing directions 330 (e.g., the maximum number of rows), the number of receive beam pointing directions 330 for the report 305 (e.g., the number of rows or entries), or both. In some examples, the UE 115-b may send such information as part of the payload when reporting the report 305.

[0146] Alternatively, a standards body may define the total number of possible receive beam pointing directions 330 (e.g., a maximum number of rows), the number of receive beam pointing directions 330 reported 305 (e.g., the number of rows or entries), or both. If the UE 115-b or the standards body defines the total number of possible receive beam pointing directions 330 (e.g., a maximum number of rows), the network entity 105-b may indicate the number of receive beam pointing directions 330 out of the total number of possible receive beam pointing directions 330 via control signaling 335.

[0147] UE 115-b may populate report 305 with one or more non-zero values ​​320, where such non-zero values ​​320 indicate a preferred beam pair. As an illustrative example, UE 115-b may populate report 305 with one or more non-zero values, where each non-zero value 320 is equal to one. Thus, when a component (e.g., an entry) of report 305 is equal to one (e.g., the entry has a non-zero value 320), then the receive beam associated with the indicated receive beam pointing direction 330 may be paired with a corresponding transmit resource 325 of network entity 105-b. Otherwise, if the report entry is equal to zero, then such receive beam pointing direction 330 may not be associated with a receive beam at UE 115-b, not be associated with a transmit resource 325 at network entity 105-b, or both.

[0148] In addition, in some examples, UE 115-b may transmit one or more non-zero values ​​320 that further indicate beamwidth or beamgain information associated with the receive beam at UE 115-b. For example, UE 115-b may include beamwidth and beamgain information associated with one or more receive beams at UE 115-b in non-zero value 320 based on standard predefinition (e.g., as predefined in a 3GPP standard), based on an indication from network entity 105-b, based on a capability report of UE 115-b, or a combination thereof.

[0149] In one example, a standards body may predefine one or more options associated with the number of bits to be used for non-zero value 320. Accordingly, UE 115-b may convey information associated with the beamwidth and beamgain of one or more receive beams of UE 115-b according to one or more options associated with the predefined number of bits. For example, a standard may predefine an option that includes using zero bits in non-zero value 320. In such an example, UE 115-b may refrain from reporting beamwidth and beamgain information and may instead report a preferred beam pointing direction via non-zero value 320.

[0150] Additionally, the standard may predefine an option to include using more than zero bits in non-zero value 320. In such an example, UE 115-b may use a predefined number of bits to quantize beamwidth information, beamgain information, or both. Such predefinition may further be based on separate definitions for quantizing only beamgain, only beamwidth, or both beamgain and width, respectively.

[0151] In such an example (e.g., predefined using a standard), UE 115-b may send a UE capability message 340 indicating which option UE 115-b supports. For example, UE 115-b may send via capability message 340 that UE 115-b supports a zero-bit option. Thus, UE 115-b may avoid reporting beamwidth and beamgain via non-zero values ​​320. In some examples, network entity 105-b may indicate via control signaling 335 the number of bits per non-zero value 320 in report 305. That is, based on one or more options (e.g., a zero-bit non-zero value 320, or a multi-bit non-zero value 320), network entity 105-b may indicate which option UE 115-b will use to report 305.

[0152] In some examples, network entity 105-b may indicate the number of bits to use in non-zero value 320 based on an artificial intelligence or machine learning model used by network entity 105 for beam prediction. For example, depending on the specific implementation of the artificial intelligence or machine learning model, network entity 105-b may determine whether beam gain and beamwidth need to be quantized via multiple bits in non-zero value 320. Accordingly, based on this determination, network entity 105-b may output control signaling 335 to UE 115-b indicating the number of bits to use for non-zero value 320 for report 305. In the event that UE 115-b is to send report 305 via a CSI report in UCI, network entity 105-b may configure the number of bits via an associated CSI report setting, an associated MAC-CE that activates semi-persistent CSI reporting, or a CSI-AssociatedReportConfigInfo element for aperiodic CSI reporting. In some examples, the quantification of beam gain, beam width, etc. in the one or more non-zero values ​​320 of report 305 may be referred to as a fourth dimension of report 305 .

[0153] In some examples, the total number of non-zero values ​​320 may be fixed. For example, the total number of non-zero values ​​320 may be fixed per transmit resource 325 (e.g., per column). Thus, the number of receive beams of UE 115-b associated with a single transmit resource 325 of network entity 105-b may be fixed, resulting in a fixed number of beam pairs (e.g., pairs between the transmit resource of network entity 105-b and the receive beam of UE 115-b). As an illustrative example, the total number of non-zero values ​​320 per transmit resource 325 (e.g., per column) may be fixed to a value of three. Thus, UE 115-b may populate a report with a maximum of three non-zero values ​​320 per transmit resource 325.

[0154] Additionally or alternatively, the total number of non-zero values ​​320 may be fixed per report 305 (e.g., per matrix). Thus, the total number of beam pairs may be fixed, but the total number of receive beams associated with a single transmit resource 325 of the network entity 105-b may be variable. As an illustrative example, the total number of non-zero values ​​320 per report 305 may be fixed to a value of ten. Thus, the UE 115-b may populate the report 305 with up to ten non-zero values ​​320, but such non-zero values ​​320 may be any combination. For example, the UE 115-b may populate the first column associated with the first transmit resource 325 of the report 305 with ten non-zero values ​​320 and avoid populating other columns with non-zero values ​​320.

[0155] In addition, the total number of non-zero values ​​320 (e.g., per report 305 or per transmission resource 325) may be predefined based on a capability report of the UE 115-b, an indication from the network entity 105-b, or a standard. For example, prior to or concurrently with sending the report 305, the UE 115-b may send a UE capability message 340 indicating the total number of possible non-zero values ​​320 per report 305 (e.g., a maximum number of non-zero values ​​320 per matrix), the total number of possible non-zero values ​​320 per transmission resource 325 (e.g., a maximum number of non-zero values ​​320 per column), the number of non-zero values ​​320 per report 305, the number of non-zero values ​​per transmission resource 325, or a combination thereof. In some examples, the UE 115-b may send such information as part of the payload when reporting the report 305.

[0156] Additionally or alternatively, a standards body may predefine the total number of possible non-zero values ​​320 per report 305 (e.g., a maximum number of non-zero values ​​320 per matrix), the total number of possible non-zero values ​​320 per transmission resource 325 (e.g., a maximum number of non-zero values ​​320 per column), the number of non-zero values ​​per report 305, the number of non-zero values ​​320 per transmission resource 325, or a combination thereof. Accordingly, the network entity 105-b and the UE 115-b may operate according to the predefined numbers.

[0157] In some examples, if the total number of possible non-zero values ​​320 is reported or defined (e.g., a maximum value per matrix or per column), based on the UE capability message 340, a standard pre-definition, or both, the network entity 105-b may output the number of non-zero values ​​320 (e.g., per matrix, per column, or both) to the UE 115-b via control signaling 335, where the UE 115-b may accordingly populate the report 305. In the event that the UE 115-b is to send the report 305 via a CSI report in UCI, the network entity 105-b may configure the number of non-zero values ​​320 (e.g., per matrix, per column, or both) via an associated CSI report setting, an associated MAC-CE that activates semi-persistent CSI reporting, or via a CSI-AssociatedReportConfigInfo element for aperiodic CSI reporting.

[0158] In response to generating the report 305 and populating the report 305 with the non-zero values ​​320, the UE 115-b may send the report 305 via RRC signaling, MAC-CE signaling, or UCI. In some examples, the UE 115-b may dynamically report the report 305 based on which candidate receive beams are preferred at the UE 115-b. In such examples, due to the sparse nature of the report 305 (e.g., because a fixed number of non-zero values ​​320 may be reported), the UE 115-b may use overhead reduction techniques to send the report 305.

[0159] As described herein, UE 115-b may transmit report 305 via a CSI report in UCI. The CSI report may be an example of a periodic CSI report, a semi-persistent CSI report, or an aperiodic CSI report. In such examples, in addition to report 305, UE 115-b may also transmit dimension information associated with report 305, such as the total number of rows (e.g., the total number of receive beam pointing directions), the number of non-zero values ​​320 per transmit resource 325 or per report 305, or a combination thereof.

[0160] For example, UE 115-b may send dimensional information of report 305 via a first portion of CSI (e.g., CSI part 1), where the first portion of CSI has a fixed payload size. That is, UE 115-b may send the number of receive beam pointing directions 330, the number of non-zero values ​​320 (e.g., per column or per matrix) via the first portion of CSI. Accordingly, UE 115-b may send report 305 in a second portion of CSI (e.g., CSI part 2), which includes the location of each non-zero value 320, the value of the non-zero value 320, or both. The location of each non-zero value 320 may be determined according to the method described herein. Figure 4A The technique is further described.

[0161] In such examples, network entity 105-b may determine a payload size for the second portion of CSI based on information in the first portion of CSI (e.g., based on dimension information indicated in the first portion of CSI). Thus, the second portion of CSI may have a payload of variable size. In some examples, UE 115-b may send report 305 via a single portion of CSI based on an indication from network entity 105-b, a standard predefined value, or both.

[0162] In some other examples, UE 115-b may send the report via RRC signaling or MAC-CE signaling. In such examples, network entity 105-b may output an RRC configuration, a MAC-CE activation command, or downlink control information (DCI) indicating one or more uplink resources so that UE 115-b can use such resources to send report 305.

[0163] In response to receiving the report 305, the network entity 105-b may obtain the first receive beam pointing direction 330-a based on performing a beam prediction process using the beam prediction component 302. That is, the network entity 105-b may input the non-zero value 320 of the report 305 into the artificial intelligence or machine learning model of the beam prediction component 302 and output the preferred beam pair. The network entity 105-b may use the beam prediction component 302 to output a TCI state activation command 345 indicating the preferred beam pair (e.g., the first receive beam pointing direction 330-a associated with the first transmit resource 325-a) to the UE 115-b. Figure 4B Indication of a preferred beam pair is further described. Based on the preferred beam pair, UE 115-b may determine a receive beam 355 associated with the first receive beam pointing direction 330-a (eg, indicated via beam pair prediction) and receive the downlink message 350 using the receive beam 355.

[0164] In this manner, because receive beam pointing direction 330 is defined by the GCS and a subset of the overall receive beams of UE 115-b is reported via report 305, network entity 105-b may not be able to determine UE 115-b-specific information (e.g., such as UE 115-b's receive beam codebook). Additionally, UE 115-b may experience lower uplink reporting overhead due to the configuration (e.g., definition) of report 305. That is, because UE 115-b may report receive beam information for a subset of UE 115-b's receive beams, UE 115-b may dynamically update reports relatively frequently and without incurring additional overhead, resulting in relatively smaller reports.

[0165] Figure 4A and Figure 4B An example of a reporting diagram 400 and a reporting diagram, respectively, supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The reporting diagram 400 and the reporting diagram may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, and the wireless communication system 300 as described herein. For example, the reporting diagram 400 and the reporting diagram may be implemented by a UE and a network entity. The reporting diagram 400 and the reporting diagram may include a report 405, which may be as described in reference Figure 3 An example of a report 305 is described.

[0166] With respect to report diagram 400 and in accordance with aspects of the present disclosure, a UE may generate a report 405-a, wherein a first dimension (e.g., columns) of report 405-a is associated with one or more transmit resources of a network entity, and a second dimension (e.g., rows) of report 405-a is associated with one or more receive beam pointing directions of the UE. Additionally, report 405-a may include one or more non-zero values. The non-zero values ​​may indicate a preferred beam pair between one or more receive beam pointing directions of the UE and one or more transmit resources of the network entity. The UE may send report 405-a to the network entity so that the network entity may use the receive beam information (e.g., non-zero values) in report 405-a to perform beam pair prediction.

[0167] In some examples, prior to or concurrently with sending report 405-a, the UE may send an indication of the location of each non-zero value relative to report 405-a so that a network entity can identify a preferred beam pair and process the receive beam information. This location information may be indicated via one or more non-zero value indication methods 406, such as bitmap 410, combination index 415, and row index 420.

[0168] In some examples, the UE may transmit a bitmap 410 indicating the location of each non-zero value relative to report 405-a. To indicate such location information, the UE may set each bit in bitmap 410 to the corresponding component in report 405-a. As an illustrative example, if report 405-a has a first dimension with eight entries (e.g., a matrix with eight columns) and a second dimension with 17 entries (e.g., a matrix with 17 rows), the corresponding bitmap 410 may have 136 bits (e.g., 8×17=136), where each bit may represent an entry in report 405-a. Thus, the UE may fill the bits in bitmap 410 with "1"s to indicate the associated receive beam pointing direction and the corresponding transmit resource's non-zero value, while the zeros in bitmap 410 are associated with the zero-valued components of report 405-a.

[0169] In some other examples, the UE may send a combined index 415 indicating the position of each non-zero value relative to the report. In one example, the combined index 415 may be relative to the entire report, where the combined index 415 may be equal to: Thus, a combined index may be used to feedback the locations of non-zero values, where N is the total number of entries in report 405-a, and K is the total number of non-zero values ​​in report 405-a. As an illustrative example, if report 405-a has a first dimension with eight entries (e.g., a matrix with eight columns) and a second dimension with 17 entries (e.g., a matrix with 17 rows), then the value of N may be equal to 136. Alternatively, the value of K may be equal to 24. Thus, the network entity may use a combined index with the values ​​136 and 24 to identify the locations of non-zero values.

[0170] In another example, the combined index 415 may be relative to a separate combined index associated with the first dimension of the report. That is, the combined index may be relative to a separate combined index for a different column, where such a combined index 415 may be equal to: The combined index 415 may be used to feedback the location of the non-zero value in the mth row, where M is the number of entries in the second dimension of the report 405 (eg, the number of rows), and K m It can be the total number of non-zero values ​​in the mth row. As described herein, if the total number of non-zero values ​​is fixed per transmit resource (e.g., per column), then for different reported receive beam pointing directions (e.g., rows), K m Otherwise, the UE may first report K via the first part of CSI (e.g., in CSI part 1). m and then reported via the second part of CSI (e.g., in CSI Part 2)

[0171] In some examples, the UE may send an index of the second dimension for the corresponding entry of the first dimension to report the location of the non-zero value in report 405-a. That is, the UE may send a row index for the corresponding column of report 405-a. For example, the UE may use log2 M bits to report the row index for the first receive beam pointing direction, where M is equal to the total number of entries in the second dimension (e.g., the total number of rows). As described herein, if the number of non-zero values ​​per column is free (e.g., not fixed), the UE may first report the number of non-zero values ​​per column via the first portion of CSI (e.g., in CSI part 1) and report the corresponding row index via the second portion of CSI (e.g., in CSI part 2). As an illustrative example, if the number of non-zero values ​​per transmit resource (e.g., per column) is fixed to three, the UE may report three row indices associated with each column. For example, as illustrated in report 405-a, the non-zero values ​​associated with the first transmit resource may be located at the second entry, the ninth entry, and the fifteenth entry. Thus, the UE may report 02, 09, and 15 as indices of the first transmission resource.The UE may report such values ​​for each transmission resource (eg, each column) in report 405-a.

[0172] In addition, in addition to the position of the non-zero value, the UE may also report the value of the non-zero value. In one example, if the non-zero value is not associated with the beam width and beam gain information, the UE may avoid reporting these values. That is, because the non-zero value is not associated with the beam width and beam gain information, the UE may report the position of the preferred receive beam pointing direction (e.g., non-zero value) without reporting the additional bit in each non-zero value. Alternatively, if the non-zero value is based on Figure 3 If the beam information is quantized using the techniques described herein (e.g., based on standards body definitions, network configuration, or UE reporting), the UE may report the beam information via one or more bits in each non-zero value. That is, if the non-zero value carries beamforming width and beamforming gain information, the UE may report such information, where the number of bits per non-zero value may be based on the information described herein with respect to the beamforming width and beamforming gain information. Figure 3 Described by standards body definition, network configuration or UE reporting.

[0173] At once Figure 4BFor purposes of the report diagram and in accordance with aspects of the present disclosure, a network entity may use information received via report 405-a (e.g., the location and value of non-zero values) as input to a machine learning or artificial intelligence model to perform beam pair prediction and obtain a preferred receive beam pointing direction (e.g., a first receive beam pointing direction). In response to obtaining the preferred receive beam pointing direction, the network entity may send a TCI state activation command (e.g., such as TCI state activation command 345) including an indication of the preferred receive beam pointing direction (e.g., the preferred beam pair). To provide an indication to the UE, the network entity may use a beam pair index (e.g., a single-dimensional index 425), as represented by report 405-b, or a receive beam index (e.g., a multi-dimensional index 430), as represented by report 405-c.

[0174] In the example of beam pair indexing, the network entity may send an indication of one or more beam pairs via a TCI state activation MAC-CE or a receive beam refinement command, where the indicated beam pair index is defined based on the most recently sent report 405. Such an index may be based on a standard definition or network configuration, where non-zero values ​​of the report 405-b are sorted first by transmit resource (e.g., column) and then by receive beam orientation (e.g., row).

[0175] For example, if a network entity receives report 405-b and is using beam pair indexing, the network entity may assign a corresponding index to each non-zero value in report 405-b, starting with the first column. As an illustrative example, the network entity may assign an index of zero to the first non-zero value in the first column, an index of one to the second non-zero value in the first column, and an index of two to the third non-zero value in the first column. Once the network entity has assigned an index to each non-zero value in the first column, the network entity may begin indexing the second column, starting with index value three. In this manner, each non-zero value may be associated with a corresponding index. Thus, in a TCI state activation command or a receive beam refinement command, the network entity may include an indication of such an index and provide an indication of one or more preferred receive beam pairs. For example, the network entity may determine, based on a machine learning or artificial intelligence model, that beam pairs associated with indices 3, 8, 14, and 16 are preferred. Therefore, the network entity may send an indication via a TCI state activation command or a received beam refinement command that beam pairs associated with indices 3, 8, 14, and 16 are preferred. Such an indication may be referred to as a single-dimensional index 425.

[0176] In the example of receive beam indexing, the network entity may send an indication of one or more beam pairs via a TCI state activation MAC-CE or a receive beam refinement command, wherein the indicated beam pair index is defined according to the most recently reported report 405. Such an index may be further based on a separate network command that first indicates a transmit resource (e.g., based on SSB or CSI-RS) and additionally indicates a receive beam pointing direction associated with the transmit resource. In such an example, the receive beam index may be based on a definition according to the most recently reported report 405.

[0177] For example, if the network entity receives report 405-c and is using receive beam indexing, the network entity may index each non-zero value with a corresponding index per transmit resource (e.g., per column). As an illustrative example, the network entity may receive report 405-c and assign an index of zero to the first non-zero value associated with the first column (e.g., the first transmit resource), one to the second non-zero value associated with the first column, and two to the third non-zero value associated with the first column. Thus, the network entity may restart such indexing on a per-column basis, where, for example, the network entity assigns an index of zero to the first non-zero value in the second column. Thus, each column (e.g., transmit resource) may include a corresponding index for the non-zero value.

[0178] In such an example, the network entity may transmit a multidimensional index 430 via a TCI state activation command or a receive beam refinement command, wherein a first dimension 430-a of the multidimensional index 430 indicates a corresponding transmit resource (e.g., a corresponding column), and a second dimension 430-b of the multidimensional index 430 may indicate a corresponding receive beam pointing direction associated with a non-zero value. As illustrative examples, the network entity may indicate one or more multidimensional indices 430 having values ​​(1, 1), (3, 2), and (5, 2), wherein the first dimension 430-a corresponds to a transmit resource, and the second dimension 430-b corresponds to a corresponding receive beam pointing direction.

[0179] In some examples, the network entity may include a CSI report setting identifier, a CSI report time slot identifier, or both in the TCI state activation command or the receive beam refinement command. For example, if the UE sends the report 405 via a CSI report in UCI, the network entity may indicate the CSI report setting identifier, the time slot or subframe identifier associated with the CSI report setting, or both via the TCI state activation command or the receive beam refinement command to avoid ambiguity issues. For example, to indicate to the UE that the index in the TCI state activation command or the receive beam refinement command is associated with the most recent report 405, the network entity may include an identifier associated with the CSI report used by the UE to send the most recent report 405. In this way, the UE can identify a preferred receive beam from the correct report 405 based on the received index.

[0180] Figure 5 An example of a reporting diagram 500 supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The reporting diagram 500 may be implemented as described herein with reference to Figures 1 to 4B Aspects of the wireless communication system 100, network architecture 200, wireless communication system 300, reporting diagram 400, and reporting diagrams described herein may be implemented by or as such. For example, reporting diagram 500 may be implemented by a UE and include a report 505, which may be an example of report 305, report 405-a, report 405-b, and report 405-c as described herein.

[0181] According to aspects of the present disclosure, a UE may generate a report 505, wherein a first dimension (e.g., columns) of the report 505 is associated with one or more transmit resources of a network entity, and a second dimension (e.g., rows) of the report 505 is associated with one or more receive beam pointing directions of the UE. Additionally, the report 505 may include one or more non-zero values ​​510. The non-zero values ​​510 may indicate a preferred beam pair between the one or more receive beam pointing directions of the UE and the one or more transmit resources of the network entity. The UE may transmit the report 505 to the network entity, so that the network entity may use the receive beam information (e.g., non-zero values ​​510) in the report 505 to perform beam pair prediction.

[0182] In some examples, the UE can generate a report 505 in which each transmit resource (e.g., each column) of the reported network entity can correspond to the same receive beam pointing direction of the UE. That is, each transmit resource of the network entity is associated with the same one or more receive beams of the UE. In such an example, instead of sending a report 505 indicating the same preferred receive beam pointing direction for each transmit resource, the UE can send a vector 515 when each transmit resource of the network entity shares the same receive beam at the UE.

[0183] For example, a standards body (e.g., such as a 3GPP standard) may predefine, a network entity may configure, or a UE may report that the receive beam at the UE is the same relative to various transmit resources of the network, such that report 505 becomes vector 515. In one example, the network entity may send control signaling (e.g., such as control signaling 335) indicating that each receive beam pointing direction at the UE is to be the same for each transmit resource, such that the UE uses vector 515 to indicate a preferred beam pair. In such an example, the control signaling may be an example of a CSI report setup, a MAC-CE activating semi-persistent CSI reporting, or a CSI-AssociatedReportConfigInfo for aperiodic CSI reporting. In another example, the UE may send a UE capability message indicating that the same receive beam can be used for all transmit resources of the network entity. In such an example, report 505 may use (e.g., fall back to) vector 515.

[0184] In the example where report 505 indicates the same receive beam for each transmit resource, the UE may transmit a dimension identifier associated with vector 515. That is, the matrix dimension identifier falls back to the vector dimension identifier, such as indicating the number of receive beam pointing directions associated with vector 515, the number of non-zero values ​​510 associated with vector 515, etc. Similarly, reporting the position of non-zero values ​​510 in the matrix falls back to reporting the position of non-zero values ​​510 in the vector 515 or reporting the first column of report 505. Such techniques may be implemented if the dimensionality of report 505 becomes relatively large, when the UE is unable to recover the receive beam associated with one or more transmit resources, or both.

[0185] In this way, where the receive beam pointing direction is the same for each transmit resource indicated in the report, the UE can efficiently resize the report 505 to become the vector 515, resulting in reduced uplink overhead.

[0186] Figure 6 An example of a machine learning diagram 600 that supports beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The machine learning process may be performed by a machine learning diagram as described herein. Figures 1 to 5 Aspects of the described wireless communication system 100, network architecture 200, wireless communication system 300, reporting graph 400, reporting graph, and reporting graph 500 may be implemented. For example, the machine learning graph 600 may be implemented at the network entity 105 or the UE 115, or both, as described with reference to FIG. Figures 1 to 5 described.

[0187] The machine learning graph 600 may include a machine learning algorithm 610. As illustrated, the machine learning algorithm 610 may be an example of a neural network, such as a feedforward (FF) or deep feedforward (DFF) neural network, a recurrent neural network (RNN), a long / short term memory (LSTM) neural network, or any other type of neural network. However, any other machine learning algorithm may be supported. For example, the machine learning algorithm 610 may implement a nearest neighbor algorithm, a linear regression algorithm, a naive Bayes algorithm, a random forest algorithm, or any other machine learning algorithm. Furthermore, the machine learning graph 600 may involve supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or any combination thereof.

[0188] The machine learning algorithm 610 may include an input layer 615, one or more hidden layers 620, and an output layer 625. In a fully connected neural network with one hidden layer 620, each hidden layer node 635 may receive a value as input from each input layer node 630, where each input may be weighted. These neural network weights may be based on a cost function modified during training of the machine learning algorithm 610. Similarly, each output layer node 640 may receive a value as input from each hidden layer node 635, where the inputs are weighted. If post-deployment training (e.g., online training) is supported, memory may be allocated to store errors and / or gradients of inverse matrix multiplications. These errors and / or gradients may support updating the machine learning algorithm 610 based on output feedback. Training the machine learning algorithm 610 may support the calculation of weights (e.g., connecting input layer nodes 630 to hidden layer nodes 635 and connecting hidden layer nodes 635 to output layer nodes 640) to map input patterns to desired output results. The training may generate a device-specific machine learning algorithm 610 based on historical application data and data transfer for a particular network entity 105 or UE 115 .

[0189] In some examples, input values ​​605 may be transmitted to the machine learning algorithm 610 for processing. Such input values ​​605 may include receive beam information of the UE indicated via a report (e.g., an entry in a report). In some examples, preprocessing may be performed on the input values ​​605 according to an operation sequence so that the input values ​​605 may be in a format compatible with the machine learning algorithm 610. The input values ​​605 may be converted into a set of k input layer nodes 630 at the input layer 615. In some cases, different measurements may be input at different input layer nodes 630 of the input layer 615. If the number of input layer nodes 630 exceeds the number of inputs corresponding to the input values ​​605, default values ​​(e.g., a value of 0) may be assigned to some input layer nodes 630. As illustrated, the input layer 615 may include three input layer nodes 630-a, 630-b, and 630-c. However, it should be understood that the input layer 615 may include any number of input layer nodes 630 (e.g., 20 input nodes).

[0190] The machine learning algorithm 610 can convert the input layer 615 into a hidden layer 620 based on the number of input-to-hidden weights between the k input layer nodes 630 and the n hidden layer nodes 635. The machine learning algorithm 610 can include any number of hidden layers 620 as an intermediate step between the input layer 615 and the output layer 625. Additionally, each hidden layer 620 can include any number of nodes. For example, as illustrated in the figure, the hidden layer 620 can include four hidden layer nodes 635-a, 635-b, 635-c, and 635-d. However, it should be understood that the hidden layer 620 can include any number of hidden layer nodes 635 (e.g., 10 input nodes). In a fully connected neural network, each node in a layer can be based on each node in the previous layer. For example, the value of the hidden layer node 635-a can be based on the values ​​of the input layer nodes 630-a, 630-b, and 630-c (e.g., where different weights are applied to each node value).

[0191] The machine learning algorithm 610 may determine the value of an output layer node 640 of an output layer 625 following one or more hidden layers 620. For example, the machine learning algorithm 610 may convert the hidden layer 620 into an output layer 625 based on the number of hidden-to-output weights between n hidden layer nodes 635 and m output layer nodes 640. In some cases, n=m. Each output layer node 640 may correspond to a different output value 645 of the machine learning algorithm 610. The output value 645 may indicate one or more beam pair predictions, allowing a network entity (e.g., using the machine learning algorithm 610) to indicate such predictions to a UE. As illustrated, the machine learning algorithm 610 may include three output layer nodes 640-a, 640-b, and 640-c, each supporting three different thresholds. However, it should be understood that the output layer 625 may include any number of output layer nodes 640. In some examples, the output value 645 may be post-processed according to a sequence of operations so that the output value 645 is in a format compatible with reporting the output value 645.

[0192] In this manner, the network entity may receive a report from the UE and input the non-zero value of the report as an input value 605 into the machine learning algorithm 610. The network entity may use the machine learning algorithm to determine one or more output values ​​645, where such output values ​​645 indicate a beam pair prediction for the UE. Thus, the network entity may utilize the machine learning algorithm 610 to efficiently and accurately perform beam pair prediction.

[0193] Figure 7 An example of a process flow 700 for supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The process flow 700 may be implemented as described herein with reference to Figures 1 to 6Aspects of the wireless communication system 100, network architecture 200, wireless communication system 300, reporting diagram 400, reporting diagram, reporting diagram 500, and machine learning diagram 600 are described herein or implemented by these aspects. For example, the process flow 700 can be implemented by the network entity 105-c and the UE 115-c, which can be examples of corresponding devices described herein. In the following description of the process flow 700, the operations can be performed in an order different from the order shown. Certain operations can also be excluded from the process flow 700, or other operations can be added to the process flow 700. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations can actually occur simultaneously.

[0194] The process flow 700 may describe a method for enabling a UE 115-c to send a report (e.g., such as that described herein with reference to Figures 3 to 5 The technology of the report described herein, wherein a first dimension (e.g., columns of the report) may be associated with one or more transmit resources of the network entity 105-c and a second dimension (e.g., rows) may be associated with one or more receive beam pointing directions of the UE 115-c.

[0195] For example, at 705, UE 115-c may send a UE capability message (e.g., such as reference Figure 3 UE capability message 340), where the capability message may instruct the UE to report the report (e.g., as referred to herein). Figures 3 to 5 In some examples, the UE capability message may include the number of entries associated with the second dimension of the report (e.g., such as those described herein). Figure 3 The number of receive beam pointing directions described herein), the number of non-zero values ​​associated with a report, the number of non-zero values ​​per transmit resource, or a combination thereof.

[0196] At 710, the network entity 105-c may output control signaling (e.g., such as control signaling 335), wherein such control signaling may indicate one or more dimensions associated with the report. For example, the network entity 105-c may indicate a total number of entries associated with a first dimension of the report (e.g., a total number of transmit resources or columns) and a total number of entries associated with a second dimension of the report (e.g., a total number of receive beam pointing directions or rows). The network entity 105-c may indicate one or more configurations associated with the report, such as a fixed number of non-zero values ​​per transmit resource or per report, as described herein with reference to Figure 3 described.

[0197] At 715, the UE 115-c may send a report indicating receive beam information of the UE. For example, the UE 115-c may send a report indicating one or more non-zero values ​​associated with receive beam pointing directions in the report, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction, a beamwidth associated with each preferred receive beam pointing direction, a beamforming gain associated with each preferred receive beam pointing direction, or a combination thereof. The non-zero value may be a value that is not specified herein. Figure 3 An example of a non-zero value 320 is described.

[0198] Additionally, in some examples, the UE 115-c may send a location of each of the one or more non-zero values ​​in the report, where the location is indicated via a bitmap, a combination index, an index, or a combination thereof. Such location information may be as described herein with reference to Figure 4A Examples of the described position indications.

[0199] In some examples, UE 115-c may transmit dimension information associated with the report via a first portion of the CSI report (e.g., CSI part 1), while transmitting the locations and values ​​of the reported non-zero values ​​in a second portion of the CSI report (e.g., CSI part 2), as described herein with reference to Figure 3 described.

[0200] In some examples, UE 115-c may transmit one or more non-zero values ​​associated with one or more receive beam pointing directions at UE 115-c for a single transmit resource (e.g., for a single column) based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources. That is, UE 115-c may transmit a vector based on one or more receive beam pairings with all transmit resources of network entity 105-c, such as described herein with reference to FIG. Figure 5 Described vector 515.

[0201] At 720, in response to receiving the report, the network entity 105-c may optionally perform a beam prediction process. For example, the network entity 105-c may obtain a first receive beam pointing direction based on the beam prediction process and the report. In some examples, the network entity 105-c may use one or more non-zero values ​​and the associated pairs between transmit resources and receive beam pointing directions as input into a machine learning or artificial intelligence model. The output of such a model may be a preferred beam pair (e.g., a first receive beam pointing direction associated with a first transmit resource of the network entity 105-c).

[0202] At 725, the network entity 105-c may output a TCI state activation command, wherein the activation command includes an indication of a first receive beam pointing direction for use in a downlink message for the UE. In some examples, the TCI state activation command may include a two-dimensional index (e.g., a row index and a column index), wherein a first dimension of the two-dimensional index indicates a first transmit resource and a second dimension of the two-dimensional index indicates a first receive beam pointing direction. In some other examples, the TCI state activation command may include a single-dimensional index associated with the report, wherein the single-dimensional index indicates a value of the first receive beam pointing direction. Additionally, in some examples, the TCI state activation command may include a CSI report setting identifier, a time slot identifier, or both associated with the report, such that the UE 115-c may associate the index with the report. Such an index and indication may be as described herein with reference to Figure 4B An example of the described index.

[0203] At 730, based on the index received in the TCI state activation command, the UE 115-c may identify a receive beam associated with the first receive beam pointing direction and the first transmit resource. At 735, the UE 115-c may receive a downlink message using the identified receive beam associated with the first receive beam pointing direction.

[0204] Figure 8 A block diagram 800 illustrates a device 805 that supports beam pair information reporting according to one or more aspects of the present disclosure. The device 805 can be an example of aspects of the UE 115 as described herein. The device 805 can include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0205] The receiver 810 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 information reporting). The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0206] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., a control channel related to beam pair information reporting, a data channel, an information channel), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0207] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of beam pair information reporting as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0208] In some examples, the communication manager 820, the receiver 810, the transmitter 815, 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 components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0209] Additionally or alternatively, in some examples, the communication manager 820, receiver 810, transmitter 815, 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 820, receiver 810, transmitter 815, 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 in this disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0211] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured as or otherwise support means for sending a report indicating receive beam information for the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. The communication manager 820 may be configured as or otherwise support means for receiving, based on the report, an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The communication manager 820 may be configured as or otherwise support means for receiving, based on the indication of the first receive beam pointing direction, a downlink message using a receive beam associated with the first receive beam pointing direction.

[0212] The communication manager 820 may be an example of a component for performing various aspects of managing beam pair prediction as described herein. The communication manager 820 or its subcomponents may be implemented in hardware (e.g., in communication management circuitry). The circuitry may include a processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0213] In another specific implementation, the communication manager 820 or its subcomponents may be implemented in code executed by a processor (e.g., as communication management software or firmware) or any combination thereof. If implemented in code executed by a processor, the functionality of the communication manager 820 or its subcomponents may be performed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device.

[0214] In some examples, communication manager 820 may be configured to perform various operations (eg, receive, determine, send, output, obtain) using or otherwise cooperating with receiver 810, sender 815, or both.

[0215] By including or configuring a communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) may support techniques for beam pair prediction based on reports indicating beam information associated with a subset of receive beam pointing directions at the UE, which may reduce processing and more efficiently utilize communication resources.

[0216] Figure 9A block diagram 900 illustrates a device 905 that supports beam pair information reporting according to one or more aspects of the present disclosure. The device 905 may be an example of aspects of the device 805 or the UE 115 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).

[0217] The receiver 910 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 information reporting). The information may be passed to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0218] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., a control channel related to beam pair information reporting, a data channel, an information channel), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0219] Device 905 or its various components can be examples of means for performing various aspects of beam pair information reporting as described herein. For example, communication manager 920 can include reporting component 925, indexing component 930, receive beam component 935, or any combination thereof. Communication manager 920 can be an example of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 910, transmitter 915, or both. For example, communication manager 920 can receive information from receiver 910, transmit information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0220] According to examples as disclosed herein, a communication manager 920 can support wireless communications at a UE. A reporting component 925 can be configured as or otherwise support means for sending a report indicating receive beam information for the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. An indexing component 930 can be configured as or otherwise support means for receiving, based on the report, an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. A receive beam component 935 can be configured as or otherwise support means for receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0221] The communication manager 920 may be an example of a component for performing various aspects of managing beam pair prediction as described herein. The communication manager 920 or its subcomponents may be implemented in hardware (e.g., in communication management circuitry). The circuitry may include a processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0222] In another specific implementation, the communication manager 920 or its subcomponents may be implemented in code executed by a processor (e.g., as communication management software or firmware) or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 920 or its subcomponents may be performed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device.

[0223] In some examples, communication manager 920 may be configured to perform various operations (eg, receive, determine, send, output, obtain) using or otherwise cooperating with receiver 910, transmitter 915, or both.

[0224] Figure 10Block diagram 1000 illustrates a communication manager 1020 that supports beam pair information reporting in accordance with one or more aspects of the present disclosure. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both, as described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of beam pair information reporting as described herein. For example, the communication manager 1020 may include a reporting component 1025, an indexing component 1030, a receive beam component 1035, a dimension component 1040, a UE capability component 1045, a beam pair component 1050, a first partial CSI component 1055, a second partial CSI component 1060, a vector component 1065, a non-zero value positioning component 1070, a non-zero value component 1075, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0225] According to examples as disclosed herein, a communication manager 1020 can support wireless communications at a UE. A reporting component 1025 can be configured as or otherwise support means for sending a report indicating receive beam information for the UE, wherein a first dimension of the report is associated with one or more transmit resources of a network entity, and a second dimension of the report is associated with one or more receive beam pointing directions at the UE. An indexing component 1030 can be configured as or otherwise support means for receiving, based on the report, an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. A receive beam component 1035 can be configured as or otherwise support means for receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0226] In some examples, dimension component 1040 can be configured as or otherwise support means for receiving an indication of a total number of entries associated with a first dimension of a report and a total number of entries associated with a second dimension of the report, wherein the report is based on the indication.

[0227] In some examples, the total number of entries associated with the first dimension is based on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0228] In some examples, the UE capability component 1045 may be configured as or otherwise support a component for sending an indication of the UE's ability to report the report, where the capability indication includes the number of entries associated with a second dimension of the report, the number of non-zero values ​​associated with one or more receive beam pointing directions in the report, the number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource, or a combination thereof.

[0229] In some examples, beam pair component 1050 may be configured as or otherwise support a component for sending one or more non-zero values ​​associated with one or more receive beam pointing directions in a report, where the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with one or more transmit resources of a network entity.

[0230] In some examples, the non-zero value location component 1070 may be configured as or otherwise support a component for sending an indication of the location of each of one or more non-zero values ​​in a report, where the location is indicated via one of: a bitmap, a combined index, an index associated with each of one or more receive beam pointing directions, or a combination thereof.

[0231] In some examples, the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0232] In some examples, the number of non-zero values ​​associated with one or more receive beam pointing directions is fixed per transmit resource.

[0233] In some examples, non-zero value component 1075 can be configured as or otherwise support means for receiving an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource.

[0234] In some examples, the number of non-zero values ​​associated with one or more receive beam pointing directions is fixed for reporting.

[0235] In some examples, non-zero value component 1075 can be configured as or otherwise support means for receiving an indication of a number of non-zero values ​​associated with one or more receive beam pointing directions in a report.

[0236] In some examples, the first portion CSI component 1055 can be configured as or otherwise support means for transmitting, via a first CSI message, a number of one or more receive beam pointing directions at the UE, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, a number of non-zero values ​​associated with the one or more receive beam pointing directions in a report, or any combination thereof. In some examples, the second portion CSI component 1060 can be configured as or otherwise support means for transmitting, via a second CSI message and based on the first CSI message, one or more non-zero values ​​in the report, an index associated with each of the one or more non-zero values, or both, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction at the UE associated with a transmit resource of the network entity.

[0237] In some examples, index component 1030 may be configured as or otherwise support a component for receiving a multidimensional index associated with a report via an indication, wherein a first dimension of the multidimensional index indicates a first transmit resource from one or more transmit resources of a network entity and a second dimension of the multidimensional index indicates a first receive beam pointing direction from one or more receive beam pointing directions at a UE.

[0238] In some examples, vector component 1065 may be configured as or otherwise support means for transmitting one or more non-zero values ​​associated with one or more receive beam pointing directions at a UE for a single transmit resource of a network entity based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

[0239] In some examples, the indication of the first receive beam pointing direction includes a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0240] In some examples, the indication of the direction in which the first receive beam is pointed includes a CSI report setting identifier, a time slot identifier associated with a reported transmit time slot, or both.

[0241] In some examples, the report includes a multi-dimensional report.

[0242] Figure 11A diagram illustrating a system 1100 including a device 1105 supporting beam pair information reporting according to one or more aspects of the present disclosure is shown. Device 1105 may be an example of, or include components of, device 805, device 905, or UE 115 as described herein. Device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 1105 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. 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 1145).

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

[0244] In some cases, device 1105 may include a single antenna 1125. However, in some other cases, device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired, or wireless links, as described herein. For example, transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1115 may also include a modem for modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. Transceiver 1115, or transceiver 1115 and one or more antennas 1125, may be examples of transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof, or components thereof, as described herein.

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

[0246] The processor 1140 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, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1140 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 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., various functions or tasks supporting beam pair information reporting). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or coupled to the processor 1140, the processor 1140 and the memory 1130 being configured to perform the various functions described herein.

[0247] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. For example, the communication manager 1120 may be configured as or otherwise support means for sending a report indicating receive beam information for the UE, wherein a first dimension of the report is associated with one or more transmit resources of a network entity, and a second dimension of the report is associated with one or more receive beam pointing directions at the UE. The communication manager 1120 may be configured as or otherwise support means for receiving, based on the report, an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The communication manager 1120 may be configured as or otherwise support means for receiving, based on the indication of the first receive beam pointing direction, a downlink message using a receive beam associated with the first receive beam pointing direction.

[0248] By including or configuring a communication manager 1120 according to examples as described herein, the device 1105 may support techniques for beam pair prediction based on reports indicating beam information associated with a subset of receive beam pointing directions at the UE, which may reduce power consumption and more efficiently utilize communication resources.

[0249] In some examples, the communication manager 1120 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 can be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 can include instructions executable by the processor 1140 to cause the device 1105 to perform various aspects of beam pair information reporting as described herein, or the processor 1140 and the memory 1130 can be otherwise configured to perform or support such operations.

[0250] Figure 12 A block diagram 1200 illustrates a device 1205 that supports beam pair information reporting according to one or more aspects of the present disclosure. The device 1205 may be an example of aspects of the network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0251] Receiver 1210 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 device 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0252] The transmitter 1215 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1215 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 examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0253] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of beam pair information reporting as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0255] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, 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 1220, the receiver 1210, the transmitter 1215, 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 in this disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0256] In some examples, communication manager 1220 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 can receive information from receiver 1210, transmit information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0257] For example, the communication manager 1220 may be configured as or otherwise support means for obtaining a report indicating receive beam information for the UE, wherein a first dimension of the report is associated with one or more transmit resources of the network entity, and a second dimension of the report is associated with one or more receive beam pointing directions of the UE. The communication manager 1220 may be configured as or otherwise support means for outputting an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message for the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The communication manager 1220 may be configured as or otherwise support means for outputting a downlink message using a first transmit resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction.

[0258] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 (e.g., a processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof) may support techniques for beam pair prediction based on reports indicating beam information associated with a subset of receive beam pointing directions at the UE, which may reduce processing and more efficiently utilize communication resources.

[0259] Figure 13 Block diagram 1300 illustrates a device 1305 supporting beam pair information reporting according to one or more aspects of the present disclosure. Device 1305 may be an example of aspects of device 1205 or network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0260] Receiver 1310 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 device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0261] Transmitter 1315 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 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 examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0262] Device 1305 or its various components can be examples of means for performing various aspects of beam pair information reporting as described herein. For example, communication manager 1320 can include reporting component 1325, beam pair component 1330, transmit resource component 1335, or any combination thereof. Communication manager 1320 can be an example of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 can receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in conjunction with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0263] The reporting component 1325 may be configured as or otherwise support means for obtaining a report indicating receive beam information for the UE, wherein a first dimension of the report is associated with one or more transmit resources of the network entity, and a second dimension of the report is associated with one or more receive beam pointing directions of the UE. The beam pair component 1330 may be configured as or otherwise support means for outputting, based on the report, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The transmit resource component 1335 may be configured as or otherwise support means for outputting, based on the indication of the first receive beam pointing direction, a downlink message using a first transmit resource associated with the first receive beam pointing direction.

[0264] Figure 14 A block diagram 1400 illustrates a communication manager 1420 that supports beam pair information reporting in accordance with one or more aspects of the present disclosure. The communication manager 1420 can be an example of aspects of the communication manager 1220, the communication manager 1320, or both, as described herein. The communication manager 1420 or its various components can be examples of means for performing various aspects of beam pair information reporting as described herein. For example, the communication manager 1420 can include a reporting component 1425, a beam pair component 1430, a transmit resource component 1435, a machine learning component 1440, a dimension component 1445, a UE capability component 1450, a CSI component 1455, an index component 1460, a vector component 1465, a positioning component 1470, a non-zero value component 1475, 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.

[0265] Reporting component 1425 may be configured as or otherwise support means for obtaining a report indicating receive beam information for the UE, wherein a first dimension of the report is associated with one or more transmit resources of a network entity, and a second dimension of the report is associated with one or more receive beam pointing directions of the UE. Beam pair component 1430 may be configured as or otherwise support means for outputting, based on the report, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. Transmit resource component 1435 may be configured as or otherwise support means for outputting, based on the indication of the first receive beam pointing direction, a downlink message using a first transmit resource associated with the first receive beam pointing direction.

[0266] In some examples, the machine learning component 1440 can be configured as or otherwise support a component for obtaining a first receive beam pointing direction based on a beam prediction process and report, wherein the output indication of the first receive beam pointing direction is based on the obtained first receive beam pointing direction.

[0267] In some examples, the beam prediction process is based on a machine learning model.

[0268] In some examples, dimension component 1445 can be configured as or otherwise support means for outputting an indication of a total number of entries associated with a first dimension of a report and a total number of entries associated with a second dimension of the report, wherein the report is based on the indication.

[0269] In some examples, the total number of entries associated with the first dimension is based on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0270] In some examples, the UE capability component 1450 may be configured as or otherwise support a component for obtaining an indication of the UE's capability to report the report, where the capability indication is the number of entries associated with a second dimension of the report, the number of non-zero values ​​associated with one or more receive beam pointing directions in the report, the number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource, or a combination thereof.

[0271] In some examples, the beam pair component 1430 may be configured as or otherwise support a component for obtaining one or more non-zero values ​​associated with one or more receive beam pointing directions in a report, where the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with one or more transmit resources of the network entity.

[0272] In some examples, the positioning component 1470 may be configured as or otherwise support means for obtaining an indication of a location for each of one or more non-zero values ​​in a report, where the location is indicated via one of: a bitmap, a combined index, an index associated with each of one or more receive beam pointing directions, or a combination thereof.

[0273] In some examples, the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0274] In some examples, the number of non-zero values ​​associated with one or more receive beam pointing directions is fixed per transmit resource.

[0275] In some examples, non-zero value component 1475 can be configured as or otherwise support means for outputting an indication of the number of non-zero values ​​associated with one or more receive beam pointing directions per transmit resource.

[0276] In some examples, the number of non-zero values ​​associated with one or more receive beam pointing directions is fixed for reporting.

[0277] In some examples, non-zero value component 1475 can be configured as or otherwise support means for outputting an indication of the number of non-zero values ​​associated with one or more receive beam pointing directions in a report.

[0278] In some examples, the CSI component 1455 can be configured as or otherwise support means for obtaining, via a first CSI message, a number of one or more receive beam pointing directions at the UE, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, a number of non-zero values ​​associated with one or more receive beam pointing directions in a report, or any combination thereof. In some examples, the CSI component 1455 can be configured as or otherwise support means for obtaining, via a second CSI message and based on the first CSI message, one or more non-zero values ​​in the report, an index associated with each of the one or more non-zero values, or both, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with the transmit resources of the network entity at the UE.

[0279] In some examples, index component 1460 may be configured as or otherwise support a component for outputting a multidimensional index associated with a report via an indication, wherein a first dimension of the multidimensional index indicates a first transmit resource from one or more transmit resources of a network entity and a second dimension of the multidimensional index indicates a first receive beam pointing direction from one or more receive beam pointing directions at a UE.

[0280] In some examples, vector component 1465 may be configured as or otherwise support means for obtaining one or more non-zero values ​​associated with one or more receive beam pointing directions at a UE for a single transmit resource of a network entity based on one or more non-zero values ​​associated with one or more receive beam pointing directions being equal for each of one or more transmit resources.

[0281] In some examples, the indication of the first receive beam pointing direction includes a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0282] In some examples, the indication of the direction in which the first receive beam is pointed includes a CSI report setting identifier, a time slot identifier associated with a reported transmit time slot, or both.

[0283] In some examples, the report includes a multi-dimensional report.

[0284] Figure 15A diagram illustrates a system 1500 including a device 1505 supporting beam pair information reporting, according to one or more aspects of the present disclosure. Device 1505 may be an example of, or include a component of, device 1205, device 1305, or network entity 105 as described herein. Device 1505 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, one or more wireless interfaces, or any combination thereof. Device 1505 may include components that support outgoing and incoming communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. 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 1540).

[0285] The transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1510 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 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535 or memory 1525 or both) may be included in a chip or chip assembly installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

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

[0287] Processor 1535 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 components, discrete hardware components, or any combination thereof). In some cases, processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1535. Processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to cause device 1505 to perform various functions (e.g., functions or tasks supporting beam pair information reporting). For example, device 1505 or a component of device 1505 may include processor 1535 and memory 1525 coupled to processor 1535, with processor 1535 and memory 1525 configured to perform the various functions described herein. Processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that may host functions (e.g., by executing code 1530) to perform the functions of device 1505. Processor 1535 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (such as within memory 1525). In some implementations, processor 1535 can be a component of a processing system. A processing system can refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs that can be passed to other systems or components (e.g., device 1505). For example, the processing system of device 1505 can refer to a system that includes various other components or subcomponents of device 1505, such as processor 1535, or transceiver 1510, or communication manager 1520, or other components or combinations of components of device 1505. The processing system of device 1505 can interface with other components of device 1505 and can process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1505 can include a processing system and one or more interfaces for outputting information, for receiving 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 implementations. In some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, such that the device 1505 can transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1505 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0288] In some examples, bus 1540 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1505 or between different components of device 1505 that may be co-located or located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of the different components or divided between the different components).

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

[0290] For example, the communication manager 1520 may be configured as or otherwise support means for obtaining a report indicating receive beam information for the UE, a first dimension of the report being associated with one or more transmit resources of the network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE. The communication manager 1520 may be configured as or otherwise support means for outputting, based at least in part on the report, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The communication manager 1520 may be configured as or otherwise support means for outputting, based on the indication of the first receive beam pointing direction, a downlink message using a first transmit resource associated with the first receive beam pointing direction.

[0291] By including or configuring a communication manager 1520 according to examples as described herein, the device 1505 may support techniques for beam pair prediction based on reports indicating beam information associated with a subset of receive beam pointing directions at the UE, which may reduce power consumption and more efficiently utilize communication resources.

[0292] In some examples, the communication manager 1520 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise coordinating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 can be supported or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 can include instructions executable by the processor 1535 to cause the device 1505 to perform various aspects of beam pair information reporting as described herein, or the processor 1535 and the memory 1525 can be otherwise configured to perform or support such operations.

[0293] Figure 16 The flowchart of the method 1600 for supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the method 1600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The described UE 115 performs the operations of method 1600. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0294] At 1605, the method may include sending a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of the network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Figure 10 The described reporting component 1025 is executed.

[0295] At 1610, the method may include receiving an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figure 10The described indexing component 1030 is performed.

[0296] At 1615, the method may include: receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 10 The receive beam component 1035 described above is performed.

[0297] Figure 17 The flowchart of the method 1700 for supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The described UE 115 performs the operations of method 1700. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0298] At 1705, the method may include receiving an indication of a total number of entries associated with a first dimension of the report and a total number of entries associated with a second dimension of the report. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figure 10 The described dimension component 1040 is executed.

[0299] At 1710, the method may include sending a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of the network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figure 10 The described reporting component 1025 is executed.

[0300] At 1715, the method may include receiving an indication of a first receive beam pointing direction of one or more receive beam pointing directions for a downlink message for the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Figure 10 The described indexing component 1030 is performed.

[0301] At 1720, the method may include: receiving a downlink message using a receive beam associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction. The operations of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1720 may be implemented as described in reference to Figure 10 The receive beam component 1035 described above is performed.

[0302] Figure 18 A flowchart illustrating a method 1800 for supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 7 as well as Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0303] At 1805, the method may include obtaining a report indicating receive beam information of the UE, wherein a first dimension of the report is associated with one or more transmit resources of the network entity, and a second dimension of the report is associated with one or more receive beam pointing directions of the UE. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 14 The described reporting component 1425 is executed.

[0304] At 1810, the method may include outputting, based on the report, an indication of a first receive beam pointing direction of one or more receive beam pointing directions for use in a downlink message of the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be implemented as described with reference to Figure 14 The described beamforming is performed by component 1430.

[0305] At 1815, the method may include: outputting a downlink message using a first transmission resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction. The operations of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figure 14 The described sending resource component 1435 is executed.

[0306] Figure 19A flowchart illustrating a method 1900 for supporting beam pair information reporting according to one or more aspects of the present disclosure is illustrated. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 7 as well as Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0307] At 1905, the method may include obtaining a report indicating receive beam information of the UE, wherein a first dimension of the report is associated with one or more transmit resources of the network entity, and a second dimension of the report is associated with one or more receive beam pointing directions of the UE. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Figure 14 The described reporting component 1425 is executed.

[0308] At 1910, the method may include obtaining a first receive beam pointing direction based on the beam prediction process and the report, wherein the output indication of the first receive beam pointing direction is based on the obtained first receive beam pointing direction. The operations of 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1910 may be implemented as described in reference to Figure 14 The machine learning component 1440 described is executed.

[0309] At 1915, the method may include: outputting an indication of a first receive beam pointing direction of one or more receive beam pointing directions for use in a downlink message of the UE based on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Figure 14 The described beamforming is performed by component 1430.

[0310] At 1920, the method may include: outputting a downlink message using a first transmission resource associated with the first receive beam pointing direction based on the indication of the first receive beam pointing direction. The operations of 1920 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1920 may be implemented as described in reference to Figure 14 The described sending resource component 1435 is executed.

[0311] The following provides an overview of various examples of the present disclosure:

[0312] Aspect 1: A device for performing wireless communication at a UE, the device comprising: a processor; a memory coupled to the processor, the processor being configured to send a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE; receiving an indication of a first receive beam pointing direction among the one or more receive beam pointing directions for a downlink message for the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources; and receiving the downlink message using a receive beam associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

[0313] Aspect 2: An apparatus according to Aspect 1, wherein the processor is further configured to: receive an indication of the total number of entries associated with the first dimension of the report and the total number of entries associated with the second dimension of the report, wherein the report is based on the indication.

[0314] Aspect 3: The apparatus of aspect 2, wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0315] Aspect 4: The apparatus according to any one of aspects 1 to 3, wherein the processor is further configured to: send an indication of a capability of the UE to report the report, the capability indicating a number of entries associated with the second dimension of the report.

[0316] Aspect 5: An apparatus according to any one of Aspects 1 to 3, wherein the processor is further configured to: send an indication of the ability of the UE to report the report, the capability indicating the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0317] Aspect 6: An apparatus according to any one of Aspects 1 to 3, wherein the processor is further configured to: send an indication of a capability of reporting the report to the UE, the capability indicating the number of non-zero values ​​associated with the one or more receiving beam pointing directions per transmitting resource.

[0318] Aspect 7: An apparatus according to any one of Aspects 1 to 6, wherein in order to send the report, the processor is further configured to: send one or more non-zero values ​​associated with the one or more receiving beam pointing directions in the report, wherein the one or more non-zero values ​​indicate one or more preferred receiving beam pointing directions associated with the one or more transmitting resources of the network entity.

[0319] Aspect 8: An apparatus according to Aspect 7, wherein the processor is further configured to: send an indication of the location of each of the one or more non-zero values ​​in the report, wherein the location is indicated via one of the following items: a bitmap, a combined index, or an index associated with each of the one or more receive beam pointing directions.

[0320] Aspect 9: An apparatus according to any one of Aspects 7 to 8, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0321] Aspect 10: The apparatus according to any one of aspects 7 to 8, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

[0322] Aspect 11: The apparatus according to aspect 10, wherein the processor is further configured to: receive an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource.

[0323] Aspect 12: The apparatus according to any one of aspects 7 to 11, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed for the reporting.

[0324] Aspect 13: The apparatus of aspect 12, wherein the processor is further configured to: receive an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0325] Aspect 14: The apparatus according to any one of aspects 1 to 13, wherein, in order to send the report, the processor is further configured to: send the number of the one or more receive beam pointing directions at the UE via a first CSI message.

[0326] Aspect 15: An apparatus according to any one of Aspects 1 to 13, wherein, in order to send the report, the processor is further configured to: send the number of non-zero values ​​associated with the one or more receiving beam pointing directions per transmission resource via a first CSI message.

[0327] Aspect 16: An apparatus according to any one of Aspects 1 to 13, wherein, in order to send the report, the processor is further configured to: send the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report via a first CSI message.

[0328] Aspect 17: The apparatus according to any one of aspects 14 to 16, wherein, to send the report, the processor is further configured to: send one or more non-zero values ​​in the report via a second CSI message and according to the first CSI message.

[0329] Aspect 18: An apparatus according to any one of Aspects 14 to 16, wherein, in order to send the report, the processor is further configured to: send an index associated with each of the one or more non-zero values ​​via a second CSI message and based on the first CSI message.

[0330] Aspect 19: The apparatus according to any one of aspects 17 to 18, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction at the UE associated with the transmit resources of the network entity.

[0331] Aspect 20: An apparatus according to any one of Aspects 1 to 19, wherein in order to receive the first receiving beam pointing direction, the processor is further configured to: receive a multidimensional index associated with the report via the indication, wherein the first dimension of the multidimensional index indicates the first transmitting resource among the one or more transmitting resources of the network entity, and the second dimension of the multidimensional index indicates the first receiving beam pointing direction among the one or more receiving beam pointing directions at the UE.

[0332] Aspect 21: An apparatus according to any one of Aspects 1 to 20, wherein, in order to send the report, the processor is further configured to: send one or more non-zero values ​​associated with the one or more receive beam pointing directions at the UE for a single transmit resource of the network entity, at least in part based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

[0333] Aspect 22: The apparatus according to any one of aspects 1 to 21, wherein the indication of the pointing direction of the first receive beam comprises a single-dimensional index associated with the report indicating the pointing direction of the first receive beam.

[0334] Aspect 23: An apparatus according to any one of aspects 1 to 22, wherein the indication of the pointing direction of the first receive beam comprises a CSI report setting identifier, a time slot identifier associated with a transmission time slot of the report, or both.

[0335] Aspect 24: The apparatus of any one of aspects 1 to 23, wherein the report comprises a multi-dimensional report.

[0336] Aspect 25: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a processor; a memory coupled to the processor, the processor configured to obtain a report indicating receive beam information of a UE, a first dimension of the report being associated with one or more transmit resources of the network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE; outputting an indication of a first receive beam pointing direction among the one or more receive beam pointing directions for use in a downlink message of the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources; and outputting the downlink message using the first transmit resource associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

[0337] Aspect 26: An apparatus according to Aspect 25, wherein the processor is further configured to: obtain the first receive beam pointing direction based at least in part on a beam prediction process and the report, wherein the output indication of the first receive beam pointing direction is based on the obtained first receive beam pointing direction.

[0338] Aspect 27: The apparatus of aspect 26, wherein the beam prediction process is based at least in part on a machine learning model.

[0339] Aspect 28: An apparatus according to any one of Aspects 25 to 27, wherein the processor is further configured to: output an indication of the total number of entries associated with the first dimension of the report and the total number of entries associated with the second dimension of the report, wherein the report is based on the indication.

[0340] Aspect 29: The apparatus of aspect 28, wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0341] Aspect 30: An apparatus according to any one of aspects 25 to 29, wherein the processor is further configured to: obtain an indication of a capability of the UE to report the report, wherein the capability indicates a number of entries associated with the second dimension of the report.

[0342] Aspect 31: An apparatus according to any one of Aspects 25 to 29, wherein the processor is further configured to: obtain an indication of the ability of the UE to report the report, wherein the capability indication is the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0343] Aspect 32: An apparatus according to any one of Aspects 25 to 29, wherein the processor is further configured to: obtain an indication of a capability of reporting the report to the UE, wherein the capability indicates the number of non-zero values ​​associated with the one or more receiving beam pointing directions per transmitting resource.

[0344] Aspect 33: An apparatus according to any one of Aspects 25 to 32, wherein in order to obtain the report, the processor is further configured to: obtain one or more non-zero values ​​associated with the one or more receiving beam pointing directions in the report, wherein the one or more non-zero values ​​indicate one or more preferred receiving beam pointing directions associated with the one or more transmitting resources of the network entity.

[0345] Aspect 34: An apparatus according to Aspect 33, wherein the processor is further configured to: obtain an indication of the position of each of the one or more non-zero values ​​in the report, wherein the position is indicated via one of the following items: a bitmap, a combined index, or an index associated with each of the one or more receive beam pointing directions.

[0346] Aspect 35: An apparatus according to any one of Aspects 33 to 34, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0347] Aspect 36: The apparatus according to any one of aspects 33 to 35, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

[0348] Aspect 37: The apparatus according to aspect 36, wherein the processor is further configured to: output an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource.

[0349] Aspect 38: The apparatus according to any one of aspects 33 to 37, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed for the reporting.

[0350] Aspect 39: The apparatus of aspect 38, wherein the processor is further configured to output an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0351] Aspect 40: The apparatus according to any one of aspects 25 to 39, wherein, in order to obtain the report, the processor is further configured to: obtain the number of the one or more receive beam pointing directions at the UE via a first CSI message.

[0352] Aspect 41: An apparatus according to any one of Aspects 25 to 39, wherein, in order to obtain the report, the processor is further configured to: obtain, via a first CSI message, the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource.

[0353] Aspect 42: An apparatus according to any one of Aspects 25 to 39, wherein, in order to obtain the report, the processor is further configured to: obtain, via a first CSI message, a number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0354] Aspect 43: The apparatus according to any one of aspects 40 to 42, wherein, to obtain the report, the processor is further configured to: obtain one or more non-zero values ​​in the report via a second CSI message and based on the first CSI message.

[0355] Aspect 44: An apparatus according to any one of Aspects 40 to 42, wherein, in order to obtain the report, the processor is further configured to: obtain an index associated with each of the one or more non-zero values ​​via a second CSI message and based on the first CSI message.

[0356] Aspect 45: An apparatus according to any one of aspects 40 to 44, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions at the UE associated with the transmit resources of the network entity.

[0357] Aspect 46: An apparatus according to any one of Aspects 25 to 45, wherein in order to output the indication of the first receiving beam, the processor is further configured to: output a multidimensional index associated with the report via the indication, wherein a first dimension of the multidimensional index indicates the first transmitting resource among the one or more transmitting resources of the network entity, and a second dimension of the multidimensional index indicates the first receiving beam pointing direction among the one or more receiving beam pointing directions at the UE.

[0358] Aspect 47: An apparatus according to any one of Aspects 25 to 46, wherein, in order to obtain the report, the processor is further configured to: obtain one or more non-zero values ​​associated with the one or more receive beam pointing directions at the UE for a single transmit resource of the network entity, at least in part based on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

[0359] Aspect 48: The apparatus according to any one of aspects 25 to 47, wherein the indication of the first receive beam pointing direction comprises a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0360] Aspect 49: An apparatus according to any one of aspects 25 to 48, wherein the indication of the pointing direction of the first receive beam comprises a CSI report setting identifier, a time slot identifier associated with a transmission time slot of the report, or both.

[0361] Aspect 50: A method for performing wireless communications at a UE, the method comprising: sending a report indicating receive beam information of the UE, a first dimension of the report being associated with one or more transmit resources of a network entity, and a second dimension of the report being associated with one or more receive beam pointing directions at the UE; receiving an indication of a first receive beam pointing direction among the one or more receive beam pointing directions for a downlink message for the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources; and receiving the downlink message using a receive beam associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

[0362] Aspect 51: The method according to aspect 50, further comprising: receiving an indication of the total number of entries associated with the first dimension of the report and the total number of entries associated with the second dimension of the report, wherein the report is based on the indication.

[0363] Aspect 52: The method of aspect 51, wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0364] Aspect 53: The method according to any one of aspects 50 to 52, further comprising: sending an indication of a capability of the UE to report the report, the capability indicating a number of entries associated with the second dimension of the report.

[0365] Aspect 54: The method according to any one of Aspects 50 to 52 further comprises: sending an indication of the capability of the UE to report the report, the capability indicating the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0366] Aspect 55: According to any one of aspects 50 to 52, the method further includes: sending an indication of the ability of the UE to report the report, the capability indicating the number of non-zero values ​​associated with the one or more receiving beam pointing directions per transmission resource.

[0367] Aspect 56: According to the method described in any one of Aspects 50 to 55, the sending includes: sending one or more non-zero values ​​associated with the one or more receiving beam pointing directions in the report, wherein the one or more non-zero values ​​indicate one or more preferred receiving beam pointing directions associated with the one or more transmitting resources of the network entity.

[0368] Aspect 57: The method according to Aspect 56 further includes: sending an indication of the position of each of the one or more non-zero values ​​in the report, wherein the position is indicated via one of the following items: a bitmap, a combined index, or an index associated with each of the one or more receive beam pointing directions.

[0369] Aspect 58: A method according to any one of Aspects 56 to 57, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0370] Aspect 59: The method according to any one of aspects 56 to 58, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

[0371] Aspect 60: The method of aspect 59, further comprising: receiving an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource.

[0372] Aspect 61: The method according to any one of aspects 56 to 60, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed for the reporting.

[0373] Aspect 62: The method of aspect 61, further comprising: receiving an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0374] Aspect 63: According to the method of any one of aspects 50 to 62, the sending includes: sending the number of the one or more receive beam pointing directions at the UE via a first CSI message.

[0375] Aspect 64: The method according to any one of aspects 50 to 62, wherein the transmitting comprises transmitting the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource via a first CSI message.

[0376] Aspect 65: The method according to any one of aspects 50 to 62, wherein the sending comprises sending the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report via a first CSI message.

[0377] Aspect 66: The method according to any one of aspects 63 to 65, wherein the sending comprises sending the one or more non-zero values ​​in the report via a second CSI message and in accordance with the first CSI message.

[0378] Aspect 67: The method according to any one of aspects 63 to 65, wherein the sending comprises sending an index associated with each of the one or more non-zero values ​​via a second CSI message and in accordance with the first CSI message.

[0379] Aspect 68: The method according to any one of aspects 63 to 67, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction at the UE associated with the transmit resources of the network entity.

[0380] Aspect 69: According to the method described in any one of Aspects 50 to 68, receiving the first beam pointing direction includes: receiving a multidimensional index associated with the report via the indication, wherein the first dimension of the multidimensional index indicates the first transmitting resource among the one or more transmitting resources of the network entity, and the second dimension of the multidimensional index indicates the first receiving beam pointing direction among the one or more receiving beam pointing directions at the UE.

[0381] Aspect 70: According to the method described in any one of Aspects 50 to 69, the sending includes: sending one or more non-zero values ​​associated with the one or more receiving beam pointing directions at the UE for a single transmitting resource of the network entity, at least in part based on the one or more non-zero values ​​associated with the one or more receiving beam pointing directions being equal for each of the one or more transmitting resources.

[0382] Aspect 71: The method according to any one of aspects 50 to 70, wherein the indication of the pointing direction of the first receive beam comprises a single-dimensional index associated with the report indicating the pointing direction of the first receive beam.

[0383] Aspect 72: The method according to any one of aspects 50 to 71, wherein the indication of the pointing direction of the first receive beam comprises a CSI report setting identifier, a time slot identifier associated with a transmission time slot of the report, or both.

[0384] Aspect 73: The method according to any one of aspects 50 to 72, wherein the report comprises a multi-dimensional report.

[0385] Aspect 74: A method for wireless communication at a network entity, the method comprising: obtaining a report indicating receive beam information of a UE, a first dimension of the report being associated with one or more transmit resources of the network entity, and a second dimension of the report being associated with one or more receive beam pointing directions of the UE; outputting an indication of a first receive beam pointing direction among the one or more receive beam pointing directions for use in a downlink message of the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource among the one or more transmit resources; and outputting the downlink message using the first transmit resource associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

[0386] Aspect 75: According to the method of Aspect 74, the method further includes: obtaining the first receiving beam pointing direction at least in part based on the beam prediction process and the report, wherein the output indication of the first receiving beam pointing direction is based on the obtained first receiving beam pointing direction.

[0387] Aspect 76: The method according to Aspect 75, wherein the beam prediction process is based at least in part on a machine learning model.

[0388] Aspect 77: A method according to any one of Aspects 74 to 76, further comprising: outputting an indication of the total number of entries associated with the first dimension of the report and the total number of entries associated with the second dimension of the report, wherein the report is based on the indication.

[0389] Aspect 78: The method of aspect 77, wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

[0390] Aspect 79: The method according to any one of aspects 74 to 78, the method further comprising: obtaining an indication of a capability of the UE to report the report, wherein the capability indicates a number of entries associated with the second dimension of the report.

[0391] Aspect 80: The method according to any one of Aspects 74 to 78, further comprising: obtaining an indication of the capability of the UE to report the report, wherein the capability indication is the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0392] Aspect 81: The method according to any one of Aspects 74 to 78, further comprising: obtaining an indication of a capability of the UE to report the report, wherein the capability indicates the number of non-zero values ​​associated with the one or more receiving beam pointing directions per transmitting resource.

[0393] Aspect 82: According to the method described in any one of Aspects 74 to 81, the obtaining includes: obtaining one or more non-zero values ​​associated with the one or more receiving beam pointing directions in the report, wherein the one or more non-zero values ​​indicate one or more preferred receiving beam pointing directions associated with the one or more transmitting resources of the network entity.

[0394] Aspect 83: The method according to Aspect 82 further includes: obtaining an indication of the position of each of the one or more non-zero values ​​in the report, wherein the position is indicated via one of the following items: a bitmap, a combination index, an index associated with each of the one or more receive beam pointing directions, or a combination thereof.

[0395] Aspect 84: A method according to any one of Aspects 82 to 83, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

[0396] Aspect 85: The method according to any one of aspects 82 to 84, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

[0397] Aspect 86: The method of aspect 85, further comprising: outputting an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource.

[0398] Aspect 87: The method according to any one of aspects 82 to 86, wherein the number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed for the reporting.

[0399] Aspect 88: The method of aspect 87, further comprising: outputting an indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0400] Aspect 89: According to the method of any one of aspects 74 to 88, the obtaining includes: obtaining the number of the one or more receive beam pointing directions at the UE via a first CSI message.

[0401] Aspect 90: The method according to any one of aspects 74 to 88, wherein the obtaining comprises obtaining, via a first CSI message, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmission resource.

[0402] Aspect 91: The method according to any one of aspects 74 to 88, wherein the obtaining comprises obtaining, via a first CSI message, a number of non-zero values ​​associated with the one or more receive beam pointing directions in the report.

[0403] Aspect 92: The method according to any one of aspects 89 to 91, wherein the obtaining comprises obtaining the one or more non-zero values ​​in the report via a second CSI message and based on the first CSI message.

[0404] Aspect 93: According to the method of any one of aspects 89 to 91, the obtaining comprises: obtaining an index associated with each of the one or more non-zero values ​​via a second CSI message and based on the first CSI message.

[0405] Aspect 94: The method according to any one of aspects 89 to 93, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions at the UE associated with the transmit resources of the network entity.

[0406] Aspect 95: According to the method described in any one of Aspects 74 to 94, outputting the first beam pointing direction includes: outputting a multidimensional index associated with the report via the indication, wherein the first dimension of the multidimensional index indicates the first transmitting resource among the one or more transmitting resources of the network entity, and the second dimension of the multidimensional index indicates the first receiving beam pointing direction among the one or more receiving beam pointing directions at the UE.

[0407] Aspect 96: According to the method described in any one of Aspects 74 to 95, the obtaining includes: obtaining one or more non-zero values ​​associated with the one or more receiving beam pointing directions at the UE for a single transmitting resource of the network entity, at least in part based on the one or more non-zero values ​​associated with the one or more receiving beam pointing directions being equal for each of the one or more transmitting resources.

[0408] Aspect 97: The method according to any one of aspects 74 to 96, wherein the indication of the first receive beam pointing direction comprises a single-dimensional index associated with the report indicating the first receive beam pointing direction.

[0409] Aspect 98: The method according to any one of aspects 74 to 97, wherein the indication of the pointing direction of the first receive beam comprises a CSI report setting identifier, a time slot identifier associated with a transmission time slot of the report, or both.

[0410] Aspect 99: The method of any one of aspects 74 to 98, wherein the report comprises a multidimensional report.

[0411] Aspect 100: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 50 to 73.

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

[0413] Aspect 102: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 74 to 99.

[0414] Aspect 103: A non-transitory computer-readable medium storing code comprising instructions executable by a processor to perform the method according to any one of aspects 74 to 99.

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

[0416] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR 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.

[0417] The information and signals described herein may be represented using 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.

[0418] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic components, 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 in conjunction with a DSP core, or any other such configuration).

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

[0420] Computer-readable medium includes both non-transient computer storage media and communication media, and it includes any medium that promotes a 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 a 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 a general or special-purpose computer or a general or special-purpose processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and optical disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Magnetic disk can reproduce data magnetically, and optical disc can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0422] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, and the like. 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.

[0423] In the accompanying 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 applies to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

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

[0425] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: sending a report indicating receive beam information of the UE, wherein a first dimension of the report is associated with one or more transmit resources of a network entity, and a second dimension of the report is associated with one or more receive beam pointing directions at the UE; receiving, based at least in part on the report, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources; as well as The downlink message is received via a receive beam associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

2. The apparatus of claim 1 , wherein the processor is further configured to: An indication of a total number of entries associated with the first dimension of the report and a total number of entries associated with the second dimension of the report is received, wherein the reporting is based on the indication. 3 . The apparatus of claim 2 , wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

4. The apparatus of claim 1 , wherein the processor is further configured to: Send an indication of the UE's ability to report the report, wherein the capability indication is the number of entries associated with the second dimension of the report, the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report, the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, or a combination thereof.

5. The device according to claim 1, wherein To transmit, the processor is configured to: One or more non-zero values ​​associated with the one or more receive beam pointing directions in the report are transmitted, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with the one or more transmit resources of the network entity.

6. The apparatus of claim 5, wherein the processor is further configured to: Send an indication of a location of each of the one or more non-zero values ​​in the report, wherein the location is indicated via one of the following items: a bitmap, a combination index, an index associated with each of the one or more receive beam pointing directions, or a combination thereof.

7. The apparatus of claim 5, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

8. The apparatus of claim 5, wherein a number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

9. The apparatus of claim 8, wherein the processor is further configured to: An indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource is received.

10. The apparatus of claim 5, wherein a number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed for the reporting.

11. The apparatus of claim 10, wherein the processor is further configured to: An indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report is received.

12. The device according to claim 1, wherein To transmit, the processor is configured to: transmitting, via a first channel state information message, a number of the one or more receive beam pointing directions at the UE, a number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, a number of non-zero values ​​associated with the one or more receive beam pointing directions in the report, or any combination thereof; as well as One or more non-zero values ​​in the report, an index associated with each of the one or more non-zero values, or both are sent via a second channel state information message and based on the first channel state information message, wherein the one or more non-zero values ​​indicate a preferred receive beam pointing direction associated with the transmit resources of the network entity at the UE.

13. The device according to claim 1, wherein To receive the first receive beam pointing direction, the processor is configured to: A multidimensional index associated with the report is received via the indication, wherein a first dimension of the multidimensional index indicates the first transmission resource among the one or more transmission resources of the network entity, and a second dimension of the multidimensional index indicates the first reception beam pointing direction among the one or more reception beam pointing directions at the UE.

14. The device according to claim 1, wherein To transmit, the processor is configured to: One or more non-zero values ​​associated with the one or more receive beam pointing directions at the UE are transmitted for a single transmit resource of the network entity based at least in part on the one or more non-zero values ​​associated with the one or more receive beam pointing directions being equal for each of the one or more transmit resources.

15. The apparatus of claim 1, wherein the indication of the first receive beam pointing direction comprises a single-dimensional index associated with the report indicating the first receive beam pointing direction.

16. The apparatus of claim 1, wherein the indication of the pointing direction of the first receive beam comprises a channel state information report setting identifier, a time slot identifier associated with a transmission time slot of the report, or both.

17. The apparatus of claim 1, wherein the report comprises a multi-dimensional report.

18. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; and a memory coupled to the processor, the processor being configured to: obtaining a report indicating receive beam information of a user equipment (UE), a first dimension of the report being associated with one or more transmit resources of the network entity, and the second dimension of the report is associated with one or more receive beam pointing directions of the UE; outputting an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message to the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources; as well as Based at least in part on the indication of the first receive beam pointing direction, the downlink message is output via the first transmit resource associated with the first receive beam pointing direction.

19. The apparatus of claim 18, wherein the processor is further configured to: The first receive beam pointing direction is obtained based at least in part on a beam prediction process and the report, wherein the output indication of the first receive beam pointing direction is in accordance with the obtained first receive beam pointing direction.

20. The apparatus of claim 19, wherein the beam prediction process is based at least in part on a machine learning model.

21. The apparatus of claim 18, wherein the processor is further configured to: An indication of a total number of entries associated with the first dimension of the report and a total number of entries associated with the second dimension of the report is output, wherein the report is based on the indication.

22. The apparatus of claim 21, wherein the total number of entries associated with the first dimension is based at least in part on one or more channel measurement resources, one or more virtual resources, or a combination thereof.

23. The apparatus of claim 18, wherein the processor is further configured to: Obtain an indication of the UE's ability to report the report, wherein the capability indication is the number of entries associated with the second dimension of the report, the number of non-zero values ​​associated with the one or more receive beam pointing directions in the report, the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource, or a combination thereof.

24. The apparatus according to claim 18, wherein To obtain, the processor is configured to: Obtain one or more non-zero values ​​associated with the one or more receive beam pointing directions in the report, wherein the one or more non-zero values ​​indicate one or more preferred receive beam pointing directions associated with the one or more transmit resources of the network entity.

25. The apparatus of claim 24, wherein the processor is further configured to: Obtain an indication of a position of each of the one or more non-zero values ​​in the report, wherein the position is indicated via one of: a bitmap, a combination index, an index associated with each of the one or more receive beam pointing directions, or a combination thereof.

26. The apparatus of claim 24, wherein the one or more non-zero values ​​indicate a beamwidth associated with the one or more preferred receive beam pointing directions, a beamforming gain associated with the one or more preferred receive beam pointing directions, or both.

27. The apparatus of claim 24, wherein a number of non-zero values ​​associated with the one or more receive beam pointing directions is fixed per transmit resource.

28. The apparatus of claim 27, wherein the processor is further configured to: An indication of the number of non-zero values ​​associated with the one or more receive beam pointing directions per transmit resource is output.

29. A method for wireless communication at a user equipment (UE), the method comprising: sending a report indicating receive beam information of the UE, wherein a first dimension of the report is associated with one or more transmit resources of a network entity, and a second dimension of the report is associated with one or more receive beam pointing directions at the UE; receiving, based at least in part on the report, an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for a downlink message for the UE, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources; as well as The downlink message is received using a receive beam associated with the first receive beam pointing direction based at least in part on the indication of the first receive beam pointing direction.

30. A method of wireless communication at a network entity, the method comprising: Obtaining a report indicating receive beam information of a user equipment (UE), wherein a first dimension of the report is associated with one or more transmit resources of the network entity and a second dimension of the report is associated with one or more receive beam pointing directions of the UE; outputting an indication of a first receive beam pointing direction of the one or more receive beam pointing directions for use in a downlink message to the UE based at least in part on the report, the first receive beam pointing direction being associated with a first transmit resource of the one or more transmit resources; as well as Based at least in part on the indication of the first receive beam pointing direction, the downlink message is output using the first transmit resources associated with the first receive beam pointing direction.

Images