Downlink control information format for multi-cell scheduling

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a multi-cell scheduling downlink control information (DCI) communication that includes a co-scheduling cell indicator field that indicates one or more cells scheduled through the DCI communication. The UE may identify a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 18 / 168,942, filed on February 14, 2023, entitled “DOWNLINK CONTROLINFORMATION FORMAT FOR MULTI-CELL SCHEDULING,” and assigned to the assignee of the present application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for downlink control information formats for multi-cell scheduling. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting 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 communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned 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, regional, and / or global level. New Radio (NR) (which may 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: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a multi-cell scheduled downlink control information (DCI) communication including a co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication. The method may include identifying a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication to a UE. The method may include sending the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a multi-cell scheduled DCI communication including a co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication. The one or more processors may be configured to identify a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to: send a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication to a UE. The one or more processors may be configured to: send the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a multi-cell scheduled DCI communication including a co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to identify a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication to a UE. The set of instructions, when executed by one or more processors of the network node, may cause the network node to send the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a multi-cell scheduled DCI communication including a co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication. The apparatus may include means for identifying a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication to a UE. The apparatus may include means for sending the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

[0015] The various aspects collectively 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 accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in this disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0022] Figure 4 is a diagram illustrating an example of carrier aggregation according to the present disclosure.

[0023] Figures 5A to 5B is a diagram illustrating an example of downlink control information (DCI) scheduling a plurality of cells according to the present disclosure.

[0024] Figures 6A to 6G is a diagram illustrating an example associated with a DCI format for multi-cell scheduling according to the present disclosure.

[0025] Figure 7 is a diagram of another example associated with a DCI format for multi-cell scheduling according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0027] Figure 9 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0028] Figure 10 is a diagram of an example apparatus for wireless communications according to the present disclosure.

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

[0030] 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 interpreted as being limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Those skilled in the art will appreciate 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 that are practiced using other structures, functionality, or structure 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.

[0031] A network node may use downlink control information (DCI) to schedule communications with a user equipment (UE). For example, a network node may use DCI to schedule uplink data communications (such as communications using a physical uplink shared channel (PUSCH)) or downlink data communications (such as communications using a physical downlink shared channel (PDSCH)). In some cases, such as where the network node and / or UE operates in carrier aggregation mode, the network node may use a single DCI communication (sometimes referred to as a multi-cell scheduled DCI communication) to schedule multiple cells. The multi-cell scheduled DCI communication may include a co-scheduled cell indicator field that indicates a set of cells to be scheduled by the DCI communication (e.g., indicating a set of cells to be scheduled using PUSCH or PDSCH). In such cases, the number of cells that may be scheduled using a multi-cell scheduled DCI communication may vary, and therefore the size of the fields associated with the DCI communication may vary from one DCI communication to another. For example, a frequency domain resource allocation (FDRA) field associated with a DCI communication that schedules four cells may be larger (e.g., include more total bits) than an FDRA field associated with a DCI communication that schedules only two cells. Because the size of certain fields may vary, in some cases, a network node may need to signal one or more field sizes associated with a DCI communication to a UE, resulting in higher overhead; otherwise, the varying field sizes may cause communication errors, resulting in high power consumption, high computational resource consumption, and high network resource consumption for correcting the communication errors.

[0032] Certain techniques and apparatus described herein enable a UE to identify the bit width of one or more fields of a DCI communication without supplemental signaling from a network node, thereby reducing overhead and improving decoding of the DCI communication at the UE. In some aspects, a UE may receive a multi-cell scheduled DCI communication that includes a co-scheduled cell indicator field that indicates one or more cells scheduled by the DCI communication, and the UE may identify the bit width associated with a field of the DCI communication based at least in part on the configuration of the co-scheduled cell indicator field. For example, the UE may identify the bit width based at least in part on a necessary number of bits used for the field associated with the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells that maximizes the bit width of the field. In some aspects, when the set of cells indicated by the co-scheduled cell indicator is not a set of cells that maximizes the bit width of the field, the UE may determine the number of bits actually used for the field and / or the position of other fields in the DCI communication relative to the field based at least in part on the number of bits actually used for the field. Thus, the signaling overhead associated with the network node indicating to the UE certain bit widths for a given DCI communication may be reduced or eliminated, and / or communication errors caused by varying field sizes in multi-cell scheduled DCI communications may be reduced, thereby reducing the power consumption, computational resource consumption, and network resource consumption that would otherwise be required to correct communication errors.

[0033] 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, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terminology 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 post-5G (e.g., 6G) RATs.

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / 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 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (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), meaning 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)).

[0036] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged 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. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, 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 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0037] In some examples, 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 ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0038] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple 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 repeatedly perform 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 another base station function. In this way, a single device may include more than one base station.

[0039] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit 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 can relay 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, a relay, etc.

[0040] 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, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts 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).

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

[0042] UEs 120 may be dispersed throughout 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, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), 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 computer, 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 smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

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

[0044] 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. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. 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.

[0045] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can 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 can 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), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0046] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is 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).

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

[0048] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or 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, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0049] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a multi-cell scheduled DCI communication including a co-scheduled cell indicator field that indicates one or more cells scheduled by the DCI communication, and identify a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0050] In some aspects, the network node 110 may include a communications manager 150. As described in greater detail elsewhere herein, the communications manager 150 may transmit to a UE a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication; and transmit to the UE the multi-cell scheduled DCI communication including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

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

[0052] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. 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 radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0053] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. 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., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as 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 through 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, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit the set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0054] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / 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 through 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, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the 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, if 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 a 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, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

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

[0056] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0057] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the 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, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 6A to 11 ) any aspects of any of the methods described.

[0058] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, 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, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 6A to 11 ) any aspects of any of the methods described.

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with DCI formats for multi-cell scheduling, as described in more detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 8 The process of 800 Figure 9 900 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 / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Figure 9 The process 900 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.

[0060] In some aspects, the UE 120 includes: means for receiving a multi-cell scheduled DCI communication including a co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication; and / or means for identifying a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0061] In some aspects, the network node 110 includes: means for transmitting to a UE a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication; and / or means for transmitting to the UE the multi-cell scheduled DCI communication including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field. Means for the network node 110 to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

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

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

[0064] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, 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 known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "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).

[0065] A converged base station (e.g., a converged 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, the 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 spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and 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), among others.

[0066] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated 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 scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated 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. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0067] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that 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, 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.

[0068] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, 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 the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0069] In some aspects, the CU 310 may host one or more high-level 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, among others. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0070] 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, a DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher 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, a DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0071] Each RU 340 may implement low-layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as low-layer functional split), 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 communications 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).

[0072] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the 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 the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the 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.

[0073] The non-RT RIC 315 can 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 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and actions over 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.

[0074] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate the AI / ML model to be deployed in the near-RT RIC 325. Such information may be utilized by the near-RT RIC 325 and may be received from non-network data sources or from network functions 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 in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

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

[0076] Figure 4 is a diagram illustrating an example 400 of carrier aggregation according to the present disclosure.

[0077] Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers or cells) to be combined (e.g., into a single channel) for a single UE 120 to increase data capacity. As shown, carriers can be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers can be combined. Network node 110 can configure carrier aggregation for UE 120, such as in an RRC message, DCI, and / or another signaling message.

