CSI feedback based on codebooks associated with power fallback values

Abstract

Systems, methods, and apparatus provide channel state information (CSI) feedback based on one or more codebooks and power back-off values corresponding to the codebooks. A user equipment (UE) (110) receives (404) at least one channel state information (CSI) report configuration from a network entity (120), the at least one CSI reporting configuration includes a codebook entity, one or more power relationship indicators indicating a power relationship between a physical downlink shared channel (PDSCH) and a CSI reference signal (CSI-RS) for each codebook entity, and one or more channel measurement resources (CMRs) associated with the CSI-RS. The UE receives (408) one or more CMRs from the network entity. The UE sends (412) at least one CSI report to the network entity based on the at least one CSI report configuration and the one or more CMRs.

Description

Technical Field

[0001] The various aspects of this disclosure generally relate to wireless communication and techniques for providing channel state information (CSI) feedback based on one or more codebooks and power back-off values ​​corresponding to those codebooks. Background Technology

[0002] Multiple-input multiple-output (MIMO) technology improves the reliability and efficiency of communication between a UE and a network entity. MIMO employs multiple antennas at both the network entity and the UE to concurrently transmit and receive multiple spatial streams. MIMO can be used to improve data throughput, increase spectral efficiency, and enhance overall network performance. Beamforming is another technique that enhances signal quality between a network entity and the UE, thereby improving data rates, reducing latency, and enhancing overall network performance. In beamforming, the transmitter directs radio frequency (RF) transmission in a specific direction (e.g., toward the intended receiver), creating a “beam” of focused energy instead of radiating the signal equally in all directions.

[0003] Network entities and UEs can collaborate to determine appropriate operating parameters for MIMO and beamforming operations. For example, a network entity can provide the UE with a reference signal known as a Channel State Information Reference Signal (CSI-RS). The UE can measure various characteristics of the CSI-RS and provide Channel State Information (CSI) feedback to the network entity based on the measured characteristics. The network entity can use the CSI feedback to adjust transmission parameters to optimize MIMO and beamforming operations. Summary of the Invention

[0004] The systems, methods, and apparatuses disclosed herein each have several innovative aspects, wherein no single innovative aspect is solely responsible for the desired properties disclosed herein.

[0005] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a user equipment. The method may include receiving at least one Channel State Information (CSI) report configuration from a network entity, the at least one CSI report configuration including: a plurality of codebook entities, one or more power relationship indicators indicating the power relationship between the Physical Downlink Shared Channel (PDSCH) and the CSI Reference Signal (CSI-RS) for each of the plurality of codebook entities, and one or more channel measurement resources (CMRs) associated with the CSI-RS. The method may further include receiving the one or more CMRs from the network entity. The method may further include sending at least one CSI report to the network entity based on the at least one CSI report configuration and the one or more CMRs.

[0006] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a network entity. The method may include sending at least one Channel State Information (CSI) report configuration to a User Equipment (UE), the at least one CSI report configuration including: a plurality of codebook entities, one or more power relationship indicators indicating the power relationship between the Physical Downlink Shared Channel (PDSCH) and the CSI Reference Signal (CSI-RS) for each of the plurality of codebook entities, and one or more channel measurement resources (CMRs) associated with the CSI-RS. The method may further include sending the one or more CMRs to the UE. The method may further include receiving at least one CSI report from the UE based on the at least one CSI report configuration and the one or more CMRs.

[0007] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Attached Figure Description

[0008] It should be noted that the relative dimensions in the following figures may not be drawn to scale. The same reference numerals and names in the various figures indicate the same elements. To facilitate identification of the discussion of any particular element or action, one or more of the most significant digits in the reference numerals refer to the figure number in which that element was first introduced.

[0009] Figure 1 This is a diagram illustrating an example wireless system that includes user equipment communicating with network entities.

[0010] Figure 2 This is a block diagram illustrating an example configuration of network entities and user equipment.

[0011] Figure 3A This is a diagram illustrating the antenna port configuration for PDSCH transmission using a type 1 precoder.

[0012] Figure 3B This is a diagram illustrating the antenna port configuration for PDSCH transmission using a type 2 precoder.

[0013] Figure 4A This is a sequence diagram illustrating example operations for providing CSI feedback based on one or more codebooks and a power back-off value corresponding to those codebooks, where the UE selects a codebook.

[0014] Figure 4B This is a sequence diagram illustrating example operations for providing CSI feedback based on one or more codebooks and corresponding power back-off values, where the UE provides multiple CSIs to a network entity.

[0015] Figure 5 This is a flowchart illustrating an example UE operation for providing CSI feedback based on one or more codebooks and a power back-off value corresponding to those codebooks.

[0016] Figure 6 This is a flowchart illustrating an example network entity operation for receiving CSI feedback based on one or more codebooks and a power backoff value corresponding to those codebooks.

[0017] Figure 7 This is an illustration showing an example of CSI feedback using waveform and power backoff sensing codebook.

[0018] Figure 8 This is an illustration showing an example of CSI feedback using a subset of waveform and power backoff sensing codebook.

[0019] Figure 9 This is an illustration showing an example of CSI feedback using a waveform-specific codebook and a power backoff sensing codebook subset.

[0020] Figure 10 This is a diagram illustrating a codebook for example UE selection used for CSI feedback.

[0021] Figure 11 This is a diagram illustrating an example CSI report with a separate CSI for the configured codebook.

[0022] Figure 12 This is an illustration of a sample CSI report with a public RI for a configured codebook.

[0023] Figure 13 This is a diagram illustrating a sample CSI report with RI or PMI for a configured codebook. Detailed Implementation

[0024] For the purpose of describing the innovative aspects of this disclosure, the following description relates to certain implementations. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some examples in this disclosure are based on wireless communication according to 3GPP wireless standards such as the 4th generation (4G) Long Term Evolution (LTE) standard and the 5th generation (5G) New Radio (NR) standard. However, the described implementations can be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals or other known signals according to any wireless communication standard, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.15, or 802.16 wireless standards, for communication within wireless, cellular, or Internet of Things (IoT) networks such as systems utilizing 3G, 4G, 5G, WiFi, or future radio technologies.

[0025] As noted above, MIMO technology can improve the reliability and efficiency of communication between the UE and network entities. In MIMO-implemented systems, Channel State Information (CSI) provides information that the network entity can use to select a digital precoder for use when communicating with the UE. In some aspects, the network entity can use RRC signaling (e.g., CSI- ReportConfig The network entity can configure CSI reporting, where the Channel State Information Reference Signal (CSI-RS) is used as a Channel Measurement Resource (CMR) for the UE to measure downlink channels. In some aspects, the network entity can configure Interference Measurement Resource (IMR) for the UE to measure interference.

[0026] Network entities and UEs can collaborate to determine appropriate operating parameters for MIMO and beamforming operations. For example, the UE can identify the CSI based on configured CMR and IMR (if IMR is available). The CSI can include at least one of a Rank Indicator (RI), Precoder Matrix Indicator (PMI), Channel Quality Indicator (CQI), and Layer Indicator (LI). RI and PMI indicate the digital precoder, CQI indicates the Signal-to-Interference-plus-Noise (SINR) state to assist the network entity in determining the Modulation and Code Processing Scheme (MCS), and LI identifies the strongest layer of the reported precoder indicated by RI and PMI. The UE can provide CSI feedback to the network entity based on measured characteristics. The network entity can use the CSI feedback to adjust transmission parameters to optimize MIMO and beamforming operations.

[0027] Network entities can transmit data to UEs via the Physical Downlink Shared Channel (PDSCH). Network entities can select different waveforms and precoders for PDSCH transmission based on radio network conditions and CSI received from the UE. Different waveforms can have different peak-to-average power ratios (PAPR). It may be desirable for network entities to transmit downlink signals with low PAPR and higher transmit power compared to downlink signals with high PAPR. Downlink signals with high PAPR may produce less accurate signals (e.g., signals with higher error vector magnitude (EVM)). Therefore, to transmit downlink signals with higher PAPR, network entities can apply power backoff to PDSCH transmission.

[0028] In some aspects, network entities may use Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveforms to transmit PDSCH. In other aspects, to reduce PAPR and provide high power amplifier efficiency, network entities may use Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), or other single-carrier waveforms to transmit PDSCH. Therefore, network entities can transmit such low PAPR waveforms at higher power compared to high PAPR waveforms such as CP-OFDM. Different types of precoders and different waveforms can produce different PAPRs. Therefore, different types of precoders and different waveforms can lead to different downlink transmit power backoff values ​​or power offset values.

[0029] The first potential problem when using MIMO and beamforming is that network entities may lack information in selecting the appropriate precoder and waveform for PDSCH. The second potential problem is that the UE may lack information that could be used to provide appropriate CSI feedback to facilitate network entities in selecting the appropriate precoder and waveform.

