Hybrid automatic repeat request process space management for multi-cell scheduling

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may transmit multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication with a user equipment (UE), the multi-cell scheduling DCI including a hybrid automatic repeat request (HARQ) process identification field, the hybrid automatic repeat request (HARQ) process identification field is based at least in part on a merged HARQ process space associated with the at least two CCs. The network node may receive HARQ feedback associated with the multi-cell communication, the HARQ feedback based at least in part on the merged HARQ process space. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 817,819, filed on August 5, 2022, entitled “HYBRID AUTOMATIC REPEATREQUEST PROCESS SPACE MANAGEMENT FOR MULTI-CELL SCHEDULING,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for hybrid automatic repeat request process space management for multi-cell scheduling. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of 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 network nodes that support communications for wireless communication devices, such as a user equipment (UE) or multiple (UEs). The UE may communicate with the network nodes via downlink communications and uplink communications. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communications, such as via local links (e.g., side links (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. 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 network node. The method may include sending multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication with a user equipment (UE), the multi-cell scheduling DCI including a hybrid automatic repeat request (HARQ) process identification field, the hybrid automatic repeat request (HARQ) process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The method may include receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the combined HARQ process space.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication performed by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The method may include sending HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a merged HARQ process space associated with the at least two CCs. The one or more processors may be configured to receive HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the merged HARQ process space.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication performed by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The one or more processors may be configured to send HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a merged HARQ process space associated with the at least two CCs. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the merged HARQ process space.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication performed by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The instruction set, when executed by one or more processors of the UE, may cause the UE to send HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field.

[0013] Some aspects described herein relate to an apparatus. The apparatus may include means for sending a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a merged HARQ process space associated with the at least two CCs. The apparatus may include means for receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the merged HARQ process space.

[0014] Some aspects described herein relate to an apparatus. The apparatus may include means for receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The apparatus may include means for sending HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field.

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

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of 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 devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and 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] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

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

[0021] Figure 3 is a diagram illustrating an example of downlink control information (DCI) for scheduling a plurality of cells according to the present disclosure.

[0022] Figure 4A and Figure 4B is a diagram illustrating a first example in which a network node transmits a multi-cell scheduling DCI according to the present disclosure and a second example in which a UE assigns a HARQ process number based at least in part on the multi-cell scheduling DCI.

[0023] Figure 5 is a diagram illustrating an example of hybrid automatic repeat request (HARQ) retransmission based at least in part on multi-cell communication according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a wireless communication process between a network node and a UE according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a wireless communication process between a network node and a UE according to the present disclosure.

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

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

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

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

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

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

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

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

[0034] In some examples, the network node 110 is a network node that communicates with the UE 120 via a radio access link, such as an RU, or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU, or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is a network node that includes communicating with other network nodes 110 via a midhaul link or communicating with a core network via a backhaul link, such as a CU, or includes communicating with other network nodes 110 via a midhaul link or communicating with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network nodes 110 may include NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, transmit receive points (TRPs), DUs, RUs, CUs, mobility elements of a network, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, the network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0035] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, 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 a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

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

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

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

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

[0040] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can 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, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0041] 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 network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices 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 operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), 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 network node 110.

[0044] 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 to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0045] The frequency between FR1 and FR2 is generally referred to as mid-band frequency. Recent 5G NR research has identified the operating band for these mid-band frequencies as a frequency range designated FR3 (7.125GHz to 24.25GHz). The frequency band falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the characteristics of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, currently exploring higher frequency bands to extend 5G NR operation to more than 52.6GHz. For example, three higher operating bands have been identified as frequency ranges designated FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] 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 a frequency that can be lower than 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 a frequency 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.

[0047] In some aspects, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may perform the following operations: sending a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field based at least in part on a merged HARQ process space associated with the at least two CCs; and receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback based at least in part on the merged HARQ process space. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may perform operations such as receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field based at least in part on a combined HARQ process space associated with the at least two CCs; and sending HARQ feedback associated with the multi-cell communication, the HARQ feedback based at least in part on the HARQ process identification field. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

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

[0051] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a 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 (CQIs) received from the UE 120. The network node 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-coding) 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 upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a 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.

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

[0054] 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. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0055] 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 sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, 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 FIG. 4A to FIG. 11 ).

[0056] At the network node 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 network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). FIG. 4A to FIG. 11 ).

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component that can execute or guide e.g. Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to execute or direct, for example Figure 8 The process of 800 Fig. 9 The process 900 of , and / or the operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the network node includes: a component for sending a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; and / or a component for receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the combined HARQ process space. In some aspects, the components for the network node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0059] In some aspects, the UE includes: a component for receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication performed by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; and / or a component for sending HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field. The components for the UE to perform the operations described herein may include, for example, one or more of the following: 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.

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

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

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

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

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

[0065] Figure 3 3 is a diagram illustrating an example 300 of scheduling downlink control information (DCI) for multiple cells according to the present disclosure. Figure 3 As shown, network node 110 and UE 120 may communicate with each other (eg, directly or via one or more network nodes).

[0066] The network node 110 may send DCI 305 to the UE 120 (e.g., directly or via one or more network nodes) for scheduling 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). The DCI that schedules communications for the cell that sends the DCI may be referred to as self-carrier (or self-cell) scheduling DCI. The DCI that schedules communications for the cell that sends the DCI may be referred to as cross-carrier (or cross-cell) scheduling DCI. For illustration, the DCI 305 may be cross-carrier scheduling DCI, and may be self-carrier scheduling DCI or may not be self-carrier scheduling DCI. In some aspects, the DCI 305 carrying communications in at least two cells may be referred to as combined DCI.

[0067] In example 300, DCI 305 schedules communications for a first cell 310 (shown as CC0) that carries DCI 305, schedules communications for a second cell 315 (shown as CC1) that does not carry DCI 305, and schedules communications for a third cell 320 (shown as CC2) that does not carry DCI 305. While example 300 shows that DCI 305 may schedule three cells, other examples may include DCI 305 scheduling communications on a different number of cells (e.g., two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0068] The communication scheduled by DCI 305 may include data communication, such as physical downlink shared channel (PDSCH) communication or physical uplink shared channel (PUSCH) communication. For data communication, DCI 305 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs separately in multiple cells. Additionally or alternatively, the communication scheduled by DCI 305 may include reference signals, such as channel state information reference signals (CSI-RS) or sounding reference signals (SRS). For reference signals, DCI 305 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, the scheduling information in DCI 305 may be indicated once and reused for multiple communications (e.g., on different cells), such as modulation and coding scheme (MCS), resources for confirmation (ACK) or negative confirmation (NACK) of communications scheduled by DCI 305, and / or resource allocation for scheduled communications to save signaling overhead. In some aspects, the DCI may include hybrid automatic repeat request (HARQ) information.

[0069] HARQ refers to a retransmission protocol (e.g., a HARQ protocol) in which a wireless communication receiver device checks for errors in received data. If an error is detected, the receiver device may buffer the received data and request a retransmission from the wireless communication transmitter device. Based at least in part on the HARQ protocol, the receiver device may combine the buffered received data with the retransmitted data before channel decoding and error detection, which improves the performance of the retransmission. The HARQ protocol may be implemented at the medium access control (MAC) layer in the protocol stack.

[0070] The HARQ protocol relies on the transmitter device to receive an ACK or NACK from the receiver device. For illustration, a single HARQ process stops and waits for an ACK before continuing to transmit additional data. Therefore, the transmitter device may become inactive (for communication with the receiver wireless communication device) while waiting for an ACK or waiting for a scheduling opportunity. Multiple HARQ processes can be used to avoid the impact of round-trip time on throughput. That is, when a given HARQ process is waiting for an ACK, other HARQ processes can transmit data. The transmitter device can buffer the transmitted data until a positive ACK has been received (for example, in the case where a retransmission is required). Once a positive ACK has been received or the maximum number of allowed retransmissions has been reached, the data is cleared from the transmit buffer. Once the transmit buffer has been cleared, new data can be transmitted by the given HARQ process.

