Method of framework for channel-based beamforming

Abstract

Wireless communication equipment, methods, including computer programs encoded on a storage medium, for beamforming weight measurement and reporting are provided. The UE quantizes (310, 410) beamforming weights based on measured qualities of one or more downlink reference signals, RS, transmitted by a network entity, NE, using a plurality of antenna ports. The UE sends a beamforming weight report to the NE (312, 412), the beamforming weight report comprising at least one set of beamforming weights for the plurality of antenna ports. The UE may select at least one set of beamforming weights based on a predetermined rule.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to beamforming in wireless communications. Background Art

[0002] The Third Generation Partnership Project (3GPP) has specified a radio interface called Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes the 5G Core (5GC) network, the 5G Radio Access Network (5G-RAN), and user equipment (UE). Compared to previous generation cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems are generally configured to provide various telecommunication services (e.g., telephony, video, data, messaging, broadcast, etc.) based on multiple access technologies (such as Orthogonal Frequency Division Multiple Access (OFDMA)) that support communication with multiple UEs. The advancement of mobile broadband continues the development of such wireless communication technologies. For example, in conventional beamforming, the beam direction of a selected (optimal) beam may not actually match the optimal direction for a UE. Summary of the Invention

[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0005] Conventionally, network entities and UEs perform beam management using codebook-based beamforming. In codebook-based beamforming, a specific beam, and therefore a (predetermined) beam direction, is identified as optimal. However, in codebook-based beamforming, the beam direction selected (as the optimal) beam may not actually match the optimal direction for the UE.

[0006] Various aspects of the present disclosure address the above and other deficiencies by using channel-based beamforming. In channel-based beamforming, the UE or network entity obtains the original channel or the eigenvector of the original channel, and then the UE or NE identifies the best UE beam and NE beam based on the eigenvector and eigenvalue of the original channel. In some examples, the NE may send control signaling that configures the UE to generate a beamforming weight report based on a multi-port RS or a multi-resource RS. The control signal configures the beamforming weight report to select at least one set of beamforming weights based on predetermined rules. The NE then sends the multi-port RS or the multi-resource RS. The UE measures and quantizes the beamforming weights based on the measured quality of the multi-port RS or the multi-resource RS. The UE then sends a beamforming weight report indicating the beamforming weights. The NE uses the beamforming weight report to generate a beam for communicating with the UE.

[0007] According to some aspects, a UE quantizes beamforming weights based on measured quality of one or more downlink reference signals (RSs) transmitted by a network entity (NE) using multiple antenna ports. The UE sends a beamforming weight report to the NE, the beamforming weight report including at least one set of beamforming weights for the multiple antenna ports.

[0008] According to some aspects, a NE configures a beamforming weight report associated with one or more reference signals (RSs). The NE receives a beamforming weight report from a UE, the beamforming weight report including beamforming weights based on measured quality of the one or more RSs.

[0009] Advantageously, by using channel-based beamforming, network entities and / or UEs can identify better network beams or UE beams than with codebook-based beamforming. Consequently, network entities and UEs can more efficiently perform beam management, resulting in higher signal received power or signal-to-noise ratio. Consequently, channel-based beamforming improves the performance of wireless communication systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A diagram of a wireless communication system including a plurality of user equipments (UEs) and network entities communicating through one or more cells is shown.

[0011] Figure 2 is a block diagram illustrating an example of solving problems in codebook-based beamforming.

[0012] Figure 3 is a signaling diagram illustrating an example of communication between a UE and a network entity for multi-port RS based beamforming weight measurement and reporting.

[0013] Figure 4 is a block diagram illustrating an example of UE behavior for multi-port RS based beamforming weight measurement and reporting.

[0014] Figure 5 is a block diagram illustrating an example of network entity behavior for multi-port RS-based beamforming weight measurement and reporting.

[0015] Figure 6 is a block diagram illustrating an example of a TDM+FDM-based multi-port RS for beamforming weight measurement and reporting.

[0016] Figure 7A and Figure 7B is a block diagram illustrating an example of a TDM+CDM based multi-port RS for beamforming weight measurement and reporting.

[0017] Figure 8A is a block diagram showing an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) is used for phase tracking in each symbol and there are up to 3 ports per symbol.

[0018] Figure 8B is a block diagram showing an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, where there is one port (port 3000) for phase tracking in each symbol and up to 2 ports per symbol.

[0019] Figure 9A is a block diagram illustrating an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, with one additional port in each symbol for phase tracking and up to 3 ports per symbol.

[0020] Figure 9B is a block diagram illustrating an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, with one additional port in each symbol for phase tracking and up to 2 ports per symbol.

[0021] Figure 10A and Figure 10B is a block diagram showing an example of a TDM+CDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) (without OCC) is used for phase tracking in each symbol, with up to 3 ports per symbol.

[0022] Figure 11A and Figure 11Bis a block diagram showing an example of a TDM+CDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) (without OCC) is used for phase tracking in each symbol, with a maximum of 2 ports per symbol.

[0023] Figure 12A and Figure 12B is a block diagram illustrating an example of a TDM+CDM based multi-port RS for beamforming weight measurement and reporting, with one additional port (without OCC) in each symbol for phase tracking.

[0024] Figure 13 is a block diagram illustrating an example of partial antenna or antenna port measurement.

[0025] Figure 14 is a block diagram illustrating an example of beamforming weight reporting with complete eigenvector reporting.

[0026] Figure 15 is a block diagram illustrating an example of beamforming weight reporting with only NZP coefficient reporting.

[0027] Figure 16 is a block diagram illustrating an example of beamforming weight reporting with only the top N strongest coefficients reported.

[0028] Figure 17 is a block diagram illustrating an example of beamforming weight grouping and codebook subset restriction based on codebook eigenvector reporting.

[0029] Figure 18 is a signaling diagram illustrating an example of communication between a UE and a network entity for multi-resource RS based beamforming weight measurement and reporting.

[0030] Figure 19 is a block diagram illustrating an example of UE behavior for multi-resource RS based beamforming weight measurement and reporting.

[0031] Figure 20 is a block diagram illustrating an example of network entity behavior for multi-resource RS-based beamforming weight measurement and reporting.

[0032] Figure 21 is a block diagram illustrating an example of a multi-resource RS with antenna or antenna port switching.

[0033] Figure 22 is a block diagram illustrating an example of a multi-resource RS using partial antenna or antenna port switching.

[0034] Figure 23 is a block diagram illustrating an example of multi-resource RS transmission in which antenna switching is first performed.

[0035] Figure 24 is a block diagram illustrating an example of performing repeated multi-resource RS transmission first.

[0036] Figure 25 Flowchart of a method of wireless communication at a UE for beamforming weight measurement and reporting.

[0037] Figure 26 is a flow chart of a method of wireless communication for beamforming weight measurement and reporting at a network entity.

[0038] Figure 27 is a diagram showing a hardware implementation for an example UE apparatus.

[0039] Figure 28 is a diagram illustrating a hardware implementation for one or more example network entities. DETAILED DESCRIPTION

[0040] Figure 1 Figure 100 shows a wireless communication system associated with multiple cells 190. The wireless communication system includes a user equipment (UE) 102 and a base station / network entity 104. Some base stations may include a converged base station architecture, while other base stations may include a decomposed base station architecture. The converged base station architecture includes a radio unit (RU) 106, a distributed unit (DU) 108, and a centralized unit (CU) 110, which are configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack that is physically or logically distributed across two or more units (e.g., RU 106, DU 108, CU 110). For example, CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RUs 106. Each of the RU 106, DU 108, and CU 110 may be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / network entity 104 (e.g., a converged base station or a disaggregated unit of a base station, such as the RU 106, DU 108, or CU 110) may be referred to as a transmit-receive point (TRP).

[0041] The operation and / or network design of the base station 104 can be based on the aggregation characteristics of base station functions. For example, a disaggregated base station architecture is utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtualized radio access network (vRAN) (which may also be referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functions across two or more units located at various physical locations, as well as distributing functions for at least one unit virtually, which can achieve flexibility in network design. Various units of a disaggregated base station architecture or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit. For example, the base station 104a / 104e and / or RUs 106a-106d can communicate with UEs 102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In an example, multiple RUs 106 and / or base stations 104 can simultaneously serve a UE 102, such as via intra-cell and / or inter-cell access links between the UE 102 and the RUs 106 / base stations 104.

[0042] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to send or receive information / signals via a wired or wireless transmission medium. Base station 104 or any of the one or more decomposed base station units may be configured to communicate with one or more other base stations 104 or one or more other decomposed base station units via a wired or wireless transmission medium. In an example, a processor, memory, and / or controller associated with executable instructions of the interface may be configured to provide communication between base stations 104 and / or one or more decomposed base station units via a wired or wireless transmission medium. For example, a wired interface may be configured to send or receive information / signals via a wired transmission medium, such as via a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. The BBU 112 includes the DU 108 and the CU 110, and may also have a wired interface (e.g., a midhaul link) configured between the DU 108 and the CU 110 to transmit or receive information / signals between the DU 108d and the CU 110d. In a further example, a wireless interface, which may include a receiver, transmitter, or transceiver (such as an RF transceiver), may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information for transmission between the RU 106a of the cell 190a and the base station 104e of the cell 190e via the cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0043] The RU 106 may be configured to implement lower layer functions. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node hosting RF processing functions or lower layer PHY functions, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functions of the RU 106 may be based on functional partitioning, such as lower layer functional partitioning.

[0044] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beam set 132 of RU 106b and a second communication beam set 134b of UE 102b, which may correspond to inter-cell communication beams or, in some examples, to cross-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beam set 134a of UE 102b and a fourth communication beam set 136 of RU 106a. Both real-time and non-real-time features of control and user plane communications of RU 106 can be controlled by the associated DU 108.

[0045] Any combination of RU 106, DU 108, and CU 110, or any reference to any of them individually, may correspond to base station 104. Thus, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 may relay communications between UE 102 and the core network. Base station 104 may be associated with a macro cell of a high-power cellular base station and / or a small cell of a low-power cellular base station. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femto cells, pico cells, micro cells, and the like. A cell structure including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network."

[0046] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from a base station 104 / RU 106 to a UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions, and downlink transmissions may also be referred to as forward link transmissions. For example, RU 106 d utilizes antenna 114 of base station 104 d in cell 190 d to transmit downlink / forward link communications to UE 102 d or receive uplink / reverse link communications from UE 102 d over a Uu interface associated with an access link between UE 102 d and base station 104 d / RU 106 d.

[0047] The communication link between the UE 102 and the base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. The UE 102 and the base station 104 / RU 106 can utilize a spectrum bandwidth of Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) per carrier, allocated in a carrier aggregation of up to a total of Yx MHz, with x component carriers (CCs) used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along the spectrum. In an example, uplink and downlink carriers can be allocated in an asymmetric manner, with more or fewer carriers allocated for the uplink or downlink. The component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

