Hybrid automatic repeat request feedback codebook for multi-cell scheduling

By using the DCI-based subcodebook cascaded HARQ feedback mechanism in multi-cell scheduling scenarios, the problem of inefficient HARQ management in the prior art is solved, and more efficient network resource utilization and scheduling efficiency are achieved.

CN118923069APending Publication Date: 2024-11-08QUALCOMM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202380028886.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-03-06
Filing Date
2023-03-07
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In multi-cell scheduling scenarios, it is difficult for the prior art to efficiently manage hybrid automatic retransmission request (HARQ) feedback codebooks, resulting in insufficient utilization of network resources and inefficient scheduling efficiency.

Method used

User equipment (UE) and network nodes use subcodebooks in a set of subcodebooks for HARQ feedback by receiving and sending physical downlink shared channel (PDSCH) communications based on downlink control information (DCI) scheduling, at least Partly based on the DCI configuration, scheduling on a single carrier or multiple carriers, implementing single cell or multi-cell scheduling.

Benefits of technology

The formation of joint codebooks by cascaded subcodebooks reduces the utilization of network resources, improves the efficiency of HARQ feedback and scheduling flexibility, and improves the efficiency of multi-cell scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923069A_ABST
    Figure CN118923069A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI). The UE may transmit hybrid automatic repeat request (HARQ) feedback for the one or more PDSCH communications using a sub-codebook of a set of sub-codebooks based at least in part on whether the DCI is a first format configured for scheduling on a single carrier or a second format configured for scheduling on multiple carriers, the sub-codebook is a single-cell scheduling sub-codebook in the group of sub-codebooks or a multi-cell scheduling sub-codebook in the group of sub-codebooks. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 362,991, filed on April 14, 2022, entitled "HYBRID AUTOMATIC REPEAT REQUEST FEEDBACK CODEBOOK FOR MULTI-CELL SCHEDULING" and U.S. Non-Provisional Patent Application No. 18 / 178,989, filed on March 6, 2023, entitled "HYBRID AUTOMATIC REPEAT REQUEST FEEDBACK CODEBOOK FOR MULTI-CELL SCHEDULING" and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

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

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

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

[0006] 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 referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by 3GPP. NR is designed to support beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, thereby better supporting mobile broadband Internet access to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: receiving one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI). The method may include: sending hybrid automatic repeat request (HARQ) feedback using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein at least in part based on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: sending one or more PDSCH communications scheduled by a DCI. The method may include: receiving HARQ feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive one or more PDSCH communications scheduled by a DCI. The one or more processors may be configured to send HARQ feedback using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for scheduling the one or more PDSCH communications on a single carrier in a first format or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: send one or more PDSCH communications scheduled by a DCI. The one or more processors may be configured to: receive HARQ feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein at least in part based on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive one or more PDSCH communications scheduled by a DCI. The instruction set, when executed by one or more processors of the UE, may cause the UE to: send HARQ feedback using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication 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 one or more PDSCH communications scheduled by a DCI. The instruction set, when executed by one or more processors of the network node, may cause the network node to: receive HARQ feedback for the one or more PDSCH communications sent using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving one or more PDSCH communications scheduled by a DCI. The apparatus may include a component for sending HARQ feedback using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for scheduling the one or more PDSCH communications on a single carrier in a first format or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending one or more PDSCH communications scheduled by a DCI. The apparatus may include a component for receiving HARQ feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for scheduling the one or more PDSCH communications on a single carrier in a first format or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

[0015] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, 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 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 base station and a user equipment (UE) in a wireless network according to the present disclosure.

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

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

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

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

[0025] 7A to 7D is a diagram illustrating an example associated with using a hybrid automatic repeat request (HARQ) feedback codebook in a multi-cell scheduling scenario according to the present disclosure.

[0026] Figures 8 to 9 is a diagram illustrating an example process associated with using a HARQ feedback codebook in a multi-cell scheduling scenario according to the present disclosure.

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

[0028] The various aspects of the disclosure are described more fully below with reference to the accompanying drawings. However, the 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 disclosure. Instead, these aspects are provided so that the disclosure will be thorough and complete, and the protection scope of the disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the 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 disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein 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.

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

[0030] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), 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).

[0031] 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, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), 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)).

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

[0033] 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 with an association 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).

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

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

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

[0037] 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 link or a wired backhaul link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0038] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. 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.

[0039] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a 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.

[0040] 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, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

[0042] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs 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-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0044] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can broadly refer to frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is expected 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.

[0045] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI); and send hybrid automatic repeat request (HARQ) feedback for the one or more PDSCH communications using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is a first format configured for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: send one or more PDSCH communications scheduled by a DCI; and receive HARQ feedback for the one or more PDSCH communications sent using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is a first format configured for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0048] 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 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The 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 up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

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

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

