Rank-specific codebook for wireless communication

Abstract

The present disclosure provides systems, apparatuses, apparatuses, and methods, including computer programs encoded on a storage medium, for beam measurement and reporting processes. A user equipment (UE) (102) receives (304), from a network entity (104), a rank-specific CSI reporting configuration indicating rank-specific parameters for channel state information (CSI) reporting. The UE (102) sends (310), to a network entity (104), a CSI report comprising CSI measurement information for a channel state information reference signal (CSI-RS), the CSI measurement information being associated with a rank-specific parameter.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more specifically, to configurations such as rank-specific channel state information (CSI) reporting for rank-specific codebooks. Background Technology

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

[0003] Generally, wireless communication systems provide various telecommunications services (e.g., telephony, video, data, messaging, broadcasting, etc.) based on multiple access technologies (such as Orthogonal Frequency Division Multiple Access (OFDMA)) that support communication with multiple UEs. Improvements in mobile broadband have continued the development of such wireless communication technologies. The transmission of Channel State Information (CSI) reports can correspond to a single codebook configuration. For example, a UE can provide a CSI report to a network entity based on a single configuration of its antenna ports. Summary of the Invention

[0004] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes 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 descriptions that follow.

[0005] Network entities (such as base stations or base station elements) can configure CSI feedback using Channel State Information (CSI) report configuration. CSI report configuration configures Channel Measurement Resources (CMR), Interference Measurement Resources (IMR), codebook configuration, and / or uplink resources for CSI feedback. User Equipment (UE) measures the Channel State Information Reference Signal (CSI-RS) and sends CSI feedback in a CSI report based on the CSI report configuration. The CSI report may include a CSI Resource Indicator (CRI), Rank Indicator (RI), Precoder Matrix Indicator (PMI), Channel Quality Indicator (CQI), and / or Layer Indicator (LI).

[0006] In some implementations, CSI reporting is based on a single codebook configuration. For example, the UE provides CSI to the network entity based on a single configuration of antenna ports (N1, N2). UEs near the cell edge may have greater coupling loss than UEs near the cell center. Therefore, UEs near the cell edge may have lower-rank transmission (e.g., rank 1 transmission), which can be associated with higher power allocation / more active antenna ports at the network entity for sending Physical Downlink Shared Channel (PDSCH) transmissions to the UE. Conversely, UEs near the cell center may have higher-rank transmissions, which may require a reduced number of antenna ports for PDSCH transmission. However, a single codebook configuration for CSI reporting limits the UE to reporting CSI based on a single antenna port configuration, making it difficult for the network entity to determine a more appropriate number of antenna ports for PDSCH transmission.

[0007] The aspects of this disclosure address the aforementioned and other deficiencies by implementing a rank-specific codebook configuration process for network entities to communicate with the UE on a rank-specific basis. In a first example, the UE may receive from the network entity a single configuration that jointly indicates the set of rank-specific parameters used for CSI reporting. In a second example, the UE may receive from the network entity a separate configuration for individual rank-specific parameters associated with CSI reporting. Based on determining a more appropriate number of antenna ports to be used for PDSCH transmission, the rank-specific codebook configuration process can provide improved accuracy for CSI measurements and report CSI measurements to the network entity.

[0008] According to some aspects, the UE receives a rank-specific CSI report configuration from the network entity, which indicates rank-specific parameters used for CSI reporting. The UE sends a CSI report to the network entity, which includes CSI measurement information for CSI-RS, associated with the rank-specific parameters.

[0009] Depending on some aspects, the network entity sends a rank-specific CSI reporting configuration to the UE, indicating rank-specific parameters used for CSI reporting. The network entity receives a CSI report from the UE that includes CSI measurement information for CSI-RS, which is associated with rank-specific parameters. Attached Figure Description

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

[0011] Figure 2A A diagram of high-rank transmission is shown.

[0012] Figure 2B A diagram of low-rank transmission is shown.

[0013] Figure 3 A signaling diagram is shown for an example scenario, according to some embodiments, in which the UE and network entity exchange messages and implement procedures for performing rank-specific configuration and reporting processes.

[0014] Figure 4 This is a flowchart of the wireless communication method at the UE.

[0015] Figure 5 This is a flowchart of a wireless communication method at a network entity.

[0016] Figure 6A An example of a rank-specific codebook configuration based on a codebook configuration is shown.

[0017] Figure 6B An example of a configuration of a rank-specific codebook based on a codebook configuration set is shown.

[0018] Figure 6C An example of a CSI report based on a CSI report configuration with more than one codebook is shown.

[0019] Figure 7 An example of port selection for CSI measurements with a reduced number of ports is shown.

[0020] Figure 8 An example of a CSI report based on the CSI-RS set, as well as the codebook and rank-restricted set, is shown.

[0021] Figure 9 An example of a CSI report configured based on multiple CSI reports is shown.

[0022] Figure 10 This is a flowchart of the wireless communication method at the UE.

[0023] Figure 11 This is a flowchart of a wireless communication method at a network entity.

[0024] Figure 12 This is a diagram illustrating the hardware implementation of an example UE device.

[0025] Figure 13 It is a diagram illustrating the hardware implementation of one or more example network entities. Detailed Implementation

[0026] Figure 1Figure 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, while others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as 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 RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0027] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functions. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functions among two or more units located in various physical locations, as well as virtually distributing the functions of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate wired or wirelessly with at least one other unit. For example, base stations 104d / 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 the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base station 104.

[0028] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission media—such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108d and CU 110d to transmit or receive information / signals between DU 108d and CU 110d. In a further example, a wireless interface that 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 transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0029] RU 106 can be configured to implement low-level functions. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functions such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0030] 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, inter-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. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0031] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to base station 104. Therefore, 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 communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0032] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0033] The communication link between UE 102 and 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. UE 102 and base station 104 / RU 106 can utilize a per-carrier Y MHz spectral bandwidth (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. Carriers can be adjacent to each other along the spectrum or can be non-adjacent. In the example, uplink and downlink carriers can be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with the primary cell (PCell), and the secondary component carrier can be associated with the secondary cell (SCell).

[0034] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0035] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on the different frequencies / wavelengths associated with it. Fifth-generation (5G) NR is generally associated with two operating frequency ranges (FRs) known 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, which includes 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 different from the "extremely high frequency" (EHF) band, but is an approximate subset of it, the EHF band which ranges from 30 GHz to 300 GHz, and is sometimes also referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are generally referred to as the "mid-band" frequencies. The operating frequency band of the mid-band can be referred to as Frequency Range 3 (FR3), ranging from 7.125 GHz to 24.25 GHz. The frequency bands within FR3 can include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 can be extended to the mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communication above 52.6 GHz, which is associated with the upper limit of FR2. Three of these higher operating frequency bands are 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 "below 6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies within FR2-1, FR4, FR2-2, and / or FR5, or frequencies within the EHF band.

