Sending downlink feedback information with downlink control information for multi-cell scheduling

By using the DCI format associated with C-RNTI and CS-RNTI in a multi-cell scheduling scenario, combined with CRC and carrier indicator fields, the problem of inefficiency of communication between UE and network entities is solved, and more accurate scheduling information is achieved Decoding and network performance improvements.

CN118985164APending Publication Date: 2024-11-19QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034128.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-21
Filing Date
2023-03-23
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In multi-cell scheduling scenarios, it is difficult for the prior art to effectively decode downlink control information (DCI), resulting in inefficient communication between user equipment (UE) and network entities, especially in cyclic redundancy verification (CRC) calibration When the verification is not satisfied, it is difficult to distinguish the scheduling information on the cell set.

Method used

DCI is decoded based on the satisfaction of the CRC to identify DCI by using the DCI format associated with the Cell Radio Network Temporary Identifier (C-RNTI) and the configured Scheduled Radio Network Temporary Identifier (CS-RNTI) between the UE and the network entity to identify the DCI format associated with the Cell Radio Network Temporary Identifier (CS-RNTI) Scheduling or downlink feedback information (DFI) on the cell set, and a carrier indicator field and HARQ ACK bitmap are introduced in the DCI to improve scheduling accuracy.

Benefits of technology

The communication efficiency and accuracy under multi-cell scheduling are improved, ensuring that the UE can correctly decode DCI and identify scheduling information on the cell set, improving network performance and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985164A_ABST
    Figure CN118985164A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a downlink control information (DCI) associated with a downlink control information (DCI) format for shared channel scheduling on a set of cells, where the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI). The UE may decode the DCI to identify a schedule on the set of cells or identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC). Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 17 / 660,174, filed on April 21, 2022, entitled “TRANSMISSION OF DOWNLINK FEEDBACK INFORMATIONWITH DOWNLINK CONTROLINFORMATION FOR MULTI-CELL SCHEDULING” and assigned to the assignee of this 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 transmitting downlink feedback information using downlink control information for multi-cell scheduling. Background Art

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

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, 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 better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, 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, 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 in 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 downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI). The method may include decoding the DCI to identify scheduling on the set of cells or identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The method may include communicating with the UE based at least in part on the scheduling or DFI on the set of cells, the scheduling or the DFI on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0009] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The one or more processors may be configured to decode the DCI to identify scheduling on a set of cells or identify a DFI based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0010] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The one or more processors may be configured to communicate with the UE based at least in part on a scheduling or DFI on a set of cells, wherein the scheduling or the DFI on the set of cells is decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The instruction set, when executed by one or more processors of the UE, may cause the UE to decode the DCI to identify scheduling on a set of cells or identify a DFI based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to communicate with the UE based at least in part on a scheduling or DFI on a set of cells, wherein the scheduling or DFI on the set of cells is decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving a DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The apparatus may include a component for decoding the DCI to identify scheduling on the set of cells or identifying a DFI based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The apparatus may include a component for communicating with the UE based at least in part on a scheduling or DFI on a set of cells, wherein the scheduling or the DFI on the set of cells is decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC.

[0015] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and descriptions and as illustrated in the accompanying drawings and descriptions.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection 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 accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present 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 non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, 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 devices 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 a variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0020] FIG. 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] FIG. 3 is a diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.

[0022] FIG. 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

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

[0024] 6A to 6E are diagrams illustrating examples associated with transmitting downlink feedback information (DFI) using DCI for multi-cell scheduling according to the present disclosure.

[0025] 7 to 8 are diagrams illustrating example procedures associated with transmitting a DFI using DCI for multi-cell scheduling according to the present disclosure.

[0026] 9-10 are diagrams of example apparatuses for wireless communications according to the present disclosure. DETAILED DESCRIPTION

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

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

[0029] 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 applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] FIG. 1 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, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) 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, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0031] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. 1, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0032] In some examples, the cell may not necessarily be fixed, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

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

[0034] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 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 base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link.

[0036] UE 120 may be distributed 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 smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet 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 a 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, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0037] Some UEs 120 may be considered as 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 may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of 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, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a 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.

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

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–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 a “below 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 a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations 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–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); and decode the DCI to identify scheduling on the set of cells or identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC). Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI; and communicate with the UE based at least in part on a schedule or a DFI on the set of cells, the schedule or the DFI on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, FIG1 is provided as an example. Other examples may differ from that described with respect to FIG1 .

[0046] 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R ≥ 1).

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

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

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

[0050] 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 one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more of FIG. 2 ).

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 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 perform aspects of any of the methods described herein (eg, with reference to FIGS. 6A-10 ).

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

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with transmitting a DFI using a DCI for multi-cell scheduling, as described in more detail elsewhere herein. In some aspects, the network entity described herein is a base station 110, is included in a base station 110, or includes one or more components of a base station 110 shown in FIG. 2. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may perform or direct the operation of, for example, the process 700 of FIG. 7, the process 800 of FIG. 8, and / or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some examples, the memory 242 and / or the 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 by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after being compiled, converted, and / or interpreted), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct operations such as process 700 of FIG. 7 , process 800 of FIG. 8 , and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0054] In some aspects, the UE 120 includes means for receiving (e.g., using the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the controller / processor 280, the memory 282, etc.) a DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI; and / or means for decoding the DCI to identify scheduling on a set of cells or identifying a DFI (e.g., using the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the controller / processor 280, the memory 282, etc.) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a CRC. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication 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.

[0055] In some aspects, a network entity (e.g., base station 110) includes means for sending (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242, etc.) a DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI; and / or for communicating (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242, MIMO detector 236, receive processor 238, etc.) with the UE based at least in part on a schedule or a DFI on a set of cells, wherein the schedule or the DFI on the set of cells is decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a CRC. In some aspects, means for the network entity to perform operations described herein may include, for example, communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242, MIMO detector 236, receive processor 238, etc. One or more of a MIMO processor 230 , a modem 232 , an antenna 234 , a MIMO detector 236 , a receive processor 238 , a controller / processor 240 , a memory 242 , or a scheduler 246 .

