Techniques for transmitting channel state information feedback for multi-cell downlink control information

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on a plurality of component carriers (CCs). The UE may send channel state information (CSI) feedback to the network node for a set of cells scheduled by the MC-DCI based at least in part on a radio resource control (RRC) configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 885,247, filed on August 10, 2022, entitled "TECHNIQUES FOR TRANSMITTING CHANNEL STATE INFORMATION FEEDBACK FOR A MULTI-CELL DOWNLINK CONTROLINFORMATION," and the above application is hereby expressly incorporated herein by reference. Technical Field

[0003] Various aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for sending channel state information (CSI) feedback for multi-cell downlink control information (MC-DCI). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, or global level. New Radio (NR), which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. Summary of the invention

[0007] In some specific implementations, a method of wireless communication performed by a user equipment (UE) includes: receiving multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); and sending channel state information (CSI) feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on a radio resource control (RRC) configuration.

[0008] In some specific implementations, a method of wireless communication performed by a network node includes: sending MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and receiving CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on an RRC configuration.

[0009] In some specific implementations, an apparatus for performing wireless communications at a UE includes: a memory; and one or more processors, the one or more processors coupled to the memory and configured to: receive MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and send CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on an RRC configuration.

[0010] In some specific implementations, an apparatus for wireless communication at a network node includes: a memory; and one or more processors, the one or more processors coupled to the memory and configured to: send MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and receive CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on an RRC configuration.

[0011] In some specific implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and send CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on an RRC configuration.

[0012] In some specific implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: send an MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and receive CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on an RRC configuration.

[0013] In some specific implementations, an apparatus for wireless communication includes: a component for receiving MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and a component for sending CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on an RRC configuration.

[0014] In some specific implementations, an apparatus for wireless communication includes: a component for sending MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs; and a component for receiving CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on an RRC configuration.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example of channel state information (CSI) reporting configured per cell or carrier according to the present disclosure.

[0022] Figures 5 to 8 is a diagram illustrating an example associated with transmitting CSI feedback for multi-cell downlink control information (MC-DCI) according to the present disclosure.

[0023] Figures 9 and 10 is a diagram illustrating an example process associated with sending CSI feedback for MC-DCI according to the present disclosure.

[0024] Figure 11 to Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0025] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. Those skilled in the art will recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0026] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0027] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0028] Figure 11 is a diagram illustrating an example of a wireless network 100. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. The network node 110 is an example of a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0029] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, or a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0030] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0031] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a certain number of different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0032] The wireless network 100 may include one or more relay stations. A relay station is a network node that receives transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmits transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a relay, etc.

[0033] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0034] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0035] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless or wired medium.

[0036] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0037] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as a radio technology or air interface. Frequency may also be referred to as a carrier or frequency channel. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0038] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0039] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0041] With these examples in mind, unless otherwise specifically stated, if the term "sub-6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Additionally, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies that may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0042] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); and send channel state information (CSI) feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on a radio resource control (RRC) configuration. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0043] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling a channel on multiple CCs; and receive CSI feedback from the UE for a set of cells scheduled by the MC-DCI based at least in part on an RRC configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0045] Figure 2 2 is a diagram illustrating an example 200 in which a network node 110 communicates with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0046] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may use one or more channel quality indicators (CQIs) received from the UE 120 to select one or more modulation and coding schemes (MCSs) for the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 using the MCS selected for the UE 120 and may provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0047] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0048] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0049] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more antenna element sets, or one or more antenna arrays, etc. An antenna panel, antenna group, antenna element set, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a coplanar antenna element set, a non-coplanar antenna element set, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0050] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the processes described herein (eg, with reference to Figures 5 to 12 ).

[0051] At the network node 110, uplink signals from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein (e.g., reference 200 to FIG. 1 ). Figures 5 to 12 ).

[0052] In some aspects, the controller / processor 280 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be communicated to other systems or components, such as the UE 120. For example, the processing system of the UE 120 may be a system that includes various other components or subcomponents of the UE 120.

[0053] The processing system of UE 120 may interface with one or more other components of UE 120, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of UE 120 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that UE 120 may receive information or signal input, and may pass the information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that UE 120 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0054] In some aspects, controller / processor 240 may be a component of a processing system. A processing system may generally be a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs that may be passed to other systems or components, such as network node 110. For example, a processing system of network node 110 may be a system that includes various other components or subcomponents of network node 110.

[0055] The processing system of the network node 110 may interface with one or more other components of the network node 110, may process information (such as input or signal) received from one or more other components, or may output information to one or more other components. For example, a chip or modem of the network node 110 may include: a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, sending, or providing information. In some examples, the first interface may be an interface between a processing system and a receiver of the chip or modem, so that the network node 110 may receive information or signal input, and may pass the information to the processing system. In some examples, the second interface may be an interface between a processing system and a transmitter of the chip or modem, so that the network node 110 may send information output from the chip or modem. A person of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or the like may perform one or more techniques associated with sending CSI feedback for MC-DCI, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or the like Figure 2 Any other component (or combination of components) may perform or direct, for example Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, conversion, or interpretation), may cause the one or more processors, UE 120, or network node 110 to perform or direct, for example, Fig. 9 The process of 900 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0057] In some aspects, a UE (e.g., UE 120) includes a component for receiving MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling a channel on multiple CCs; and / or a component for sending CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on an RRC configuration. The component for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0058] In some aspects, a network node (e.g., network node 110) includes a component for sending MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling a channel on multiple CCs; and / or a component for receiving CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on an RRC configuration. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0059] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0061] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or components. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0062] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0063] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] Figure 33 is a diagram illustrating an example of a decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0065] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

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