[0036] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b.

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

[0038] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as 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 can be the primary node, while base station / RU 160a can be the secondary node.

[0039] Uplink / downlink signaling can also be communicated via a Satellite Positioning System (SPS) 114. In the example, the SPS 114 of cell 190c can communicate with one or more UEs 102 (such as UE 102c) and one or more base stations 104 / RU 106 (such as RU 106c). The SPS 114 can correspond to one or more of Global Navigation Satellite Systems (GNSS), Global Positioning Systems (GPS), Non-Terrestrial Networks (NTN), or other satellite positioning / location systems. The SPS 114 can 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, Terrestrial Beacon Systems (TBS), sensor-based information, NR Enhanced Cell ID (NR E-CID) technology, Downlink Angle of Arrival (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.

[0040] Still referencing Figure 1 In some respects, any of the UEs 102 may include a reporting component 140 configured to: receive from network entity 104 a rank-specific CSI report configuration indicating rank-specific parameters for CSI reporting; and send to network entity 104 a CSI report including CSI measurement information for CSI-RS associated with the rank-specific parameters.

[0041] In some respects, any of the base stations 104 or the network entity of the base station 104 may include a rank-specific configuration component 150 configured to: send a rank-specific CSI report configuration to the UE 102 indicating rank-specific parameters for CSI reporting; and receive from the UE 102 a CSI report including CSI measurement information for CSI-RS associated with the rank-specific parameters.

[0042] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with one or more other figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0043] Figure 2A Figure 200 illustrates downlink transmissions using different transmission powers for serving UE 102a at the center of cell 206. Figure 200 includes network entity 104, serving UE 102a, and victim UE 102b. Network entity 104 can utilize network beam 204a to schedule downlink (DL) transmissions to serving UE 102a.

[0044] Serving UE 102a can be located at the center of cell 206. In this case, the coupling loss between serving UE 102a and network entity 104 can be small. Therefore, serving UE 102a can send a report including a rank indicator RI indicating a high-rank transmission. Because RI indicates a high-rank transmission, network entity 104 sends PDSCH transmissions from a reduced number of antenna ports. However, currently, the network entity can only configure a single codebook for CSI reporting. Therefore, serving UE 102a can only report CSI based on a single codebook configuration of antenna ports (N1, N2). Network entity 104 may not be able to accurately determine the number of antenna ports used for PDSCH transmission.

[0045] Still referencing Figure 2AIf network entity 104 uses more antenna ports for downlink transmission, it may consume unnecessary power, potentially increasing interference to other UEs in neighboring cells (e.g., victim UE 102b). Referring to the spectral efficiency with respect to the number of antenna ports 208a, the spectral efficiency (SE) of serving UE 102a remains substantially unchanged with an increase in the number of antenna ports (e.g., from 16 ports to 32 ports). However, referring to the spectral efficiency with respect to the number of antenna ports 208b, the spectral efficiency (SE) of victim UE 102b can decrease significantly with an increase in the number of antenna ports (e.g., from 16 ports to 32 ports).

[0046] Figure 2B Figure 240 illustrates downlink transmissions using different transmission powers for the serving UE 102 at the edge of cell 206. Figure 204 includes network entity 104, serving UE 102a, and victim UE 102b. Network entity 104 can utilize network beam 204b to schedule downlink (DL) transmissions to serving UE 102a.

[0047] Serving UE 102a may be located at the edge of cell 206. In this case, serving UE 102a may not have sufficient cell coverage. Therefore, serving UE 102a may send a report including a rank indicator (RI) indicating low-rank transmission. Because the RI indicates low-rank transmission, network entity 104 uses a larger number of antenna ports (e.g., 32 ports), which can increase the SE of serving UE 102a.

[0048] Still referencing Figure 2B If network entity 104 uses more antenna ports (e.g., 32 ports) for downlink transmission, network entity 104 may potentially increase interference to other UEs in neighboring cells (e.g., victim UE 102b). Referring to spectrum efficiency versus antenna port number 208c, the spectrum efficiency (SE) of serving UE 102a increases with the increase in the number of antenna ports (e.g., from 16 ports to 32 ports). In this scenario, if network entity 104 uses a reduced number of antenna ports (e.g., 16 ports), serving UE 102 may experience spectrum efficiency (SE) degradation. Referring to spectrum efficiency versus antenna port number 208d, the spectrum efficiency (SE) of victim UE 102b decreases with the increase in the number of antenna ports (e.g., from 16 ports to 32 ports).

[0049] Network entity 104 can allocate different transmission power to serving UE 102a with high-rank or low-rank transmission. For example, network entity 104 can allocate higher transmission power to serving UE 102a with low-rank transmission. However, network entity 104 can allocate lower transmission power to serving UE 102a with high-rank transmission to save network power and reduce interference to victim UE 102b.

[0050] although Figures 2A to 2B Two UEs (e.g., 102a and 102b) are shown, but it should be understood that, based on the aspects described in detail below, network entity 104 can serve more than two UEs. Therefore, Figure 3 The diagram illustrates a signaling scenario in which user equipment (UE) and network entities exchange messages and implement procedures for performing rank-specific configuration and reporting processes to address these technical issues.

[0051] Figure 3 Signaling diagram 300 illustrates an example scenario in which UE 102 and network entity 104 exchange messages and implement procedures for performing rank-specific configuration and reporting processes, according to some embodiments. Network entity 104 may correspond to a base station or entities at a base station such as RU 106, DU 108, CU 110, etc.

[0052] In some examples, initially, UE 102 may send a 302 (which network entity 104 can receive) UE capability report to network entity 104, which indicates the UE's ability to send reports associated with a codebook configuration set and a rank restriction set. The UE capability report may also indicate one or more of the following parameters: a first maximum number of codebooks configured for CSI reporting, a second maximum number of CSIs configured for CSI reporting, a third maximum number of CSIs configured for reporting links, and a fourth maximum number of reported CSIs configured for reporting links.

[0053] Based on UE capabilities, network entity 104 sends (UE 102 receives 304) a rank-specific CSI report configuration via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a CSI report configuration with a power offset between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration has multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits.