[0048] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via a sidelink. For example, the sidelink communication / D2D link utilizes the spectrum of a wireless wide area network (WWAN) associated with uplink and downlink communications. The sidelink communication / D2D link can also use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and / or a physical sidelink control channel (PSCCH) to transmit information between UEs 102a and 102s. Such sidelink / D2D communication can be performed via various wireless communication systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, long term evolution (LTE) systems, new radio (NR) systems, and the like.

[0049] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on the different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is typically associated with two operating frequency ranges (FR), referred to as Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 ranges from 410 MHz to 7.125 GHz, and FR2 ranges from 24.25 GHz to 71.0 GHz, including FR2-1 (24.25 GHz to 52.6 GHz) and FR2-2 (52.6 GHz to 71.0 GHz). Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is distinct from the "extremely high frequency" (EHF) band, but is a close subset of it. The EHF band ranges from 30 GHz to 300 GHz and is sometimes also referred to as the "millimeter wave" band. Frequencies between FR1 and FR2 are often referred to as "mid-band" frequencies. The operating band for mid-band frequencies may be referred to as Frequency Range 3 (FR3), which ranges from 7.125 GHz to 24.25 GHz. Frequency bands within FR3 may include characteristics of FR1 and / or FR2. Thus, the features of FR1 and / or FR2 may be extended to mid-band frequencies. Higher operating bands have been identified to extend 5G NR communications above the 52.6 GHz associated with the upper limit of FR2. Three of these higher operating bands include FR2-2 (ranging from 52.6 GHz to 71.0 GHz), FR4 (ranging from 71.0 GHz to 114.25 GHz), and FR5 (ranging from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF band. Therefore, unless otherwise expressly stated herein, the term "sub-6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Further, unless otherwise expressly stated herein, the term "millimeter wave" or mmW may refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2-1, FR4, FR2-2, and / or FR5, or frequencies that may be within the EHF band.

[0050] UE 102 and base station 104 / RU 106 may each include multiple antennas. The multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, RU 106b may transmit downlink beamformed signals to UE 102b based on a first communication beam set 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamformed signals from RU 106b based on a second communication beam set 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamformed signals to RU 106b based on a second communication beam set 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamformed signals from UE 102b in one or more receive directions of RU 106b.

[0051] UE 102b may perform beam training to determine optimal receive and transmit directions for beamformed signals. The transmit and receive directions of UE 102 and base station 104 / RU 106 may or may not be the same. In a further example, beamformed signals may be transmitted between a first base station / RU 106a and a second base station 104e. For example, base station 104e of cell 190e may transmit beamformed signals to RU 106a based on communication beam 138 in one or more transmit directions of base station 104e. RU 106a may receive beamformed signals from base station 104e of cell 190e based on RU communication beam 136 in one or more receive directions of RU 106a. In a further example, base station 104e transmits downlink beamformed signals to UE 102e based on communication beam 138 in one or more transmit directions of base station 104e. The UE 102e receives downlink beamformed signals from the base station 104e in one or more receive directions of the UE 102e based on the UE communication beam 130. The UE 102e may also transmit uplink beamformed signals to the base station 104e in one or more transmit directions of the UE 102e based on the UE communication beam 130, so that the base station 104e can receive the uplink beamformed signals from the UE 102e in one or more receive directions of the base station 104e.

[0052] The base station 104 may include and / or be referred to as a network entity. That is, a “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB), a first generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network device, or other related terms. The base station 104 or an entity at the base station 104 may be implemented as an IAB node, a relay node, a sidelink node, a converged (monolithic) base station having the RU 106 and the BBU 112 including the DU 108 and the CU 110, or as a decomposed base station including one or more RUs 106, DUs 108, and / or CUs 110. A converged or disaggregated set of base stations may be referred to as a next generation radio access network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such a case, base station 104e may be the primary node, while base station / RU 160a may be the secondary node.

[0053] Uplink / downlink signaling may also be communicated via a satellite positioning system (SPS) 114. In an example, the SPS 114 of cell 190c may communicate with one or more UEs 102 (such as UE 102c) and one or more base stations 104 / RUs 106 (such as RU 106c). The SPS 114 may correspond to one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round-trip time (RTT) and / or multiple RTTs), wireless local area network (WLAN) signals, a terrestrial beacon system (TBS), sensor-based information, NR enhanced cell ID (NR E-CID) technology, downlink angle of departure (DL-AoD), downlink time difference of arrival (DL-TDOA), uplink time difference of arrival (UL-TDOA), uplink angle of arrival (UL-AoA), and / or other systems, signals, or sensors.

[0054] Still refer to Figure 1In certain aspects, any of the UEs 102 may include a beamforming weight component 140 configured to quantize beamforming weights based on measured quality of one or more downlink reference signals, RS, transmitted by a network entity, NE, using a plurality of antenna ports. The beamforming weight component 140 is further configured to send a beamforming weight report to the NE, the beamforming weight report including at least one set of beamforming weights for the plurality of antenna ports.

[0055] In certain aspects, any of the base stations 104 or a network entity of the base station 104 may include a report configuration component 150 configured to configure a beamforming weight report associated with one or more reference signals (RSs). The report configuration component 150 is further configured to receive a beamforming weight report from a user equipment, the beamforming weight report including beamforming weights based on measured quality of the one or more RSs.

[0056] therefore, Figure 1 Describes aspects that may be combined with one or more of the other figures described herein (such as Figures 2 to 28 Further, although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-Advanced (LTE-A), and other wireless technologies such as 6G.

[0057] Figure 2 is a block diagram 200 illustrating an example of solving the problem in codebook-based beamforming. A network entity 104 may maintain multiple beams. The network entity applies different beams to different downlink reference signals, such as synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs), to perform beam measurements. In conventional codebook-based beamforming, the UE 102 measures the layer 1 reference signal received power (L1-RSRP) or layer 1 signal to interference plus noise ratio (L1-SINR) of each SSB / CSI-RS to identify the best network beam. However, for codebook-based beamforming, the number of beams is always limited. Therefore, the beam codebook may not always be able to cover the best direction for the UE. For example, Figure 2 As shown in FIG, the network entity 104 maintains the plurality of beams 210, however, for the UE, the best direction 220 is between two beams in the plurality of beams 210. Therefore, the plurality of beams 210 from the beam codebook fails to cover the best direction 220 for the UE 102.

[0058] In some examples, network entity 104 and UE 102 use channel-based beamforming to improve performance. Network entity 104 and UE 102 can perform channel-based beamforming by obtaining an original channel. The original channel refers to a channel without beamforming from the network entity. For example, the original channel estimate refers to data recovered in the channel estimate based on known downlink reference signals from one or more antenna elements in the network entity. If the UE or network entity is able to obtain the original channel, the UE or network entity can identify the best UE beam and the best network entity beam based on the eigenvector of the original channel as follows.

[0059] Where H indicates the original channel between the network entity and the UE, and the dimension is ; is the number of receive antenna ports on the UE side, and is the number of transmit antenna ports on the network entity side. Then, the optimal network beam can be derived as the first M in the matrix V p Row, where M p Indicates the maximum number of antenna ports used to transmit one downlink signal.

[0060] The optimal UE beam can be derived as the matrix The first Q in p row, where Q p indicates the maximum number of antenna ports for receiving one downlink signal, and the channel eigenvector is calculated as follows :

[0061] Compared to codebook-based beamforming, channel-based beamforming can provide significant gains, such as more than 5 dB L1-RSRP gain. The network entity can select up to M p Antenna ports transmit downlink signals, where M p Much smaller than the total number of antenna ports N in the network entity p It is challenging for a network entity to obtain the original channel or the eigenvector of the original channel for channel-based beamforming.

[0062] The present disclosure provides a framework for channel-based beamforming, including control signaling for channel-based beamforming, downlink reference signals for beamforming weight measurement using symbol-level antenna or antenna port switching, and feedback for beamforming weights. In this way, beam management can be based on channel-based beamforming, which can identify better network beams compared to codebook-based beamforming, thereby improving system performance.

[0063] In some examples, the network entity and the UE use multi-port reference signal (RS)-based beamforming weight measurement and reporting in channel-based beamforming. In some examples, the network entity and the UE use multi-resource RS-based beamforming weight measurement and reporting in channel-based beamforming. Both multi-port reference signal (RS)-based beamforming weight measurement and reporting and multi-resource RS-based beamforming weight measurement and reporting are discussed below.

[0064] Figure 3 3 is a signaling diagram 300 illustrating an example of communication between UE 102 and network entity 104 for beamforming weight measurement and reporting based on multi-port RS. Network entity 104 may correspond to a base station or a unit of a base station such as RU 106, DU 108, CU 110, etc. Figure 3 , the UE 102 may send 303 a UE capability report indicating UE capabilities, the UE capabilities indicating whether the UE supports beamforming weight measurement and reporting based on multi-port RS. In one example, the UE 102 sends UE capabilities regarding beamforming weight measurement and reporting based on multi-port RS, the UE capabilities indicating at least one of the following: whether the UE supports beamforming weight measurement and reporting based on multi-port RS; the maximum number of configured multi-port RS resources per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, and / or across all frequency bands; the maximum number of multi-port RS resources in a time slot per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, and / or across all frequency bands; and the number of ports of the multi-port RS. The UE may report UE capabilities per feature set, per frequency band, per frequency band combination, or across all frequency bands.

[0065] Additionally, the network entity 104 may obtain UE capabilities from another network entity 104 or a core network (eg, an access and mobility management function (AMF)).

[0066] Based on the UE capabilities, the network entity 104 sends 304 first control signaling, such as RRC signaling (RRCReconfiguration), which configures at least one beamforming weight report based on at least one multi-port RS. The network entity 104 may send 304 a control signal that configures the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule. For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the network entity 104 may send 306 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or the at least one multi-port RS for beamforming weight measurement and reporting. For example, to trigger the beamforming weight report, the second control signaling may indicate a report ID for the beamforming weight report, and the UE 102 may identify the time / frequency resources of the uplink signal for the beamforming weight report. For example, to trigger at least one multi-port RS, the second control signaling may indicate at least one multi-port RS resource index, and the UE may identify the location of the at least one multi-port RS resource, such as the time / frequency resource for the at least one multi-port RS. The network entity 104 then transmits 308 the at least one multi-port RS on the configured at least one multi-port RS resource. In one example, the multi-port RS is a CSI-RS.

[0067] UE 102 measures at least one multi-port RS. UE 102 quantizes 310 beamforming weights based on the measured quality of at least one multi-port RS. UE 102 quantizes the beamforming weights based on the received first control signaling and / or second control signaling. For example, the beamforming weights are associated with a floating-point matrix calculated based on the measured quality of at least one multi-port RS. As an example, the beamforming weights form eigenvectors of the floating-point matrix. For example, the beamforming weights are based on the floating-point matrix. UE 102 quantizes the floating-point matrix by one or more fixed-point indicators for beamforming weight reporting. In one example, the UE may report each coefficient in the floating-point matrix by a 3-bit indicator for amplitude indication and a 2-bit indicator for angle indication. In another example, the UE reports only the first N coefficients. Then, the UE may additionally report another indicator to indicate the positions of the reported N coefficients. This will be described below in conjunction with Figures 13 to 17 Discusses the details of beamforming weight reporting.

