Techniques for communicating 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, from a network node, multi-cell downlink control information (MC-DCI) indicating scheduling information for co-scheduled component carriers (CCs), wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs. The UE may perform a transmission based at least in part on the scheduling information indicated by the MC-DCI. 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,232, entitled “TECHNIQUES FOR COMMUNICATING MULTI-CELL DOWNLINK CONTROL INFORMATION,” filed on August 10, 2022, which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for communicating 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, etc.).

[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) indicating scheduling information for co-scheduled component carriers (CCs) from a network node, wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more co-scheduled CCs in the co-scheduled CCs; and performing transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0008] In some specific implementations, a method of wireless communication performed by a network node includes: sending an MC-DCI indicating scheduling information for co-scheduled CCs to a UE, wherein the MC-DCI indicates one or more of antenna port fields or MCS fields of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and performing the sending based at least in part on the scheduling information indicated by the MC-DCI.

[0009] In some specific implementations, an apparatus for performing wireless communications at a UE includes a memory and one or more processors coupled to the memory, the one or more processors being configured to: receive an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and perform transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0010] In some specific implementations, an apparatus for performing wireless communications at a network node includes a memory and one or more processors coupled to the memory, the one or more processors being configured to: send an MC-DCI indicating scheduling information for co-scheduled CCs to a UE, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and perform the sending based at least in part on the scheduling information indicated by the MC-DCI.

[0011] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and perform transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0012] In some specific implementations, a non-transitory computer-readable medium storing an instruction set 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 indicating scheduling information for co-scheduled CCs to a UE, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and perform the sending based at least in part on the scheduling information indicated by the MC-DCI.

[0013] In some specific implementations, an apparatus for wireless communication includes: a component for receiving an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and a component for performing transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0014] In some specific implementations, an apparatus for wireless communication includes: a component for sending an MC-DCI indicating scheduling information for co-scheduled CCs to a UE, wherein the MC-DCI indicates one or more of antenna port fields or MCS fields of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs; and a component for performing the transmission based at least in part on the scheduling information indicated by the MC-DCI.

[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 multiple lookup tables and corresponding radio resource control (RRC) configurable parameters according to the present disclosure.

[0022] Figure 5 is a diagram illustrating an example of multiple lookup tables and corresponding conditions according to the present disclosure.

[0023] Figures 6 to 13 is a diagram illustrating an example associated with communicating MC-DCI according to the present disclosure.

[0024] Figure 14 to Figure 15is a diagram illustrating an example process associated with communicating MC-DCI according to the present disclosure.

[0025] Figure 16 to Figure 17 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] 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. It should be appreciated by those skilled in the art 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.

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

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

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

[0030] 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. For example, the network node 110 may include 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, 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.

[0031] 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 in , 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. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0032] 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 a plurality of 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 geographic location or in different geographic 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.

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

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

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

[0036] 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), an in-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.

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

[0038] Generally speaking, 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.

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

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

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

[0042] 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 the techniques described herein are applicable to those modified frequency ranges.

[0043] 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) indicating scheduling information for co-scheduled component carriers (CCs) from a network node, wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and perform transmission based at least in part on the scheduling information indicated by the MC-DCI. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] 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 to the UE an MC-DCI indicating scheduling information for co-scheduled CCs, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs; and perform the sending based at least in part on the scheduling information indicated by the MC-DCI. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

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

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

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

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

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

[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a 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 a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted 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 (e.g., the controller / processor 280) and a memory 282 to perform operations described herein (e.g., with reference to Figures 6 to 17 )Aspects of any process described in the process.

[0052] 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 operations described herein (e.g., with reference to Figures 6 to 17 )Aspects of any process described in the process.

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

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

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

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

[0057] 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 UE 120 may perform one or more techniques associated with communicating 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 Figure 2 Any other component (or combination of components) may perform or direct, for example Fig.14 The process of 1400 Fig.15 The operations of process 1500 and / or 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 a non-transitory computer-readable medium 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.14 The process of 1400 Fig.15 The process 1500 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, etc.

[0058] In some aspects, a UE (e.g., UE 120) includes a means for receiving an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs; and / or a means for performing transmission based at least in part on the scheduling information indicated by the MC-DCI. The means 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.

[0059] In some aspects, a network node (e.g., network node 110) includes means for sending to a UE an MC-DCI indicating scheduling information for co-scheduled CCs, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs; and / or means for performing transmission based at least in part on the scheduling information indicated by the MC-DCI. In some aspects, means for a network node to perform operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0060] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for 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.

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

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

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

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

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

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

[0067] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function can be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. 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, 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, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0068] 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 partition 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.

[0069] 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 splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, 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.

[0070] 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-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

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

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

[0074] The antenna port field in the downlink control information (DCI) format 1_1 / 1_2 may indicate a row of a lookup table identified by various RRC parameters. The lookup table may be associated with 3GPP Technical Specification (TS) Release 17 and subsequent releases (e.g., TS 38.212). The RRC parameters may be associated with the number of codewords (CWs), DMRS type, maximum length, and / or number of transmit configuration indication (TCI) states per TCI code point.

[0075] Figure 4 is a diagram illustrating an example 400 of multiple lookup tables and corresponding RRC configurable parameters according to the present disclosure.

[0076] like Figure 4As shown in , a set of RRC configurable parameters may correspond to a certain lookup table in 3GPP TS (e.g., TS 38.212), and in some cases, to the left column or right column of the certain lookup table. The RRC configurable parameter set may include the number of CWs (e.g., one or two), the DMRS type (e.g., one or two), the maximum length (e.g., one or two), and / or the number of TCI states per TCI code point (e.g., one or two). The lookup table may be associated with an antenna port field, which may be associated with a plurality of bits (e.g., 4, 5, or 6 bits).

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