[0054] In some implementations, network entity 104 configures a CSI report configuration, wherein network entity 104 configures a codebook configuration set and a rank constraint set, and each rank constraint is mapped to each codebook configuration respectively. In some other implementations, network entity 104 configures multiple CSI report configurations, wherein each CSI report configuration provides a codebook configuration and a rank constraint. Network entity 104 configures CSI report configurations as linked CSI report configurations. Network entity 104 configures orthogonal rank constraints for linked CSI report configurations. Therefore, the candidate rank is different in different CSI report configurations.

[0055] Network entity 104 sends 306 (UE 102 receives 306) to trigger a CSI report configured for the CSI report and / or a Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI) for CSI acquisition of CSI-RS.

[0056] For a certain type of CSI report (e.g., semi-persistent or aperiodic CSI report) and / or a certain type of CSI-RS (e.g., semi-persistent or aperiodic CSI-RS), the network entity may send a second control signaling (e.g., Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI)) that triggers the configured report and / or configured CSI-RS resources.

[0057] Network entity 104 sends 308 (UE 102 receives 308) CSI-RS for CSI acquisition.

[0058] Network entity 104 receives 310 (UE 102 sends 310) a CSI report based on one or more CSI report configurations.

[0059] In this disclosure, unless otherwise specified, RRC signaling may instruct an RRC reconfiguration message or a System Information Block (SIB) from network entity 104 to UE 102, wherein the SIB may be an existing SIB (e.g., SIB1) or a new SIB sent by the network entity (e.g., SIB J, where J is an integer greater than 21). Additionally, network entity 104 may obtain UE capabilities via UE capability reporting signaling or from another network entity 104 or the core network (e.g., Access and Mobility Management Function (AMF)).

[0060] Figure 3 A signaling diagram is provided illustrating an example scenario in which the UE and network entities exchange messages and implement procedures for performing rank-specific configuration and reporting processes. Figure 4 A method from the UE side of the wireless communication link is described.

[0061] Now go to Figure 4 This illustrates an example method 400 for performing rank-specific configuration and reporting procedures implemented in the UE. Method 400 can be... Figures 1 to 2B The UE 102 implementation is depicted in the image. (Reference) Figures 1 to 3 Method 400 can be executed by UE 102, UE equipment 1200, etc., which may include memory 1224' and may correspond to the entire UE 102 or UE equipment 1200, or components of UE 102 or UE equipment 1200 (such as wireless baseband processor 1224 and / or application processor 1206).

[0062] UE 102 sends a 402 indication to network entity 104 of the UE capabilities supported by the rank-specific codebook configuration. For example, refer to... Figure 3 UE 102 can send a 302 UE capability report to network entity 104, which indicates the UE's ability to send reports associated with the codebook configuration set and the rank restriction set.

[0063] UE 102 receives 404 RRC signaling from network entity 104. This RRC signaling is configured with multiple codebook configurations corresponding to different rank limits and / or a CSI report configuration for the power offset between CSI-RS and PDSCH. In some implementations, the RRC signaling configuration includes multiple CSI report configurations with different codebook configurations and / or power offsets between CSI-RS and PDSCH, as well as rank limits. For example, refer to... Figure 3 UE 102 can receive a 304-specific CSI report configuration from network entity 104 via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between CSI-RS and PDSCH. In some implementations, the RRC signaling configuration is a CSI report configuration with multiple links having different codebook configurations and / or power offsets between CSI-RS and PDSCH, as well as rank limits.

[0064] UE 102 can receive a 406-triggered CSI report configured for one or more CSI reports and / or a MAC CE or DCI for CSI acquisition from network entity 104. (See reference) Figure 3 For example, UE 102 receives 306 triggering a CSI report configured for the configured CSI report and / or a Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI) for CSI acquisition of CSI-RS.

[0065] UE 102 receives CSI-RS 408 from network entity 104 for CSI acquisition. (Reference) Figure 3 For example, UE 102 receives 308 CSI-RS for CSI acquisition.

[0066] UE 102 determines CSI 410 based on the received CSI report configuration and sends the determined CSI to network entity 104. (See reference) Figure 3 For example, UE 102 sends a CSI report based on the CSI report configuration 310.

[0067] Figure 4 A method from the UE side of the wireless communication link is described, while Figure 5 A method from the network side of a wireless communication link is described.

[0068] Figure 5 This is flowchart 500, which describes a method for wireless communication at a network entity. (Reference) Figures 1 to 3 The method can 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 1306, DU processor 1326, CU processor 1346, etc.). One or more network entities 104 may include memories 1306' / 1326' / 1346', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1306, DU processor 1326, or CU processor 1346).

[0069] Network entity 104 receives a UE capability report from UE 102 indicating the supported rank-specific codebook configuration, as specified in 502. For example, refer to... Figure 3 Network entity 104 receives a UE capability report 302 from UE 102, which indicates the UE's ability to send reports associated with the codebook configuration set and the rank restriction set.

[0070] Network entity 104 sends a 504 RRC signaling message to UE 102. This RRC signaling message is configured with multiple codebook configurations corresponding to different rank limits and / or a CSI report configuration for the power offset between CSI-RS and PDSCH. In some implementations, the RRC signaling message configuration includes multiple CSI report configurations with different codebook configurations and / or power offsets between CSI-RS and PDSCH, as well as rank limits. For example, refer to... Figure 3The network entity sends a 304 rank-specific CSI report configuration to UE 102 via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between CSI-RS and PDSCH. In some implementations, the RRC signaling configuration has multiple linked CSI report configurations with different codebook configurations and / or power offsets between CSI-RS and PDSCH, as well as rank limits.

[0071] Network entity 104 sends a 506 trigger to UE 102 to perform a CSI report configured for one or more CSI reports and / or a MAC CE or DCI for CSI acquisition of CSI-RS. For example, refer to Figure 3 Network entity 104 sends 306 to UE 102 to trigger the CSI report configured for the configured CSI report and / or the Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI) for CSI acquisition of CSI-RS.

[0072] Network entity 104 sends CSI-RS 508 for CSI acquisition to UE 102. For example, refer to Figure 3 Network entity 104 sends 308 CSI-RS for CSI acquisition to UE 102.

[0073] Network entity 104 receives 510 CSI reports corresponding to one or more CSI report configurations. For example, refer to Figure 3 Network entity 104 receives 310 CSI reports from UE 102 based on one or more CSI report configurations.

[0074] Figure 5 A method from the network side of the wireless communication link is described, while Figure 6A An example of a rank-specific codebook configuration based on a codebook configuration is shown.

[0075] Figure 6A Example 600 is a configuration of a rank-specific codebook based on a codebook configuration. In some implementations, network entity 104 uses a codebook configuration 601 (e.g., codebookConfig) to configure the codebook set.