[0071] The HARQ protocol can be used on the downlink or uplink. "Downlink HARQ" may refer to the transmission of downlink data on the PDSCH, where the HARQ ACK is returned on the physical uplink control channel (PUCCH) or PUSCH. "Uplink HARQ" may refer to the transmission of uplink data on the PUSCH, where the HARQ confirmation is returned on the physical downlink control channel (PDCCH). For both downlink HARQ and uplink HARQ, each serving cell has its own HARQ entity and its own set of HARQ processes. In addition, both downlink HARQ and uplink HARQ are asynchronous, which means that there is no fixed timing pattern for each HARQ process. Instead, the network node must signal the identity of the relevant HARQ process with each downlink resource allocation. It is worth noting that although asynchronous HARQ increases signaling overhead, asynchronous HARQ increases flexibility because retransmissions do not have to be scheduled during specific time slots.

[0072] DCI may be used to provide dynamic downlink resource allocation on the PDCCH. The DCI associated with dynamic downlink resource allocation may include information that enables downlink HARQ operations, such as information indicating a HARQ process number, a new data indicator (NDI), a redundancy version (RV), a PDSCH to HARQ feedback timing indicator, a PUCCH resource indicator, a downlink assignment index (DAI), code block group (CBG) transmission information (CBGTI), CBG clear information (CBGFI), modulation and decoding (MCS) information, or frequency resource allocation information (e.g., resource block allocation information). Similarly, DCI may be used to provide dynamic uplink resource allocation on the PDCCH. The DCI associated with dynamic uplink resource allocation may include information that enables uplink HARQ operations, such as information indicating a HARQ process number, NDI, RV, or CBGTI.

[0073] In some aspects, maintaining multiple HARQ processes for each of multiple cells (e.g., multiple CCs) via a single DCI (e.g., DCI 305) may present challenges. For illustration, each PDSCH and / or PUSCH scheduled on a corresponding CC in a plurality of CCs may carry a separate transport block (TB), and a corresponding HARQ process ID (e.g., per CC HARQ process ID) may be assigned to each TB. Including per CC HARQ information in a single DCI may increase the size of the DCI, and result in more air interface resources (e.g., time resources and / or frequency resources) being used to send the DCI and fewer air interface resources being used to send the payload. Fewer air interface resources for payload transmission may result in increased data transmission delays and / or reduced data throughput in a wireless network. As another example, a common HARQ process ID (e.g., instead of a per CC HARQ process ID) may reduce the flexibility associated with multiple HARQ processes, such as delaying data transmission to one or more CCs in a plurality of CCs by a transmitter device to align the HARQ processes. Delaying data transmission may also result in increased data transmission delays and / or reduced data throughput in a wireless network.

[0074] Some techniques and devices described herein provide HARQ process space management for multi-cell scheduling. In some aspects, a network node may send a multi-cell scheduling DCI associated with at least two CCs of multi-cell communication with a UE. The multi-cell scheduling DCI may include a HARQ process identification field, which is based at least in part on a merged HARQ process space associated with at least two CCs. "Merged HARQ process space" may represent a set of CCs associated with multi-cell wireless communication performed by a device (e.g., selected by a network node), such as downlink dual connectivity, uplink dual connectivity, downlink carrier aggregation, and / or uplink carrier aggregation associated with the UE. The network node may then receive HARQ feedback associated with multi-cell communication, such as from the UE. In some aspects, the HARQ feedback is based at least in part on the merged HARQ process space, such as HARQ feedback for one or more HARQ processes associated with the CC merged in the HARQ process space.

[0075] In some aspects, a UE may receive a multi-cell scheduling DCI associated with at least two CCs of a multi-cell communication performed by the UE. The multi-cell scheduling DCI may include a HARQ process identification field, which is based at least in part on a merged HARQ process space associated with the at least two CCs. The UE may then send HARQ feedback associated with the multi-cell communication. In some aspects, the HARQ feedback may be based at least in part on the HARQ process identification field.

[0076] By using the merged HARQ process space, the network node can indicate multiple HARQ processes assigned to multiple CCs in a multi-cell scheduling DCI using fewer bits relative to a second DCI, the second DCI including a corresponding set of bits for each CC (e.g., each CC in multiple CCs associated with the same multi-cell communication). For example, the multi-cell scheduling DCI may indicate a first HARQ process ID for a first scheduled CC in multiple CCs, and the UE may derive additional HARQ process IDs for other CCs by incrementing the first HARQ process ID for each corresponding CC and / or each additional HARQ process. The multi-cell scheduling DCI using fewer bits can consume fewer air interface resources (e.g., relative to the second DCI) and reserve more air interface resources for payload transmission. Using more air interface resources for payload transmission increases data throughput and / or reduces data transmission latency. The ability to assign multiple HARQ process IDs to each CC also provides greater flexibility to HARQ management relative to using a common HARQ process ID, such as by eliminating the need to align HARQ processes with each other. The increased flexibility may reduce delays in the HARQ process, increase data throughput and / or reduce data transmission latency.

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

[0078] Figure 4A and Figure 4B is a diagram illustrating a first example 400 of a network node sending a multi-cell scheduling DCI and a second example 402 of a UE assigning a HARQ process number based at least in part on the multi-cell scheduling DCI according to the present disclosure.

[0079] like Figure 4A As shown in example 400 of , a network node 110 may participate in multi-cell wireless communication 404 with a UE 120, which may include multi-cell downlink communication (e.g., from the network node 110 to the UE 120) and / or multi-cell uplink communication (e.g., from the UE 120 to the network node 110). For illustration, the multi-cell wireless communication 404 may include a first transmission associated with a first component carrier 406 (first CC 406), a second transmission associated with a second component carrier 408 (second CC 408), a third transmission associated with a third component carrier 410 (third CC 410), and / or a fourth transmission associated with a fourth component carrier 412 (fourth CC 412). Thus, while example 400 shows four CCs associated with the multi-cell wireless communication 404, other examples may include more CCs and / or fewer CCs. For clarity, example 400 shows a single network node participating in the multi-cell wireless communication 404, but other examples may include more network nodes participating in the multi-cell wireless communication 404.

[0080] In some aspects, the network node 110 may determine to form a combined HARQ process space 414 based at least in part on the first CC 406, the second CC 408, the third CC 410, and the fourth CC 412 being associated with the multi-cell wireless communication 404. Alternatively or additionally, the network node 110 may form and / or configure the combined HARQ process space 414 based at least in part on the first CC 406, the second CC 408, the third CC 410, and the fourth CC 412 being associated with any combination of a cell group (CG), dual connectivity with the UE 120, a PUCCH cell group, and / or a PUCCH secondary cell (Scell). For illustration, the network node 110 may determine to form a first combined HARQ process space including the first CC 406, the second CC 408, the third CC 410, and the fourth CC 412 based at least in part on all CCs being in the same CG. Alternatively or additionally, the network node 110 may determine to form a second merged HARQ process space including all CCs in the CC based at least in part on the CCs participating in multi-cell dual connectivity communications with the UE 120, and / or determine to form a third HARQ process space including all CCs based at least in part on the CCs being in the same PUCCH cell group.

[0081] The network node 110 may determine to assign K HARQ processes to each of the N CCs included in the combined HARQ process space, where K is an integer (e.g., 16) and N is an integer (shown as four in the example 400). Thus, the network node 110 may assign K×N=M HARQ processes to the combined HARQ process space 414, where M is an integer representing the total number of HARQ processes associated with and / or assigned to the combined HARQ process space. For example, for N=4 CCs, the network node 110 may determine to assign K=16 HARQ processes to each CC, resulting in a total of M=64 HARQ processes assigned to the combined HARQ process space 414.

[0082] To indicate the total number of HARQ processes and / or one or more HARQ process number assignments to the UE 120, the network node 110 may send a multi-cell scheduling DCI 416, such as a multi-cell PDSCH scheduling DCI and / or a multi-cell PUSCH scheduling DCI, including a HARQ process identification field 418. In some aspects, the length and / or size of the HARQ process identification field 418 may indicate the total number of HARQ processes. As an example, the HARQ process identification field 418 may include log2(M) and / or in represents an upper limit function for rounding the result to an integer. Referring to the above example of M=64, the HARQ process identification field 418 may have Thus, the UE 120 can derive the total number of HARQ processes assigned to the combined HARQ process space 414 based at least in part on the size of the HARQ process identification field 418 .