[0078] In some cases, the antenna port field may be five bits (e.g., the antenna port field associated with Table 7.3.1.2.2-3 may be five bits). The antenna port field may indicate a value for one codeword or for two codewords. The value for one codeword may be associated with the left column of the lookup table, and the value for the second codeword may be associated with the right column of the lookup table. For a component carrier configured with two CWs, the DCI may carry two MCS or redundancy version (RV) fields for the two CWs. Whether the value for one codeword is used or the value for two codewords is used (e.g., the left portion or the right portion of the lookup table will be used) may depend on whether the scheduled physical downlink shared channel (PDSCH) carries one CW (e.g., one transport block TB) or two CWs (e.g., two TBs). When an RRC parameter such as the maximum number of CWs scheduled by DCI (maxNrofCodeWordsScheduledByDCI) RRC parameter is set to "n2" and the DCI does not indicate {MCS=26, RV=1}, the scheduled PDSCH can carry two CWs, where MCS=26 and RV=1 may correspond to a special combination indicating that CW (e.g., TB) is disabled.

[0079] The MCS for a TB may indicate a row of an MCS table identified by various conditions. The MCS table may be associated with a 3GPP TS (e.g., TS 38.214). The various conditions may include an MCS cell radio network temporary identifier (MCS-C-RNTI) for a cell group (e.g., configured or unconfigured), an RRC configuration of the MCS table (e.g., set to quadrature amplitude modulation (QAM) 1024, set to QAM 256, etc.), a DCI format (e.g., DCI format 1_1, 1_2, etc.), and an RNTI scrambled cyclic redundancy check (CRC) for the DCI.

[0080] Figure 5is a diagram illustrating an example 500 of multiple lookup tables and corresponding conditions according to the present disclosure.

[0081] like Figure 5 As shown in , the condition set may correspond to a lookup table in 3GPP TS (e.g., TS 38.214). The lookup table may be associated with the MCS field (or MCS index table). These conditions may include the MCS-C-RNTI for the cell group, the RRC configuration of the MCS table, the DCI format, and the RNTI scrambled CRC of the DCI. The MCS-C-RNTI for the cell group may be configured or not configured. The RRC configuration of the MCS table may correspond to a Mcs-Table set to "qam1024", a Mcs-TableDCI-1-2 set to "qam1024", a Mcs-TableDCI-1-2 set to "qam256", a Mcs-TableDCI-1-2 set to "qam64LowSE", a Mcs-Table set to "qam256", a Mcs-Table for multicast set to "qam256", a Mcs-Table for multicast control channel (MCCH) or multicast traffic channel (MTCH) set to "qam256", a Mcs-Table for multicast set to "qam64LowSE", or a Mcs-Table set to "qam64LowSE". The DCI format may be DCI format 1_1, DCI format 1_2, DCI format 4_1 / 4_2, DCI format 4_0, DCI format 1_0 / 1_1, or DCI format 1_0 / 1_1 / 1_2 in a UE-specific search space (USS). The RNTI scrambled CRC of the DCI may be C-RNTI, group RNTI (G-RNTI), MCCH-RNTI, or MCS-C-RNTI.

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

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

[0084] However, for DCI or multi-cell downlink control information (MC-DCI) that implements multi-cell scheduling, the antenna port field and the MCS field may need to be redefined, because having an antenna port field and an MCS field for each of the component carriers co-scheduled by MC-DCI may significantly increase the DCI overhead. For example, using the antenna port field and the MCS field for each of two component carriers (CCs) (or two cells) scheduled by MC-DCI may generate twice as many bits as a single CC (or a single cell), thereby increasing the signaling overhead.

[0085] In various aspects of the techniques and apparatus described herein, a UE may receive from a network node an MC-DCI indicating scheduling information for a co-scheduled CC. The MC-DCI may indicate an antenna port field and / or an MCS field to be applied to one or more co-scheduled CCs in the co-scheduled CCs. In some aspects, the co-scheduled CCs may be associated with the same number of codewords, the same DMRS type, the same maximum length, and / or the same number of TCI states per TCI code point. The antenna port field for the co-scheduled CCs may be a common lookup table for the co-scheduled CCs. In some aspects, the MCS table DCI RRC parameter may be set to the same value from QAM 1024, QAM 256, or QAM 64 low spectral efficiency for the co-scheduled CCs, or the MCS table DCI RRC parameter may not be configured for any co-scheduled CC in the co-scheduled CCs. The UE and / or network node may perform transmission based at least in part on the scheduling information indicated by the MC-DCI. In some aspects, by jointly indicating the antenna port field and / or MCS field for co-scheduled CCs in the MC-DCI, the size of the MC-DCI can be reduced and the signaling overhead associated with sending the MC-DCI can be reduced, thereby saving power at the UE and / or network node.

[0086] Figure 6 6 is a diagram illustrating an example 600 associated with communicating MC-DCI according to the present disclosure. Figure 6 As shown in , example 600 includes communications between a UE (eg, UE 120) and a network node (eg, network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0087] As shown in the figure 602, the UE may receive from the network node an MC-DCI indicating scheduling information for a co-scheduled CC. The MC-DCI may indicate an antenna port field and / or an MCS field to be applied to one or more co-scheduled CCs in the co-scheduled CCs. In some aspects, the co-scheduled CCs may be associated with the same number of CWs, the same DMRS type, the same maximum length, and / or the same number of TCI states per TCI code point. The antenna port field for the co-scheduled CCs may be a common lookup table for the co-scheduled CCs. In some aspects, the MCS table DCI RRC parameter may be set to QAM 1024, QAM 256, or QAM 64 low spectral efficiency for the co-scheduled CCs, or the MCS table DCI RRC parameter may not be configured for any co-scheduled CC in the co-scheduled CCs. In some cases, the MCS table DCI RRC parameter may be defined as a per-CC parameter, and the same MCS table DCI RRC parameter may be associated with each co-scheduled CC in the co-scheduled CCs.

[0088] In some aspects, a network node may send a MC-DCI for multi-cell scheduling to a UE. Multi-cell scheduling may be used for co-scheduled CCs. The MC-DCI may indicate a field, such as an antenna port field and / or an MCS field, that may be commonly applied to one or more co-scheduled CCs in the co-scheduled CCs. The MC-DCI may include a common indication for co-scheduled CCs. For co-scheduled CCs that commonly apply the antenna port field, the same lookup table may be used. The lookup table may be associated with the antenna port field.