[0067] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partitioning (such as that defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0068] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming or PRACH extraction and filtering, etc.). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0069] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RTRIC 315 configured to support the functionality of the SMO framework 305.

[0070] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0072] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0073] A single downlink control information (DCI) may be used to implement multi-cell physical uplink shared channel (PUSCH) or physical downlink shared channel (PDSCH) scheduling. The multi-cell PUSCH / PDSCH scheduling may be associated with one PDSCH / PUSCH per cell and may be associated with a single DCI. The multi-cell PUSCH / PDSCH scheduling may be limited by the maximum number of cells allowed to be scheduled simultaneously. The multi-cell PUSCH / PDSCH scheduling may be applicable to both intra-band carrier aggregation operations and inter-band carrier aggregation operations. The multi-cell PUSCH / PDSCH scheduling may be applicable to both FR1 and FR2. For the multi-cell PUSCH / PDSCH scheduling, a single DCI may be optimized for three or more cells. The multi-cell PUSCH / PDSCH scheduling may be associated with co-scheduled component carriers (CCs) having different bandwidths (e.g., 5MHz and 10MHz) or the same bandwidth (e.g., 100MHz).

[0074] In NR, channel state information (CSI) measurements and CSI reporting may be configured per cell / carrier. For a given carrier, the UE may report a channel state information reference signal (CSI-RS) resource indicator (CRI), a rank indicator (RI), a precoding matrix indication (PMI), a channel quality indicator (CQI), and / or a layer indicator (LI) with various dependencies. The CRI may be selected without restriction. The RI may be selected based at least in part on the selected CRI. The PMI may be selected based at least in part on the selected RI. The CQI may be selected based at least in part on the selected PMI. The LI may be selected based at least in part on the selected CQI. CSI dependency may define the RI as dependent on the CRI, the PMI as dependent on the RI, the CQI as dependent on the PMI, and the LI as dependent on the CQI. For example, when the UE reports the PMI with RI=4, the PMI for rank 2 may not be reported.

[0075] CSI reports for CSI measurements (e.g., CSI-RS measurements) for different cells / carriers may be time-division multiplexed on the same uplink channel, or CSI reports for CSI measurements for different cells / carriers may be multiplexed on the same uplink channel. When multiplexed on the same uplink channel, the CSI measurements may be independent of each other. For example, the uplink channel may include a CSI report for a first CC, a CSI report for a second CC, and so on. Depending on the CSI report for each cell / carrier, the network may determine the transmit rank, antenna port, and MCS index for each scheduled data.

[0076] Figure 4is a diagram illustrating an example 400 of CSI reporting configured per cell or carrier according to the present disclosure.

[0077] like Figure 4 As shown, according to CSI dependency, RI may depend on CRI, PMI may depend on RI, CQI may depend on PMI, and LI may depend on CQI. CSI reports for CSI measurements of different cells / carriers (e.g., CC#2, CC#1, and CC#0) may be time-division multiplexed. Alternatively, CSI reports for CSI measurements of different cells / carriers (e.g., CC#2, CC#1, and CC#0) may be multiplexed.

[0078] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0079] For multi-cell scheduling, the DCI that schedules PDSCH / PUSCH on multiple cells / carriers (which may be referred to as multi-cell DCI (MC-DCI) in this article) may need to carry scheduling information for all scheduled PDSCHs. CSI feedback for the cell / carrier may be based at least in part on the MC-DCI. When the indication fields associated with the transmission rank, antenna port, and MCS index are for each cell / carrier, the MC-DCI may need to carry these indication fields for each cell / carrier. The MC-DCI may carry information associated with the transmission rank, the antenna port, and the MCS index of the scheduled data on multiple cells / carriers, which will significantly increase the DCI overhead. The DCI overhead can be reduced by defining these indication fields as common indication fields for multiple co-scheduled cells of the MC-DCI. For example, a field may indicate a value for multiple co-scheduled cells / carriers for the MC-DCI. In other words, in order to compress the size associated with the MC-DCI, a common indication of the transmission rank, the antenna port, and the MCS index may be used.

[0080] The conventional per-cell CSI measurement / reporting framework may not be suitable for supporting common indications of transmit rank, antenna port, and MCS for multiple co-scheduled cells. For example, the UE may report RI=2 for CC1 using a PMI selected from a PMI set specified for rank 2, and the UE may report RI=4 for CC2 using a PMI selected from a PMI set specified for rank 4. In addition, the UE may report CQI based at least in part on the {RI, PMI} selected for CC1 and report CQI based at least in part on the {RI, PMI} selected for CC2, respectively. In this example, the network may identify an appropriate precoder for rank 2 for CC1 and an appropriate precoder for rank 4 for CC2, but the network may not be able to identify the appropriate rank and precoder for CC1 and CC2. The network may select rank 2 for both CCs. However, the PMI / CQI reported by the UE for CC2 may be for rank 4, and therefore, in the case of rank 2 for CC2, the network may not be able to identify the appropriate precoder and MCS.

