Acknowledgement (ACK) and negative acknowledgement (NACK) reporting for physical downlink shared channel (PDSCH) grants

Abstract

This disclosure provides systems, methods, and apparatus for using ACK-NACK bundling when a user equipment (UE) reports bundled acknowledgments or negations (ACK-NACKs) for multiple PDSCHs associated with Physical Downlink Shared Channel (PDSCH) grants. A counter downlink assignment indicator (DAI) and a total DAI can be used to track PDSCH grants received at the UE. The UE can detect lost PDSCHs and report ACK-NACKs for the lost PDSCHs based on the counter DAI and the total DAI. A base station (BS) can send PDSCH grants associated with multiple PDSCHs to the UE. The BS can receive bundled ACK-NACKs from the UE for the multiple PDSCHs associated with the PDSCH grants.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to the following applications: U.S. Provisional Patent Application No. 63 / 198,341, filed October 12, 2020, entitled “ACKNOWLEDGEMENT (ACK) AND NEGATIVE ACKNOWLEDGEMENT (NACK) REPORTING FOR APHYSICAL DOWNLINK SHARED CHANNEL (PDSCH) GRANT”; and U.S. Non-Provisional Patent Application No. 17 / 449,761, filed October 1, 2021, entitled “ACKNOWLEDGEMENT (ACK) AND NEGATIVE ACKNOWLEDGEMENT (NACK) REPORTING FOR A PHYSICAL DOWNLINK SHARED CHANNEL (PDSCH) GRANT”, which are hereby expressly incorporated herein by reference. Technical Field

[0003] In summary, various aspects of this disclosure relate to wireless communications and to techniques for acknowledgment and negative acknowledgment (ACK / NACK) reporting for Physical Downlink Shared Channel (PDSCH) clearance. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems 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 / Improved LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

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

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, or global level. New Radio (NR) (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard released by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM) and CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, thereby better supporting mobile broadband internet access. Summary of the Invention

[0007] The systems, methods, and apparatus disclosed herein are innovative in several ways, but no single aspect is solely responsible for the intended properties of this disclosure.

[0008] One innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a user equipment (UE) apparatus. The method may include: receiving from a base station downlink control information (DCI) configured to schedule a plurality of physical downlink shared channels (PDSCHs), wherein the DCI indicates: a PDSCH to hybrid automatic repeat request (HARQ) feedback timing value, and a PUCCH resource indicator (PRI) associated with physical uplink control channel (PUCCH) resources; and using the PUCCH resources to send HARQ feedback to the base station for the plurality of PDSCHs.

[0009] One innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a device of a UE. The method may include: receiving a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; and sending bundled acknowledgments and negative acknowledgments (ACK-NACK) to the base station via a PUCCH for the plurality of PDSCHs.

[0010] One innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a device of a UE. The method may include: receiving a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; identifying a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs; and sending an ACK-NACK for the plurality of PDSCHs to the base station via a PUCCH based on the virtual DCI.

[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a UE (User Equipment) for wireless communication. The apparatus may include a first interface configured to obtain a DCI (Distributed Control Information Center) configured to schedule a plurality of PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI (Primary Information Point) associated with a PUCCH resource. The apparatus may include either the first interface or a second interface configured to use the PUCCH resource to output HARQ feedback for the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0012] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a UE for wireless communication. The apparatus may include a first interface configured to acquire a DCI, the DCI including PDSCH authorization for a plurality of PDSCHs. The apparatus may include either the first interface or a second interface configured to output bundled ACK-NACKs for the plurality of PDSCHs via a PUCCH. The apparatus may be implemented to perform any of the method steps described herein.

[0013] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a UE (User Equipment) for wireless communication. The apparatus may include a first interface configured to obtain a DCI (Distributed Control Interface) including PDSCH authorization for a plurality of PDSCHs. The apparatus may include a processing system configured to identify a virtual DCI associated with at least one PDSCH included among the plurality of PDSCHs. The apparatus may include either the first interface or a second interface configured to output an ACK-NACK for the plurality of PDSCHs via a PUCCH based on the virtual DCI. The apparatus may be implemented to perform any of the method steps described herein.

[0014] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to: receive from a base station a DCI configured to schedule a plurality of PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource; and use the PUCCH resource to send HARQ feedback to the base station for the plurality of PDSCHs. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the UE, are used to perform any of the method steps described herein.

[0015] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to: receive a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; and send a bundled ACK-NACK to the base station via a PUCCH for the plurality of PDSCHs. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the UE, are used to perform any of the method steps described herein.

[0016] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a UE, the one or more instructions may cause the one or more processors to: receive a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; identify a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs; and send an ACK-NACK for the plurality of PDSCHs to the base station via a PUCCH based on the virtual DCI. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the UE, are used to perform any of the method steps described herein.

[0017] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for receiving from a base station a DCI configured to schedule a plurality of PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource; and a unit for using the PUCCH resource to transmit HARQ feedback to the base station for the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0018] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for receiving a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; and a unit for transmitting bundled ACK-NACKs for the plurality of PDSCHs to the base station via a PUCCH. The apparatus may be implemented to perform any of the method steps described herein.

[0019] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for receiving a DCI from a base station, the DCI including PDSCH authorization for a plurality of PDSCHs; a unit for identifying a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs; and a unit for sending an ACK-NACK for the plurality of PDSCHs to the base station via a PUCCH based on the virtual DCI. The apparatus may be implemented to perform any of the method steps described herein.

[0020] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a base station apparatus. The method may include: sending a DCI configured to schedule a plurality of PDSCHs to a UE, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource; and using the PUCCH resource to receive HARQ feedback from the UE for the plurality of PDSCHs.

[0021] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a base station apparatus. The method may include: sending a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and receiving, via a PUCCH, bundled ACK-NACKs from the UE for the plurality of PDSCHs.

[0022] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method of wireless communication performed by a base station apparatus. The method may include: sending a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and receiving ACK-NACK from the UE via a PUCCH for the plurality of PDSCHs based on a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs.

[0023] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a base station used in wireless communication. The apparatus may include a first interface configured to output a DCI configured to schedule a plurality of PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource. The apparatus may include either the first interface or a second interface configured to use the PUCCH resource to obtain HARQ feedback for the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0024] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a base station used in wireless communication. The apparatus may include a first interface configured to output a DCI, the DCI including PDSCH grants for a plurality of PDSCHs. The apparatus may include either the first interface or a second interface configured to obtain bundled ACK-NACKs for the plurality of PDSCHs via a PUCCH. The apparatus may be implemented to perform any of the method steps described herein.

[0025] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for a base station used in wireless communication. The apparatus may include a first interface configured to output a DCI including PDSCH authorization for a plurality of PDSCHs. The apparatus may include either the first interface or a second interface configured to obtain ACK-NACK for the plurality of PDSCHs via a PUCCH based on a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0026] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: send a DCI configured to schedule multiple PDSCHs to a UE, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource; and use the PUCCH resource to receive HARQ feedback from the UE for the multiple PDSCHs. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the base station, are used to perform any of the method steps described herein.

[0027] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: send a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and receive bundled ACK-NACKs for the plurality of PDSCHs from the UE via a PUCCH. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the base station, are used to perform any of the method steps described herein.

[0028] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: send a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and receive an ACK-NACK from the UE via a PUCCH based on a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs. The non-transitory computer-readable medium may be implemented to store one or more instructions that, when executed by the one or more processors of the base station, are used to perform any of the method steps described herein.

[0029] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for transmitting to a UE a DCI configured to schedule a plurality of PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with a PUCCH resource; and a unit for using the PUCCH resource to receive HARQ feedback from the UE for the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0030] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for transmitting a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and a unit for receiving bundled ACK-NACKs for the plurality of PDSCHs from the UE via a PUCCH. The apparatus may be implemented to perform any of the method steps described herein.

[0031] Another innovative aspect of the subject matter described in this disclosure can be implemented in an apparatus for wireless communication. The apparatus may include: a unit for transmitting a DCI to a UE, the DCI including PDSCH authorization for a plurality of PDSCHs; and a unit for receiving ACK-NACK from the UE via a PUCCH based on a virtual DCI associated with at least one PDSCH included in the plurality of PDSCHs. The apparatus may be implemented to perform any of the method steps described herein.

[0032] In summary, the terms include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, or processing systems as fully described herein with reference to the accompanying drawings and as illustrated by the drawings.

[0033] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0034] Figure 1 This is a schematic diagram illustrating an example of a wireless network.

[0035] Figure 2 This is a schematic diagram illustrating an example of communication between a base station (BS) and a user equipment (UE) in a wireless network.

[0036] Figure 3This is a schematic diagram illustrating an example associated with Physical Downlink Shared Channel (PDSCH) permission.

[0037] Figure 4-9 This is a schematic diagram illustrating an example associated with an Acknowledgment-Nack (ACK-NACK) report, which has ACK-NACK bindings for PDSCH-permitted requests.

[0038] Figure 10-11 This is a schematic diagram illustrating an example of an ACK-NACK report associated with PDSCH permission for the Virtual Downlink Control Information (DCI).

[0039] Figure 12-14 This is a schematic diagram illustrating, for example, an example process performed by the UE.

[0040] Figure 15-17 This is a schematic diagram illustrating an example process, such as that performed by a BS.

[0041] Figure 18 and Figure 19 This is a block diagram of an example device for wireless communication.

[0042] Similar reference numerals and naming conventions in the various figures indicate similar elements. Detailed Implementation