[0089] In some aspects, for co-scheduled CCs, the number of CWs, DMRS type, maximum length, and number of TCI states per TCI code point may be the same, such that the antenna port field for the co-scheduled CCs may refer to a common lookup table. The relevant RRC parameters for each CC may be configured such that the antenna port field refers to the same lookup table for all co-scheduled CCs in the co-scheduled CCs. For example, the same set of RRC parameters (e.g., number of CWs equal to two, DMRS type one, maximum length one, and one TCI state per TCI code point) may be associated with all co-scheduled CCs in the co-scheduled CCs.

[0090] In some aspects, the MC-DCI may indicate an antenna port field and / or an MCS field for a first subgroup and a second subgroup. The first subgroup may be associated with a first CC subset of co-scheduled CCs, and the second subgroup may be associated with a second CC subset of co-scheduled CCs. The MC-DCI may indicate a common indication field applicable to a subset of co-scheduled CCs associated with a subgroup in a co-scheduled CC, and different bits in the MC-DCI may be used for subsets of co-scheduled CCs in different subgroups. A subset of co-scheduled CCs in a subgroup of a co-scheduled CC may be associated with the same RRC parameter. In some aspects, the subgrouping of co-scheduled CCs may be based at least in part on a dedicated RRC parameter, and the UE may be configured with an association between each co-scheduled CC and each subgroup in the co-scheduled CC using a dedicated RRC parameter. In some aspects, the subgrouping of co-scheduled CCs may be based at least in part on whether the co-scheduled CCs are associated with the same antenna port field or MCS field.

[0091] When fields in the MC-DCI, such as the antenna port field and / or the MCS field, apply to all co-scheduled CCs in a co-scheduled CC, the indication may not be optimal for all co-scheduled CCs in a co-scheduled CC. Co-scheduled CCs may be associated with different frequency bands, operate with different RF components / chains, or may have different bandwidths. Therefore, when the co-scheduled CCs do not have the same physical characteristics, a common indication for all co-scheduled CCs in a co-scheduled CC may result in some performance degradation.

[0092] In some aspects, the MC-DCI may be associated with a subgroup of co-scheduled CCs. The MC-DCI may support subgroups of co-scheduled CCs, and the common indication field may be applicable to the co-scheduled CCs associated with the subgroup. For example, for four co-scheduled CCs, two CCs may be associated with subgroup 1, and the other two CCs may be associated with subgroup 2. In this example, the MC-DCI may include two copies of a particular field, and each copy of the particular field may be applicable to each subgroup. Different bits in the MC-DCI may be used for co-scheduled CCs in different subgroups.

[0093] In some aspects, for co-scheduled CCs in a sub-group, a field (e.g., antenna port field or MCS field) may indicate a value of a common table. Thus, the RRC parameters may be configured to be the same between co-scheduled CCs in a sub-group.

[0094] In some aspects, for the subgroup configuration, the subgroup may be explicitly determined by a dedicated RRC parameter. The UE may be configured with an association between each co-scheduled CC in the co-scheduled CC and each subgroup in the subgroup through a specific RRC parameter. When the UE is configured with multiple subgroups, the UE may consider that the MC-DCI for the co-scheduled CC has two specific fields (e.g., an antenna port field and an MCS field), and each field in the field may be used for each subgroup in the subgroup. When all co-scheduled CCs in the co-scheduled CC have the same RRC configuration, more than one subgroup may be configured.

[0095] In some aspects, for subgrouping configuration, the subgrouping may be implicitly determined based at least in part on whether the co-scheduled CCs use the same lookup table. For example, when all co-scheduled CCs in the co-scheduled CCs have the same RRC configuration set regarding the number of CWs, DMRS type, maximum length, number of TCI states, and MCS table, the UE may consider the MC-DCI for the co-scheduled CCs to have only one specific field (e.g., antenna port field or MCS field). When two sets of co-scheduled CCs have the same RRC configuration set regarding the number of CWs, DMRS type, maximum length, number of TCI states, and MCS table, the UE may consider the MC-DCI for the co-scheduled CCs to have two specific fields (e.g., antenna port field and MCS field), and each of the two specific fields may be used for each subgroup. When different RRC configurations are used for co-scheduled CCs, duplicate fields may be present in the MC-DCI.

[0096] In some aspects, subgroups may be used for multiple different configurations for cells co-scheduled by MC-DCI. The subgroups may be cell-level subgroups. For example, all bandwidth part (BWP) configurations for a given cell may be associated with a subgroup. Alternatively, the subgroups may be BWP-level subgroups. For example, each BWP configuration for a given cell may be associated with a subgroup.

[0097] In some aspects, the subgrouping of the co-scheduled CCs may be cell-level subgroupings. Multiple bandwidth portion configurations for a given cell may be associated with a subgroup. The BWP may be switchable (e.g., dynamically switchable or semi-statically switchable) on each CC without changing the subgrouping of the co-scheduled CCs. In some aspects, the subgrouping of the co-scheduled CCs may be BWP-level subgroupings. Each BWP configuration for a given cell may be associated with a subgroup. The BWP switched on a particular CC may change the subgrouping of the co-scheduled CCs.

[0098] In some aspects, the MC-DCI may include an RRC parameter indicating which subgroups of co-scheduled CCs use the MCS index lookup table when the MC-DCI has an MCS-C-RNTI. In some aspects, the MC-DCI may include an RRC parameter for each CC in the co-scheduled CCs indicating which CCs use the MCS index lookup table when the MC-DCI has an MCS-C-RNTI. In some aspects, the antenna port field may indicate the antenna port value for two CWs and the value of the MCS index for a CC in the co-scheduled CC where both CWs are not disabled, or the antenna port field may indicate the antenna port value for one CW of a CC in the co-scheduled CC where the CW is disabled. In some aspects, the MCS for the CC in which the CW is disabled and the antenna port value for the CC in which the CW is disabled may be configured via RRC signaling for each value of the antenna port field.