[0052] 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 (within 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.

[0053] 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. 7A to FIG. 11 ).

[0054] 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 provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink 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. 7A to FIG. 11 ).

[0055] 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 of the 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 perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0056] In some aspects, the UE 120 includes means for receiving one or more PDSCH communications scheduled by a DCI; and / or means for sending HARQ feedback for the one or more PDSCH communications using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers. The means for the UE 120 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.

[0057] In some aspects, a network node (e.g., network node 110) includes means for sending one or more PDSCH communications scheduled by a DCI; and / or means for receiving HARQ feedback for the one or more PDSCH communications sent using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is a first format configured for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers. In some aspects, the means for the network node to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0058] 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 with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0059] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0060] 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 node, 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, 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).

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

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

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

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

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

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

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

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

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

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

[0071] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0072] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown, the downlink channel and the downlink reference signal may carry information from the network node 110 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network node 110 .

[0073] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying DCI, a PDSCH carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, as well as other examples. PDSCH communication may be scheduled by PDCCH communication. For example, the DCI of the PDCCH transmitted on the first carrier may include scheduling information for scheduling PDSCH on the first carrier and / or scheduling PDSCH on one or more second carriers (e.g., in a cross-carrier scheduling scenario). As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, as well as other examples. UE 120 may send confirmation (ACK) or negative confirmation (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on PUCCH and / or PUSCH. UE 120 may send HARQ feedback (eg, HARQ ACK or HARQ NACK) using a HARQ codebook, which may also be referred to as a “HARQ ACK codebook,” “HARQ-ACK codebook,” or “HARQ feedback codebook,” among other examples.

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

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

[0076] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network node 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters (e.g., in a CSI report) to the network node 110, such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or reference signal received power (RSRP), among other examples. The network node 110 may use the CSI report to select transmission parameters for downlink communication with the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or refined downlink beams (e.g., using a beam refinement procedure or a beam management procedure), etc.

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

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

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

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

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

[0082] Figure 5 is a diagram illustrating an example 500 of carrier aggregation according to the present disclosure.

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

[0084] As indicated by reference numeral 505, carrier aggregation may be configured in an intra-band contiguous mode, in which the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 510, carrier aggregation may be configured in an intra-band discontiguous mode, in which the aggregated carriers are discontiguous with each other and in the same frequency band. As indicated by reference numeral 515, aggregation may be configured in an inter-band discontiguous mode, in which the aggregated carriers are discontiguous with each other and in different frequency bands.

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

[0086] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0087] Figure 6 600 is a diagram illustrating an example of scheduling DCI for multiple cells according to the present disclosure. Figure 6 As shown, network node 110 and UE 120 may communicate with each other.

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

[0089] In example 600, DCI 605 schedules communications for a first cell 610 (shown as CC0) that carries DCI 605, schedules communications for a second cell 615 (shown as CC1) that does not carry DCI 605, and schedules communications for a third cell 620 (shown as CC2) that does not carry DCI 605. DCI 605 may schedule communications with Figure 6, (eg, two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0090] The communication scheduled by DCI 605 may include data communication, such as PDSCH communication or PUSCH communication. For data communication, DCI 605 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs in the multiple cells separately. Additionally or alternatively, the communication scheduled by DCI 605 may include a reference signal, such as CSI-RS or SRS. For reference signals, DCI 605 may trigger a single resource for reference signal transmission across multiple cells, or may schedule multiple resources separately for reference signal transmission in the multiple cells. In some cases, the scheduling information in DCI 605 may be indicated once and reused for multiple communications (e.g., on different cells), such as MCS, resources for HARQ ACK or NACK to be used for communications scheduled by DCI 605, and / or resource allocation for scheduled communications to save signaling overhead.

[0091] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.

[0092] As described above, the network node may send DCI to the UE to schedule PDSCH in a group of carriers or cells. For example, the network node may send a single-cell scheduling DCI for scheduling PDSCH in a single carrier or a multi-cell scheduling DCI for scheduling PDSCH in multiple carriers. The multi-cell scheduling DCI may be a DCI format configured to be able to schedule PDSCH on up to N cells, where N>1. In some cases, regardless of whether such DCI actually schedules PDSCH on multiple cells, the DCI is classified as multi-cell scheduling DCI, and the corresponding PDSCH is a multi-cell scheduled PDSCH. In some other cases, when such DCI does not schedule PDSCH on multiple cells (although the DCI format has a field that provides the ability to schedule PDSCH on multiple cells), the DCI is classified as a single-cell scheduling DCI, and the corresponding PDSCH is a single-cell scheduled PDSCH (for example, although scheduled by a DCI format for multi-cell scheduling).