[0068] The network entity identifies 314 the beamforming weights based on the configuration in the first control signaling and / or the second control signaling. Figure 4 and Figure 5The UE behavior and network entity behavior for beamforming weight measurement and reporting based on multi-port RS are discussed in.

[0069] In the present disclosure, unless otherwise specified, RRC signaling may indicate an RRC reconfiguration message from a network entity to a UE, or a system information block (SIB), where the SIB may be an existing SIB (e.g., SIB1) or a new SIB (e.g., SIB J, where J is an integer greater than 21) sent by the network entity.

[0070] Figure 4 FIG4 is a block diagram 400 illustrating an example of UE behavior for beamforming weight measurement and reporting based on multi-port RS. Figure 4 , the UE 102 may send 403 UE capabilities regarding multi-port RS based beamforming weight measurement and reporting.

[0071] The UE 102 may receive 404 first control signaling, such as RRC signaling (RRCReconfiguration), that configures at least a beamforming weight report based on at least one multi-port RS. The UE 102 may also receive 304 a control signal that configures the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule.

[0072] For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the UE may receive 406 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or the configured multi-port RS for beamforming weight measurement and reporting. In one example, the multi-port RS is a CSI-RS. The UE then receives 408 at least one multi-port RS for beamforming weight measurement and reporting.

[0073] The UE 102 measures and quantizes 410 beamforming weights based on the at least one multi-port RS and the received first control signaling and / or second control signaling. The UE 102 sends 412 a beamforming weight report to a network entity.

[0074] Figure 5 is a block diagram illustrating an example of network entity behavior for beamforming weight measurement and reporting based on multi-port RS. Figure 5 , the network entity 104 may receive 503 UE capabilities regarding multi-port RS based beamforming weight measurement and reporting.

[0075] The network entity 104 sends 504 first control signaling, such as RRC signaling (RRCReconfiguration), which configures at least a beamforming weight report based on at least one multi-port RS. The network entity 104 can configure 504 the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule.

[0076] For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the network entity 104 may send 506 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or the configured multi-port RS for beamforming weight measurement and reporting. In one example, the multi-port RS is a CSI-RS. Then, the network entity 104 sends 508 at least one multi-port RS for beamforming weight measurement and reporting.

[0077] After the UE 102 measures and quantizes 410 the beamforming weights based on at least one multi-port RS, the network entity 104 receives 512 the beamforming weight report from the UE.

[0078] Figure 6 6 is a block diagram 600 illustrating an example of a TDM+FDM-based multi-port RS for beamforming weight measurement and reporting. The network entity 104 may transmit a multi-port RS having multiple antenna ports with different structures using relevant control signaling. The multi-port RS may include multiple parts that are transmitted or transmitted using multiple antenna ports. In the present disclosure, the terms "port" and "antenna port" are used interchangeably. In the present disclosure, a network entity transmitting a port may refer to a portion of the multi-port RS that the network entity transmits using the port. In some examples, the network entity 104 transmits different portions of the multi-port RS of different port groups in different symbols, and the network entity multiplexes portions of the multi-port RS of the ports within the group in a frequency domain multiplexing (FDM) manner. For example, the network entity 104 transmits different portions of the multi-port RS of different ports in the antenna port group in different subcarriers. As Figure 6 As shown in FIG, the network entity 104 transmits multiple parts of the multi-port RS in multiple symbols through multiple port groups including group 1 (ports 3000 and 3001), group 2 (ports 3002 and 3003), group 3 (ports 3004 and 3005), and group 4 (ports 3006 and 3007). Each port group in the multiple port groups is located in one symbol in the multiple symbols. The network entity 104 transmits different parts of the multi-port RS in different subcarriers through ports 3000 and 3001 in port group 1.

[0079] The number of ports in the port group may be predefined or configured by the network entity through the first control signaling or the second control signaling. The number of ports in the port group may be predefined or configured by the network entity through the first control signaling or the second control signaling.

[0080] In some implementations, the network entity 104 may configure a symbol and / or time slot index for each port group via the first control signaling and / or the second control signaling. In some other implementations, the network entity 104 may configure a starting symbol and / or time slot index for each port group via the first control signaling and / or the second control signaling. The network entity 104 may further configure a symbol offset between each port group. Alternatively, the symbol offset may be predefined, for example, so that different port groups are multiplexed in consecutive symbols.

[0081] In some implementations, the network entity 104 may configure the bandwidth of the multi-port RS through the first control signaling or the second control signaling. In some other implementations, the bandwidth of the multi-port RS may be predefined, for example, the same as the bandwidth of the bandwidth part.

[0082] In some implementations, the network entity 104 may configure the frequency domain density and / or resource element (RE) offset for each port through the first control signaling and / or the second control signaling. In some other implementations, the frequency domain density per port may be predefined, for example, 3 REs per resource block (RB). The RE offset per port may be predefined, for example, for even-numbered ports, the RE offset is 0, and for odd-numbered ports, the RE offset is 2.

[0083] In some implementations, the network entity 104 may configure the SSB as a quasi-collocated (QCL) source of the multi-port RS through the first control signaling or the second control signaling. The UE 102 may then identify the receive beam of the multi-port RS based on the measurement of the SSB.

[0084] Figure 7A and Figure 7B is a block diagram illustrating an example of a TDM+CDM-based multi-port RS for beamforming weight measurement and reporting. In this example, the network entity 104 transmits different parts of the multi-port RS from different port groups in different symbols, and the network entity 104 multiplexes the parts of the multi-port RS from the ports within the group in a code domain multiplexing (CDM) manner, for example, the network entity transmits different parts of the multi-port RS from different ports in different groups through different orthogonal cover codes (OCCs). In combination with Figure 6Compared to the example discussed above, the difference is that the network entity 104 transmits the portion of the multi-port RS from each port in the group in the same subcarrier but with different OCCs. The OCC code for each portion of the multi-port RS from each port can be predefined, for example, [1, 1] for even ports and [1, -1] for odd ports. The UE 102 can then distinguish different portions of the multi-port RS from different ports in the port group by applying different OCCs for despreading. Figure 7A and Figure 7B As shown in FIG, the network entity 104 transmits multiple portions of multi-port RSs from multiple port groups including group 1 (ports 3000 and 3001), group 2 (ports 3002 and 3003), group 3 (ports 3004 and 3005), and group 4 (ports 3006 and 3007) in multiple symbols. Each port group in the multiple port groups is located in one symbol in the multiple symbols. The network entity 104 transmits portions of the multi-port RSs from ports 3000 and 3001 in port group 1 in the same subcarrier but using different OCCs. For example, the network entity 104 transmits the portion of the multi-port RS from port 3000 using OCC code "1" and transmits the portion of the multi-port RS from port 3001 using OCC code "-1" in the same subcarrier.

[0085] Figure 8A is a block diagram showing an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) is used for phase tracking in each symbol and there are up to 3 ports per symbol. Figure 8B is a block diagram illustrating an example of a TDM+FDM-based multi-port RS for beamforming weight measurement and reporting, wherein one port (port 3000) is used for phase tracking in each symbol, with up to two ports per symbol. In some examples, a network entity transmits different groups of ports in different symbols, and the network entity multiplexes the ports within a group in a frequency domain multiplexing (FDM) manner, for example, the network entity transmits different ports in a group in different subcarriers. The network entity utilizes the multi-port RS to transmit at least one port for phase tracking in each symbol.

[0086] refer to Figure 8A In this example, the network entity 104 transmits a TDM+FDM-based multi-port RS in different port groups in different symbols, where one port (port 3000) is used for phase tracking in each symbol. Figure 8A As shown in , the network entity is able to send 3 ports simultaneously.

[0087] refer to Figure 8BIn this example, the network entity 104 transmits a TDM+FDM-based multi-port RS in different port groups in different symbols, where one port (port 3000) is used for phase tracking in each symbol. Figure 8B As shown in , the network entity is able to send 3 ports simultaneously.

[0088] refer to Figure 8A and Figure 8B By using at least one port in each symbol for phase tracking using a multi-port RS, the UE 102 can compare the phase offset measured in the port and perform phase compensation for each antenna port group.

[0089] In some examples, the UE may calculate the channel from all ports as follows:

[0090] in Indicates the phase offset of port group j, with the phase in the phase port group as a reference; Indicates the measured channel of port group j, with dimension is the number of receive antenna ports on the UE side, and is the number of transmit antenna ports in each port group.

[0091] In some implementations, the network entity sends the at least one port for phase tracking as at least one port in a port group. In some other implementations, the network entity sends the at least one port for phase tracking as an independent port.

[0092] In some implementations, the network entity configures the frequency domain density, frequency offset, and / or time domain density of at least one port used for phase tracking through first control signaling and / or second control signaling. In some other implementations, the frequency domain density, frequency offset, and / or time domain density of at least one port used for phase tracking is predefined.

[0093] Figure 9A is a block diagram illustrating an example of a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, with one additional port in each symbol for phase tracking and up to 3 ports per symbol. Figure 9B is a block diagram illustrating an example of a TDM+FDM-based multi-port RS for beamforming weight measurement and reporting, with one additional port for phase tracking in each symbol, with up to two ports per symbol. In some examples, the network entity transmits one additional port for phase tracking in each symbol.

[0094] refer to Figure 9A and Figure 9B, the network entity 104 sends a multi-port RS based on TDM+FDM, where there is an additional port (port 6000) in each symbol for phase tracking. Figure 9A As shown in , the network entity can send 3 ports at the same time. Figure 9B As shown in , the network entity is able to send 2 ports simultaneously.

[0095] Figure 10A and Figure 10B is a block diagram showing an example of a TDM+CDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) (without OCC) is used for phase tracking in each symbol, with up to 3 ports per symbol. Figure 11A and Figure 11B is a block diagram illustrating an example of a TDM+CDM-based multi-port RS for beamforming weight measurement and reporting, wherein one port (port 3000) (without OCC) is used for phase tracking in each symbol, and there are at most two ports per symbol. In some examples, the network entity 104 sends different port groups in different symbols, and the network entity 104 multiplexes the ports within the group in a code domain multiplexing (CDM) manner, that is, the network entity sends different ports in different groups through different orthogonal cover codes (OCCs). In combination with Figure 8A 、 Figure 8B 、 Figure 9A and Figure 9B Compared to the previously discussed example, the network entity transmits each port within the group in the same subcarrier but with a different OCC. The OCC code for each port can be predefined, for example, [1, 1] for even ports and [1, -1] for odd ports. The UE can then distinguish between different ports within the port group by applying different OCCs for despreading. Furthermore, the UE 102 can transmit at least one port for phase tracking with or without an OCC.

[0096] refer to Figure 10A 、 Figure 10B 、 Figure 11A and Figure 11B , the network entity 104 sends a TDM+FDM based multi-port RS for beamforming weight measurement and reporting, where one port (port 3000) (without OCC) is used for phase tracking in each symbol. Figure 10A and Figure 10B As shown in , the network entity 104 is able to send 3 ports simultaneously. Figure 11A and Figure 11B As shown in , the network entity 104 is able to send 2 ports simultaneously.