[0099] As shown in reference numeral 604, the UE and / or the network node may perform transmission based at least in part on the scheduling information indicated by the MC-DCI. For example, the UE may send an uplink transmission to the network node based at least in part on the scheduling information indicated by the MC-DCI. The uplink transmission may be a PUSCH transmission. As another example, the network node may send a downlink transmission to the UE based at least in part on the scheduling information indicated by the MC-DCI. The downlink transmission may be a PDSCH transmission.

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

[0101] Figure 7 is a diagram illustrating an example 700 associated with communicating MC-DCI according to the present disclosure.

[0102] like Figure 7 As shown in , MC-DCI may be associated with co-scheduled CCs. Co-scheduled CCs may be associated with different bandwidths. Some of the co-scheduled CCs may be associated with continuous bandwidths. Some of the co-scheduled CCs may be associated with non-contiguous bandwidths. MC-DCI may indicate fields that are commonly applicable to co-scheduled CCs, such as an antenna port field and / or an MCS field.

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

[0104] Figure 8is a diagram illustrating an example 800 associated with communicating MC-DCI according to the present disclosure.

[0105] like Figure 8 As shown in , for co-scheduled CCs, if configured, the Mcs-TableDCI-1-X RRC parameter may be set to the same value from 'qam1024', 'qam256', 'qam64LowSE', or the Mcs-TableDCI-1-XRRC parameter may not be configured for any of the co-scheduled CCs. When the Mcs-TableDCI-1-XRRC parameter is defined as a per-CC parameter, if configured, the Mcs-TableDCI-1-X RRC parameter for each of the co-scheduled CCs may be set to the same value, and if not configured for any of the co-scheduled CCs, the Mcs-TableDCI-1-X RRC parameter may not be configured for all of the co-scheduled CCs in the co-scheduled CCs.

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

[0107] Fig. 9 is a diagram illustrating an example 900 associated with communicating MC-DCI according to the present disclosure.

[0108] As shown in reference numeral 902, the MC-DCI may indicate a field for a first subgroup (or a set of fields for the first subgroup). The MC-DCI may indicate the same field for a second subgroup (or the same set of fields for the second subgroup). The first subgroup may be associated with a first set of co-scheduled CCs, and the second subgroup may be associated with a second set of co-scheduled CCs. The common indication field may be applicable to the co-scheduled CCs associated with the first subgroup, and the common indication field may be applicable to the co-scheduled CCs associated with the second subgroup.

[0109] As shown by reference numeral 904, the MC-DCI may be associated with a first subgroup of co-scheduled CCs and a second subgroup of co-scheduled CCs. The first subgroup may be associated with co-scheduled CCs of similar bandwidth. The second subgroup may be associated with co-scheduled CCs of similar bandwidth. The bandwidth of the CCs associated with the first subgroup may be different in size than the bandwidth of the CCs associated with the second subgroup.

[0110] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9The examples described are different.

[0111] Fig.10 is a diagram illustrating an example 1000 associated with communicating MC-DCI according to the present disclosure.

[0112] like Fig.10 As shown in , the first subgroup may be associated with CC1 and CC2. CC1 may be associated with BWP1, BWP2, and BWP3. CC2 may be associated with BWP1, BWP2, and BWP3. The second subgroup may be associated with CC3 and CC4. CC3 may be associated with BWP1, BWP2, and BWP3. CC4 may be associated with BWP1, BWP2, and BWP3. BWPs may be dynamically switched on each CC, but BWP switching may not change the subgroups (e.g., the network may ensure that BWP switching does not change the subgroups).

[0113] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 The examples described are different.

[0114] Fig.11 is a diagram illustrating an example 1100 associated with communicating MC-DCI according to the present disclosure.

[0115] like Fig.11 As shown in , the first subgroup can be associated with CC1 and CC2. CC1 and CC2 can each be associated with BWP1. The second subgroup can be associated with CC3 and CC4. CC3 and CC4 can each be associated with BWP1. BWP switching on CC2 can dynamically change the subgrouping. After BWP switching, the first subgroup can be associated with CC1, and the second subgroup can be associated with CC2, CC3, and CC4. CC2 can be associated with BWP2, and CC3 and CC4 can each be associated with BWP1.

[0116] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 The examples described are different.

[0117] In some aspects, when MCS-C-RNTI is configured and when the CRC of a DCI format is scrambled with MCS-C-RNTI, the UE may consider a certain lookup table to be used (e.g., the MCS table from TS 5.1.3.1-3). When MCS-C-RNTI is configured but the CRC of a DCI format is scrambled with C-RNTI, the UE may consider another lookup table to be used (e.g., the MCS table from TS 5.1.3.1-1 / 2 / 4). The CRC scrambled RNTI may dynamically indicate which MCS table (e.g., the MCS table from TS 5.1.3.1-3 vs. the MCS table from TS 5.1.3.1-1 / 2 / 4) will be used for the data. The MCS table may be common to all CCs co-scheduled by MC-DCI.

[0118] In some aspects, when there are more than one subgroup for CCs co-scheduled by MC-DCI, MCS alignment can be within a subgroup rather than across subgroups. Therefore, the MCS table determination by the RNTI that scrambles the CRC can also be based on the subgroup. For example, when the MC-DCI has a CRC scrambled by MCS-C-RNTI, the lookup table from TS 5.1.3.1-3 can be used for co-scheduled CCs in one subgroup, but another lookup table from TS 5.1.3.1-1 / 2 / 4 can be used for CCs in other subgroups. In some aspects, an RRC parameter can be added to indicate which subgroup(s) the lookup table from TS 5.1.3.1-3 can be used for when the MC-DCI has an MCS-C-RNTI. For other subgroups, even when the MC-DCI has an MCS-C-RNTI, the configured lookup table from TS 5.1.3.1-1 / 2 / 4 can be used. In some aspects, an RRC parameter may be added for each CC to indicate for which CC(s) the lookup table from TS 5.1.3.1-3 may be used when the MC-DCI has an MCS-C-RNTI. Regardless of which subgroup the CC is associated with, the MCS table for the CC may be from TS 5.1.3.1-3 or TS 5.1.3.1-1 / 2 / 4 depending on this RRC parameter and whether the MC-DCI has an MCS-C-RNTI or a C-RNTI.