[0076] refer to Figure 6AIn this embodiment, for CSI reports, network entity 104 configures a single CSI report configuration 602, which configures at least one of the following parameters: a codebook set 604, a rank limit set 606, and a power offset set 608 between the CSI-RS and PDSCH. Each rank limit (e.g., rank limit 1 606a) is mapped one-to-one to a codebook configuration (e.g., codebook 604a with port configuration 1) and a power offset between the CSI-RS and PDSCH (e.g., power offset 1 608a). Network entity 104 may configure orthogonal rank limits. Therefore, the candidate rank corresponding to each rank limit should be different.

[0077] In one example, network entity 104 configures a first codebook configuration 604a for a first rank constraint 606a corresponding to lower ranks (e.g., rank = 1 and 2). The first rank constraint 606a is mapped one-to-one to power offset 1 608a. Network entity 104 configures a second codebook configuration 604b for a second rank constraint 606b corresponding to higher ranks (e.g., rank = 3 and 4). The second rank constraint 606b is mapped one-to-one to power offset 2 608b.

[0078] In some other implementations, network entity 104 configures a common rank limit for the CSI report, and the power offset between each codebook and / or CSI-RS and PDSCH is mapped to each candidate rank. In one example, network entity 104 configures the rank limit indicating the candidate rank as {1, 2, 4}. Then, network entity 104 configures three codebooks and / or three power offsets, with each codebook and / or power offset corresponding to a rank {1, 2, 4}.

[0079] In some implementations, network entity 104 configures different numbers of ports for the codebook. In other implementations, network entity 104 configures a common value for at least one parameter in the codebook configuration for the codebook set, other than the number of ports. Therefore, network entity 104 avoids configuring different values ​​for at least one parameter in the codebook configuration, other than the number of ports. In one example, network entity 104 configures codebooks of the same type (e.g., Type1, Type2, eType2, etc.) and codebook mode (e.g., codebookMode) in the codebook set. In another example, if the codebook is configured as a Type2 codebook, network entity 104 configures the same values ​​for the number of PMIs per CQI (e.g., numberOfPMI-SubbandsPerCQI-Subband), the number of beams (e.g., numberOfBeams), and the parameter combination (e.g., paramCombination). In some other implementations, UE 102 may report UE capabilities that indicate whether UE 102 supports different values ​​for at least one of the parameters in the codebook configuration for the codebook set, other than the number of ports.

[0080] In some implementations, UE 102 measures the CSI based on the codebook for each rank in the CSI reporting configuration used for triggering, and UE 102 reports only one CSI to the network entity using either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). In addition to other CSI elements indicating the codebook corresponding to the CSI, UE 102 may also report a Codebook Indicator (CI). When reporting the CSI via a long PUCCH (e.g., a PUCCH with more than four symbols) or PUSCH, UE 102 may report the CI in either CSI Part 1 or CSI Part 2. Alternatively, network entity 104 configures orthogonal rank constraints. UE 102 can then indicate the codebook used for the CSI by reporting RIs, where RIs are based on all rank constraints in the CSI reporting configuration. In one example, network entity 104 configures the two rank constraints indicating candidate ranks as {1, 3} and {4, 7}. Then, RI={0, 1, 2, 3} indicates the rank {1, 3, 4, 7} respectively.

[0081] In some other implementations, network entity 104 can configure the number of reported CSIs via RRC signaling, MAC CE, or DCI. In some other implementations, UE 102 reports one CSI per codebook. In some other implementations, UE 102 reports a UE capability indicating the maximum number of reported CSIs configured for CSI reports with more than one codebook. UE 102 can multiplex CSIs based on the order of the codebooks. In one example, UE 102 multiplexes CSIs for the first codebook, then multiplexes CSIs for the second codebook, and so on.

[0082] Figure 6B Example 650 is a configuration of a rank-specific codebook based on a codebook configuration set. For example... Figure 6B As shown, network entity 104 configures the codebook set through a codebook configuration set (e.g., codebook ConfigList). Each codebook configuration with port configuration and rank limit (e.g., codebook configuration 654a with port configuration 1 and rank limit 1) is mapped one-to-one to a corresponding power offset between CSI-RS and PDSCH (e.g., power offset 1 658a). For example, as... Figure 6B As shown, codebook configuration 654a with port configuration 1 and rank limit 1 is mapped one-to-one to power offset 1 658a, codebook configuration with port configuration 2 and rank limit 2 is mapped one-to-one to power offset 2, and so on.

[0083] Figure 6C An example 680 of a CSI report based on a CSI report configuration with more than one codebook is shown. For example, such as... Figure 6C As shown, CSI report configuration 682 includes codebook configuration 684a with port configuration 1 and rank limit 1, codebook configuration 684b with port configuration 2 and rank limit 2, ..., and codebook configuration 684c with port configuration N and rank limit N. The reported CSIs (e.g., 686a and 686b) include CI indicating the codebook used for the CSI measurement. For example, UE 102 can send CSI report 686a, which includes CI=0 and other CSIs (e.g., RI / PMI / CQI) corresponding to codebook configuration 1. UE 102 can also send CSI report 686b, which includes CI=2 and other CSIs (e.g., RI / PMI / CQI) corresponding to codebook configuration 3.

[0084] In this embodiment, network entity 104 is configured with CSI-RS for CSI reporting configurations having more than one codebook or power offset. The number of ports used for CSI-RS is based on the maximum number of horizontal and vertical ports in the configured codebook. In one example, the number of ports used for CSI-RS is [number missing]. ,in and This refers to the number of horizontal and vertical ports configured for a codebook with the maximum number of ports.

[0085] For CSI measurements from other codebooks with a reduced number of ports, the antenna-to-port mapping is determined based on the configurations N1 and N2 in the codebook and the number of horizontal and vertical ports configured for the codebook with the maximum number of ports.

[0086] Figure 7 Example 700 of port selection for CSI measurement for a codebook with a reduced number of ports is shown. Network entity 104 determines the number of horizontal and vertical ports (e.g., N1=4, N2=4) based on (N1, N2) configured in a codebook with the maximum number of ports. For example, the number of horizontal and vertical ports 702 is 16.

[0087] like Figure 7 As shown, network entity 104 reduces the number of port antenna ports from the CSI-RS configuration used for CSI measurements against the codebook. For example, network entity 104 determines the number of horizontal and vertical ports used for CSI measurements based on (N1, N2) configured in the codebook with the reduced number of ports (e.g., N1=4, N2=2). In this example, the number of horizontal and vertical ports 704 used for CSI measurements is 8, which is less than the number of horizontal and vertical ports 702.