[0043] For the purpose of describing the innovative aspects of this disclosure, the following description relates to certain implementations. However, it will be readily recognized by those skilled in the art that the teachings herein can be applied in a variety of different ways. Some examples in this disclosure are based on wireless and wired local area network (LAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 power line communication (PLC) standard. The described implementations can be implemented in any device, system, or network capable of transmitting and receiving radio frequency signals according to any wireless communication standard including any of the following: IEEE 802.11 standard, Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband-CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolved High-Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or other known signals used for communication in wireless, cellular, or Internet of Things (IoT) networks (such as systems utilizing 3G, 4G, 5G, or other implementations thereof).

[0044] In New Radio Unlicensed (NR-U), Physical Uplink Shared Channel (PUSCH) granting or multiple PUSCH granting can be used for control overhead savings. Multiple PUSCH granting, which can be included in the Downlink Control Information (DCI), can schedule multiple consecutive PUSCH transmissions. Multiple consecutive PUSCH transmissions can be associated with Common Frequency Domain Resource Allocation (FDRA), Modulation and Coding Scheme (MCS), rank, and various other transmission parameters. Multiple consecutive PUSCH transmissions can be associated with start and end positions, which can be provided by Time Domain Resource Allocation (TDRA) including multiple start and length indicator values ​​(SLIV). Multiple PUSCH granting can indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier (ID), and subsequent transmissions can use incremental HARQ process IDs. Each PUSCH transmission can be associated with a separate New Data Indicator (NDI) and a separate Compressed Redundancy Version Indicator (RVID). Various design options for multiple PUSCH granting can be trade-offs between scheduling flexibility and the length of the DCI providing multiple PUSCH granting.

[0045] To control overhead savings, multi-PUSCH grants can be redesigned for use as multi-physical downlink shared channel (PDSCH) grants. For millimeter-wave (mmWave) channels, time slots can be associated with shorter durations (compared to other channel types), especially when using increased subcarrier spacing (SCS). Multi-PDSCH grants enable scheduling downlink bursts with increased durations, thereby reducing control overhead.

[0046] Several aspects of multiple PUSCH authorization can be used for multiple PDSCH authorization. For example, common FDRA, MCS, rank, precoding, and various other transport parameters can also be used for multiple PDSCH authorization. Multiple PDSCH authorization can indicate the first HARQ process ID, and subsequent transports can use incremental HARQ process IDs. Each PDSCH transport can be associated with a separate NDI and a separate compressed RVID.

[0047] Several aspects of multi-PDSCH permissioning are not defined in multi-PUSCH permissioning. For example, regarding SLIV, one or more gaps can be configured between consecutive PDSCH transmissions, which can allow opportunities for UE feedback by the served UE or other UEs. One or more gaps can also allow opportunities for downlink monitoring by the served UE, or opportunities for downlink control transmissions to the served UE or other UEs. Another aspect of multi-PDSCH permissioning not defined in multi-PUSCH permissioning is the processing of the PDSCH to HARQ feedback timing value (K1), the Physical Uplink Control Channel (PUCCH) Resource Indicator (PRI) indicating PUCCH resources, and the Downlink Assignment Indicator (DAI). No processing for the K1 value, PRI, and DAI is defined for PUSCH permissioning because the K1 value, PRI, and DAI are not available for PUSCH permissioning.

[0048] For multiple PDSCH grants, both semi-static and dynamic codebooks can be considered. Semi-static codebook reporting can be based on a set of K1 values, and this method can be applied to multiple PDSCH grants if the set of K1 values ​​used for semi-static codebook construction covers the possible PDSCH-to-PUCCH offsets. By configuring the set of K1 values, the multiple PDSCH grant length, and the K1 values ​​used for multiple PDSCH grants, a semi-static codebook can be used without redesign. However, for dynamic codebook reporting, a redesign is necessary because a downlink grant DCI can trigger an ACK-NACK feedback within a single PDSCH grant, but multiple PDSCH grants can grant multiple PDSCHs, with each PDSCH corresponding to an ACK-NACK.

[0049] A base station can send multiple DCIs to a UE, where each DCI may include multiple PDSCH grants. In some cases, the base station may attempt to send two DCIs corresponding to two separate multiple PDSCH grants to the UE, but the UE may not receive either the first or second DCI. Therefore, the UE may not receive either the first or second multiple PDSCH grant. The UE can report an ACK-NACK for the PDSCH corresponding to the received multiple PDSCH grant via PUCCH, but the UE may not be able to determine when the multiple PDSCH grant that should have been received at the UE was actually lost at the UE. When the base station receives an ACK-NACK from the UE, it may not be able to determine whether the ACK-NACK is associated with the first or the second multiple PDSCH grant. In other words, the base station and the UE may disagree on the number of ACK-NACK bits included in the PUCCH used for ACK-NACK reporting and the position of the ACK-NACK for each PDSCH in the dynamic codebook.

[0050] In various aspects of the technologies and apparatus described herein, each of the multiple PDSCH grants (DCIs) can be associated with a counter (DAI). The counter (DAI) enables the UE to track whether a PDSCH has not yet been received at the UE. When the UE determines that a PDSCH has not been received based on the counter (DAI) associated with a subsequently received multiple PDSCH grant, the UE can report ACK-NACKs for the multiple multiple PDSCH grants accordingly. For example, the UE can report NACKs for lost multiple PDSCH grants. The UE can bundle ACK-NACKs for multiple PDSCHs associated with a particular multiple PDSCH grant and report the bundled ACK-NACKs during the PUCCH. The counter (DAI) can be used when configuring a single component carrier, and both the counter (DAI) and the total (DAI) can be used when configuring carrier aggregation.

[0051] In various aspects of the technologies and apparatus described herein, the UE can bind ACK-NACK based on the association of the PDSCH with a single codeword or multiple codewords. The UE can bind ACK-NACK based on whether spatial binding is configured or not for the bound PDSCH. The UE can bind ACK-NACK based on whether block group (CBG) ACK-NACK is configured or not.

[0052] In various aspects of the technologies and apparatus described herein, the UE can receive a DCI including multiple PDSCH grants, and the UE can associate one or more virtual DCIs with multiple PDSCH grants. Virtual DCIs can be associated with a counter DAI. The counter DAI enables the UE to track whether a PDSCH has not yet been received at the UE. When the UE determines that a PDSCH has not been received based on the counter DAI associated with a later-received multiple PDSCH grant, the UE can report an ACK-NACK for the PDSCH associated with the multiple PDSCH grant. The counter DAI can be used when a single component carrier is configured, and both the counter DAI and the total DAI can be used when carrier aggregation is configured.

[0053] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. The UE can employ a counter DAI (and in some cases, a total DAI mechanism) to track multiple PDSCH grants received at the UE and multiple PDSCH grants not received at the UE. Based on the counter DAI and total DAI mechanisms, the UE can detect lost PDSCHs and report ACK-NACKs for the lost PDSCHs. The counter DAI and total DAI mechanisms can be used in conjunction with ACK-NACK bundling. For example, the UE can use ACK-NACK bundling to report bundled ACK-NACKs for multiple PDSCHs associated with multiple PDSCH grants, which can reduce signaling overhead between the UE and the base station. ACK-NACK bundling can result in reduced ACK-NACK overhead. In some cases, the counter DAI and total DAI mechanisms can be used in conjunction with a virtual DCI mechanism. For example, a UE can associate a virtual DCI with one or more PDSCHs associated with multiple PDSCH permission, and the virtual DCI can indicate the counter DAI and the total DAI. This allows the UE to detect lost PDSCHs and report ACK-NACK responses for the lost PDSCHs. Furthermore, the counter DAI and total DAI mechanism, along with ACK-NACK bundling, may facilitate multiple PDSCH permission, which, compared to single PDSCH permission, can be associated with lower control overhead and involves less PDCCH monitoring.

[0054] Figure 1This is a schematic diagram illustrating an example of a wireless network 100. Wireless network 100 may be or may include elements of a 5G (e.g., NR) network or a 4G (e.g., LTE) network, as well as other examples. Wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. Base station 110 is the entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, or a Transmit / Receive Point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​base station 110 or the base station subsystem serving that coverage area, depending on the context in which the term is used.

[0055] Base station 110 can provide communication coverage for macro cells, pico cells, femtocells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed User Group (CSG)). Base station 110 for macro cells can be referred to as a macro base station. Base station 110 for pico cells can be referred to as a pico base station. Base station 110 for femtocells can be referred to as a femtocell or a home base station. Figure 1 In the example shown, BS 110a can be a macro base station for macro cell 102a, BS 110b can be a pico base station for pico cell 102b, and BS 110c can be a femto base station for femto cell 102c. A base station can support one or more (e.g., three) cells.

[0056] In some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, any suitable transport network can be used to interconnect the base stations 110 with each other or with one or more other base stations 110 or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks).

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

[0058] Wireless network 100 can be a heterogeneous network comprising different types of base stations 110 (such as macro base stations, pico base stations, femto base stations, or relay base stations). These different types of base stations 110 may have different transmit power levels, different coverage areas, or different effects on interference in wireless network 100. For example, macro base stations may have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0059] Network controller 130 can be coupled to or communicate with a group of base stations 110, and can provide coordination and control for these base stations 110. Network controller 130 can communicate with base stations 110 via backhaul communication links. Base stations 110 can communicate with each other directly or indirectly via wireless or wired backhaul communication links.

[0060] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a user unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio unit), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

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

[0062] Typically, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology or air interface. A frequency can be referred to as a carrier or channel. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0063] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication 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), vehicle-to-infrastructure (V2I), or vehicle-to-pedestrian (V2P) protocols), or a mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described herein as being performed by base station 110.

[0064] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “below 6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although it differs from the extremely high frequency (EHF) band (30GHz–300GHz), it is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, while the EHF band is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0065] The frequencies between FR1 and FR2 are often referred to as intermediate frequency (IF) frequencies. Recent 5G NR studies have identified the operating bands for these IF frequencies as the frequency range name FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit characteristics of either FR1 or FR2, and thus can effectively extend the characteristics of FR1 or FR2 to IF frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4–1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0066] In light of these examples, unless otherwise specifically stated, it should be understood that, if used herein, the term "below 6 GHz" can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that, if used herein, the term "millimeter wave" can broadly refer to frequencies that may include intermediate frequency bands, within FR2, FR4, FR4-a, FR4-1, or FR5, or within the EHF band. It is anticipated that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0067] Figure 2 This is a schematic diagram illustrating example 200 of communication between base station 110 and UE 120 in wireless network 100. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0068] At base station 110, transmit processor 220 can receive data from data source 212 intended for UE 120 (or a set of UEs 120). Transmit processor 220 can use one or more Channel Quality Indicators (CQIs) received from UE 120 to select one or more MCSs for that UE 120. Base station 110 can use the selected MCS for UE 120 to process (e.g., encode and modulate) the data for UE 120 and provide data symbols for UE 120. Transmit processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, permission, or upper-layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 can 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 signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, overhead symbols, or reference symbols, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems), shown as modems 232a to 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use its respective modulator component to process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use its respective modulator component to process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0069] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 or other base stations 110, and can provide an array of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use its respective demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, can perform MIMO detection on the received symbols (if applicable), and can provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control and system information to the controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, and other examples. In some examples, one or more components of the UE 120 may be included in a housing.

[0070] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0071] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, and other examples. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, or coupled to one or more transmitting or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

[0072] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, or CQI). Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and a memory 282 to perform aspects of the processes described herein.

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

[0074] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components of, for example, UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0075] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface can also acquire or receive information or signal input, and the first interface can also output, transmit, or provide information.

[0076] In some aspects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to, for example, other systems or components of base station 110). For example, the processing system of base station 110 may be a system that includes various other components or sub-components of base station 110.

[0077] The processing system of base station 110 can interface with one or more other components of base station 110, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of base station 110 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing base station 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing base station 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface can also acquire or receive information or signal input, and the first interface can also output, transmit, or provide information.

[0078] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 or Figure 2 Any other component may perform one or more techniques associated with ACK-NACK reporting for downlink shared channel permission, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, or... Figure 2 Any other component (or combination of components) can perform or direct, for example Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 Process 1500 Figure 16 Process 1600 Figure 17 The operation of process 1700, or other processes as described herein. Memory 242 and memory 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 or UE 120 (e.g., directly, or after compilation, translation, or interpretation), may cause one or more processors, UE 120, or base station 110 to perform or direct, for example... Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 Process 1500 Figure 16 Process 1600 Figure 17The operation of process 1700, or other processes as described herein. In some examples, execution instructions may include run instructions, transform instructions, compile instructions, or interpret instructions.

[0079] In some aspects, UE 120 may include: a unit for receiving from a base station a DCI configured to schedule multiple PDSCHs, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with PUCCH resources; a unit for using PUCCH resources to send HARQ feedback to the base station for multiple PDSCHs, and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, one or more antennas 252, DEMOD 254, MIMO detector 256, or receive processor 258.

[0080] In some aspects, UE 120 may include: a unit for receiving DCI from a base station, the DCI including PDSCH authorization for multiple PDSCHs; a unit for transmitting bundled ACK-NACKs for multiple PDSCHs to the base station via PUCCH; and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, one or more antennas 252, DEMOD 254, MIMO detector 256, or receive processor 258.

[0081] In some aspects, UE 120 may include: a unit for receiving a DCI from a base station, the DCI including PDSCH authorization for multiple PDSCHs; a unit for identifying a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs; a unit for sending ACK-NACK for the multiple PDSCHs to the base station via PUCCH based on the virtual DCI; and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, one or more antennas 252, DEMOD 254, MIMO detector 256, or receive processor 258.