[0119] In the legacy DCI, when MCS=26 and RV=1 for a TB, one of the CWs / TBs may be disabled by the DCI. For MC-DCI, the MCS field may be common for the CWs used for the CCs in the subgroup, and the RV may be independent for each CW used for each CC. A specific combination of {MCS, RV} for the CWs used for the CCs in the subgroup may indicate the corresponding CW for the disabled CC (e.g., MCS=26 and RV=1 or 2). However, for CCs that do not disable CWs, the MCS for the CWs may be automatically fixed to a specific value (e.g., 26). In addition, the antenna port may be common to all CCs in the subgroup, so the values ​​indicating the CC for which one of the CWs is disabled and the CC for which both CWs are enabled may be difficult to operate.

[0120] Fig.12 is a diagram illustrating an example 1200 associated with communicating MC-DCI according to the present disclosure.

[0121] like Fig.12 As shown in , the first subgroup can be associated with the first CC and the second CC. For the first CW, the MCS can be associated with the first CC and the second CC, the first RV can be associated with the first CC, and the second RV can be associated with the second CC. For the second CW, the MCS can be associated with the first CC and the second CC, the first RV can be associated with the first CC, and the second RV can be associated with the second CC. The second subgroup can have a similar structure compared to the first subgroup. In a specific example, in the first subgroup, the MCS associated with the second CW can correspond to MCS=26, and the second RV associated with the second CW and the second CC can correspond to RV=1. In this case, the corresponding CW for the second CC can be disabled.

[0122] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 The examples described are different.

[0123] In some aspects, a specific combination of {MCS, RV} for a CC in a subgroup may indicate a corresponding CW (e.g., a second CW) for a disabled CC (e.g., MCS=26 and RV=1 or 2). The antenna port field for a CC of a subgroup may be interpreted in various ways. For a CC in which both CWs are not disabled, the antenna port field may indicate antenna port values ​​for both CWs, and the antenna port field may also indicate the value of the MCS index. For a CC in which a CW is disabled, the antenna port field may indicate an antenna port value for one CW. The MCS for a CC in which a CW is not disabled and the antenna port value for a CC in which a CW is disabled may be configured by RRC signaling for each value of the antenna port field.

[0124] Fig.13 is a diagram illustrating an example 1300 associated with communicating MC-DCI according to the present disclosure.

[0125] like Fig.13 As shown in , a specific combination of {MCS, RV} for CCs in a subgroup may indicate that the corresponding CW (e.g., the second CW) for the CC is disabled (e.g., MCS=26 and RV=1 or 2). In the antenna port field for the CCs of the subgroup, the value may correspond to the antenna port value for the CC with two CWs (e.g., 0, 1, 2, or 3), the MCS value (e.g., MCS index) for the CW for the CC in which the corresponding CW is not disabled, and the antenna port value for the other CWs of the CC in which the corresponding CW is disabled. Therefore, for the antenna port field for the CCs of the subgroup, the MCS for the CC in which the CW is not disabled and the antenna port value for the CC in which the CW is disabled may be configured by the RRC for each value of the antenna port field.

[0126] As indicated above, Fig.13 are provided as examples. Other examples can be found in the Fig.13 The examples described are different.

[0127] Fig.14 is a diagram illustrating an example process 1400 performed, for example, by a UE in accordance with the present disclosure. Example process 1400 is an example in which a UE (eg, UE 120) performs operations associated with communicating MC-DCI.