[0030] According to publicly available information, various techniques can be used by the UE and network entities to facilitate the selection of appropriate precoders and waveforms for PDSCH transmission. In some aspects, the UE can inform the network entity that it can provide CSI feedback based on codebooks (or subsets of codebooks) corresponding to different power backoff or power offset values ​​between the PDSCH and CSI-RS. The network entity can provide the UE with a CSI reporting configuration indicating one or more codebooks corresponding to the different power backoff or power offset values, and channel measurement resources (CMR) to be used to measure the CSI associated with the different codebooks. The network entity can trigger the UE to provide CSI reports, or the UE can be configured to provide CSI reports periodically. In response to triggering or period expiration, the UE can measure CSI with respect to the different codebooks configured in the CSI reporting configuration and generate a CSI report according to the CSI reporting configuration. In some aspects, the UE selects and recommends a codebook associated with a CSI that is better than CSI associated with other codebooks. In some aspects, the UE provides CSI reports for multiple codebooks, and network entities can select a codebook based on the reported CSI. Network entities can use the CSI feedback provided by the UE to determine waveforms and codebooks that achieve better PDSCH transmission quality compared to other candidate waveforms and codebooks.

[0031] Figure 1 This is an illustration of an example wireless system 100 including user equipment 110 communicating with network entity 120. Although in Figure 1 While shown as a smartphone, UE 110 can be implemented as any suitable computing or electronic device, such as a mobile communication device, modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, Internet of Things (IoT) device (e.g., sensor node, controller / actuator node, combination thereof), etc. Network entity 120 (e.g., base station, Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), Evolved Node B, eNodeB, eNB, Next Generation Node B, gNodeB, gNB, ng-eNB, access point, radio head, etc.) can be implemented in macro cells, micro cells, small cells, pico cells, etc., or any combination thereof. Network entity 120 and UE 110 can be configured to use MIMO communication, wherein multiple beams 122 are used to exchange wireless communication signals with UE 110.

[0032] In some respects, the functionality of network entity 120, and therefore its hardware components, can be distributed across multiple network nodes or devices and can be distributed in a manner suitable for performing the functions described herein. As an example, the functionality of network entity 120 can be distributed across radio units (RUs), distributed units (DUs), or central units (CUs).

[0033] UE 110 can communicate with network entity 120 using a radio link, which can be implemented as any suitable type of radio link. The radio link may include one or more radio links (e.g., a radio link) or bearers, which are implemented using any suitable communication protocol or standard, or a combination of communication protocols or standards (such as 3GPP LTE, 5G NR, etc.). Multiple radio links can be aggregated in carrier aggregation to provide a higher data rate for UE 110.

[0034] Network entity 120 supports wireless communication with one or more UEs, such as UE 110, via radio frequency (RF) signaling using one or more applicable radio access technologies (RATs) as specified by one or more communication protocols or standards. Network entity 120 may employ any of a variety of RATs, such as NodeB (or Base Transceiver Station (BTS)) operation as a Universal Mobile Telecommunications System (UMTS) RAT (also known as "3G"), Enhanced NodeB ("eNB") operation as a 3GPP Long Term Evolution (LTE) RAT, 5G NodeB ("gNB") operation as a 3GPP 5th Generation (5G) New Radio (NR) RAT, etc.

[0035] Network entity 120 may be part of a radio access network (RAN) (e.g., Evolved Universal Terrestrial Radio Access Network E-UTRAN, 5G NR RAN, or NR RAN). Network entity 120 may connect to core network 150. For example, network entity 120 may connect to core network 150 via the NG2 interface for control plane signaling and the NG3 interface for user plane data communication when connecting to a 5G core network, or via the Si interface for control plane signaling and user plane data communication when connecting to an evolved packet core (EPC) network. Network entity 120 may communicate via the Xn interface using the Xn Application Protocol (XnAP) or via the X2 interface using the X2 Application Protocol (X2AP) to exchange user plane data and control plane data. UE 110 may connect to one or more wide area networks (WANs) 160 or other packet data networks (PDNs), such as the Internet, via network entity 120 and core network 150.

[0036] Communication between network entity 120 and UE 110 utilizes uplink (UL) transmission path 112 for RF transmission from UE 110 to network entity 120, and downlink (DL) transmission path 114 for RF transmission from network entity 120 to UE 110. Therefore, in the context of UL transmission path 112, UE 110 acts as a data transmitter and network entity 120 acts as a data receiver, while in the context of DL transmission path 114, network entity 120 acts as a data transmitter and UE 110 acts as a data receiver. UL transmission path 112 and DL transmission path 114 can utilize multiple communication channels for signal transmission. These multiple channels can each have different purposes.

[0037] UL transmission path 112 may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), and a Physical Random Access Channel (PRACH). The PUSCH is used for transmitting user data, such as voice data, video data, or text message data, from UE 110 to network entity 120. Additionally, the PUSCH can be used to transmit control information (e.g., uplink control information (UCI)). The PUSCH can be shared by multiple UEs. The PUCCH is used to transmit control information (e.g., UCI) from the UE to the network, such as channel quality feedback, scheduling requests, and acknowledgments. The PRACH is used for random access in the uplink direction, enabling the UE to access the system without prior reservation.

[0038] DL transmission path 114 may include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Broadcast Channel (PBCH), or Paging Channel. The PDSCH is used for transmitting user data from a network entity to the UE. The PDSCH can be shared by multiple UEs. Similar to the PUSCH, the data can be any type of information, such as voice data, video data, or text message data. The Paging Channel is used to notify UE 110 of the presence of an incoming service from network entity 120.

[0039] UE 110 and network entity 120 can use Channel State Information (CSI) to optimize the communication quality between UE 110 and network entity 120 or TRP. UE 110 can provide UE capability information 102, which indicates whether UE 110 supports CSI feedback based on one or more codebooks and corresponding power backoff values. If the UE indicates support for providing such CSI feedback, network entity 120 can configure UE 110 to provide multiple CSIs for different codebooks and subsets of codebooks, where different power backoff values ​​are associated with the codebooks and subsets. For example, network entity 120 can provide UE 110 with CSI reporting configuration 104 for use when reporting CSI to network entity 120. Network entity 120 can send a reference signal 108 that can be used by UE 110 to measure CSI. UE 110 can use CSI reporting configuration 104 to generate a CSI report 112. For example, the UE may report at least one of the following for each codebook or subset: Rank Indicator (RI), Precoder Matrix Indicator (PMI), Channel Quality Indicator (CQI), and Layer Indicator (LI). The RI and PMI may be used to indicate a digital precoder, and the CQI may be used to indicate the Signal-to-Interference-plus-Noise (SINR) status. In some aspects, the UE selects the codebook or subset to be used by the network entity based on the CSI of the codebook or subset and the power backoff value associated with that codebook or subset. In some other aspects, the network entity selects the codebook or subset based on the CSI reported by the UE in its CSI report.

[0040] The following text is about Figure 2 , Figure 3A , Figure 3B , Figure 4A , Figure 4B and Figures 5-13 Further details on the various techniques and aspects of this disclosure are provided.

[0041] Figure 2 This is a block diagram illustrating an example configuration of network entity 120 and UE 110. It should be noted that the depicted hardware configuration represents processing and communication components associated with providing CSI feedback based on one or more codebooks and corresponding power back-off values. Certain components that are well understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, etc., may be omitted from the depicted hardware configuration.

[0042] UE 110 includes an antenna 202, a radio frequency front-end (RF front-end) 204, and radio frequency transceivers (e.g., LTE transceiver 206 and 5G NR transceiver 208) for communicating with network entity 120.

[0043] The RF front end 204 includes one or more modems, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), signal processors, etc., configured for the corresponding RAT (e.g., 3GPP 5th Generation New Radio (5G NR)). Figure 2 In the example shown, the RF front-end 204 of UE 110 can couple or connect the LTE transceiver 206 and the 5G NR transceiver 208 to the antenna 202 to facilitate various types of wireless communication. The RF front-end 204 actually operates as a physical (PHY) transceiver interface to conduct and process signaling between one or more processors 214 and the antenna 202, thereby facilitating various types of wireless communication.

[0044] The antenna 202 of UE 110 may include an array of multiple antennas configured similarly or differently from each other, and may be tuned to one or more frequency bands associated with a corresponding RAT. The antenna 202 and RF front-end 204 may be tuned to and / or be able to be tuned to one or more frequency bands defined by the 2GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 206 and / or the 5G NR transceiver 208. Additionally, the antenna 202, RF front-end 204, LTE transceiver 206, and / or 5G NR transceiver 208 may be configured to support beamforming for use with network entity 120 and / or with one or more transmit / receive points (TRPs). Figure 2 The transmission and reception of communications (not shown in the diagram). By way of example and not limitation, antenna 202 and RF front end 204 can be implemented for operation in sub-gigahertz bands, sub-6 GHz bands and / or above 6 GHz bands as defined by 2GPP LTE and 5G NR communication standards.

[0045] UE 110 also includes processor 214 and computer-readable storage medium (CRM) 216. Processor 214 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs). For illustration, processor 214 may include an application processor (AP) used by UE 110 to execute an operating system and various user-level software applications, as well as one or more processors or a baseband processor of RF front end 204 utilized by a modem.