[0093] In carrier aggregation, both single-cell scheduling and multi-cell scheduling may be allowed. For example, the network node may send a first set of single-cell scheduling DCI to schedule PDSCH on the first set of cells, and send a second set of multi-cell scheduling DCI to schedule PDSCH on the second set of cells. The network node may provide uplink channel resources, such as in PUCCH or PUSCH, which the UE may use to send HARQ feedback for scheduled PDSCH. The UE may have a first codebook for sending HARQ feedback for single-cell scheduled PDSCH in the first PUSCH or PUCCH resource, and a second codebook for sending HARQ feedback for multi-cell scheduled PDSCH in the second PUSCH or PUCCH resource. However, sending HARQ feedback for single-cell scheduled PDSCH and multi-cell scheduled PDSCH may result in overutilization of network resources.

[0094] Some aspects described herein enable a UE to construct a joint codebook for single-cell scheduled PDSCH HARQ feedback and multi-cell scheduled PDSCH HARQ feedback using common uplink resources. In this case, the UE may form a HARQ feedback codebook by concatenating two subcodebooks. For example, the UE may concatenate or otherwise combine a first subcodebook for single-cell scheduling and a second subcodebook for multi-cell scheduling. In some aspects, the order of combination may be multi-cell scheduling first, followed by single-cell scheduling, or vice versa. In this case, the UE may use a combined codebook to generate HARQ feedback that the UE sends using, for example, a single PUSCH or PUCCH resource, thereby reducing the utilization of network resources relative to having separate uplink channel resources for single-cell scheduling HARQ feedback and multi-cell scheduling HARQ feedback.

[0095] 7A to 7D is a diagram illustrating an example 700 associated with using a HARQ feedback codebook in a multi-cell scheduling scenario according to the present disclosure. Fig. 7A As shown, network node 110 and UE 120 may communicate with each other.

[0096] As in Fig. 7A 1 and further illustrated by reference numeral 710, UE 120 may receive DCI that schedules PDSCH on a group of carriers. For example, UE 120 may receive a first group of DCI messages associated with single-cell scheduling of PDSCH and a second group of DCI messages associated with multi-cell scheduling of PDSCH from network node 110. In this case, Figure 7BAs shown, for single-cell scheduling, UE 120 receives the following items in a first format: DCI on carrier #0, which schedules PDSCH on carrier #0; DCI on carrier #1, which schedules PDSCH on carrier #1; and DCI on carrier #4, which schedules PDSCH on carrier #4. In addition, for multi-cell scheduling, UE 120 receives the following items in a second format: DCI on carrier #1, which schedules PDSCH on carrier #2 and carrier #3; and DCI on carrier #5, which schedules PDSCH on carrier #5 and carrier #6, as shown.

[0097] return Fig. 7A , and as indicated by reference numeral 720, UE 120 may attempt to receive one or more PDSCHs. For example, UE 120 may receive a single-cell scheduled PDSCH and / or a multi-cell scheduled PDSCH from network node 110 on one or more carriers. In this case, Figure 7B As shown, for single-cell scheduling, UE 120 may attempt to receive PDSCH on carriers #0 to #6.

[0098] In some aspects, whether a particular DCI format is used for single-cell scheduling or multi-cell scheduling is semi-statically configured. For example, UE 120 may receive semi-static signaling (e.g., RRC signaling) indicating whether to monitor a first DCI format or a second DCI format in a cell. Additionally or alternatively, UE 120 may receive signaling (e.g., RRC or DCI) indicating whether to monitor a first format of DCI (e.g., for single-cell scheduling) or a second format of DCI (e.g., for multi-cell scheduling) in a cell. In this case, UE 120 may monitor both the first format and the second format, and the received DCI itself may indicate whether the received DCI is the first format or the second format. Additionally or alternatively, UE 120 may determine whether the second format of DCI in a cell is considered to be a DCI for single-cell scheduling or for multi-cell scheduling based on conditions. For example, if the second format of DCI in a cell schedules PDSCH on only one cell, the UE may determine that the second format of DCI in the cell is a DCI for single-cell scheduling.

[0099] return Fig. 7A , and as shown by reference numeral 730, UE 120 may send HARQ feedback. For example, UE 120 may send a HARQ feedback message (e.g., one or more HARQ-ACKs or HARQ-NACKs) via uplink channel resources. In this case, Figure 7BAs shown, UE 120 may multiplex HARQ feedback from carriers #0 to #6 onto a single PUCCH resource. Additionally or alternatively, UE 120 may multiplex HARQ feedback onto a single PUSCH resource. In this case, by multiplexing HARQ feedback from both a single-cell scheduled PDSCH and a multi-cell scheduled PDSCH onto a single uplink channel resource, UE 120 reduces utilization of network resources relative to using separate uplink channel resources for different types of DCI and associated PDSCHs (e.g., single-cell scheduled DCI and single-cell scheduled PDSCH and multi-cell scheduled DCI and multi-cell scheduled PDSCH).