[0097] Figure 12A and Figure 12B1 is a block diagram illustrating an example of a TDM+CDM-based multi-port RS for beamforming weight measurement and reporting, wherein one additional port (without OCC) is used for phase tracking in each symbol. In this example, the network entity 104 transmits a TDM+FDM-based multi-port RS, wherein one additional port (port 6000) is used for phase tracking in each symbol.

[0098] In some examples, the network entity 104 configures a multiplexing scheme, such as FDM or CDM, for the ports in the port group through the first control signaling and / or the second control signaling. The network entity may configure the presence of at least one port for phase tracking through the first control signaling and / or the second control signaling. Then, the network entity may configure the presence of at least one port for phase tracking based on the combination of 7A to 12B The discussed example configures and sends a multi-port RS.

[0099] In some examples, UE 102 reports UE capabilities or UE assistance information indicating at least one of the following parameters: a supported or preferred multiplexing scheme for ports within a port group, such as FDM or CDM; and a supported or preferred number of ports for phase tracking. In one example, the UE can report that the UE does not support at least one port for phase tracking by reporting the number of ports for phase tracking as 0 or not reporting the number of ports for phase tracking.

[0100] In some examples, UE 102 reports an indicator indicating beamforming weight reporting based on the number of ports of a multi-port RS. For example, the beamforming weights are associated with a floating-point matrix calculated based on the measured quality of at least one multi-port RS. As an example, the beamforming weights form eigenvectors of the floating-point matrix. For example, the beamforming weights are based on the floating-point matrix. UE 102 quantizes the floating-point matrix using one or more fixed-point indicators for beamforming weight reporting. UE 102 quantizes the floating-point matrix using one or more fixed-point indicators for beamforming weight reporting.

[0101] In some implementations, the beamforming weights and dimensions are × 1 or 2 matrices (e.g., floating-point matrices), where Indicates the number of ports of the multi-port RS. In some other implementations, the beamforming weights and dimensions are × The matrix is ​​associated with is the maximum or minimum number of ports in a symbol of a multi-port RS. In some other implementations, the beamforming weights are related to the dimension × The matrix is ​​associated with The network entity configures the first control signaling.

[0102] Figure 13 is a block diagram illustrating an example of partial antenna or antenna port measurement. In some examples, the beamforming weights may have more ports, such as more rows, than the number of ports of the multi-port RS. Figure 13 , the network entity transmits the multi-port RS only from a first subset of antennas or antenna ports (e.g., 1351). The UE measures the multi-port RS from the first subset of antennas or antenna ports (e.g., 1351). The UE does not measure the multi-port RS from a second subset of antennas or antenna ports (e.g., 1352). The UE may perform spatial domain interpolation or prediction to estimate the channel from the second subset of antennas or antenna ports that have not been measured (e.g., 1352). Therefore, the UE may use spatial domain interpolation or spatial domain prediction (e.g., spatial domain prediction using machine learning) to predict the channels from all antennas or all antenna ports (e.g., 1351 and 1352).

[0103] The network entity may then configure the number of horizontal antenna ports and the number of vertical antenna ports for beamforming weight reporting via first control signaling. The network entity may further configure the position of each antenna port for the multi-port RS in the complete antenna port structure via first control signaling and / or second control signaling. For example, the UE may report UE capabilities indicating at least one of the following: the minimum number of measured antenna ports; the minimum number of measured horizontal antenna ports; the minimum number of measured vertical antenna ports; a preferred measured antenna port index in the horizontal direction; and a preferred measured antenna port index in the vertical direction.