[0046] CRM 216 may include any suitable memory or storage device, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), flash memory, solid-state drive (SSD), or other high-capacity storage devices, which may be used to store one or more executable software instruction sets and associated data that manipulate one or more processors 214 and other components of UE 110 to perform the various functions described herein and belonging to UE 110. The executable software instruction sets include, for example, an operating system (OS) and various drivers (not shown) and various software applications (not shown), which may be executed by processor 214 to enable user plane communications, control plane signaling, and user interaction with UE 110. Data 218 stored in CRM 216 represents, for example, user data, multimedia data, software application configuration information, etc. Data 218 may include codebook entity 220 and CSI report configuration 219. Codebook entity 220 may be a codebook or subset thereof containing various beamforming vectors or MIMO precoding matrices. These beamforming vectors or MIMO precoding matrices can be used to adjust signals transmitted by the network entity and align the transmitted signals with the UE's antennas to attempt to optimize signal transmission and reception in a multi-antenna wireless communication system. The CSI report configuration may include one or more of the following parameters: ● A set of codebooks; ● A set of subsets of the codebook; ● A codebook, and a set of subsets of the codebook; ● A set of power back-off or power offset indicators for PDSCH based on the reported CSI; ● Indicates one or more waveform indicators for the target waveform of PDSCH based on the reported CSI; ● One or more CMRs; ● One or more IMRs; ● A rank-limiting indicator that indicates the number of candidate layers used for CSI feedback; ● A set of indicators for CQI table indication, wherein each indicator can indicate a CQI table for a codebook or a subset of the codebook; ● The number of CSI reports.

[0047] CRM 216 also includes a communication controller 222. Alternatively or additionally, the communication controller 222 may be implemented, in whole or in part, as a hardware logic or circuit system integrated or separate from other components of the UE 110. In some aspects, the communication controller 222 configures the RF front end 204, the LTE transceiver 206, and / or the 5G NR transceiver 208 to implement the techniques described herein for providing CSI feedback based on one or more codebooks and corresponding power back-off values.

[0048] When navigating to the hardware configuration of network entity 120, it should be noted that, although Figure 2 The implementation of network entity 120 is shown as a single network node (e.g., a 5G NR node B or "gNB"), but the functionality of network entity 120 and therefore its hardware components can be distributed across multiple network nodes or devices, and can be distributed in a manner used to perform the functions described herein. As an example, the functionality of network entity 120 can be distributed across radio units (RUs), distributed units (DUs), and / or central units (CUs).

[0049] Network entity 120 includes an antenna 252, a radio frequency front-end (RF front-end) 254, one or more LTE transceivers 256 and / or one or more 5G NR transceivers 258 for communicating with UE 110. The RF front-end 254 of network entity 120 can couple or connect the LTE transceivers 256 and 5G NR transceivers 258 to the antenna 252 to facilitate various types of wireless communication. Similar to RF front-end 204, RF front-end 254 includes one or more modems, one or more ADCs, one or more DACs, etc. RF front-end 254 receives one or more RF signals, such as RF signals from UE 110, and preprocesses the one or more RF signals to generate data from the RF signals, which is provided as input to processes and / or applications performed on network entity 120. Such preprocessing may include, for example, power amplification, conversion of band signaling to baseband signaling, initial analog-to-digital conversion, etc.

[0050] The antenna 252 of network entity 120 can be configured individually and / or configured as one or more arrays of multiple antennas. The antenna 252 and RF front-end 254 can be tuned to and / or are capable of being tuned to one or more frequency bands defined by the 3GPP LTE and 5G NR communication standards and implemented by the LTE transceiver 256 and / or the 5G NR transceiver 258. Additionally, the antenna 252, RF front-end 254, LTE transceiver 256, and / or 5G NR transceiver 258 can be configured to support beamforming, such as massive MIMO, for transmitting and receiving communications with UE 110.

[0051] Network entity 120 also includes processor 260 and computer-readable storage medium (CRM) 262. Processor 260 may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs). For illustration, processor 260 may include an application processor (AP) used by network entity 120 to execute an operating system and various user-level software applications, as well as one or more processors or a baseband processor of RF front-end 254 utilized by a modem to enable communication with UE 110.

[0052] CRM 262 may include any suitable memory or storage device that can be used to store device data of network entity 120, such as random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or flash memory. Device data may include data 264, which includes network scheduling data, radio resource management data, software application configuration information, etc. Data 264 may further include codebook entity 261 and CSI report 263. Similar to codebook entity 220 described above, codebook entity 261 may be a codebook or a subset of a codebook. CSI report 263 may be a report received from the UE that provides CSI feedback information on channel quality and channel conditions, which the network entity can use to adjust signal transmission parameters to improve network performance.

[0053] CRM 262 also includes an RF resource manager 265. In some aspects, the RF resource manager 265 of network entity 120 is implemented to perform various functions associated with allocating physical access (e.g., resource blocks) or communication resources for the air interface of network entity 120. The air interface of network entity 120 may be partitioned or divided into various units (e.g., frames, subframes, or time slots) of one or more of bandwidth, time, symbol, or spatial layers. For example, within the framework of the 5G NR protocol, the RF resource manager 265 may allocate bandwidth and access time intervals within resource blocks, each resource block may be allocated wholly or partially to one or more channels for communication with UE 110. Channels may include one or more of PRACH, PUCCH, PUSCH, PDCCH, PDSCH, PBCH, or paging channels. A resource block may include multiple subcarriers, each subcarrier spanning a portion of the frequency domain of the resource block. Subcarriers may be further divided into resource elements or Orthogonal Frequency Division Multiplexing (OFDM) symbols, each resource element or OFDM symbol spanning a portion of the time domain of the subcarrier. Therefore, a resource block comprises multiple OFDM symbols, which can be grouped into subcarriers together with other OFDM symbols that share a common frequency bandwidth.

[0054] CRM 262 further includes a network entity manager 266. Alternatively or additionally, the network entity manager 266 may be implemented wholly or partially as a hardware logic or circuit system integrated or separate from other components of the network entity 120. In at least some aspects, the network entity manager 266 configures an LTE transceiver 256 and a 5G NR transceiver 258 for communication with the UE 110 and with the core network 150. Figure 1 ).

[0055] In some aspects, network entity 120 includes an Internetwork Entity Interface 268, such as an Xn and / or X2 interface, which network entity manager 266 configures to exchange user plane and control plane data between another network entity to manage communication between network entity 120 and UE 110. Network entity 120 includes a core network interface 270, which network entity manager 266 configures to exchange user plane and control plane data with core network functions and entities.

[0056] As discussed above, network entity 120 may utilize different waveforms and precoders for PDSCH transmission depending on the wireless network conditions. In some aspects, network entity 120 may utilize a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform to transmit PDSCH. In other aspects, to reduce the peak-to-average power ratio (PAPR) and provide high power amplifier efficiency, network entity 120 may utilize a discrete Fourier transform extended orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, a single-carrier frequency division multiple access (SC-FDMA) waveform, or other single-carrier waveforms to transmit PDSCH. In some implementations, a low PAPR waveform refers to a waveform associated with a PAPR below a threshold decibel (dB) level (e.g., a PAPR lower than that of a CP-OFDM waveform). Different types of precoders and different waveforms can produce different PAPRs. Similarly, different types of precoders and different waveforms can result in different downlink transmit power backoff values. Figure 3A and Figure 3B This illustrates different example antenna port mappings and their associated precoder types used by network entity 120 when transmitting PDSCH using a DFT-s-OFDM waveform. Figure 3A and Figure 3B In the example shown, the set 352 of antenna ports can be mapped to different beamforming layers. The set 352 of antenna ports can represent some or all of the antennas in the antennas 252 of network entity 120.

[0057] The following discussion Figure 3A , Figure 3B , Figure 4A , Figure 4B and Figures 5-13 Various techniques and examples for providing CSI feedback based on one or more codebooks and corresponding power back-off values ​​are illustrated. In some of the examples below, the operation can be described as utilizing RRC signaling. Unless otherwise stated, RRC signaling can instruct an RRC reconfiguration message from a network entity to the UE, or a System Information Block (SIB), where the SIB can be an existing SIB (e.g., SIB1) or a new SIB sent by the network entity (e.g., SIB2). J ,in J (It is an integer greater than 21).

[0058] Figure 3A This is an illustration of antenna port configuration 300 for PDSCH transmission using a Type 1 precoder. A Type 1 precoder is a type of precoder in which different beamforming layers are mapped to different antenna ports. In some aspects, network entity 120 may select a digital precoder, where one beamforming layer 306 is mapped to two antenna ports 304. Here, an "X" configuration indicates two antenna ports from two different polarizations (e.g., +45 degrees and -45 degrees). For example, layer 306A is mapped to two antenna ports 304A, layer 306B is mapped to two other antenna ports 304B, and so on. In other words, every two antenna ports 304 are mapped to a different layer 306.