[0081] MC-DCI may be used to perform multi-cell PUSCH / PDSCH scheduling for a first cell associated with CC1 and a second cell associated with CC2. Through the MC-DCI, the network may not be able to determine the common rank of the co-scheduled CCs (e.g., CC1 and CC2). The network may select a conservative rank (e.g., rank 2) for the co-scheduled CC, but the network may not be able to determine the appropriate precoder / MCS for the co-scheduled CC. As an example, CC1 may be associated with RI=2, PMI=x1, and CQI=y1, and CC2 may be associated with RI=4, PMI=x2, and CQI=y2. In this example, the UE may not report the PMI / CQI for RI=2.

[0082] In various aspects of the techniques and apparatus described herein, a UE may receive an MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs (or multiple cells). The multiple CCs may include a first CC and a second CC. The channels may include a PDSCH / PUSCH. The UE may receive an RRC configuration for reporting CSI feedback from the network node. The UE may send the CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on the RRC configuration. In some aspects, the RRC configuration may configure the UE to report a first RI, a first PMI, a first CQI, a second PMI, and a second CQI for the first CC, wherein the second PMI and the second CQI may be based at least in part on a second RI selected for the second CC. In some aspects, the RRC configuration configures the UE to report multiple RIs, PMIs, and CQIs, and use a different RI for each CC in the multiple CCs. In some aspects, the RRC configuration may configure the UE to multiplex multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel. In some aspects, the RRC configuration may configure the UE to report the same RI for the multiple CCs. Thus, the UE is able to report the CSI feedback for multiple co-scheduled cells associated with the MC-DCI. The network node may use the CSI feedback to determine a common rank for the co-scheduled CCs. The network node may use the CSI feedback to determine an appropriate precoder and / or MCS value (e.g., a common precoder and / or MCS value) for the co-scheduled CCs.

[0083] Figure 5 is a diagram illustrating an example 500 associated with sending CSI feedback for MC-DCI according to the present disclosure. Figure 5 As shown, example 500 includes communications between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0084] As shown in the figure 502, the UE may receive an MC-DCI from the network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs. The channel scheduled by the MC-DCI may be a PDSCH / PUSCH. The MC-DCI may be associated with a DCI format 1_X for a downlink or a DCI format 0_X for an uplink. The multiple CCs may include a first CC and a second CC, and the MC-DCI may indicate scheduling information for the first CC and the second CC. The MC-DCI may provide a common indication of a transmission rank, an antenna port, and / or an MCS, which may compress the size associated with the MC-DCI. In other words, the transmission rank, the antenna port, and / or the MCS may be associated with a common indication field for multiple co-scheduled cells for the MC-DCI.

[0085] As shown in the figure numeral 504, the UE may receive an RRC configuration from the network node. The RRC configuration may be associated with a new mode or a new configuration for reporting CSI feedback. For a set of cells configured to be scheduled by the MC-DCI, the UE may perform CSI feedback in a specific manner for the set of cells configured to be scheduled by the MC-DCI, wherein the CSI feedback in a specific manner may be based at least in part on the RRC configuration. In a first option, the RRC configuration may configure the UE to report a first RI, a first PMI, a first CQI, a second PMI, and a second CQI for the first CC, wherein the second PMI and the second CQI may be based at least in part on a second RI selected for the second CC. In a second option, the RRC configuration configures the UE to report multiple RIs, PMIs, and CQIs, and use a different RI for each of the multiple CCs. In the first option and in the second option, the RRC configuration may configure the UE to multiplex (or time-division multiplex) multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel. In the third option, the RRC configuration may configure the UE to report the same RI for the multiple CCs.

[0086] As shown in reference numeral 506, the UE may send CSI feedback for the set of cells scheduled by the MC-DCI to the network node based at least in part on the RRC configuration. The CSI feedback may indicate one or more RIs, one or more PMIs, one or more CQIs, and one or more LIs for the multiple CCs scheduled by the MC-DCI. The network node may receive the CSI feedback from the UE. The network node may select an appropriate rank, precoder, and / or MCS value for the co-scheduled CC based at least in part on the CSI feedback.

[0087] In some aspects, according to the first option, when sending the CSI feedback, the UE may send a first RI for the first CC, a second RI for the second CC, and one or more of the following: a PMI or CQI associated with the first RI for the first CC, a PMI and CQI associated with the second RI for the first CC, a PMI and CQI associated with the second RI for the second CC, and a PMI and CQI associated with the first RI for the second CC. In some aspects, according to the second option, when sending the CSI feedback, the UE may send a first RI for the first CC and one or more of the following: a PMI, CQI, or LI associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, a PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and a PMI, CQI, and LI associated with the fourth RI. In some aspects, according to the third option, when sending the CSI feedback, the UE may send one or more of the following: the same RI for the first CC and the second CC, the same or different PMI for the first CC and the second CC, the same or different CQI for the first CC and the second CC, and the same or different LI for the first CC and the second CC.

[0088] In some aspects, the UE may be configured via RRC signaling with the first option (e.g., the UE reports {PMI, CQI} associated with each RI for each CC), the second option (e.g., the UE reports multiple RI values ​​for each CC, and the UE reports the associated PMI / CQI / LI for each RI value) and / or the third option (e.g., the UE selects a common RI for co-scheduled CCs).

[0089] In some aspects, for the first option, the UE may report {RI, PMI, CQI} and {PMI, CQI} for a CC, where the {PMI, CQI} may be based at least in part on the RI selected for another CC. For the second option, the UE may report multiple {RI, PMI, CQI} with different RI values ​​for each CC. For the first option and the second option, multiple report sets for each CC may be time division multiplexed or multiplexed on the same uplink channel.