[0083] The network node 110 may configure the HARQ process identification field 418 with a HARQ process identifier 420 (HPID 420). For example, the network node 110 may set the bit value of the HARQ process identification field 418 to a value n, where n is an integer. In some aspects, the network node 110 may indicate that the value (e.g., n) stored in the HARQ process identification field 418 is a first HARQ process identifier (ID) associated with a first scheduled CC in a multi-cell communication. As an example, the network node 110 may indicate a scheduling order of CCs (e.g., a first CC, a second CC, and / or a last CC) based at least in part on a radio resource control (RRC) configuration message and / or carrier subset information in a DCI and / or the UE 120 may determine the scheduling order of the CCs (e.g., a first CC, a second CC, and / or a last CC). For illustration, the network node 110 may indicate the scheduling order in the RRC configuration message based at least in part on including the CC list in the RRC configuration and ordering the CC list based at least in part on the scheduling order (e.g., listing the first CC in a first position within the list and / or listing the second CC in a second position within the list). The network node 110 may indicate a subset of CCs from the CC list based at least in part on the DCI. Alternatively or additionally, the network node 110 may indicate that a subsequent HARQ process ID for a subsequently scheduled CC in the multi-cell communication may be derived from the value stored in the HARQ process identification field 418, such as by indicating that the subsequent HARQ process ID may be derived based at least in part on incrementing the value by one.

[0084] like Figure 4BAs shown in example 402 of , UE 120 may receive multi-cell scheduling DCI 416 and recover HPD 420 from HARQ process identification field 418. In some aspects, UE 120 may assign a first HARQ process ID n to a first HARQ process associated with a first transport block (TB) 422 based at least in part on the first TB 422 being sent by and / or using a first scheduled CC (e.g., CC0). For illustration, UE 120 may assign the value indicated in HARQ process identification field 418 as the first HARQ process ID. Alternatively or additionally, UE 120 may derive additional HARQ process IDs from n, such as deriving a second HARQ process ID by incrementing n by 1 (e.g., n+1), deriving a third HARQ process ID by incrementing the second HARQ process ID by 1 (e.g., n+2), and / or deriving a fourth HARQ process ID by incrementing the third HARQ process ID by 1 (e.g., n+3). That is, UE 120 may derive subsequent HARQ process IDs as sequential (e.g., in a given order and consecutive) HARQ process IDs. The UE 120 may assign sequential HARQ process IDs to subsequently scheduled CCs participating in multi-cell communication (e.g., and / or each respective TB assigned to each respective scheduled CC), such as by assigning a second HARQ process ID (e.g., n+1) to a second TB 424 associated with a second scheduled CC (e.g., CC1), assigning a third HARQ process ID (e.g., n+2) to a third TB 426 associated with a third scheduled CC (e.g., CC2), and / or assigning a fourth HARQ process ID (e.g., n+3) to a fourth TB 428 associated with a fourth scheduled CC (e.g., CC3).

[0085] While example 400 shows that UE 120 increments the HARQ process ID and assigns the incremented HARQ process ID, other examples may include that UE 120 refrains from assigning the incremented HARQ process ID to the TB. For illustration, a start and length indicator value (SLIV) may represent an allocation (e.g., in the time domain) for a PDSCH, such as a start symbol and / or a number of (consecutive) symbols associated with the PDSCH allocation. In some aspects, UE 120 may detect an error in a received TB based at least in part on the SLIV, such as by failing to receive a PDSCH carrying a TB indicated by the SLIV. Based at least in part on detecting a SLIV error associated with a received TB, UE 120 may refrain from assigning the incremented HARQ process ID to a CC based at least in part on not receiving a TB on the CC associated with the SLIV error. In some aspects, UE 120 may assign the incremented HARQ process ID to the next TB received without the SLIV error.

[0086] By using a merged HARQ process group, a network node can indicate a single HARQ process ID in a multi-cell scheduling DCI, and further indicate the use of the single HARQ process ID to derive subsequent HARQ process IDs. Indicating a single HARQ process ID enables the network node to use fewer bits in the multi-cell scheduling DCI, and subsequently use fewer air interface resources. The reserved air interface resources can then be used for payload transmission. The ability to assign multiple HARQ process IDs based at least in part on sending a single HARQ process ID also provides increased flexibility to HARQ management relative to using a common HARQ process ID. The increased flexibility and reserved air interface resources for payload transmission increase data throughput and / or reduce data transmission latency in a wireless network.

[0087] As indicated above, Figure 4A and Figure 4B Other examples can be found in the Figure 4A and Figure 4B The examples described are different.

[0088] Figure 5 is a diagram illustrating an example 500 of HARQ retransmission based at least in part on multi-cell communication in accordance with the present disclosure.

[0089] Figure 5 The illustrated example 500 illustrates the progress of communication between the network node 110 and the UE 120. In some aspects, the example 500 may be considered as relating to Figure 4A and Figure 4B400 and 402. For example, UE 120 may receive a message based at least in part on the received message. Figure 4A The multi-cell scheduling DCI (e.g., the multi-cell scheduling DCI 416) further described herein and / or derived as described with respect to Figure 4B The multiple HARQ process IDs further described are configured with multiple HARQ process IDs. For clarity, example 500 illustrates a single network node 110, but other examples may use multiple network nodes, such as by using a respective network node for each CC.

[0090] As shown by reference numeral 502, the network node 110 may send one or more TBs to the UE 120 based at least in part on multi-cell communication (e.g., using multiple CCs). The top-to-bottom ordering of CCs shown in example 500 indicates an earliest-to-latest scheduling order for each CC in the multi-cell communication. For example, a first scheduled CC 504 (e.g., CC0 shown at the top position) may send a first TB 506, a second scheduled CC 508 (e.g., CC1 shown at the second position from the top position) may send a second TB 510, a third scheduled CC 512 (e.g., CC2 shown at the third position from the top position) may send a third TB 514, and / or a fourth scheduled CC 516 (e.g., CC3 shown at the bottom position) may send a fourth TB 518. In some aspects, the first TB 506, the second TB 510, the third TB 514, and / or the fourth TB 518 are original transmissions of data, as shown by the solid white fill, rather than retransmissions. Although the example 500 shows the multi-cell communication as a downlink communication from the network node 110 to the UE 120, other examples may include the multi-cell communication being an uplink communication from the UE 120 to the network node 110.

[0091] In some aspects, the UE 120 may assign a first HARQ process ID (eg, n) to a first HARQ process associated with the first TB 506. Figure 4BAs further described, the UE 120 may derive and assign a second HARQ process ID to a second HARQ process associated with the second TB 510, derive and assign a third HARQ process ID to a third HARQ process associated with the third TB 514, and / or derive and assign a fourth HARQ process ID to a fourth HARQ process associated with the fourth TB 518. As shown in example 500, the UE 120 may fail to receive one or more of the TBs. For illustration, and as shown by reference numeral 520, the UE 120 may fail to receive the second TB 510, such as due to a failure to receive the second TB 510 with a first number of bit errors that satisfy an error threshold. Alternatively or additionally, and as shown by reference numeral 522, the UE 120 may fail to receive the fourth TB 518 with a second number of bit errors that satisfy the error threshold.

[0092] As indicated by reference numeral 524, the UE 120 may send HARQ feedback 526 indicating one or more ACKs and / or NACKs to the network node 110 based at least in part on the reception of the first TB 506, the second TB 510, the third TB 514, and / or the fourth TB 518. In some aspects, the HARQ feedback 526 may include one or more HARQ process IDs, some of which may be derived by the UE 120.

[0093] As indicated by reference numeral 528, the network node 110 may retransmit the data to the UE 120 (illustrated by the diagonal hashing pattern). In some aspects, the network node 110 may send the retransmission using a different CC and / or serving cell than the CC and / or serving cell used for the retransmission of the original transmission. For illustration, the second scheduled CC 508 sends the original transmission of the second TB 510 associated with the HARQ process ID n+1, as indicated by reference numeral 502. However, and as indicated by reference numeral 530, a different CC (e.g., the first scheduled CC 504) may send the retransmission of the second TB associated with the HARQ process ID n+1. In some aspects, the different CC may send the retransmission based at least in part on the network node 110 prioritizing the retransmission and / or based at least in part on the different CC (e.g., the first scheduled CC 504) having an earlier schedule relative to the CC associated with the original transmission (e.g., the second scheduled CC 508).