[0100] In some aspects, the UE 120 may use a codebook to send combined HARQ feedback (e.g., HARQ feedback for a single-cell scheduled PDSCH and for a multi-cell scheduled PDSCH). For example, the UE 120 may concatenate a first subcodebook assigned for HARQ feedback for a PDSCH scheduled by a first format of DCI (e.g., a DCI format for single-cell scheduling) and a second subcodebook assigned for HARQ feedback for a PDSCH scheduled by a second format of DCI (e.g., a DCI format for multi-cell scheduling). Although some aspects are described herein in terms of concatenated operations, other types of combined operations are possible. Additionally or alternatively, the concatenated codebook as described herein may be a static codebook rather than a constructed codebook. In other words, instead of the UE 120 constructing a codebook by concatenating sub-codebooks, a codebook may be provided to the UE 120 that may correspond to a concatenation of two sub-codebooks (e.g., if the two sub-codebooks were concatenated, they would form the same codebook as the codebook provided to the UE 120).

[0101] In some aspects, the UE 120 may determine a downlink assignment index (DAI) value in conjunction with HARQ feedback. For example, a counter DAI (C-DAI) value (which results from counting the number of DCIs sent until the current serving cell and the current PDCCH monitoring opportunity) may be incremented on a per-subcodebook basis (e.g., separate C-DAI values ​​correspond to HARQ feedback for DCIs of a first format and DCIs of a second format). In this manner, the UE 120 avoids codebook size misalignment when DCIs other than the last DCI associated with the last HARQ ACK in the subcodebook are lost (e.g., not successfully received). Similarly, a total DAI (T-DAI) value is updated on a per-subcodebook basis, the total DAI value resulting from counting the total number of DCIs until the current PDCCH monitoring opportunity (e.g., in a certain T-DAI interval before being reset). In this manner, the UE 120 avoids codebook size misalignment when the DCI associated with the last HARQ ACK in the subcodebook is lost.

[0102] In some aspects, UE 120 may generate HARQ ACK feedback based at least in part on the configuration for monitoring DCI. For example, when the UE is statically instructed whether to monitor DCI of the first format or the second format, as described above, for single-cell scheduling, UE 120 may generate one or two HARQ ACK bits per DAI count for PUCCH or PUSCH transmission. In this case, when UE 120 is configured with parameter maxNrofCodeWordsScheduledByDCI (where two transport blocks are used for at least one downlink bandwidth portion of at least one serving cell in which DCI for single-cell scheduling can schedule PDSCH), and when UE 120 is not configured with harq-ACK-SpatialBundlingPUCCH parameter or harq-ACK-SpatialBudlingPUSCH parameter in the cell group or PUCCH group, UE 120 may generate two HARQ ACK bits. Alternatively, when the UE 120 is not configured with the parameter maxNrofCodeWordsScheduledByDCI or when the UE 120 is configured with either of the parameters harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH, the UE 120 may generate one HARQ ACK bit.

[0103] Similarly, for multi-cell scheduling, UE 120 may generate Nmax HARQ bits per DAI count. In some aspects, parameter Nmax may be based at least in part on the number NPDSCH that may be received by a DCI scheduled PDSCH for multi-cell scheduling (in a particular carrier aggregation configuration), and at least in part on the number NTB of transport blocks for PUCCH or PUSCH transmission, for example, where Nmax = NPDSCH × NTB. When UE 120 is configured with parameter maxNrofCodeWordsScheduledByDCI (where two transport blocks are used for at least one downlink bandwidth portion of at least one serving cell in which a DCI for multi-cell scheduling may schedule a PDSCH), and when UE 120 is not configured with a harq-ACK-SpatialBundlingPUCCH parameter or a harq-ACK-SpatialBudlingPUSCH parameter in a cell group or PUCCH group, the number of transport blocks is two. Alternatively, when the UE 120 is not configured with the parameter maxNrofCodeWordsScheduledByDCI or when the UE 120 is configured with either of the parameters harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH, the number of transport blocks is one. Additionally or alternatively, in any serving cell where the DCI can schedule PDSCH for multi-cell scheduling, the UE 120 may set the number of transport blocks to one. In some aspects, the harq-ACK-SpatialBundlingPUCCH parameter or the harq-ACK-SpatialBudlingPUSCH parameter may be set on a per-cell basis for single-cell scheduling or multi-cell scheduling to enable different values ​​to be configured for NTB for single-cell scheduling and multi-cell scheduling.