[0090] In some aspects, for the third option, the UE may report the same RI for multiple CCs, where the multiple CCs may be scheduled by the same MC-DCI. In an explicit configuration, RRC parameters may configure the UE to report the same RI for CSI reports for multiple CCs. In an implicit configuration, when the UE is configured to monitor the MC-DCI for multiple co-scheduled CCs, the UE may report the same RI for multiple CCs scheduled by the same MC-DCI without explicit configuration.

[0091] In some aspects, among the multiple {RI, PMI, CQI} having different RI values ​​for each CC in the co-scheduled CCs, the UE may select the same RI value of at least one {RI, PMI, CQI} for the co-scheduled CCs. For example, the UE may report two {RI, PMI, CQI} sets for each CC. In this case, the UE may select (e.g., the UE may be required to select) a common RI value for the multiple CCs, and the UE may report the selection as the {RI, PMI, CQI} set for the CC. The UE may not perform such actions for another {RI, PMI, CQI} set for the CC.

[0092] In some aspects, the UE may send the CSI feedback based at least in part on the CSI-RS resources on the multiple CCs or the CSI report type for the aligned multiple CCs. In some aspects, the UE may send the CSI feedback based at least in part on the same CSI report configuration type, the same reporting amount, the same time limit, or the same codebook configuration for the multiple CCs. In some aspects, the MC-DCI may be one MC-DCI among multiple MC-DCIs, wherein each MC-DCI in the multiple MC-DCIs may be used to schedule a downlink shared channel of a specific rank with co-scheduled CCs. Based at least in part on the different ranks of these MC-DCIs, these MC-DCIs may have different fields or different bit widths of fields.

[0093] In some aspects, the UE may monitor the multiple MC-DCIs, each of which may be used to schedule a PDSCH of a specific rank with the co-scheduled CC. For example, the UE may monitor MC-DCI-1 for a set of co-scheduled CCs for a PDSCH with a common rank of 1, the UE may monitor MC-DCI-2 for the same set of co-scheduled CCs for a PDSCH with a common rank of 2, and so on. These MC-DCIs may have different fields or different bit widths of fields (because they are for different ranks), and the total size of these MC-DCIs may be the same or different. Therefore, scheduling flexibility may be improved. Although the bit width of the field indicating the transmit rank / antenna port in each MC-DCI may be limited, different MC-DCIs for different ranks can effectively increase the number of rank / antenna port indications by selecting one of the multiple MC-DCIs for the same set of co-scheduled CCs.

[0094] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0095] Figure 6 is a diagram illustrating an example 600 associated with sending CSI feedback for MC-DCI according to the present disclosure.

[0096] As shown in the figure 602, when sending CSI feedback, in a first option, the UE may report RI-x for CC-i and RI-y for CC-j, where CC-i and CC-j may be co-scheduled by the network entity using MC-DCI. CC-i and CC-j may refer to a first CC and a second CC, respectively. When the UE reports RI-x for CC-i and RI-y for CC-j, where CC-i and CC-j may be co-scheduled by the MC-DCI, the UE may report PMI and CQI (e.g., {PMI, CQI}) associated with each of RI-x and RI-y for each of CC-i and CC-j. For example, for CC-i, the UE may report the PMI and the CQI associated with RI-x, and the UE may report the PMI and the CQI associated with RI-y. For CC-j, the UE may report the PMI and the CQI associated with RI-y, and the UE may report the PMI and the CQI associated with RI-x.

[0097] As shown in reference numeral 604, when sending CSI feedback, in a second option, for each of CC-i and CC-j, the UE may report multiple RI values ​​and the PMI / CQI / LI associated with each RI value, which may result in a higher probability of a common RI across CCs. For example, for CC-i, the UE may report RI-x and RI-y. The UE may report PMI / CQI / LI associated with RI-x. The UE may report PMI / CQI / LI associated with RI-y. For CC-j, the UE may report RI-a and RI-b. The UE may report PMI / CQI / LI associated with RI-a. The UE may report PMI / CQI / LI associated with RI-b.

[0098] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0099] Figure 7 is a diagram illustrating an example 700 associated with sending CSI feedback for MC-DCI according to the present disclosure.

[0100] like Figure 7 As shown, when sending CSI feedback, in the third option, the UE may report a common RI for a co-scheduled CC. Under certain conditions, the UE may select the common RI for the co-scheduled CC in the CSI report. For co-scheduled CCs, PMI / CQI / LI may be shared / aligned. An independent PMI / CQI / LI or a shared PMI / CQI / LI may be configured via RRC signaling. The PMI, CQI and / or LI may be configured to be independent or shared with respect to other PMI / CQI / LI, respectively.

[0101] For example, for CC-i, the UE may report RI-x. The UE may report PMI / CQI / LI associated with RI-x. For CC-j, the UE may also report RI-x. For CC-j, the UE may also report the PMI / CQI / LI associated with RI-x. The PMI associated with CC-i may be the same as the PMI associated with CC-j. The CQI associated with CC-i may be the same as the CQI associated with CC-j. The LI associated with CC-i may be the same as the LI associated with CC-j.