[0104] Figures 14 to 17 Details of different options for beamforming weight reporting are shown. In some examples, the UE sends an explicit eigenvector report (e.g., Figures 14 to 16 In some other examples, the UE sends a codebook-based eigenvector report (e.g., Figure 17 ).

[0105] For explicit eigenvector reporting, the UE reports an eigenvector calculated based on a channel measured from at least one multi-port RS. The UE measures the eigenvector based on a wideband channel estimated from the multi-port RS.

[0106] In some implementations, the network entity configures the number of columns, L, for the feature vector report. In some other implementations, the number of columns, L, for the feature vector report is predefined, for example, L=1 or L=2. In some other implementations, the number of columns, L, for the feature vector report is determined based on the number of ports in the port group. The UE reports the first L columns of the feature vector, which are defined as the reported feature vector.

[0107] Figure 14 1400 is a block diagram illustrating an example of beamforming weight reporting with full eigenvector reporting. In some implementations, the UE reports the magnitude and phase of each coefficient in the reported eigenvector. In some implementations, the network entity may configure the number of bits and step size used for magnitude and / or phase quantization. In some other implementations, the number of bits and step size used for magnitude and / or phase quantization is predefined. In some implementations, the UE quantizes each coefficient based on the number of bits X1 used for magnitude quantization and the number of bits X2 used for phase quantization. In one example, the magnitude may be quantized to [0, ], and the phase can be quantized as [ , , ,…,1]. The UE may then report the magnitude and phase of each coefficient to the network. In some other implementations, the UE reports the real and imaginary parts of each coefficient in the reported eigenvector.

[0108] refer to Figure 14 , the UE reports all coefficients of the first two columns of the eigenvector measured from the 8-port RS. The reported coefficients 1412 in the beamforming weight report include the measured magnitudes 1451 and measured phases 1452 of all coefficients of the first two columns of the eigenvector measured from the 8-port RS. In one example, the UE can report each coefficient in the matrix using a 3-bit indicator for magnitude indication and a 2-bit indicator for angle indication.

[0109] Figure 15 is a block diagram 1500 illustrating an example of beamforming weight reporting with only non-zero power (NZP) coefficient reporting. In some examples, the UE reports only the NZP coefficients to the network entity. The UE reports an indicator indicating the location of the NZP coefficients within the eigenvector to the network entity. In one example, for a dimension of The reported feature vector, UE report dimension is A bitmap of , where bit x indicates whether the corresponding coefficient x in the reported eigenvector is reported.

[0110] refer to Figure 15 The UE reports the NZP coefficients for the first two columns of the eigenvector measured from the 8-port RS. The reported coefficients 1512 in the beamforming weight report may include the measured magnitude 1551 and measured phase 1552 of the NZP coefficients. The UE may further report a bitmap 1550 indicating whether the corresponding coefficients in the reported eigenvector are reported.

[0111] Figure 161600 is a block diagram illustrating an example of beamforming weight reporting with only the top N strongest coefficients reported. In some examples, the network entity configures a maximum number of reported coefficients for a reported eigenvector via first control signaling or second control signaling. In some examples, the network entity configures a maximum number of reported coefficients per column for a reported eigenvector via first control signaling or second control signaling. The UE then reports the strongest coefficient, i.e., the coefficient with the highest magnitude, to the network entity. The UE reports an indicator to the network entity indicating the location of the strongest coefficient within the eigenvector. In one example, for a dimension of The reported feature vector, UE report dimension is A bitmap of , where bit x indicates whether the corresponding coefficient x in the reported eigenvector is reported.

[0112] refer to Figure 16 , the UE reports the N strongest coefficients of the first 2 columns of the eigenvector measured from the 8-port RS. As an example, the UE reports only the first N coefficients. The number of strongest coefficients can be any value. Figure 16 As shown in , the UE reports the eight strongest coefficients of the first two columns of the eigenvector measured from the 8-port RS. The coefficients 1612 reported in the beamforming weight report may include the measured amplitudes 1651 and the measured phases 1652 of the N strongest coefficients. The UE may further report a bitmap 1650 that indicates whether the corresponding coefficients in the reported eigenvector are reported. The UE may then additionally report another indicator to indicate the positions of the N reported coefficients.

[0113] In some implementations, the UE may send the reported eigenvectors via PUCCH or PUSCH. For long PUCCH or PUSCH, the UE may send the reported eigenvectors in CSI part 1 or CSI part 2. Alternatively, the UE may send a portion of the reported eigenvectors (e.g., an indicator indicating the position of the NZP coefficient or the strongest coefficient) in CSI part 1 and the remainder of the reported eigenvectors (e.g., the amplitude and phase of each NZP or strong coefficient, or the real and imaginary parts of each NZP or strong coefficient) in CSI part 2. In some other implementations, the UE may send the reported eigenvectors via MAC CE.

[0114] Figure 171700 is a block diagram illustrating an example of beamforming weight grouping and codebook subset restriction based on codebook eigenvector reporting. In some examples, a UE may report at least one beamforming weight from a beamforming weight codebook based on a channel measured from at least one multi-port RS. The beamforming weight codebook may include sets of beamforming weights with different directions. The UE may identify one of the beamforming weights from the beamforming weight codebook for the channel measured from the at least one multi-port RS that may produce the strongest channel energy.

[0115] In some implementations, the network entity may configure the codebook subset restriction via the first control signaling and / or the second control signaling. For example, the network entity may configure a subset set of beamforming weights from the beamforming weight codebook. The UE may then search for beamforming weights from the configured subset of beamforming weights from the beamforming weight codebook.

[0116] In one example, the network entity may send a bitmap indicating whether each beam in the beamforming weight codebook is valid for reporting. In another example, the network entity may configure a group for each beamforming weight in the beamforming weight codebook, and the network entity may configure a corresponding group index in the first control signaling and / or the second control signaling to indicate a valid beamforming weight group for the UE to search for the beamforming weight.

[0117] refer to Figure 17 , the beamforming weight codebook may include a set of beamforming weights, e.g., beamforming weight set 1721 and beamforming weight set 1722. The network entity 104 may identify a coarse direction of the UE 102 based on the L1-RSRP report from the SSB to which the wide beam is applied. For example, the coarse direction of the UE is indicated by the beam 1762 used for the SSB with the strongest L1-RSRP. The network entity 104 may configure a subset set of beamforming weights from the beamforming weight codebook, the subset set corresponding to the beamforming weight set 1722. The UE may then search for a beamforming weight from the configured subset (e.g., beamforming weight set 1722) of the beamforming weights in the beamforming weight codebook. The network entity 104 may then require the UE 102 to search for corresponding beamforming weights (e.g., beamforming weight set 1722) around a coarse direction (e.g., beam 1762 for the SSB with the strongest L1-RSRP) to identify the best beamforming weights (e.g., beamforming weights 1732). The UE may identify one of the beamforming weights from a codebook for a channel measured from at least one multi-port RS that may produce the strongest channel energy.

[0118] In some examples, the beamforming weight codebook includes Q beamforming weights, and in the absence of antenna combination cross-polarization, the beamforming weights are the same for each polarization. In one example, the beamforming weight codebook is defined as follows, where for the dual column case, the first half of the rows are used for the first polarization, and the second half of the rows are used for the second polarization

[0119] For single column based reports,

[0120] For dual column based reports,

[0121] in, represents the Kronecker product. Different beams are generated based on different values ​​of m and / or n. In some implementations, the network entity configures the number of horizontal antenna ports (N1), the number of horizontal oversampling factors (O1), the number of horizontal antenna ports (N2), and the number of horizontal oversampling factors (O2) through first control signaling or second control signaling. In some other implementations, some parameters may be predefined, for example, O1 = O2 = 1.

[0122] In some examples, the beamforming weight codebook includes Q beamforming weights, and in the absence of antenna combination cross-polarization, the beamforming weights can be different for different polarizations. In one example, the beamforming weight codebook is defined as follows, where for the dual column case, the first half of the rows are used for the first polarization and the second half of the rows are used for the second polarization.

[0123] For single column based reports,

[0124] For dual column based reports,

[0125] in, represents a Kronecker product. Different beams are generated based on at least one different value of m, n, m', and n'. In some implementations, the network entity configures the number of horizontal antenna ports (N1), the number of horizontal oversampling factors (O1), the number of horizontal antenna ports (N2), and the number of horizontal oversampling factors (O2) through first control signaling or second control signaling. In some other implementations, some parameters may be predefined, for example, O1 = O2 = 1.

[0126] In some examples, the beamforming weight codebook includes Q beamforming weights, and in the case of cross-polarization combining, the beamforming weights are generated based on common beamforming weights in each polarization. In one example, the beamforming weight codebook is defined as follows, where the first half of the rows are used for the first polarization and the second half of the rows are used for the second polarization.

[0127] For single column based reports,

[0128] For dual column based reports,

[0129] in, represents the Kronecker product. Different beams are generated based on at least one different value of m, n, m', n', k, and k'. In some implementations, the network entity configures the number of horizontal antenna ports (N1), the number of horizontal oversampling factors (O1), the number of horizontal antenna ports (N2), the number of horizontal oversampling factors (O2), and the polarization combination oversampling factor (O3) through first control signaling or second control signaling. In some other implementations, some parameters may be predefined, for example, O1 = O2 = O3 = 1.

[0130] In some examples, the beamforming weight codebook includes Q beamforming weights, and in the case of cross-polarization combining, the beamforming weights are generated based on common beamforming weights in each polarization. In one example, the beamforming weight codebook is defined as follows, where the first half of the rows are used for the first polarization and the second half of the rows are used for the second polarization.

[0131] For single column based reports,

[0132] For dual column based reports,

[0133] in, represents the Kronecker product. Different beams are generated based on at least one different value of m, n, m', n', m'', n'', m''', n''', k, and k'. In some implementations, the network entity configures the number of horizontal antenna ports (N1), the number of horizontal oversampling factors (O1), the number of horizontal antenna ports (N2), the number of horizontal oversampling factors (O2), and the polarization combination oversampling factor (O3) through first control signaling or second control signaling. In some other implementations, some parameters may be predefined, for example, O1 = O2 = O3 = 1.

[0134] In some examples, the network entity configures whether the beamforming weight codebook is generated based on polarization-common beamforming weights or polarization-specific beamforming weights, and / or whether the beamforming weight codebook is generated with or without cross-polarization combining. The UE can then report the beamforming weight index from the beamforming weight codebook based on the examples discussed above.

[0135] In some examples, the UE reports UE capabilities or UE assistance information that indicates a supported or preferred beamforming weight codebook structure, i.e., whether the beamforming weight codebook is generated based on polarization-common beamforming weights or polarization-specific beamforming weights, and / or whether the beamforming weight codebook is generated with or without cross-polarization combining. The network entity may then further configure the UE to report a beamforming weight index from the corresponding beamforming weight codebook based on the examples discussed above.

[0136] In some implementations, the UE may send the beamforming weight index through PUCCH or PUSCH. For long PUCCH or PUSCH, the UE may send the beamforming weight index in CSI part 1 or CSI part 2. In some implementations, the UE may send the beamforming weight index through MAC CE. The UE reports at least one beamforming weight and a beam combining vector from the beamforming weight codebook based on the channel measured from at least one multi-port RS. Compared to the example discussed above, the difference is that in this option, the UE reports at least one beam index based on the dual column beams in the above beamforming weight codebook, and reports the beam combining vector of the reported beam.

[0137] The UE can calculate the beam combining vector W2 as follows:

[0138] Where W1 is the beam selected from the beamforming weight codebook, and V is the first L rows of the eigenvector of the channel measured from at least one multi-port RS, for example, L=1 or 2.

[0139] In some implementations, the network entity configures the selected number of beams, N3, through first control signaling or second control signaling. In some other implementations, the UE selects the selected number of beams, N3, and reports the selected number of beams. The dimension of W2 is then N3 × L. The UE can report W2 in a similar manner to the eigenvector reporting discussed above.

[0140] In some implementations, the UE sends the beamforming weight index and the beam combining vector via PUCCH or PUSCH. For long PUCCH or PUSCH, the UE may send the beamforming weight index and the beam combining vector in CSI part 1 or CSI part 2. Alternatively, the UE may send the beamforming weight index in CSI part 1 and the beam combining vector in CSI part 2. Alternatively, the UE may send the beamforming weight index and a portion of the beam combining vector in CSI part 1 and the rest of the beam combining vector in CSI part 2, for example, sending an indicator indicating the position of the NZP coefficients or the strongest coefficients of the beam combining vector in CSI part 1 and sending the rest of the beam combining vector, for example, the amplitude and phase of each NZP or strong coefficient, or the real and imaginary parts of each NZP or strong coefficient, in CSI part 2. In some other implementations, the UE may send the beamforming weight index and the beam combining vector via MAC CE.

[0141] In some examples, the network entity may configure whether the UE should report the complete reported eigenvector, or the beamforming weight index, or the beamforming weight index and the beam combining vector via the first control signaling or the second control signaling. The UE may then report the beamforming weights based on the corresponding examples.

[0142] In some examples, the UE may report UE capabilities or UE assistance information indicating whether the UE supports or prefers reporting the complete reported eigenvector, or the beamforming weight index, or the beamforming weight index and the beam combining vector via the first control signaling or the second control signaling. The network entity may then configure the beamforming weight reporting based on the corresponding examples discussed above.

[0143] In some examples, in addition to the reported eigenvectors, the network entity may also configure the UE to report L1-RSRP or L1-SINR measured based on the reported eigenvectors. In some implementations, the UE may report L1-RSRP or L1-SINR and eigenvectors jointly via PUCCH or PUSCH or MAC CE. In some other implementations, the UE may report L1-RSRP or L1-SINR and eigenvectors separately via separate PUCCH or PUSCH or MAC CE. In some examples, the network entity and the UE use multi-port RS-based beamforming weight measurement and reporting in channel-based beamforming, as described above in conjunction with Figures 3 to 13 In some examples, the network entity and the UE use multi-resource RS-based beamforming weight measurement and reporting in channel-based beamforming, which will be discussed below in conjunction with Figures 18 to 24 Have a discussion.

[0144] Figure 18 is a signaling diagram illustrating an example of communication between UE 102 and network entity 104 for beamforming weight measurement and reporting based on multi-resource RS. Figures 3 to 13 Compared to the previously discussed beamforming weight measurement and reporting based on multi-port RS, the difference is that in beamforming weight measurement and reporting based on multi-resource RS, UE 102 measures beamforming weights based on RS resource sets (e.g., CSI-RS resource sets) rather than multi-port RS. Network entity 104 can configure multi-resource RS using the same bandwidth and transmit different RS resources in different symbols using different antenna ports. The UE can construct a channel from all antenna ports based on the RS resource set. The UE can then measure and report eigenvectors based on the constructed channel.

[0145] refer to Figure 18, UE 102 may send 1803 UE capabilities, the UE capabilities indicating whether the UE supports beamforming weight measurement and reporting based on multi-resource RS. In one example, UE 102 sends UE capabilities regarding beamforming weight measurement and reporting based on multi-resource RS, the UE capabilities indicating at least one of the following: whether the UE supports beamforming weight measurement and reporting based on multi-resource RS; the maximum number of configured multi-resource RS sets per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, and / or per UE; the maximum number of RS resources in a time slot per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, and / or per UE; and the number of resources per resource set of multi-resource RS. The UE may report UE capabilities per feature set, per frequency band, per frequency band combination, or per UE. In addition, the network entity 104 may obtain the UE capabilities from another network entity 104 or a core network (e.g., an access and mobility management function (AMF)).

[0146] Based on the UE capabilities, the network entity 104 sends 1804 first control signaling, such as RRC signaling (RRCReconfiguration), which configures at least one beamforming weight report based on at least one RS resource set. The network entity 104 may send 1804 a control signal that configures the beamforming weight report to include at least one set of beamforming weights selected based on a predetermined rule. For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the network entity 104 may send 1806 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or at least one RS resource set for beamforming weight measurement and reporting. For example, to trigger the beamforming weight report, the second control signaling may indicate a report ID for the beamforming weight report, and the UE 102 may identify the time / frequency resources of the uplink signal for the beamforming weight report. For example, to trigger at least one RS resource set, the second control signaling may indicate at least one RS resource index set, and the UE may identify the location of the at least one RS resource set, such as the time / frequency resource of the at least one RS resource set. The network entity 104 then transmits 1808 the at least one RS set on the configured at least one RS resource set. In one example, the at least one RS set is a CSI-RS.

[0147] The UE 102 measures at least one RS set. The UE 102 quantizes 1810 beamforming weights based on the measured quality of the at least one RS set. The UE 102 quantizes the beamforming weights based on the received first control signaling and / or second control signaling.

[0148] The UE 102 sends 1812 a beamforming weight report to the network entity. The network entity identifies 1814 the beamforming weight based on the configuration in the first control signaling and / or the second control signaling. Figure 19 and Figure 20 The UE behavior and network entity behavior for beamforming weight measurement and reporting based on multi-resource RS are discussed in

[15] .

[0149] Figure 19 FIG1 is a block diagram 1900 illustrating an example of UE behavior for beamforming weight measurement and reporting based on multi-resource RS. Figure 19 , UE 102 may send 1903 UE capabilities regarding multi-resource RS based beamforming weight measurement and reporting.

[0150] UE 102 may receive 1904 first control signaling, such as RRC signaling (RRCReconfiguration), that configures at least one beamforming weight report based on at least one RS resource set. UE 102 may receive 1904 a control signal that configures the beamforming weight report to include at least one set of beamforming weights selected based on a predetermined rule.

[0151] For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the UE may receive 1906 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or at least one RS resource set for beamforming weight measurement and reporting. In one example, the at least one RS resource set is a CSI-RS resource. The UE then receives 1908 at least one RS resource set for beamforming weight measurement and reporting.

[0152] The UE 102 measures and quantizes 1910 beamforming weights based on at least one RS resource set and the received first control signaling and / or second control signaling. The UE 102 sends 1912 a beamforming weight report to a network entity.

[0153] Figure 20 FIG2 is a block diagram 2000 illustrating an example of network entity behavior for beamforming weight measurement and reporting based on multi-resource RS. Figure 20, the network entity 104 may receive 2003 UE capabilities regarding multi-resource RS based beamforming weight measurement and reporting.

[0154] The network entity 104 sends 2004 first control signaling, such as RRC signaling (RRCReconfiguration), which configures at least a beamforming weight report based on at least one RS resource set. The network entity 104 may configure 2004 the beamforming weight report to include at least one set of beamforming weights selected based on a predetermined rule.

[0155] For a specific type of beamforming weight report (e.g., semi-persistent or aperiodic beamforming weight report) and / or a specific type of multi-port RS (e.g., semi-persistent or aperiodic multi-port RS), the network entity 104 may send 2006 second control signaling (e.g., MAC CE or DCI) that triggers the configured beamforming weight report and / or at least one RS resource set for beamforming weight measurement and reporting. In one example, the at least one RS resource set is a CSI-RS resource. The network entity 104 sends 2008 at least one RS set on the at least one RS resource set for beamforming weight measurement and reporting. The network entity 104 then receives 2012 a beamforming weight report from the UE.

[0156] Figure 21 is a block diagram illustrating an example of multi-resource RS utilizing full antenna or antenna port switching. The network entity 104 may transmit multi-resource RS with different structures and associated control signaling. The network entity may utilize antenna or antenna port switching to transmit the multi-resource RS. In some examples, the network entity 104 utilizes full antenna port switching across resources to transmit the multi-resource RS. The network entity utilizes different antennas or antenna ports in different resources. The network entity may configure whether the RS resource set should be transmitted utilizing antenna switching via first control signaling or second control signaling. The network entity may multiplex signals of different ports within a resource in an FDM manner (e.g., utilizing different subcarriers for different ports) or a CDM manner (e.g., utilizing different OCC codes for different ports).

[0157] refer to Figure 21 , the network entity 104 transmits an RS on resource 2101 from antennas or antenna ports 1 and 2, transmits an RS on resource 2102 from antennas or antenna ports 3 and 4, transmits an RS on resource 2103 from antennas or antenna ports 5 and 6 in resource 2101, and transmits an RS on resource 2104 from antennas or antenna ports 7 and 8. The network entity may multiplex RSs from different ports within the same resource in an FDM manner or a CDM manner.

[0158] In some examples, the network entity configures RS resources for antenna switching using at least one of the following common configurations: frequency domain density, bandwidth, transmit power, number of ports, resource elements, etc. The network entity may configure a common value for the corresponding parameter of each resource. Alternatively, the network entity may configure a common parameter set for a resource set.

[0159] In some implementations, the network entity configures RS resources in contiguous symbols. In some other implementations, the network entity may configure RS resources in discontinuous symbols. The UE may further report UE capabilities that indicate the maximum offset between each symbol or the maximum time domain duration of a resource set with antenna switching.

[0160] Figure 22 This is a block diagram illustrating an example of multi-resource RS using partial antenna or antenna port switching. A network entity may transmit multi-resource RS using partial antenna or antenna port switching. The network entity may multiplex RSs from different ports within a resource using FDM (e.g., using different subcarriers for different ports) or CDM (e.g., using different OCC codes for different ports).

[0161] and Figure 21 Compared to the example shown in , the difference is that, in this example, the network entity applies at least one antenna or antenna port across resources. For other antenna ports, the network entity applies different antennas or antenna ports in different resources. The UE can then perform phase tracking and compensation based on at least one antenna port across resources. The UE can track the phases of multiple RSs on multiple RS resources by receiving multiple RSs on multiple RS resources from at least one antenna port among the multiple antenna ports. The network entity can configure whether the RS resource set should be sent using partial antenna switching through the first control signaling or the second control signaling. The network entity can further configure the number of ports without switching antennas or antenna ports across resources.

[0162] refer to Figure 22, the network entity transmits all RSs across a set of RS resources (e.g., resources 2201, 2202, 2203, 2204, 2205, 2206, 2207) through at least one antenna or antenna port (e.g., antenna or antenna port 1). The network entity applies at least one antenna or antenna port (e.g., antenna or antenna port 1) across the resources (e.g., resources 2201, 2202, 2203, 2204, 2205, 2206, 2207). For other antenna ports (e.g., antennas or antenna ports 2, 3, 4, 5, 6, 7, 8), the network entity applies different antennas or antenna ports in different resources. The UE can then perform phase tracking and compensation based on at least one antenna port (e.g., antenna or antenna port 1) across the resources (e.g., resources 2201, 2202, 2203, 2204, 2205, 2206, 2207).

[0163] Figure 23 is a block diagram illustrating an example of multi-resource RS transmission in which antenna switching is first performed. Figure 24 is a block diagram illustrating an example of first performing repeated multi-resource RS transmission. In some examples, a network entity configures, via first control signaling or second control signaling, whether to transmit the multi-resource RS using full antenna port switching or partial antenna port switching. The network entity then transmits the multi-resource RS accordingly.

[0164] The network entity may configure the network entity to transmit multiple resource RSs using antenna switching and repetition. In some implementations, the network entity may configure the number of repetitions. The network entity can then divide the resources into In each group, the network entity may utilize antenna switching to transmit multi-resource RS. In some other implementations, the network entity configures the total number of antennas or antenna ports used for antenna switching. , the network entity can then use antenna switching to send Resources, including Indicates the number of ports per resource. The network entity may further configure whether the network entity should first perform antenna switching or first perform repetition to send the multi-resource RS. In one example, the network entity first performs antenna switching to send the multi-resource RS. In another example, the network entity first performs repetition to send the multi-resource RS.

[0165] refer to Figure 23The network entity first performs antenna switching to transmit multi-resource RSs (resources 2301, 2302, 2303, and 2304). The network entity 104 transmits RSs on resource 2301 from antennas or antenna ports 1 and 2, transmits RSs on resource 2302 from antennas or antenna ports 3 and 4, transmits RSs on resource 2303 from antennas or antenna ports 5 and 6 within resource 2101, and transmits RSs on resource 2304 from antennas or antenna ports 7 and 8. The network entity may multiplex RSs from different ports within the same resource using either FDM or CDM.

[0166] refer to Figure 24 , the network entity first repeats to send multiple resource RSs (resources 2301, 2302, 2303, 2304). For example, the network entity 104 repeatedly sends RSs on resource 2301 from antennas or antenna ports 1 and 2 before sending RSs on resource 2302 from antennas or antenna ports 3 and 4.

[0167] In some examples, the UE reports UE capabilities or assistance information that indicates supported or preferred antenna switching schemes across resources, such as full antenna switching or partial antenna switching. Based on the UE report, the network entity can then configure the network entity to send multi-resource RS based on full antenna port switching or partial antenna port switching.

[0168] In some examples, the network entity configures an antenna or antenna port index for each resource, and the UE can reconstruct the channel based on the antenna or antenna port index configured for each resource. Alternatively, the antenna or antenna port index for each resource is predefined. In one example, the network entity can configure an antenna or antenna port index for each resource. ports, then the ports in resource k in the resource set should come from antennas or antenna ports Using the configured or predefined antenna or antenna port index, the UE can measure and report the beamforming weights, as shown above in combination with Figures 14 to 16 discussed.

[0169] In some implementations, the UE reports an indicator indicating beamforming weight reporting based on the number of ports across the multi-resource RS set. In some implementations, the beamforming weight is of dimension × 1 or 2 matrix, where Indicates the number of ports across the multi-resource RS set. In some other implementations, the beamforming weights are of dimension × The matrix of is the maximum or minimum number of ports per resource. In some other implementations, the beamforming weights are of dimension × The matrix of The network entity configures the first control signaling.

[0170] In some other implementations, the beamforming weights may have more ports, i.e., more rows, than the number of ports across the multi-resource RS set. The network entity sends the multi-resource RS only from a subset of antennas or antenna ports. The UE may predict the channels from all antennas or all antenna ports using spatial domain interpolation or spatial domain prediction (e.g., spatial domain prediction using machine learning). The network entity may then configure the number of horizontal antenna ports and the number of vertical antenna ports for beamforming weight reporting through a first control signaling. The network entity may further configure the position of each antenna port for each resource in the complete antenna port structure through a first control signaling and / or a second control signaling. The UE may report UE capabilities indicating at least one of the following: the minimum number of measured antenna ports across resources; the minimum number of measured horizontal antenna ports across resources; the minimum number of measured vertical antenna ports across resources; the preferred measured antenna port index in the horizontal direction; the preferred measured antenna port index in the vertical direction.

[0171] Figures 2 to 24 An example of beamforming weight measurement and reporting is shown. Figures 25 to 26 Shown for implementation Figures 2 to 24 In particular, Figure 25 UE 102 is shown Figures 2 to 24 Implementation of one or more aspects. Figure 26 The network entity 104 is shown Figures 2 to 24 Implementation of one or more aspects.

[0172] Figure 25 2500 is a flow chart of a method for wireless communication at a UE for beamforming weight measurement and reporting. Figure 1 and Figure 24 , the method can be performed by UE 102, UE equipment 2702, etc., which may include memory 2726', 2706', 2716, and may correspond to the entire UE 102 or the entire UE equipment 2702, or components of the UE 102 or UE equipment 2702 (such as wireless baseband processor 2726 and / or application processor 2706).

[0173] UE 102 may send 2503 a UE capability report to the NE. For example, Figure 3, UE 102 may send 303 a UE capability report indicating UE capabilities, the UE capabilities indicating whether the UE supports beamforming weight measurement and reporting based on multi-port RS. Figure 18 , UE 102 may send 1803 indicating whether the UE supports UE capability of beamforming weight measurement and reporting based on multiple resource RSs.

[0174] The UE 102 may receive 2504 a control signal from the NE that configures the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule. Figure 4 , the UE 102 may receive 404 a control signal that configures the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule. Figure 19 , the UE 102 may receive 1904 a control signal that configures the beamforming weight report to select at least one set of beamforming weights based on a predetermined rule.

[0175] The UE 102 may receive 2506 a trigger signal from the NE that triggers at least one of a beamforming weight report or one or more downlink RSs. Figure 4 , the UE may receive 406 second control signaling, such as MAC CE or DCI, which triggers the configured beamforming weight reporting and / or the configured multi-port RS for beamforming weight measurement and reporting. Figure 19 , the UE may receive 1906 second control signaling, such as a MAC CE or a DCI, which triggers the configured beamforming weight reporting and / or at least one RS resource set for beamforming weight measurement and reporting.

[0176] UE 102 receives 2508 one or more downlink reference signals. For example, reference Figure 4 , the UE receives 408 at least one multi-port RS for beamforming weight measurement and reporting. Figure 19 , the UE receives 1908 at least one RS resource set for beamforming weight measurement and reporting.

[0177] The UE 102 quantizes 2510 the beamforming weights based on the measured quality of one or more downlink reference signals RS transmitted by the NE using multiple antenna ports. Figure 3 , the UE 102 quantizes 310 the beamforming weights based on the measured quality of at least one multi-port RS. Figure 18 , the UE 102 quantizes 1810 beamforming weights based on the measured quality of at least one RS set.

[0178] UE 102 sends 2512 a beamforming weight report to NE, the beamforming weight report including at least one set of beamforming weights for a plurality of antenna ports. Figure 3 , UE 102 sends 312 a beamforming weight report to the network entity. Figure 18 , UE 102 sends 1812 a beamforming weight report to the network entity.

[0179] Figure 26 2600 is a flow chart of a method for wireless communication at a network entity for beamforming weight measurement and reporting. Figures 1 to 24 The method may be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, RU processor 2806, DU processor 2826, CU processor 2846, etc.). One or more network entities 104 may include a memory 2806' / 2826' / 2846', which may correspond to the entirety of one or more network entities 104 or a component of one or more network entities 104 (such as RU processor 2806, DU processor 2826, or CU processor 2846).