[0059] Figure 3B This illustration shows antenna port configuration 320 for PDSCH transmission using a Type 2 precoder. A Type 2 precoder is a type of precoder in which different beamforming layers are mapped to partially or fully overlapping antenna ports. In some aspects, network entity 120 can select precoders where each beamforming layer 306 can be mapped to more than one antenna port 304. In other words, the precoder can map different layers 306 to partially or fully overlapping antenna ports 304. Such mapping can provide more than... Figure 3A The diagram shows a better precoding gain mapping from one layer to multiple antenna ports. Figure 3B In the example shown, each layer 306 is mapped to each antenna port in antenna port 304. For example, each layer in layers 306A-306D is mapped to each antenna port in antenna ports 304A-304D. Here, the "X" configuration represents two antenna ports from two different polarizations (e.g., +45 degrees and -45 degrees).

[0060] Different combinations of waveforms and antenna port-to-layer mappings can produce different PAPRs. As an example, consider two waveforms, CP-OFDM and DFT-s-OFDM, where the antenna ports transmitting these waveforms can be mapped to one or four layers. Compared to other waveforms in the example, the CP-OFDM waveform where the antenna port is mapped to four layers can produce a relatively high PAPR. The CP-OFDM waveform where one antenna port is mapped to one layer can produce a slightly lower PAPR than the CP-OFDM waveform where one antenna port is mapped to four layers. The DFT-s-OFDM waveform where the antenna port is mapped to four layers can produce a lower PAPR than either of the CP-OFDM waveforms. Compared to other waveforms, the DFT-s-OFDM waveform where the antenna port is mapped to one layer can produce a relatively low PAPR.

[0061] Figure 4A This is a sequence diagram illustrating example operations for providing CSI feedback based on one or more codebooks and corresponding power back-off values, where the UE selects a codebook. Although not shown for clarity, it is possible to implement... Figure 4A The various confirmations of the messages shown are to ensure reliable operation for providing CSI feedback based on one or more codebooks and the power backoff value corresponding to those codebooks.

[0062] At operation 402, UE 110 may send or report to network entity 120 its capability to provide CSI feedback based on one or more codebooks and corresponding power backoff values. In some aspects, UE 110 may transmit UE capability information to network entity 120 during the initial communication session establishment process between UE 110 and network entity 120. UE capability information may include supported frequency bands, radio access technologies, maximum transmit power, maximum data rate, and network protocols. In some implementations, UE 110 may report UE capability information indicating whether UE 110 supports CSI feedback based on one or more codebooks and corresponding power backoff values, the maximum number of codebooks or subsets of codebooks supported in the CSI reporting configuration with different power backoffs or power offsets between PDSCH and CSI-RS, and the maximum number of CSIs reported for CSI reporting. In some implementations, the UE capability information may include an indication of support for CMRs configured with different numbers of ports, different bandwidths, different subcarriers, different periodicities, and / or different TCI states associated with different codebooks or subsets of codebooks. In some other implementations, the UE includes in its capability information an indication of whether it supports different codebooks corresponding to different waveforms in the CSI report configuration.

[0063] exist Figure 4A In the example, UE 110 sends UE capability information to network entity 120. In some implementations, the network entity can send this information from the core network (e.g., from...). Figure 1 The core network 150 receives UE capabilities from the Access and Mobility Management Function (AMF). In some other implementations, the network entity receives UE capabilities from another network entity (e.g., a gNB or eNB).

[0064] At operation 404, network entity 120 can configure at least one CSI report configuration, including multiple codebooks or subsets of codebooks (collectively, "codebook entities"), based on the UE capability information received at operation 402, wherein different codebooks or subsets of codebooks correspond to different power back-offs or power offsets. (See above regarding...) Figure 2 The CSI report configuration discussed in section 219 may include one or more of the following parameters: ● A set of codebooks; ● A codebook, and a set of subsets of the codebook; ● A set of subsets of the codebook; ● A set of power back-off or power offset indicators for PDSCH based on the reported CSI; ● Indicates one or more waveform indicators for the target waveform of PDSCH based on the reported CSI; ● One or more CMRs; ● One or more IMRs; ● A rank-limiting indicator that indicates the number of candidate layers used for CSI feedback; ● A set of indicators for CQI table indication, wherein each indicator can indicate a CQI table for a codebook or a subset of the codebook; ● The number of CSI reports.