[0078] As indicated by reference numeral 405, in some aspects, carrier aggregation may be configured in an intra-band contiguous mode, where the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 410, in some aspects, carrier aggregation may be configured in an intra-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in the same frequency band. As indicated by reference numeral 415, in some aspects, carrier aggregation may be configured in an inter-band discontiguous mode, where the aggregated carriers are discontiguous with each other and in different frequency bands.

[0079] In carrier aggregation, a UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., DCI and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

[0080] In some aspects, a single DCI communication may be used to schedule communications on multiple cells, which is sometimes referred to as a multi-cell scheduled DCI communication. For example, a multi-cell scheduled DCI communication may be used to schedule PUSCH on up to four cells, and / or a multi-cell scheduled DCI communication may be used to schedule PDSCH on up to four cells. Figures 5A to 5B Various aspects of multi-cell scheduled DCI communications are described in more detail.

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

[0082] Figures 5A to 5B is a diagram illustrating an example 500 of scheduling DCI for multiple cells according to the present disclosure.As shown in FIG5 , a network node 110 and a UE 120 may communicate with each other (eg, directly or via one or more network nodes).

[0083] The network node 110 may send (e.g., directly or via one or more network nodes) to the UE 120 a multi-cell scheduling DCI 505 that schedules multiple communications for the UE 120. Multiple communications may be scheduled for one or more cells (e.g., one or more CCs). In some cases, DCI that schedules communications for the cell via which the DCI is sent may be referred to as self-carrier (or self-cell) scheduled DCI. In some cases, DCI that schedules communications for the cell via which the DCI is sent may be referred to as cross-carrier (or cross-cell) scheduled DCI. In some aspects, the multi-cell scheduling DCI 505 may be cross-carrier scheduling DCI and may or may not be self-carrier scheduling DCI. In some aspects, the multi-cell scheduling DCI 505 that carries communications in at least two cells may be referred to as combined DCI.

[0084] In example 500, the multi-cell scheduling DCI 505 schedules communications for a first cell 510 (shown as CC0) that carries the multi-cell scheduling DCI 505, the multi-cell scheduling DCI 505 schedules communications for a second cell 515 (shown as CC1) that does not carry the multi-cell scheduling DCI 505, and the multi-cell scheduling DCI 505 schedules communications for a third cell 520 (shown as CC2) that does not carry the multi-cell scheduling DCI 505. In some aspects, the multi-cell scheduling DCI 505 may schedule communications over a different number of cells than shown in FIG5 (e.g., two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0085] Communications scheduled by the multi-cell scheduling DCI 505 may include data communications, such as PDSCH communications or PUSCH communications. Multi-cell scheduling DCI 505 for scheduling PUSCH communications on up to four cells is sometimes referred to as DCI format 0_X communications (where "X" corresponds to a number yet to be determined, such that multi-cell scheduling DCI 505 for scheduling PUSCH communications may ultimately be referred to as DCI format 0_3, DCI format 0_4, etc.), and multi-cell scheduling DCI 505 for scheduling PDSCH communications on up to four cells is sometimes referred to as DCI format 1_X communications (where "X" again corresponds to a number yet to be determined, such that multi-cell scheduling DCI 505 for scheduling PDSCH communications may ultimately be referred to as DCI format 1_3, DCI format 1_4, etc.). For data communications, the multi-cell scheduling DCI 505 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs separately in multiple cells. Additionally or alternatively, communications scheduled by the multi-cell scheduling DCI 505 may include reference signals, such as a channel state information reference signal (CSI-RS) or a sounding reference signal (SRS). For reference signals, the multi-cell scheduling DCI 505 may trigger a single resource for reference signal transmission across multiple cells, or may separately schedule multiple resources for reference signal transmission in multiple cells. In some cases, scheduling information in the multi-cell scheduling DCI 505 may be indicated once and reused for multiple communications (e.g., on different cells), such as the MCS, resources to be used for acknowledgment (ACK) or negative acknowledgment (NACK) of communications scheduled by the multi-cell scheduling DCI 505, and / or resource allocations for the scheduled communications, to save signaling overhead.

[0086] Additionally or alternatively, some fields of the multi-cell scheduling DCI 505 may indicate that individual information for each cell is scheduled via the multi-cell scheduling DCI 505 (sometimes referred to as per-cell fields), some fields of the multi-cell scheduling DCI 505 may indicate that common information applicable to all cells is scheduled via the multi-cell scheduling DCI 505 (sometimes referred to as single fields), and some fields may be configurable between per-cell fields and single fields. For example, the FDRA field of the multi-cell scheduling DCI 505 may be a per-cell field, meaning that separate FDRA information may be indicated for each cell being scheduled via the multi-cell scheduling DCI 505. Similarly, the MCS field, the new data indicator (NDI) field, the redundancy version (RV) field, and / or the hybrid automatic repeat request (HARQ) process number field may be per-cell fields. Furthermore, the antenna port field may be configurable between a per-cell field and a single field.

[0087] In some examples, the multi-cell scheduling DCI 505 may include additional individual fields, such as a bandwidth part (BWP) indicator field, a time domain resource allocation (TDRA) field, a virtual resource block (VRB) to physical resource block (PRB) mapping field, a PRB bundling size field, a rate matching indicator field, a zero power (ZP) CSI-RS trigger field, a transmit configuration indicator (TCI) field, a DMRS sequence initialization field, an SRS request field, an SRS offset field, a frequency hopping (FH) flag field, an open loop power control (OLPC) field, and / or an uplink (UL) / supplementary UL (SUL) indicator field, etc. Additionally or alternatively, the multi-cell scheduling DCI 505 may include additional per-cell fields, such as a PUSCH transmit power control (TPC) field, a phase tracking reference signal (PTRS)-DMRS association field, and / or a UL / SUL indicator field, etc. Additionally or alternatively, the multi-cell scheduling DCI 505 may include additional fields configurable between the single field and the per-cell field, such as precoding and number of layers fields and / or an SRS resource indicator field, etc.