[0094] After the retransmission indicated by reference numeral 530, the second scheduled CC 508 (e.g., the next available scheduled CC) may transmit a second original transmission (e.g., TB 532) associated with a different HARQ process ID than the first original transmission transmitted by the second scheduled CC 508. For example, the first original transmission (e.g., the second TB 510) by the second CC 508 has an association with HARQ process ID n+1, and the second original transmission (e.g., TB 532) has an association with HARQ process ID n+2. As indicated by reference numeral 534, the network node 110 may retransmit the fourth TB 518 based at least in part on the availability of the third scheduled CC 512. The network node 110 may alternate between retransmissions and / or original transmissions based at least in part on priority and / or the next scheduled CC. For illustration, after the retransmission of the fourth TB 518 as indicated by reference numeral 534, the network node may transmit the retransmission or the original transmission using the fourth scheduled CC 516.

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

[0096] Figure 6 is a diagram illustrating an example 600 of a wireless communication process between a network node (eg, network node 110) and a UE (eg, UE 120) according to the present disclosure.

[0097] As indicated by reference numeral 610, the network node 110 may form a merged HARQ process space. As an example, the network node 110 may form the merged HARQ process by selecting at least two CCs associated with multi-cell wireless communication with the UE 120, such as by selecting at least two CCs associated with dual connectivity and / or carrier aggregation associated with the UE 120. Alternatively or additionally, the network node 110 may form the merged HARQ process by selecting two or more CCs based at least in part on the CCs being in the same cell group, the same PUCCH cell group, and / or a PUCCH secondary cell. In some aspects, at least some of the CCs may be associated with different serving cells. For illustration, a first CC may be associated with a first serving cell and a second CC may be associated with a second serving cell. When forming the merged HARQ process space, the network node 110 may select a total number of HARQ processes to assign to the merged HARQ process space and / or associate with the merged HARQ process space, such as with respect to Figure 4A as further described.

[0098] As shown by reference numeral 620, the network node 110 may send a multi-cell scheduling DCI, and the UE 120 may receive the multi-cell scheduling DCI. In some aspects, the multi-cell scheduling DCI may be associated with scheduling a multi-cell PDSCH and / or a multi-cell PUSCH. Alternatively or additionally, the multi-cell scheduling DCI may include a HARQ process identification field that is based at least in part on the total number of HARQ processes assigned to the combined HARQ process space. For illustration, the number of bits used for the HARQ process identification field may be based at least in part on the total number of HARQ processes (e.g., log2(M) and / or For example, Figure 4A As further described, the network node 110 may indicate in the HARQ process identification field a first HARQ process ID associated with the first scheduled CC (e.g., and / or a first HARQ process for a first received TB associated with the first scheduled CC). The network node 110 may alternatively or additionally indicate that an additional HARQ process ID is derived based at least in part on the first HARQ process ID, such as by indicating that the first HARQ process ID is incremented by a value (e.g., one).

[0099] In some aspects, the network node 110 may form a merged HARQ process and / or associate the merged HARQ process with multiple CCs, but schedule a subset of CCs in the multiple CCs. For illustration, the network node 110 may determine to schedule a first subset of CCs in the multiple CCs, and determine to suppress scheduling a second subset of CCs in the multiple CCs. The network node 110 may indicate in the multi-cell scheduling DCI that the first HARQ process ID is associated with the first subset of CCs and disassociated from the second subset of CCs. That is, the network node 110 may indicate that the HARQ process IDs for the first subset of CCs are derived based at least in part on the HARQ process IDs indicated in the multi-cell scheduling DCI, and / or exclude the derivation and / or allocation of the HARQ process IDs for the second subset of CCs.

[0100] As shown by reference numeral 630, the network node 110 may transmit multi-cell communication, and the UE 120 may receive the multi-cell communication. Although example 600 shows multi-cell communication as downlink communication, other examples may include multi-cell communication as uplink communication. Therefore, multi-cell communication may be associated with PDSCH transmission and / or PUSCH transmission. As an example, the network node 110 may be associated with a first CC of multiple CCs for multi-cell communication. The network node 110 may send a first TB to the UE 120 based at least in part on using the PDSCH associated with the first CC. As another example, the network node 110 may receive a second TB from the UE 120 based at least in part on using the PUSCH associated with the first CC. As further described above, multi-cell communication may be based at least in part on multiple serving cells, each of which is associated with a corresponding CC of the multi-cell communication shown by reference numeral 630.

[0101] As shown by reference numeral 640, UE 120 may derive one or more HARQ process IDs based at least in part on the multi-cell scheduling DCI. As an example, UE 120 may derive the HARQ process ID based at least in part on the first HARQ process ID indicated in the HARQ process identification field of the multi-cell scheduling DCI. UE 120 may assign a first HARQ process ID to a first TB received using a first scheduled CC, and calculate a second HARQ process ID by incrementing the first HARQ process ID by one. UE 120 may assign a second HARQ process ID to a second TB (e.g., TB 424) received using a second scheduled CC (e.g., second CC 408), and calculate a third HARQ process ID by incrementing the second HARQ process ID by one.

[0102] In some aspects, the UE 120 may refrain from allocating and / or deriving a new HARQ process ID until the current HARQ process ID is assigned. For example, the UE may refrain from assigning the current HARQ process ID based at least in part on detecting a SLIV error associated with a received TB. The UE 120 may refrain from assigning the current HARQ process ID to the TB associated with the SLIV error, and then refrain from incrementing the current HARQ process ID (e.g., to derive a new HARQ process ID) until after the current HARQ process ID is assigned.

[0103] As shown by reference numeral 650, the UE 120 may send HARQ feedback based at least in part on the multi-cell communication shown by reference numeral 630, and the network node 110 may receive the HARQ feedback based at least in part on the multi-cell communication shown by reference numeral 630. Although example 600 shows that the UE 120 sends HARQ feedback and the network node 110 receives the HARQ feedback, other examples may include the network node 110 sending HARQ feedback and the UE 120 receiving the HARQ feedback. The HARQ feedback may include any combination of ACKs and / or NACKs based at least in part on a reception error detected by the UE 120. For example, the UE 120 may send a first ACK associated with a first received TB associated with a first CC, a first NACK associated with a second received TB associated with a second CC (e.g., received with error), a second ACK associated with a third received TB associated with a third CC, and a second NACK associated with a fourth received TB associated with a fourth CC (e.g., received with error). Thus, the HARQ feedback may include multi-cell HARQ feedback based at least in part on the multi-cell scheduling DCI and / or the first HARQ process ID indicated by the multi-cell scheduling DCI.

[0104] As shown by reference numeral 660, the network node 110 may send a retransmission based at least in part on the multi-cell communication shown by reference numeral 630, and the UE 120 may receive the retransmission based at least in part on the multi-cell communication shown by reference numeral 630. Although example 600 shows the network node sending the retransmission and the UE 120 receiving the retransmission, other examples may include the UE 120 sending the retransmission and the network node 110 receiving the retransmission. In some aspects, the network node 110 may send the retransmission using a second CC different from the first CC used to send the original transmission, such as with respect to Figure 5 as further described.

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

[0106] Figure 7 is a diagram illustrating an example 700 of a wireless communication process between a network node (eg, network node 110) and a UE (eg, UE 120) according to the present disclosure.

[0107] As shown in example 700, the network node 110 may form a merged HARQ process space, such as with respect to Figure 6Based at least in part on forming the combined HARQ process space, the network node 110 may indicate to the UE 120 a multi-cell scheduling DCI, such as regarding Figure 6 As further described by reference number 620.

[0108] As shown by reference numeral 710, the network node 110 and the UE 120 may communicate with each other based at least in part on the combined HARQ process space. For illustration, the network node 110 may send at least a first portion of a multi-cell downlink communication and / or the UE 120 may send at least a second portion of a multi-cell uplink communication received by the network node 110, as described with respect to Figure 6 Alternatively or additionally, UE 120 may derive one or more HARQ process IDs based at least in part on the multi-cell scheduling DCI, as described with respect to Figure 6 In some aspects, the UE 120 may send HARQ feedback to the network node 110 and / or the network node 110 may send HARQ feedback to the UE 120, as described with reference to 640. Figure 6 The multi-cell communication may be further described as reference numeral 650. Based at least in part on receiving the HARQ feedback, the network node 110 and / or the UE 120 may resend at least a portion of the multi-cell communication. The network node 110 and / or the UE 120 may iteratively communicate with each other based at least in part on any combination of the above actions, where each iteration may include a different combination of actions.

[0109] As indicated by reference numeral 720, the network node 110 may detect a state change associated with at least one CC included in the combined HARQ process space and / or participating in multi-cell communication associated with the UE 120. For illustration, the CC included in the combined HARQ process space and / or participating in multi-cell communication may be based at least in part on a secondary cell. The network node 110 may detect a state change of the secondary cell, such as an activation state change (e.g., a transition from an activated state to an inactive state or from an inactive state to an activated state) and / or a dormant state change (e.g., a transition from a dormant state to an activated state or from an activated state to a dormant state).

[0110] In some aspects, and based at least in part on detecting a state change associated with the secondary cell, the network node 110 may maintain the current merged HARQ process space. For example, the network node 110 may refrain from resetting the HARQ state for any HARQ process associated with the merged HARQ process space (e.g., refraining from resetting the HARQ state based at least in part on detecting a state change). Alternatively or additionally, the network node 110 may maintain the size of the HARQ process identification field in the multi-cell scheduling DCI. Thus, the network node 110 and the UE 120 may continue to communicate with each other based at least in part on the merged HARQ process space, as further described with respect to reference numeral 710.

[0111] Alternatively, and as indicated by reference numeral 730, the network node may update the combined HARQ process space. For illustration, the network node 110 may determine, based at least in part on detecting a change in state, that the number of activated CCs participating in multi-cell communication with the UE has changed from a first number of CCs to a second number of CCs. The change in the number of CCs may include the first number of CCs being less than the second number of CCs, or the first number of CCs being greater than the second number of CCs. In some aspects, and based at least in part on detecting the change in the number of CCs, the network node may recalculate the total number of HARQ processes for the updated combined HARQ process space (e.g., based at least in part on the second number of CCs).

[0112] Based at least in part on updating the combined HARQ process space, the network node 110 may determine that the number of activated CCs has decreased (e.g., the second number of CCs is less than the first number of CCs), and reset one or more HARQ processes associated with the number of activated CCs. For illustration, the network node 110 may instruct the UE 120 to reset a subset of HARQ processes currently associated with the number of activated CCs and / or the multi-cell scheduling DCI with respect to reference numeral 620. Alternatively, the network node 110 may determine that the number of activated CCs has increased, and refrain from resetting one or more HARQ processes associated with the number of activated CCs and / or the multi-cell scheduling DCI with respect to reference numeral 620.

[0113] As indicated by reference numeral 740, the network node 110 may indicate an updated multi-cell scheduling DCI to the UE 120, wherein the updated multi-cell scheduling DCI may be based at least in part on the updated combined HARQ process space. For example, the multi-cell scheduling DCI sent as indicated with respect to reference numeral 620 may have a first size and / or include a first HARQ process identification field with a first number of bits, the first number of bits being associated with the total number of HARQ processes assigned to the combined HARQ process space. The updated multi-cell scheduling DCI may have a second size and / or include a second HARQ process identification field with a second number of bits, the second number of bits being based at least in part on the updated total number of HARQ processes assigned by the network node 110 to the updated combined HARQ process space (e.g., based at least in part on the changed number of activated CCs). Therefore, based at least in part on the increase or decrease of participating CCs and / or the increase or decrease in the total number of HARQ processes assigned to the updated combined HARQ process space, the size of the updated multi-cell scheduling DCI may be different from the size of the (first) multi-cell scheduling DCI.

[0114] As indicated by reference numeral 750, the network node 110 and the UE 120 may communicate with each other based at least in part on the updated combined HARQ process space, as further described with respect to reference numeral 710. For illustration, the network node 110 and / or the UE 120 may iteratively communicate with each other based at least in part on any combination of: sending and / or receiving multi-cell communications, deriving and / or calculating HARQ process IDs based at least in part on the updated multi-cell scheduling DCI, receiving and / or sending HARQ feedback based at least in part on the derived HARQ process IDs, and / or resending TBs based at least in part on the HARQ feedback, wherein each iteration may include a different combination of actions.

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

[0116] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network node in accordance with the present disclosure. The example process 800 is an example in which a network node (eg, the network node 110) performs operations associated with HARQ process space management for multi-cell scheduling.

[0117] like Figure 8As shown, in some aspects, process 800 may include sending a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a merged HARQ process space associated with the at least two CCs (block 810). For example, a network node (e.g., using communication manager 150, sending component 1004, and / or merged HARQ process manager component 1008, as shown in FIG. 1 ) may include sending a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE, the multi-cell scheduling DCI including a HARQ process identification field, the HARQ process identification field being based at least in part on a merged HARQ process space associated with the at least two CCs (block 810). Fig.10 As depicted), a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with a UE may be sent, the multi-cell scheduling DCI including a HARQ process identification field based at least in part on a combined HARQ process space associated with the at least two CCs, as described above.