[0056] Although the blocks in FIG2 are illustrated as distinct components, 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.

[0057] As indicated above, FIG2 is provided as an example. Other examples may differ from that described with respect to FIG2.

[0058] FIG3 is a diagram illustrating an example 300 of an open radio access network (O-RAN) architecture according to the present disclosure. As shown in FIG3, the O-RAN architecture may include a control unit (CU) 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links. The DUs 330 may each communicate with one or more radio units (RUs) 340 via corresponding fronthaul links, and the RUs 340 may each communicate with corresponding UEs 120 via radio frequency (RF) access links. The DUs 330 and RUs 340 may also be referred to as O-RAN DUs (O-DUs) 330 and O-RAN RUs (O-RUs) 340, respectively.

[0059] The DU 330 and the RU 340 may be implemented according to a functional split architecture, wherein the functionality of a base station 110 (e.g., an eNB or gNB) is provided by a DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, a base station 110 may include a DU 330 and one or more RUs 340, which may be co-located or geographically distributed. The DU 330 and associated RUs 340 may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0060] Thus, the 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. For example, the DU 330 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. Based at least in part on the lower layer functional split, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering). Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and the CU 310 to be implemented in a cloud-based radio access network (RAN) architecture.

[0061] As indicated above, FIG3 is provided as an example. Other examples may differ from that described with respect to FIG3.

[0062] FIG4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. As shown in FIG4, downlink channels and downlink reference signals may carry information from a network entity 402 to a UE 120, and uplink channels and uplink reference signals may carry information from a UE 120 to a network entity 402.

[0063] As shown, the downlink channels may include a physical downlink control channel (PDCCH) carrying DCI, a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. PDSCH communication may be scheduled via PDCCH communication. As further shown, the uplink channels may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, etc. UE 120 may send acknowledgement (ACK) or negative acknowledgement (NACK) (ACK / NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0064] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0065] The SSB may carry information used for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. The network entity 402 may send multiple SSBs on multiple corresponding beams, and the SSB may be used for beam selection.

[0066] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network entity 402 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurement, the UE 120 may perform channel estimation and may report channel estimation parameters (e.g., in a CSI report) such as CQI, a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or RSRP, etc., to the network entity 402. The network entity 402 may use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), a precoding matrix (e.g., a precoder), an MCS, or a refined downlink beam (e.g., using a beam refinement process or a beam management process), etc.

[0067] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and can be sent only when necessary. As shown in the figure, DMRS is used for both downlink and uplink communications.

[0068] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with increasing oscillator carrier frequency. Therefore, PTRS can be utilized at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0069] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network entity 402 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may require detecting downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. The network entity 402 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0070] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network entity 402 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured usages, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network entity 402 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0071] As indicated above, FIG4 is provided as an example. Other examples may differ from that described with respect to FIG4.

[0072] FIG5 is a diagram illustrating an example 500 of scheduling DCI for multiple cells according to the present disclosure. As shown in FIG5, a network entity 502 and a UE 120 may communicate with each other.

[0073] The network entity 502 may send DCI 505 to the UE 120 that schedules multiple communications for the UE 120. The multiple communications may be scheduled for at least two different cells. In some cases, a cell may be referred to as a "component carrier (CC)" or a "carrier". In some cases, DCI that schedules communications for a 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 a cell via which the DCI is sent may be referred to as "cross-carrier" or "cross-cell" scheduled DCI. The DCI 505 may be a cross-carrier scheduled DCI and may or may not be a self-carrier scheduled DCI. The DCI 505 that carries communications in at least two cells may be referred to as a combined DCI.

[0074] In example 500, DCI 505 schedules communications for a first cell 510 (shown as CC0) that carries DCI 505, schedules communications for a second cell 515 (shown as CC1) that does not carry DCI 505, and schedules communications for a third cell 520 (shown as CC2) that does not carry DCI 505. 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.

[0075] Communications scheduled by DCI 505 may include data communications, such as PDSCH communications or PUSCH communications. For data communications, 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 DCI 505 may include reference signals, such as CSI-RS or SRS. For reference signals, DCI 505 may trigger a single resource for reference signal transmission across multiple cells, or may schedule multiple resources separately for reference signal transmission in multiple cells. In some cases, scheduling information in DCI 505 may be indicated once and reused for multiple communications (e.g., on different cells), such as MCS, resources for ACK or NACK to be used for communications scheduled by DCI 505, and / or resource allocation for scheduling communications to save signaling overhead.

[0076] As indicated above, FIG5 is provided as an example. Other examples may differ from that described with respect to FIG5.

[0077] As described above, the DCI may have a DCI format including a set of fields for multi-cell scheduling. For example, a network entity may send a single DCI to schedule PUSCH and / or PDSCH on a set of cells of a single DCI. In this case, the network entity may configure a single DCI to schedule a set of cells through RRC signaling (e.g., the network entity may configure the UE so that the UE may interpret a single DCI as scheduling a set of cells). However, a single DCI may schedule one cell, some cells, or all cells in the configured set of cells. Similarly, in some cases, a single DCI may be configured to schedule up to 110 resource blocks (RBs) in a cell, but may actually schedule one RB, some RBs, or all RBs out of up to 110 RBs for a particular cell.

[0078] A network entity may send a DCI having a specific format and having a CRC scrambled with a CS-RNTI to activate or release downlink (DL) semi-persistent scheduling (SPS) (DL-SPS) resources or uplink (UL) configured grant (CG) (UL-CG) resources. Similarly, a network entity may use a DCI having a specific format and a CRC scrambled with a CS-RNTI to schedule a retransmission of a DL-SPS transmission or a UL-CG transmission. When the network entity configures the UE to interpret a specific DCI format as including activation, release, or retransmission of DL-SPS resources for UL-CG resources, the UE may monitor a specific DCI format with a CRC scrambled by a CS-RNTI and a specific DCI format scrambled with a C-RNTI. CS-RNTI-scrambled DCI (DCI with a CRC scrambled with a CS-RNTI) and C-RNTI-scrambled DCI (DCI with a CRC scrambled with a C-RNTI) may each have the same DCI size and the same set of control channel elements (CCEs). In other words, the CS-RNTI-scrambled DCI and the C-RNTI-scrambled DCI can be distinguished only from whether the CRC is scrambled with the CS-RNTI or with the C-RNTI.