[0065] In some aspects, network entity 120 can communicate via control signaling through RRC signaling (e.g., RRCReconfiguration or CSI-ReportConfig To send CSI reports, network entity 120 can configure the CSI report sending process. In some aspects, network entity 120 can configure the CSI report sending process, for example... CSI-ReportConfig allows you to configure multiple CSI report sub-configurations.For example, network entity 120 can configure one or more of the above parameters in one CSI reporting sub-configuration, and configure one or more other parameters in different CSI reporting sub-configurations. Therefore, network entity 120 can configure at least one parameter in each CSI reporting sub-configuration, including codebooks, codebook subsets, power back-off or power offset indicators, waveform indicators, CMR, IMR, and CQI table indicators. In some aspects, one or more of these parameters may be predefined (e.g., the number of reported CSIs is 1) or the same as another parameter. For example, the number of reported CSIs may be the same as the number of configured codebooks or codebook subsets.

[0066] In some aspects, network entity 120 may include power back-off or power offset indicators for CQI corresponding to different modulation orders in the CSI reporting configuration. For example, network entity 120 may configure higher power back-off or power offset for CQI at higher modulation orders. In some aspects, the power back-off or power offset for CQI corresponding to different modulation orders may be predefined.

[0067] In some aspects, network entity 120 may include an indication of a common CMR for all configured codebooks or subsets of codebooks in the CSI report configuration. In other aspects, network entity 120 may send a CSI report configuration indicating individual CMRs for different configured codebooks or subsets of codebooks. In such aspects, network entity 120 may configure CMRs for different codebooks or subsets of codebooks with the same number of ports, the same bandwidth, the same subcarriers, the same periodicity, and / or the same Transmit Configuration Indication (TCI) state for Quasi-Co-bit (QCL) indication. In such aspects, UE 110 may therefore not expect the CMRs for different codebooks or subsets of codebooks to be configured with different numbers of ports, different bandwidths, different subcarriers, different periodicity, and / or different TCI states. In other aspects, UE capability information may, as described above with respect to operation 402, indicate that UE 110 supports CMRs configured with different numbers of ports, different bandwidths, different subcarriers, different periodicity, and / or different TCI states for different codebooks or subsets of codebooks.

[0068] In some aspects, network entity 120 can configure waveform indicators in the CSI report configuration by configuring codebook types. For example, different types of codebooks can be predefined for different waveforms. Network entity 120 can include codebook types in the CSI report configuration, which will then also indicate the waveform corresponding to that codebook type.

[0069] In some other implementations, network entity 120 may avoid including codebooks corresponding to different waveforms in the CSI report configuration. Therefore, in such implementations, UE 110 may not expect network entity 120 to configure codebooks corresponding to different waveforms in the CSI report configuration.

[0070] In some implementations, network entity 120 includes the same number of horizontal and vertical antenna ports for the configured codebook in the CSI report configuration. In some implementations, the network entity may include orthogonal codebooks or subsets of codebooks for different waveforms and / or different power backoffs or power offsets in the CSI report configuration.

[0071] In some implementations, network entity 120 includes a common CQI table in the CSI reporting configuration for CQI measurement and reporting for a configured codebook or subset of codebooks. In other implementations, network entity 120 includes indications of separate CQI tables in the CSI reporting configuration for CQI measurement and reporting for each configured codebook or subset of codebooks. In some aspects, candidate CQI tables may be similar to those defined in 3GPP Technical Specification (TS) 38.214.

[0072] At operation 406, network entity 120 may trigger UE 110 to provide a CSI report according to the CSI report configuration provided to UE 110 at operation 404. For example, network entity 120 may trigger a semi-persistent CSI report or an aperiodic CSI report. In some aspects, network entity 120 may send a MAC CE or DCI to activate or trigger the CSI report. In some aspects, network entity 120 may provide one or more parameters from the CSI report configuration parameters described above with respect to operation 404 by triggering the MAC CE or DCI for the CSI report. For example, the network entity may provide parameters such as waveform indicators or the number of reported CSIs by using the MAC CE or DCI.

[0073] At operation 408, network entity 120 may send the CMR configured in the CSI report configuration at operation 404. In some aspects, if the CSI report configuration received at operation 404 includes an IMR, then network entity 120 may also send an IMR in addition to the CMR.

[0074] At operation 410, UE 110 measures CSI for some or all of the codebooks or subsets of codebooks configured in the CSI reporting configuration, based on CMR (and optionally IMR).

[0075] At operation 412, UE 110 can select a codebook or a subset of codebooks from those configured in the CSI report configuration based on the CSI measurement obtained at operation 410. In some aspects, UE 110 selects a codebook or a subset of codebooks associated with the highest spectral efficiency (SE). As an example, UE 110 can indicate in its UE capability information that it is capable of selecting a codebook or a subset of codebooks. Network entity 120 can configure UE 110 to perform such a selection in the CSI report configuration.

[0076] At operation 414, UE 110 may send a CSI report corresponding to the configured CSI report interval, or send a CSI report as a CSI triggered at operation 406. In some aspects, the CSI report provides CSI information about the codebook or codebook entity selected at operation 412 and is configured according to the CSI report received at operation 404.

[0077] Figure 4B This is a sequence diagram illustrating example operations for providing CSI feedback based on one or more codebooks and corresponding power back-off values, where the UE provides multiple CSIs to a network entity. Although not shown for clarity, it is possible to implement... Figure 4B The various confirmations of the messages shown are to ensure reliable operation for providing CSI feedback based on one or more codebooks and the power backoff value corresponding to those codebooks.

[0078] The operation of communication process 420 is similar to the above. Figure 4A The operation of the described communication process 400 is similar. The difference is that instead of UE 110 selecting a codebook or codebook set for reporting CSI feedback, UE 110 reports CSI feedback for multiple codebooks or subsets of codebooks. Therefore, in some aspects, Figure 4B Operations 402-412 are related to the above. Figure 4A The operations described in 410-412 are the same or substantially similar.

[0079] At operation 416, UE 110 sends a CSI report to network entity 120. In some aspects, the CSI report includes CSIs for some or all of the codebooks and / or subsets of codebooks configured in the CSI report configuration received at operation 404. Different CSIs in the CSI report may correspond to different codebooks and / or subsets of codebooks in the CSI report.

[0080] Figure 5 This is a flowchart illustrating an example UE operation for providing CSI feedback based on one or more codebooks and corresponding power back-off values. The example operation of method 500 can be, for example, by... Figure 1 , Figure 2 , Figure 4A and Figure 4B UE 110 execution.

[0081] At box 502, and as mentioned above... Figure 4A and Figure 4B As described in operation 402, the UE may send UE capability information to a network entity. In some aspects, the UE 110 may send UE capability information including at least one of the following: a first indicator indicating support for providing CSI feedback based on one or more codebook entities and power relationship indicators corresponding to the one or more codebook entities; a maximum number of codebook entities with different power relationship indicators; a maximum number of CSI reports for at least one CSI report; a number of CSI processing units (CPUs) for at least one CSI report; or a second indicator indicating the minimum processing latency for at least one CSI report. For example, the UE 110 may report UE capability information indicating whether the UE 110 supports CSI feedback based on one or more codebooks and power backoff values ​​corresponding to the codebooks, and information related to such support.

[0082] At box 504, and as per the information provided... Figure 4A and Figure 4B As described in operation 404, UE 110 may receive at least one CSI report configuration comprising multiple codebook entities, wherein different codebooks or subsets of codebooks correspond to different power back-offs or power offsets. In some aspects, UE 110 may receive at least one CSI report configuration comprising: multiple codebook entities (e.g., codebooks or subsets of codebooks), one or more power relationship indicators (e.g., power back-off or power offset indicators) indicating the power relationship between the PDSCH and CSI-RS for each of the multiple codebook entities, and one or more CMRs associated with the CSI-RS.

[0083] In some other aspects, the at least one CSI reporting configuration further includes at least one of the following: at least one waveform indicator indicating the target waveform for the PDSCH based on the reported CSI; at least one IMR; a rank-limiting indicator indicating the number of candidate layers for CSI feedback; a first CQI table indicator indicating a common or individual CQI table for multiple codebook entities; a second CQI table indicator indicating an individual CQI table for each of the multiple codebook entities; an indicator indicating the number of reported CSIs; a configuration of power relationship indicators for CQIs corresponding to different modulation orders; one or more common CMRs for multiple codebook entities; or one or more individual CMRs for multiple codebook entities.

[0084] In some aspects, the target waveform includes at least one of the following: CP-OFDM waveform, DFT-s-OFDM waveform, or SC-FDMA waveform.

[0085] At box 506, and as about Figure 4A and Figure 4B As described in operation 406, UE 110 may receive an indication (e.g., "trigger") that UE 110 intends to provide a CSI report based on the CSI report configuration received by UE 110 at block 504. In addition to receiving this indication to provide a CSI report, UE 110 may also receive one or more parameters from the CSI report configuration parameters described above by activating or triggering the MAC CE or DCI for CSI reporting. For example, the UE may receive parameters such as waveform indicators or the number of reported CSIs via the MAC CE or DCI.

[0086] At box 508, and as about Figure 4A and Figure 4B As described in Operation 408, UE 110 can receive CMRs configured in the CSI Report Configuration from a network entity. In some aspects, UE 110 can receive one or more CMRs associated with the CSI-RS. In some aspects, if an IMR is included in the CSI Report Configuration, UE 110 can also receive an IMR in addition to the CMRs. In some aspects, UE 110 can receive multiple CMRs, each of which has the same value for at least one of the following: the number of antenna ports; bandwidth; subcarrier configuration; periodicity; or transmission configuration indication (TCI) status.

[0087] At box 510, and as about Figure 4A and Figure 4BAs described in operation 410, UE 110 measures CSI for some or all of the codebooks or subsets of codebooks configured in the CSI reporting configuration based on CMR (and optionally IMR). In some aspects, UE 100 may calculate CSI for at least one CSI report based on at least one of the following: a codebook entity among a plurality of codebook entities; a power relationship indicator for a codebook entity among a plurality of codebook entities; a target waveform for a codebook entity among a plurality of codebook entities; or a rank constraint for a codebook entity among a plurality of codebook entities.

[0088] In some respects, at box 512, and as about Figure 4A As described in operation 412, UE 110 may optionally select a codebook or a subset of codebooks from those configured in the CSI report configuration, wherein the selection of a codebook or subset of codebooks may be based on the CSI measurement obtained at block 510. In some aspects, UE 110 selects the codebook or subset of codebooks associated with the highest SE.

[0089] At box 518, and as mentioned above... Figure 4A Operation 414 and Figure 4B As described in operation 416, UE 110 sends a CSI report to a network entity. In some aspects, UE 110 may send at least one CSI report based on at least one CSI report configuration and one or more CMRs. In some aspects, UE 110 sends a CSI report containing information about a codebook or codebook entity optionally selected by the UE at block 512. In some aspects, UE 110 sends a CSI report including CSIs for some or all of the codebooks and / or subsets of codebooks configured in the CSI report configuration.

[0090] In some aspects, UE 110 may send at least one CSI report having at least one of the following: a subset of measured CSIs in the at least one CSI report; a first indicator indicating the number of reported CSIs; a second indicator indicating a codebook entity among a plurality of codebook entities for each reported CSI; all measured CSIs in the at least one CSI report; an RI for each CSI in the at least one CSI report; a PMI for each CSI in the at least one CSI report; a CQI for each CSI in the at least one CSI report; an LI for each CSI in the at least one CSI report; a common RI for all reported CSIs; or at least one of a common RI, a common PMI, or a common LI based on a codebook entity among a plurality of codebook entities and the CQI for each CSI in the at least one CSI report.

[0091] In some other respects, UE 110 may avoid sending CSI reports when the number of CPUs occupied in or across component carriers (CCs) exceeds the maximum number of CPUs. In still other respects, UE 110 may avoid sending CSI reports when the scheduling offset for a CSI report is less than the minimum processing delay.

[0092] Figure 6 This is a flowchart illustrating example network entity operations for receiving CSI feedback based on one or more codebooks and corresponding power backoff values. The example operations of method 600 can be, for example, performed by... Figure 1 , Figure 2 , Figure 4A and Figure 4B Network entity 120 executes.

[0093] At box 602, and as mentioned above... Figure 4A and Figure 4B As described in operation 402, the network entity can receive UE capability information from the UE. For example, the network entity can receive UE capability information indicating whether the UE supports providing CSI feedback based on one or more codebooks and corresponding power backoff values. In some aspects, network entity 120 can receive UE capability information including information about... Figure 5 Similar UE capabilities to those described in Operation 502.

[0094] At box 604, and as about Figure 4A and Figure 4B As described in operation 404, the network entity may send at least one CSI report configuration to the UE, comprising multiple codebook entities, wherein different codebooks or subsets of codebooks correspond to different power back-offs or power offsets. The network entity may include CMRs and optionally IMRs in the CSI report configuration. In some aspects, the network entity may send at least one CSI report configuration comprising: multiple codebook entities (e.g., codebooks or subsets of codebooks), one or more power relationship indicators (e.g., power back-off or power offset indicators) indicating the power relationship between the PDSCH and CSI-RS for each of the multiple codebook entities, and one or more CMRs associated with the CSI-RS. In some other aspects, the at least one CSI report configuration further includes information regarding... Figure 5 The operation 504 describes similar parameters.

[0095] At box 606, and as about Figure 4A and Figure 4BAs described in operation 406, the network entity may send an indication (e.g., "trigger") that the UE wants to provide a CSI report according to the CSI reporting configuration provided to the UE at block 604. In addition to sending the indication that the UE wants to provide a CSI report, the network entity may also send one or more CSI reporting configuration parameters described above in the MAC CE or DCI used to trigger the CSI report. For example, the network entity may send parameters such as waveform indicators or the number of CSIs to be reported.

[0096] At box 608, and as about Figure 4A and Figure 4B As described in operation 408, the network entity may send the CMR configured in the CSI report configuration to the UE. In some aspects, the network entity may send one or more CMRs associated with the CSI-RS. In some aspects, if an IMR is included in the CSI report configuration, the network entity may also send an IMR in addition to the CMR. In some aspects, the network entity 120 may send multiple CMRs, each of which has the same value for at least one of the following: the number of antenna ports; bandwidth; subcarrier configuration; periodicity; or TCI state.

[0097] At box 618, and as mentioned above... Figure 4A Operation 414 and Figure 4B As described in operation 416, the network entity receives a CSI report from the UE. In some aspects, the network entity may receive at least one CSI report based on at least one CSI report configuration and one or more CMRs. In some aspects, the network entity receives a CSI report having information about a codebook or codebook entity selected by the UE. In some aspects, the network entity receives a CSI report including CSI feedback for some or all of the codebooks and / or codebook subsets configured in the CSI report configuration. The network entity may select an appropriate codebook or codebook subset based on the CSI feedback. In some aspects, network entity 120 may receive at least one CSI report having information about... Figure 5 Operation 518 describes a similar CSI component.

[0098] Figures 7-13 Examples of CSI feedback that can be provided by the UE in various scenarios involving different CSI reporting configurations, codebooks, and subsets of codebooks are provided. Figures 7-13 The examples provided are just a few of the many different possible combinations of CSI report configuration, codebook, and codebook offset.

[0099] Figure 7This is an illustration of an example of CSI feedback using waveform and power backoff-aware codebooks. In some aspects, the network entity provides the UE with a set of codebooks 704, where power backoff or power offset indicators are specific to each configured codebook. Figure 7 In the example shown, the network entity has configured three codebooks 704A-704C. Based on the waveform and CMR associated with the respective codebook, each codebook 704A-704C can generate different measured CSI 706A-706C. In this example, the network entity has configured a power back-off or power offset indicator for each codebook 704A-704C. For example, codebook 704A includes a power back-off / offset indicator 1 indicating 0dB back-off, codebook 704B includes a power back-off / offset indicator 2 indicating 3dB back-off or offset, and codebook 704C has a power back-off / offset indicator 3 indicating 6dB power back-off or offset. In some other aspects, the network entity can configure N codebooks and N power back-off or power offset indicators, and the power back-off indicator or offset can be mapped one-to-one with the codebook. In some aspects, each codebook 704 can specify one type of precoder, but different codebooks can specify precoders of different types from each other.

[0100] In some aspects, for a codebook with a Type 2 precoder, the network entity can provide the UE with a codebook 704 specifying a common or separate power back-off or power offset indicator, where an antenna port in each codebook can be mapped to a different number of layers. For example, the network entity can provide separate power back-off or power offset indicators for the Type 2 precoder. As an example, one antenna port can be mapped to two layers, another antenna port can be mapped to three layers, a further antenna port can be mapped to four layers, and so on. Furthermore, a layer can be mapped to one or more antenna ports.

[0101] In some aspects, network entities can configure common or individual waveform indications for each codebook 704. Figure 7 In the example shown, codebooks 704A and 704B have a common waveform indication for DFT-s-OFDM, while codebook 704C has a separate waveform indication for CP-OFDM. This facilitates compatibility with UE implementations that can apply different receivers to receive PDSCHs with different waveforms.

[0102] In some aspects, the network entity can configure a common rank limit indicator for each codebook 704. In other aspects, the network entity can configure an individual rank limit indicator for each codebook 704. In still other aspects, the network entity can configure individual rank limit indicators for different waveforms.

[0103] In some aspects, the network can configure codebook parameters in the CSI sub-configuration within the CSI report configuration.

[0104] Figure 8 This is an illustration of an example of CSI feedback using waveform and power backoff-aware codebook subsets. In some aspects, the network entity provides the UE with a codebook 802 having a set of codebook subsets 804 and a power backoff or power offset indicator for each configured codebook subset 804. Figure 8 In the example shown, codebook 802 includes three codebook subsets 804A-804C. Based on the CMR and waveform associated with the respective codebook subset, each codebook subset 804A-804C can generate different measured CSI 706A-706C. In some aspects, the network entity configures a power back-off or power offset indicator in the configuration of each codebook subset 804. In this example, the network entity has configured a power back-off or power offset indicator in each codebook subset 804A-804C. For example, codebook subset 804A includes a power back-off / offset indicator 1 indicating 0dB back-off, codebook subset 804B includes a power back-off / offset indicator 2 indicating 3dB back-off or offset, and codebook subset 804C has a power back-off / offset indicator 3 indicating 6dB power back-off or offset. In some other aspects, the network entity configures N codebook subsets and N power backoff or power offset indicators that can be mapped one-to-one with each codebook subset 804. In some implementations, each codebook subset 804 can specify only one type of precoder.

[0105] In some aspects, for a codebook subset 804 with a Type 2 precoder, the network entity can provide the UE with a codebook subset 804 having common or separate power back-off or power offset indicators for the precoder, where one antenna port can be mapped to a different number of layers. For example, the network entity can provide separate power back-off or power offset indicators for the precoder. As an example, one antenna port can be mapped to two layers, another antenna port can be mapped to three layers, a further antenna port can be mapped to four layers, and so on.

[0106] In some aspects, network entities can configure common or separate waveform indications for each codebook subset 804. Figure 8 In the example shown, codebook subsets 804A and 804B have a common waveform indication for DFT-s-OFDM, while codebook subset 804C has a separate waveform indication for CP-OFDM. This facilitates compatibility with UE implementations that can apply different receivers to different waveforms. For example, the UE can apply a receiver corresponding to a waveform when measuring its CQI.

[0107] In some aspects, the network entity configures a common rank constraint indicator for codebook subset 804. In other aspects, the network entity configures separate rank constraint indicators for different waveforms. In still other aspects, the network entity configures separate rank constraint indicators for different codebook subsets 804. In some aspects, the codebook subset for CP-OFDM waveforms can be the same as the codebook subset with a Type 2 precoder for DFT-s-OFDM waveforms.

[0108] Figure 9 This is an illustration of an example of CSI feedback using waveform-specific codebooks and power back-off-aware codebook subsets. In some aspects, the network entity configures sets of codebooks 902A and 902B, where each codebook corresponds to a different waveform, and configures a set of codebook subsets 904A-904C for at least one of the configured codebooks. Additionally, the network entity configures a power back-off or power offset indicator for each configured codebook subset. Figure 9 In the example shown, the network entity has configured a first codebook 902A with codebook subsets 904A and 904B that share the same waveform indication (e.g., DFT-s-OFDM). Additionally, the network entity has configured a codebook 902B with a codebook subset 904C that has a different waveform indication (e.g., CP-OFDM) than codebook subsets 904A and 904B. In some aspects, the network entity configures a power back-off or power offset indicator in the configuration of each codebook subset. In some other aspects, the network entity configures N codebook subsets and N power back-off or power offset indicators that can be mapped one-to-one with each codebook subset. In some aspects, each codebook subset can specify only one type of precoder. Based on the CMR and waveform associated with the respective codebook subset, each codebook subset 904A-904C can produce different measured CSI 706A-706C.

[0109] In some aspects, for a codebook subset with a Type 2 precoder, the network entity can configure the UE with a codebook subset having common or separate power back-off or power offset indicators, where each antenna port can be mapped to a different number of layers than the other antenna ports. For example, the network entity can provide separate power back-off or power offset indicators for the precoder. As an example, one antenna port can be mapped to two layers, another antenna port can be mapped to three layers, a further antenna port can be mapped to four layers, and so on.

[0110] In some aspects, the network entity can configure a codebook subset with a common rank constraint indicator. In other aspects, the network entity can configure a codebook subset with separate rank constraint indicators for different waveforms. In still other aspects, the network entity can configure separate rank constraint indicators for different codebook subsets. In some aspects, the codebook subset indicating the CP-OFDM waveform can be configured to be the same as or similar to the codebook subset indicating the Type 2 precoder for the DFT-s-OFDM waveform.

[0111] Figure 10-13 Various example CSI reports that can be generated by the UE and sent to network entities are shown. These various CSI reports are based on... Figure 7 The codebooks 704A-704C and the CSI measurements associated with the waveform, which are associated with the codebook.

[0112] Figure 10 This is an illustration of example 1000 of a codebook selected by the UE for CSI feedback. In some aspects, the UE sends a CSI report 1002 based on a CSI report configuration received from a network entity. The CSI report 1002 may include at least one CSI based on a configured codebook or subset of codebooks and its corresponding power back-off or power offset. Figure 10 In the example shown, the UE has selected codebook 704B and its associated measurement CSI 706B for reporting. CSI report 1002 includes an indicator of codebook 704B and at least one of RI, PMI, CQI, or LI from measurement CSI 706B.

[0113] In some aspects, network entities can configure the number of CSIs reported. In others, UE reports an indicator of the number of CSIs reported. Network entities can configure the maximum number of CSIs reported. In still others, the number of CSIs reported can be predefined, for example, one (“1”).

[0114] In some aspects, when reporting multiple CSIs, the UE may report an indicator indicating whether the CSI is based on a codebook or subset of codebooks selected by the UE. Where the UE reports the CSI on a PUSCH or a long PUCCH (e.g., a PUCCH with more than four symbols), the UE may report the selection indicator in CSI section 1. Alternatively, the UE may report the selection indicator in CSI section 2. CSI sections 1 and 2 are defined in 3GPP TS 38.212. In some other aspects, the UE may report a first indicator indicating the codebook selected by the UE and a second indicator indicating a subset of the codebook selected for the UE's chosen codebook. The UE may further report at least one of the RI, PMI, CQI, and LI of the CSI (e.g., CSI 706B) of the measurement corresponding to the UE's chosen codebook or subset of codebooks.

[0115] In some aspects, the UE may report a selection indicator that indicates the UE's selection of a codebook or a subset of codebooks for the entire bandwidth associated with the CSI measurement. In other aspects, the UE may report a selection indicator that indicates the UE's selection of a codebook or a subset of codebooks for the entire bandwidth associated with each subband, which is associated with the CSI measurement.

[0116] In some aspects, if a network entity configures separate CMRs or CMR sets for different codebooks or subsets of codebooks, the UE reports an index of the CMR or CMR set of the selected codebook or subset of codebooks.

[0117] In some aspects, the UE can select the CSI for reporting based on the measured spectral efficiency (SE). For example, the UE can report the CSI with the highest SE. If the SE is the same for some CSIs, the UE can report the CSI with the highest power backoff for network energy saving.

[0118] Figure 11 , Figure 12 and Figure 13 Various example configurations for CSI reporting are illustrated, including example reports with individual CSI values ​​for each CSI and example reports with common CSI values ​​for some of the reported CSIs. In some aspects, network entities can configure whether the UE reports common or individual CSI values. For example, network entities can configure whether the UE reports common or individual RI, PMI, and / or LI for each CSI.

[0119] Figure 11This is an illustration of an example CSI report 1100 with individual CSIs for each configured codebook. In some aspects, the UE sends a configured CSI report that includes CSIs for all configured codebooks and their corresponding power back-offs or power offsets, where each CSI is based on a configured codebook or subset of codebooks and its corresponding power back-off or power offset. Figure 11 In the example shown, CSI report 1102 includes measurements from each of the CSIs 1106A-1106C associated with the configured codebooks 704A-704C. The network entity can select the waveform and precoder corresponding to the selected CSI in the reported CSI.

[0120] In some aspects, the UE can report at least one of the RI, PMI, CQI, and LI for each CSI based on the corresponding codebook or subset of the codebook for each CSI, as well as power back-off or power offset. Figure 11 In the example shown, the UE reports individual RI, PMI, and / or CQI for each CSI in CSI report 1102.

[0121] Figure 12 This is an illustration of an example CSI report 1200 with a common RI for a configured codebook. In some other aspects, the UE can report a common RI for all CSIs, as well as separate PMI, CQI, and / or LI for each reported CSI. Figure 12 In the example shown, the RI measured for each CSI in CSI 1206 is the same, for example, one (“1”). CSI report 1202 includes a single public RI for the reported CSI as well as individual PMI and / or individual CQI for each reported CSI.

[0122] Figure 13 This is an illustration of an example CSI report 1300 with RI or PMI for a configured codebook. In some aspects, the UE may report the RI, PMI, and / or LI for one CSI corresponding to a codebook or subset of codebooks, and report a separate CQI for each reported CSI. Figure 13In the example shown, CSI report 1302 includes separate CQIs for codebooks 704A and 704B based on measured CSIs 1306A and 1306B, respectively. CSI report 1302 includes RI, PMI, and / or CQI for codebook 704C based on measured CSI 1306C. The separately reported codebooks or subsets of codebooks can be predefined, for example, codebooks or subsets of codebooks for Type 2 precoders or for precoders used for CP-OFDM waveforms. Additionally, codebooks or subsets of codebooks can be configured by network entities. Furthermore, in addition to CSI values, codebooks or subsets of codebooks can also be reported by the UE. In some aspects, the UE can measure the CQI based on the reported RI and the precoder selected by the UE from the corresponding codebook for each CSI.

[0123] When implementing the techniques described herein, there may be considerations regarding UE complexity and reporting time. For example, in some cases, reducing UE complexity may be advantageous. Furthermore, in some cases, minimizing reporting time may be advantageous.

[0124] In some aspects, UE complexity can be influenced by the number of CSI processing units (CPUs). In some aspects, network entities and the UE determine the number of CPUs used for CSI reporting based on the number (N) of configured codebooks or subsets of codebooks and / or the number (K) of CSI resources configured for CMR. In some aspects, network entities and the UE may determine the number of CPUs as NK+M, where M indicates the additional CPUs used for CSI processing (e.g., CSI comparison of CSI from configured codebooks or subsets of codebooks). In some other aspects, network entities and the UE may determine the number of CPUs as ceil(RNK)+M, where R is in the range (0,1), and this value may be predefined or reported by the UE as part of UE capability information. In some aspects, M may be predefined, for example, M=0. In some aspects, M may be reported as part of UE capability information.

[0125] In some aspects, if the number of CPUs used for CSI reporting in a component carrier (CC) or across all configured CCs exceeds the maximum number of CPUs the UE reports in the UE capability information, the UE may report outdated CSIs for CSI reporting or may avoid sending CSI reports.

[0126] In some aspects, network entities and UEs can determine the minimum processing delays Z and Z' for a CSI report based on the number (N) of configured codebooks or subsets of codebooks and / or the number (K) of CSI resources configured as CMRs, where Z indicates the minimum offset between the last symbol of the PDCCH that schedules the CSI report and the first symbol of the PUSCH or PUCCH that has the CSI report, and Z' indicates the minimum value between the last symbol of the last CMR / IMR and the first symbol of the PUSCH or PUCCH that has the CSI report.

[0127] For example, in some aspects, network entities and UEs may determine the minimum processing delay as Z=ZxNK and Z'=Zx'NK, where Zx and Zx' are Z2 and Z2' or Z3 and Z3' as defined in 3GPP TS 38.214. In some other aspects, network entities and UEs may determine the minimum processing delay as Z=ZxN and Z'=Zx'N. In still other aspects, network entities and UEs may determine the minimum processing delay as Z=Zx+r and Z'=Zx'+r, where r may be predefined or reported by the UE via UE capability information. In yet another aspect, network entities and UEs may determine the minimum processing delay as Z=ZxN+r and Z'=Zx'N+r. If the scheduling offset for the CSI report is less than the minimum processing delay, the UE may report an outdated CSI or may avoid sending a CSI report.

[0128] It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X or Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and Y". It should be noted that throughout this disclosure, the expression "X / Y" can include the meaning of "X and / or Y". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "B only". It should be noted that throughout this disclosure, the expression "(A) B" or "B (A)" can include the concept of "A+B" or "B+A".

[0129] It should be noted that some or all of the aforementioned or following implementations may be combined or combined to form a new or other implementation.

[0130] It should be noted that the foregoing or following techniques can be used to solve at least (but not limited to) the problems or scenarios mentioned in this disclosure.

[0131] The following additional considerations apply to the foregoing and the following discussion.

[0132] It should be noted that any two or more of the foregoing or following paragraphs, (sub)bullets, points, actions or claims described in each method / technique / implementation may be logically, reasonably and appropriately combined to form a particular method.

[0133] It should be noted that any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the foregoing or following techniques / implementations / concepts may be implemented independently and separately to form a particular method. Dependencies such as “based on,” “more specifically,” “wherein,” etc., in the techniques / implementations / concepts mentioned in this disclosure are merely one possible implementation that does not limit the particular method.

[0134] Certain techniques described in this disclosure include logic or multiple components or modules. A module can be a software module (such as code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system or logic (such as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) permanently configured to perform certain operations. A hardware module may also include programmable logic or circuit systems temporarily configured by software to perform certain operations (e.g., contained within a general-purpose processor or other programmable processor). The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0135] Figure 1 , Figure 2 , Figure 3A , Figure 3B , Figure 4A , Figure 4B and Figures 5-13 The operations described herein are examples intended to aid in understanding exemplary implementations and should not be used to limit potential implementations or the scope of the claims. Some implementations may include additional operations, fewer operations, operations in parallel or different orders, and several different operations.

[0136] As used herein, the terms “component” and “module” are intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly interpreted as meaning “at least partially based on”.

[0137] This article describes several aspects in conjunction with thresholds. As used in this article, satisfying a threshold can refer to a value that is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold.

[0138] As used herein, the phrase “at least one of” or “one or more of” in the list of references refers to any combination of these items, including a single member. For example, “at least one of the following: a, b, or c” is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0139] In this disclosure, the term "can" indicates capability, or alternatively, a possible implementation option. The term "may" indicates permission or a possible implementation option.