[0082] In some aspects, base station 110 may include: a unit for transmitting a DCI configured to schedule multiple PDSCHs to the UE, wherein the DCI indicates: a PDSCH-to-HARQ feedback timing value, and a PRI associated with PUCCH resources; a unit for using PUCCH resources to receive HARQ feedback from the UE for multiple PDSCHs, and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 The described base station 110 includes one or more components such as one or more antennas 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232 or antenna 234, and other examples.

[0083] In some aspects, base station 110 may include: a unit for transmitting DCI to the UE, the DCI including PDSCH permission for multiple PDSCHs; a unit for receiving bundled ACK-NACK for multiple PDSCHs from the UE via PUCCH; and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 The described base station 110 includes one or more components such as one or more antennas 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232 or antenna 234, and other examples.

[0084] In some aspects, base station 110 may include: a unit for transmitting a DCI to a UE, the DCI including PDSCH authorization for multiple PDSCHs; a unit for receiving ACK-NACK from the UE via PUCCH for multiple PDSCHs based on a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs; and other examples, or combinations thereof. In some aspects, such a unit may include a combination of... Figure 2 The described base station 110 includes one or more components such as one or more antennas 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TXMIMO processor 230, MOD 232 or antenna 234, and other examples.

[0085] Although Figure 2The boxes in the diagram are shown as different components, but the functions described for each box can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for the transmit processor 264, receive processor 258, TX MIMO processor 266, or another processor can be performed by or under the control of the controller / processor 280.