[0079] When the UE is configured with cross-carrier scheduling, the DCI may include a carrier indicator field (CIF) indicating which scheduling cell the DCI format of the DCI applies to. In this case, the network entity may use RRC signaling to configure the mapping between each CIF value and the scheduled cell, and may be common across all dynamic PDSCH or PUSCH scheduling, DL-SPS activation, release or retransmission, UL-CG activation, release or retransmission, and CG downlink feedback information DFI (CG-DFI). However, when multi-cell scheduling via a single DCI is configured, the network entity and the UE may be out of sync on how to distinguish and interpret DCIs with the same DCI size and CCE, which may prevent the UE from using the DCI to successfully determine on which resources to communicate with the network entity and / or what information to communicate with the network entity.

[0080] Certain aspects described herein enable DFI to be sent using DCI for multi-cell scheduling. For example, the UE monitors the DCI format for PDSCH or PUSCH scheduling of up to N cells, and may check whether the candidate decoded by C-RNTI or CS-RNTI passes the CRC. In this case, when the candidate decoded by C-RNTI passes the CRC, the UE decodes the DCI as scheduling up to N cells for PDSCH or PUSCH communications. Alternatively, when the candidate decoded by CS-RNTI passes the CRC, the UE decodes the DCI as being used for DL-SPS or UL-CG activation, release or retransmission signaling or for CG-DFI signaling. In other words, in multi-cell scheduling, the network entity and the UE use C-RNTI or CS-RNTI encoding and decoding to distinguish how the UE interprets the DCI for subsequent communications.

[0081] 6A-6E are diagrams illustrating examples 600 associated with transmitting DFI using DCI for multi-cell scheduling according to the present disclosure. As shown in FIG. 6A , example 600 includes communications between a network entity 602 and a UE 120.

[0082] 6A and further illustrated by reference numeral 610, network entity 602 may send DCI encoded with a C-RNTI or a CS-RNTI. For example, UE 120 may monitor a set of resources (e.g., configured for UE 120 by network entity 602 using RRC signaling), and network entity 602 may send DCI in the set of resources. In this case, UE 120 may receive DCI in the set of resources.

[0083] As further shown in FIG. 6A and by reference numerals 620 and 630, the UE 120 may decode the DCI based at least in part on whether the C-RNTI or CS-RNTI passes the CRC, and communicate with the network entity 602 based at least in part on the decoded DCI. For example, the UE 120 may decode the candidate (e.g., data of the DCI) and determine whether the decoded candidate C-RNTI passes or satisfies the CRC (e.g., this indicates that the CRC is scrambled using the C-RNTI). In this case, if the C-RNTI passes the CRC, the UE 120 decodes the DCI and determines that the DCI is for PDSCH or PUSCH scheduling of up to N cells. As described above, although the DCI is configured to schedule a set of cells configured by RRC (multi-cell scheduling), the DCI may actually schedule only a single cell, a subset of a set of cells, or an entire set of cells. Alternatively, the UE 120 may determine whether the decoded candidate CS-RNTI passes or satisfies the CRC. In this case, the UE can determine the decoded candidate CS-RNTI through CRC, decode the DCI, and determine whether the DCI is used for DL-SPS or UL-CG activation, release or retransmission configuration and / or for CG-DFI transmission.

[0084] In some aspects, when the CS-RNTI satisfies the CRC, the UE 120 may determine the configuration of a single cell in a set of N cells for which the DCI is configured for scheduling (e.g., DL-SPS or UL-CG activation, release, or retransmission configuration). For example, the network entity 602 may configure DL-SPS transmission or UL-CG transmission on a single cell among the N cells. In this case, the UE 120 may identify the DCI and the associated N cells that may be scheduled by the DCI, and the UE 120 may determine the configuration indicated by the DCI. For example, as shown in FIG. 6B and by reference numeral 650, the UE 120 may map one or more values ​​of the CIF field in the DCI to one or more cells for dynamic PDSCH or PUSCH scheduling, but to only one cell for DL-SPS or UL-CG activation, release, or retransmission. Here, the CIF value "3" is mapped to three carriers CC#4, CC#5, and CC#6 for dynamic PDSCH or PUSCH scheduling, but is mapped to only CC#5 for DL-SPS or UL-CG activation, release, or retransmission. Therefore, UE 120 can communicate with network entity 602 on CC#5 according to the configuration of DCI (for example, UE 120 can send UL-CG transmission, can determine that network entity 602 has released DL-SPS resources, etc.).

[0085] Additionally or alternatively, as shown in FIG. 6B and by reference numeral 652, when UE 120 maps one or more values ​​of the CIF field in the DCI to multiple cells for DL-SPS or UL-CG activation, release, or retransmission, UE 120 may use rules for parsing which cell of the multiple cells the configuration of the DCI applies to. Here, CIF values ​​"2" and "3" are each mapped to multiple carriers. In some aspects, UE 120 may select a carrier from the multiple carriers based at least in part on the timing (e.g., an index of a subframe, time slot, symbol, etc.) at which the DCI is detected by UE 120. Additionally or alternatively, UE 120 may select a carrier based at least in part on the PDCCH (e.g., a search space index, a control source set (CORESET) index, a CCE index of a search space set) at which the DCI is detected. Additionally or alternatively, the network entity 602 may include an indication in the DCI (eg, in a frequency domain resource allocation (FDRA) field for the cell) of which carrier the UE 120 is to select.