[0088] Figure 8 An example 800 of a CSI report based on the CSI-RS set, codebook set, and rank-restricted set is shown. (Reference) Figure 8 For example, CSI report configuration 802 configures rank-specific parameters for a CSI-RS set 808, a codebook set 804, and a rank limit set 806. In an embodiment, network entity 104 configures a CSI-RS set for a CSI report configuration having more than one codebook or power offset. Each CSI-RS corresponds to a codebook, power offset, or rank limit. For example, CSI-RS 1 808a with a power offset of 1 is mapped one-to-one to rank limit 1 806a and codebook 1 804a.

[0089] In some implementations, network entity 104 configures at least one parameter of the parameters used for the CSI-RS set to have the same value. These parameters include the Transport Configuration Indicator (TCI) or Quasi-Co-bit (QCL), resource block, subcarrier, temporal behavior (aperiodic, semi-persistent, periodic), periodicity, and slot offset. Therefore, network entity 104 can avoid configuring different values ​​for at least one of the aforementioned parameters used for the CSI-RS set. In some other implementations, UE 102 can report UE capabilities indicating whether the UE supports different values ​​for at least one of the aforementioned parameters used for the CSI-RS set.

[0090] In some other implementations, network entity 104 may configure the same number of ports or the same number of horizontal and vertical ports for each CSI-RS resource. Alternatively, network entity 104 may configure an antenna index (horizontal and vertical port index) for each port of the CSI-RS resource. Network entity 104 may configure the association between the CSI-RS resource and each codebook. The UE 102 can then measure CSI from more than one CSI-RS resource.

[0091] In this embodiment, network entity 104 configures a CSI-RS report configuration set for a rank-specific codebook based on CSI reports. Network entity 104 can configure links for CSI-RS report configuration via RRC signaling, MAC CE, or DCI.

[0092] In one example, for periodic CSI reporting, network entity 104 configures the CSI reporting configuration for the link used for CSI reporting via RRC signaling. For semi-persistent CSI reporting, network entity 104 indicates the CSI reporting configuration index for the link used to activate the CSI report. For non-periodic CSI reporting, network entity 104 can trigger a CSI report corresponding to one or more CSI reporting configurations, where the triggered CSI reporting configuration is the linked CSI reporting configuration.

[0093] In some implementations, network entity 104 can configure different codebooks and / or power offsets and rank limits between the CSI-RS and PDSCH for linked CSI report configurations. Network entity 104 can provide the same configuration for at least one parameter in the CSI report configuration other than the codebook, power offset, and rank limit. Therefore, network entity 104 can avoid configuring different values ​​for at least one parameter in the CSI report configuration other than the codebook, power offset, and rank limit. In some other implementations, UE 102 can report UE capabilities indicating whether the UE supports different values ​​for at least one parameter in the CSI report configuration other than the codebook, power offset, and rank limit.

[0094] Figure 9 An example 900 of CSI reporting based on multiple CSI reporting configurations is shown. In some implementations, UE 102 reports only one CSI based on the linked CSI reporting configurations. In some implementations, UE 102 may also report a CSI reporting configuration indicator (CRCI) (e.g., 906a) indicating the corresponding CSI reporting configuration (902a) used for the reported CSI, in addition to other CSI elements (e.g., RI / PMI / CQI). When reporting CSI via a long PUCCH (e.g., a PUCCH with more than 4 symbols) or PUSCH, UE 102 may report the CRCI in CSI section 1 or CSI section 2. In some other implementations, network entity 104 configures orthogonal rank constraints for linked CSI reporting configurations. Therefore, network entity 104 avoids configuring non-orthogonal rank constraints for linked CSI reporting configurations. UE 102 can then report an RI to indicate the corresponding CSI reporting configuration used for the reported CSI. Therefore, RI is based on all rank constraints configured in the linked CSI report configurations. In one example, network entity 104 configures two rank constraints indicating candidate ranks in two CSI report configurations as {1,3} and {4,7}. Then, RI={0, 1, 2, 3} indicates ranks {1, 3, 4, 7} respectively.

[0095] In some other implementations, network entity 104 can configure the number of CSIs reported in link-based CSI reporting via RRC signaling, MAC CE, or DCI. UE 102 can report a UE capability indicating the maximum number of CSIs reported in the link-based CSI reporting configuration. In some other implementations, UE 102 reports one CSI per CSI reporting configuration. UE 102 can reuse CSIs based on the order of CSI reporting configuration identifiers.

[0096] In this embodiment, network entity 104 configures public CSI-RS resources in a linked CSI reporting configuration. The number of ports used for CSI-RS is based on the maximum number of horizontal and vertical ports in the codebook configured in the linked CSI reporting configuration. In one example, the number of ports used for CSI-RS is... ,in and This refers to the number of horizontal and vertical ports configured for a codebook with the maximum number of ports.

[0097] For CSI measurements from other codebooks with a reduced number of ports, the antenna-to-port mapping is determined based on the configurations of N1 and N2 in the codebook used for CSI reporting configuration and the number of horizontal and vertical ports in the codebook with the maximum number of ports in the CSI reporting configuration used for linking.

[0098] In this embodiment, network entity 104 configures a CSI-RS or a list of CSI-RS for the linked CSI report configuration. The CSI-RS in the CSI report configuration correspond to the codebook, power offset, and rank limit configured in the CSI report configuration.

[0099] In some implementations, network entity 104 configures at least one parameter of the CSI-RS parameters in the CSI report configuration for linking to have the same value. These parameters include TCI or QCL, resource block, subcarrier, temporal behavior (aperiodic, semi-persistent, periodic), periodicity, and slot offset. Therefore, network entity 104 can avoid configuring different values ​​for at least one of the above parameters for the CSI-RS set. In some other implementations, UE 102 can report UE capabilities indicating whether the UE supports different values ​​for at least one of the above parameters of the CSI-RS in the CSI report configuration for linking.

[0100] Figure 10 A flowchart 1000 illustrates a method for wireless communication at the UE. (Reference) Figures 1 to 4 and Figure 12 The method can be executed by UE 102, UE equipment 1202, etc., which may include memories 1226', 1206', 1216 and may correspond to the entire UE 102 or the entire UE equipment 1202, or components of UE 102 or UE equipment 1202 (such as wireless baseband processor 1226 and / or application processor 1206).

[0101] UE 102 can send a UE capability report (1002) to network entity 104. For example, refer to... Figure 4UE 102 can send a 402 indication to network entity 104 of the UE capabilities supported by the rank-specific codebook configuration.