[0128] like Fig.14 As shown in FIG. 14 , in some aspects, process 1400 may include receiving, from a network node, an MC-DCI indicating scheduling information for co-scheduled CCs, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs (block 1410). For example, a UE (e.g., using Fig.16 The receiving component 1602 depicted in the figure can receive an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of antenna port fields or MCS fields of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs, as described above.

[0129] like Fig.14 As further shown in FIG. 14 , in some aspects, process 1400 may include performing transmission based at least in part on scheduling information indicated by the MC-DCI (block 1420). For example, a UE (e.g., using Fig.16 The receiving component 1602 and / or the sending component 1604 depicted in the figure can perform transmission based at least in part on the scheduling information indicated by the MC-DCI, as described above.

[0130] Process 1400 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.

[0131] In a first aspect, the co-scheduled CCs are associated with one or more of the same number of codewords, the same DMRS type, the same maximum length, and the same number of TCI states per TCI codepoint, and the antenna port field for the co-scheduled CCs is a common lookup table for the co-scheduled CCs.

[0132] In a second aspect, alone or in combination with the first aspect, the MCS table DCI RRC parameters are set to QAM 1024, QAM 256 or QAM 64 low spectral efficiency for the co-scheduled CCs, or the MCS table DCI RRC parameters are not configured for any of the co-scheduled CCs.

[0133] In a third aspect, alone or in combination with one or more of the first and second aspects, an MCS table DCI RRC parameter is defined as a per-CC parameter, and the same MCS table DCI RRC parameter is associated with each of the co-scheduled CCs.

[0134] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the MC-DCI indicates one or more of antenna port fields or MCS fields for a first subgroup and a second subgroup, wherein the first subgroup is associated with a first CC subset in a co-scheduled CC, and the second subgroup is associated with a second CC subset in a co-scheduled CC.

[0135] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the MC-DCI indication is applicable to a common indication field of a subset of co-scheduled CCs associated with a subgroup in a co-scheduled CC, and different bits in the MC-DCI are used for subsets of co-scheduled CCs in different subgroups.

[0136] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, a subset of the co-scheduled CCs in the subgroup among the co-scheduled CCs are associated with the same RRC parameters.

[0137] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the subgrouping of the co-scheduled CCs is at least partially based on dedicated RRC parameters, and the UE uses the dedicated RRC parameters to configure an association between each co-scheduled CC in the co-scheduled CCs and each subgroup.

[0138] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the subgrouping of the co-scheduled CCs is based at least in part on whether the co-scheduled CCs are associated with the same antenna port field or MCS field.

[0139] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the subgrouping of the co-scheduled CCs is a cell-level subgrouping, wherein multiple bandwidth portion configurations for a given cell are associated with the subgroups, and the BWP is switchable on each CC without changing the subgrouping of the co-scheduled CCs.

[0140] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the subgrouping of co-scheduled CCs is a BWP-level subgrouping, wherein each BWP configuration for a given cell is associated with a subgroup, and BWP switching on a particular CC changes the subgrouping of the co-scheduled CCs.

[0141] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the MC-DCI includes an RRC parameter indicating which subgroups of co-scheduled CCs use the MCS index lookup table when the MC-DCI has an MCS-C-RNTI, or the MC-DCI includes an RRC parameter for each CC in the co-scheduled CCs, indicating which CCs use the MCS index lookup table when the MC-DCI has an MCS-C-RNTI.

[0142] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the antenna port field indicates antenna port values ​​for two codewords and the value of the MCS index for a CC in which both codewords are not disabled in a co-scheduled CC, or the antenna port field indicates an antenna port value for a codeword of a CC in which a codeword is disabled in a co-scheduled CC.

[0143] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the MCS for a CC in which codewords are disabled and the antenna port value for a CC in which codewords are disabled are configured via RRC signaling for each value of the antenna port field.

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

[0145] Fig.15 is a diagram illustrating an example process 1500, performed, for example, by a network node, in accordance with the present disclosure. Example process 1500 is an example in which a network node (eg, network node 110) performs operations associated with communicating MC-DCI.

[0146] like Fig.15 As shown in FIG. 1 , in some aspects, process 1500 may include sending an MC-DCI indicating scheduling information for co-scheduled CCs to a UE, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs (block 1510). For example, a network node (e.g., using Fig.17 The sending component 1704 depicted in the figure can send an MC-DCI indicating scheduling information for co-scheduled CCs to the UE, wherein the MC-DCI indicates one or more of the antenna port fields or the MCS fields of one or more co-scheduled CCs to be commonly applied to the co-scheduled CCs, as described above.

[0147] like Fig.15 As further shown in FIG. 1 , in some aspects, process 1500 may include performing transmission based at least in part on scheduling information indicated by the MC-DCI (block 1520). For example, a network node (e.g., using Fig.17 The receiving component 1702 and / or the sending component 1704 depicted in the figure can perform transmission based at least in part on the scheduling information indicated by the MC-DCI, as described above.

[0148] Process 1500 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.

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

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

[0151] In some aspects, the apparatus 1600 may be configured to perform the Figures 6 to 13 Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Fig.14 The process 1400. In some aspects, Fig.16 The device 1600 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.16 One or more of the components shown in the figure 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.

[0152] The receiving component 1602 may receive communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 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 1600. In some aspects, the receiving component 1602 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0153] The transmitting component 1604 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1606. In some aspects, one or more other components of the device 1600 may generate communications and may provide the generated communications to the transmitting component 1604 for transmission to the device 1606. In some aspects, the transmitting component 1604 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 1606. In some aspects, the transmitting component 1604 may include a combination of 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 1604 can be co-located with the receive component 1602 in a transceiver.

[0154] The receiving component 1602 may receive an MC-DCI indicating scheduling information for co-scheduled CCs from a network node, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs. The receiving component 1602 and / or the transmitting component 1604 may perform the transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0155] Fig.16 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.16 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.16 Two or more components shown in the figure may be implemented in a single component, or Fig.16The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig.16 One or more functions performed by another set of components shown in the figure.

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

[0157] In some aspects, the apparatus 1700 may be configured to perform the Figures 6 to 13 Additionally or alternatively, the apparatus 1700 may be configured to perform one or more processes described herein, such as Fig.15 The process 1500. In some aspects, Fig.17 The apparatus 1700 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.17 One or more of the components shown in the figure 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.

[0158] The receiving component 1702 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1706. The receiving component 1702 may provide the received communications to one or more other components of the apparatus 1700. In some aspects, the receiving component 1702 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 apparatus 1700. In some aspects, the receiving component 1702 may include combining Figure 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0159] The transmitting component 1704 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1706. In some aspects, one or more other components of the device 1700 may generate communications and may provide the generated communications to the transmitting component 1704 for transmission to the device 1706. In some aspects, the transmitting component 1704 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 1706. In some aspects, the transmitting component 1704 may include a combination of 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 1704 can be co-located with the receive component 1702 in a transceiver.

[0160] The transmitting component 1704 may transmit to the UE an MC-DCI indicating scheduling information for the co-scheduled CCs, wherein the MC-DCI indicates one or more of an antenna port field or an MCS field to be commonly applied to one or more of the co-scheduled CCs. The receiving component 1702 and / or the transmitting component 1704 may perform the transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0161] Fig.17 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.17 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.17 Two or more components shown in the figure may be implemented in a single component, or Fig.17 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.17 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig.17 One or more functions performed by another set of components shown in the figure.

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

[0163] Aspect 1: A method of wireless communication performed by a user equipment (UE) includes: receiving multi-cell downlink control information (MC-DCI) indicating scheduling information for a co-scheduled component carrier (CC) from a network node, wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and performing transmission based at least in part on the scheduling information indicated by the MC-DCI.

[0164] Aspect 2: A method according to Aspect 1, wherein the co-scheduled CCs are associated with one or more of: the same number of codewords, the same demodulation reference signal type, the same maximum length, and the same number of transmit configuration indication (TCI) states per TCI code point, and wherein the antenna port field for the co-scheduled CCs is a common lookup table for the co-scheduled CCs.

[0165] Aspect 3: A method according to any one of Aspects 1 to 2, wherein: the MCS table downlink control information (DCI) radio resource control (RRC) parameters are set to quadrature amplitude modulation (QAM) 1024, QAM256 or QAM 64 low spectrum efficiency for the co-scheduled CCs; or the MCS table DCI RRC parameters are not configured for any co-scheduled CCs among the co-scheduled CCs.

[0166] Aspect 4: A method according to any one of Aspects 1 to 3, wherein an MCS table downlink control information (DCI) radio resource control (RRC) parameter is defined as a per-CC parameter, and the same MCS table DCI RRC parameter is associated with each of the co-scheduled CCs.

[0167] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the MC-DCI indicates one or more of the antenna port field or the MCS field for a first subgroup and a second subgroup, wherein the first subgroup is associated with a first CC subset in the co-scheduled CCs, and the second subgroup is associated with a second CC subset in the co-scheduled CCs.