[0086] Additionally or alternatively, as shown in FIG. 6B and by reference numeral 652, UE 120 may determine the carrier based at least in part on a received indication (e.g., an indication received in RRC, medium access control (MAC) control element (CE), or DCI signaling). For example, to enable multi-cell scheduling via DCI with C-RNTI, one or more CIF values ​​in the DCI may be mapped to more than one cell (e.g., CIF value "3" is mapped to carriers CC#4, CC#5, and CC#6). In this case, for DCI with the same CIF value and CS-RNTI, network entity 602 may send an indication of selecting a specific carrier for DL-SPS or UL-CG activation, release, or retransmission.

[0087] Additionally or alternatively, as shown in FIG. 6B and by reference numeral 654, the network entity 602 may configure DL-SPS transmission or UL-CG transmission on a single cell outside the N cells (the single cell being a cell that does not belong to the N cells). The UE 120 may map one or more values ​​of the CIF field in the DCI to one or more cells for dynamic PDSCH or PUSCH scheduling, but to only one cell for DL-SPS or UL-CG activation, release, or retransmission, wherein the cell for DL-SPS or UL-CG activation, release, or retransmission is a cell outside the one or more cells for dynamic PDSCH or PUSCH scheduling. Here, the CIF value "2" is mapped to two carriers CC#2 and CC#3 for dynamic PDSCH or PUSCH scheduling, but is mapped to CC#4 for DL-SPS or UL-CG activation, release, or retransmission. Therefore, UE 120 may communicate with network entity 602 on CC#4 according to the configuration of the DCI (e.g., UE 120 may send a UL-CG transmission, may determine that network entity 602 has released DL-SPS resources, etc.). In this case, as shown by reference numeral 654, for a CIF value of "2", UE 120 may use the received indication that CC#4 will be selected.

[0088] In some aspects, when the CS-RNTI satisfies the CRC, the UE 120 may determine the configuration of one or more cells in a set of N cells for which the DCI is configured for scheduling (e.g., DL-SPS or UL-CG activation, release, or retransmission configuration). For example, the network entity 602 may configure DL-SPS transmission or UL-CG transmission on one or more of the N cells. In this case, in order to enable multi-cell scheduling via DCI with C-RNTI, one or more CIF values ​​in the DCI are mapped to more than one cell, as shown in FIG. 6C and by reference numeral 660. For a DCI with a CIF value and a CS-RNTI, one or more cells may be indicated as having a DL-SPS or UL-CG activation, release, or retransmission configuration of the DCI. In this case, the UE 120 may identify which cells the DL-SPS or UL-CG activation, release, or retransmission configuration applies to based at least in part on another DCI field (such as an FDRA field or a hybrid automatic repeat request (HARQ) process number field, etc.). Reference numeral 660 shows an example when the one or more cells are a subset of N cells, however, as shown in reference numeral 662, the one or more cells may not be limited to the subset of N cells.

[0089] In some aspects, the UE 120 may determine whether the DCI conveys a CG-DFI for PUSCH transmission on one or more cells based at least in part on the DFI flag. For example, when the DFI flag is set to a configured value (e.g., "1") in the DCI and the DCI has a CRC scrambled by the CS-RNTI, the UE 120 may determine that the DCI conveys the CG-DFI. In this case, the DCI may include one or more fields to convey HARQ-ACK information for a set of HARQ processes for a serving cell indicated by the DCI corresponding to a transport block transmitted by the PUSCH. In some aspects, when the CIF field is present, the UE 120 may determine the serving cell indicated by the DCI based at least in part on the CIF field. Additionally or alternatively, when the CIF field is not present, the UE 120 may determine the serving cell indicated by the DCI based at least in part on the serving cell on which the DCI is received. Additionally or alternatively, the UE 120 may map a transmit power control (TPC) command field for the PUSCH in the serving cell to which the DCI applies. In some aspects, the UE 120 may map the HARQ-ACK feedback to the HARQ processes using a configured order. For example, the UE 120 may map the 16-bit bitmap of the DCI to a set of 16 HARQ processes in ascending order from the most significant bit (MSB) to the least significant bit (LSB) and in order of the index of each of the 16 HARQ processes. In some aspects, when the DCI conveys the CG-DFI, a set of bits may have values ​​for HARQ-ACK feedback, but other fields of the DCI may be set to configured values ​​(e.g., "0") instead of conveying other information.

[0090] In some aspects, when UE 120 determines that the DCI conveys a CG-DFI for PUSCH transmission on one or more cells, UE 120 may identify one or more cells for PUSCH transmission based at least in part on the configured mapping. For example, as shown in FIG. 6D and by reference numeral 670, UE 120 may select from a set of cells based at least in part on the corresponding index of the set of cells mapped to the CIF value (e.g., UE 120 may select the cell with the lowest index). Here, as shown by reference numeral 670, for a CIF value of "2" mapped to CC#2 and CC#3 for dynamic PDSCH or PUSCH scheduling, UE 120 may select CC#2 for CG-DFI based at least in part on CC#2 having a lower index than CC#3. Additionally or alternatively, UE 120 may select a carrier with a UL-CG configuration (e.g., when the UL-CG configuration is only on one of the one or more cells and the remaining cells in the one or more cells have, for example, a DL-SPS configuration). Additionally or alternatively, as indicated by reference numeral 672, the UE 120 may have a mapping dedicated to the configuration of the CG-DFI (e.g., separate from the mapping to the carrier for dynamic PDSCH or PUSCH scheduling). Additionally or alternatively, as indicated by reference numeral 674, the UE 120 may have a mapping for the configuration of more than one cell (e.g., for at least one of the CIF values). In this case, the UE 120 may select from the more than one cell based at least in part on a rule (e.g., all cells, all cells with UL-CG configuration, etc.) or based at least in part on a dedicated mapping.

[0091] In some aspects, the UE 120 may interpret the DCI with the DFI flag having the configured value as including a HARQ-ACK bitmap for one or more cells. For example, as shown in FIG. 6E and by reference numeral 680, the UE 120 may interpret the bitmap as including HARQ process indices of a first cell (e.g., a first CC) mapped in ascending order in a first sub-bitmap, HARQ process indices of a second cell (e.g., a second CC) mapped in ascending order in a second sub-bitmap, and so on, to form a HARQ-ACK bitmap (e.g., by concatenation of the sub-bitmaps). Additionally or alternatively, as shown by reference numeral 682, the UE 120 may interpret the bitmap as including different cells mapped in ascending order of cell indices per HARQ process identifier (HPID), which are concatenated to form the bitmap. In other words, the first sub-bitmap of HPID 0 includes HARQ feedback of a group of carriers in ascending order of index, the second sub-bitmap of HPID 1 includes HARQ feedback of the group of carriers in ascending order of index, and so on, and these sub-bitmaps are concatenated to form a bitmap.

[0092] In some aspects, the UE 120 may interpret a DCI having a DFI flag and a configured value as including a TPC command for one or more PUSCHs. For example, the UE 120 may identify a single TPC command field and apply the value in the single TPC command field to a set of serving cells, where the DCI includes HARQ-ACK information for PUSCH transmissions on the set of serving cells. Additionally or alternatively, the UE 120 may identify a set of TPC command fields applicable to the set of serving cells (e.g., via a one-to-one mapping). Additionally or alternatively, the UE 120 may map at least one TPC command to more than one serving cell and map at least one TPC command to a single serving cell (e.g., a combination of a one-to-one mapping and a one-to-many mapping). In this case, the UE 120 may then send a PUSCH transmission to the network entity 602 using a transmit power based at least in part on the one or more TPC commands included in the DCI.

[0093] As indicated above, Figures 6A-6E are provided as examples. Other examples may differ from those described with respect to Figures 6A-6E.

[0094] 7 is a diagram illustrating an example process 700, performed, for example, by a UE, in accordance with the present disclosure. Example process 700 is an example in which a UE (eg, UE 120) performs operations associated with transmitting a DFI with a DCI for multi-cell scheduling.

[0095] As shown in FIG7, in some aspects, process 700 may include receiving DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI (block 710). For example, a UE (e.g., using communication manager 140 and / or receiving component 902 as depicted in FIG9) may receive DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI, e.g., as described above with reference to FIG6A to FIG6E.

[0096] As further shown in FIG7, in some aspects, process 700 may include decoding the DCI to identify scheduling on a set of cells or identifying the DFI based at least in part on determining whether the C-RNTI or CS-RNTI satisfies the CRC (block 720). For example, the UE (e.g., using the communication manager 140 and / or decoding component 908 depicted in FIG9) may decode the DCI to identify scheduling on a set of cells or identifying the DFI based at least in part on determining whether the C-RNTI or CS-RNTI satisfies the CRC, e.g., as described above with reference to FIG6A to FIG6E.

[0097] Process 700 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.

[0098] In a first aspect, the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release, or retransmission for a single cell in a downlink semi-persistent scheduling scenario or a grant scenario of an uplink configuration.

[0099] In a second aspect, alone or in combination with the first aspect, the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from a set of cells associated with a DCI format for shared channel scheduling.

[0100] In a third aspect, alone or in combination with one or both of the first and second aspects, the single cell is based at least in part on a received indication of the single cell.

[0101] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for one or more cells in a downlink semi-persistent scheduling scenario or an uplink configured grant scenario.

[0102] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more cells are based at least in part on a subset of one or more cells from a set of cells associated with a DCI format for shared channel scheduling.

[0103] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more cells include at least one cell other than the group of cells monitored for receiving the DCI.

[0104] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the DCI includes a grant DFI for configuration of shared channel transmission on a single cell.

[0105] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, a single cell is based at least in part on a mapping of a carrier indicator field to a carrier.

[0106] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the DCI includes a grant DFI for configuration of shared channel transmission on one or more cells.

[0107] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more cells are based at least in part on a mapping of a carrier indicator field to one or more carriers.

[0108] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the DCI includes a HARQ ACK bitmap for one or more cells.

[0109] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a first set of HARQ process indices of a first cell among one or more cells are mapped in a static order and cascaded to a second set of HARQ process indices of a second cell among one or more cells to form a HARQ ACK bitmap.

[0110] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a first HARQ process index of one or more cells forms a first sub-bitmap of a HARQ ACK bitmap, which is cascaded to a second sub-bitmap corresponding to a second HARQ process index of one or more cells to form a HARQ ACK bitmap.

[0111] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the DCI includes at least one TPC command field for at least one uplink shared channel.

[0112] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, at least one TPC command field is a single TPC command field applicable to each serving cell in which HARQ ACK information of at least one uplink shared channel is included in the DCI.

[0113] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, at least one TPC command field is a TPC command field set, which is applicable to a cell group in which HARQ ACK information of at least one uplink shared channel is included in the DCI.

[0114] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, at least one TPC command field includes a first TPC command and a second TPC command, the first TPC command being applicable to a single cell in which HARQ ACK information is included in the DCI, and the second TPC command being applicable to a group of cells in which HARQ ACK information is included in the DCI.

[0115] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, one or more trailing bits in the DCI are set to 0 based at least in part on the DCI identifying scheduling on a set of cells or identifying a DFI.

[0116] Although Figure 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0117] 8 is a diagram illustrating an example process 800 performed, for example, by a network entity according to the present disclosure. Example process 800 is an example in which a network entity (e.g., base station 110, CU 310, DU 330, RU 340, network entity 402, network entity 502, or network entity 602, etc.) performs operations associated with transmitting a DFI using DCI for multi-cell scheduling.