[0102] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0103] In some aspects, CSI resources / reports may be defined based on a configuration. The configuration may indicate a reporting configuration type (e.g., periodic, semi-persistent, or aperiodic) and reporting periodicity / offset / timing, reporting amount (e.g., cri-RI-PMI-CQI, cri-RI-i1, cri-RI-i1-CQI, cri-RI-CQI, and cri-RI-LI-PMI-CQI), wideband or subband parameters, time restrictions (e.g., whether the report is based at least in part on the latest CSI-RS), CQI table (e.g., one of multiple CQI tables may be used for CQI reporting), codebook configuration (e.g., type, codebook subset restriction, and / or RI restriction), and / or CSI physical uplink control channel (PUCCH) CSI-PUCCH resources (e.g., for periodic or semi-persistent CSI on PUCCH).

[0104] In some aspects, a first option (e.g., UE reports {PMI, CQI} associated with each RI for each CC) may enable cross-CC CSI dependency, and a third option (e.g., UE selects a common RI for co-scheduled CCs) may enable cross-CC CSI alignment. The first option and / or the third option may be enabled based at least in part on certain conditions. For example, the first option and / or the third option may be enabled when the CSI-RS resources on the CCs and / or the CSI reporting type / timing for the CCs are aligned (or within a time window). The first option and / or the third option may be enabled when the CSI reporting configuration type, reporting amount, time limit, and / or codebook configuration for the CCs are configured to be the same.

[0105] Figure 8 is a diagram illustrating an example 800 associated with sending CSI feedback for MC-DCI according to the present disclosure.

[0106] like Figure 8 As shown, the CSI report may be based at least in part on cross-CC CSI dependency, and / or the CSI report may be based at least in part on the same RI. The CSI report may be associated with different CCs (e.g., CC#2 and CC#1). The cross-CC CSI dependency and / or the same RI may be based at least in part on the CSI-RS resources on the CCs and / or the CSI report type / timing for the CCs that are aligned (or within a time window). The cross-CC CSI dependency and / or the same RI may be based at least in part on the CSI report configuration type, reporting amount, time limit, and / or codebook configuration for the CCs that are configured to be the same.

[0107] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0108] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE in accordance with the present disclosure. Example process 900 is an example of operations in which the UE (eg, UE 120) performs operations associated with sending CSI feedback for MC-DCI.

[0109] like Fig. 9 As shown, in some aspects, process 900 may include receiving MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs (block 910). For example, the UE (e.g., using Fig.11 Depicted receiving component 1102) can receive MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs, as described above.

[0110] like Fig. 9 As further shown, in some aspects, process 900 may include sending CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on the RRC configuration (block 920). Fig.11 Depicted transmitting component 1104) may transmit, based at least in part on an RRC configuration, CSI feedback for a set of cells scheduled by the MC-DCI to the network node, as described above.

[0111] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0112] In a first aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 900 includes: sending a first RI for the first CC, a second RI for the second CC, and one or more of the following: a PMI or CQI associated with the first RI for the first CC, a PMI and CQI associated with the second RI for the first CC, a PMI and CQI associated with the second RI for the second CC, and a PMI and CQI associated with the first RI for the second CC.

[0113] In a second aspect, alone or in combination with the first aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 900 includes: sending a first RI for the first CC and one or more of the following: a PMI, a CQI or a LI associated with the first RI, a second RI for the first CC, a PMI, a CQI and a LI associated with the second RI, a third RI for the second CC, a PMI, a CQI and a LI associated with the third RI, a fourth RI for the second CC, and a PMI, a CQI and a LI associated with the fourth RI.

[0114] In a third aspect, alone or in combination with one or more of the first aspect and the second aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 900 includes: sending one or more of the following: the same RI for the first CC and the second CC, the same or different PMI for the first CC and the second CC, the same or different CQI for the first CC and the second CC, and the same or different LI for the first CC and the second CC.

[0115] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the RRC configuration configures the UE to report a first RI, a first PMI, a first CQI, a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are at least partially based on a second RI selected for a second CC.

[0116] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the RRC configuration configures the UE to report multiple RIs, PMIs, and CQIs, and uses a different RI for each CC in the multiple CCs.

[0117] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel.

[0118] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RRC configuration configures the UE to send the same RI for the multiple CCs.

[0119] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 900 includes sending the CSI feedback based at least in part on one or more of the CSI reference signal resources on the multiple CCs or a CSI report type for the aligned multiple CCs.

[0120] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 900 includes sending the CSI feedback based at least in part on the same CSI reporting configuration type, the same reporting amount, the same time limit, or the same codebook configuration for the multiple CCs.

[0121] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the MC-DCI is one MC-DCI among the multiple MC-DCIs, and each MC-DCI among the multiple MC-DCIs is used to schedule a downlink shared channel of a specific rank with co-scheduled CCs, and at least in part based on the MC-DCIs having different fields or different bit widths of fields for different ranks.

[0122] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The depicted blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0123] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a network node in accordance with the present disclosure. Example process 1000 is an example of the network node (eg, network node 110) performing operations associated with sending CSI feedback for MC-DCI.

[0124] like Fig.10 As shown, in some aspects, process 1000 may include: sending a MC-DCI to a UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs (block 1010). For example, a network node (e.g., using Fig.12 Depicted transmitting component 1204) can transmit MC-DCI to the UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs, as described above.

[0125] like Fig.10 As further shown, in some aspects, process 1000 may include: receiving CSI feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on the RRC configuration (block 1020). Fig.12 Depicted receiving component 1202) can receive, from the UE, CSI feedback for a set of cells scheduled by the MC-DCI based at least in part on an RRC configuration, as described above.