[0140] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in connection with the implementations disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed herein and their structural equivalents. The interchangeability of hardware, firmware, and software has been generally described in terms of functionality, and has been illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and design constraints imposed on the system as a whole.

[0141] Hardware and data processing apparatuses for implementing the various illustrative components, logic, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices (PLDs), discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some implementations, specific processes, operations, and methods can be performed by a circuit system specific to a given function.

[0142] As described above, in some aspects, the implementation of the subject matter described herein can be implemented as software. For example, the various functions of the components disclosed herein, or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein, can be implemented as one or more modules of one or more computer programs. Such computer programs may include non-transitory processor-executable instructions or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or control of, a data processing apparatus including the apparatus described herein. By way of example and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media. When implemented in software, the technology may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

[0143] As used herein, the terms “user device,” “user equipment” (e.g., UE 110), “wireless communication device,” “mobile communication device,” “communication device,” or “mobile device” refer to any or all of the following: cellular phone, smartphone, portable computing device, personal or mobile multimedia player, laptop computer, tablet computer, smartbook, Internet of Things (IoT) device, handheld computer, wireless email receiver, cellular phone with multimedia internet support, wireless game controller, display subsystem, driver assistance system, vehicle controller, vehicle system controller, vehicle communication system, infotainment system, vehicle telematics system or subsystem, vehicle display system or subsystem, vehicle data controller, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, broadband router, or other type of router, and similar electronic devices including programmable processors and memories configured to perform the operations described herein, as well as circuitry. Further, in some cases, the user device may be embedded in an electronic system such as a vehicle’s main unit or an advanced driver assistance system (ADAS). Even further, a mobile internet device (MID). Depending on the type, a user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0144] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are given the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0145] Furthermore, the various features described in this specification in the context of individual implementations may also be implemented in combination in a single implementation. Conversely, the various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations. Thus, although features may be described above as functioning in a particular combination and even initially claimed in this way, in some cases one or more features from the claimed combination may be removed from the combination, and the claimed combination may involve sub-combinations or variations of sub-combinations.