[0118] like Figure 8 As further shown, in some aspects, process 800 may include receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the combined HARQ process space (block 820). For example, a network node (e.g., using communication manager 150 and / or receiving component 1002, such as Fig.10 ) may receive HARQ feedback associated with multi-cell communication, the HARQ feedback being based at least in part on a combined HARQ process space, as described above.

[0119] By using the combined HARQ process space, the network node can indicate multiple HARQ processes assigned to multiple CCs in a multi-cell scheduling DCI using fewer bits relative to a second DCI, the second DCI including a corresponding set of bits for each CC (e.g., each CC in multiple CCs associated with the same multi-cell communication), and reserve air interface resources for payload transmission. Using more air interface resources for payload transmission increases data throughput and / or reduces data transmission latency.

[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 multi-cell scheduling DCI indicates multi-cell physical downlink shared channel scheduling.

[0122] In a second aspect, the multi-cell scheduling DCI indicates multi-cell physical uplink shared channel scheduling.

[0123] In a third aspect, process 800 includes configuring a merged HARQ process space based at least in part on the CG.

[0124] In a fourth aspect, merging HARQ process spaces is based at least in part on dual connectivity.

[0125] In a fifth aspect, the merged HARQ process space is based at least in part on PUCCH cell groups.

[0126] In a sixth aspect, the HARQ process space is merged based at least in part on the UE being configured with a PUCCH secondary cell.

[0127] In a seventh aspect, M is an integer associated with a total number of HARQ processes for the combined HARQ process space, and wherein the HARQ process identification field comprises log2(M) bits.

[0128] In an eighth aspect, process 800 includes including, in a HARQ process identification field, a first HARQ process ID associated with a first scheduled component carrier of at least two CCs.

[0129] In a ninth aspect, process 800 includes indicating that a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is based at least in part on incrementing the first HARQ process ID by an integer value of one.

[0130] In a tenth aspect, process 800 includes indicating refraining from assigning a HARQ process ID to one of at least two CCs based at least in part on detecting a SLIV error.

[0131] In an eleventh aspect, process 800 includes determining a first subset of CCs among at least two CCs to be scheduled, determining a second subset of CCs among at least two CCs to be suppressed from scheduling, and indicating in a multi-cell scheduling DCI that a first HARQ process ID is associated with the first subset of CCs and disassociated with the second subset of CCs.

[0132] In a twelfth aspect, receiving HARQ feedback further comprises receiving a negative acknowledgement for a first transport block associated with a first HARQ process, wherein the first HARQ process is associated with a first CC of at least two CCs, and resending the first transport block based at least in part on a second CC of the at least two CCs.

[0133] In a thirteenth aspect, the first CC is associated with a first serving cell and the second CC is associated with a second serving cell.

[0134] In a fourteenth aspect, at least two CCs are based at least in part on a secondary cell, and process 800 further includes detecting a state change for the secondary cell and maintaining a combined HARQ process space.

[0135] In the fifteenth aspect, the state change comprises at least one of an activated state change or a dormant state change.

[0136] In a sixteenth aspect, maintaining the combined HARQ process space includes refraining from resetting a HARQ state associated with the combined HARQ process space.

[0137] In a seventeenth aspect, the at least two CCs are based at least in part on a secondary cell, and process 800 further includes detecting a state change for the secondary cell and determining an updated combined HARQ process space based at least in part on the state change.

[0138] In the eighteenth aspect, determining the updated merged HARQ process space also includes determining that the number of activated CCs included in the at least two CCs has changed from a first number of CCs to a second number of CCs, and recalculating the total number of HARQ processes for the merged HARQ process space based at least in part on at least two CCs including the second number of CCs.

[0139] In a nineteenth aspect, method 800 includes the first amount being less than the second amount, or the first amount being greater than the second amount.

[0140] In a twentieth aspect, process 800 includes sending an updated multi-cell scheduling DCI based at least in part on an updated combined HARQ process space.

[0141] In a twenty-first aspect, wherein the updated multi-cell scheduling DCI has a first size based at least in part on a number of activated CCs including a second number of CCs, and wherein the multi-cell scheduling DCI has a second size based at least in part on the first number of CCs.

[0142] In a twenty-second aspect, a first HARQ process identification field size included in the updated multi-cell scheduling DCI is different from a second HARQ process identification field size included in the multi-cell scheduling DCI.

[0143] In a twenty-third aspect, determining that a number of activated CCs included in the at least two CCs has changed includes determining that the number of activated CCs has decreased, and wherein process 800 further includes resetting one or more HARQ processes associated with the number of activated CCs.

[0144] In a twenty-fourth aspect, determining that a number of activated CCs included in the at least two CCs has changed includes determining that the number of activated CCs has increased, and wherein process 800 further includes refraining from resetting one or more HARQ processes associated with the number of activated CCs.

[0145] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0146] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE in accordance with the present disclosure. Example process 900 is an example in which a UE (eg, UE 120) performs operations associated with HARQ process space management for multi-cell scheduling.