[0118] As shown in FIG8, in some aspects, process 800 may include sending DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI (block 810). For example, a network entity (e.g., using communication manager 150 and / or transmitting component 1004 as depicted in FIG10) may send DCI associated with a DCI format for shared channel scheduling on a set of cells to a UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI, e.g., as described above with reference to FIG6A to FIG6E.

[0119] As further shown in FIG8, in some aspects, process 800 may include communicating with the UE based at least in part on a schedule or DFI on a set of cells, the schedule or the DFI on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or CS-RNTI satisfies the CRC (block 820). For example, a network entity (e.g., using the communication manager 150 and / or the receiving component 1002 or the sending component 1004 depicted in FIG10) may communicate with the UE based at least in part on a schedule or the DFI on a set of cells, the schedule or the DFI on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or CS-RNTI satisfies the CRC, e.g., as described above with reference to FIGS. 6A to 6E.

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

[0121] In a first aspect, the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release, or retransmission for a single cell in a downlink semi-persistent scheduling scenario or a grant scenario of an uplink configuration.

[0122] In a second aspect, alone or in combination with the first aspect, the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from a set of cells associated with a DCI format for shared channel scheduling.

[0123] In a third aspect, alone or in combination with one or both of the first and second aspects, the single cell is based at least in part on a received indication of the single cell.