[0168] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the MC-DCI indication is a common indication field applicable to a subset of the co-scheduled CCs associated with a subgroup in the co-scheduled CCs, and wherein different bits in the MC-DCI are used for subsets of the co-scheduled CCs in different subgroups.

[0169] Aspect 7: The method according to any one of aspects 1 to 6, wherein a subset of the co-scheduled CCs in the subgroup among the co-scheduled CCs are associated with the same radio resource control parameters.

[0170] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the subgrouping of the co-scheduled CCs is at least partially based on dedicated radio resource control (RRC) parameters, and wherein the UE uses the dedicated RRC parameters to configure an association between each co-scheduled CC in the co-scheduled CCs and each subgroup.

[0171] Aspect 9: The method according to any one of aspects 1 to 8, wherein the subgrouping of the co-scheduled CCs is based at least in part on whether the co-scheduled CCs are associated with the same antenna port field or MCS field.

[0172] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the subgrouping of the co-scheduled CCs is a cell-level subgrouping, wherein multiple bandwidth portion configurations for a given cell are associated with the subgroups, and wherein the BWP can be switched on each CC without changing the subgrouping of the co-scheduled CCs.

[0173] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the subgrouping of the co-scheduled CCs is a bandwidth part (BWP) level subgrouping, wherein each BWP configuration for a given cell is associated with a subgroup, and wherein BWP switching on a specific CC changes the subgrouping of the co-scheduled CCs.

[0174] Aspect 12: A method according to any one of Aspects 1 to 11, wherein: the MC-DCI includes a radio resource control (RRC) parameter, the radio resource control (RRC) parameter indicating which subgroups of co-scheduled CCs use the MCS index lookup table when the MC-DCI has an MCS cell radio network temporary identifier (MCS-C-RNTI); or the MC-DCI includes an RRC parameter for each CC in the co-scheduled CCs, the RRC parameter indicating which CCs use the MCS index lookup table when the MC-DCI has the MCS-C-RNTI.

[0175] Aspect 13: A method according to any one of Aspects 1 to 12, wherein: the antenna port field indicates antenna port values ​​for two codewords and the value of the MCS index for a CC in which both codewords are not disabled in the co-scheduled CCs; or the antenna port field indicates the antenna port value for a codeword of a CC in which the codewords are disabled in the co-scheduled CCs.

[0176] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the MCS for a CC in which codewords are disabled and the antenna port value for the CC in which the codewords are disabled are configured via radio resource control signaling for each value of the antenna port field.

[0177] Aspect 15: A method of wireless communication performed by a network node, comprising: sending multi-cell downlink control information (MC-DCI) indicating scheduling information for a co-scheduled component carrier (CC) to a user equipment (UE), wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and performing the sending at least in part based on the scheduling information indicated by the MC-DCI.

[0178] Aspect 16: An apparatus for wireless communication at a device, 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 14.

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

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

[0181] Aspect 19: 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 14.

[0182] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, 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 14.

[0183] Aspect 21: An apparatus for wireless communication at a device, 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 the method according to Aspect 15.

[0184] Aspect 22: An apparatus for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to aspect 15.

[0185] Aspect 23: An apparatus for wireless communication, comprising: at least one component for performing the method according to aspect 15.

[0186] Aspect 24: 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 aspect 15.

[0187] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to aspect 15.

[0188] 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 are possible in light of the above disclosure or may be acquired from practice of these aspects.

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

[0190] In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "group" are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with "one or more". If only one item 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 can 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").

[0191] The various illustrative logics, logic 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.

[0192] 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. A 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.

[0193] 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 (e.g., 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.

[0194] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via 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.

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

[0196] 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 corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the correct orientation of any device as implemented.

[0197] 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 sub-combination. 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 sub-combination, or a variation of a sub-combination.

[0198] 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), comprising: receiving multi-cell downlink control information (MC-DCI) indicating scheduling information for co-scheduled component carriers (CCs) from a network node, wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and Transmitting is performed based at least in part on the scheduling information indicated by the MC-DCI.

2. The method of claim 1 , wherein the co-scheduled CCs are associated with one or more of: the same number of codewords, the same demodulation reference signal type, the same maximum length, and the same number of transmit configuration indication (TCI) states per TCI code point, and wherein the antenna port field for the co-scheduled CCs is a common lookup table for the co-scheduled CCs.

3. The method according to claim 1, wherein: The MCS table downlink control information (DCI) radio resource control (RRC) parameters are set to quadrature amplitude modulation (QAM) 1024, QAM 256 or QAM 64 low spectral efficiency for the co-scheduled CC; or The MCS table DCI RRC parameters are not configured for any of the co-scheduled CCs.

4. The method of claim 1 , wherein an MCS table downlink control information (DCI) radio resource control (RRC) parameter is defined as a per-CC parameter, and the same MCS table DCI RRC parameter is associated with each of the co-scheduled CCs.

5. The method of claim 1 , wherein the MC-DCI indicates one or more of the antenna port field or the MCS field for a first subgroup and a second subgroup, wherein the first subgroup is associated with a first CC subset in the co-scheduled CCs, and the second subgroup is associated with a second CC subset in the co-scheduled CCs.

6. The method of claim 1, wherein the MC-DCI indicates a common indication field applicable to a subset of the co-scheduled CCs associated with a sub-group in the co-scheduled CCs, and wherein different bits in the MC-DCI are used for subsets of the co-scheduled CCs in different sub-groups. 7 . The method of claim 1 , wherein a subset of the co-scheduled CCs in a subgroup of the co-scheduled CCs are associated with the same radio resource control parameters.

8. The method of claim 1 , wherein the subgrouping of the co-scheduled CCs is based at least in part on dedicated radio resource control (RRC) parameters, and wherein the UE is configured with an association between each of the co-scheduled CCs and each subgroup using the dedicated RRC parameters.

9. The method of claim 1, wherein the subgrouping of the co-scheduled CCs is based at least in part on whether the co-scheduled CCs are associated with the same antenna port field or MCS field.