[0147] like Fig. 9 As shown, in some aspects, process 900 may include receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs (block 910). For example, the UE (e.g., using the communication manager 140 and / or the receiving component 1102, as shown in FIG. 1 ) may include receiving a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by the UE, the multi-cell scheduling DCI including a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs (block 910). Fig.11 ) as depicted may receive a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by a UE, the multi-cell scheduling DCI comprising a combined HARQ process identification field based at least in part on a combined HARQ process space associated with the at least two CCs, as described above.

[0148] like Fig. 9 As further shown, in some aspects, process 900 may include sending HARQ feedback associated with the multi-cell communication, the HARQ feedback based at least in part on the HARQ process identification field (block 920). For example, the UE (e.g., using communication manager 140 and / or transmitting component 1104, such as Fig.11 As depicted) may send HARQ feedback associated with multi-cell communication, the HARQ feedback being based at least in part on a HARQ process identification field, as described above.

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

[0150] In a first aspect, the multi-cell scheduling DCI indicates multi-cell physical downlink shared channel scheduling.

[0151] In a second aspect, the multi-cell scheduling DCI indicates multi-cell physical uplink shared channel scheduling.

[0152] In a third aspect, the HARQ process space is merged based at least in part on cell groups.

[0153] In a fourth aspect, merging HARQ process spaces is based at least in part on dual connectivity.

[0154] In a fifth aspect, the merged HARQ process space is based at least in part on PUCCH cell groups.

[0155] In a sixth aspect, the HARQ process space is merged based at least in part on the UE being configured with a PUCCH secondary cell.

[0156] In a seventh aspect, M is an integer associated with a total number of HARQ processes for the combined HARQ process space, and wherein the HARQ process identification field comprises log2(M) bits.

[0157] In an eighth aspect, process 900 includes receiving, in a HARQ process identification field, a first HARQ process ID associated with a first scheduled component carrier of at least two CCs.

[0158] In a ninth aspect, process 900 includes calculating a second HARQ process ID associated with a second scheduled component carrier of at least two CCs based at least in part on incrementing the first HARQ process ID by an integer value of one.

[0159] In a tenth aspect, process 900 includes refraining from assigning a HARQ process ID to one of at least two CCs based at least in part on detecting a SLIV error.

[0160] In an eleventh aspect, the multi-cell scheduling DCI indicates that a first HARQ process ID is associated with a first subset of CCs in at least two CCs and is disassociated from a second set of CCs in at least two CCs.

[0161] In the twelfth aspect, sending HARQ feedback also includes: sending a negative acknowledgment for a first transport block associated with a first HARQ process, wherein the first HARQ process is associated with a first CC of at least two CCs; and receiving a retransmission of the first transport block based at least in part on a second CC of the at least two CCs.

[0162] In a thirteenth aspect, the first CC is associated with a first serving cell and the second CC is associated with a second serving cell.

[0163] In a fourteenth aspect, process 900 includes receiving updated multi-cell scheduling DCI based at least in part on an updated combined HARQ process space.

[0164] In a fifteenth aspect, a first HARQ process identification field size included in the updated multi-cell scheduling DCI is different from a second HARQ process identification field size included in the multi-cell scheduling DCI.

[0165] In a sixteenth aspect, the updated combined HARQ space is changed from a first number of CCs to a second number of CCs based at least in part on a number of activated CCs included in the at least two CCs.

[0166] In a seventeenth aspect, method 900 includes the second amount being less than the first amount, or the second amount being greater than the first amount.

[0167] In an eighteenth aspect, the updated multi-cell scheduling DCI has a first size based at least in part on a number of activated CCs including a second number of CCs, and wherein the multi-cell scheduling DCI has a second size based at least in part on the first number of CCs.

[0168] In a nineteenth aspect, process 900 includes receiving an indication to reset one or more HARQ processes associated with a number of activated CCs.

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

[0170] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a network node, or a network node 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 one or more of merged HARQ process management components 1008, and the like.

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

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

[0173] 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 combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0174] The transmitting component 1004 may transmit a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication with the UE, the multi-cell scheduling DCI comprising a HARQ process identification field, the HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The receiving component 1002 may receive HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the combined HARQ process space.

[0175] The merged HARQ process manager component 1008 may configure the merged HARQ process space based at least in part on the CG. Alternatively or additionally, the merged HARQ process manager component 1008 may include a first HARQ process ID associated with a first scheduled component carrier of the at least two CCs in the HARQ process identification field. The merged HARQ process manager component 1008 may indicate that a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is based at least in part on incrementing the first HARQ process ID by an integer value of one. In some aspects, the merged HARQ process manager component 1008 may indicate to suppress assignment of a HARQ process ID to one of the at least two CCs based at least in part on detecting a SLIV error.

[0176] The merged HARQ process manager component 1008 may determine to schedule a first subset of CCs in the at least two CCs. Alternatively or additionally, the merged HARQ process manager component 1008 may determine to suppress scheduling a second subset of CCs in the at least two CCs. In some aspects, the merged HARQ process manager component 1008 may indicate in a multi-cell scheduling DCI that the first HARQ process ID is associated with the first subset of CCs and is disassociated from the second subset of CCs.

[0177] Transmitting component 1004 can transmit an updated multi-cell scheduling DCI based at least in part on the updated combined HARQ process space.

[0178] In some aspects, the combined HARQ process manager component 1008 included in the apparatus 1000 may perform as described with respect to Fig.11 One or more actions described with respect to incorporating one or more actions described for HARQ process manager component 1108.

[0179] Fig.10 The number and arrangement of components shown are provided as examples. Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The collection of (one or more) components shown in can perform the operations described by Fig.10 Another collection of components shown in the figure performs one or more functions.

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

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

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

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

[0184] The combined HARQ process manager component 1108 may receive, via the receiving component 1102, a multi-cell scheduling DCI associated with at least two CCs for multi-cell communication by the UE, the multi-cell scheduling DCI comprising a combined HARQ process identification field, the combined HARQ process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs. The combined HARQ process manager component 1108 may send, via the sending component 1104, HARQ feedback associated with the multi-cell communication, the HARQ feedback being based at least in part on the HARQ process identification field.

[0185] The merged HARQ process manager component 1108 may receive, via the receiving component 1102 and in the HARQ process identification field, a first HARQ process ID associated with a first scheduled component carrier of the at least two CCs. Alternatively or additionally, the merged HARQ process manager component 1108 may calculate a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs based at least in part on incrementing the first HARQ process ID by an integer value of one. In some aspects, the merged HARQ process manager component 1108 may refrain from assigning a HARQ process ID to one of the at least two CCs based at least in part on detecting a SLIV error.

[0186] Combined HARQ process manager component 1108 can receive updated multi-cell scheduling DCI based at least in part on the updated combined HARQ process space via receiving component 1102. Alternatively or additionally, combined HARQ process manager component 1108 can receive an indication via receiving component 1102 to reset one or more HARQ processes associated with the number of activated CCs.

[0187] In some aspects, the combined HARQ process manager component 1108 included in the apparatus 1100 may perform as described with respect to Fig.10 One or more actions described with respect to incorporating one or more actions described for HARQ process manager component 1008.