[0146] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or requiring all illustrated operations to be performed to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of a flowchart or table. However, other operations not depicted may be incorporated into the schematically shown example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operations. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the implementations described above should not be construed as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the appended claims. In some cases, the actions set forth in the claims may be performed in a different order and still achieve the desired result.

[0147] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or modifications and variations can be derived from practice of these aspects. Although aspects of this disclosure have been described with reference to various examples, any combination of aspects from any example is also within the scope of this disclosure. The examples in this disclosure are provided for illustrative purposes only.

Claims

1. A method for wireless communication by a user equipment, UE (110), comprising: receiving (404, 504), from a network entity (120), at least one channel state information, CSI, report configuration (219) comprising: a plurality of codebook entities (220), one or more power relation indicators indicating a power relation between a physical downlink shared channel, PDSCH, and a CSI reference signal, CSI-RS, for each codebook entity of the plurality of codebook entities, and one or more channel measurement resources, CMRs, associated with the CSI-RS; receiving (408, 508), from the network entity, the one or more CMRs; and transmitting (412, 512), to the network entity, at least one CSI report based on the at least one CSI report configuration and the one or more CMRs.

2. The method of claim 1, further comprising transmitting (402, 502) UE capability information comprising at least one of: a first indicator indicating support for providing CSI feedback based on one or more codebook entities and power relation indicators corresponding to the one or more codebook entities; a maximum number of codebook entities with different power relation indicators; a maximum number of reported CSIs for the at least one CSI report; a number of CSI processing units, CPUs, for the at least one CSI report; or a second indicator indicating a minimum processing delay for the at least one CSI report.