[0124] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for one or more cells in a downlink semi-persistent scheduling scenario or an uplink configured grant scenario.

[0125] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more cells are based at least in part on a subset of one or more cells from a set of cells associated with a DCI format for shared channel scheduling.

[0126] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more cells include at least one cell other than the group of cells monitored for receiving the DCI.

[0127] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the DCI includes a grant DFI for configuration of shared channel transmission on a single cell.

[0128] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, a single cell is based at least in part on a mapping of a carrier indicator field to a carrier.

[0129] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the DCI includes a grant DFI for configuration of shared channel transmission on one or more cells.

[0130] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more cells are based at least in part on a mapping of a carrier indicator field to one or more carriers.

[0131] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the DCI includes a HARQ ACK bitmap for one or more cells.

[0132] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a first set of HARQ process indices of a first cell among one or more cells are mapped in a static order and cascaded to a second set of HARQ process indices of a second cell among one or more cells to form a HARQ ACK bitmap.

[0133] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a first HARQ process index of one or more cells forms a first sub-bitmap of a HARQ ACK bitmap, which is cascaded to a second sub-bitmap corresponding to a second HARQ process index of one or more cells to form a HARQ ACK bitmap.

[0134] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the DCI includes at least one TPC command field for at least one uplink shared channel.

[0135] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, at least one TPC command field is a single TPC command field applicable to each serving cell in which HARQ ACK information of at least one uplink shared channel is included in the DCI.

[0136] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, at least one TPC command field is a TPC command field set, which is applicable to a cell group in which HARQ ACK information of at least one uplink shared channel is included in the DCI.

[0137] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, at least one TPC command field includes a first TPC command and a second TPC command, the first TPC command being applicable to a single cell in which HARQ ACK information is included in the DCI, and the second TPC command being applicable to a group of cells in which HARQ ACK information is included in the DCI.

[0138] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, one or more trailing bits in the DCI are set to 0 based at least in part on the DCI identifying scheduling on a set of cells or identifying a DFI.

[0139] Although Figure 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted in Figure 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0140] 9 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 140. Communication manager 140 may include a decoding component 908, among others.

[0141] In some aspects, the device 900 may be configured to perform one or more operations described herein in conjunction with Figures 6A to 6E. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the device 900 and / or one or more components shown in Figure 9 may include one or more components of the UE described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 9 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code 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.

[0142] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 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 900. In some aspects, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the UE described in conjunction with FIG. 2.

[0143] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 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 906. In some aspects, the transmitting component 904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with FIG. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

[0144] The receiving component 902 can receive DCI associated with a DCI format for shared channel scheduling on a set of cells, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The decoding component 908 can decode the DCI to identify scheduling on a set of cells or identify a DFI based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies the CRC.

[0145] The number and arrangement of the components shown in FIG. 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. 9 . In addition, two or more components shown in FIG. 9 may be implemented within a single component, or a single component shown in FIG. 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 9 may perform one or more functions described as being performed by another set of components shown in FIG. 9 .

[0146] FIG. 10 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a network entity, or a network entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 150. Communication manager 150 may include encoding component 1008, etc.

[0147] In some aspects, the device 1000 may be configured to perform one or more operations described herein in conjunction with Figures 6A to 6E. Additionally or alternatively, the device 1000 may be configured to perform one or more processes described herein, such as process 800 of Figure 8. In some aspects, the device 1000 and / or one or more components shown in Figure 10 may include one or more components of the network entity described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 10 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code 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.

[0148] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 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 device 1000. In some aspects, the receiving component 1002 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the network entities described in conjunction with FIG. 2.

[0149] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. 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 device 1006. In some aspects, the transmitting component 1004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the network entities described in conjunction with FIG. 2. In some aspects, the transmitting component 1004 may be co-located with the receiving component 1002 in a transceiver.

[0150] The sending component 1004 may send a DCI associated with a DCI format for shared channel scheduling on a set of cells to the UE, wherein the DCI is associated with a C-RNTI and a CS-RNTI. The receiving component 1002 and / or the sending component 1004 may communicate with the UE based at least in part on a schedule or a DFI on a set of cells, the schedule or the DFI on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies the CRC. The encoding component 1008 may encode the DCI with the C-RNTI or the CS-RNTI to indicate whether the DCI includes a schedule or a DFI on a set of cells.

[0151] The number and arrangement of the components shown in Figure 10 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in Figure 10. In addition, two or more components shown in Figure 10 may be implemented in a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, the component set (one or more components) shown in Figure 10 may perform one or more functions described as being performed by another component set shown in Figure 10.

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

[0153] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); and decoding the DCI to identify scheduling on the set of cells or identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

[0154] Aspect 2: The method according to aspect 1, wherein the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for a single cell in a downlink semi-persistent scheduling scenario or a grant scenario of uplink configuration.

[0155] Aspect 3: The method according to aspect 2, wherein the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from the set of cells associated with the DCI format for shared channel scheduling.

[0156] Aspect 4: The method according to any one of aspects 2 to 3, wherein the single cell is based at least in part on a received indication of the single cell.

[0157] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for one or more cells in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