[0126] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0127] In a first aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 1000 includes: receiving a first RI for the first CC, a second RI for the second CC, and one or more of the following: a PMI or CQI associated with the first RI for the first CC, a PMI and CQI associated with the second RI for the first CC, a PMI and CQI associated with the second RI for the second CC, and a PMI and CQI associated with the first RI for the second CC.

[0128] In a second aspect, alone or in combination with the first aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 1000 includes: receiving a first RI for the first CC and one or more of the following: a PMI or CQI and LI associated with the first RI, a second RI for the first CC, a PMI, CQI and LI associated with the second RI, a third RI for the second CC, PMI, CQI and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI and LI associated with the fourth RI.

[0129] In a third aspect, alone or in combination with one or more of the first aspect and the second aspect, the MC-DCI indicates the scheduling information for the first CC and the second CC, and process 1000 includes: receiving one or more of the following: the same RI for the first CC and the second CC, the same or different PMI for the first CC and the second CC, the same or different CQI for the first CC and the second CC, and the same or different LI for the first CC and the second CC.

[0130] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the RRC configuration configures the UE to report a first RI, a first PMI, a first CQI, a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are at least partially based on a second RI selected for a second CC.

[0131] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the RRC configuration configures the UE to report multiple RIs, PMIs, and CQIs, and uses a different RI for each CC in the multiple CCs.

[0132] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel.

[0133] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RRC configuration configures the UE to report RI for the multiple CCs.

[0134] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1000 includes: receiving the CSI feedback based at least in part on one or more CSI reference signal resources among the CSI reference signal resources on the multiple CCs or a CSI report type for the aligned multiple CCs.

[0135] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1000 includes receiving the CSI feedback based at least in part on the same CSI reporting configuration type, the same reporting amount, the same time limit, or the same codebook configuration for the multiple CCs.

[0136] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the MC-DCI is one MC-DCI among the multiple MC-DCIs, and each MC-DCI among the multiple MC-DCIs is used to schedule a downlink shared channel of a specific rank with co-scheduled CCs, and at least in part based on the MC-DCIs having different fields or different bit widths of fields for different ranks.

[0137] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 The depicted blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0138] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104.

[0139] In some aspects, the apparatus 1100 may be configured to perform Figures 5 to 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0140] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0141] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0142] Receiving component 1102 can receive MC-DCI from a network node, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs. Sending component 1104 can send CSI feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on the RRC configuration.

[0143] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

[0144] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network node, or a network node may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204.

[0145] In some aspects, the apparatus 1200 may be configured to perform Figures 5 to 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 The process 1000. In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0146] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0147] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0148] Transmitting component 1204 can transmit MC-DCI to the UE, the MC-DCI indicating scheduling information for scheduling channels on multiple CCs. Receiving component 1202 can receive CSI feedback from the UE for a set of cells scheduled by the MC-DCI based at least in part on the RRC configuration.

[0149] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly of (one or more) components shown may be described as being executable by Fig.12Another collection of components shown performs one or more functions.

[0150] The following provides an overview of some aspects of the disclosure:

[0151] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); and sending channel state information (CSI) feedback for a set of cells scheduled by the MC-DCI to the network node based at least in part on a radio resource control (RRC) configuration.

[0152] Aspect 2: A method according to aspect 1, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein a first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following are sent: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and a CQI associated with the second RI for the first CC, a PMI and a CQI associated with the second RI for the second CC, and a PMI and a CQI associated with the first RI for the second CC.

[0153] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein sending the CSI feedback includes: sending a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

[0154] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein sending the CSI feedback includes: sending one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

[0155] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the RRC configuration configures the UE to report a first rank indicator (RI), a first precoding matrix indicator (PMI), a first channel quality indicator (CQI), a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are at least partially based on a second RI selected for a second CC.

[0156] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the RRC configuration configures the UE to report multiple rank indicators (RIs), precoding matrix indicators (PMIs), and channel quality indicators (CQIs), and uses a different RI for each CC in the multiple CCs.

[0157] Aspect 7: The method according to any one of aspects 1 to 6, wherein the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel.

[0158] Aspect 8: The method according to any one of aspects 1 to 7, wherein the RRC configuration configures the UE to report the same rank indicator reported for the multiple CCs.

[0159] Aspect 9: A method according to any one of aspects 1 to 8, wherein the sending of the CSI feedback is based at least in part on one or more of the following: CSI reference signal resources on the multiple CCs or CSI reporting types for the multiple CCs that are aligned.

[0160] Aspect 10: The method according to any one of aspects 1 to 9, wherein the sending of the CSI feedback is based at least in part on the same CSI reporting configuration type, the same reporting amount, the same time limit or the same codebook configuration for the multiple CCs.

[0161] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the MC-DCI is one MC-DCI among multiple MC-DCIs, wherein each MC-DCI among the multiple MC-DCIs is used to schedule a downlink shared channel of a specific rank with a co-scheduled CC, and wherein the MC-DCI has different fields or different bit widths of fields for different ranks based at least in part on the MC-DCI.

[0162] Aspect 12: A method of wireless communication performed by a network node, the method comprising: sending multi-cell downlink control information (MC-DCI) to a user equipment (UE), the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); and receiving channel state information (CSI) feedback for a set of cells scheduled by the MC-DCI from the UE based at least in part on a radio resource control (RRC) configuration.

[0163] Aspect 13: A method according to Aspect 12, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback includes: a first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and CQI associated with the second RI for the first CC, a PMI and CQI associated with the second RI for the second CC, and a PMI and CQI associated with the first RI for the second CC.