[0188] Fig.11 The number and arrangement of components shown are provided as examples. Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The assembly of (one or more) components shown may perform the operations described as being performed by Fig.11 Another collection of components shown performs one or more functions.

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

[0190] Aspect 1: A method of wireless communication performed by a network node, the method comprising: sending multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication with a user equipment (UE), the multi-cell scheduling DCI comprising a hybrid automatic repeat request (HARQ) process identification field, the hybrid automatic repeat request (HARQ) process identification field being at least partially based on a merged HARQ process space associated with the at least two CCs; and receiving HARQ feedback associated with the multi-cell communication, the HARQ feedback being at least partially based on the merged HARQ process space.

[0191] Aspect 2: The method according to aspect 1, wherein the multi-cell scheduling DCI indicates multi-cell physical downlink shared channel scheduling.

[0192] Aspect 3: The method according to aspect 1, wherein the multi-cell scheduling DCI indicates multi-cell physical uplink shared channel scheduling.

[0193] Aspect 4: According to the method according to any one of Aspects 1 to 3, the method also includes: configuring the combined HARQ process space at least partially based on a cell group (CG).

[0194] Aspect 5: The method according to aspect 4, wherein the merged HARQ process space is based at least in part on dual connectivity.

[0195] Aspect 6: The method according to any one of aspects 1 to 4, wherein the combined HARQ process space is based at least in part on a physical uplink control channel (PUCCH) cell group.

[0196] Aspect 7: The method according to aspect 6, wherein the merged HARQ process space is based at least in part on the UE being configured with a PUCCH secondary cell.

[0197] Aspect 8: A method according to any one of aspects 1 to 7, wherein M is an integer associated with the total number of HARQ processes for the combined HARQ process space, and wherein the HARQ process identification field comprises log2(M) bits.

[0198] Aspect 9: The method according to aspect 8, the method further comprising: including, in the HARQ process identification field, a first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs.

[0199] Aspect 10: The method according to aspect 9, the method further comprising: indicating a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is based at least in part on incrementing the first HARQ process ID by an integer value of one.

[0200] Aspect 11: The method according to aspect 9, further comprising: indicating suppression of assigning a HARQ process ID to one of the at least two CCs based at least in part on detecting a start length indicator value (SLIV) error.

[0201] Aspect 12: According to the method described in any one of Aspects 9 to 11, the method further includes: determining a first subset of CCs among the at least two CCs to be scheduled; determining a second subset of CCs among the at least two CCs to be suppressed from scheduling; and indicating in the multi-cell scheduling DCI that the first HARQ process ID is associated with the first subset of CCs and disassociated with the second subset of CCs.

[0202] Aspect 13: A method according to any one of Aspects 1 to 12, wherein receiving the HARQ feedback further includes: receiving a negative acknowledgment for a first transmission block associated with a first HARQ process, wherein the first HARQ process is associated with a first CC among the at least two CCs; and resending the first transmission block based at least in part on a second CC among the at least two CCs.

[0203] Aspect 14: The method according to aspect 13, wherein the first CC is associated with a first serving cell and the second CC is associated with a second serving cell.

[0204] Aspect 15: The method according to any one of aspects 1 to 14, wherein the at least two CCs are based at least in part on a secondary cell, and the method further includes: detecting a state change for the secondary cell; and maintaining the combined HARQ process space.

[0205] Aspect 16: The method according to aspect 15, wherein the state change comprises at least one of an activation state change or a dormant state change.

[0206] Aspect 17: The method according to aspect 15 or aspect 16, wherein maintaining the combined HARQ process space comprises: suppressing resetting a HARQ state associated with the combined HARQ process space.

[0207] Aspect 18: A method according to any one of aspects 1 to 14, wherein the at least two CCs are based at least in part on a secondary cell, and the method further comprises: detecting a state change for the secondary cell; and determining an updated combined HARQ process space based at least in part on the state change;

[0208] Aspect 19: A method according to Aspect 18, wherein determining the updated merged HARQ process space also includes: determining that the number of activated CCs included in the at least two CCs has changed from a first number of CCs to a second number of CCs; and recalculating the total number of HARQ processes for the merged HARQ process space based at least in part on the at least two CCs including the second number of CCs.

[0209] Aspect 20: The method according to Aspect 19, wherein: the first number is smaller than the second number, or the first number is larger than the second number.

[0210] Aspect 21: The method according to aspect 19 or aspect 20 further comprises: sending an updated multi-cell scheduling DCI based at least in part on the updated combined HARQ process space.

[0211] Aspect 22: A method according to Aspect 21, wherein the updated multi-cell scheduling DCI has a first size based at least in part on the number of activated CCs including the second number of CCs, and wherein the multi-cell scheduling DCI has a second size based at least in part on the first number of CCs.

[0212] Aspect 23: The method according to aspect 22, wherein a first HARQ process identification field size included in the updated multi-cell scheduling DCI is different from a second HARQ process identification field size included in the multi-cell scheduling DCI.

[0213] Aspect 24: A method according to any one of Aspects 19 to 23, wherein determining that the number of activated CCs included in the at least two CCs has changed includes: determining that the number of activated CCs has decreased, and wherein the method also includes: resetting one or more HARQ processes associated with the number of activated CCs.

[0214] Aspect 25: A method according to any one of Aspects 19 to 23, wherein determining that the number of activated CCs included in the at least two CCs has changed includes: determining that the number of activated CCs has increased, and wherein the method also includes: suppressing resetting one or more HARQ processes associated with the number of activated CCs.

[0215] Aspect 26: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) used for multi-cell communication performed by the UE, the multi-cell scheduling DCI comprising a combined hybrid automatic repeat request (HARQ) process identification field, the combined hybrid automatic repeat request (HARQ) process identification field being at least partially based on a combined HARQ process space associated with the at least two CCs; and sending HARQ feedback associated with the multi-cell communication, the HARQ feedback being at least partially based on the HARQ process identification field.

[0216] Aspect 27: The method according to aspect 26, wherein the multi-cell scheduling DCI indicates multi-cell physical downlink shared channel scheduling.

[0217] Aspect 28: The method according to aspect 26, wherein the multi-cell scheduling DCI indicates multi-cell physical uplink shared channel scheduling.

[0218] Aspect 29: A method according to any one of aspects 26 to 28, wherein the merged HARQ process space is based at least in part on a cell group.

[0219] Aspect 30: The method according to any one of aspects 26 to 28, wherein the merged HARQ process space is based at least in part on dual connectivity.

[0220] Aspect 31: The method according to aspect 26, wherein the combined HARQ process space is based at least in part on a physical uplink control channel (PUCCH) cell group.

[0221] Aspect 32: The method according to aspect 31, wherein the merged HARQ process space is based at least in part on the UE being configured with a PUCCH secondary cell.

[0222] Aspect 33: A method according to any one of Aspects 26 to 32, wherein M is an integer associated with the total number of HARQ processes for the combined HARQ process space, and wherein the HARQ process identification field comprises log2(M) bits.

[0223] Aspect 34: The method according to aspect 33, the method further comprising: receiving a first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs in the HARQ process identification field.

[0224] Aspect 35: The method according to aspect 34, the method further comprising: calculating a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs based at least in part on incrementing the first HARQ process ID by an integer value of one.

[0225] Aspect 36: The method according to aspect 35, the method further comprising: refraining from assigning a HARQ process ID to one of the at least two CCs based at least in part on detecting a start length indicator value (SLIV) error.

[0226] Aspect 37: The method according to aspect 35, wherein the multi-cell scheduling DCI indicates that the first HARQ process ID is associated with a first subset of CCs in the at least two CCs and is disassociated from a second set of CCs in the at least two CCs.

[0227] Aspect 38: A method according to any one of Aspects 26 to 37, wherein sending the HARQ feedback further includes: sending a negative acknowledgment for a first transmission block associated with a first HARQ process, wherein the first HARQ process is associated with a first CC among the at least two CCs; and receiving a retransmission of the first transmission block based at least in part on a second CC among the at least two CCs.

[0228] Aspect 39: The method according to aspect 38, wherein the first CC is associated with a first serving cell and the second CC is associated with a second serving cell.

[0229] Aspect 40: The method according to any one of aspects 26 to 39, the method further comprising: receiving an updated multi-cell scheduling DCI based at least in part on the updated combined HARQ process space.

[0230] Aspect 41: The method according to aspect 40, wherein a first HARQ process identification field size included in the updated multi-cell scheduling DCI is different from a second HARQ process identification field size included in the multi-cell scheduling DCI.