[0158] Aspect 6: The method according to aspect 5, wherein the one or more cells are based at least in part on a subset of one or more cells from the set of cells associated with the DCI format for shared channel scheduling.

[0159] Aspect 7: The method according to any one of aspects 5 to 6, wherein the one or more cells include at least one cell other than the group of cells monitored for receiving the DCI.

[0160] Aspect 8: The method according to any one of aspects 1 to 7, wherein the DCI includes a grant DFI for configuration of shared channel transmission on a single cell.

[0161] Aspect 9: The method of aspect 8, wherein the single cell is based at least in part on a mapping of a carrier indicator field to a carrier.

[0162] Aspect 10: The method according to any one of aspects 1 to 9, wherein the DCI comprises a grant DFI for configuration of shared channel transmission on one or more cells.

[0163] Aspect 11: The method according to aspect 10, wherein the one or more cells are based at least in part on a mapping of a carrier indicator field to one or more carriers.

[0164] Aspect 12: The method according to any one of aspects 10 to 11, wherein the DCI comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) bitmap for the one or more cells.

[0165] Aspect 13: A method according to Aspect 12, wherein a first set of HARQ process indices of a first cell among the one or more cells are mapped in a static order and concatenated to a second set of HARQ process indices of a second cell among the one or more cells to form the HARQ ACK bitmap.

[0166] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the first HARQ process index of the one or more cells forms a first sub-bitmap of the HARQ ACK bitmap, and the first sub-bitmap is cascaded to a second sub-bitmap corresponding to the second HARQ process index of the one or more cells to form the HARQ ACK bitmap.

[0167] Aspect 15: The method according to any one of aspects 1 to 14, wherein the DCI comprises at least one transmit power control (TPC) command field for at least one uplink shared channel.

[0168] Aspect 16: A method according to aspect 15, wherein the at least one TPC command field is a single TPC command field, and the single TPC command field is applicable to each serving cell for which hybrid automatic repeat request (HARQ) acknowledgement (ACK) information of the at least one uplink shared channel is included in the DCI.

[0169] Aspect 17: A method according to any one of Aspects 15 to 16, wherein the at least one TPC command field is a TPC command field set, and the TPC command field set is applicable to a cell group in which hybrid automatic repeat request (HARQ) acknowledgment (ACK) information of the at least one uplink shared channel is included in the DCI.

[0170] Aspect 18: A method according to any one of Aspects 15 to 17, wherein the at least one TPC command field includes a first TPC command and a second TPC command, the first TPC command being applicable to a single cell in which hybrid automatic repeat request (HARQ) acknowledgment (ACK) information is included in the DCI, and the second TPC command being applicable to a cell group in which HARQ ACK information is included in the DCI.

[0171] Aspect 19: A method according to any one of aspects 1 to 18, wherein one or more trailing bits in the DCI are set to 0 based at least in part on the DCI identifying the scheduling on the set of cells or identifying the DFI.

[0172] Aspect 20: A method of wireless communication performed by a network entity, the method comprising: sending a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells to a user equipment (UE), wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); and communicating with the UE based at least in part on scheduling or downlink feedback information (DFI) on the set of cells, wherein the scheduling or downlink feedback information (DFI) on the set of cells is decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

[0173] Aspect 21: A method according to aspect 20, wherein the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for a single cell in a downlink semi-persistent scheduling scenario or a grant scenario of uplink configuration.

[0174] Aspect 22: The method according to aspect 21, wherein the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from the set of cells associated with the DCI format for shared channel scheduling.

[0175] Aspect 23: The method according to any one of aspects 21 to 22, wherein the single cell is based at least in part on a received indication of the single cell.

[0176] Aspect 24: A method according to any one of Aspects 20 to 22, wherein the CS-RNTI satisfies the CRC, and wherein the DCI is configured for activation, release or retransmission for one or more cells in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

[0177] Aspect 25: The method according to aspect 24, wherein the one or more cells are based at least in part on a subset of one or more cells from the set of cells associated with the DCI format for shared channel scheduling.

[0178] Aspect 26: The method according to any one of aspects 20 to 25, wherein the one or more cells include at least one cell other than the group of cells monitored for receiving the DCI.

[0179] Aspect 27: The method according to any one of aspects 20 to 25, wherein the DCI comprises a grant DFI for configuration of shared channel transmission on a single cell.

[0180] Aspect 28: The method of aspect 27, wherein the single cell is based at least in part on a mapping of a carrier indicator field to a carrier.

[0181] Aspect 29: The method according to any one of aspects 20 to 28, wherein the DCI comprises a grant DFI for configuration of shared channel transmission on one or more cells.

[0182] Aspect 30: The method of aspect 29, wherein the one or more cells are based at least in part on a mapping of a carrier indicator field to one or more carriers.

[0183] Aspect 31: The method according to any one of aspects 29 to 30, wherein the DCI comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) bitmap for the one or more cells.

[0184] Aspect 32: A method according to Aspect 31, wherein a first group of HARQ process indices of a first cell among the one or more cells are mapped in a static order and concatenated to a second group of HARQ process indices of a second cell among the one or more cells to form the HARQ ACK bitmap.

[0185] Aspect 33: A method according to any one of Aspects 31 to 32, wherein the first HARQ process index of the one or more cells forms a first sub-bitmap of the HARQ ACK bitmap, and the first sub-bitmap is cascaded to a second sub-bitmap corresponding to the second HARQ process index of the one or more cells to form the HARQ ACK bitmap.

[0186] Aspect 34: The method according to any one of aspects 20 to 33, wherein the DCI comprises at least one transmit power control (TPC) command field for at least one uplink shared channel.

[0187] Aspect 35: A method according to aspect 34, wherein the at least one TPC command field is a single TPC command field, and the single TPC command field is applicable to each serving cell for which hybrid automatic repeat request (HARQ) confirmation (ACK) information of the at least one uplink shared channel is included in the DCI.

[0188] Aspect 36: A method according to any one of Aspects 34 to 35, wherein the at least one TPC command field is a TPC command field set, and the TPC command field set is applicable to a cell group in which hybrid automatic repeat request (HARQ) acknowledgment (ACK) information of the at least one uplink shared channel is included in the DCI.