[0088] like Figure 5B As shown, in some examples, the multi-cell scheduling DCI 505 may include a co-scheduled cell indicator field 530. In some examples, the co-scheduled cell indicator field 530 may indicate a code point corresponding to a subset of cells scheduled by the multi-cell scheduling DCI 505, where the subset of cells is equal to one or more cells in a configured set of cells (including, in some aspects, all cells in the configured set of cells) that may potentially be scheduled by the multi-cell scheduling DCI 505. For example, the UE 120 may be configured with a table 535 or similar information that associates various code points with one or more cells in a configured set of cells (such as cell #1, cell #2, cell #3, and cell #4). Figure 5BIn the example shown, table 535 may associate code point 00 with a first subset of the cell set (e.g., cell #1 and cell #2), code point 01 with a second subset of the cell set (e.g., cell #3 and cell #4), code point 10 with a third subset of the cell set (e.g., cell #1, cell #2, and cell #3), and code point 11 with a fourth subset of the cell set (e.g., cell #1, cell #2, cell #3, and cell #4). In other words, in some examples, for a cell set configured for multi-cell scheduling (e.g., cell #1, cell #2, cell #3, and cell #4), the subset of cells co-scheduled by the multi-cell scheduling DCI 505 may be indicated by a co-scheduled cell indicator field 530 in the multi-cell scheduling DCI 505 (e.g., DCI format 0_X and / or DCI format 1_X), where the co-scheduled cell indicator field 530 points to a row of a table defining a combination of co-scheduled cells for the cell set. In some cases, table 535 may be configured for the set of cells via RRC signaling. Additionally, the size of the co-scheduled cell indicator field 530 may be determined based at least in part on the number of rows in the table. Figure 5B In the example depicted in FIG, table 535 includes four rows (eg, four combinations of co-scheduled cells for the cell set), and thus the size of the co-scheduled cell indicator field 530 may be two bits (eg, ) to indicate one of four possible subsets of cells. More generally, for a table comprising M rows and / or entries, the size of the corresponding co-scheduled cell indicator field may be equal to

[0089] In some aspects, the size of one or more per-cell fields of the multi-cell scheduling DCI 505 and / or the number of bits actually used within one or more per-cell fields of the multi-cell scheduling DCI 505 may vary depending on the configuration of the co-scheduled cell indicator field 530 and / or the number of cells scheduled by the multi-cell scheduling DCI 505. More specifically, Figure 5BIn the example shown, a per-cell field (such as an FDRA field or the like) of the multi-cell scheduling DCI 505 may need to be large enough to indicate FDRA information for up to four cells (corresponding to the subset of cells including cell #1, cell #2, cell #3, and cell #4). However, in examples where the multi-cell scheduling DCI 505 schedules fewer than four cells (e.g., when the co-scheduled cell indicator field 530 indicates one of codepoint 00, codepoint 01, or codepoint 10), the number of bits used for this field may be less than the bit width of the entire field. Furthermore, in aspects where the UE 120 is configured with a table that includes only a proper subset of the set of cells (e.g., where each possible combination of co-scheduled cells is less than all of cell #1, cell #2, cell #3, and cell #4), the bit width of a per-cell field (such as an FDRA field or the like) of the multi-cell scheduling DCI 505 may be less than that in the example described above, in which up to four cells may be co-scheduled, because the field only needs to be large enough to indicate FDRA information for fewer than four cells. This variation in the bit width of certain per-cell fields and / or the number of bits used for certain per-cell fields may require high signaling overhead associated with the network node 110 indicating certain bit widths to be used for a given DCI communication to the UE 120, which may otherwise result in communication errors between the network node 110 and the UE 120, and thus may result in high power consumption, high computational resource consumption, and high network resource consumption to correct the communication errors.

[0090] Some techniques and apparatus described herein enable a UE 120 to identify the bit width of a per-cell field of a DCI communication, the number of bits associated with the per-cell field, and / or the relative position of the DCI field, thereby improving decoding of the DCI communication at the UE 120 and, therefore, reducing communication errors between the network node 110 and the UE 120. In some aspects, the UE 120 may receive a multi-cell scheduled DCI communication that includes a co-scheduled cell indicator field that indicates one or more cells scheduled by the DCI communication, and the UE 120 may identify the bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field. For example, the UE 120 may identify the bit width based at least in part on a necessary number of bits used for the field related to the co-scheduled cell indicator field that indicates a subset of cells that maximizes the bit width. Additionally or alternatively, when the cell subset indicated by the co-scheduled cell indicator is a cell subset that does not maximize the bit width, the UE 120 may determine the number of bits actually used for the field and / or the position of other fields in the DCI communication relative to the field. Thus, communication errors associated with multi-cell scheduled DCI communications may be reduced, thereby reducing power consumption, computing resource consumption, and network resource consumption that would otherwise be required to correct communication errors, and / or reducing or eliminating signaling overhead associated with the network node 110 indicating certain bit widths for a given DCI communication to the UE 120.

[0091] As indicated above, Figures 5A to 5B are provided as examples. Other examples can be found in the Figures 5A to 5B What is described is different.

[0092] Figures 6A to 6G 6 is a diagram illustrating an example 600 associated with a DCI format for multi-cell scheduling according to the present disclosure. Example 600 may be associated with communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0093] like Figure 6A As shown, UE 120 and network node 110 may communicate using multi-cell scheduling DCI 505, as described above in conjunction with Figures 5A to 5BIn this regard, the multi-cell scheduling DCI 505 may include a co-scheduled cell indicator field 530 that indicates a code point associated with a subset of cells in the configured set of cells that are co-scheduled by the multi-cell scheduling DCI 505 (e.g., a subset of cells that are co-scheduled with PUSCH in aspects where the multi-cell scheduling DCI 505 is associated with DCI format 0_X communication, or a subset of cells that are co-scheduled with PDSCH in aspects where the multi-cell scheduling DCI 505 is associated with DCI format 1_X communication). More specifically, the UE 120 may receive (e.g., via RRC signaling) a configuration of the co-scheduled cell indicator field 530, which may indicate a table (e.g., table 535) that associates a set of cells (e.g., cell #1, cell #2, cell #3, and cell #4) with respective code points, and the co-scheduled cell indicator field 530 may indicate one of the plurality of code points in the table, the one code point corresponding to the subset of cells co-scheduled via the multi-cell scheduling DCI 505. Although a table has been described herein for ease of discussion, in some other aspects, a different data structure may be used to associate a set of cells with respective code points. For example, the configuration of the co-scheduled cell indicator field 530 may indicate a parameter list, the number of entries in the parameter list corresponding to the number of rows in the table (e.g., table 535) as described herein.

[0094] In some aspects, the UE 120 may identify the bit width of one or more per-cell fields (e.g., the FDRA field, the MCS field, the NDI, the RV field, and / or similar per-cell fields) in the multi-cell scheduling DCI 505 based at least in part on the configuration of the co-scheduled cell indicator field 530. As used herein, the bit width of a field may refer to the number of bits (sometimes referred to herein as N) associated with the field in the multi-cell scheduling DCI 505. In some aspects, the UE 120 may identify the bit width associated with the field by identifying the necessary number of bits related to the co-scheduled cell indicator field used for the field, the co-scheduled cell indicator indicating a subset of cells of a potential subset of cells that can be indicated by the co-scheduled cell indicator field that maximizes the bit width. For example, in some aspects, when the multi-cell scheduling DCI 505 schedules PUSCH or PDSCH in a maximum number of cells in the set of cells indicated by table 535, the UE 120 may derive the necessary number (e.g., N) for the FDRA field, MCS field, NDI field, RV field, or similar fields.

[0095] More specifically, in Figure 6AIn the example depicted in FIG, table 535 indicates that the co-scheduled cell indicator field 530 may perform one of the following operations: indicate a first subset of cells (e.g., cell #1 and cell #2) by using code point 00, indicate a second subset of cells (e.g., cell #3 and cell #4) by using code point 01, indicate a third subset of cells (e.g., cell #1, cell #2, and cell #3) by using code point 10, or indicate a fourth subset of cells (e.g., cell #1, cell #2, cell #3, and cell #4) by using code point 11. In this regard, because the fourth subset of cells associated with code point 11 includes the most cells of all potential cell sets (and therefore, in this example, includes the maximum bit requirement for the field), the UE 120 may use the fourth subset of cells to identify the bit width of the field in the DCI communication (e.g., to derive N).

[0096] More specifically, because the fourth subset of cells includes cell #1, cell #2, cell #3, and cell #4, UE 120 may identify a first set of bits 605, a second set of bits 610, a third set of bits 615, and a fourth set of bits 620. The first set of bits is required to indicate information associated with the field for cell #1 when using codepoint 11, the second set of bits is required to indicate information associated with the field for cell #2 when using codepoint 11, the third set of bits is required to indicate information associated with the field for cell #3 when using codepoint 11, and the fourth set of bits is required to indicate information associated with the field for cell #4 when using codepoint 11. These bits (e.g., first set of bits 605, second set of bits 610, third set of bits 615, and fourth set of bits 620) may collectively form a field bit width 625. In other words, the sum of the first set of bits 605, second set of bits 610, third set of bits 615, and fourth set of bits 620 may be equal to N. In some aspects, the first set of bits 605, the second set of bits 610, the third set of bits 615, and the fourth set of bits 620 may be identified by the UE 120 based at least in part on certain configuration parameters. For example, in aspects where the field is an FDRA field, the UE 120 may identify the first set of bits 605, the second set of bits 610, the third set of bits 615, and the fourth set of bits 620 (and thus N as the sum of the four sets of bits) based at least in part on a BWP size of the corresponding cell and / or a resource block group (RBG) size of the corresponding cell.

[0097] like Figure 6BAs shown, in some aspects, the number of bits actually used in the multi-cell scheduling DCI field for a given cell may be greater than the size of the bit sets 605, 610, 615, 620 determined by the UE 120 for the purpose of deriving N. More specifically, in aspects where the number of co-scheduled cells is less than the number of cells used to derive N, the bit width of the portion of the field used for each co-scheduled cell may be greater than the bit width of the corresponding bit sets 605, 610, 615, 620 used to derive N, provided that the total number of bits used for the field does not exceed N. Figure 6B In the example shown, the co-scheduled cell indicator field 530 indicates code point 00 corresponding to the first set of cells (e.g., cell #1 and cell #2). Thus, the field may include a bit for the first cell 630 and a bit for the second cell 632. Figure 1 As shown, the bits for the first cell 630 include more bits than the first set of bits 605 (e.g., the number of bits allocated to cell #1 when deriving N), and the bits for the second cell 632 include more bits than the second set of bits 610 (e.g., the number of bits allocated to cell #1 when deriving N). However, the sum of the bits for the first cell 630 and the bits for the second cell 632 is less than or equal to N (e.g., the bits actually used in the field may be less than or equal to the derived bit width N of the field).

[0098] In this regard, when the co-scheduled cell indicator field 530 is used to co-schedule many cells, the portion of the field allocated to each cell may be smaller than when the co-scheduled cell indicator field 530 is used to co-schedule a smaller number of cells. For example, in aspects where the field corresponds to the FDRA field, when the multi-cell scheduling DCI 505 is used to schedule four cells (e.g., when the co-scheduled cell indicator field 530 indicates code point 11), a coarser resource allocation granularity may be used than when the multi-cell scheduling DCI 505 is used to schedule two cells (e.g., when the co-scheduled cell indicator field 530 indicates code point 00). In other words, when the number of cells co-scheduled by the multi-cell scheduling DCI 505 is smaller than the number of cells used to derive N, a finer resource allocation granularity may be used, thereby improving spectral efficiency by achieving improved scheduling flexibility.

[0099] Additionally or alternatively, when the total number of bits used for the field is less than the bit width of the field (e.g., when the total number of bits used for the field is less than N, such as Figure 6B As shown), there may be unused bits in the multi-cell scheduling DCI 505. In some aspects, such as Figure 6CAs shown, when the total number of bits used for the field is less than N, resulting in unused bits 635 in the multi-cell scheduling DCI 505, the next field 640 in the multi-cell scheduling DCI 505 may begin at the first bit after the N bits associated with the field. In this regard, the unused bits 635 may be provided between the total number of bits used for the field (e.g., bits for the first cell 630 and bits for the second cell 632) and the next field 640 in the multi-cell scheduling DCI 505. In other words, in some aspects, the starting bit of the next field 640 in the multi-cell scheduling DCI 505 is fixed and does not change regardless of which cells are co-scheduled via the multi-cell scheduling DCI 505.

[0100] In some other aspects, such as Figure 6D As shown, when the total number of bits used for this field is less than N, resulting in unused bits 635 in the multi-cell scheduling DCI 505, the next field 640 in the multi-cell scheduling DCI 505 may start at the first bit after the bits actually used for the field (e.g., bits that appear after the bits used for the first cell 630 and the bits used for the second cell 632). In this regard, to maintain a constant DCI size, the unused bits 635 may be placed at the end of the multi-cell scheduling DCI 505. In other words, in some aspects, the starting bit of the next field 640 in the multi-cell scheduling DCI 505 may not be fixed, but may change based at least in part on which cells are co-scheduled via the multi-cell scheduling DCI 505.

[0101] In some aspects, at least a portion of the unused bits 635 may be used to indicate additional information associated with at least one of the co-scheduled cells. For example, in some aspects, the multi-cell scheduling DCI 505 may be used to schedule two TBs / codewords (CWs) associated with a cell, and the unused bits 635 may be used to indicate information associated with at least one of the two TBs / CWs. More specifically, in some aspects, this field may be associated with the MCS field, the NDI field, and / or the RV field. In such aspects, the UE 120 may be combined with the above Figure 6AIn a similar manner as described above, the total bit width (e.g., N) of the MCS field, the NDI field, and / or the RV field is identified so that the total bit width is the largest among all co-scheduled cell combinations. In such an aspect, when the total number of bits of the MCS field, the NDI field, and / or the RV field for the co-scheduled cell is less than the derived bit width, the unused bits 635 in the MCS field, the NDI field, and / or the RV field may be used as the MCS field, NDI field, and / or RV field for the second TB / CW of one or more co-scheduled cells in the co-scheduled cell. In other words, the first portion of the field (e.g., the first portion of N bits) may be used to indicate the MCS, NDI, and / or RV associated with the first TB / CW of at least one co-scheduled cell, and the second portion of the field (e.g., the second portion of N bits) may be used to indicate the MCS, NDI, and / or RV associated with the second TB / CW of at least one co-scheduled cell.

[0102] In some aspects, the UE 120 may be configured with only a proper subset of the configured set of cells that may be co-scheduled using the multi-cell scheduling DCI 505. For example, Figure 6E As shown, the UE 120 may be configured with a table 645 that may indicate true subsets of a set of cells (e.g., cell #1, cell #2, cell #3, and cell #4) that may be co-scheduled using the multi-cell scheduling DCI 505. More specifically, the table 645 indicates that the co-scheduled cell indicator field 530 may perform one of the following operations: indicate a first subset of cells (e.g., cell #1) by using code point 00, indicate a second subset of cells (e.g., cell #2) by using code point 01, indicate a third subset of cells (e.g., cell #3 and cell #4) by using code point 10, or indicate a fourth subset of cells (e.g., cell #1 and cell #2) by using code point 11. In this regard, and in conjunction with the above, 6A to 6D Unlike the described table 535, none of the cell subsets includes all cells in the cell set (for example, none of the cell subsets includes all of cell #1, cell #2, cell #3, and cell #4), and all cells in the cell set can be coordinated using the multi-cell scheduling DCI 505.

[0103] In some aspects, UE 120 may use the following to derive the necessary number of bits for this field (e.g., N, as Figure 6E The number of bits required for this field is the maximum value from all possible combinations of co-scheduled cells. Figure 6EIn the example shown, UE 120 may identify that the third subset of cells (e.g., cell #3 and cell #4) results in the maximum number of bits required for the field, and therefore, the UE may use the third subset (e.g., the subset associated with code point 10) to identify the field bit width 650 (e.g., for deriving N). In other words, UE 120 may compare the total number of bits required for the field to indicate information associated with the first subset of cells (e.g., cell #1), the second subset of cells (e.g., cell #2), the third subset of cells (e.g., cell #3 and cell #4), and the fourth subset of cells (e.g., cell #1 and cell #2), and may identify the field bit width 650 based on the co-scheduled cell combination that results in the maximum number of necessary bits for the field.

[0104] More specifically, in Figure 6E In the example shown, UE 120 may determine that the third subset of cells results in the maximum number of bits used for the field. Furthermore, because the third subset of cells includes cell #3 and cell #4, UE 120 may identify a first set 655 of bits necessary to indicate information associated with the field for cell #3 when using codepoint 10, and a second set 660 of bits necessary to indicate information associated with the field for cell #4 when using codepoint 10. These bits (e.g., the first set 655 of bits and the second set 660 of bits) may collectively form the field bit width 650 (e.g., the sum of the first set 655 of bits and the second set 660 of bits may be equal to N). In conjunction with the above, Figure 6A In a similar manner as described for the field width 625 in , the first set of bits 655 and the second set of bits 660 can be identified by the UE 120 based at least in part on specific configuration parameters (e.g., based at least in part on the BWP size of the corresponding cell and / or the RBG size of the corresponding cell).

[0105] like Figure 6F As shown, and in combination with the above Figure 6B In a similar manner as described, in some aspects, the number of bits actually used in the multi-cell scheduling DCI field for a given cell may be larger than the size of the bit set determined by the UE 120 when deriving N. More specifically, in Figure 6F In the example shown, the co-scheduled cell indicator field 530 indicates code point 00 corresponding to the first subset of cells (e.g., cell #1). Thus, the field may include a bit for the first cell 665. Figure 6F As shown, the bits used for the first cell 665 may include more bits than the bits allocated to the third cell and / or the fourth cell when deriving N.

[0106] In some aspects, such as Figure 6GAs shown, even when the multi-cell scheduling DCI 505 is used to co-schedule the same number of cells as used to derive N, the total number of bits used for this field may be less than N. More specifically, as Figure 6G As shown, the co-scheduled cell indicator field 530 indicates code point 11 corresponding to the fourth subset of cells (e.g., cell #1 and cell #2). Thus, the field may include a bit for the first cell 670 and a bit for the second cell 675. Figure 6G As shown, the total number of bits used for the field (e.g., the sum of the bits used for the first cell 670 and the bits used for the second cell 675) may be less than N, even if N is derived using the bit allocation for the two cells (e.g., cell #3 and cell #4). For example, due to differences in BWP size between cells, RBG size between cells, etc., the number of bits used for the FDRA field corresponding to the first cell and the second cell may be less than the number of bits used for the FDRA field corresponding to the first cell and the second cell. As described above, in such aspects, the next field in the multi-cell scheduling DCI 505 may start at the first bit after the N bits associated with the field (as described above in conjunction with Figure 6C Otherwise, the next field 640 in the multi-cell scheduling DCI 505 may start with the first bit after the bits actually used for that field (as described above in conjunction with Figure 6D described).

[0107] Combined with the following Figure 7 Describing in greater detail additional aspects of network node 110 and / or UE 120 , the network node configures UE 120 to receive multi-cell scheduling DCI 505 , the UE identifies a bit width of at least one field of multi-cell scheduling DCI 505 based at least in part on a configuration of co-scheduled cell indicator field 530 .

[0108] As indicated above, Figures 6A to 6G are provided as examples. Other examples can be found in the Figures 6A to 6G The examples described are different.

[0109] Figure 7 FIG. 7 is a diagram illustrating another example 700 associated with a DCI format for multi-cell scheduling according to the present disclosure. Figure 7 As shown, a network node 110 (e.g., a CU, DU, and / or RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless network 100). The network node 110 and the UE 120 may be in a Figure 7 The operations shown are performed after a wireless connection has been established.

[0110] As indicated by reference numeral 705, the network node 110 may send configuration information, and the UE 120 may receive the configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, among others. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., already known to the UE 120 and / or previously indicated by the network node 110 or other network device), and / or explicit configuration information for use by the UE 120 to configure the UE 120, among others.

[0111] In some aspects, the configuration information may include a configuration of a co-scheduled cell indicator field (e.g., co-scheduled cell indicator field 530) associated with a multi-cell scheduled DCI communication (e.g., multi-cell scheduled DCI 505). Figures 6A to 6G 535, table 645, or a similar table described above to configure UE 120. In this regard, network node 110 may indicate to UE 120 a set of cells (e.g., cell #1, cell #2, cell #3, and cell #4, as described above in conjunction with FIG) that may be co-scheduled using multi-cell scheduled DCI communications. Figures 6A to 6G ), and / or may indicate a code point associated with the co-scheduled cell indicator field, the code point corresponding to a configured subset of the cell set. In some aspects, these subsets may be true subsets of the cell set, as described above in conjunction with Figures 6E to 6G described.

[0112] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0113] As shown in the reference numeral 710, the network node 110 may send a multi-cell scheduled DCI communication, and the UE 120 may receive the multi-cell scheduled DCI communication. In some aspects, the multi-cell scheduled DCI communication may include a co-scheduled cell indicator field, which indicates one or more cells scheduled by the DCI communication. More specifically, the co-scheduled cell indicator field may indicate code points associated with a subset of cells (e.g., one or more of four potential cells) that are co-scheduled using the multi-cell scheduled DCI communication. In some aspects, the multi-cell scheduled DCI communication may be associated with a DCI format 0_X communication, and thus the multi-cell scheduled DCI communication may utilize a PUSCH co-scheduled cell set. In some aspects, the multi-cell scheduled DCI communication may be associated with a DCI format 1_X communication, and thus the multi-cell scheduled DCI communication may utilize a PDSCH co-scheduled cell set.

[0114] As indicated by reference numeral 715, the UE 120 may identify a bit width associated with a field of the DCI communication based at least in part on the configuration of the co-scheduled cell indicator field. In some aspects, the field may include at least one of an FDRA field, an MCS field, an NDI field, or an RV field. Furthermore, in some aspects, identifying the bit width associated with the field may include: identifying a necessary number of bits associated with the co-scheduled cell indicator field for the field, the co-scheduled cell indicator field indicating a set of cells in a potential cell set that maximizes the bit width, the potential cell set being capable of being indicated by the co-scheduled cell indicator field, as described above in conjunction with Figure 6A In some other aspects, the co-scheduled cell indicator field may indicate one of a plurality of co-scheduled cell combinations associated with the DCI communication, and identifying the bit width associated with the field may include the number of bits necessary for the UE 120 to identify the co-scheduled cell combination associated with the maximum number of bits to schedule the plurality of co-scheduled cell combinations, such as described above in conjunction with Figure 6E described.

[0115] In addition, as mentioned above Figures 6B to 6D and Figures 6F to 6GAs described, in some aspects, the total number of bits used for the field may be less than the bit width (such as when less than a maximum number of cells are co-scheduled via the multi-cell scheduled DCI communication). In other words, in some aspects, the total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits (e.g., unused bits 635). For example, where the co-scheduled cell indicator field indicates a first set of cells in the respective potential sets of cells indicated by the configuration information, a first number of bits may be associated with the field, and where the co-scheduled cell indicator field indicates a second set of cells in the potential set of cells, a second number of bits that is different from the first number of bits is associated with the field. Furthermore, in aspects where the first set of cells corresponds to the set of cells that maximizes the bit width, the second number of bits may be less than the first number of bits, as described above in conjunction with Figures 6B to 6D and Figures 6F to 6G described.

[0116] In some aspects, another field of the DCI communication that occurs directly after this field (e.g., next field 640) may begin after the number of unused bits, as described above in connection with Figure 6C In some other aspects, another field of the DCI communication that occurs directly after the field may begin after the total number of bits used for the field, and / or the number of unused bits may be included at the end of the DCI communication, as described above in conjunction with Figure 6D Additionally or alternatively, in some aspects, two TBs and / or CWs may be scheduled via the DCI communication, as described above in conjunction with Figure 6D In such aspects, the total number of bits used for the field may be associated with a first TB / CW of the two TB / CWs, and at least a portion of the number of unused bits may be associated with a second TB / CW of the two TB / CWs.

[0117] In some aspects, the multi-cell scheduled DCI communication may schedule only a single cell, such as when UE 120 is configured with the above-described Figures 6E to 6GTable 645 is described and the co-scheduled cell indicator field indicates one of codepoint 00 or codepoint 01. In such aspects, the number of bits used for this field may be based at least in part on at least one of a BWP size associated with the single cell or an RBG size associated with the single cell. For example, the number of bits used for this field may be based at least in part on a wireless communication standard, such as by using a formula and / or table provided in 3GPP Technical Specification (TS) 38.214 Version 17.4.0. For example, in aspects in which this field is associated with the FDRA field and only a single cell is scheduled via the multi-cell scheduled DCI communication, the number of bits used for the FERA field may be identified by using legacy rules associated with identifying the bit width of the FERA field for single-cell scheduled DCI, such as legacy rules specified by the 3GPP wireless communication standard or similar standards (e.g., the formula provided in Section 5.1.2.2 of TS 38.214). For example, in aspects where the field is associated with the FDRA field and only a single cell is scheduled via multi-cell scheduled DCI communications, the number of bits used for the FDRA field may be associated with the number of PRBs associated with the cell and the downlink resource allocation scheme type (e.g., one of: Type 0, Configuration 1; Type 0, Configuration 2; or Type 1).

[0118] Based at least in part on UE 120 identifying the bit width associated with a field of a multi-cell scheduled DCI communication based at least in part on a configuration of the co-scheduled cell indicator field associated with the DCI communication, UE 120 and / or network node 110 may conserve computational resources, power resources, network resources, and / or communication resources. For example, based at least in part on UE 120 identifying the bit width associated with a field of a multi-cell scheduled DCI communication based at least in part on a configuration of the co-scheduled cell indicator field associated with the DCI communication, UE 120 and network node 110 may communicate with a reduced error rate and / or may eliminate overhead associated with network node 110 signaling the bit width of the field to UE 120, which may conserve computational resources, power resources, network resources, and / or communication resources that may otherwise be consumed to detect and / or correct communication errors and / or signal information regarding the bit width of one or more DCI fields.

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

[0120] Figure 8is a diagram illustrating an example process 800, for example, performed by a UE, in accordance with the present disclosure. Example process 800 is an example in which the UE (eg, UE 120) performs operations associated with a DCI format for multi-cell scheduling.

[0121] like Figure 8 As shown, in some aspects, process 800 may include receiving a multi-cell scheduled DCI communication including a co-scheduled cell indicator field indicating one or more cells scheduled via the DCI communication (block 810). For example, the UE (e.g., using Figure 10 The receiving component 1002 and / or the communication manager 1006 depicted in FIG may receive a multi-cell scheduled DCI communication including a co-scheduled cell indicator field indicating one or more cells scheduled via the DCI communication, as described above.

[0122] like Figure 8 As further shown, in some aspects, process 800 may include identifying a bit width associated with a field of the DCI communication based at least in part on the configuration of the co-scheduled cell indicator field (block 820). Figure 10 The communication manager 1006 depicted in FIG) may identify a bit width associated with a field of the DCI communication based at least in part on the configuration of the co-scheduled cell indicator field, as described above.

[0123] Process 800 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.

[0124] In a first aspect, the field includes at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

[0125] In a second aspect, alone or in combination with the first aspect, identifying the bit width associated with the field includes: identifying a necessary number of bits used for the field related to the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells in a potential cell set that maximizes the bit width, the potential cell set being capable of being indicated by the co-scheduled cell indicator field.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, in a case where the co-scheduled cell indicator field indicates a first set of cells in the set of potential cells, a first number of bits is associated with the field, and in a case where the co-scheduled cell indicator field indicates a second set of cells in the set of potential cells, a second number of bits different from the first number of bits is associated with the field.

[0127] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first set of cells corresponds to the set of cells that maximizes the bit width, and the second number of bits is less than the first number of bits.

[0128] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

[0129] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, another field of the DCI communication occurring directly after the field begins after the number of unused bits.

[0130] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, another field of the DCI communication that occurs directly after the field begins after the total number of bits used for the field, and the number of unused bits is included at the end of the DCI communication.

[0131] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, two transport blocks are scheduled via the DCI communication, the total number of bits used for the field is associated with the first of the two transport blocks, and at least a portion of the number of unused bits is associated with the second of the two transport blocks.

[0132] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the co-scheduling cell indicator field indicates one of a plurality of co-scheduling cell combinations associated with the DCI communication, and identifying the bit width associated with the field also includes identifying the number of bits necessary to schedule a co-scheduling cell combination associated with a maximum number of bits among the plurality of co-scheduling cell combinations.

[0133] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the one or more cells include only a single cell, and the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

[0134] although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include Figure 8 800. In some embodiments, the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 800 may be executed in parallel.

[0135] Figure 9 is a diagram illustrating an example process 900, for example, performed by a network node, in accordance with the present disclosure. Example process 900 is an example in which the network node (eg, network node 110) performs operations associated with DCI formats for multi-cell scheduling.

[0136] like Figure 9 As shown, in some aspects, process 900 may include: sending a configuration of a co-scheduled cell indicator field associated with multi-cell scheduled DCI communication to a UE (block 910). For example, the network node (e.g., using Figure 11 The transmitting component 1104 and / or the communication manager 1106 depicted in FIG may transmit a configuration of the co-scheduled cell indicator field associated with multi-cell scheduled DCI communication to the UE, as described above.

[0137] like Figure 9 As further shown, in some aspects, process 900 may include: sending the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled via the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field (block 920). For example, the network node (e.g., using Figure 11 The transmitting component 1104 and / or the communication manager 1106 depicted in the figure may send the multi-cell DCI communication including the co-scheduled cell indicator field to the UE, wherein the co-scheduled cell indicator field indicates one or more cells scheduled by the DCI communication, wherein the bit width associated with the field of the DCI communication is at least partially based on the configuration of the co-scheduled cell indicator field, as described above.

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

[0139] In a first aspect, the field includes at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

[0140] In a second aspect, alone or in combination with the first aspect, the bit width associated with the field is based at least in part on a necessary number of bits used for the field related to the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells in a potential set of cells that maximizes the bit width, the potential set of cells being capable of being indicated by the co-scheduled cell indicator field.

[0141] In a third aspect, alone or in combination with one or more of the first and second aspects, in a case where the co-scheduled cell indicator field indicates a first set of cells in the set of potential cells, a first number of bits is associated with the field, and in a case where the co-scheduled cell indicator field indicates a second set of cells in the set of potential cells, a second number of bits different from the first number of bits is associated with the field.

[0142] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first set of cells corresponds to the set of cells that maximizes the bit width, and the second number of bits is less than the first number of bits.

[0143] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

[0144] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, another field of the DCI communication occurring directly after the field begins after the number of unused bits.

[0145] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, another field of the DCI communication that occurs directly after the field begins after the total number of bits used for the field, and the number of unused bits is included at the end of the DCI communication.

[0146] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, two transport blocks are scheduled via the DCI communication, the total number of bits used for the field is associated with the first of the two transport blocks, and at least a portion of the number of unused bits is associated with the second of the two transport blocks.

[0147] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the co-scheduled cell indicator field indicates one of a plurality of co-scheduled cell combinations associated with the DCI communication, and the bit width associated with the field is further based at least in part on the number of bits necessary to schedule a co-scheduled cell combination associated with a maximum number of bits among the plurality of co-scheduled cell combinations.

[0148] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the one or more cells include only a single cell, and the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

[0149] although Figure 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Figure 9 900. In some embodiments, the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 900 may be executed in parallel.

[0150] Figure 10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE, or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002, a sending component 1004, and / or a communication manager 1006, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1006 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 140. As shown, the apparatus 1000 can communicate with another apparatus 1008, such as a UE or a network node, such as a CU, DU, RU, or base station, using a receiving component 1002 and a sending component 1004.

[0151] In some aspects, the apparatus 1000 may be configured to perform Figures 6A to 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more of the processes described herein, such as Figure 8 The process 800. In some aspects, Figure 10 The device 1000 and / or one or more components shown may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Figure 10 One or more of the components shown may be combined Figure 2Additionally 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 code 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 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1008. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 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 1000. In some aspects, the receiving component 1002 may include processing the received communications in conjunction with one or more other components of the apparatus 1000. Figure 2 The depicted UE 120 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0153] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1008. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the apparatus 1008. In some aspects, the transmitting component 1004 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 apparatus 1008. In some aspects, the transmitting component 1004 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 depicted UE 120. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0154] The communications manager 1006 can support the operation of the receiving component 1002 and / or the sending component 1004. For example, the communications manager 1006 can receive information associated with configuring the receipt of communications by the receiving component 1002 and / or the sending of communications by the sending component 1004. Additionally or alternatively, the communications manager 1006 can generate and / or provide control information to the receiving component 1002 and / or the sending component 1004 to control the receipt and / or sending of communications.

[0155] Receiving component 1002 can receive a multi-cell scheduled DCI communication including a co-scheduled cell indicator field that indicates one or more cells scheduled by the DCI communication. Communications manager 1006 can identify a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduled cell indicator field.

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

[0157] Figure 11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102, a sending component 1104, and / or a communication manager 1106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1106 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 150. As shown, the device 1100 can communicate with another device 1108, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1102 and a sending component 1104.

[0158] In some aspects, the apparatus 1100 may be configured to perform Figures 6A to 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 The process 900. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include a combination of Figure 2 One or more components of the described network node 110. Additionally or alternatively, Figure 11 One or more of the components shown may be combined Figure 2Additionally 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 code 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.

[0159] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1108. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network node 110. In some aspects, the receiving component 1102 and / or the transmitting component 1104 may comprise or be included in a network interface. The network interface may be configured to obtain and / or output signals for the device 1100 via one or more communication links (such as a backhaul link, a midhaul link, and / or a fronthaul link).

[0160] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1108. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1108. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1108. In some aspects, the transmitting component 1104 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 depicted network node 110. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0161] The communications manager 1106 can support the operation of the receiving component 1102 and / or the sending component 1104. For example, the communications manager 1106 can receive information associated with configuring the receipt of communications by the receiving component 1102 and / or the sending of communications by the sending component 1104. Additionally or alternatively, the communications manager 1106 can generate and / or provide control information to the receiving component 1102 and / or the sending component 1104 to control the receipt and / or sending of communications.

[0162] The transmitting component 1104 may transmit a configuration of a co-scheduled cell indicator field associated with a multi-cell scheduled DCI communication to a UE. The transmitting component 1104 may transmit the multi-cell DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled via the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

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

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

[0165] Aspect 1: A wireless communication method performed by a UE, the method comprising: receiving a multi-cell scheduled DCI communication including a co-scheduling cell indicator field, the co-scheduling cell indicator field indicating one or more cells scheduled by the DCI communication; and identifying a bit width associated with a field of the DCI communication based at least in part on a configuration of the co-scheduling cell indicator field.

[0166] Aspect 2: The method according to aspect 1, wherein the field comprises at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

[0167] Aspect 3: A method according to any one of Aspects 1 to 2, wherein identifying the bit width associated with the field further includes: identifying the necessary number of bits related to the co-scheduling cell indicator field used for the field, the co-scheduling cell indicator field indicating a set of cells in a potential cell set that maximizes the bit width, and the potential cell set can be indicated by the co-scheduling cell indicator field.

[0168] Aspect 4: A method according to Aspect 3, wherein, in a case where the co-scheduling cell indicator field indicates a first set of cells in the potential cell set, a first number of bits is associated with the field, and wherein, in a case where the co-scheduling cell indicator field indicates a second set of cells in the potential cell set, a second number of bits different from the first number of bits is associated with the field.

[0169] Aspect 5: The method of aspect 4, wherein the first set of cells corresponds to the set of cells that maximizes the bit width, and wherein the second number of bits is less than the first number of bits.

[0170] Aspect 6: The method of any one of aspects 1 to 5, wherein the total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

[0171] Aspect 7: The method of aspect 6, wherein another field of the DCI communication occurring directly after the field begins after the number of unused bits.

[0172] Aspect 8: The method of aspect 6, wherein another field of the DCI communication that occurs directly after the field begins after the total number of bits used for the field, and wherein the number of unused bits is included at the end of the DCI communication.

[0173] Aspect 9: A method according to Aspect 6, wherein two transport blocks are scheduled via the DCI communication, wherein the total number of bits used for the field is associated with a first transport block of the two transport blocks, and wherein at least a portion of the number of unused bits is associated with a second transport block of the two transport blocks.

[0174] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the co-scheduling cell indicator field indicates one of a plurality of co-scheduling cell combinations associated with the DCI communication, and wherein the bit width associated with the field further includes identifying the number of bits necessary to schedule a co-scheduling cell combination associated with the maximum number of bits among the plurality of co-scheduling cell combinations.

[0175] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the one or more cells include only a single cell, and wherein the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

[0176] Aspect 12: A method of wireless communication performed by a network node, the method comprising: sending a configuration of a co-scheduling cell indicator field associated with a multi-cell scheduled DCI communication to a UE; and sending the multi-cell DCI communication including the co-scheduling cell indicator field to the UE, the co-scheduling cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is at least partially based on the configuration of the co-scheduling cell indicator field.

[0177] Aspect 13: The method according to aspect 12, wherein the field comprises at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

[0178] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the bit width associated with the field is at least partially based on the necessary number of bits related to the co-scheduling cell indicator field used for the field, the co-scheduling cell indicator field indicating a set of cells in a potential cell set that maximizes the bit width, and the potential cell set can be indicated by the co-scheduling cell indicator field.

[0179] Aspect 15: A method according to Aspect 14, wherein, in a case where the co-scheduled cell indicator field indicates a first set of cells in the potential cell set, a first number of bits is associated with the field, and wherein, in a case where the co-scheduled cell indicator field indicates a second set of cells in the potential cell set, a second number of bits different from the first number of bits is associated with the field.

[0180] Aspect 16: The method of aspect 15, wherein the first set of cells corresponds to the set of cells that maximizes the bit width, and wherein the second number of bits is less than the first number of bits.

[0181] Aspect 17: The method of any one of aspects 12 to 16, wherein the total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

[0182] Aspect 18: The method of aspect 17, wherein another field of the DCI communication occurring directly after the field begins after the number of unused bits.

[0183] Aspect 19: The method of aspect 17, wherein another field of the DCI communication that occurs directly after the field begins after the total number of bits used for the field, and wherein the number of unused bits is included at the end of the DCI communication.

[0184] Aspect 20: A method according to Aspect 17, wherein two transport blocks are scheduled via the DCI communication, wherein the total number of bits used for the field is associated with a first transport block of the two transport blocks, and wherein at least a portion of the number of unused bits is associated with a second transport block of the two transport blocks.

[0185] Aspect 21: A method according to any one of Aspects 12 to 20, wherein the co-scheduling cell indicator field indicates one of a plurality of co-scheduling cell combinations associated with the DCI communication, and wherein the bit width associated with the field is further based at least in part on the number of bits necessary to schedule a co-scheduling cell combination associated with a maximum number of bits among the plurality of co-scheduling cell combinations.

[0186] Aspect 22: A method according to any one of Aspects 12 to 21, wherein the one or more cells include only a single cell, and wherein the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

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

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

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

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

[0191] Aspect 27: 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 22.

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

[0193] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0194] As used herein, "satisfying a threshold" may mean that a value is 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., depending on the context.

[0195] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0196] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element having" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a multi-cell scheduled downlink control information (DCI) communication including a co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication; and A bit width associated with a field of the DCI communication is identified based at least in part on the configuration of the co-scheduled cell indicator field. 2 . The UE according to claim 1 , wherein the field comprises at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

3. The UE of claim 1 , wherein the one or more processors for identifying the bit width associated with the field are configured to: identify a necessary number of bits for the field related to the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells in a potential cell set that maximizes the bit width, the potential cell set being capable of being indicated by the co-scheduled cell indicator field.

4. The UE according to claim 3, wherein: In a case where the co-scheduled cell indicator field indicates a first set of cells in the set of potential cells, a first number of bits is associated with the field, and wherein in a case where the co-scheduled cell indicator field indicates a second set of cells in the set of potential cells, a second number of bits different from the first number of bits is associated with the field. 5 . The UE of claim 4 , wherein the first set of cells corresponds to the set of cells that maximizes the bit width, and wherein the second number of bits is less than the first number of bits.

6. The UE of claim 1, wherein a total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

7. The UE of claim 6, wherein another field of the DCI communication occurring directly after the field begins after the number of unused bits.

8. The UE of claim 6, wherein another field of the DCI communication occurring directly after the field begins after the total number of bits used for the field, and wherein the number of unused bits is included at the end of the DCI communication.

9. The UE of claim 6 , wherein two transport blocks are scheduled via the DCI communication, wherein the total number of bits used for the field is associated with a first transport block of the two transport blocks, and wherein at least a portion of the number of unused bits is associated with a second transport block of the two transport blocks.

10. The UE of claim 1 , wherein the co-scheduled cell indicator field indicates one of a plurality of co-scheduled cell combinations associated with the DCI communication, and wherein the one or more processors for identifying the bit width associated with the field are configured to identify a number of bits necessary to schedule a co-scheduled cell combination associated with a maximum number of bits among the plurality of co-scheduled cell combinations.

11. The UE of claim 1 , wherein the one or more cells comprise only a single cell, and wherein the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

12. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting a configuration of a co-scheduled cell indicator field associated with multi-cell scheduled downlink control information (DCI) communication to a user equipment (UE); as well as and transmitting the multi-cell scheduled DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

13. The network node according to claim 12, wherein the field comprises at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

14. The network node of claim 12 , wherein the bit width associated with the field is based at least in part on a necessary number of bits used for the field related to the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells in a set of potential cells that can be indicated by the co-scheduled cell indicator field that maximizes the bit width. The network node according to claim 14 , wherein: In a case where the co-scheduled cell indicator field indicates a first set of cells in the set of potential cells, a first number of bits is associated with the field, and wherein in a case where the co-scheduled cell indicator field indicates a second set of cells in the set of potential cells, a second number of bits different from the first number of bits is associated with the field.

16. The network node of claim 15, wherein the first set of cells corresponds to the set of cells that maximizes the bit width, and wherein the second number of bits is less than the first number of bits.

17. The network node of claim 12, wherein a total number of bits used for the field is less than the bit width associated with the field, resulting in a certain number of unused bits.

18. The network node of claim 17, wherein another field of the DCI communication occurring directly after the field begins after the number of unused bits.

19. The network node of claim 17, wherein another field of the DCI communication occurring directly after the field begins after the total number of bits used for the field, and wherein the number of unused bits is included at the end of the DCI communication.

20. The network node of claim 17 , wherein two transport blocks are scheduled via the DCI communication, wherein the total number of bits used for the field is associated with a first transport block of the two transport blocks, and wherein at least a portion of the number of unused bits is associated with a second transport block of the two transport blocks.

21. The network node of claim 12, wherein the co-scheduled cell indicator field indicates one of a plurality of co-scheduled cell combinations associated with the DCI communication, and wherein the bit width associated with the field is further based at least in part on a number of bits necessary to schedule a co-scheduled cell combination associated with a maximum number of bits among the plurality of co-scheduled cell combinations.

22. The network node of claim 12, wherein the one or more cells comprise only a single cell, and wherein the number of bits used for the field is based at least in part on at least one of a bandwidth portion size associated with the single cell or a resource block group size associated with the single cell.

23. A wireless communication method performed by a user equipment (UE), the method comprising: receiving a multi-cell scheduled downlink control information (DCI) communication including a co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication; and A bit width associated with a field of the DCI communication is identified based at least in part on the configuration of the co-scheduled cell indicator field.

24. The method of claim 23, wherein the field comprises at least one of a frequency domain resource allocation field, a modulation and coding scheme field, a new data indicator field, or a redundancy version field.

25. The method of claim 23, wherein identifying the bit width associated with the field further comprises: A necessary number of bits related to the co-scheduled cell indicator field is identified for the field, the co-scheduled cell indicator field indicating a cell set that maximizes the bit width among a potential cell set that can be indicated by the co-scheduled cell indicator field.

26. The method according to claim 25, wherein In a case where the co-scheduled cell indicator field indicates a first set of cells in the set of potential cells, a first number of bits is associated with the field, and wherein in a case where the co-scheduled cell indicator field indicates a second set of cells in the set of potential cells, a second number of bits different from the first number of bits is associated with the field.

27. The method of claim 26, wherein the first set of cells corresponds to the set of cells that maximizes the bit width, and wherein the second number of bits is less than the first number of bits.

28. A wireless communication method performed by a network node, the method comprising: transmitting a configuration of a co-scheduled cell indicator field associated with multi-cell scheduled downlink control information (DCI) communication to a user equipment (UE); as well as and transmitting the multi-cell scheduled DCI communication to the UE including the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating one or more cells scheduled by the DCI communication, wherein a bit width associated with a field of the DCI communication is based at least in part on the configuration of the co-scheduled cell indicator field.

29. The method of claim 28 , wherein the bit width associated with the field is based at least in part on a necessary number of bits used for the field in relation to the co-scheduled cell indicator field, the co-scheduled cell indicator field indicating a set of cells in a set of potential cells that can be indicated by the co-scheduled cell indicator field that maximizes the bit width.

30. The method of claim 28, wherein the co-scheduled cell indicator field indicates one of a plurality of co-scheduled cell combinations associated with the DCI communication, and wherein the bit width associated with the field is further based at least in part on a number of bits necessary to schedule a co-scheduled cell combination associated with a maximum number of bits among the plurality of co-scheduled cell combinations.

Images