10. The method of claim 1, wherein the subgrouping of the co-scheduled CCs is a cell-level subgrouping, wherein multiple bandwidth portion configurations for a given cell are associated with a subgroup, and wherein a BWP is switchable on each CC without changing the subgrouping of the co-scheduled CCs.

11. The method of claim 1 , wherein the subgrouping of the co-scheduled CCs is a bandwidth part (BWP) level subgrouping, wherein each BWP configuration for a given cell is associated with a subgroup, and wherein a BWP switching on a particular CC changes the subgrouping of the co-scheduled CCs.

12. The method of claim 1, wherein: The MC-DCI includes a radio resource control (RRC) parameter indicating which subsets of co-scheduled CCs to use an MCS index lookup table for when the MC-DCI has an MCS cell radio network temporary identifier (MCS-C-RNTI); or The MC-DCI includes an RRC parameter for each of the co-scheduled CCs, the RRC parameter indicating for which CCs the MCS index lookup table is used when the MC-DCI has the MCS-C-RNTI.

13. The method of claim 1, wherein: The antenna port field indicates an antenna port value for two codewords and a value of an MCS index for a CC in which both codewords are not disabled in the co-scheduled CCs; or The antenna port field indicates an antenna port value used for a codeword of a CC whose codeword is disabled in the co-scheduled CC.

14. The method of claim 1, wherein an MCS for a CC in which a codeword is disabled and an antenna port value for the CC in which the codeword is disabled are configured via radio resource control signaling for each value of the antenna port field.

15. A method of wireless communication performed by a network node, comprising: sending multi-cell downlink control information (MC-DCI) indicating scheduling information for co-scheduled component carriers (CCs) to a user equipment (UE), wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and Transmitting is performed based at least in part on the scheduling information indicated by the MC-DCI.

16. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and one or more processors coupled to the memory and configured to: receiving multi-cell downlink control information (MC-DCI) indicating scheduling information for co-scheduled component carriers (CCs) from a network node, wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and Transmitting is performed based at least in part on the scheduling information indicated by the MC-DCI.

17. The apparatus of claim 16, wherein the co-scheduled CCs are associated with one or more of: a same number of codewords, a same demodulation reference signal type, a same maximum length, and a same number of transmit configuration indication (TCI) states per TCI code point, and wherein the antenna port field for the co-scheduled CCs is a common lookup table for the co-scheduled CCs.

18. The apparatus of claim 16, wherein: The MCS table downlink control information (DCI) radio resource control (RRC) parameters are set to quadrature amplitude modulation (QAM) 1024, QAM 256 or QAM 64 low spectral efficiency for the co-scheduled CC; or The MCS table DCI RRC parameters are not configured for any of the co-scheduled CCs.

19. The apparatus of claim 16, wherein an MCS table downlink control information (DCI) radio resource control (RRC) parameter is defined as a per-CC parameter, and the same MCS table DCI RRC parameter is associated with each of the co-scheduled CCs.

20. The apparatus of claim 16, wherein the MC-DCI indicates one or more of the antenna port field or the MCS field for a first subgroup and a second subgroup, wherein the first subgroup is associated with a first CC subset of the co-scheduled CCs, and the second subgroup is associated with a second CC subset of the co-scheduled CCs.

21. The apparatus of claim 16, wherein the MC-DCI indicates a common indication field applicable to a subset of the co-scheduled CCs associated with a sub-group in the co-scheduled CCs, and wherein different bits in the MC-DCI are used for subsets of the co-scheduled CCs in different sub-groups.

22. The apparatus of claim 16, wherein a subset of the co-scheduled CCs in a subgroup of the co-scheduled CCs are associated with the same radio resource control parameters.

23. The apparatus of claim 16, wherein the subgrouping of the co-scheduled CCs is based at least in part on dedicated radio resource control (RRC) parameters, and wherein the UE is configured with an association between each of the co-scheduled CCs and each subgroup using the dedicated RRC parameters.

24. The apparatus of claim 16, wherein the subgrouping of the co-scheduled CCs is based at least in part on whether the co-scheduled CCs are associated with the same antenna port field or MCS field.

25. The apparatus of claim 16, wherein the subgrouping of the co-scheduled CCs is a cell-level subgrouping, wherein multiple bandwidth portion configurations for a given cell are associated with a subgroup, and wherein a BWP is switchable on each CC without changing the subgrouping of the co-scheduled CCs.

26. The apparatus of claim 16, wherein the subgrouping of the co-scheduled CCs is a bandwidth part (BWP) level subgrouping, wherein each BWP configuration for a given cell is associated with a subgroup, and wherein a BWP switching on a particular CC changes the subgrouping of the co-scheduled CCs.

27. The apparatus of claim 16, wherein: The MC-DCI includes a radio resource control (RRC) parameter indicating which subsets of co-scheduled CCs to use an MCS index lookup table for when the MC-DCI has an MCS cell radio network temporary identifier (MCS-C-RNTI); or The MC-DCI includes an RRC parameter for each of the co-scheduled CCs, the RRC parameter indicating for which CCs the MCS index lookup table is used when the MC-DCI has the MCS-C-RNTI.

28. The apparatus of claim 16, wherein: The antenna port field indicates an antenna port value for two codewords and a value of an MCS index for a CC in which both codewords are not disabled in the co-scheduled CCs; or The antenna port field indicates an antenna port value used for a codeword of a CC whose codeword is disabled in the co-scheduled CC.

29. The apparatus of claim 16, wherein an MCS for a CC in which codewords are disabled and an antenna port value for the CC in which the codewords are disabled are configured via radio resource control signaling for each value of the antenna port field.

30. An apparatus for wireless communication at a network node, comprising: Memory; and one or more processors coupled to the memory and configured to: sending multi-cell downlink control information (MC-DCI) indicating scheduling information for co-scheduled component carriers (CCs) to a user equipment (UE), wherein the MC-DCI indicates one or more of an antenna port field or a modulation and coding scheme (MCS) field to be commonly applied to one or more of the co-scheduled CCs; and Transmitting is performed based at least in part on the scheduling information indicated by the MC-DCI.

Images