[0104] In some aspects, the parameter Nmax may be at least partially based on a static configuration. For example, the UE 120 may receive RRC signaling identifying the value of Nmax. In this case, when Nmax > NTB × NPDSCH, the UE 120 may include up to NTB × NPDSCH bits of HARQ ACK feedback and may fill the NACK bits up to Nmax - NTB × NPDSCH bits (e.g., as padding). Additionally or alternatively, when Nmax < NTB × NPDSCH, the UE 120 may use one or more logical operations (e.g., an "AND" operation) to combine multiple HARQ ACK bits to reduce NTB × NPDSCH to be equal to Nmax. Although some aspects are described herein with the UE 120 performing the foregoing logical operations, in some aspects, the UE 120 may reduce the HARQ ACK bits in another form, such as by using a look-up table (e.g., which may be at least partially based on logical operations). In some aspects, the harq-ACK-SpatialBundlingPUCCH parameter or the harq-ACK-SpatialBudlingPUSCH parameter may be set on a per-cell basis for single-cell scheduling or multi-cell scheduling such that different values can be configured for NTB for single-cell scheduling and multi-cell scheduling.

[0105] Additionally or alternatively, when the UE is dynamically indicated to monitor DCI of a first format or DCI of a second format, as described above, for single-cell scheduling, the UE may generate one or two HARQ ACK bits per DAI count for PUCCH or PUSCH transmission. In this case, when the UE 120 is configured with maxNrofCodeWordsScheduledByDCI in a cell group of a PUCCH group (where two transport blocks are used for at least one downlink bandwidth part of at least one serving cell), and when the UE 120 is not configured with harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH in the cell group or the PUCCH group, the UE 120 may generate two HARQ ACK bits. Alternatively, when the UE 120 is not configured with the parameter maxNrofCodeWordsScheduledByDCI or when the UE 120 is configured with any one of the parameters harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH, the UE 120 may generate one HARQ ACK bit.

[0106] Similarly, in the case of a dynamic DCI format indication, for multi-cell scheduling, the UE 120 may generate Nmax HARQ bits per DAI count. In some aspects, the parameter Nmax may be Nmax=NPDSCH×NTB. When the UE 120 is configured with maxNrofCodeWordsScheduledByDCI in a cell group or PUCCH group (where two transport blocks are used for at least one downlink bandwidth portion of at least one serving cell), and when the UE 120 is not configured with harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH parameters in the cell group or PUCCH group, the number of transport blocks is two. Alternatively, when the UE 120 is not configured with maxNrofCodeWordsScheduledByDCI, or when the UE 120 is configured with either harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBudlingPUSCH, the number of transport blocks is one. Alternatively, in any serving cell where the DCI for multi-cell scheduling may schedule a PDSCH, the UE 120 may set the number of transport blocks to one.

[0107] Figure 7C and Fig.7D An example of T-DAI for UE 120 is shown when UE 120 is scheduled using a DCI of a first format associated with single-cell scheduling and a DCI of a second format associated with multi-cell scheduling. Figure 7C As shown, UE 120 monitors single-cell scheduling DCI on carriers #0, #1, and #4, but only monitors multi-cell scheduling DCI on carrier #1. As shown, when UE 120 is configured with more than one downlink cell for monitoring DCI format for single-cell scheduling or for multi-cell scheduling, T-DAI is included in the DCI. In this case, when UE 120 is not configured with more than one downlink cell for monitoring DCI for single-cell scheduling or for multi-cell scheduling, T-DAI is not included even when multiple downlink cells are configured in a carrier aggregation configuration. Therefore, as Figure 7C As shown (via deleted lines), for DCI for multi-cell scheduling, T-DAI is not included. As an alternative, T-DAI may be included in the DCI even if UE 120 is configured with only a single downlink cell for monitoring DCI for multi-cell scheduling. In another example, Fig.7DIn the example of FIG. 1 , when T-DAI is not included (e.g., as a result of only a single cell being configured for, e.g., multi-cell scheduling), T-DAI may be reused, and UE 120 may interpret the T-DAI value based on the reuse. Fig.7D As shown (via underlining), the T-DAI value for the multi-cell scheduling DCI is used as a repetition of the T-DAI value for the single-cell scheduling DCI in the same carrier (carrier #1), thereby improving reliability.

[0108] As indicated above, 7A to 7D are provided as examples. Other examples can be found in the 7A to 7D Different than described.

[0109] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE according to the present disclosure. Example process 800 is an example in which a UE (eg, UE 120) performs operations associated with using a HARQ feedback codebook in a multi-cell scheduling scenario.