3. The method of any one of claims 1-2, wherein the at least one CSI report configuration further comprises at least one of: at least one waveform indicator indicating a target waveform for the PDSCH based on the reported CSI; at least one interference measurement resource, IMR; a rank limitation indicator indicating a number of candidate layers for CSI feedback; a first channel quality indicator, CQI, table indicator indicating a common or separate CQI table for the plurality of codebook entities; a second CQI table indicator indicating a separate CQI table for each codebook entity of the plurality of codebook entities; an indicator indicating a number of reported CSIs; a configuration of power relation indicators for channel quality indicators, CQIs, corresponding to different modulation orders; one or more common CMRs for the plurality of codebook entities; or one or more separate CMRs for the plurality of codebook entities.

4. The method of claim 3, wherein the target waveform comprises at least one of: a cyclic prefix orthogonal frequency-division multiplexing, CP-OFDM, waveform, a discrete Fourier transform spread orthogonal frequency-division multiplexing, DFT-s-OFDM, waveform, or a single carrier frequency-division multiple access, SC-FDMA, waveform.

5. The method of any one of claims 1-4, wherein receiving the one or more CMRs comprises receiving a plurality of CMRs, each CMR of the plurality of CMRs having a same value for at least one of: a number of antenna ports; a bandwidth; a configuration of subcarriers; periodic; or transmitting a configuration indicating TCI states.

6. The method of any one of claims 1-5, further comprising computing CSI for the at least one CSI report based on at least one of: one codebook entity of the plurality of codebook entities; a power relationship indicator for one codebook entity of the plurality of codebook entities; a target waveform for one codebook entity of the plurality of codebook entities; or a rank restriction for one codebook entity of the plurality of codebook entities.

7. The method of any one of claims 1-6, wherein the transmitting comprises transmitting at least one of: a subset of measured CSIs in the at least one CSI report; a first indicator indicating a number of reported CSIs; a second indicator indicating a codebook entity of the plurality of codebook entities for each reported CSI; all of the measured CSIs in the at least one CSI report; a rank indicator, RI, for each CSI in the at least one CSI report; a precoder matrix indicator, PMI, for each CSI in the at least one CSI report; a channel quality indicator, CQI, for each CSI in the at least one CSI report; a layer indicator, LI, for each CSI in the at least one CSI report; a common RI for all reported CSIs; or at least one of a common RI, a common PMI, or a common LI for one codebook entity of the plurality of codebook entities and the CQI for each CSI in the at least one CSI report.

8. The method of claim 7, further comprising computing a CQI for each CSI based on an RI corresponding to the CSI and a codebook entity of the plurality of codebook entities corresponding to the CSI.

9. The method of any one of claims 1-8, further comprising: avoiding transmitting the CSI report when: a number of occupied CPUs in a component carrier, CC, or across CCs exceeds a maximum number of CPUs, or a scheduling offset for the CSI report is less than a minimum processing delay.

10. The method of any one of claims 1-9, further comprising determining either or both of a number of CPUs or a minimum scheduling offset based on at least one of: a number of the plurality of codebook entities; or a number of the one or more CMRs.

11. A method for wireless communications by a network entity (120), comprising: transmitting (404, 604), to a user equipment, UE (110), at least one channel state information, CSI, report configuration (219), the at least one CSI report configuration comprising: a plurality of codebook entities (320), one or more power relationship indicators indicating a power relationship between a physical downlink shared channel, PDSCH, and a CSI reference signal, CSI-RS, for each codebook entity of the plurality of codebook entities, and one or more channel measurement resources, CMRs, associated with the CSI-RS. ​ ​ transmitting (408, 608) the one or more CMRs to the UE; and receiving (412, 414, 612) at least one CSI report from the UE based on the at least one CSI report configuration and the one or more CMRs.

12. The method of claim 11, further comprising receiving (402, 602) UE capability information from the UE, the UE capability information comprising at least one of: a first indicator indicating support for providing CSI feedback based on one or more codebook entities and a power relation indicator corresponding to the one or more codebook entities; a maximum number of codebook entities with different power relation indicators; a maximum number of codebook entities with different power relation indicators; a maximum number of reported CSIs for the at least one CSI report; a number of CSI processing units, CPUs, for the at least one CSI report; or a second indicator indicating a minimum processing delay for the at least one CSI report.

13. The method of any one of claims 11-12, wherein the at least CSI report configuration further comprises at least one of: at least one waveform indicator indicating a target waveform for the PDSCH based on the reported CSI; at least one interference measurement resource, IMR; a rank limit indicator indicating a number of candidate layers for CSI feedback; a CQI table indicator indicating a common or separate channel quality indicator, CQI, table for the plurality of codebook entities; a first indicator indicating a number of reported CSIs; a second indicator indicating a maximum number of reported CSIs; a configuration of power relation indicators for channel quality indicators, CQIs, corresponding to different modulation orders; one or more common CMRs for the plurality of codebook entities; or one or more separate CMRs for the plurality of codebook entities.

14. The method of any one of claims 11-13, wherein the receiving comprises receiving from the UE at least one of: a subset of measured CSIs in the at least one CSI report; a first indicator indicating a number of reported CSIs; a second indicator indicating a codebook entity in the plurality of codebook entities for each reported CSI; all of the measured CSIs in the at least one CSI report; a rank indicator, RI, for each CSI in the at least one CSI report; a precoder matrix indicator, PMI, for each CSI in the at least one CSI report; a channel quality indicator, CQI, for each CSI in the at least one CSI report; a layer indicator, LI, for each CSI in the at least one CSI report; a common RI for all reported CSIs; or at least one of a common RI, a common PMI, or a common LI for one codebook entity in the plurality of codebook entities and the CQI for each CSI in the at least one CSI report.

15. The method of any of claims 1-14, wherein the plurality of codebook entities comprises a plurality of codebooks or codebook subsets, and wherein the one or more power relationship indicators comprise one or more power back-off indicators or power offset indicators.

16. An apparatus comprising: a communication unit; and a processing system configured to control the communication unit to implement any of the methods of claims 1-15.

Images