[0164] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback includes: receiving a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

[0165] Aspect 15: A method according to any one of Aspects 12 to 14, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback includes: receiving one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

[0166] Aspect 16: A method according to any one of Aspects 12 to 15, wherein the RRC configuration configures the UE to report a first rank indicator (RI), a first precoding matrix indicator (PMI), a first channel quality indicator (CQI), a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are at least partially based on a second RI selected for a second CC.

[0167] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the RRC configuration configures the UE to report multiple rank indicators (RIs), precoding matrix indicators (PMIs), and channel quality indicators (CQIs), and uses a different RI for each CC in the multiple CCs.

[0168] Aspect 18: The method according to any one of aspects 12 to 17, wherein the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each CC in the multiple CCs on an uplink channel.

[0169] Aspect 19: The method according to any one of aspects 12 to 18, wherein the RRC configuration configures the UE to report the same rank indicator for the multiple CCs.

[0170] Aspect 20: A method according to any one of aspects 12 to 19, wherein the receiving of the CSI feedback is based at least in part on one or more of: CSI reference signal resources on the multiple CCs or CSI reporting types for the multiple CCs that are aligned.

[0171] Aspect 21: A method according to any one of aspects 12 to 20, wherein the receiving of the CSI feedback is based at least in part on the same CSI reporting configuration type, the same reporting amount, the same time limit or the same codebook configuration for the multiple CCs.

[0172] Aspect 22: A method according to any one of Aspects 12 to 21, wherein the MC-DCI is one MC-DCI among multiple MC-DCIs, wherein each MC-DCI among the multiple MC-DCIs is used to schedule a downlink shared channel of a specific rank with a co-scheduled CC, and wherein the MC-DCI has different fields or different bit widths of fields for different ranks based at least in part on the MC-DCI.

[0173] Aspect 23: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0174] Aspect 24: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory and configured to execute the method according to one or more of aspects 1 to 11.

[0175] Aspect 25: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 to 11.

[0176] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0177] Aspect 27: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.

[0178] Aspect 28: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 22.

[0179] Aspect 29: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory and configured to perform the method according to one or more of aspects 12 to 22.

[0180] Aspect 30: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 12 to 22.

[0181] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 22.

[0182] Aspect 32: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 12 to 22.

[0183] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0184] As used herein, the term "component" is 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 "based at least in part on". As used herein, depending on the context, "satisfying a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0185] In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries (e.g., related entries, unrelated entries, or a combination of related and unrelated entries), and can be used interchangeably with "one or more". If only one entry is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "having" and similar terms are intended to be open terms that do not limit the elements (e.g., elements "including" A may also contain B) that they modify. In addition, as used herein, the term "or" is intended to be inclusive when used in a sequence, and can be used interchangeably with "and / or", unless otherwise expressly stated (e.g., in the case of being used in combination with "any one of" or "only one of").

[0186] The various illustrative logics, logical blocks, modules, circuits, and algorithmic processes described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0187] The hardware and data processing apparatus for implementing the various illustrative logic components, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. In some aspects, specific processes and methods may be performed by circuits dedicated to a given function.

[0188] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on computer storage media to be executed by a data processing apparatus or to control the operation of the data processing apparatus.

[0189] If implemented in software, the function may be stored on a computer-readable medium as one or more instructions or codes or sent through a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any medium that can realize the transfer of a computer program from one place to another. Storage media can be any available medium that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The combination of media described herein should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0190] Various modifications to the various aspects described in this disclosure may be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0191] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0192] Certain features described in this specification in the context of independent aspects may also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect may also be implemented in multiple aspects individually or in any suitable subcombination. In addition, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may be removed from the combination in some cases, and a claimed combination may be directed to a subcombination, or a variation of a subcombination.

[0193] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted can be incorporated into the example processes schematically illustrated. For example, one or more additional operations can be performed before, after, at the same time, or between any operations in the illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the various aspects described should not be understood as requiring such separation in all aspects, 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 aspects also fall within the scope of the appended claims. In some cases, the actions recorded in the claims can be performed in different orders and still achieve the desired result.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on a plurality of component carriers (CCs); as well as Based at least in part on a radio resource control (RRC) configuration, channel state information (CSI) feedback is sent to the network node for a set of cells scheduled by the MC-DCI.

2. The method of claim 1, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein sending the CSI feedback comprises: Send a first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and a CQI associated with the second RI for the first CC, a PMI and a CQI associated with the second RI for the second CC, and a PMI and a CQI associated with the first RI for the second CC.

3. The method of claim 1 , wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein sending the CSI feedback comprises: Send a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

4. The method of claim 1 , wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein sending the CSI feedback comprises: Send one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

5. The method of claim 1 , wherein the RRC configuration configures the UE to report a first rank indicator (RI), a first precoding matrix indicator (PMI), a first channel quality indicator (CQI), a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are based at least in part on a second RI selected for a second CC.

6. The method of claim 1, wherein the RRC configuration configures the UE to report a plurality of rank indicators (RIs), precoding matrix indicators (PMIs), and channel quality indicators (CQIs), and uses a different RI for each CC in the plurality of CCs.

7. The method of claim 1, wherein the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each of the plurality of CCs on an uplink channel.

8. The method of claim 1, wherein the RRC configuration configures the UE to report the same rank indicator for the multiple CCs.