[0110] like Figure 8 As shown, in some aspects, process 800 may include receiving a DCI scheduling one or more PDSCH communications (block 810). For example, a UE (e.g., using Fig.10 The communication manager 140 and / or receiving component 1002 depicted in FIG. 1004 may receive DCI that schedules one or more PDSCH communications, as described above. In some aspects, the one or more PDSCH communications may be scheduled on one or more carriers.

[0111] like Figure 8 As further shown, in some aspects, process 800 may include receiving the one or more PDSCH communications in accordance with the DCI (block 820). Fig.10 The communication manager 140 and / or receiving component 1002 depicted in FIG. 1004 may receive the one or more PDSCH communications according to the DCI, as described above. In some aspects, the one or more PDSCH communications may be received on one or more carriers.

[0112] like Figure 8 As further shown, in some aspects, process 800 may include sending HARQ feedback using a subcodebook from a set of subcodebooks for the one or more PDSCH communications (block 830). Fig.10The communication manager 140 and / or the transmitting component 1004 depicted in FIG. 1004 may transmit HARQ feedback using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, as described above. In some aspects, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is a first format configured for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

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

[0114] In a first aspect, the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

[0115] In a second aspect, alone or in combination with the first aspect, the C-DAI value for the DCI is incremented on a per sub-codebook basis for the set of sub-codebooks.

[0116] In a third aspect, alone or in combination with one or more of the first and second aspects, the T-DAI value for the DCI is incremented on a per sub-codebook basis for the set of sub-codebooks.

[0117] In a fourth aspect, alone or in combination with one or more of the first to third aspects, whether the DCI is in the first format or the second format is semi-statically configured for a cell.

[0118] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, whether the DCI is in the first format or the second format is dynamically indicated for a cell.

[0119] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the DCI is in a first format, and a number of HARQ bits of the HARQ feedback is based at least in part on a configuration of the UE.

[0120] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the DCI is in a second format, and the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a UE configuration or a radio resource control configuration parameter.

[0121] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, spatial bundling parameters for HARQ feedback are configured on a per-cell basis and based at least in part on whether the DCI is in a first format or a second format.

[0122] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, T-DAI parameters are included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

[0123] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, the UE is configured to interpret T-DAI parameters included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

[0124] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional 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 of the blocks in the process 800 may be performed in parallel.

[0125] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a network node according to the present disclosure. Example process 900 is an example in which a network node (e.g., network node 110, CU 310, DU 330, or RU 340) performs operations associated with using a HARQ feedback codebook in a multi-cell scheduling scenario.

[0126] like Fig. 9 As shown, in some aspects, process 900 may include sending a DCI that schedules one or more PDSCH communications (block 910). For example, a network node (e.g., using Fig.11 The communication manager 150 and / or the transmitting component 1104 depicted in FIG. 100 may transmit a DCI that schedules one or more PDSCH communications, as described above. In some aspects, the one or more PDSCH communications may be scheduled on one or more carriers.

[0127] like Fig. 9 As further shown, in some aspects, process 900 may include sending the one or more PDSCH communications in accordance with the DCI (block 920). Fig.11 The communication manager 150 and / or the transmitting component 1104 depicted in FIG. 100 may transmit the one or more PDSCH communications according to the DCI, as described above. In some aspects, the one or more PDSCH communications may be transmitted on one or more carriers.

[0128] like Fig. 9As further shown, in some aspects, process 900 may include receiving HARQ feedback sent using a subcodebook from a set of subcodebooks for the one or more PDSCH communications (block 930). Fig.11 The communication manager 150 and / or receiving component 1102 depicted in FIG. 1 may receive HARQ feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, as described above. In some aspects, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks, as described above, based at least in part on whether the DCI is a first format configured for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

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

[0130] In a first aspect, the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

[0131] In a second aspect, alone or in combination with the first aspect, the C-DAI value for the DCI is incremented on a per sub-codebook basis for the set of sub-codebooks.

[0132] In a third aspect, alone or in combination with one or more of the first and second aspects, the T-DAI value for the DCI is incremented on a per sub-codebook basis for the set of sub-codebooks.

[0133] In a fourth aspect, alone or in combination with one or more of the first to third aspects, whether the DCI is in the first format or the second format is semi-statically configured for a cell.

[0134] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, whether the DCI is in the first format or the second format is dynamically indicated for a cell.

[0135] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the DCI is in a first format, and a number of HARQ bits of the HARQ feedback is based at least in part on a configuration of the UE.

[0136] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the DCI is in a second format, and the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a UE configuration or a radio resource control configuration parameter.

[0137] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, spatial bundling parameters for HARQ feedback are configured on a per-cell basis and based at least in part on whether the DCI is in a first format or a second format.

[0138] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, T-DAI parameters are included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

[0139] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, the UE is configured to interpret T-DAI parameters included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

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

[0141] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a UE, or a UE 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 use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include a determining component 1008, as well as other examples.

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

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

[0144] 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, among other examples) 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 UE. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0145] The receiving component 1002 may receive a DCI for scheduling one or more PDSCH communications. The receiving component 1002 may receive the one or more PDSCH communications according to the DCI. The sending component 1004 may send HARQ feedback for the one or more PDSCH communications using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers. The determining component 1008 may construct and / or determine a codebook for sending HARQ feedback.

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

[0147] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending 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 use receiving component 1102 and sending component 1104 to communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include a determining component 1108, as well as other examples.

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