[0086] Figure 3 This is a schematic diagram illustrating example 300 associated with PDSCH permission. Figure 3 The examples described can also be used in multi-PDSCH permission. Base stations (e.g., Figure 1 and 2 The base station 110 described in the text can send signals to the UE (e.g., in...) Figure 1 and 2 The UE 120 described herein transmits a first DCI including a first multiple PDSCH grant, which may correspond to time slots 1, 2, and 3. The base station may transmit a second DCI to the UE including a second multiple PDSCH grant, which may correspond to time slots 5 and 6. A PUCCH may be scheduled after the PDSCH corresponding to the first and second multiple PDSCH grants, where the PUCCH may be used for ACK-NACK reporting.

[0087] A dynamic codebook can be designed so that the base station and the UE have consistent knowledge about the number of ACK-NACK bits included in the PUCCH used for ACK-NACK reporting and the position of the ACK-NACK for each PDSCH in the dynamic codebook. The number of ACK-NACK bits included in the PUCCH can refer to the ACK-NACK bits corresponding to the first multiple PDSCH permission and the ACK-NACK bits corresponding to the first multiple PDSCH permission.

[0088] Furthermore, the dynamic codebook can be designed to provide robustness in the event of a lost multi-PDSCH grant. For example, the dynamic codebook can provide robustness when a second multi-PDSCH grant is received at the UE but the first multi-PDSCH grant is not received at the UE. In this case, the UE should be configured to include three negative acknowledgment (NACK) bits at the beginning of the five-bit codebook, where these three NACK bits correspond to the first multi-PDSCH grant that was not received, and two ACK-NACK bits correspond to the second multi-PDSCH grant that was received. In other words, when the UE only receives the second multi-PDSCH grant, the UE should be configured to determine that the base station granted three PDSCHs before the two PDSCHs associated with the second multi-PDSCH grant, but these three PDSCHs were not received at the UE.

[0089] Figure 4 This is a schematic diagram illustrating an example 400 associated with an ACK-NACK report that has ACK-NACK bundled with PDSCH permission. Figure 4 The examples described can also be used in multi-PDSCH permission. Base stations (e.g., Figure 1 and 2 The base station 110 described in the text can send signals to the UE (e.g., in...) Figure 1 and 2 The UE 120 described herein transmits a DCI that includes multiple PDSCH permission. For example, multiple PDSCH permission can schedule multiple consecutive PDSCHs. The DCI may include a K1 value, where K1 may indicate a feedback timing value between the last PDSCH in the multiple consecutive PDSCHs and a PUCCH, which can be used for ACK-NACK reporting. The DCI may include a PRI, which indicates a PUCCH (or PUCCH resource) that can be used for ACK-NACK reporting. The UE may use a PUCCH to send HARQ feedback, as indicated by the K1 value and PRI included in the DCI. HARQ feedback may include ACK-NACK for multiple PDSCH permission.

[0090] In some respects, sending a DCI with a K1 value and PRI may result in reduced control overhead, but may lead to increased feedback latency. In some cases, sending a DCI with a K1 value and PRI can be similar to a multi-PUSCH grant design, where a single K2 value can be provided, indicating the timing offset from multi-PUSCH grant to the first PUSCH transmission.

[0091] One issue with multiple PDSCH grants is that the feedback size associated with the ACK-NACK report used for multiple PDSCH grants can be variable due to the variable number of PDSCHs associated with them. This variability in the feedback size associated with the ACK-NACK report can pose challenges for both the UE and the base station when implementing multiple PDSCH grants. In some aspects, to address this issue, the feedback size associated with the ACK-NACK report can be fixed, such that the feedback size corresponds to the feedback size associated with the ACK-NACK report used for a single PDSCH grant. The feedback size associated with the ACK-NACK report can be fixed based on ACK-NACK bundling. For example, the ACK-NACK for a PDSCH indicated in a multiple PDSCH grant can be bundled to the same size as a single PDSCH grant to be included in the dynamic codebook. Furthermore, multiple PDSCH grants can follow a counter / total DAI mechanism, which can be used by the UE to detect lost PDSCH grants. When a lost PDSCH permission is detected based on the counter / total DAI mechanism, the UE can assign a fixed number of NACKs to the lost PDSCH permission. In other words, the UE can patch vulnerabilities in the codebook (e.g., a semi-static codebook or a dynamic codebook) by assigning a fixed number of NACKs to the lost PDSCH permission.

[0092] Figure 5 This is a schematic diagram illustrating an example 500 associated with an ACK-NACK report that has ACK-NACK binding for PDSCH permission. Figure 5 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described in the text can be based on data from a base station (e.g., Figure 1 and 2 The base station 110 described in the text receives multiple PDSCHs to send ACK-NACK reports with ACK-NACK bindings to the base station.

[0093] In some aspects, the UE can perform an ACK-NACK report when the base station is configured with a single component carrier and a counter DAI. In other aspects, the UE can perform an ACK-NACK report when it is configured for carrier aggregation and both the counter DAI and the total DAI are configured by the base station.

[0094] As shown by reference numeral 502 in the attached figure, for the single-component carrier case, the base station can send a first DCI and a second DCI to the UE. The first DCI may include a first multiple PDSCH grant, consisting of three PDSCHs whose grant counter DAI equals zero. These three PDSCHs may correspond to time slots 1, 2, and 3. The second DCI may include a second multiple PDSCH grant, consisting of two PDSCHs whose grant counter DAI equals one. These two PDSCHs may correspond to time slots 5 and 6. In some aspects, when the UE receives both the first and second multiple PDSCH grants, the UE may report two ACK-NACK sets in the PUCCH. For example, the UE may send two ACK-NACK sets to the base station in the PUCCH, which may correspond to time slot 8.

[0095] In some aspects, when a UE receives a second multiple PDSCH grant but not a first multiple PDSCH grant, the UE can determine, based on a counter DAI equal to one associated with the second multiple PDSCH grant, that an earlier multiple PDSCH grant (such as the first multiple PDSCH grant) was not received or was lost at the UE. In this case, the UE can populate the NACK set before the ACK-NACK report for the second multiple PDSCH grant. In other words, the UE can associate a NACK with a first multiple PDSCH grant that was not received at the UE. The UE may not know the number of PDSCHs associated with the first multiple PDSCH grant. However, since the UE can bundle NACKs for the first multiple PDSCH grant that was not received at the UE, the number of PDSCHs associated with the first multiple PDSCH grant may be irrelevant to the UE.

[0096] In some cases, the UE might receive a first multiple PDSCH grant but not a second multiple PDSCH grant. The UE can report an ACK-NACK set in the PUCCH of slot 8, where one ACK-NACK set might correspond to the first multiple PDSCH grant but not the second. The counter DAI associated with the first multiple PDSCH grant might not enable the UE to detect when the second multiple PDSCH grant is lost. In this scenario, a codebook size mismatch may occur between the UE and the base station.

[0097] As shown by reference numeral 504, in the case of carrier aggregation, the base station can transmit a first DCI and a second DCI to the UE on a first component carrier, and a third DCI and a fourth DCI to the UE on a second component carrier. The first DCI can be associated with a first multi-PDSCH grant, which grants three PDSCHs corresponding to time slots 1, 2, and 3. The second DCI can be associated with a second multi-PDSCH grant, which grants two PDSCHs corresponding to time slots 5 and 6. The third DCI can be associated with a third multi-PDSCH grant, which grants two PDSCHs corresponding to time slots 2 and 3. The fourth DCI can be associated with a fourth multi-PDSCH grant, which grants a single PDSCH corresponding to time slot 5. The first, second, third, and fourth DCIs can each be associated with both a counter DAI and a total DAI, which allows the UE to detect lost multi-PDSCH grants, similar to the single-component carrier case. In addition, the UE can perform ACK-NACK reporting for both the first component carrier and the second component carrier in the PUCCH associated with the first component carrier.

[0098] Figure 6 This is a schematic diagram illustrating an example 600 associated with an ACK-NACK report that has ACK-NACK binding for PDSCH permission. Figure 6 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described in the text can be based on data from a base station (e.g., Figure 1 and 2 The base station 110 described in the text receives multiple PDSCHs to send ACK-NACK reports with ACK-NACK bindings to the base station.

[0099] As shown by reference numeral 602, the UE can report a single ACK-NACK bit per DCI. A single ACK-NACK bit can be associated with a single codeword, and a code block group may not be configured for the UE. In this case, the single ACK-NACK bit can correspond to a time slot associated with the PDSCH in the time domain. As shown by reference numeral 602, a single ACK-NACK bit can be a bundled ACK-NACK associated with time slots 0 through 7 in the time domain.

[0100] As shown by reference numeral 604, the UE can report a single ACK-NACK bit per DCI. A single ACK-NACK bit can be associated with multiple codewords having spatial bundling, and CBG configuration is not required for the UE. Spatial bundling can be used when a single ACK-NACK bit corresponds to time slots spanning the frequency domain. As shown by reference numeral 604, a single ACK-NACK bit can be a bundled ACK-NACK associated with time slots 0 to 7 of the first component carrier and time slots 0 to 7 of the second component carrier.

[0101] In some respects, an ACK-NACK bundle for a multi-PDSCH permission may be NACK when at least one transport block (TB) of at least one PDSCH associated with a multi-PDSCH permission is NACK.

[0102] Figure 7 This is a schematic diagram illustrating an example 700 associated with an ACK-NACK report that has ACK-NACK binding for PDSCH permission. Figure 7 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described in the text can be based on data from a base station (e.g., Figure 1 and 2 The base station 110 described in the text receives multiple PDSCHs to send ACK-NACK reports with ACK-NACK bindings to the base station.

[0103] In some cases, multiple codewords can be configured for the UE, and CBG ACK-NACK can be omitted. In this case, the UE can report two ACK-NACK bits for each PDSCH.

[0104] As shown by reference numeral 702, the UE can report two ACK-NACK bits using ACK-NACK bundling across the PDSCH in the time domain. In this case, the ACK-NACK bundling performed by the UE may not be spatial bundling. In other words, ACK-NACK bundling may not be performed in the frequency domain. In some aspects, when the UE uses a single codeword (not exceeding rank four), one of the two ACK-NACK bits may correspond to NACK. As shown by reference numeral 702, the first ACK-NACK bit may be a bundled ACK-NACK (e.g., NACK) associated with slots 0 to 7 of the first component carrier, and the second ACK-NACK bit may be a bundled ACK-NACK associated with slots 0 to 7 of the second component carrier.

[0105] As shown by reference numeral 704, the UE can report two ACK-NACK bits using ACK-NACK bundling across the PDSCH in the time domain, instead of spatial bundling. In this case, the two ACK-NACK bits can be associated with multiple codewords. As shown by reference numeral 704, the first ACK-NACK bit can be a bundled ACK-NACK associated with slots 0 to 7 of the first component carrier, and the second ACK-NACK bit can be a bundled ACK-NACK associated with slots 0 to 7 of the second component carrier.

[0106] As shown by reference numeral 706, the UE can use ACK-NACK bundling to report two ACK-NACK bits. In this case, the two ACK-NACK bits can be associated with multiple codewords. Furthermore, the ACK-NACK bundling performed by the UE can use spatial bundling across the PDSCH in both the frequency and time domains. For example, ACK-NACK bundling can be performed spatially, and then, for the ACK-NACK bundling, multiple PDSCHs can be evenly split in the time domain. Multiple PDSCHs can be evenly split based on the first and second halves, based on even and odd PDSCHs, or other mechanisms. As shown by reference numeral 706, the first ACK-NACK bit can be a spatially bundled ACK-NACK associated with time slots 0 to 3 of the first component carrier and time slots 0 to 3 of the second component carrier, and the second ACK-NACK bit can be a spatially bundled ACK-NACK associated with time slots 4 to 7 of the first component carrier and time slots 4 to 7 of the second component carrier.

[0107] Figure 8 This is a schematic diagram illustrating an example 800 associated with an ACK-NACK report that has ACK-NACK binding for PDSCH permission. Figure 8 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described in the text can be based on data from a base station (e.g., Figure 1 and 2 The base station 110 described in the text receives multiple PDSCHs to send ACK-NACK reports with ACK-NACK bindings to the base station.

[0108] In some aspects, CBG ACK-NACK can be configured with a single codeword for the UE. In some aspects, for CBG ACK-NACK and a single codeword, ACK-NACK bundling can fall back to TB-level feedback for multi-PDSCH permission, where TBs can be allocated to available CBG ACK-NACK bits. In some aspects, for CBG ACK-NACK and a single codeword, ACK-NACK bundling can involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling CBG-level ACK-NACKs. For example, all CBG ACK-NACKs from all PDSCHs can be aggregated. In some aspects, for CBG ACK-NACK and a single codeword, ACK-NACK bundling can involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling ACK-NACKs based on the actual number of CBGs per TB.

[0109] As shown by reference numeral 802, ACK-NACK bundling can fall back to TB-level feedback for multiple PDSCH permission, where TBs can be allocated to available CBG ACK-NACK bits. In this particular example, four CBG ACK-NACK bits can be configured for the UE. In some aspects, when the number of PDSCHs is less than the number of CBG ACK-NACK bits configured for the UE, NACKs can be used to fill some bits in the CBG ACK-NACK bits. In some aspects, when the number of PDSCHs is greater than the number of CBG ACK-NACK bits configured for the UE, ACK-NACK bundling can be applied, where each CBG ACK-NACK bit has approximately the same number of TBs. As shown by reference numeral 802, the four CBG ACK-NACK bits may include a first CBG ACK-NACK bit corresponding to slots 0 and 1, a second CBG ACK-NACK bit corresponding to slots 2 and 3, a third CBG ACK-NACK bit corresponding to slots 4 and 5, and a fourth CBG ACK-NACK bit corresponding to slots 6 and 7.

[0110] As shown by reference numeral 804, ACK-NACK bundling can involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling CBG-level ACK-NACKs. In this particular example, three PDSCHs can be granted through multi-PDSCH granting, and four CBG ACK-NACKs can be configured for the UE. As shown by reference numeral 804, a total of twelve CBG ACK-NACKs spanning three PDSCHs can be bundled together in groups of three to form four bundled CBG ACK-NACKs.

[0111] As shown by reference numeral 806, ACK-NACK bundling can involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling ACK-NACKs based on the actual number of CBGs per TB. In some cases, some PDSCHs may actually have fewer CBGs than configured, which may occur when the payload size is reduced, so the actual number of CBGs is less than the configured number of CBGs. In this particular example, three PDSCHs can be granted through multi-PDSCH granting, and four CBG ACK-NACKs can be configured for the UE. In this example, the first PDSCH may have one CBG, the second PDSCH may have four CBGs, and the third PDSCH may have two CBGs. As shown by reference numeral 806, a total of seven CBGs can be split into four CBG ACK-NACKs, such that two CBGs can be associated with the first CBG ACK-NACK, two CBGs can be associated with the second CBG ACK-NACK, two CBGs can be associated with the third CBG ACK-NACK, and one CBG can be associated with the fourth CBG ACK-NACK.

[0112] Figure 9 This is a schematic diagram illustrating an example 900 associated with an ACK-NACK report that has ACK-NACK binding for PDSCH permission. Figure 9 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described in the text can be based on data from a base station (e.g., Figure 1 and 2 The base station 110 described in the text receives multiple PDSCHs to send ACK-NACK reports with ACK-NACK bindings to the base station.

[0113] In some aspects, CBG ACK-NACK can be configured with multiple spatial codewords for the UE, such as two codewords. For a single PDSCH case, the same number of CBG ACK-NACK bits can be configured per codeword, regardless of whether the codeword is used.

[0114] As shown by reference numeral 902 in the attached figure, ACK-NACK bundling may not involve spatial bundling. For each codeword, ACK-NACK bundling may fall back to TB-level feedback for multi-PDSCH permission, where TBs can be allocated to available CBG ACK-NACK bits. ACK-NACK bundling may involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling CBG-level ACK-NACKs, or ACK-NACK bundling may involve aggregating multiple CBG ACK-NACKs from multiple PDSCHs and bundling ACK-NACKs based on the actual number of CBGs per TB. In this example, when a codeword is not used for a multi-PDSCH transmission, the multiple CBG ACK-NACKs for that codeword (e.g., all CBG ACK-NACKs) may be NACKs. As indicated by reference numeral 902 in the accompanying drawings, the time slot pairs associated with the first component carrier (e.g., time slots 0 and 1, time slots 2 and 3, etc.) can be ACK-NACK bundled in the time domain, and the time slot pairs associated with the second component carrier (e.g., time slots 0 and 1, time slots 2 and 3, etc.) can be ACK-NACK bundled in the time domain.

[0115] As shown by reference numeral 904, ACK-NACK bundling may involve aggregating PDSCHs and then aggregating codewords. In some aspects, ACK-NACK bundling may involve aggregating TBs spanning codewords into a common pool and bundling the TBs to available CBG ACK-NACKs (or feedback). In some aspects, ACK-NACK bundling may involve aggregating CBGs spanning codewords into a common pool and bundling the CBGs to available CBG ACK-NACKs (or feedback). In some aspects, ACK-NACK bundling may involve aggregating an actual number of CBGs spanning codewords into a common pool and bundling that actual number of CBGs to available CBG ACK-NACKs (or feedback). As shown by reference numeral 904, ACK-NACKs for slots 0 to 7 of the first component carrier may be bundled in the time domain and then spatially bundled with ACK-NACKs for slots 0 to 7 of the second component carrier bundled in the time domain.

[0116] As shown by reference numeral 906, ACK-NACK bundling may involve aggregating codewords and then aggregating PDSCHs. In some aspects, ACK-NACK bundling may involve aggregating TBs spanning codewords into a common pool and bundling the TBs to available CBG ACK-NACKs (or feedback). In some aspects, ACK-NACK bundling may involve aggregating CBGs spanning codewords into a common pool and bundling the CBGs to available CBG ACK-NACKs (or feedback). In some aspects, ACK-NACK bundling may involve aggregating the actual number of CBGs spanning codewords into a common pool and bundling that actual number of CBGs to available CBG ACK-NACKs (or feedback). As shown by reference numeral 906, ACK-NACKs spanning slot 0 of the first and second component carriers may be spatially bundled and then bundled with ACK-NACKs spatially bundled for slot 1 of the first and second component carriers, and so on.

[0117] In some aspects, multiple PDSCH grants can be associated with virtual DCI, which may result in a reduction in the amount of lost information compared to ACK-NACK binding. For example, each PDSCH in a multiple PDSCH grant, except for the first PDSCH, can be associated with a virtual DCI. The virtual DCI may not actually be transmitted from the base station to the UE, but can be identified at the UE based on the multiple PDSCH grants. The counter DAI and total DAI in a multiple PDSCH grant can be associated with the first PDSCH granted by the multiple PDSCH grant, where the counter DAI and total DAI in the virtual DCI can take into account the associated PDSCH.

[0118] As an example, multiple PDSCH grants can be sent from the base station to the UE in time slot 0, where multiple PDSCH grants can schedule PDSCHs in time slots 0, 1, 2, and 3. The UE can identify virtual DCIs in time slots 1, 2, and 3, and can virtually schedule PDSCHs in time slots 1, 2, and 3 respectively. The UE can identify virtual DCIs based on the multiple PDSCH grants received from the base station.

[0119] Figure 10 This is a schematic diagram illustrating Example 1000 associated with ACK-NACK reporting permitted by PDSCH for virtual DCI. Figure 10 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described and illustrated in the text can be accessed from a base station (e.g., in...) Figure 1 and 2The base station 110 described in the figure receives multiple PDSCH grants. The UE can associate one or more virtual DCIs based on the multiple PDSCH grants. The UE can send ACK-NACK reports to the base station based on the virtual DCIs associated with the multiple PDSCH grants.

[0120] like Figure 10 As shown, in the case of a single-component carrier, the base station can send a first DCI and a second DCI to the UE. The first DCI may include a first multi-PDSCH grant, which grants three PDSCHs with a counter DAI equal to zero. These three PDSCHs may correspond to time slots 1, 2, and 3. When the UE detects the first DCI, the UE can associate two virtual DCIs of the last two PDSCHs of the three granted PDSCHs. The two virtual DCIs identified by the UE may not actually have been sent by the base station. The first virtual DCI associated with the second PDSCH of the three granted PDSCHs may include a counter DAI equal to one, which may be an increment from the actual DCI counter DAI associated with the first DCI. The second virtual DCI associated with the third PDSCH of the three granted PDSCHs may include a counter DAI equal to two, which may be an increment from the first virtual DCI counter DAI (e.g., the counter DAI associated with the first virtual DCI). The first DCI may not include the total DAI.

[0121] like Figure 10 As shown, the second DCI may include a second multiple PDSCH permission that allows two PDSCHs. These three PDSCHs may correspond to time slots 5 and 6. The second DCI may include a counter DAI equal to three. The counter DAI associated with the second DCI may be incremented from the second virtual DCI counter DAI (e.g., the counter DAI associated with the second virtual DCI). In some aspects, when the UE detects the second DCI, the UE may associate a third virtual DCI with the last PDSCH of the two permitted PDSCHs. The third virtual DCI identified by the UE may not actually be transmitted by the base station. The third virtual DCI may include a counter DAI equal to zero, which may be an increment from the actual DCI counter DAI associated with the second DCI.

[0122] In some aspects, when a UE receives a second multiple PDSCH grant but not a first multiple PDSCH grant, the UE can determine that an earlier multiple PDSCH grant, such as the first multiple PDSCH grant, was not received at the UE based on a counter DAI of three associated with the second multiple PDSCH grant. Based on the counter DAI of three associated with the second multiple PDSCH grant, the UE can determine that three PDSCH grants (including actual and virtual grants) have been lost at the UE. In this case, the UE can fill the NACK set for the lost PDSCH grants (e.g., three NACK sets for the three lost PDSCH grants). The UE can send NACKs for the lost PDSCH grants and ACK-NACKs for the second multiple PDSCH grants in the PUCCH. The UE may not be aware of the configuration associated with the lost PDSCH grants, such as whether three lost PDSCH grants are associated with a multi-PDSCH grant that grants three PDSCHs, or whether three lost PDSCH grants are associated with three separate PDSCH grants that each grant one PDSCH, or vice versa. However, the configuration associated with the three lost PDSCH grants may not affect the codebook generated by the UE.

[0123] In some cases, the UE may receive the first multiple PDSCH approval but not the second multiple PDSCH approval. The UE may report three ACK-NACK sets in the PUCCH, where each set corresponds to the first multiple PDSCH approval but not the second. In this scenario, a codebook size mismatch may occur between the UE and the base station.

[0124] Figure 11 This is a schematic diagram illustrating Example 1100 associated with an ACK-NACK report permitted by PDSCH for and related to virtual DCI. Figure 11 The examples described can also be used in multi-PDSCH permissioned applications. UE (e.g., Figure 1 and 2 The UE 120 described and illustrated in the text can be accessed from a base station (e.g., in...) Figure 1 and 2 The base station 110 described in the figure receives multiple PDSCH grants. The UE can associate one or more virtual DCIs based on the multiple PDSCH grants. The UE can send ACK-NACK reports to the base station based on the virtual DCIs associated with the multiple PDSCH grants.

[0125] like Figure 11As shown, in carrier aggregation, each component carrier can dynamically schedule a single PDSCH grant or multiple PDSCH grants. For example, the base station can send a first DCI 1102 to the UE on the first component carrier, a second DCI 1104 on the second component carrier, a third DCI 1106 on the second component carrier, a fourth DCI 1108 on the first component carrier, and a fifth DCI 1110 on the second component carrier. The first DCI 1102 can be associated with a first multiple PDSCH grant that grants three PDSCHs (e.g., slots 1, 2, and 3). The second DCI 1104 can be associated with a first single PDSCH grant that grants slot 1. The third DCI 1106 can be associated with a second multiple PDSCH grant that grants two PDSCHs (e.g., slots 3 and 4). The fourth DCI 1108 can be associated with a third multiple PDSCH grant that grants two PDSCHs (e.g., slots 5 and 6). The fifth DCI can be associated with the second single PDSCH permission in permission slot 6.

[0126] In some aspects, the UE can associate the first virtual DCI and the second virtual DCI with the first DCI 1102. The UE can associate the third virtual DCI with the third DCI 1106. The UE can associate the fourth virtual DCI with the fourth DCI 1108.

[0127] In some aspects, DCI and virtual DCI can be associated with both the counter DAI and the total DAI, which allows the UE to detect lost multi-PDSCH grants or lost single-PDSCH grants, similar to the single-component carrier case. Furthermore, the UE can perform ACK-NACK reporting for both the first and second component carriers in the PUCCH associated with the first component carrier.

[0128] In some aspects, the UE can use virtual DCI and actual DCI to determine the counter DAI and total DAI. For example, when virtual DCI and actual DCI start at the same symbol, the total DAI can be counted jointly, and the counter DAI can be similar to the order of two simultaneously transmitted actual DCIs. In other words, virtual DCI and actual DCI can be considered to originate from the same monitoring time.

[0129] In some respects, the virtual DCI can be based on the location of the detected actual DCI. During search space configuration, symbol-level offsets can be defined for the virtual DCI to be introduced for each additional PDSCH in a multi-PDSCH allowance. In one example, 14 symbol offsets can be introduced for each additional PDSCH. In another example, for example, when micro-slot-level scheduling is supported, 7 symbol offsets can be introduced for each additional PDSCH.

[0130] In some aspects, after receiving the actual DCI, a virtual DCI can be added for each time slot, starting from symbol 0 for each time slot. In other words, when the actual DCI is received at the UE, the UE can add or identify a virtual DCI for each time slot (e.g., until another actual DCI is received).

[0131] In some respects, the location associated with the virtual DCI may not be associated with the actual search space monitoring configuration. In other words, the UE may not perform search space monitoring at the location associated with the virtual DCI.

[0132] Figure 12 This is a schematic diagram illustrating, for example, an example procedure 1200 performed by a UE. Procedure 1200 is an example in which a UE (e.g., UE 120) performs operations associated with an ACK-NACK report for downlink shared channel permission.

[0133] like Figure 12 As shown, in some aspects, process 1200 may include: receiving from a base station a DCI configured to schedule multiple PDSCHs, wherein the DCI indicates: a PDSCH to HARQ feedback timing value, and a PRI associated with PUCCH resources (block 1210). For example, a UE (such as by using...) Figure 18 The receiving component 1802 described herein can receive a DCI configured to schedule multiple PDSCHs from the base station, wherein the DCI indicates: the PDSCH to HARQ feedback timing value, and the PRI associated with the PUCCH resource, as described herein.

[0134] like Figure 12 As further shown, in some aspects, process 1200 may include: using PUCCH resources to send HARQ feedback to the base station for multiple PDSCHs (box 1220). For example, the UE (such as by using...) Figure 18 The transmitting component 1804 described herein can use PUCCH resources to send HARQ feedback to the base station for multiple PDSCHs, as described herein.

[0135] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0136] In the first additional aspect, the PDSCH to HARQ feedback timing value corresponds to the time period between the last PDSCH and the PUCCH resource among multiple PDSCHs.

[0137] In the second additional aspect, either alone or in combination with the first aspect, HARQ feedback for multiple PDSCHs includes ACK or NACK associated with multiple PDSCHs.

[0138] Although Figure 12 An example box of process 1200 is shown, but in some aspects, process 1200 may include... Figure 12 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1200 may be executed in parallel.

[0139] Figure 13 This is a schematic diagram illustrating, for example, an example procedure 1300 performed by a UE. Procedure 1300 is an example in which a UE (e.g., UE 120) performs operations associated with an ACK-NACK report for downlink shared channel permission.

[0140] like Figure 13 As shown, in some aspects, process 1300 may include: receiving a DCI from a base station, the DCI including PDSCH permission for multiple PDSCHs (block 1310). For example, a UE (such as by using...) Figure 18 The receiving component 1802 depicted herein can receive a DCI from a base station, the DCI including PDSCH permissions for multiple PDSCHs as described herein.

[0141] like Figure 13 As further shown, in some aspects, process 1300 may include: sending bundled ACK-NACKs for multiple PDSCHs to a base station via PUCCH (box 1320). For example, a UE (such as by using...) Figure 18 The transmitting component 1804 described herein can transmit bundled ACK-NACKs for multiple PDSCHs to the base station via PUCCH, as described herein.

[0142] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0143] In the first additional aspect, PDSCH permission is a multi-PDSCH permission, and the size of the bundled ACK-NACK for the multiple PDSCHs associated with the multi-PDSCH permission corresponds to the size of the ACK-NACK for a single PDSCH permission.

[0144] In the second additional aspect, either alone or in combination with the first aspect, when a single component carrier is configured, the PDSCH is permitted to be associated with the counter DAI.

[0145] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, a PDSCH grant is a first PDSCH grant with a first counter DAI, wherein a second PDSCH grant that occurs later in time than the first PDSCH grant is associated with a second counter DAI incremented from the first counter DAI, wherein the first PDSCH grant and the second PDSCH grant are associated with the same PUCCH reporting instance.

[0146] In the fourth additional aspect, either alone or in combination with one or more of the first to third aspects, process 1300 includes: determining, based on a first counter DAI or a second counter DAI, whether a first PDSCH grant or a second PDSCH grant corresponds to a lost PDSCH grant, and wherein sending ACK-NACK includes: sending a NACK for the lost PDSCH grant.

[0147] In the fifth additional aspect, either alone or in combination with one or more of the first through fourth aspects, PDSCH is permitted to be associated with the counter DAI and the total DAI when carrier aggregation is enabled.

[0148] In the sixth additional aspect, sending ACK-NACK, either alone or in combination with one or more of the first to fifth aspects, includes sending ACK-NACK for multiple PDSCHs per DCI for a single codeword that does not have spatial binding and when no CBG ACK-NACK is configured for the UE.

[0149] In the seventh additional aspect, sending ACK-NACK, either alone or in combination with one or more of the first to sixth aspects, includes sending ACK-NACK for multiple PDSCHs per DCI when there is no CBG ACK-NACK configured for the UE and for multiple codewords with spatial binding.

[0150] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, the ACK-NACK for multiple PDSCHs is an ACK-NACK bit.

[0151] In the ninth additional aspect, sending ACK-NACK, either alone or in combination with one or more of the first to eighth aspects, includes sending ACK-NACK for multiple codewords and, when no CBG ACK-NACK is configured for the UE, sending ACK-NACK for multiple PDSCHs.

[0152] In the tenth additional aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, the ACK-NACK for each PDSCH included in the multiple PDSCHs is two ACK-NACK bits.

[0153] In the eleventh additional aspect, either alone or in combination with one or more aspects from the first to the tenth aspects, ACK-NACK is bundled across multiple PDSCHs.

[0154] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, ACK-NACK is spatially bundled and associated with a subgroup of PDSCHs in a plurality of PDSCHs.

[0155] In the thirteenth additional aspect, either alone or in combination with one or more of the first to twelfth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with a single codeword, sending a plurality of bundled ACK-NACK bits, wherein each of the plurality of bundled ACK-NACK bits corresponds to a bundled transport block level feedback.

[0156] In the fourteenth additional aspect, either alone or in combination with one or more of the first to thirteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with a single codeword, sending multiple bundled ACK-NACK bits, wherein CBG ACK-NACK for multiple PDSCHs is aggregated and split to form multiple bundled ACK-NACK bits.

[0157] In the fifteenth additional aspect, either alone or in combination with one or more of the first to fourteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with a single codeword, sending a plurality of bundled ACK-NACK bits, wherein each of the plurality of bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in the plurality of PDSCHs.

[0158] In the sixteenth additional aspect, either alone or in combination with one or more of the first to fifteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured to have multiple codewords, sending a plurality of bundled ACK-NACK bits for each codeword that does not have spatial bundling, wherein the plurality of bundled ACK-NACK bits correspond to bundled transport block-level feedback, the plurality of bundled ACK-NACK bits being based on the aggregation and splitting of CBG ACK-NACK for multiple PDSCHs to form a plurality of bundled ACK-NACK bits, or each of the plurality of bundled ACK-NACK bits being based on the actual number of CBGs for each transport block in the multiple PDSCHs.

[0159] In the seventeenth additional aspect, either alone or in combination with one or more of the first to sixteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, sending multiple bundled ACK-NACK bits, wherein transport blocks are aggregated into a common pool across codewords and bundled with the available multiple bundled ACK-NACK bits.

[0160] In the eighteenth additional aspect, either alone or in combination with one or more of the first to seventeenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured to have multiple codewords, sending multiple bundled ACK-NACK bits, wherein CBG across codewords is aggregated into a common pool and bundled with the available multiple bundled ACK-NACK bits.

[0161] In the nineteenth additional aspect, either alone or in combination with one or more of the first to eighteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, sending multiple bundled ACK-NACK bits, wherein the actual number of CBG span codewords for each transport block are aggregated into a common pool and bundled into the available multiple bundled ACK-NACK bits.

[0162] In the twentieth additional aspect, either alone or in combination with one or more of the first to nineteenth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, sending multiple bundled ACK-NACK bits, wherein the aggregation of multiple PDSCHs occurs prior to the aggregation of the multiple codewords.

[0163] In the twenty-first additional aspect, either alone or in combination with one or more of the first to twentieth aspects, sending ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, sending multiple bundled ACK-NACK bits, wherein the aggregation of the multiple codewords occurs before the aggregation of the multiple PDSCHs.

[0164] Although Figure 13 An example box of process 1300 is shown, but in some aspects, process 1300 may include... Figure 13 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1300 may be executed in parallel.

[0165] Figure 14 This is a schematic diagram illustrating, for example, an example procedure 1400 performed by a UE. Procedure 1400 is an example in which a UE (e.g., UE 120) performs an operation associated with an ACK-NACK report for downlink shared channel permission.

[0166] like Figure 14 As shown, in some aspects, process 1400 may include: receiving a DCI from a base station, the DCI including PDSCH permission for multiple PDSCHs (box 1410). For example, a UE (such as by using...) Figure 18 The receiving component 1802 depicted herein can receive a DCI from a base station, the DCI including PDSCH permissions for multiple PDSCHs as described herein.

[0167] like Figure 14 As further shown, in some aspects, process 1400 may include: identifying a virtual DCI associated with at least one PDSCH included in a plurality of PDSCHs (box 1420). For example, a UE (such as by using...) Figure 18 The identification component 1810 described herein can identify virtual DCIs associated with at least one of the multiple PDSCHs included herein.

[0168] like Figure 14 As further shown, in some aspects, process 1400 may include: sending ACK-NACK for multiple PDSCHs to the base station via PUCCH based on virtual DCI (box 1430). For example, the UE (such as by using...) Figure 18 The transmitting component 1804 described herein can transmit ACK-NACK for multiple PDSCHs to the base station via PUCCH based on virtual DCI, as described herein.

[0169] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0170] In the first additional aspect, the first counter DAI included in the DCI permitted by the PDSCH is associated with the first PDSCH among the plurality of PDSCHs, and the subsequent counter DAI is associated with the remaining PDSCHs among the plurality of PDSCHs.

[0171] In the second additional aspect, either alone or in combination with the first aspect, the subsequent counter DAI for the remaining PDSCH is associated with the virtual DCI.

[0172] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, for one or more DCIs and virtual DCIs associated with the same PUCCH reporting instance, the counter DAI associated with one or more DCIs and virtual DCIs is incremented so that the UE can detect one or more lost PDSCH permission.

[0173] In the fourth additional aspect, PDSCH is permitted to be associated with a single component carrier, either alone or in combination with one or more of the first to third aspects.

[0174] In the fifth additional aspect, either alone or in combination with one or more of the first through fourth aspects, PDSCH is permitted to be associated with the counter DAI and the total DAI when carrier aggregation is enabled.

[0175] In the sixth additional aspect, either alone or in combination with one or more of the first through fifth aspects, for each PDSCH permitted, the virtual DCI is configured according to the symbol-level offset of the definition of PDSCH permitted.

[0176] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the virtual DCI is configured in each time slot after receiving the DCI associated with PDSCH permission from the base station.

[0177] Although Figure 14 An example box of process 1400 is shown, but in some aspects, process 1400 may include... Figure 14 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1400 may be executed in parallel.

[0178] Figure 15This is a schematic diagram illustrating, for example, an example process 1500 performed by a base station (BS). Process 1500 is an example in which a base station (e.g., base station 110) performs operations associated with an ACK-NACK report for downlink shared channel permission.

[0179] like Figure 15 As shown, in some aspects, process 1500 may include: sending a DCI configured to schedule multiple PDSCHs to the UE, wherein the DCI indicates: a PDSCH to HARQ feedback timing value, and a PRI associated with PUCCH resources (block 1510). For example, a base station (such as by using...) Figure 19 The transmitting component 1904 described herein can transmit a DCI configured to schedule multiple PDSCHs to the UE, wherein the DCI indicates: the PDSCH to HARQ feedback timing value, and the PRI associated with the PUCCH resource, as described herein.

[0180] like Figure 15 As further shown, in some aspects, process 1500 may include: using PUCCH resources to receive HARQ feedback from the UE for multiple PDSCHs (box 1520). For example, a base station (such as by using...) Figure 19 The receiving component 1902 described herein can use PUCCH resources to receive HARQ feedback from the UE for multiple PDSCHs, as described herein.

[0181] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0182] In the first additional aspect, the PDSCH to HARQ feedback timing value corresponds to the time period between the last PDSCH and the PUCCH resource among multiple PDSCHs.

[0183] In the second additional aspect, either alone or in combination with the first aspect, HARQ feedback for multiple PDSCHs includes ACK or NACK associated with multiple PDSCHs.

[0184] Although Figure 15 An example box of process 1500 is shown, but in some aspects, process 1500 may include... Figure 15 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1500 may be executed in parallel.

[0185] Figure 16This is a schematic diagram illustrating, for example, an example process 1600 performed by a base station (BS). Process 1600 is an example in which a base station (e.g., base station 110) performs operations associated with an ACK-NACK report for downlink shared channel permission.

[0186] like Figure 16 As shown, in some aspects, process 1600 may include: sending a DCI to the UE, the DCI including PDSCH permission for multiple PDSCHs (box 1610). For example, a base station (such as by using...) Figure 19 The transmitting component 1904 described herein can transmit a DCI to the UE, which includes PDSCH authorization for multiple PDSCHs, as described herein.

[0187] like Figure 16 As further shown, in some aspects, process 1600 may include: receiving bundled ACK-NACKs for multiple PDSCHs from the UE via PUCCH (box 1620). For example, a base station (such as by using...) Figure 19 The receiving component 1902 described herein can receive bundled ACK-NACKs for multiple PDSCHs from the UE via PUCCH, as described herein.

[0188] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0189] In the first additional aspect, the size of the bundled ACK-NACK for multiple PDSCHs associated with a PDSCH permission corresponds to the size of the ACK-NACK for a single PDSCH permission.

[0190] In the second additional aspect, either alone or in combination with the first aspect, when a single component carrier is configured, the PDSCH is permitted to be associated with the counter DAI.

[0191] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, a PDSCH grant is a first PDSCH grant with a first counter DAI, wherein a second PDSCH grant that occurs later in time than the first PDSCH grant is associated with a second counter DAI incremented from the first counter DAI, wherein the first PDSCH grant and the second PDSCH grant are associated with the same PUCCH reporting instance.

[0192] In the fourth additional aspect, either alone or in combination with one or more of the first to third aspects, a first PDSCH permission or a second PDSCH permission is detected as corresponding to a lost PDSCH permission based on a first counter DAI or a second counter DAI.

[0193] In the fifth additional aspect, either alone or in combination with one or more of the first through fourth aspects, PDSCH is permitted to be associated with the counter DAI and the total DAI when carrier aggregation is enabled.

[0194] In the sixth additional aspect, receiving ACK-NACK, either alone or in combination with one or more of the first to fifth aspects, includes: receiving ACK-NACK for multiple PDSCHs per DCI for a single codeword that does not have spatial binding and when no CBG ACK-NACK is configured for the UE.

[0195] In the seventh additional aspect, receiving ACK-NACK, either alone or in combination with one or more of the first to sixth aspects, includes receiving ACK-NACK for multiple PDSCHs per DCI when there is no CBG ACK-NACK configured for the UE and for multiple codewords with spatial binding.

[0196] In the eighth additional aspect, either alone or in combination with one or more of the first to seventh aspects, the ACK-NACK for multiple PDSCHs is an ACK-NACK bit.

[0197] In the ninth additional aspect, receiving ACK-NACK, either alone or in combination with one or more of the first to eighth aspects, includes receiving ACK-NACK for multiple codewords and, when no CBG ACK-NACK is configured for the UE, receiving ACK-NACK for multiple PDSCHs.

[0198] In the tenth additional aspect, either alone or in combination with one or more aspects from the first to the ninth aspect, the ACK-NACK for each PDSCH included in the multiple PDSCHs is two ACK-NACK bits.

[0199] In the eleventh additional aspect, either alone or in combination with one or more aspects from the first to the tenth aspects, ACK-NACK is bundled across multiple PDSCHs.

[0200] In the twelfth additional aspect, either alone or in combination with one or more of the first to eleventh aspects, ACK-NACK is spatially bundled and associated with a subgroup of PDSCHs in a plurality of PDSCHs.

[0201] In the thirteenth additional aspect, receiving ACK-NACK, either alone or in combination with one or more of the first to twelfth aspects, includes: receiving a plurality of bundled ACK-NACK bits when the CBG ACK-NACK is configured with a single codeword, wherein each of the plurality of bundled ACK-NACK bits corresponds to a bundled transport block-level feedback.

[0202] In the fourteenth additional aspect, receiving ACK-NACK, either alone or in combination with one or more of the first to thirteenth aspects, includes: receiving multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein CBG ACK-NACK for multiple PDSCHs is aggregated and split to form multiple bundled ACK-NACK bits.

[0203] In the fifteenth additional aspect, alone or in combination with one or more of the first to fourteenth aspects, receiving ACK-NACK includes: receiving a plurality of bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein each of the plurality of bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in the plurality of PDSCHs.

[0204] In the sixteenth additional aspect, alone or in combination with one or more of the first to fifteenth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving a plurality of bundled ACK-NACK bits for each codeword that does not have spatial bundling, wherein the plurality of bundled ACK-NACK bits correspond to bundled transport block-level feedback, the plurality of bundled ACK-NACK bits being based on the aggregation and splitting of CBG ACK-NACK for multiple PDSCHs to form a plurality of bundled ACK-NACK bits, or each of the plurality of bundled ACK-NACK bits being based on the actual number of CBGs for each transport block in the multiple PDSCHs.

[0205] In the seventeenth additional aspect, alone or in combination with one or more of the first to sixteenth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving multiple bundled ACK-NACK bits, wherein transport blocks are aggregated across codewords into a common pool and bundled with the available multiple bundled ACK-NACK bits.

[0206] In the eighteenth additional aspect, alone or in combination with one or more of the first to seventeenth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving multiple bundled ACK-NACK bits, wherein CBG across codewords is aggregated into a common pool and bundled with the available multiple bundled ACK-NACK bits.

[0207] In the nineteenth additional aspect, alone or in combination with one or more of the first to eighteenth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving multiple bundled ACK-NACK bits, wherein the actual number of CBG span codewords for each transport block are aggregated into a common pool and bundled into the available multiple bundled ACK-NACK bits.

[0208] In the twentieth additional aspect, alone or in combination with one or more of the first to nineteenth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving multiple bundled ACK-NACK bits, wherein the aggregation of multiple PDSCHs occurs prior to the aggregation of the multiple codewords.

[0209] In the twenty-first additional aspect, alone or in combination with one or more of the first to twentieth aspects, receiving ACK-NACK includes: when CBG ACK-NACK is configured with multiple codewords, receiving multiple bundled ACK-NACK bits, wherein the aggregation of the multiple codewords occurs prior to the aggregation of the multiple PDSCHs.

[0210] Although Figure 16 An example box of process 1600 is shown, but in some aspects, process 1600 may include... Figure 16 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1600 may be executed in parallel.

[0211] Figure 17 This is a schematic diagram illustrating, for example, an example procedure 1700 performed by a base station (BS). Procedure 1700 is an example in which a base station (e.g., base station 110) performs operations associated with an ACK-NACK report for downlink shared channel permission.

[0212] like Figure 17 As shown, in some aspects, process 1700 may include: sending a DCI to the UE, the DCI including PDSCH permission for multiple PDSCHs (box 1710). For example, a base station (such as by using...) Figure 19 The transmitting component 1904 described herein can transmit a DCI to the UE, which includes PDSCH authorization for multiple PDSCHs, as described herein.

[0213] like Figure 17 As further shown, in some aspects, process 1700 may include: receiving ACK-NACK for multiple PDSCHs from the UE via PUCCH based on a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs (box 1720). For example, a base station (such as by using...) Figure 19 The receiving component 1902 described herein can receive ACK-NACK for multiple PDSCHs from the UE via PUCCH based on a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs, as described herein.

[0214] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described herein or in conjunction with one or more other processes described elsewhere herein.

[0215] In the first additional aspect, the first counter DAI included in the DCI permitted by the PDSCH is associated with the first PDSCH among the plurality of PDSCHs, and the subsequent counter DAI is associated with the remaining PDSCHs among the plurality of PDSCHs.

[0216] In the second additional aspect, either alone or in combination with the first aspect, the subsequent counter DAI for the remaining PDSCH is associated with the virtual DCI.

[0217] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, for one or more DCIs and virtual DCIs associated with the same PUCCH reporting instance, the counter DAI associated with one or more DCIs and virtual DCIs is incremented so that the UE can detect one or more lost PDSCH permission.

[0218] In the fourth additional aspect, PDSCH is permitted to be associated with a single component carrier, either alone or in combination with one or more of the first to third aspects.

[0219] In the fifth additional aspect, either alone or in combination with one or more of the first through fourth aspects, PDSCH is permitted to be associated with the counter DAI and the total DAI when carrier aggregation is enabled.

[0220] In the sixth additional aspect, either alone or in combination with one or more of the first through fifth aspects, for each PDSCH permitted, the virtual DCI is configured according to the symbol-level offset of the definition of PDSCH permitted.

[0221] In the seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the virtual DCI is configured in each time slot after receiving the DCI associated with PDSCH permission from the base station.

[0222] Although Figure 17 An example box of process 1700 is shown, but in some aspects, process 1700 may include... Figure 17 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Alternatively, two or more boxes in process 1700 may be executed in parallel.

[0223] Figure 18 This is a block diagram of an example device 1800 for wireless communication. Device 1800 may be a UE, or a UE may include device 1800. In some aspects, device 1800 includes a receiving component 1802 and a transmitting component 1804, which can communicate with each other (e.g., via one or more buses or one or more other components). As shown, device 1800 can use the receiving component 1802 and the transmitting component 1804 to communicate with another device 1806 (such as a UE, a base station, or another wireless communication device). As further shown, device 1800 may include one or more of a determining component 1808 or an identifying component 1810, and other examples.

[0224] In some respects, device 1800 can be configured to perform the functions described herein. Figure 4-11 One or more operations described herein. Alternatively or concurrently, the apparatus 1800 may be configured to perform one or more processes described herein, such as... Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 The process 1400 or a combination thereof. In some respects, Figure 18 The device 1800 or one or more components shown herein may include those described in conjunction with this document. Figure 2 One or more components of the UE as described. Alternatively or in addition, Figure 18 One or more components shown can be combined in this article Figure 2The description refers to implementation within one or more components. Alternatively, one or more components in the set of components may be implemented, at least partially, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0225] Receiver 1802 may receive communications from device 1806, such as reference signals, control information, data communications, or combinations thereof. Receiver 1802 may provide the received communications to one or more other components of device 1800. In some aspects, receiver 1802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1800. In some aspects, receiver 1802 may include, as described herein... Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0226] Transmitting component 1804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1806. In some aspects, one or more other components of device 1800 can generate communications and provide the generated communications to transmitting component 1804 for transmission to device 1806. In some aspects, transmitting component 1804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 1806. In some aspects, transmitting component 1804 can include, as described herein... Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, transmit component 1804 may be co-located with receive component 1802 in a transceiver.

[0227] The receiving component 1802 can receive a DCI configured to schedule multiple PDSCHs from the base station, wherein the DCI indicates the PDSCH to HARQ feedback timing value and the PRI associated with the PUCCH resource. The transmitting component 1804 can use the PUCCH resource to transmit HARQ feedback for multiple PDSCHs to the base station.

[0228] The receiving component 1802 can receive a DCI from the base station, which includes PDSCH authorization for multiple PDSCHs. The transmitting component 1804 can transmit bundled ACK-NACKs for multiple PDSCHs to the base station via PUCCH.

[0229] The determining component 1808 may determine, based on a first counter DAI or a second counter DAI, whether the first PDSCH permission corresponds to a lost PDSCH permission. In some aspects, the determining component 1808 may include, as described herein, […]. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Transmit component 1804 can transmit a NACK granted for a lost PDSCH.

[0230] The transmitting component 1804 can transmit ACK-NACK for multiple PDSCHs per DCI for a single codeword that does not have spatial binding and when no CBGACK-NACK is configured for the UE.

[0231] The transmitting component 1804 can transmit ACK-NACK for multiple PDSCHs per DCI when there are multiple codewords with spatial binding and when no CBG ACK-NACK is configured for the UE.

[0232] The transmitting component 1804 can transmit ACK-NACK for multiple PDSCHs even when CBG ACK-NACK is not configured for the UE.

[0233] The transmitting component 1804 can transmit multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein each of the multiple bundled ACK-NACK bits corresponds to a bundled transport block level feedback.

[0234] The transmitting component 1804 can transmit multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein CBG ACK-NACK for multiple PDSCHs is aggregated and split to form multiple bundled ACK-NACK bits.

[0235] The transmitting component 1804 can transmit multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein each of the multiple bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in the multiple PDSCHs.

[0236] When CBG ACK-NACK is configured to have multiple codewords, the transmitting component 1804 may transmit multiple bundled ACK-NACK bits for each codeword that does not have spatial bundling, wherein the multiple bundled ACK-NACK bits correspond to bundled transport block-level feedback, and the multiple bundled ACK-NACK bits are based on the aggregation and splitting of CBG ACK-NACK for multiple PDSCHs to form multiple bundled ACK-NACK bits, or each of the multiple bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in the multiple PDSCHs.

[0237] When CBG ACK-NACK is configured to have multiple codewords, the transmitting component 1804 can transmit multiple bundled ACK-NACK bits, wherein transport blocks are aggregated into a common pool across codewords and bundled with multiple available bundled ACK-NACK bits.

[0238] When CBG ACK-NACK is configured to have multiple codewords, the sending component 1804 can send multiple bundled ACK-NACK bits, wherein the CBG spans codewords and is aggregated into a common pool and bundled with the available multiple bundled ACK-NACK bits.

[0239] When CBG ACK-NACK is configured to have multiple codewords, the transmitting component 1804 can transmit multiple bundled ACK-NACK bits, wherein the actual number of CBG span codewords for each transport block are aggregated into a common pool and bundled into the available multiple bundled ACK-NACK bits.

[0240] When CBG ACK-NACK is configured to have multiple codewords, the transmitting component 1804 can transmit multiple bundled ACK-NACK bits, wherein the aggregation of multiple PDSCHs occurs before the aggregation of multiple codewords.

[0241] When CBG ACK-NACK is configured to have multiple codewords, the transmitting component 1804 can transmit multiple bundled ACK-NACK bits, wherein the aggregation of multiple codewords occurs before the aggregation of multiple PDSCHs.

[0242] The receiving component 1802 can receive a DCI from a base station, the DCI including PDSCH permissions for multiple PDSCHs. The identification component 1810 can identify a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs. In some aspects, the identification component 1810 may include elements incorporated herein by reference. Figure 2The described UE includes one or more antennas, demodulators, MIMO detectors, receive processors, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Transmit component 1804 can transmit ACK-NACK signals for multiple PDSCHs to the base station via PUCCH based on virtual DCI.

[0243] Figure 18 The number and arrangement of components shown are provided as an example. In reality, they can exist in combination with... Figure 18 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 18 The two or more components shown can be implemented within a single component, or Figure 18 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 18 The set (one or more) components shown can perform actions described by Figure 18 The other set of components shown performs one or more functions.

[0244] Figure 19 This is a block diagram of an example device 1900 for wireless communication. Device 1900 may be a base station, or a base station may include device 1900. In some aspects, device 1900 includes a receiving component 1902 and a transmitting component 1904, which can communicate with each other (e.g., via one or more buses or one or more other components). As shown, device 1900 can use the receiving component 1902 and the transmitting component 1904 to communicate with another device 1906 (such as a UE, a base station, or another wireless communication device).

[0245] In some respects, device 1900 can be configured to perform the functions described herein. Figure 4-11 One or more operations described herein. Alternatively or concurrently, the apparatus 1900 may be configured to perform one or more processes described herein, such as... Figure 15 Process 1500 Figure 16 Process 1600 Figure 17 The process 1700 or a combination thereof. In some respects, Figure 19 The device 1900 or one or more components shown herein may include those described in conjunction with this document. Figure 2 One or more components of the described base station. Alternatively, Figure 19 One or more components shown can be combined in this article Figure 2The description refers to implementation within one or more components. Alternatively, one or more components in the set of components may be implemented, at least partially, as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0246] Receiver 1902 may receive communications from device 1906, such as reference signals, control information, data communications, or combinations thereof. Receiver 1902 may provide the received communications to one or more other components of device 1900. In some aspects, receiver 1902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signal to one or more other components of device 1900. In some aspects, receiver 1902 may include, as described herein... Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0247] Transmitting component 1904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1906. In some aspects, one or more other components of device 1900 can generate communications and provide the generated communications to transmitting component 1904 for transmission to device 1906. In some aspects, transmitting component 1904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples) on the generated communications and can transmit the processed signals to device 1906. In some aspects, transmitting component 1904 can include, as described herein... Figure 2 The described base station includes one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof. In some aspects, the transmit component 1904 may be co-located with the receive component 1902 in a transceiver.