[0180] The network entity 104 may receive 2603 a UE capability report from the UE. Figure 5 , the network entity 104 may receive 503 the UE capability regarding beamforming weight measurement and reporting based on multi-port RS. Figure 20 , the network entity 104 may receive 2003 UE capabilities regarding multi-resource RS based beamforming weight measurement and reporting.

[0181] The network entity 104 may configure 2604 the beamforming weight report to include at least one set of beamforming weights based on a predetermined rule. Figure 5 , the network entity 104 may configure 504 the beamforming weight report to include at least one set of beamforming weights selected based on a predetermined rule. Figure 20 , the network entity 104 may configure 2004 the beamforming weight report to include at least one set of beamforming weights selected based on a predetermined rule.

[0182] The network entity 104 may send 2606 a trigger signal to the UE, the trigger signal triggering at least one of the beamforming weight report or one or more downlink RSs. Figure 5, the network entity 104 may send 506 a second control signaling, such as a MAC CE or a DCI, which triggers the configured beamforming weight reporting and / or the configured multi-port RS for beamforming weight measurement and reporting. Figure 20 , the network entity 104 may send 2006 second control signaling, such as a MAC CE or a DCI, which triggers the configured beamforming weight reporting and / or at least one RS resource set for beamforming weight measurement and reporting.