[0189] Aspect 37: A method according to any one of Aspects 34 to 36, wherein the at least one TPC command field includes a first TPC command and a second TPC command, the first TPC command being applicable to a single cell in which hybrid automatic repeat request (HARQ) acknowledgment (ACK) information is included in the DCI, and the second TPC command being applicable to a cell group in which HARQ ACK information is included in the DCI.

[0190] Aspect 38: A method according to any one of aspects 20 to 37, wherein one or more trailing bits in the DCI are set to 0 based at least in part on the DCI identifying the scheduling on the set of cells or identifying the DFI.

[0191] Aspect 39: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 19.

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

[0193] Aspect 41: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 19.

[0194] Aspect 42: 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 19.

[0195] Aspect 43: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 1 to 19.

[0196] Aspect 44: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 20 to 38.

[0197] Aspect 45: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 20 to 38.

[0198] Aspect 46: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 20 to 38.

[0199] Aspect 47: 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 20 to 38.

[0200] Aspect 48: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 20 to 38.

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

[0202] 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 as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0203] As used herein, "satisfying a threshold" may refer to a value being 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.

[0204] 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 the various aspects. Many of these features can be combined in ways that are not specifically listed in the claims and / or 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, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with 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 ordering of a, b, and c).

[0205] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more entries and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); as well as The DCI is decoded to identify scheduling on the set of cells or to identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

2. The method according to claim 1, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit a single cell in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

3. The method of claim 2, wherein the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from the set of cells associated with the DCI format for shared channel scheduling.

4. The method of claim 2, wherein the single cell is based at least in part on a received indication of the single cell.

5. The method of claim 1, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit one or more cells in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

6. The method of claim 5, wherein the one or more cells are based at least in part on a subset of the set of cells associated with the DCI format for shared channel scheduling. 7 . The method of claim 5 , wherein the one or more cells include at least one cell other than a group of cells monitored for receiving the DCI.

8. The method of claim 1, wherein the DCI comprises a grant DFI for configuration of shared channel transmission on a single cell.

9. The method of claim 8, wherein the single cell is based at least in part on a mapping of a carrier indicator field to a carrier.

10. The method of claim 1, wherein the DCI comprises a grant DFI for configuration of shared channel transmission on one or more cells.

11. The method of claim 10, wherein the one or more cells are based at least in part on a mapping of a carrier indicator field to one or more carriers.

12. The method of claim 10, wherein the DCI comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) bitmap for the one or more cells.

13. The method of claim 12, wherein a first set of HARQ process indices of a first cell among the one or more cells are mapped in a static order and concatenated to a second set of HARQ process indices of a second cell among the one or more cells to form the HARQ ACK bitmap.

14. The method of claim 12, wherein a first HARQ process index of the one or more cells forms a first sub-bitmap of the HARQ ACK bitmap, and the first sub-bitmap is concatenated to a second sub-bitmap corresponding to a second HARQ process index of the one or more cells to form the HARQ ACK bitmap.

15. The method of claim 1, wherein the DCI comprises at least one transmit power control (TPC) command field for at least one uplink shared channel.

16. The method of claim 15, wherein the at least one TPC command field is a single TPC command field applicable to each serving cell for which hybrid automatic repeat request (HARQ) acknowledgement (ACK) information of the at least one uplink shared channel is included in the DCI.

17. The method of claim 15, wherein the at least one TPC command field is a TPC command field set applicable to a cell group for which hybrid automatic repeat request (HARQ) acknowledgement (ACK) information of the at least one uplink shared channel is included in the DCI.

18. The method of claim 15, wherein the at least one TPC command field comprises a first TPC command and a second TPC command, the first TPC command being applicable to a single cell whose hybrid automatic repeat request (HARQ) acknowledgement (ACK) information is included in the DCI, and the second TPC command being applicable to a cell group whose HARQ ACK information is included in the DCI.

19. The method of claim 1, wherein one or more trailing bits in the DCI are set to zero based at least in part on the DCI identifying the schedule on the set of cells or identifying the DFI.

20. A method of wireless communication performed by a network entity, the method comprising: sending to a user equipment (UE) a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); as well as Communicate with the UE based at least in part on scheduling or downlink feedback information (DFI) on the set of cells, the scheduling or downlink feedback information (DFI) on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

21. The method of claim 20, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit a single cell in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

22. The method of claim 21, wherein the single cell is based at least in part on a cell configured with downlink semi-persistent scheduling or configured with a grant of uplink configuration from the set of cells associated with the DCI format for shared channel scheduling.

23. The method of claim 21, wherein the single cell is based at least in part on a received indication of the single cell.

24. The method of claim 20, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit one or more cells in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

25. The method of claim 24, wherein the one or more cells are based at least in part on a subset of one or more cells from the set of cells associated with the DCI format for shared channel scheduling.

26. The method of claim 24, wherein the one or more cells include at least one cell other than a group of cells monitored for receiving the DCI.

27. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); as well as The DCI is decoded to identify scheduling on the set of cells or to identify downlink feedback information (DFI) based at least in part on determining whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

28. The UE according to claim 27, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit a single cell in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.

29. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending to a user equipment (UE) a downlink control information (DCI) format associated with a shared channel scheduling on a set of cells, wherein the DCI is associated with a cell radio network temporary identifier (C-RNTI) and a configured scheduling radio network temporary identifier (CS-RNTI); as well as Communicate with the UE based at least in part on scheduling or downlink feedback information (DFI) on the set of cells, the scheduling or downlink feedback information (DFI) on the set of cells being decoded from the DCI based at least in part on whether the C-RNTI or the CS-RNTI satisfies a cyclic redundancy check (CRC).

30. The network entity of claim 29, wherein the CS-RNTI satisfies the CRC, and The DCI is configured to activate, release or retransmit a single cell in a downlink semi-persistent scheduling scenario or an uplink configuration grant scenario.