[0248] Transmitting component 1904 can transmit to the UE a DCI configured to schedule multiple PDSCHs, wherein the DCI indicates the PDSCH-to-HARQ feedback timing value and the PRI associated with the PUCCH resource. Receiving component 1902 can use the PUCCH resource to receive HARQ feedback from the UE for multiple PDSCHs.

[0249] The receiving component 1902 can receive a DCI to the UE, which includes PDSCH authorization for multiple PDSCHs. The receiving component 1902 can receive bundled ACK-NACKs for multiple PDSCHs from the UE via PUCCH.

[0250] The receiving component 1902 can receive ACK-NACK for multiple PDSCHs per DCI for a single codeword that does not have spatial binding and when no CBGACK-NACK is configured for the UE.

[0251] The receiving component 1902 can receive ACK-NACK for multiple PDSCHs per DCI when there are multiple codewords with spatial binding and when no CBG ACK-NACK is configured for the UE.

[0252] The receiving component 1902 can receive ACK-NACK for multiple PDSCHs even when CBG ACK-NACK is not configured for the UE.

[0253] The receiving component 1902 can receive multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein each of the multiple bundled ACK-NACK bits corresponds to a bundled transport block level feedback.

[0254] The receiving component 1902 can receive multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein CBG ACK-NACK for multiple PDSCHs is aggregated and split to form multiple bundled ACK-NACK bits.