[0183] The network entity 104 sends 2608 one or more downlink reference signals. Figure 5 , the network entity 104 sends 508 at least one multi-port RS for beamforming weight measurement and reporting. Figure 20 , the network entity 104 sends 2008 at least one RS set on at least one RS resource set for beamforming weight measurement and reporting.

[0184] The network entity receives 2612 a beamforming weight report from the UE, the beamforming weight report including at least one set of beamforming weights for a plurality of antenna ports. Figure 5 , the network entity 104 receives 512 a beamforming weight report from the UE. For example, referring to Figure 20 , the network entity 104 receives 2012 a beamforming weight report from the UE. Figure 27 As described in , UE equipment 2702 can perform the method of flowchart 2500. Figure 28 As described in , one or more network entities 104 may perform the method of flowchart 2600 .

[0185] Figure 27 Figure 2700 illustrates an example of a hardware implementation of a UE device 2702. The UE device 2702 may be a UE 102, a component of the UE 102, or may implement UE functionality. The UE device 2702 may include an application processor 2706, which may have on-chip memory 2706′. In an example, the application processor 2706 may be coupled to a secure digital (SD) card 2708 and / or a display 2710. The application processor 2706 may also be coupled to a sensor module 2712, a power supply 2714, an additional memory module 2716, a camera 2718, and / or other related components. For example, the sensor module 2712 may control a barometric pressure sensor / altimeter, a motion sensor such as an inertial management unit (IMU), a gyroscope, an accelerometer, a light detection and ranging (LIDAR) device, a radio-aided detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.

[0186] The UE equipment 2702 may further include a wireless baseband processor 2726, which may be referred to as a modem. The wireless baseband processor 2726 may have on-chip memory 2726'. Together with and similar to the application processor 2706, the wireless baseband processor 2726 may also be coupled to a sensor module 2712, a power supply 2714, an additional memory module 2716, a camera 2718, and / or other related components. The wireless baseband processor 2726 may also be coupled to one or more subscriber identity modules (SIM) cards 2720 and / or one or more transceivers 2730 (e.g., wireless RF transceivers).

[0187] Within one or more transceivers 2730, the UE equipment 2702 may include a Bluetooth module 2732, a WLAN module 2734, an SPS module 2736 (e.g., a GNSS module), and / or a cellular module 2738. The Bluetooth module 2732, the WLAN module 2734, the SPS module 2736, and the cellular module 2738 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 2732, the WLAN module 2734, the SPS module 2736, and the cellular module 2738 may each include a dedicated antenna and / or utilize an antenna 2740 to communicate with one or more other nodes. For example, the UE equipment 2702 can communicate with another UE 102 (e.g., sidelink communication) and / or communicate with a network entity 104 (e.g., uplink / downlink communication) via the antenna 2740 through the transceiver 2730, where the network entity 104 can correspond to a base station or a unit of a base station (such as RU 106, DU 108 or CU 110).

[0188] The wireless baseband processor 2726 and the application processor 2706 may each include a computer-readable medium / memory 2726′, 2706′, respectively. The additional memory module 2716 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 2726′, 2706′, 2716 may be non-transitory. The wireless baseband processor 2726 and the application processor 2706 may each be responsible for general processing, including executing software stored on the computer-readable medium / memory 2726′, 2706′, 2716. This software, when executed by the wireless baseband processor 2726 / application processor 2706, causes the wireless baseband processor 2726 / application processor 2706 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the wireless baseband processor 2726 / application processor 2706 when executing the software. The wireless baseband processor 2726 / application processor 2706 may be a component of the UE 102. UE equipment 2702 may be a processor chip (e.g., modem and / or applications) and include only a radio baseband processor 2726 and / or an application processor 2706. In other examples, UE equipment 2702 may be the entire UE 102 and include additional modules of equipment 2702.

[0189] As discussed, the beamforming weight component 140 is configured to quantize beamforming weights based on the measured quality of one or more downlink reference signals (RSs) transmitted by a network entity (NE) using multiple antenna ports. The beamforming weight component 140 is further configured to send a beamforming weight report to the NE, the beamforming weight report including at least one set of beamforming weights for the multiple antenna ports. The beamforming weight component 140 can be within the application processor 2706 (e.g., at 140a), within the radio baseband processor 2726 (e.g., at 140b), or within both the application processor 2706 and the radio baseband processor 2726. The beamforming weight components 140a-140b can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0190] Figure 28FIG2800 is a diagram illustrating an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include or correspond to at least one of the RU 106, DU 108, or CU 110. The CU 110 may include a CU processor 2846, which may have on-chip memory 2846'. In some aspects, the CU 110 may further include an additional memory module 2856 and / or a communication interface 2848, both of which may be coupled to the CU processor 2846. The CU 110 may communicate with the DU 108 via a midhaul link 162, such as an F1 interface between the communication interface 2848 of the CU 110 and the communication interface 2828 of the DU 108.

[0191] The DU 108 may include a DU processor 2826, which may have on-chip memory 2826'. In some aspects, the DU 108 may further include an additional memory module 2836 and / or a communication interface 2828, both of which may be coupled to the DU processor 2826. The DU 108 may communicate with the RU 106 via a fronthaul link 160 between the communication interface 2828 of the DU 108 and the communication interface 2808 of the RU 106.

[0192] The RU 106 may include a RU processor 2806, which may have on-chip memory 2806'. In some aspects, the RU 106 may further include an additional memory module 2816, a communication interface 2808, and one or more transceivers 2830, all of which may be coupled to the RU processor 2806. The RU 106 may further include an antenna 2840, which may be coupled to the one or more transceivers 2830, such that the RU 106 may communicate with the UE 102 via the antenna 2840 through the one or more transceivers 2830.

[0193] On-chip memory 2806', 2826', 2846' and additional memory modules 2816, 2836, 2856 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2806, 2826, 2846 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 2806, 2826, 2846, the software causes the processor 2806, 2826, 2846 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processor 2806, 2826, 2846 when executing the software. In an example, the reporting configuration component 150 can be located at any of the one or more network entities 104, such as at the CU 110; at both the CU 110 and the DU 108; at each of the CU 110, DU 108, and RU 106; at the DU 108; at both the DU 108 and the RU 106; or at the RU 106.

[0194] As discussed, the report configuration component 150 is configured to configure beamforming weight reports associated with one or more reference signals (RSs). The report configuration component 150 is further configured to receive a beamforming weight report from a user equipment, the beamforming weight report including beamforming weights based on the measured quality of the one or more RSs. The report configuration component 150 can be located within one or more processors of one or more network entities 104, such as within the RU processor 2806 (e.g., at 150a), within the DU processor 2826 (e.g., at 150b), and / or within the CU processor 2846 (e.g., at 150c). The report configuration components 150a-150c can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors 2806, 2826, 2846 configured to perform the stated processes / algorithms, stored on a computer-readable medium for implementation by one or more processors 2806, 2826, 2846, or a combination thereof.

[0195] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is illustrative of example methods. Therefore, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of a diagram. The accompanying method claims present elements of each block in an example order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0196] The detailed description set forth herein, in conjunction with the accompanying drawings, describes various configurations, but does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a comprehensive explanation of the various concepts. However, these concepts may be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0197] Various aspects of wireless communication systems (such as telecommunication systems) are presented with reference to various apparatus and methods. These apparatus and methods are described in the detailed description that follows and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0198] Element, or any part of an element or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other similar hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software, which can be referred to as software, firmware, middleware, microcode, hardware description language, or other. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, processes, functions, or any combination thereof.

[0199] If the functions described herein are implemented in software, these functions may be stored on a computer-readable medium (such as a non-transitory computer-readable storage medium) or encoded as one or more instructions or codes on the computer-readable medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. The storage medium can be any available medium that is accessible to the computer.

[0200] The various aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the various aspects, implementations, and / or use cases can be generated via integrated chip implementations and other non-module component-based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, artificial intelligence (AI)-enabled devices, machine learning (ML)-enabled devices, and the like. The various aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the techniques described herein.

[0201] Devices incorporating aspects and features described herein may also include additional components and features for implementing and practicing the aspects and features claimed and described. For example, the transmission and reception of wireless signals necessarily include many components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., in various configurations.

[0202] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in view of the full scope of the disclosure consistent with the language of the claims.

[0203] Unless expressly stated, reference to a singular element does not mean "one and only one", but rather "one or more". Terms such as "if", "when" and "at" do not imply an immediate temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a certain condition is met, a certain action will occur, but no specific or immediate time constraint is required for the occurrence of the action. The terms "may", "might" and "can" as used in this disclosure generally carry certain meanings. For example, "may" refers to a permissible feature that may or may not occur, "might" refers to a feature that may occur, and "can" refers to an ability (e.g., be able to). The phrase "for example" generally carries a similar meaning to "may", and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0204] Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A, B, and C, and may include multiple A's, multiple B's, and / or multiple C's, or may include only A's, only B's, or only C's. A set should be interpreted as a set of elements where the number of elements is one or more.