[0102] UE 102 receives 1004 from network entity 104, indicating the rank-specific CSI reporting configuration for rank-specific parameters used in CSI reporting. For example, refer to... Figure 4 Network entity 104 sends a 404 rank-specific CSI report configuration via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration has multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits. See also: Figure 6A , Figure 6B , Figure 6C , Figure 7 , Figure 8 and Figure 9 An example of CSI report configuration.

[0103] UE 102 receives a 1004A instruction from network entity 104, specifying the CSI report configuration for a particular rank. For example, refer to... Figure 4 Network entity 104 sends a 404 rank-specific CSI report configuration via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration includes multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits.

[0104] UE 102 receives from network entity 104 an indication of the association between multiple rank-specific CSI reporting configurations, including rank-specific CSI reporting configurations. For example, refer to... Figure 4 Network entity 104 sends a 404 rank-specific CSI report configuration via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration includes multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits.

[0105] UE 102 can receive 1006 trigger indications from network entity 104 for CSI reports configured based on rank-specific CSI reports. For example, refer to Figure 4 UE 102 receives from network entity 104 a second control signaling 406 triggering at least one report configuration and / or at least one SSB / CSI-RS resource. For example, refer to Figure 4 Network entity 104 sends a 406 trigger to UE 102 to send a CSI report configured for the configured CSI report and / or a Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI) for CSI acquisition of CSI-RS.

[0106] UE 102 receives a single CSI-RS (Center for SI Measurement Information) from network entity 104 (referred to as 1008A). This single CSI-RS is associated with a rank-specific CSI reporting configuration. For example, refer to... Figure 4 UE 102 receives CSI-RS from 408 for CSI acquisition.

[0107] UE 102 receives from network entity 104 1008B multiple CSI-RS for CSI measurement information, where the CSI-RS is one of multiple CSI-RS. For example, refer to Figure 4 UE 102 receives CSI-RS from 408 for CSI acquisition.

[0108] UE 102 sends a CSI report 1010 to network entity 104, including CSI measurement information for CSI-RS, which is associated with a rank-specific parameter. For example, refer to Figure 4 Network entity 104 receives 410 CSI reports based on one or more CSI report configurations.

[0109] Figure 10 A method from the UE side of the wireless communication link is described, while Figure 11 A method from the network side of a wireless communication link is described.

[0110] Figure 11 This is a flowchart 1100 showing a method for wireless communication at a network entity. (Reference) Figures 1 to 3 , Figure 5 and Figure 13The method can 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 1306, DU processor 1326, CU processor 1346, etc.). One or more network entities 104 may include memories 1306' / 1326' / 1346', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1306, DU processor 1326, or CU processor 1346).

[0111] Network entity 104 can receive UE capability reports (1102) from UE 102. For example, refer to... Figure 5 Network entity 104 receives 502 from UE 102 indicating the UE capabilities supported by the rank-specific codebook configuration.

[0112] Network entity 104 sends 1104 to UE 102, indicating the rank-specific CSI reporting configuration for the rank-specific parameters used in CSI reporting. For example, refer to... Figure 5 Network entity 104 sends a 504 RRC signaling message to UE 102. This RRC signaling message is configured with multiple codebook configurations corresponding to different rank limits and / or a CSI report configuration for the power offset between CSI-RS and PDSCH. In some implementations, the RRC signaling message configuration includes multiple CSI report configurations with different codebook configurations and / or power offsets between CSI-RS and PDSCH, as well as rank limits. See also: Figure 6A , Figure 6B , Figure 6C , Figure 7 , Figure 8 and Figure 9 An example of CSI report configuration.

[0113] Network entity 104 sends a 1104A instruction to UE 102, specifying the CSI reporting configuration for a particular CSI reporting configuration. For example, refer to... Figure 5 Network entity 104 sends a rank-specific CSI report configuration (504) via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration includes multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits.

[0114] Network entity 104 sends 1104B to UE 102 an indication of the association between multiple rank-specific CSI reporting configurations, including rank-specific CSI reporting configurations. For example, refer to Figure 5 Network entity 104 sends a rank-specific CSI report configuration (504) via control signaling (e.g., RRC signaling (RRCReconfiguration)). This RRC signaling configuration has multiple codebook configurations corresponding to different rank limits and / or a single CSI report configuration with power offsets between the CSI-RS and PDSCH. In some implementations, the RRC signaling configuration includes multiple linked CSI report configurations with different codebook configurations and / or power offsets between the CSI-RS and PDSCH, as well as rank limits.

[0115] Network entity 104 sends 1106 a trigger indication to UE 102 for a CSI report configured based on a rank-specific CSI report. For example, refer to Figure 5 Network entity 104 sends 506 to UE 102 to trigger the CSI report configured for the configured CSI report and / or the Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI) for CSI acquisition of CSI-RS.

[0116] Network entity 104 sends a single CSI-RS (1108A) to UE 102 for CSI measurement information. This single CSI-RS is associated with a rank-specific CSI reporting configuration. (Reference) Figure 5 For example, UE 102 receives 508 CSI-RS for CSI acquisition.

[0117] Network entity 104 sends 1108B to UE 102 multiple CSI-RS for CSI measurement information, where the CSI-RS is one of multiple CSI-RS. (Reference) Figure 5 For example, UE 102 receives 508 CSI-RS for CSI acquisition.

[0118] Network entity 104 sends a CSI report to the UE, including CSI measurement information for CSI-RS, which is associated with a rank-specific parameter. (Reference) Figure 5 For example, network entity 104 receives 510 CSI reports from UE 102 based on one or more CSI report configurations.

[0119] like Figure 12 The described UE equipment 1202 can execute the methods of signaling diagram 300 and flowcharts 400 and 1000. For example... Figure 13 One or more network entities 104 described can execute the methods of signaling diagram 300 and flowcharts 500 and 1100.

[0120] Figure 12 Figure 1200 illustrates an example of a hardware implementation of UE device 1202. UE device 1202 may be UE 102, a component of UE 102, or may implement UE functions. UE device 1202 may include an application processor 1206, which may have on-chip memory 1206'. In the example, application processor 1206 may be coupled to a secure digital (SD) card 1208 and / or a display 1210. Application processor 1206 may also be coupled to a sensor module 1212, a power supply 1214, an additional memory module 1216, a camera 1218, and / or other related components. For example, sensor module 1212 may control a barometric pressure sensor / altimeter, motion sensors (such as an inertial management unit (IMU), gyroscope, accelerometer), a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, audio devices, and / or other technologies for positioning.