[0255] The receiving component 1902 can receive multiple bundled ACK-NACK bits when CBG ACK-NACK is configured with a single codeword, wherein each of the multiple bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in the multiple PDSCHs.

[0256] When CBG ACK-NACK is configured to have multiple codewords, receiving component 1902 can receive multiple bundled ACK-NACK bits for each codeword that does not have spatial bundling, wherein the multiple bundled ACK-NACK bits correspond to bundled transport block-level feedback, and the multiple bundled ACK-NACK bits are based on the aggregation and splitting of CBG ACK-NACK for multiple PDSCHs to form multiple bundled ACK-NACK bits, or each of the multiple bundled ACK-NACK bits is based on the actual number of CBGs for each transport block in multiple PDSCHs.

[0257] When CBG ACK-NACK is configured to have multiple codewords, receiving component 1902 can receive multiple bundled ACK-NACK bits, wherein transport blocks are aggregated into a common pool across codewords and bundled with multiple available bundled ACK-NACK bits.

[0258] When CBG ACK-NACK is configured to have multiple codewords, receiving component 1902 can receive multiple bundled ACK-NACK bits, wherein CBG spanning codewords are aggregated into a common pool and bundled with multiple available bundled ACK-NACK bits.

[0259] When CBG ACK-NACK is configured to have multiple codewords, receiving component 1902 can receive multiple bundled ACK-NACK bits, wherein the actual number of CBG span codewords for each transport block are aggregated into a common pool and bundled into the available multiple bundled ACK-NACK bits.