[0149] 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, among other examples) 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, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0150] 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, among other examples) 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 network node. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0151] The transmitting component 1104 may transmit a DCI for scheduling one or more PDSCH communications. The transmitting component 1104 may transmit the one or more PDSCH communications according to the DCI. The receiving component 1102 may receive HARQ feedback for the one or more PDSCH communications transmitted using a subcodebook in a set of subcodebooks, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured for a first format for scheduling the one or more PDSCH communications on a single carrier or a second format for scheduling the one or more PDSCH communications on multiple carriers. The determining component 1108 may determine the configuration of the device 1106 for constructing the codebook.

[0152] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be 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 illustrated set (one or more) of components may be described as being executable by Fig.11 Another group of components shown performs one or more functions.

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

[0154] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a physical downlink shared channel (PDSCH) communication scheduled by downlink control information (DCI); and sending hybrid automatic repeat request (HARQ) feedback for the one or more PDSCH communications using a subcodebook in a set of subcodebooks, wherein at least in part based on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks.

[0155] Aspect 2: According to the method of aspect 1, the method further includes: receiving the DCI scheduling the one or more PDSCH communications.

[0156] Aspect 3: The method according to any one of aspects 1 to 2, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

[0157] Aspect 4: The method according to any one of aspects 1 to 3, wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per-subcodebook basis for the set of subcodebooks.

[0158] Aspect 5: The method according to any one of aspects 1 to 4, wherein a total downlink assignment index (T-DAI) value for the DCI is incremented on a per-subcodebook basis for the set of subcodebooks.

[0159] Aspect 6: The method according to any one of aspects 1 to 5, wherein whether the DCI is in the first format or the second format is semi-statically configured for a cell.

[0160] Aspect 7: The method according to any one of aspects 1 to 6, wherein whether the DCI is in the first format or the second format is dynamically indicated for a cell.

[0161] Aspect 8: The method according to any one of aspects 1 to 7, wherein the DCI is in the first format, and wherein the number of HARQ bits of the HARQ feedback is based at least in part on the configuration of the UE.

[0162] Aspect 9: A method according to any one of aspects 1 to 8, wherein the DCI is in the second format, and wherein the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a UE configuration or a radio resource control configuration parameter.

[0163] Aspect 10: The method according to any one of aspects 1 to 9, wherein the spatial bundling parameters for the HARQ feedback are configured on a per-cell basis and based at least in part on whether the DCI is in the first format or the second format.

[0164] Aspect 11: A method according to any one of Aspects 1 to 10, wherein a total downlink assignment index (T-DAI) parameter is included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

[0165] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the UE is configured to interpret a total downlink assignment index (T-DAI) parameter included in the DCI based at least in part on the number of downlink cells configured for the UE to monitor the DCI.

[0166] Aspect 13: A method of wireless communication performed by a network node, the method comprising: sending a physical downlink shared channel (PDSCH) communication scheduled by downlink control information (DCI); and receiving a hybrid automatic repeat request (HARQ) feedback for the one or more PDSCH communications sent using a subcodebook in a set of subcodebooks, wherein at least in part based on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers, the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks.

[0167] Aspect 14: The method according to aspect 13 further comprises: receiving the DCI scheduling the one or more PDSCH communications.

[0168] Aspect 15: The method according to any one of aspects 13 to 14, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

[0169] Aspect 16: The method according to any one of aspects 13 to 15, wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per-subcodebook basis for the set of subcodebooks.

[0170] Aspect 17: The method according to any one of aspects 13 to 16, wherein a total downlink assignment index (T-DAI) value for the DCI is incremented on a per-subcodebook basis for the set of subcodebooks.

[0171] Aspect 18: The method according to any one of aspects 13 to 17, wherein whether the DCI is in the first format or the second format is semi-statically configured for a cell.

[0172] Aspect 19: The method according to any one of aspects 13 to 18, wherein whether the DCI is in the first format or the second format is dynamically indicated for a cell.

[0173] Aspect 20: The method according to any one of aspects 13 to 19, wherein the DCI is in the first format, and wherein the number of HARQ bits of the HARQ feedback is based at least in part on a configuration of a user equipment.

[0174] Aspect 21: A method according to any one of aspects 13 to 20, wherein the DCI is in the second format, and wherein the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a user equipment configuration or a radio resource control configuration parameter.

[0175] Aspect 22: The method according to any one of aspects 13 to 21, wherein the spatial bundling parameters for the HARQ feedback are configured on a per-cell basis and based at least in part on whether the DCI is in the first format or the second format.

[0176] Aspect 23: A method according to any one of Aspects 13 to 22, wherein a total downlink assignment index (T-DAI) parameter is included in the DCI based at least in part on the number of downlink cells configured for the user equipment to monitor the DCI.