[0205] Unless otherwise expressly indicated, ordinal terms such as "first" and "second" do not necessarily imply an order in time, sequence, value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. Figure numerals as used in the specification and drawings are sometimes cross-referenced between the drawings to indicate identical or similar features. Features that are identical in multiple drawings may be labeled with the same figure numerals in the multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with figure numerals having different leading digits but one or more of the same trailing digits (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Sometimes, "X" is used to generally indicate multiple variations of a feature. For example, "X06" may generally refer to all figure numerals ending with "06" (e.g., 206, 306, 406, etc.).

[0206] Structural equivalents and functional equivalents of the elements of various aspects described in the entire present disclosure that are known or later learned by those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. The words "module", "mechanism", "element", "device" and the like may not be substitutes for the word "component". Therefore, unless the phrase "component for ..." is used to expressly describe the claim elements, any claim element shall not be interpreted as a means plus function. As used herein, the phrase "based on" should not be interpreted as a reference to a closed information set, one or more conditions, one or more factors, etc. In other words, unless explicitly described differently, the phrase "based on A" (wherein "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A".

[0207] The following examples are illustrative only and may be combined with other examples or teachings described herein without limitation.

[0208] Example 1 is a method for wireless communication at a UE, comprising: quantizing beamforming weights based on the measured quality of one or more downlink reference signals RS transmitted by a network entity NE using multiple antenna ports; and sending a beamforming weight report to the NE, the beamforming weight report including at least one set of the beamforming weights for the multiple antenna ports.

[0209] Example 2 can be combined with Example 1 and include receiving a control signal from the NE, the control signal configuring the beamforming weight report to select the at least one set of beamforming weights based on a predetermined rule.

[0210] Example 3 can be combined with Example 2 and include: the predetermined rule being that the at least one set of beamforming weights includes eigenvectors of a matrix calculated based on the measured quality of one or more downlink RSs.

[0211] Example 4 can be combined with Example 3, and further include: the beamforming weight report includes all coefficients of the eigenvector.

[0212] Example 5 can be combined with Example 3, and further include: the beamforming weight report includes non-zero power (NZP) coefficients of the eigenvector.

[0213] Example 6 can be combined with Example 3 and include: the beamforming weight report includes the strongest coefficient of the eigenvector.

[0214] Example 7 can be combined with Example 2 and include: the predetermined rule is that the UE selects the at least one set of beamforming weights from a beamforming weight codebook, and the beamforming weight codebook includes multiple sets of beamforming weights with multiple directions.

[0215] Example 8 can be combined with Example 7, and include receiving a control signal configuring the beamforming weight codebook from the NE.

[0216] Example 9 can be combined with any one of Examples 1 to 8, and further includes: receiving a trigger signal from the network entity, the trigger signal triggering at least one of the beamforming weight report or the one or more downlink RSs.

[0217] Example 10 can be combined with any one of Examples 1 to 9 and includes: sending a UE capability report to the network entity, wherein the UE capability report indicates that the UE is capable of performing at least one of the following: measuring the quality of the multi-port RS to quantify the beamforming weights; or measuring multiple RSs transmitted on multiple RS resources using the multiple antenna ports.

[0218] Example 11 can be combined with Example 10 and include: the UE capability report indicates that the UE is capable of measuring the multi-port RS, and the UE capability report further indicates at least one of the following: the maximum number of multi-port RS resources per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination or across all frequency bands; the maximum number of multi-port RS resources in a time slot per BWP, per CC, per frequency band, per frequency band combination or across all frequency bands; or the number of antenna ports used for the multi-port RS.

[0219] Example 12 can be combined with any one of Examples 1 to 11, and further includes: the one or more downlink RSs include a multi-port RS, wherein the multiple antenna ports include multiple antenna port groups, and the multi-port RSs from the multiple antenna port groups are received in multiple symbols on the RS resource, and each part of the multi-port RS from each antenna port group among the multiple antenna port groups is in one symbol among the multiple symbols.

[0220] Example 13 can be combined with Example 12, and include: different parts of the multi-port RS from different antenna ports within the antenna port group of each symbol are in different subcarriers in each symbol.

[0221] Example 14 can be combined with Example 12, and include generating different portions of the multi-port RS from different antenna ports within the antenna port group of each symbol using different orthogonal cover codes in each symbol.

[0222] Example 15 can be combined with any of Examples 12 to 14 and include: receiving the multi-port RS includes: using a portion of the multi-port RS from an antenna port present in at least one subcarrier across the multiple symbols to track the phase of one or more portions of the multi-port RS from one or more antenna ports.

[0223] Example 16 can be combined with Example 10 and include: the UE capability report indicates that the UE is capable of measuring the multiple RSs, and the UE capability report further indicates at least one of the following: the maximum number of configured multi-resource RS sets per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination or per UE; the maximum number of RS resources in a time slot per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination or per UE; or the number of resources per resource set of the RS resource set.

[0224] Example 17 can be combined with any one of Examples 1 to 10 and 16, and include: receiving the plurality of RSs on the plurality of RS resources from the plurality of antenna ports for the beamforming weight reporting.

[0225] Example 18 can be combined with Example 17 and include: different RSs among the multiple RSs on different resources among the multiple RS resources are transmitted by different antenna ports among the multiple antenna ports.

[0226] Example 19 can be combined with Example 17 and include: receiving the multiple RSs on the multiple RS resources includes: tracking the phases of the multiple RSs on the multiple RS resources by receiving the multiple RSs on the multiple RS resources from at least one of the multiple antenna ports.

[0227] Example 20 is a method for wireless communication at a network entity, comprising: configuring a beamforming weight report associated with one or more reference signals RS transmitted by the network entity NE using multiple antenna ports; receiving the beamforming weight report from a user equipment UE, wherein the beamforming weight report includes at least one set of the beamforming weights for the multiple antenna ports.

[0228] Example 21 can be combined with Example 20 and include sending a control signal to the UE to configure a beamforming weight codebook, the beamforming weight report indicating a plurality of beamforming weight indices.

[0229] Example 22 is an apparatus for wireless communication, the apparatus being configured to implement a method as described in any one of Examples 1 to 21.

[0230] Example 23 is a non-transitory computer-readable medium storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement the method of any one of Examples 1 to 21.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: quantizing (310, 410) beamforming weights based on measured qualities of one or more downlink reference signals RS transmitted by a network entity NE using a plurality of antenna ports; as well as A beamforming weight report is sent (312, 412) to the NE, the beamforming weight report including at least one set of the beamforming weights for the plurality of antenna ports.

2. The method of claim 1, further comprising: A control signal is received (404) from the NE, the control signal configuring the beamforming weight report to select the at least one set of beamforming weights based on a predetermined rule.

3. The method according to claim 2, wherein: The predetermined rule is that the at least one set of beamforming weights comprises eigenvectors of a matrix calculated based on the measured quality of one or more downlink RSs.

4. The method according to claim 3, wherein: The beamforming weight report includes all coefficients of the eigenvector.

5. The method according to claim 3, wherein: The beamforming weight report includes non-zero power (NZP) coefficients of the eigenvector.

6. The method of claim 3, wherein: The beamforming weight report includes the strongest coefficient of the eigenvector.

7. The method of claim 2, wherein: The predetermined rule is that the UE selects the at least one set of beamforming weights from a beamforming weight codebook, wherein the beamforming weight codebook includes a plurality of sets of beamforming weights having a plurality of directions.

8. The method of claim 7, further comprising: A control signal for configuring the beamforming weight codebook is received from the NE.

9. The method of any one of claims 1 to 8, further comprising: A trigger signal is received (406) from the network entity, the trigger signal triggering at least one of the beamforming weight reporting or the one or more downlink RSs.

10. The method according to any one of claims 1 to 9, further comprising: Sending a UE capability report to the network entity, where the UE capability report indicates that the UE is capable of performing at least one of the following: Measuring the quality of the multi-port RS to quantify the beamforming weights, or A plurality of RSs transmitted on a plurality of RS resources using the plurality of antenna ports are measured.

11. The method according to claim 10, wherein: The UE capability report indicates that the UE is capable of measuring the multi-port RS, and the UE capability report further indicates at least one of the following: The maximum number of multi-port RS resources per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, or across all frequency bands; Maximum number of multi-port RS resources per BWP, per CC, per band, per band combination, or in a timeslot across all bands, or The number of antenna ports used for the multi-port RS.

12. The method according to any one of claims 1 to 11, wherein The one or more downlink RSs include a multi-port RS, wherein the multiple antenna ports include multiple antenna port groups, and the method further includes: The multi-port RSs from the multiple antenna port groups are received in multiple symbols on an RS resource, each portion of the multi-port RS from each antenna port group among the multiple antenna port groups being in one symbol among the multiple symbols.

13. The method of claim 12, wherein: Different parts of the multi-port RS from different antenna ports within the antenna port group of each symbol are in different subcarriers of each symbol.

14. The method of claim 12, wherein: Different portions of the multi-port RS from different antenna ports within the antenna port group of each symbol are generated using different orthogonal cover codes in each symbol.

15. The method according to any one of claims 12 to 14, wherein Receiving the multi-port RS includes: A phase of one or more portions of the multi-port RS from one or more antenna ports is tracked using a portion of the multi-port RS from an antenna port present in at least one subcarrier across the plurality of symbols.

16. The method of claim 10, wherein: The UE capability report indicates that the UE is capable of measuring the plurality of RSs, and the UE capability report further indicates at least one of the following: The maximum number of configured multi-resource RS sets per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination or per UE, The maximum number of RS resources in a time slot per bandwidth part (BWP), per component carrier (CC), per frequency band, per frequency band combination, or per UE, or The number of resources in each resource set of the RS resource set.

17. The method according to any one of claims 1 to 10 and 16, wherein The one or more downlink RSs include multiple RSs on multiple RS resources, and the method further includes: The plurality of RSs on the plurality of RS resources are received from the plurality of antenna ports for the beamforming weight reporting.

18. The method of claim 17, wherein: Different RSs among the multiple RSs on different resources among the multiple RS resources are transmitted by different antenna ports among the multiple antenna ports.

19. The method of claim 17, wherein: Receiving the multiple RSs on the multiple RS resources includes: Phases of the plurality of RSs on the plurality of RS resources are tracked by receiving the plurality of RSs on the plurality of RS resources from at least one antenna port among the plurality of antenna ports.

20. A method for wireless communication at a network entity, comprising: configuring beamforming weight reports associated with one or more reference signals RS transmitted by the network entity NE using a plurality of antenna ports; The beamforming weight report is received from a user equipment (UE), the beamforming weight report comprising at least one set of the beamforming weights for the plurality of antenna ports.

21. The method of claim 20, further comprising: A control signal for configuring a beamforming weight codebook is sent to the UE, where the beamforming weight report indicates a plurality of beamforming weight indexes.

22. An apparatus for wireless communication, the apparatus comprising a transceiver, a memory, and a processor coupled to the memory and the transceiver, the apparatus being configured to perform the method according to any one of claims 1 to 21.

Images