[0260] The receiving component 1902 can receive multiple bundled ACK-NACK bits when CBG ACK-NACK is configured to have multiple codewords, wherein the aggregation of multiple PDSCHs occurs before the aggregation of multiple codewords.

[0261] The receiving component 1902 can receive multiple bundled ACK-NACK bits when CBG ACK-NACK is configured to have multiple codewords, wherein the aggregation of multiple codewords occurs before the aggregation of multiple PDSCHs.

[0262] The transmitting component 1904 can transmit a DCI to the UE, which includes PDSCH authorization for multiple PDSCHs. The receiving component 1902 can receive ACK-NACK for multiple PDSCHs from the UE via PUCCH based on a virtual DCI associated with at least one PDSCH included in the multiple PDSCHs.

[0263] Figure 19The number and arrangement of components shown are provided as an example. In reality, they can exist in combination with... Figure 19 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 19 The two or more components shown can be implemented within a single component, or Figure 19 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 19 The set (one or more) components shown can perform actions described by Figure 19 The other set of components shown performs one or more functions.

[0264] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on this disclosure, or may be derived from practice in relation to the aspects.

[0265] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as meaning "at least partially based on". As used herein, depending on the context, "meeting a threshold" can refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold, and other examples. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c.

[0266] Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more”. Furthermore, as used herein, the article “the” is intended to include one or more items referenced in combination with the article “the” and is interchangeable with “one or more”. Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more”. The phrase “only one” or similar language is used when only one item is anticipated. Furthermore, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise expressly stated (e.g., if used in combination with “any” or “only one of”).