[0177] Aspect 24: A method according to any one of Aspects 13 to 23, wherein the UE is configured to interpret a total downlink assignment index (T-DAI) parameter included in the DCI based at least in part on the number of downlink cells configured for the user equipment to monitor the DCI.

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

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

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

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

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

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

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

[0185] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more aspects of aspects 13 to 24.

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

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

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

[0189] 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, threads of execution, procedures and / or functions and other examples. As used herein, "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the system or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to specific software code herein to describe the operation and behavior of the system and / or method, 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.

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

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

[0192] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items 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 may be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) include: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: receiving one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI); and A hybrid automatic repeat request (HARQ) feedback is sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

2. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: The DCI scheduling the one or more PDSCH communications is received.

3. The UE of claim 1, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

4. The UE of claim 1 , wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks.

5. The UE of claim 1, wherein a total downlink assignment index (T-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks. The UE according to claim 1 , wherein whether the DCI is in the first format or the second format is semi-statically configured for a cell. 7 . The UE according to claim 1 , wherein whether the DCI is in the first format or the second format is dynamically indicated for a cell.

8. The UE of claim 1, wherein the DCI is in the first format, and wherein a number of HARQ bits of the HARQ feedback is based at least in part on a configuration of the UE.

9. The UE of claim 1, wherein the DCI is in the second format, and wherein the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a UE configuration or a radio resource control configuration parameter.

10. The UE of claim 1, wherein a spatial bundling parameter for the HARQ feedback is configured on a per-cell basis and based at least in part on whether the DCI is in the first format or the second format.

11. The UE of claim 1 , wherein a total downlink assignment index (T-DAI) parameter is included in the DCI based at least in part on a number of downlink cells configured for the UE to monitor the DCI.

12. The UE of claim 1, wherein the UE is configured to interpret a total downlink assignment index (T-DAI) parameter included in the DCI based at least in part on a number of downlink cells configured for the UE to monitor the DCI.

13. A network node for wireless communication, the network node include: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: transmitting one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI); and and receiving hybrid automatic repeat request (HARQ) feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

14. The network node of claim 13, wherein the one or more processors are further configured to cause the network node to: The DCI scheduling the one or more PDSCH communications is transmitted.

15. The network node of claim 13, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

16. The network node of claim 13, wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks.

17. The network node of claim 13, wherein a total downlink assignment index (T-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks.

18. The network node according to claim 13, wherein whether the DCI is in the first format or the second format is semi-statically configured for a cell.

19. The network node of claim 13, wherein whether the DCI is in the first format or the second format is dynamically indicated for a cell.

20. The network node of claim 13, wherein the DCI is in the first format, and The number of HARQ bits of the HARQ feedback is based at least in part on a configuration of the user equipment.

21. The network node of claim 13, wherein the DCI is in the second format, and Wherein the number of HARQ bits of the HARQ feedback is based at least in part on at least one of a user equipment configuration or a radio resource control configuration parameter.

22. The network node of claim 13, wherein spatial bundling parameters for the HARQ feedback are configured on a per-cell basis and based at least in part on whether the DCI is in the first format or the second format.

23. The network node of claim 13, wherein a total downlink assignment index (T-DAI) parameter is included in the DCI based at least in part on a number of downlink cells configured for user equipment to monitor the DCI.

24. The network node of claim 13, wherein a user equipment is configured to interpret a total downlink assignment index (T-DAI) parameter included in the DCI based at least in part on a number of downlink cells configured for the user equipment to monitor for the DCI.

25. A method of wireless communication performed by a user equipment (UE), the method include: receiving one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI); as well as A hybrid automatic repeat request (HARQ) feedback is sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

26. The method of claim 25, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

27. The method of claim 25, wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks.

28. A method of wireless communication performed by a network node, the method include: transmitting one or more physical downlink shared channel (PDSCH) communications scheduled by downlink control information (DCI); as well as and receiving hybrid automatic repeat request (HARQ) feedback sent using a subcodebook in a set of subcodebooks for the one or more PDSCH communications, wherein the subcodebook is a single-cell scheduling subcodebook in the set of subcodebooks or a multi-cell scheduling subcodebook in the set of subcodebooks based at least in part on whether the DCI is configured in a first format for scheduling the one or more PDSCH communications on a single carrier or a second format configured for scheduling the one or more PDSCH communications on multiple carriers.

29. The method of claim 28, wherein the set of sub-codebooks are concatenated to form a single HARQ codebook for both single-cell scheduling and multi-cell scheduling.

30. The method of claim 28, wherein a counter downlink assignment index (C-DAI) value for the DCI is incremented on a per subcodebook basis for the set of subcodebooks.

Citation Information

Patent Citations

  • Hybrid automatic repeat request feedback codebook for multi-cell scheduling

    US20230337256A1