[0121] The UE equipment 1202 may further include a wireless baseband processor 1226, which may be referred to as a modem. The wireless baseband processor 1226 may have on-chip memory 1226'. Together with and similarly to the application processor 1206, the wireless baseband processor 1226 may also be coupled to a sensor module 1212, a power supply 1214, an additional memory module 1216, a camera 1218, and / or other related components. The wireless baseband processor 1226 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1220 and / or one or more transceivers 1230 (e.g., wireless RF transceivers).

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

[0123] The wireless baseband processor 1226 and application processor 1206 may each include computer-readable media / memory 1226' and 1206', respectively. An additional memory module 1216 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1226', 1206', and 1216 may be non-transitory. The wireless baseband processor 1226 and application processor 1206 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1226', 1206', and 1216. When executed by the wireless baseband processor 1226 / application processor 1206, this software causes the wireless baseband processor 1226 / application processor 1206 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1226 / application processor 1206 during software execution. The wireless baseband processor 1226 / application processor 1206 may be a component of UE 102. UE equipment 1202 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1226 and / or the application processor 1206. In other examples, UE equipment 1202 may be the entire UE 102 and may include additional modules for equipment 1202.

[0124] As discussed, the reporting component 140 is configured to: receive from network entity 104 a rank-specific CSI report configuration indicating rank-specific parameters for CSI reporting; and send to network entity 104 a CSI report including CSI measurement information for CSI-RS associated with the rank-specific parameters.

[0125] Reporting component 140 may be located within application processor 1206 (e.g., at 140a), within wireless baseband processor 1226 (e.g., at 140b), or within both application processor 1206 and wireless baseband processor 1226. Reporting components 140a-140b may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for use by one or more processors, or a combination thereof.

[0126] Figure 13 Figure 1300 illustrates 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 functions. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1346, which may have on-chip memory 1346'. In some aspects, CU 110 may further include an additional memory module 1356 and / or a communication interface 1348, both of which may be coupled to the CU processor 1346. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1348 of CU 110 and the communication interface 1328 of DU 108).

[0127] DU 108 may include a DU processor 1326, which may have on-chip memory 1326'. In some aspects, DU 108 may further include an additional memory module 1336 and / or a communication interface 1328, both of which may be coupled to the DU processor 1326. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1328 and RU 106's communication interface 1308.

[0128] RU 106 may include an RU processor 1306, which may have on-chip memory 1306'. In some aspects, RU 106 may further include an additional memory module 1316, a communication interface 1308, and one or more transceivers 1330, all of which may be coupled to the RU processor 1306. RU 106 may further include an antenna 1340, which may be coupled to one or more transceivers 1330, enabling RU 106 to communicate with UE 102 via the antenna 1340 through one or more transceivers 1330.

[0129] On-chip memories 1306', 1326', 1346' and additional memory modules 1316, 1336, 1356 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1306, 1326, 1346 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1306, 1326, 1346, the software causes the processor 1306, 1326, 1346 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by processors 1306, 1326, 1346 during software execution. In the example, the rank-specific configuration component 150 may be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0130] As discussed, the rank-specific configuration component 150 is configured to: send a rank-specific CSI report configuration to the user equipment (UE) 102 indicating rank-specific parameters for CSI reporting; and receive from the UE 102 a CSI report including CSI measurement information for CSI-RS associated with the rank-specific parameters.

[0131] The rank-specific configuration component 150 may be located within one or more processors of one or more network entities 104, such as RU processor 1306 (e.g., at 150a), DU processor 1326 (e.g., at 150b), and / or CU processor 1346 (e.g., at 150c). The rank-specific configuration components 150a-150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1306, 1326, 1346 configured to execute the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1306, 1326, 1346, or combinations thereof.

[0132] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is illustrative of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements of the diagram. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0133] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0134] Various aspects of wireless communication systems, such as telecommunications systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, 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.

[0135] An 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated 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 may be referred to as software, firmware, middleware, microcode, hardware description language, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0136] If the functions described herein are implemented in software, these functions may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage 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. Storage media can be any available medium that is computer-accessible.

[0137] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of 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 technologies described herein.

[0138] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous 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 decomposed components, end-user devices, etc., in various configurations.

[0139] 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 light of the full scope of this disclosure consistent with the language of the claims.

[0140] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0141] Unless otherwise expressly stated, the term "some" means 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 and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a collection of elements having one or more elements.

[0142] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).

[0143] Structural and functional equivalents of the various aspects of the elements described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A”.

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

[0145] Example 1 is a method for wireless communication at a UE, comprising: receiving from a network entity a rank-specific CSI report configuration indicating rank-specific parameters for CSI reporting; and sending to the network entity the CSI report including CSI measurement information for CSI-RS, the CSI measurement information being associated with the rank-specific parameters.

[0146] Example 2 can be combined with Example 1 and further includes: the rank-specific CSI report is configured to jointly configure a set of parameters for each of the rank-specific parameters in the CSI report.

[0147] Example 3 can be combined with Example 1 and further includes: the rank-specific CSI report configuration configures the rank-specific parameters separately for each rank-specific CSI report configuration.

[0148] Example 4 can be combined with any of Examples 1 to 3, and further includes: the rank-specific parameter includes at least one of the following: codebook configuration, rank limit, or power offset between CSI-RS and PDSCH.

[0149] Example 5 may be combined with any of Examples 1 to 4, and further includes: receiving a single CSI-RS from the network entity for the CSI measurement information, the single CSI-RS being associated with the rank-specific CSI reporting configuration.

[0150] Example 6 may be combined with any of Examples 1 to 4, and further includes: receiving from the network entity a plurality of CSI-RS for the CSI measurement information, wherein the CSI-RS is one of the plurality of CSI-RS.

[0151] Example 7 can be combined with any of Examples 1 to 6, and further includes: sending a UE capability report to the network entity, the UE capability report indicating the UE's ability to perform CSI reporting based on the rank-specific CSI report configuration.

[0152] Example 8 can be combined with Example 7 and further includes: the UE capability report indicating at least one of the following: a first capability with respect to a first maximum number of configured codebooks, a second capability with respect to a second maximum number of reported CSIs, a third capability with respect to a third maximum number of CSI report configurations; or a fourth capability with respect to the reported CSIs and a fourth maximum number of CSI report configurations.

[0153] Example 9 may be combined with any of Examples 1 to 8, and further includes: receiving from the network entity a trigger indication for the CSI report configured based on the rank-specific CSI report.

[0154] Example 10 can be combined with any of Examples 1 to 9, and further includes: the CSI report includes a CSI report configuration indicator (CRCI) associated with the rank-specific CSI report configuration.