[0267] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been demonstrated in the various illustrative components, blocks, modules, circuits, and processes described herein, all centered around functionality. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0268] Hardware and data processing apparatuses for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, a particular process or method may be executed by circuitry specific to a given function.

[0269] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware (including the structures disclosed in this specification and their structural equivalents), or any combination thereof. Aspects of the subject matter described in this specification may also be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0270] If implemented in software, the functionality can be stored or transmitted as one or more instructions or code on or through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in processor-executable software modules that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, wherein the communication medium includes any medium capable of enabling the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection can be appropriately referred to as a computer-readable medium. As used herein, "disk" and "optical disc" include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while optical discs optically copy data using lasers. Combinations of media described herein should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as one or any combination or set of code and instructions on a machine-readable and computer-readable medium, which may be incorporated into a computer program product.

[0271] Various modifications to the aspects described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the aspects shown herein, but rather to be consistent with the widest scope in accordance with this disclosure, the principles disclosed herein, and the novel features.

[0272] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0273] Some features described in this specification in the context of a single aspect may also be implemented in combination within that single aspect. Conversely, various features described in the context of a single aspect may also be implemented individually or in any suitable sub-combination in multiple aspects. Furthermore, while features may be described as functioning in certain combinations, and even initially claimed in this way, in some cases one or more features from the claimed combination may be removed from that combination, and the claimed combination may involve sub-combinations or variations thereof.

[0274] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the shown specific order or sequential order, or to perform all shown operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the shown operations. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the described aspects should not be construed as requiring such separation in all aspects, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and the desired result may still be achieved.

Claims

1. A method for wireless communication performed by a device of a user equipment (UE), comprising: Receive downlink control information (DCI) from network nodes, including PDSCH grants configured to schedule multiple Physical Downlink Shared Channels (PDSCHs), wherein, when carrier aggregation is enabled, the PDSCH grants are associated with a total downlink assignment indicator (DAI), wherein the DCI indicates: PDSCH to Hybrid Automatic Repeat Request (HARQ) feedback timing value, and A PUCCH resource indicator (PRI) associated with the Physical Uplink Control Channel (PUCCH) resource; and HARQ ACK / NACK feedback sent to the network node using a fixed feedback size in the PUCCH resource, the HARQ ACK / NACK feedback being bundled for the plurality of PDSCHs according to the following: Relative to the spatial bundling configuration of the multiple PDSCHs, and ACK-NACK configuration for the code block group (CBG) of the UE.

2. The method according to claim 1, wherein, The PDSCH to HARQ feedback timing value corresponds to the time period between the last PDSCH among the plurality of PDSCHs and the PUCCH resource.

3. The method according to claim 1, wherein, The HARQ ACK / NACK feedback for the plurality of PDSCHs includes an acknowledgment (ACK) or a negative acknowledgment (NACK) associated with the plurality of PDSCHs.

4. A method for wireless communication performed by a device of a user equipment (UE), comprising: Receive downlink control information (DCI) from a network node, the DCI including a first PDSCH grant for multiple physical downlink shared channels (PDSCH), wherein: The first PDSCH is permitted to be associated with the first counter downlink assignment indicator (DAI). When carrier aggregation is enabled, the first PDSCH is allowed to be associated with the total DAI. The second PDSCH grant, which occurs later in time than the first PDSCH grant and is included in the second DCI, is associated with the second counter downlink assignment indicator (DAI). The first PDSCH grant and the second PDSCH grant are associated with the same Physical Uplink Control Channel (PUCCH) reporting instance; and The PUCCH reporting instance sends bundled acknowledgments / negative acknowledgments (ACK-NACK) to the network node for the plurality of PDSCHs.

5. The method according to claim 4, wherein, The PDSCH permission is a multi-PDSCH permission, and the size of the bundled ACK-NACK for the multiple PDSCHs associated with the multi-PDSCH permission corresponds to the size of the ACK-NACK for a single PDSCH permission.

6. The method according to claim 4, wherein, When a single component carrier is configured, the PDSCH permission is associated with the counter downlink assignment indicator (DAI).

7. The method according to claim 4, further comprising: The first PDSCH permission or the second PDSCH permission is determined to correspond to a lost PDSCH permission based on the first counter DAI or the second counter DAI, and Sending the ACK-NACK includes sending a negative acknowledgment (NACK) for the lost PDSCH.

8. The method according to claim 4, wherein, Sending the ACK-NACK includes: For a single codeword without spatial binding or for multiple codewords with spatial binding, and when no code block group (CBG) ACK-NACK is configured for the UE, each DCI sends the ACK-NACK for the multiple PDSCHs.

9. The method according to claim 4, wherein, The ACK-NACK for the multiple PDSCHs is an ACK-NACK bit.

10. The method according to claim 4, wherein, Sending the ACK-NACK includes: For multiple codewords and when no code block group (CBG) ACK-NACK is configured for the UE, the ACK-NACK for the multiple PDSCHs is sent.

11. The method according to claim 10, wherein, The ACK-NACK for each PDSCH included in the plurality of PDSCHs consists of two ACK-NACK bits.

12. The method according to claim 10, wherein, The ACK-NACK is bundled across the multiple PDSCHs.

13. The method according to claim 10, wherein, The ACK-NACK is spatially bound and associated with a subgroup of PDSCHs among the plurality of PDSCHs.

14. An apparatus for a user equipment (UE) for wireless communication, comprising: A first interface is configured to: obtain downlink control information (DCI) including PDSCH authorization configured to schedule multiple physical downlink shared channels (PDSCHs), wherein, when carrier aggregation is enabled, the PDSCH authorization is associated with a total downlink assignment indicator (DAI), wherein the DCI indicates: PDSCH to Hybrid Automatic Repeat Request (HARQ) feedback timing value, and A PUCCH resource indicator (PRI) associated with the Physical Uplink Control Channel (PUCCH) resource; and the first or second interface configured to output HARQ ACK / NACK feedback using a fixed feedback size in the PUCCH resource, the HARQ ACK / NACK feedback being bundled for the plurality of PDSCHs according to the following: Relative to the spatial bundling configuration of the multiple PDSCHs, and ACK-NACK configuration for the code block group (CBG) of the UE.

15. The apparatus according to claim 14, wherein, The PDSCH to HARQ feedback timing value corresponds to the time period between the last PDSCH among the plurality of PDSCHs and the PUCCH resource.

16. The apparatus according to claim 14, wherein, The HARQ ACK / NACK feedback for the plurality of PDSCHs includes an acknowledgment (ACK) or a negative acknowledgment (NACK) associated with the plurality of PDSCHs.

17. An apparatus for a user equipment (UE) for wireless communication, comprising: The first interface is configured to: obtain downlink control information (DCI), the DCI including a first PDSCH grant for multiple physical downlink shared channels (PDSCH), wherein: The first PDSCH is permitted to be associated with the first counter downlink assignment indicator (DAI). When carrier aggregation is enabled, the first PDSCH is allowed to be associated with the total DAI. The second PDSCH grant, which occurs later in time than the first PDSCH grant and is included in the second DCI, is associated with the second counter downlink assignment indicator (DAI). The first PDSCH grant and the second PDSCH grant are associated with the same Physical Uplink Control Channel (PUCCH) reporting instance; and The first or second interface is configured to output bundled acknowledgments / negative acknowledgments (ACK-NACK) for the plurality of PDSCHs via the PUCCH report instance.

18. The apparatus according to claim 17, wherein, The PDSCH permission is a multi-PDSCH permission, and the size of the bundled ACK-NACK for the multiple PDSCHs associated with the multi-PDSCH permission corresponds to the size of the ACK-NACK for a single PDSCH permission.

19. The apparatus according to claim 17, wherein, When a single component carrier is configured, the PDSCH permission is associated with the counter downlink assignment indicator (DAI).

20. The apparatus of claim 17, further comprising: The processing system is configured to: determine, based on the first counter DAI or the second counter DAI, whether the first PDSCH permission or the second PDSCH permission corresponds to a lost PDSCH permission, and The first interface or the second interface is further configured to output a negative acknowledgment (NACK) for the lost PDSCH.

21. The apparatus according to claim 17, wherein, The first interface or the second interface is further configured as follows: For a single codeword without spatial binding or for multiple codewords with spatial binding and when no code block group (CBG) ACK-NACK is configured for the UE, each DCI outputs the ACK-NACK for the multiple PDSCHs.

22. The apparatus according to claim 17, wherein, The ACK-NACK for the multiple PDSCHs is an ACK-NACK bit.

23. The apparatus according to claim 17, wherein, The first interface or the second interface is further configured as follows: For multiple codewords and when no code block group (CBG) ACK-NACK is configured for the UE, the ACK-NACK for the multiple PDSCHs is output.

24. The apparatus according to claim 23, wherein, The ACK-NACK for each PDSCH included in the plurality of PDSCHs consists of two ACK-NACK bits.

25. The apparatus according to claim 23, wherein, The ACK-NACK is bundled across the multiple PDSCHs.

26. The apparatus according to claim 23, wherein, The ACK-NACK is spatially bound and associated with a subgroup of PDSCHs among the plurality of PDSCHs.

Images