9. The method of claim 1, wherein the sending of the CSI feedback is based at least in part on one or more of: CSI reference signal resources on the plurality of CCs or CSI reporting types for the plurality of CCs that are aligned.

10. The method of claim 1, wherein sending the CSI feedback is based at least in part on a same CSI reporting configuration type, a same reporting amount, a same time limit, or a same codebook configuration for the plurality of CCs.

11. The method of claim 1 , wherein the MC-DCI is one of a plurality of MC-DCIs, wherein each of the plurality of MC-DCIs is used to schedule a downlink shared channel of a specific rank with co-scheduled CCs, and wherein the MC-DCI has different fields or different bit widths of fields for different ranks based at least in part on the MC-DCI.

12. A method of wireless communication performed by a network node, the method comprising: sending multi-cell downlink control information (MC-DCI) to a user equipment (UE), the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); as well as Based at least in part on a radio resource control (RRC) configuration, channel state information (CSI) feedback is received from the UE for a set of cells scheduled by the MC-DCI.

13. The method of claim 12, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback comprises: A first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and a CQI associated with the second RI for the first CC, a PMI and a CQI associated with the second RI for the second CC, and a PMI and a CQI associated with the first RI for the second CC.

14. The method of claim 12, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback comprises: Receive a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

15. The method of claim 12, wherein the MC-DCI indicates the scheduling information for the first CC and the second CC, and wherein receiving the CSI feedback comprises: Receive one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

16. The method of claim 12, wherein the RRC configuration configures the UE to report a first rank indicator (RI), a first precoding matrix indicator (PMI), a first channel quality indicator (CQI), a second PMI, and a second CQI for a first CC, wherein the second PMI and the second CQI are based at least in part on a second RI selected for a second CC.

17. The method of claim 12, wherein the RRC configuration configures the UE to report multiple rank indicators (RIs), precoding matrix indicators (PMIs), and channel quality indicators (CQIs), and uses a different RI for each CC in the multiple CCs.

18. The method of claim 12, wherein the RRC configuration configures the UE to multiplex multiple sets of CSI reports for each of the plurality of CCs on an uplink channel.

19. The method of claim 12, wherein the RRC configuration configures the UE to report the same rank indicator for the multiple CCs.

20. The method of claim 12, wherein the receiving of the CSI feedback is based at least in part on one or more of: CSI reference signal resources on the plurality of CCs or CSI reporting types for the plurality of CCs that are aligned.

21. The method of claim 12, wherein receiving the CSI feedback is based at least in part on a same CSI reporting configuration type, a same reporting amount, a same time limit, or a same codebook configuration for the plurality of CCs.

22. The method of claim 12, wherein the MC-DCI is one of a plurality of MC-DCIs, wherein each of the plurality of MC-DCIs is used to schedule a downlink shared channel of a specific rank with co-scheduled CCs, and wherein the MC-DCI has different fields or different bit widths of fields for different ranks based at least in part on the MC-DCI.

23. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving multi-cell downlink control information (MC-DCI) from a network node, the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on a plurality of component carriers (CCs); as well as Based at least in part on a radio resource control (RRC) configuration, channel state information (CSI) feedback is sent to the network node for a set of cells scheduled by the MC-DCI.

24. The apparatus of claim 23, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to send the CSI feedback, the one or more processors are configured to: Send a first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and a CQI associated with the second RI for the first CC, a PMI and a CQI associated with the second RI for the second CC, and a PMI and a CQI associated with the first RI for the second CC.

25. The apparatus of claim 23, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to send the CSI feedback, the one or more processors are configured to: Send a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

26. The apparatus of claim 23, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to send the CSI feedback, the one or more processors are configured to: Send one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

27. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: sending multi-cell downlink control information (MC-DCI) to a user equipment (UE), the multi-cell downlink control information (MC-DCI) indicating scheduling information for scheduling channels on multiple component carriers (CCs); as well as Based at least in part on a radio resource control (RRC) configuration, channel state information (CSI) feedback is received from the UE for a set of cells scheduled by the MC-DCI.

28. The apparatus of claim 27, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to receive the CSI feedback, the one or more processors are configured to: A first rank indicator (RI) for the first CC, a second RI for the second CC, and one or more of the following: a precoding matrix indicator (PMI) or a channel quality indicator (CQI) associated with the first RI for the first CC, a PMI and a CQI associated with the second RI for the first CC, a PMI and a CQI associated with the second RI for the second CC, and a PMI and a CQI associated with the first RI for the second CC.

29. The apparatus of claim 27, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to receive the CSI feedback, the one or more processors are configured to: Receive a first rank indicator (RI) for the first CC and one or more of the following: a precoding matrix indicator (PMI), a channel quality indicator (CQI), or a layer indicator (LI) associated with the first RI, a second RI for the first CC, a PMI, CQI, and LI associated with the second RI, a third RI for the second CC, PMI, CQI, and LI associated with the third RI, a fourth RI for the second CC, and PMI, CQI, and LI associated with the fourth RI.

30. The apparatus of claim 27, wherein the MC-DCI indicates the scheduling information for a first CC and a second CC, and wherein to receive the CSI feedback, the one or more processors are configured to: Receive one or more of the following: the same rank indicator (RI) for the first CC and the second CC, the same or different precoding matrix indicators (PMI) for the first CC and the second CC, the same or different channel quality indicators (CQI) for the first CC and the second CC, and the same or different layer indicators (LI) for the first CC and the second CC.

Images