[0155] Example 11 can be combined with any of Examples 1 to 10, and further includes: receiving the rank-specific CSI report configuration also includes receiving from the network entity an indication of association between multiple rank-specific CSI report configurations including the rank-specific CSI report configuration.

[0156] Example 12 can be combined with any of Examples 1 to 11, and further includes: the CSI report includes a codebook indicator (CI) indicating the codebook used for the CSI measurement information.

[0157] Example 13 is a method for wireless communication at a network entity, comprising: sending a rank-specific CSI report configuration to a user equipment (UE) indicating a rank-specific parameter for CSI reporting; and receiving from the UE the CSI report including CSI measurement information for CSI-RS, the CSI measurement information being associated with the rank-specific parameter.

[0158] Example 14 can be combined with Example 13 and further includes: the rank-specific CSI report is configured to jointly configure a set of parameters for each of the rank-specific parameters in the CSI report.

[0159] Example 15 can be combined with Example 13 and further includes: the rank-specific CSI report configuration configures the rank-specific parameters separately for each rank-specific CSI report configuration.

[0160] Example 16 may be combined with any of Examples 13 to 15, and further includes: the rank-specific parameter includes at least one of the following: codebook configuration, rank limitation, or power offset between the CSI-RS and the Physical Downlink Shared Channel (PDSCH).

[0161] Example 17 can be combined with any of Examples 13 to 16, and further includes: sending a single CSI-RS to the UE for the CSI measurement information, the single CSI-RS being associated with the rank-specific CSI report configuration.

[0162] Example 18 may be combined with any of Examples 13 to 16, and further includes: sending to the UE a plurality of CSI-RS for the CSI measurement information, wherein the CSI-RS is one of the plurality of CSI-RS.

[0163] Example 19 may be combined with any of Examples 13 to 18, and further includes: receiving a UE capability report from the UE, the UE capability report indicating the UE's ability to perform CSI reporting based on the rank-specific CSI report configuration.

[0164] Example 20 may be combined with Example 19 and further includes: the UE capability report indicating at least one of the following: a first capability with respect to a first maximum number of configured codebooks, a second capability with respect to a second maximum number of reported CSIs, a third capability with respect to a third maximum number of CSI report configurations; or a fourth capability with respect to the reported CSIs and a fourth maximum number of CSI report configurations.

[0165] Example 21 may be combined with any of Examples 13 to 20, and further includes sending a trigger indication to the UE for the CSI report configured based on the rank-specific CSI report.

[0166] Example 22 can be combined with any of Examples 13 to 21, and further includes: the CSI report includes a CSI report configuration indicator (CRCI) associated with the rank-specific CSI report configuration.

[0167] Example 23 can be combined with any of Examples 13 to 22, and further includes: sending the rank-specific CSI report configuration further includes: sending to the UE an indication of the association between multiple rank-specific CSI report configurations including the rank-specific CSI report configuration.

[0168] Example 24 can be combined with any of Examples 13 to 23, and further includes: the CSI report includes a codebook indicator (CI) indicating the codebook used for the CSI measurement information.

[0169] Example 25 is an apparatus for wireless communication, used to implement the method as described in any one of Examples 1 to 24.

[0170] Example 26 is an apparatus for wireless communication, including components for implementing the method as described in any one of Examples 1 to 24.

[0171] Example 27 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to perform the method as described in any one of Examples 1 to 24.

Claims

1. A method for wireless communication at a user equipment (UE) (102), comprising: Receive (304) from network entity (104) a rank-specific CSI report configuration indicating rank-specific parameters for channel state information (CSI) reporting; as well as Send (310) a CSI report to the network entity (104) including CSI measurement information for the Channel State Information Reference Signal (CSI-RS), the CSI measurement information being associated with the rank-specific parameter.

2. The method of claim 1, wherein the rank-specific CSI report is configured to jointly configure a set of parameters for each of the rank-specific parameters of the CSI report.

3. The method of claim 1, wherein the rank-specific CSI report configuration configures the rank-specific parameters individually for each rank-specific CSI report configuration.

4. The method according to any one of claims 1 to 3, wherein the rank-specific parameter includes at least one of the following: Codebook configuration, Rank restriction, or The power offset between the CSI-RS and the Physical Downlink Shared Channel (PDSCH).

5. The method according to any one of claims 1 to 4, further comprising: Receive (308) a single CSI-RS for the CSI measurement information from the network entity (104), the single CSI-RS being associated with the rank-specific CSI report configuration.

6. The method according to any one of claims 1 to 4, further comprising: Receive (308) a plurality of CSI-RS for the CSI measurement information from the network entity (104), wherein the CSI-RS is one of the plurality of CSI-RS.

7. The method according to any one of claims 1 to 6, further comprising: Send (302) UE capability report to the network entity (104), the UE capability report indicating the UE (102)’s ability to perform CSI reporting based on the rank-specific CSI report configuration.

8. The method of claim 7, wherein the UE capability report indicates at least one of the following: The first maximum number of configured codebooks is the first capability. The report states that CSI has the second largest number of second-largest capabilities. The maximum number of third capabilities configured in the CSI report; or The report's CSI and the fourth maximum number of fourth capabilities configured in the CSI report.

9. The method according to any one of claims 1 to 8, further comprising: Receive (306) a trigger indication for the CSI report configured based on the rank-specific CSI report from the network entity (104).

10. The method of any one of claims 1 to 9, wherein the CSI report includes a CSI report configuration indicator CRCI associated with the rank-specific CSI report configuration.

11. The method according to any one of claims 1 to 10, wherein receiving (304) the rank-specific CSI report configuration further comprises: Receive (304) from the network entity (104) an indication of the association between multiple rank-specific CSI report configurations, including the rank-specific CSI report configuration.

12. The method according to any one of claims 1 to 11, wherein the CSI report includes a codebook indicator CI indicating a codebook for the CSI measurement information.

13. A method for wireless communication at a network entity (104), comprising: Send (304) to User Equipment (UE) (102) an instruction for rank-specific CSI report configuration of rank-specific parameters for Channel State Information (CSI) report; as well as The UE (102) receives (310) a CSI report including CSI measurement information for the Channel State Information Reference Signal (CSI-RS), the CSI measurement information being associated with the rank-specific parameter.

14. The method of claim 13, wherein the rank-specific CSI report is configured to jointly configure a set of parameters for each of the rank-specific parameters of the CSI report.

15. The method of claim 13, wherein the rank-specific CSI report configuration configures the rank-specific parameter separately for each rank-specific CSI report configuration.

16. An apparatus for wireless communication, comprising a memory, a transceiver, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 15.

Images