[0231] Aspect 42: The method according to aspect 40 or aspect 41, wherein the updated combined HARQ space is changed from a first number of CCs to a second number of CCs based at least in part on the number of activated CCs included in the at least two CCs.

[0232] Aspect 43: A method according to Aspect 42, wherein: the second number is smaller than the first number, or the second number is larger than the first number.

[0233] Aspect 44: A method according to Aspect 42 or Aspect 43, wherein the updated multi-cell scheduling DCI has a first size based at least in part on the number of activated CCs including the second number of CCs, and wherein the multi-cell scheduling DCI has a second size based at least in part on the first number of CCs.

[0234] Aspect 45: According to any one of aspects 42 to 44, the method further comprises: receiving an indication to reset one or more HARQ processes associated with the number of activated CCs.

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

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

[0237] Aspect 48: 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 perform the method according to one or more of aspects 1 to 25.

[0238] Aspect 49: 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 perform the method according to one or more of aspects 26 to 45.

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

[0240] Aspect 51: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 26 to 45.

[0241] Aspect 52: 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 25.

[0242] Aspect 53: 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 26 to 45.

[0243] Aspect 54: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 25.

[0244] Aspect 55: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 26 to 45.

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

[0246] 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 systems and / or methods 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 at least in part based on the description herein.

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

[0248] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and 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).

[0249] 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. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element 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 can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: transmitting multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication with a user equipment (UE), the multi-cell scheduling DCI comprising a hybrid automatic repeat request (HARQ) process identification field, the hybrid automatic repeat request (HARQ) process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; as well as HARQ feedback associated with the multi-cell communication is received, the HARQ feedback being based at least in part on the combined HARQ process space.

2. The apparatus of claim 1 , wherein M is an integer associated with a total number of HARQ processes for the combined HARQ process space, and The HARQ process identification field includes log2(M) bits.

3. The apparatus of claim 2, wherein the one or more processors are further configured to: A first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs is included in the HARQ process identification field.

4. The apparatus of claim 3, wherein the one or more processors are further configured to: Indicating a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is based at least in part on incrementing the first HARQ process ID by an integer value of one.

5. The apparatus of claim 3, wherein the one or more processors are further configured to: Determine to schedule a first subset of CCs in the at least two CCs; Determine to refrain from scheduling a second subset of CCs of the at least two CCs; and Indicating in the multi-cell scheduling DCI that the first HARQ process ID is associated with the first subset of CCs and disassociated from the second subset of CCs.

6. The apparatus of claim 1 , wherein to receive the HARQ feedback, the one or more processors are configured to: receiving a negative acknowledgement for a first transport block associated with a first HARQ process associated with a first CC of the at least two CCs; and The first transport block is resent based at least in part on a second CC of the at least two CCs.

7. The apparatus of claim 1, wherein the at least two CCs are based at least in part on a secondary cell, and wherein the one or more processors are further configured to: detecting a state change for the secondary cell; and Maintaining the combined HARQ process space.

8. The apparatus of claim 7, wherein to maintain the combined HARQ process space, the one or more processors are configured to: Resetting a HARQ state associated with the combined HARQ process space is refrained.

9. The apparatus of claim 1, wherein the at least two CCs are based at least in part on a secondary cell, and wherein the one or more processors are further configured to: detecting a state change for the secondary cell; and An updated combined HARQ process space is determined based at least in part on the state change.

10. The apparatus of claim 9, wherein to determine the updated combined HARQ process space, the one or more processors are configured to: determining that the number of activated CCs included in the at least two CCs has changed from a first number of CCs to a second number of CCs; and A total number of HARQ processes for the combined HARQ process space is recalculated based at least in part on the at least two CCs including the second number of CCs.

11. The apparatus of claim 10, wherein the one or more processors are further configured to: An updated multi-cell scheduling DCI is sent based at least in part on the updated combined HARQ process space.

12. The apparatus of claim 11, wherein the updated multi-cell scheduling DCI has a first size based at least in part on the second number of CCs, and The multi-cell scheduling DCI has a second size based at least in part on the first number of CCs.

13. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication by the UE, the multi-cell scheduling DCI comprising a combined hybrid automatic repeat request (HARQ) process identification field, the combined hybrid automatic repeat request (HARQ) process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; as well as HARQ feedback associated with the multi-cell communication is transmitted, the HARQ feedback being based at least in part on the HARQ process identification field.

14. The apparatus of claim 13, wherein M is an integer associated with a total number of HARQ processes for the combined HARQ process space, and The HARQ process identification field includes log2(M) bits.

15. The apparatus of claim 14, wherein the one or more processors are further configured to: A first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs is received in the HARQ process identification field.

16. The apparatus of claim 15, wherein the one or more processors are further configured to: A second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is calculated based at least in part on incrementing the first HARQ process ID by an integer value of one.

17. The apparatus of claim 16, wherein the one or more processors are further configured to: Assigning a HARQ process ID to one of the at least two CCs is refrained from based at least in part on detecting a start length indicator value (SLIV) error.

18. The apparatus of claim 13, wherein to send the HARQ feedback, the one or more processors are configured to: sending a negative acknowledgement for a first transport block associated with a first HARQ process associated with a first CC of the at least two CCs; and A retransmission of the first transport block is received based at least in part on a second CC of the at least two CCs.

19. The apparatus of claim 13, wherein the one or more processors are further configured to: An updated multi-cell scheduling DCI is received based at least in part on the updated combined HARQ process space.

20. The apparatus of claim 19, wherein a first HARQ process identification field size included in the updated multi-cell scheduling DCI is different from a second HARQ process identification field size included in the multi-cell scheduling DCI.

21. The apparatus of claim 19, wherein the updated combined HARQ space is changed from a first number of CCs to a second number of CCs based at least in part on a number of activated CCs included in the at least two CCs.

22. The apparatus of claim 21, wherein the one or more processors are further configured to: An indication to reset one or more HARQ processes associated with the number of activated CCs is received.

23. A method of wireless communication performed by a network node, the method comprising: transmitting multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication with a user equipment (UE), the multi-cell scheduling DCI comprising a hybrid automatic repeat request (HARQ) process identification field, the hybrid automatic repeat request (HARQ) process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; as well as HARQ feedback associated with the multi-cell communication is received, the HARQ feedback being based at least in part on the combined HARQ process space.

24. The method according to claim 23, further comprising: A first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs is included in the HARQ process identification field.

25. The method according to claim 24, further comprising: Indicating a second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is based at least in part on incrementing the first HARQ process ID by an integer value of one.

26. The method of claim 23, wherein receiving the HARQ feedback further comprises: receiving a negative acknowledgement for a first transport block associated with a first HARQ process associated with a first CC of the at least two CCs; as well as The first transport block is resent based at least in part on a second CC of the at least two CCs.

27. The method of claim 23, wherein the at least two CCs are based at least in part on a secondary cell, and the method further comprises: detecting a state change for the secondary cell; determining an updated combined HARQ process space based at least in part on the state change; determining that the number of activated CCs included in the at least two CCs has changed from a first number of CCs to a second number of CCs; as well as A total number of HARQ processes for the combined HARQ process space is recalculated based at least in part on the at least two CCs including the second number of CCs.

28. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving multi-cell scheduling downlink control information (DCI) associated with at least two component carriers (CCs) for multi-cell communication by the UE, the multi-cell scheduling DCI comprising a combined hybrid automatic repeat request (HARQ) process identification field, the combined hybrid automatic repeat request (HARQ) process identification field being based at least in part on a combined HARQ process space associated with the at least two CCs; as well as HARQ feedback associated with the multi-cell communication is transmitted, the HARQ feedback being based at least in part on the HARQ process identification field.

29. The method according to claim 28, further comprising: receiving, in the HARQ process identification field, a first HARQ process identifier (ID) associated with a first scheduled component carrier of the at least two CCs; and A second HARQ process ID associated with a second scheduled component carrier of the at least two CCs is calculated based at least in part on incrementing the first HARQ process ID by an integer value of one.

30. The method of claim 28, wherein sending the HARQ feedback further comprises: sending a negative acknowledgement for a first transport block associated with a first HARQ process associated with a first CC of the at least two CCs; as well as A retransmission of the first transport block is received based at least in part on a second CC of the at least two CCs.

Images