CN117223240A - Relaxing timeline constraints on HARQ feedback multiplexing on PUSCH and related processes - Google Patents

Abstract

The UE receives at least one DL grant from the base station or a component of the base station after receiving the UL grant, the at least one DL grant being associated with a DL cDAI value and a DL tDAI value, the UL grant being associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions. The UE calculates a total number of DL grants sent to the UE based on the DL cDAI value. If there is a difference between the total number of DL grants and the UL tDAI value, the UE adjusts the total number of DL grants. The UE transmits a HARQ codebook to the base station in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on the total number of adjusted DL grants.

Description

Relaxing timeline constraints on HARQ feedback multiplexing on PUSCH and related processes

Cross Reference to Related Applications

The present application claims the benefit and priority of the following applications: U.S. provisional application Ser. No.63/186,758, filed 5/10 of 2021 and entitled "RELAXING TIMELINE CONSTRAINTS ON HARQ FEEDBACK MULTIPLEXING ON PUSCH AND RELATED PROCEDURES"; and U.S. non-provisional patent application Ser. No.17/661,400 submitted at 29 of 4 of 2022 and entitled "RELAXING TIMELINE CONSTRAINTS ON HARQ FEEDBACK MULTIPLEXING ON PUSCH ANDRELATED PROCEDURES", the entire contents of which are expressly incorporated herein by reference.

Technical Field

The present disclosure relates generally to communication systems, and more particularly, to wireless communications involving hybrid automatic repeat request (HARQ) feedback.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing the available system resources. Examples of such multiple-access techniques 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). The 5G NR is part of the continuous mobile broadband evolution promulgated by the third generation partnership project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the internet of things (IoT)), and other requirements. The 5G NR includes services associated with enhanced mobile broadband (emmbb), large-scale machine type communication (emtc), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements may also be applicable to other multiple access techniques and telecommunication standards employing these techniques.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus receives at least one Downlink (DL) grant associated with a DL current downlink assignment index (cDAI) value and a DL total downlink assignment index (tDAI) value after receiving an Uplink (UL) grant associated with a UL tDAI value and scheduling a plurality of Physical Uplink Shared Channel (PUSCH) repetitions. The apparatus calculates a total number of DL grants transmitted to the UE based on the DL cDAI value. The apparatus adjusts the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value. The apparatus transmits a hybrid automatic repeat request (HARQ) codebook in at least one PUSCH repetition of a plurality of PUSCH repetitions, the size of the HARQ codebook being based on a total number of adjusted DL grants.

In one aspect of the disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus transmits at least one DL grant for a User Equipment (UE) after transmitting the UL grant, the at least one DL grant being associated with a DL cDAI value and a DL tDAI value, the UL grant being associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions. The apparatus receives a HARQ codebook in at least one PUSCH repetition of a plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value.

To the accomplishment of the foregoing and related ends, one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present specification is intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is a schematic diagram illustrating an example of a wireless communication system and an access network.

Fig. 2A is a schematic diagram illustrating an example of a first frame in accordance with aspects of the present disclosure.

Fig. 2B is a schematic diagram illustrating an example of DL channels within a subframe according to aspects of the present disclosure.

Fig. 2C is a schematic diagram illustrating an example of a second frame in accordance with aspects of the present disclosure.

Fig. 2D is a diagram illustrating an example of UL channels within a subframe in accordance with aspects of the present disclosure.

Fig. 3 is a schematic diagram showing an example of a base station and a User Equipment (UE) in an access network.

Fig. 4 is a diagram 400 illustrating an example in which a UE multiplexes hybrid automatic repeat request (HARQ) -Acknowledgement (ACK)/Negative ACK (NACK) (HARQ-ACK/NACK) bits with a Physical Uplink Shared Channel (PUSCH) for DL grants received prior to receiving an UL grant for a scheduled PUSCH, but not for DL grants received after receiving the UL grant, in accordance with aspects of the present disclosure.

Fig. 5 is a diagram illustrating an example of a UE configured to apply a total downlink assignment index (tDAI) parameter carried by a UL grant to all repetitions scheduled by the UL grant, in accordance with various aspects of the disclosure.

Fig. 6 is a diagram illustrating an example in which a UE multiplexes HARQ-ACK/NACK bits of a late-rising DL grant (e.g., a DL grant arriving after an uplink grant) with at least one PUSCH repetition, according to aspects of the present disclosure.

Fig. 7 is a schematic diagram illustrating an example of multiplexing a late arriving DL grant with at least one of a second PUSCH repetition and a subsequent PUSCH repetition in accordance with aspects of the present disclosure.

Fig. 8 is a communication flow illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on current downlink assignment index (cDAI) parameters and/or tDAI parameters of UL/DL grants when the UE is configured to multiplex one or more late arriving DL grants with at least one of PUSCH repetitions, in accordance with aspects of the disclosure.

Fig. 9A is a communication flow illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on a cDAI and tDAI when the UE is configured to multiplex one or more late arriving DL grants with at least one of the PUSCH repetitions but not perform a cDAI and tDAI check between the early arriving DL grant and the late arriving DL grant, in accordance with aspects of the present disclosure.

Fig. 9B is a communication flow illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on a cDAI and tDAI when the UE is configured to multiplex one or more late arriving DL grants with at least one of the PUSCH repetitions but not perform a cDAI and tDAI check between the early arriving DL grant and the late arriving DL grant, in accordance with aspects of the present disclosure.

Fig. 10 is a schematic diagram illustrating an example of multiplexing a late arriving DL grant with at least one of a second PUSCH repetition and a subsequent PUSCH repetition in accordance with aspects of the present disclosure.

Fig. 11 is a flow chart of a method of wireless communication in accordance with aspects presented herein.

Fig. 12 is a flow chart of a method of wireless communication in accordance with aspects presented herein.

Fig. 13 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

Fig. 14 is a flow chart of a method of wireless communication in accordance with aspects presented herein.

Fig. 15 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus in accordance with aspects presented herein.

Detailed Description

The various configurations are described below in connection with the detailed description set forth in the drawings, and are not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Aspects of a telecommunications system are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

For example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics Processing Units (GPUs), central Processing Units (CPUs), application processors, digital Signal Processors (DSPs), reduced Instruction Set Computing (RISC) processors, system on a chip (SoC), baseband processors, field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system may execute the software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example aspects, implementations, and/or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or code. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

Although aspects, implementations, and/or use cases have been described in this disclosure by way of illustration of some examples, additional or different aspects, implementations, and/or use cases may occur in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may result from integrated chip implementations and other non-module component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial devices, retail/purchase devices, medical devices, artificial Intelligence (AI) enabled devices, etc.). While some examples may or may not be specific to use cases or applications, there may be a wide range of applicability of the described examples. Aspects, implementations, and/or use cases may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to an aggregate, distributed, or Original Equipment Manufacturer (OEM) device or system incorporating one or more techniques herein. In some practical arrangements, devices incorporating the described aspects and features may also include additional components and features for implementation and implementation of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes a plurality of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/adders, etc.). The techniques described herein may be implemented in various devices, chip-level components, systems, distributed arrangements, aggregated or disassembled components, end-user devices, and the like having different sizes, shapes, and configurations.

Deployment of a communication system, such as a 5G NR system, may be arranged in a variety of ways with various components or parts. In a 5GNR system or network, network nodes, network entities, mobility elements of the network, radio Access Network (RAN) nodes, core network nodes, network elements, or network devices, such as a Base Station (BS) or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or decomposed architecture. For example, BSs, such as Node BS (NB), evolved NB (eNB), NR BS, 5G NB, access Points (APs), transmission and Reception Points (TRP), cells, or the like, may be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a decomposed base station.

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. An decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or Centralized Units (CUs), one or more Distributed Units (DUs), or one or more Radio Units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as virtual units (i.e., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs)).

Base station operation or network design may take into account the aggregate nature of the base station functionality. For example, the split base station may be utilized in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration sponsored by the O-RAN alliance), or a virtual radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)). The decomposition may include distributing functionality across two or more units at various physical locations, and virtually distributing functionality for at least one unit, which may enable flexibility in network design. The individual units of the split base station or the split RAN architecture may be configured for wired or wireless communication with at least one other unit.

Fig. 1 is a schematic diagram 100 illustrating an example of a wireless communication system and an access network. The wireless communication system shown includes an exploded base station architecture. The split base station architecture may include one or more CUs 210 that may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near real-time (near RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non RT) RIC 115 associated with the Service Management and Orchestration (SMO) framework 105, or both. CU 110 may communicate with one or more DUs 130 via a corresponding medium range link, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective forward links. RU 140 may communicate with corresponding UEs 104 via one or more Radio Frequency (RF) access links. In some implementations, the UE 104 may be served by multiple RUs 140 simultaneously.

Each of these units (i.e., CU 110, DU 130, RU 140) and near RT RIC 125, non-RT RIC 115, and SMO framework 105 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller that provides instructions to a communication interface of these units, may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals over a wired transmission medium or to transmit signals to one or more of the other units. In addition, the units may include a wireless interface (which may include a receiver, transmitter, or transceiver (such as an RF transceiver)) configured to receive signals over a wireless transmission medium, to transmit signals to one or more of the other units, or both.

In some aspects, CU 110 may host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), packet Data Convergence Protocol (PDCP), service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bi-directionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. CU 110 may be implemented to communicate with DU 130 as needed for network control and signaling.

DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, depending at least in part on the functional split (such as defined by 3 GPP), DU 130 can host one or more of the following: a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for Forward Error Correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.). In some aspects, the DU 130 may also host one or more lower PHY layers. Each layer (or module) may be implemented with interfaces configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

The lower layer functionality may be implemented by one or more RUs 140. In some deployments, RU 140 controlled by DU 130 may correspond to a logical node hosting: RF processing functions or low PHY layer functions such as performing Fast Fourier Transforms (FFTs), inverse FFTs (iffts), digital beamforming, physical Random Access Channel (PRACH) extraction and filtering, etc., or both. In such an architecture, RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, the real-time and non-real-time aspects of control and user plane communications with RU 140 may be controlled by the corresponding DU 130. In some scenarios, such a configuration may enable DUs 130 and CUs 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, SMO framework 105 may be configured to interact with a Cloud computing platform, such as open Cloud (O-Cloud) 190, via a Cloud computing platform interface, such as an O2 interface, to perform network element lifecycle management, such as instantiating the virtualized network elements. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near RT RIC 125. In some implementations, SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as open eNB (O-eNB) 111, via an O1 interface. Further, in some implementations SMO framework 105 may communicate directly with one or more RUs 140 via an O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

non-RT RIC 115 may be configured to include the following logic functions: the logic functions enable non-real-time control and optimization of RAN elements and resources, artificial Intelligence (AI)/Machine Learning (ML) (AI/ML) workflow (including model training and updating), or policy-based guidance of applications/features in near RT RIC 125. non-RT RIC 115 may be coupled to near RT RIC 125 or in communication with near RT RIC 125 (such as via an A1 interface). Near RT RIC 125 may be configured to include the following logic functions: the logic functions enable near real-time control and optimization of RAN elements and resources via data collection and actions over interfaces (such as via E2 interfaces) connecting one or more CUs 110, one or more DUs 130, or both, and O-enbs with near RT RIC 125.

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

At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). The base station 102 provides an access point for the UE 104 to the core network 120. Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network comprising both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include home evolved node B (eNB) (HeNB) and the HeNB may provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link between RU 140 and UE 104 may include Uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to RU 140 and/or Downlink (DL) (also referred to as a forward link) transmissions from RU 140 to UE 104. The communication links may use multiple-input multiple-output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may be through one or more carriers. The base station 102/UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) bandwidth per carrier allocated in carrier aggregation up to a total yxmhz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

Aspects presented herein may improve the efficiency of HARQ feedback mechanisms and radio resource usage by providing looser/softer timeline constraints for HARQ-ACK/NACK multiplexing on PUSCH. Aspects presented herein may enable a UE to multiplex HARQ-ACK/NACK bits of a DL grant (e.g., a late arriving DL grant) arriving after an uplink grant with one or more PUSCH repetitions and determine a correct HARQ codebook size for the received DL grant based at least in part on a cDAI/tDAI associated with the DL grant and/or UL grant.

In certain aspects, the UE 104 may include a HARQ codebook determination component 198 configured to monitor DL grants arriving before and after the UL grant and perform a cDAI and/or tDAI check on the DL grant to determine the correct HARQ codebook size for the DL grant. In one configuration, HARQ codebook determination component 198 may be configured to receive at least one DL grant from a base station after receiving a UL grant, the at least one DL grant associated with a DL cDAI value and a DL tDAI value, the UL grant associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions. In such a configuration, HARQ codebook determination component 198 may calculate the total number of DL grants sent to the UE based on the received DL cDAI value. In such a configuration, the HARQ codebook determination component 198 may adjust the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value. In such a configuration, the HARQ codebook determination component 198 may transmit a HARQ codebook to the base station in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on the total number of adjusted DL grants.

In certain aspects, base station 102 can include a tDAI/cDAI configuration component 199 configured to determine a value of tDAI/cDAI associated with a DL grant sent prior to a UL grant and a DL grant sent after the UL grant. In one configuration, the tDAI/cDAI configuration component 199 may be configured to transmit at least one DL grant associated with a DL cDAI value and a DL tDAI value to the UE after transmitting the UL grant associated with the UL tDAI value and scheduling multiple PUSCH repetitions. In such a configuration, the tDAI/cDAI configuration component 199 may receive a HARQ codebook from the UE in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value.

Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL Wireless Wide Area Network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels such as a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), and a Physical Sidelink Control Channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems such as, for example, bluetooth, wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communication system may also include a Wi-Fi AP150 that communicates with the UE 104 (also referred to as a Wi-Fi Station (STA)) via a communication link 154 in, for example, a 5GHz unlicensed spectrum or the like. When communicating in the unlicensed spectrum, the UE 104/AP 150 may perform Clear Channel Assessment (CCA) prior to communicating in order to determine whether a channel is available.

The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). 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 problems sometimes occur with respect to FR2, which is commonly (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it is different from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band of these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency band falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, if the term is used herein, "below 6GHz" or the like may broadly represent frequencies that may be less than 6GHz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless specifically stated otherwise, the term "millimeter wave" or the like, if used herein, may broadly refer to frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4, FR2-2, and/or FR5, or frequencies that may be within the EHF band.

Base station 102 and UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and/or antenna arrays) to facilitate beamforming. The base station 102 may transmit the beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signals in one or more receive directions from the base station 102. The UE 104 may also transmit the beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signals from the UEs 104 in one or more receive directions. The base station 102/UE 104 may perform beam training to determine the best reception and transmission direction for each of the base stations 102/UE 104. The transmit direction and the receive direction for the base station 102 may be the same or may be different. The transmit direction and the receive direction for the UE 104 may be the same or may be different.

The base station 102 may include and/or be referred to as a gNB, a node B, eNB, an access point, a base station transceiver, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a transmit-receive point (TRP), a network node, a network entity, a network device, or some other suitable terminology. Base station 102 may be implemented as an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with baseband units (BBUs) (including CUs and DUs) and RUs, or as an decomposed base station including one or more of CUs, DUs, and/or RUs. The set of base stations, which may include the decomposed base stations and/or the aggregated base stations, may be referred to as a Next Generation (NG) RAN (NG-RAN).

The core network 120 may include access and mobility management functions (AMFs) 161, session Management Functions (SMFs) 162, user Plane Functions (UPFs) 163, unified Data Management (UDMs) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identification processing, access authorization, and subscription management. One or more location servers 168 are shown as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. In general, however, the one or more location servers 168 may include one or more location/positioning servers that may include one or more of a GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), and the like. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional velocity calculation based on the measurements. Signal measurements may be made by the UE 104 and/or the serving base station 102. The measured signals may be based on Satellite Positioning System (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global Positioning System (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless Local Area Network (WLAN) signals, bluetooth signals, terrestrial Beacon Systems (TBS), sensor-based information (e.g., barometric sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multiple round trip times (multiple RTTs), DL transmission angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and/or other systems/signals/sensors.

Examples of UEs 104 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electricity meter, an air pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similarly functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, cardiac monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and/or individually.

Fig. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Fig. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Fig. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Fig. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be Frequency Division Duplex (FDD) (where subframes within a subcarrier set are dedicated to DL or UL for a particular subcarrier set (carrier system bandwidth)) or Time Division Duplex (TDD) (where subframes within a subcarrier set are dedicated to both DL and UL for a particular subcarrier set (carrier system bandwidth). In the example provided by fig. 2A, 2C, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexibly usable between DL/UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3, 4 are shown as having slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. The slot formats 0, 1 are full DL, full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically configured by DL Control Information (DCI) or semi-statically/statically configured by Radio Resource Control (RRC) signaling) through a received Slot Format Indicator (SFI). Note that the following description also applies to a 5G NR frame structure that is TDD.

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. The subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the Cyclic Prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. The symbols on DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) -spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on CP and digital scheme (numerology). The digital scheme defines a subcarrier spacing (SCS) and in practice defines a symbol length/duration (which may be equal to 1/SCS).

μ	SCSΔf＝2 μ ·15[kHz]	Cyclic prefix
			0	15	General
1	30	General
			2	60	General, extension
3	120	General
			4	240	General

For a normal CP (14 symbols/slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8 and 16 slots, respectively, per subframe. For extended CP, digital scheme 2 allows 4 slots per subframe. Accordingly, for the normal CP and digital scheme μ, there are 14 symbols/slot and 2 ^μ Each slot/subframe. The subcarrier spacing may be equal to 2 ^μ *15kHz, where μ is the digital schemes 0 through 4. Thus, the digital scheme μ=0 has a subcarrier spacing of 15kHz, and the digital scheme μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. Fig. 2A-2D provide examples of a normal CP (with 14 symbols per slot) and a digital scheme μ=2 (with 4 slots per subframe). The slot duration is 0.25ms, the subcarrier spacing is 60kHz and the symbol duration is approximately 16.67 mus. Within the frame set, there may be one or more different bandwidth portions (BWP) of the frequency division multiplexing (see fig. 2B). Each BWP may have a specific digital scheme and CP (normal or extended).

The resource grid may be used to represent a frame structure. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)), which include 12 consecutive subcarriers. The resource grid is divided into a plurality of Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As shown in fig. 2A, some of the REs carry a reference (pilot) signal (RS) for the UE. The RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs may also include beam measurement RSs (BRSs), beam Refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

Fig. 2B shows an example of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in one OFDM symbol of an RB. The PDCCH within one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion on CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWP may be located at a larger and/or lower frequency across the channel bandwidth. The Primary Synchronization Signal (PSS) may be within symbol 2 of a particular subframe of a frame. PSS is used by the UE 104 to determine subframe/symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and a System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not transmitted over the PBCH, and paging messages.

As shown in fig. 2C, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RS for a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS may be transmitted in the previous or two symbols of PUSCH. The PUCCH DM-RS may be transmitted in different configurations according to whether a short PUCCH or a long PUCCH is transmitted and according to a specific PUCCH format used. The UE may transmit a Sounding Reference Signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency dependent scheduling on the UL.

Fig. 2D shows examples of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries Uplink Control Information (UCI) such as a scheduling request, a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indicator (RI), and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and/or Negative ACKs (NACKs)). PUSCH carries data and may additionally be used to carry Buffer Status Reports (BSR), power Headroom Reports (PHR), and/or UCI.

Fig. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In DL, internet Protocol (IP) packets may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. Controller/processor 375 provides: RRC layer functions associated with: broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with: header compression/decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper layer Packet Data Units (PDUs), error correction by ARQ, concatenation of RLC Service Data Units (SDUs), segmentation and reassembly, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto Transport Blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel prioritization.

The Transmit (TX) processor 316 and the Receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, which includes a Physical (PHY) layer, may include error detection of a transmission channel, forward Error Correction (FEC) encoding/decoding of the transmission channel, interleaving, rate matching, mapping onto a physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying the time domain OFDM symbol stream. The OFDM streams are spatially precoded to produce a plurality of spatial streams. The channel estimates from the channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. The channel estimate may be derived from reference signals and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 Tx. Each transmitter 318Tx may modulate a Radio Frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (Rx) processor 356.TX processor 368 and RX processor 356 implement layer 1 functions associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by the RX processor 356. RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functions.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. Memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with DL transmissions by the base station 310, the controller/processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and measurement report; PDCP layer functions associated with: header compression/decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper layer PDUs, error correction by ARQ, concatenation of RLC SDUs, segmentation and reassembly, re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority handling and logical channel prioritization.

Channel estimates derived by channel estimator 358 from reference signals or feedback transmitted by base station 310 may be used by TX processor 368 to select appropriate coding and modulation schemes, as well as to facilitate spatial processing. The spatial streams generated by Tx processor 368 may be provided to different antenna 352 via separate transmitters 354 Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

UL transmissions are handled at the base station 310 in a similar manner as described in connection with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the Rx processor 370.

The controller/processor 375 may be associated with a memory 376 that stores program codes and data. Memory 376 may be referred to as a computer-readable medium. In the UL, controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. Controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

At least one of TX processor 368, RX processor 356, and controller/processor 359 may be configured to perform various aspects related to HARQ codebook determination component 198 of fig. 1.

At least one of TX processor 316, RX processor 370, and controller/processor 375 may be configured to perform various aspects related to tDAI/cDAI configuration component 199 of fig. 1.

The base station or a component of the base station (e.g., CU/RU/DU) may configure the UE to send hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement (ACK) or Negative ACK (NACK)) for one or more Downlink (DL) transmissions (e.g., physical Downlink Shared Channel (PDSCH)). For example, the base station may schedule a plurality of PDSCH to be transmitted to the UE, and the base station may request the UE to provide HARQ feedback for the plurality of PDSCH based on a decoding status of the plurality of PDSCH by the UE. If the UE successfully decodes the PDSCH, the UE may indicate HARQ-ACK for the PDSCH, and if the UE does not successfully decode the PDSCH, the UE may indicate HARQ-NACK for the PDSCH. The UE may then send HARQ feedback (e.g., in a HARQ codebook) for the multiple PDSCH to the base station via Uplink Control Information (UCI). The UE may multiplex UCI with a Physical Uplink Control Channel (PUCCH), e.g., the UE may transmit UCI as a payload via the PUCCH. If the PUCCH overlaps with a Physical Uplink Shared Channel (PUSCH), UCI and PUCCH may be included as part of PUSCH, e.g., the UE may transmit UCI/PUCCH as a payload via PUSCH.

In some examples, for a UE to transmit UCI via PUSCH (e.g., multiplex HARQ feedback/HARQ codebook with PUSCH), the UE may be configured to apply or follow a set of rules/restrictions. For example, in some configurations, a UE may multiplex HARQ-ACK/NACK bits with a PUSCH if a Downlink (DL) grant corresponding to the HARQ-ACK/NACK bits (e.g., a DL grant scheduling a PDSCH to be provided with HARQ feedback) arrives before an Uplink (UL) grant scheduling a PUSCH (e.g., a UL grant providing resources for PUSCH transmission to the UE). However, if a DL grant corresponding to the HARQ-ACK/NACK bit arrives after the UL grant of the scheduled PUSCH, the UE may not multiplex the HARQ-ACK/NACK bit with the PUSCH. In another example, the UE may not desire to detect a DCI format that schedules PDSCH reception or semi-persistent scheduling (SPS) PDSCH release, or a DCI format 1_1 that indicates secondary cell (SCell) dormancy, or a DCI format that includes a single HARQ-ACK request field with a value of one (1), on the condition that all DL grants arrive before the UL grant, and if the UE previously detected a DCI format that schedules PUSCH transmission in a slot, and if the UE multiplexes HARQ-ACK information in a PUSCH transmission, the DCI format indicates resources for PUCCH transmission and corresponding HARQ-ACK information in the slot. Such configuration/restriction may increase the latency of HARQ-ACK/NACK multiplexing, for example, when the number of PUSCH repetitions increases, and may exclude multiplexing that spans PUSCH repetitions.

Fig. 4 is a diagram 400 illustrating an example in which a UE multiplexes HARQ-ACK/NACK bits for DL grants received prior to receiving an UL grant scheduling PUSCH (but not for DL grants received after receiving an UL grant) with PUSCH in accordance with aspects of the present disclosure. In one example, UE 401 may be configured with a Time Division Duplex (TDD) slot pattern 402, which may include four (4) consecutive DL slots followed by UL slots. As shown at 405, UE 401 may transmit a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH) to base station 403 or a component of base station 403 (may be referred to hereinafter as a "network node/entity") during a UL slot, and UE 401 may receive a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH) from base station 403 during a DL slot. For example, as shown at 404 and 408, during one or more DL slots, UE 401 may receive one or more DL grants scheduling one or more PDSCH from base station 403, wherein the one or more DL grants may be carried in PDCCH. Each DL grant may be associated with a Downlink Control Information (DCI) format. For purposes of this disclosure, a "DL grant" may also be referred to as a "PDSCH grant" and a "UL grant" may also be referred to as a "PUSCH grant.

For example, as shown at 404, UE 401 may receive three PDSCH grants 406 from base station 403 (e.g., at slots 00, 01, and 02), and as shown at 408, UE 401 may receive another three PDSCH grants 410 from base station 403 (e.g., at slots 05, 06, and 07). As shown at 412, UE 401 may also receive a PDCCH in a DL slot (e.g., at slot 03) that carries a PUSCH grant 414 (e.g., in an uplink DCI). PUSCH grant 414 may indicate a PUSCH transmission constituting a total of four (4) PUSCH repetitions scheduled to be transmitted via four UL slots (e.g., at slots 04, 09, 14, and 19), which may be associated with PUCCHs 416, 418, 420, and 422, respectively. As shown in diagram 400, UE 401 may receive PDSCH grant 406 before receiving PUSCH grant 414, and UE 401 may receive PDSCH grant 410 after receiving PUSCH grant 414. For purposes of this disclosure, DL grant to a UE before an UL grant may be referred to as an "early-arrival grant", "early-arrival DL grant", and/or "early-arrival PDSCH grant", while DL grant to a UE after an UL grant may be referred to as a "late-arrival grant", "late-arrival DL grant", and/or "late-arrival PDSCH grant". For example, because PDSCH grant 406 arrives at UE 401 before PUSCH grant 414, PDSCH grant 406 may be referred to as an early-arriving grant, an early-arriving DL grant, and/or an early-arriving PDSCH grant. On the other hand, since PDSCH grant 410 arrives at UE 401 after PUSCH grant 414, PDSCH grant 410 may be referred to as a late arrival grant, a late arrival DL grant, and/or a late arrival PDSCH grant, etc.

After UE 401 receives one or more DL grants from base station 403, based on the detection and decoding status of the one or more DL grants (e.g., the decoding status of PDSCH scheduled by the DL grant), UE 401 may provide HARQ feedback for the DL grant to base station 403 indicating whether the DL grant (e.g., its associated PDSCH) has been successfully decoded or not successfully decoded by UE 401. For example, each DL grant may correspond to a HARQ-ACK bit or a HARQ-NACK bit in the HARQ feedback, and then UE 401 may map the HARQ feedback to one or more PUCCHs scheduled by the base station in the UL grant. In some examples, the HARQ feedback may also be referred to as a HARQ codebook, a HARQ feedback codebook, and/or a HARQ-ACK/NACK codebook, etc. Thus, for purposes of this disclosure, the term "HARQ feedback" may be used interchangeably with "HARQ codebook", "HARQ feedback codebook", and/or "HARQ-ACK/NACK codebook"

In one example, if UE 401 is configured to multiplex HARQ-ACK/NACK bits for early-arriving DL grants and not for late-arriving DL grants with PUSCH or PUSCH repetition, UE 401 may multiplex HARQ-ACK/NACK bits associated with PDSCH grant 406 with at least one of PUCCHs 416, 418, 420, and 422. For example, as shown at 424, UE 401 may multiplex HARQ-ACK/NACK bits associated with PDSCH grant 406 with PUCCH 416 because PDSCH grant 406 was received by UE 401 before PUSCH grant 414 was received, where PUCCH 416 may overlap with the corresponding PUSCH/PUSCH repetition (e.g., at slot 04). In other words, the HARQ-ACK/NACK bits associated with PDSCH grant 406 may be multiplexed with at least one PUSCH/PUSCH repetition scheduled by PUSCH grant 414. However, UE 401 may not multiplex the HARQ-ACK/NACK bits associated with PDSCH grant 410 with PUCCHs 416, 418, 420, and/or 422 because PDSCH grant 410 is received by UE 401 after PUSCH grant 414 is received. In such an example, UE 401 may be configured to multiplex HARQ-ACK/NACK bits associated with PDSCH grant 410 (e.g., late-arriving DL grant) with PUSCH/PUSCH repetition that PUSCH grant 414 is not scheduled. For example, as shown at 424, UE 401 may multiplex HARQ-ACK/NACK bits associated with PDSCH grant 410 to PUSCH/PUSCH repetition at slot 24 (e.g., after UE 401 transmits the PUSCH repetition scheduled by PUSCH grant 414). In other words, the HARQ-ACK/ACK bits of PDSCH grant 406 may be multiplexed with PUSCH in slot 04, but the remaining three HARQ-ACK/NACK bits of PDSCH grant 410 may be deferred until four PUSCH repetitions (e.g., at slots 04, 09, 14, and 19) are completed. Thus, there may be a long delay between the reception of PDSCH grants 410 (e.g., at slots 05, 06, and 07) and the transmission of their corresponding HARQ feedback (e.g., at slot 24). If the PUSCH repetition number increases (e.g., to 8 repetitions, 16 repetitions, 32 repetitions, etc.), the delay may further increase and result in a longer delay for HARQ feedback.

Each PDSCH grant (e.g., PDSCH grant 406, 410) transmitted from the base station or component of the base station to the UE may include at least one of a current downlink assignment index (cDAI) parameter or a total downlink assignment index (tDAI) parameter. The value indicated by the cDAI parameter may provide an accumulated count of the number of PDSCH grants sent to the UE up to that point, and the tDAI parameter may provide a total count of PDSCH grants sent to the UE up to that point. In some examples, the tDAI parameter in a PDSCH grant may be used in the context of carrier aggregation. For example, if multiple carriers are activated in the DL and the UE is configured to receive PDSCH via the multiple carriers, the tDAI parameter and/or the cDAI parameter in the PDSCH grant may enable the UE to determine the total number of PDSCH grants that the UE may receive across the multiple carriers or be scheduled to receive across the multiple carriers. In some examples, if the UE is communicating with a single carrier, the DL grant may include a cDAI parameter and not a tDAI parameter.

Similarly, a PUSCH grant (e.g., PUSCH grant 414) may also include a tDAI parameter, which may enable the UE to determine the total number of PDSCH grants (e.g., sent by the base station) up to that point (e.g., the point at which the UE received the PUSCH grant). Then, based on the determined total number of PDSCH grants, the UE may determine a size of a HARQ codebook to be transmitted to the base station, the HARQ codebook carrying HARQ-ACK/NACK bits of the PDSCH grant. In other words, since each PDSCH quasi-grant may correspond to HARQ-ACK/NACK bits, the UE may determine the HARQ codebook size to be transmitted back to the base station (e.g., to be multiplexed with PUSCH/PUCCH) based on the total number of PDSCH grants determined/counted by the UE. In this way, the base station may use the tDAI parameter in the PUSCH grant to indicate to the UE that the base station expects the UE to transmit a HARQ codebook (e.g., HARQ feedback) having a HARQ codebook size corresponding to the tDAI parameter.

For example, the cDAI parameter and tDAI parameter may each be a two-bit field (e.g., representing four values: 0, 1, 2, 3, etc.). In such examples, the value indicated by the cDAI parameter and/or tDAI parameter may not be an absolute value of the HARQ-ACK/NACK bits (e.g., the base station's expected HARQ codebook size), but may be a modulus of the value of the HARQ-ACK/NACK bits. In other words, the cDAI parameter and tDAI parameter may be two-bit fields following modulo logic, wherein if the number of PDSCH grants is indicated to exceed four (4) (e.g., exceed a maximum value (three) that may be represented by the two-bit field), the number may be counted. For example, if the total number of PDSCH grants is seven (7) (e.g., HARQ codebook size is seven), it may be indicated as three (3) by the tDAI parameter or the cDAI parameter, e.g., 7mod4=3. Thus, if the tDAI parameter indicates a value of X (e.g., x=0, 1, 2, 3), the value may correspond to any value of X that results in X mod 4=3. For example, if the tDAI parameter indicates a value of three (3), it may correspond to three (3), seven (7), eleven (11), or fifteen (15) bits, etc. (e.g., corresponding to an actual HARQ codebook size). If the tDAI parameter indicates a value of two (2), it may correspond to two (2), six (6), ten (10), fourteen (14) bits, and so on.

In other words, when the UE is configured to multiplex HARQ-ACK/NACK payloads (e.g., HARQ codebooks) with PUSCH/PUSCH repetitions, the UE may use the tDAI parameters carried in the UL grant to determine a set of possible HARQ codebook sizes. For example, if tdai=3, the possible HARQ codebook size may be one of 3, 7, 11, 15, … bits, etc. The UE may then determine/select an actual or appropriate codebook size from the set of possible HARQ codebook sizes (e.g., 3/7/11/15/… bits) based on the cDAI parameters in the DL/PDSCH grant. Since the UE may be configured to track the cDAI carried in the DL grant, the UE may use the cDAI parameters associated with the DL grant to uniquely determine the HARQ codebook size from the set of possible HARQ codebook sizes.

For example, referring back to fig. 4, ue 401 may track the number of PDSCH grants received based on its associated cDAI value. As one example, the three PDSCH grants 406 may include the cDAI counters 0, 1, 2, and the three PDSCH grants 410 may include the cDAI counters 3, 0, 1. Thus, UE 401 may count a total of six (6) PDSCH grants. UE 401 may then be configured to round the counted value to the closest HARQ codebook size from the set of possible HARQ codebook sizes (e.g., the closest codebook size capable of carrying all HARQ-ACK/NACK bits for the counted PDSCH grant). For example, if UE 401 counts a total of six (6) PDSCH grants (e.g., HARQ-ACK/NACK bits = 6), and the possible HARQ codebook sizes are three (3), seven (7), eleven (11), fifteen (15) bits, etc., then UE 401 may select seven bits for the HARQ codebook size (because seven bits are the closest bits that may carry six HARQ-ACK/NACK bits). Based on the selected HARQ codebook size (e.g., seven bits), UE 401 may send HARQ feedback/codebook with the selected HARQ codebook size to base station 403, where UE 401 may include padding/pseudocode for the additional bits. For example, since six PDSCH grants may correspond to six HARQ-ACK/NACK bits, but the HARQ codebook determined by UE 401 is seven bits, UE 401 may add one dummy/padding bit to the six HARQ ACK/NACK bits.

Although the base station's expected HARQ codebook size is configured to match the HARQ codebook size determined by the UE based on the tDAI parameter in the UL grant and the cDAI parameter in the one or more DL grants, ambiguity may occur if the UE fails to receive the one or more DL grants from the base station. In some examples, if the UE fails to receive a small number of DL grants (e.g., one or two DL grants, etc.), the UE is able to detect a lost DL grant based on the cDAI parameters associated with the received DL grant. For example, if the cDAI parameters of the three received PDSCH grants correspond to 0, 2, and 3, the UE may determine that a PDSCH grant may be lost therebetween (e.g., a PDSCH grant with cdai=1). If the cDAI parameters of the two received PDSCH grants correspond to 0 and 3, the UE may determine that two PDSCH grants may be lost therebetween (e.g., PDSCH grants with cdai=1 and cdai=2). In some examples, if the UE detects one or more lost PDSCH grants, the UE may be configured to insert padding/dummy bits for the one or more PDSCH grants (e.g., for the lost cDAI) so that the UE and the base station may remain synchronized (e.g., have consistent determination/calculation for HARQ codebook size).

In some examples, the UE may not be able to detect when one or more PDSCH grants are lost. In one example, if the UE fails to receive the last DL grant to be mapped to the PUCCH, the UE may not detect the last DL grant loss. For example, the base station may send eight (8) DL grants to the UE, where the cDAI parameters associated with the eight DL grants may correspond to: 0. 1,2, 3, 0, 1,2, 3. However, if the UE fails to receive the last DL grant (e.g., a DL grant with cdai=3), the UE may determine that there are seven total DL grants based on the cDAI parameters associated with the first seven received DL grants (e.g., the cDAI parameters in the first seven DL grants are 0, 1,2, 3, 0, 1,2 in the correct order of counting). As such, ambiguity regarding the HARQ codebook size may occur between the UE and the base station because the base station may expect an eight-bit HARQ codebook size and the UE may determine a seven-bit HARQ codebook size. In such an example, the UE is still able to determine/select the correct HARQ codebook size based on the tDAI parameter in the UL grant, e.g., by rounding the counted PDSCH grant to the closest codebook size selected from a set of possible codebook sizes associated with the tDAI parameter when the base station configures the tDAI parameter. For example, if the tDAI parameter indicates a value of zero (0), it may correspond to one of four (4), eight (8), twelve (12) bits, etc. possible HARQ codebook sizes. Since the UE may round the value of the count (e.g., the counted DL grant) to the closest HARQ codebook size (e.g., eight bits) from the set of possible HARQ codebook sizes, the HARQ codebook sizes expected by the base station and determined by the UE may still match after the UE rounds the value of the count.

However, in some examples, if the UE loses more than four consecutive DL grants, the UE may not be able to detect and correct the lost DL grant. For example, the base station may send eight (8) DL grants to the UE, where the cDAI parameters associated with the eight DL grants may correspond to: 0. 1, 2, 3, 0, 1, 2, 3. However, if the UE fails to receive the last four DL grants, the UE may determine that there are a total of four DL grants based on the cDAI parameters (e.g., 0, 1, 2, 3) associated with the first four DL grants received. In such an example, the UE may not be able to determine the correct codebook size based on the tDAI parameter in the UL grant. For example, if the tDAI parameter indicates a value of zero (0) corresponding to one of four (4), eight (8), twelve (12) bits, etc., the UE may determine that the codebook size is four bits instead of eight bits. In this context, the UE may be configured not to use the tDAI parameters in the DL grant because the tDAI parameters in the UL grant may be prioritized. For example, referring back to fig. 4, the tDAI parameters in the PUSCH grant 414 may include more updated information than the tDAI parameters in the last DL grant of the PDSCH grant 406 because the PDSCH grant 406 was received prior to the PUSCH grant 414. Thus, UE 401 may be configured to not rely on the tDAI parameter in the DL grant in determining the number of received DL grants and/or HARQ codebook size.

In some examples, the tDAI parameter carried by the UL grant may apply to all repetitions scheduled by the UL grant. For example, if PUSCH transmission over a plurality of slots is scheduled by a DCI format including a DAI field, a value of the DAI field may be suitable for multiplexing HARQ-ACK information in PUSCH transmission in any slot from the plurality of slots in which the UE multiplexes HARQ-ACK information.

Fig. 5 is a diagram 500 illustrating an example of a UE configured to apply tDAI parameters carried by UL grants to all repetitions scheduled by UL grants in accordance with aspects of the disclosure. As shown at 502, the UE may receive a total of five (5) PDSCH grants before receiving PUSCH grant 504, where three PDSCH grants 506 may be received at slots 00, 01, and 02, and two PDSCH grants 508 may be received at slots 06 and 07. PUSCH grant 504 may indicate a PUSCH transmission constituting a total of four (4) PUSCH repetitions scheduled to be transmitted at slots 09, 14, 19, and 24, and PUSCH grant 504 may also include tDAI parameter 510 to be applied to these four repetitions. In one example, if the tDAI parameter 510 is configured to be three (3) (e.g., tdai=3), the UE may send three HARQ-ACK/NACK bits in each UL slot. For example, as shown at 512, the UE may multiplex the three HARQ-ACK/NACK bits for PDSCH grant 506 with PUCCH 514 (e.g., with PUSCH repetition) to be transmitted at slot 09. Similarly, as shown at 516, the UE may multiplex HARQ-ACK/NACK bits for PDSCH grant 508 with PUCCH 518 to be transmitted at slot 14. However, although the HARQ-ACK/NACK bits for PDSCH grant 508 may be two (2) bits, because there are two PDSCH grants, the UE may be configured to stuff additional dummy bits into two HARQ-ACK/NACK bits (e.g., now three HARQ-ACK/NACK bits in total) such that the size of the HARQ-ACK/NACK matches the value indicated by tDAI parameter 510 (e.g., three). In other words, even though the UE has received two actual DL grants, the uplink tDAI indicates three, so the UE may be configured to determine the HARQ codebook size as three (3) bits and fill in additional dummy bits. Thus, if the tDAI parameter 510 is configured to apply to all repetitions scheduled by the PUSCH grant 504, it may sometimes result in inefficient use of radio resources when the actual PDSCH grant received by the UE is less than the value indicated by the tDAI parameter 510.

Aspects presented herein may improve the efficiency of HARQ feedback mechanisms and radio resource usage by providing looser/softer timeline constraints for HARQ-ACK/NACK multiplexing on PUSCH. For example, the UE may be configured to repeatedly multiplex HARQ-ACK/NACK bits of DL grant arriving after an uplink grant with PUSCH while keeping track of tDAI.

Fig. 6 is a diagram 600 illustrating an example in which a UE multiplexes HARQ-ACK/NACK bits of a late arriving DL grant (e.g., a DL grant arriving after an uplink grant) with at least one PUSCH repetition, in accordance with aspects of the present disclosure. In one example, the UE 601 may be configured with a TDD slot mode 602, and the TDD slot mode 602 may include four (4) consecutive DL slots followed by a UL slot. As shown at 605, UE 601 may transmit PUCCH and/or PUSCH to base station 603 (or a component or network node/entity of base station 603) during a UL slot, and UE 601 may receive PDCCH and/or PDSCH from base station 603 during a DL slot.

As shown at 604 and 608, during a DL slot, UE 601 may receive one or more DL grants from base station 603, wherein the one or more DL grants may be carried in a PDCCH and each DL grant may be associated with a DCI format. For example, at 604, UE 601 may receive three PDSCH grants 606 from base station 603, and at 608, UE 601 may receive two PDSCH grants 610 from base station 603. At 612, UE 601 may receive a PDCCH including a PUSCH grant 614 in a DL slot (e.g., at slot 03). PUSCH grant 614 may indicate a PUSCH transmission constituting a total of four (4) PUSCH repetitions scheduled to be transmitted at slots 04, 09, 14, and 19, which may be associated with PUCCHs 616, 618, 620, and 622, respectively. PUCCHs 616, 618, 620, and 622 may also correspond to or overlap with the first PUSCH repetition, the second PUSCH repetition, the third PUSCH repetition, and the fourth PUSCH repetition, respectively. As shown in diagram 600, UE 601 may receive PUSCH grant 614 after receiving PDSCH grant 606 but before receiving PDSCH grant 610. Thus, PDSCH grant 606 may be an early-arriving DL grant and PDSCH grant 610 may be a late-arriving DL grant. Based on the detection and decoding of PDSCH grants, the UE 601 may provide HARQ feedback for the corresponding PDSCH grant, e.g., as described in connection with fig. 4.

In one aspect of the disclosure, for a first PUSCH repetition scheduled by PUSCH grant 614 (e.g., a first PUSCH repetition to be transmitted at slot 04), UE 601 may be configured to multiplex HARQ-ACK/NACK bits of an early arriving DL grant (but not for a late arriving DL grant) with the first PUSCH, e.g., as described in connection with fig. 4. For example, at slot 04, UE 601 may multiplex HARQ-ACK/NACK bits of PDSCH grant 606 with the first PUSCH repetition associated with PUCCH 616 because PDSCH grant 606 was received before PUSCH grant 614. However, if the PDSCH grant is received after the PUSCH grant 614, the UE 601 may not multiplex HARQ-ACK/NACK bits of the PDSCH grant with the first PUSCH repetition. For example, if UE 601 receives PUSCH grant 614 at slot 02 and three PDSCH grants at slots 00, 01, and 03, then UE 601 may multiplex HARQ-ACK/NACK bits of the PDSCH grant received at slots 00 and 01 with the first PUSCH repetition, but UE 601 may not multiplex HARQ-ACK/NACK bits of the PDSCH grant received at slot 03 with the first PUSCH repetition.

Then, for second PUSCH repetitions and subsequent PUSCH repetitions, such as second PUSCH repetitions, third PUSCH repetitions, and fourth PUSCH repetitions associated with PUCCHs 618, 620, and 622, UE 601 may be configured to multiplex HARQ-ACK/NACK bits of an early-arriving DL grant (e.g., a DL grant received before a UL grant) and/or a late-arriving DL grant (e.g., a DL grant received after a UL grant) to at least one of the second PUSCH/PUSCH repetitions and the subsequent PUSCH/PUSCH repetitions. For example, as shown at 624, UE 601 may multiplex HARQ-ACK/NACK bits of PDSCH grant 610 received after PUSCH grant 614 with a second PUSCH repetition at slot 9, with a third PUSCH repetition at slot 14, and/or with a fourth PUSCH repetition at slot 19, and so on. Similarly, as shown at 613, the UE 601 may also multiplex HARQ-ACK/NACK bits of the early-arriving DL grant with at least one of a second PUSCH repetition and a subsequent PUSCH repetition. For example, the UE 601 may multiplex HARQ-ACK/NACK bits of the PDSCH grant 606 with the second PUSCH repetition at slot 09.

Fig. 7 is a diagram 700 illustrating an example of multiplexing a late arriving DL grant with at least one of a second PUSCH repetition and a subsequent PUSCH repetition in accordance with aspects of the present disclosure. As shown at 702, the UE may receive a PDCCH carrying a PUSCH grant 704 in a DL slot (e.g., at slot 03), where the PUSCH grant 704 may include a tDAI parameter 706 indicating a value of three (e.g., tdai=3). PUSCH grant 704 may indicate a PUSCH transmission, which constitutes a total of four (4) PUSCH repetitions scheduled to be transmitted at slots 04, 09, 14, and 19, which slots 04, 09, 14, and 19 may be associated with PUCCHs 708, 710, 712, and 714, respectively. PUCCHs 708, 710, 712, and 714 may also correspond to or overlap with a first PUSCH repetition, a second PUSCH repetition, a third PUSCH repetition, and a fourth PUSCH repetition, respectively.

In one example, as shown at 716, the UE may receive eight (8) early-arriving DL grants, where the UE may map HARQ-ACK/NACK bits of the eight early-arriving DL grants to 3-3-2-0 across four PUSCH repetitions. For example, the UE may map HARQ-ACK/NACK bits of the first three of the (eight) early-arriving DL grants to PUCCH 708 overlapping the first PUSCH repetition, the UE may map HARQ-ACK/NACK bits of the next three early-arriving DL grants to PUCCH 710 overlapping the second PUSCH repetition, and the UE may map HARQ-ACK/NACK bits of the last two early-arriving DL grants to PUCCH 712 overlapping the third PUSCH repetition, and so on. Since the tDAI parameter 706 may be a two-bit field, when the tDAI parameter 706 is equal to three (tdai=3), the tDAI parameter 706 may correspond to a HARQ codebook size of three, seven, eleven, fifteen bits, or the like.

Then, as shown at 718, the UE may receive eight (8) late arrival DL grants. Since the UE may be configured to map HARQ-ACK/NACK bits of the late reaching DL grant not to the first PUSCH repetition but to at least one of the second PUSCH repetition and the subsequent PUSCH repetition, in one example, the UE may map HARQ-ACK/NACK bits of eight late reaching DL grants to 0-0-4-4 across four PUSCH repetitions. For example, the UE may map the first four late arriving DL grant HARQ-ACK/NACK bits to PUCCH 712 overlapping with the third PUSCH repetition, and the UE may map the next (or last) four late arriving DL grant HARQ-ACK/NAK bits to PUCCH 714 overlapping with the fourth PUSCH repetition, and so on.

In some examples, the UE may be configured to transmit HARQ-ACK/NACK bits to the base station in an order corresponding to the order in which the DL grants were received. For example, if the UE receives a first DL grant at slot 00, a second DL grant at slot 01, and a third DL grant at slot 02, the UE may send HARQ-ACK/NACK bits for the first DL grant, the second DL grant, and the third DL grant based on the same order. Under such a configuration, one PUSCH repetition (e.g., the third PUSCH) may include HARQ-ACK/NACK bits for both the early-arriving DL grant and the late-arriving DL grant, while the other PUSCH repetition (e.g., the first PUSCH repetition, the second PUSCH repetition, or the third PUSCH repetition) may include HARQ-ACK/NACK bits for one of the early-arriving DL grant or the late-arriving DL grant, but not both. For example, based on such a configuration, the UE may start to transmit/map HARQ-ACK/NACK bits for late arriving DL grants after all HARQ-ACK/NACK bits for early arriving DL grants have been transmitted/mapped, since the UE receives early arriving DL grants before late arriving DL grants. Thus, there may be one PUCCH/PUSCH repetition carrying HARQ-ACK/NACK bits for both early and late arriving DL grants.

In another aspect of the present disclosure, if the UE is configured with the capability to multiplex the late arriving DL grant with at least one of the second PUSCH repetition and the subsequent PUSCH repetition, the UE may be further configured to interpret the cDAI and tDAI parameters in various ways depending on the setting. For example, aspects presented herein may provide a UE with a number of options/configurations for interpreting uplink tDAI. Aspects presented herein may also provide additional procedures for processing time sequences of cDAI and tDAI, etc., to a UE.

Fig. 8 is a communication flow 800 illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on the cDAI parameters and/or tDAI parameters of the UL/DL grants when the UE is configured to multiplex one or more late arriving DL grants with at least one of the PUSCH repetitions, in accordance with aspects of the disclosure.

In an aspect, at 806, the UE 802 may be configured to monitor the cDAI parameters sent from the base station 804 or a component of the base station 804 for one or more PDSCH grants 808 (e.g., PDSCH grants sent to the UE 802) arriving before the PUSCH grant 810 (e.g., one or more PDSCH grants 808 are early reaching DL grants). For example, referring back to fig. 7, at slot 14, the UE may be configured to monitor the cDAI for all DL grants (e.g., a total of eight early-arriving DL grants) that arrived before PUSCH grant 704. If the UE successfully receives and decodes eight early-arriving DL grants at 716, based on the cDAI associated with the early-arriving DL grant (e.g., PDSCH grant 808), the UE may know that the two HARQ-ACK-NACK bits of the current two early-arriving DL grants will be multiplexed with a third PUSCH repetition at slot 14 (e.g., cdai=2).

At 814, the UE 802 may compare its current count of PDSCH grants (e.g., corresponding to HARQ-ACK/NACK bits to be multiplexed with the third PUSCH repetition) to the value indicated by the tDAI parameter 812 in the PUSCH grant 810, and if there is a discrepancy, the UE 802 may insert one or more dummy bits into the HARQ-ACK/NACK bits. For example, referring back to fig. 7, if the UE knows that two HARQ-ACK-NACK bits of an early arriving DL grant will be multiplexed with a third PUSCH repetition at slot 14 (e.g., cdai=2), but tDAI parameter 706 indicates a value of three (tdai=3), the UE may coordinate the difference by adding one dummy bit to the two HARQ-ACK/NACK bits such that the cDAI becomes three (3) and matches the tDAI.

At 816, the UE 802 may monitor the one or more PDSCH grants 818 (e.g., late arriving PDSCH grants) based on the cDAI and tDAI parameters in the one or more PDSCH grants 818 (e.g., late arriving PDSCH grants) and determine whether any HARQ-ACK/NACK bits for the one or more PDSCH grants 818 (e.g., late arriving PDSCH grants) are to be multiplexed (e.g., multiplexed to a third PUSCH repetition). For example, referring back to fig. 7, if the UE successfully receives eight (8) late DL grants at 718, the UE may detect/determine that four HARQ-ACK/NACK bits of four (4) late DL grants are to be multiplexed with a third PUSCH repetition at slot 14.

At 820, the UE 802 may again compare its current count of PDSCH grants (e.g., current calculated/accumulated HARQ-ACK/NACK bits for early arriving PDSCH grants, for dummy bits added at 814, and for late arriving PDSCH grants) with tDAI parameters 812 and determine the HARQ codebook size 822 of the HARQ codebook to send to the base station 804, which carries HARQ-ACK/NACK bits for early arriving PDSCH grants and late arriving PDSCH grants. Similarly, at 820, if there is a difference between the current count and the tDAI parameter, the UE 802 may insert a dummy bit into the current count of PDSCH grants. For example, referring back to fig. 7, the ue may calculate that the HARQ-ACK/NACK bits to be multiplexed with the third PUSCH repetition are seven (7), e.g., three (3) HARQ-ACK/NACK bits are associated with the early arriving DL grant (including one dummy bit), and four HARQ-ACK/NACK bits are associated with the late arriving DL grant, and so on. The UE may then compare the calculated HARQ-ACK/NACK bits with the uplink tDAI. Since tdai=3 may correspond to codebook sizes of 3, 7, 11, 14 bits, etc., the UE may determine/select 7 bits as the final codebook size. In other words, since the calculated HARQ-ACK/NACK bits (e.g., 7 bits) match one of the HARQ codebook sizes associated with the tDAI parameter 706, no dummy bits are added here.

At 824, the UE 802 may multiplex one or more PDSCH grants 818 (e.g., early arriving PDSCH grants) and/or one or more HARQ-ACK/NACK bits of late arriving PDSCH grants with PUSCH/PUSCH repetition, where the size of the HARQ-ACK/NACK bits may be based on the determined HARQ codebook size 822, and the UE may transmit PUSCH/PUSCH repetition to the base station 804. For example, referring back to fig. 7, because the UE determines that the final codebook size is seven bits, the UE may repeatedly multiplex seven HARQ-ACK/NACK bits with the third PUSCH at the slot 14, and the UE may transmit the third PUSCH to the base station.

Thus, aspects presented herein may enable the UE 802 to perform a cDAI and tDAI check (e.g., at 824) between an early-arriving DL grant and a late-arriving DL grant to coordinate their values in the presence of a discrepancy, thereby enabling the UE 802 to repeatedly multiplex HARQ-ACK/NACK bits of the late-arriving DL grant with one or more PUSCHs while maintaining an accurate count of DL grants. In other words, aspects presented herein may enable the UE 802 to determine whether there is a difference between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant, and if there is a difference between the total number of DL grants and the UL tDAI value, may enable the UE 802 to adjust the total number of DL grants. In some examples, the cDAI and tDAI checks (e.g., at 824) between the early-arriving DL grant and the late-arriving DL grant may enable the UE 802 to detect whether one or more early-arriving DL grants are lost. For example, if the UE fails to receive two early-arriving DL grants and two late-arriving DL grants, the UE can detect a lost DL grant based on an uplink tDAI check.

In another aspect of the disclosure, the UE may be configured not to perform the cDAI and tDAI checks between an early arriving DL grant and a late arriving DL grant. Fig. 9A is a communication flow 900A illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on a cDAI and tDAI when the UE is configured to multiplex the one or more late arriving DL grants with at least one of the PUSCH repetitions but not perform a cDAI and tDAI check between the early arriving DL grant and the late arriving DL grant, in accordance with aspects of the present disclosure.

In an aspect, at 906, the UE 902 may be configured to monitor the cDAI parameters of one or more PDSCH grants 908 (e.g., PDSCH grants sent to the UE 902) sent from the base station 904 or a component of the base station 904 for arrival before the PUSCH grant 910 (e.g., one or more PDSCH grants 908 are early arriving PDSCH grants), and the UE 902 may determine whether any HARQ-ACK/NACK bits for early arriving DL grants are to be multiplexed to PUSCH repetition.

At 916, the UE 902 may monitor for one or more late arriving DL grants (e.g., PDSCH grant 918) based on the cDAI and tDAI parameters in the one or more late arriving DL grants and determine whether any HARQ-ACK/NACK bits for the late arriving DL grant are to be multiplexed to PUSCH repetition.

At 920, the UE 902 may compare its current count of PDSCH grants (e.g., current calculated/accumulated HARQ-ACK/NACK bits for one or more PDSCH grants 908 (e.g., early arriving PDSCH grants) and one or more PDSCH grants 918 (e.g., late arriving PDSCH grants) with possible values associated with the tDAI parameter 912 carried in the PUSCH grant 910 and determine a HARQ codebook size 922 of a HARQ codebook to send to the base station 904, the HARQ codebook carrying HARQ-ACK/NACK bits for the one or more PDSCH grants 908 (e.g., early arriving PDSCH grants) and the one or more PDSCH grants 918 (e.g., late arriving PDSCH grants). Similarly, at 920, if there is a difference between the current count and the tDAI parameter, the UE 902 may insert a dummy bit into the current count of PDSCH grants.

For example, referring back to fig. 7, based on monitoring of early-arriving DL grants and late-arriving DL grants (e.g., at 906 and 916), the UE may determine that two HARQ-ACK/NACK bits of two early-arriving DL grants and four HARQ-ACK/NACK bits of four late-arriving DL grants are to be multiplexed with a third PUSCH repetition at slot 14 (e.g., total ACK/NACK count: 2+4=6). The UE may compare the current count of DL grants (e.g., the calculated six HARQ-ACK/NACK bits) with tDAI parameter 706. Since tdai=3 may correspond to HARQ codebook sizes of 3, 7, 11, 14 bits, etc., the UE may round the current count of DL grants to the closest HARQ codebook size supported by adding one or more dummy bits to the calculated HARQ-ACK/NACK bits. For example, since the seven-bit HARQ codebook size is closest to the current count of six PDSCH grants that may correspond to six HARQ-ACK/NACK bits, the UE may add dummy bits to the six HARQ ACK/NACK bits such that the final HARQ codebook size 822 is seven bits (e.g., 6+1=7).

At 924, the UE 902 may multiplex HARQ-ACK/NACK bits for one or more PDSCH grants 908 (e.g., early arriving PDSCH grants) and one or more PDSCH grants 918 (e.g., late arriving PDSCH grants) with PUSCH repetition, where the size of the HARQ-ACK/NACK bits may be based on the determined HARQ codebook size 922, and the UE may transmit the PUSCH repetition to the base station 904. For example, referring back to fig. 7, because the UE determines the final codebook size to be 7 bits, the UE may multiplex seven HARQ-ACK/NACK bits (e.g., one of the bits is a dummy bit) with the third PUSCH repetition at the slot 14, and the UE may transmit the third PUSCH to the base station.

Fig. 10 is a schematic diagram 1000 illustrating an example of multiplexing a late arriving DL grant with at least one of a second PUSCH repetition and a subsequent PUSCH repetition in accordance with aspects of the present disclosure. As shown at 1002, the UE may receive a PDCCH carrying a PUSCH grant 1004 in a DL slot (e.g., at slot 03), where the PUSCH grant 1004 may include a tDAI parameter 1006 indicating a value of one (e.g., tdai=1). PUSCH grant 1004 may indicate a PUSCH transmission, which constitutes a total of four (4) PUSCH repetitions scheduled to be transmitted at slots 04, 09, 14, and 19, which slots 04, 09, 14, and 19 may be associated with PUCCHs 1008, 1010, 1012, and 1014, respectively. PUCCHs 1008, 1010, 1012, and 1014 may also correspond to or overlap with the first PUSCH repetition, the second PUSCH repetition, the third PUSCH repetition, and the fourth PUSCH repetition, respectively.

In one example, as shown at 1016, the UE may receive seven (7) early-arriving DL grants, where the UE may map HARQ-ACK/NACK bits of the seven early-arriving DL grants to 2-3-2-0 across four PUSCH repetitions. For example, the UE may map HARQ-ACK/NACK bits of the first two of the (eight) early-arriving DL grants to PUCCH 1008 overlapping the first PUSCH repetition, the UE may map HARQ-ACK/NACK bits of the next three early-arriving DL grants to PUCCH 1010 overlapping the second PUSCH repetition, and the UE may map HARQ-ACK/NACK bits of the last two early-arriving DL grants to PUCCH 1012 overlapping the third PUSCH repetition, and so on. Since the tDAI parameter 1006 may be a two-bit field, when the tDAI parameter 1006 is equal to one (tdai=1), the tDAI parameter 1006 may correspond to a HARQ codebook size of one, five, nine, or thirteen bits, etc.

Then, as shown at 1018, the UE may receive eight (8) late arrival DL grants. Since the UE may be configured to map HARQ-ACK/NACK bits of the late reaching DL grant not with the first PUSCH repetition, but with at least one of the second PUSCH repetition and the subsequent PUSCH repetition, in one example, the UE may map eight HARQ-ACK/NACK bits of the late reaching DL grant to 0-0-3-5 across four PUSCH repetitions. For example, the UE may map the first three HARQ-ACK/NACK bits of the late arriving DL grant to PUCCH 1012 overlapping with the third PUSCH repetition, and the UE may map the next (or last) five HARQ-ACK/NAK bits of the late arriving DL grant to PUCCH 1014 overlapping with the fourth PUSCH repetition, and so on.

As discussed in association with fig. 8, the UE may track incoming DL grants via the cDAI and tDAI based on the following. For example, to determine the HARQ-ACK/NACK bits of the early-arriving DL grant and the late-arriving DL grant to be repeatedly multiplexed with the third PUSCH (e.g., to be transmitted at slot 14), the UE may first monitor the cDAI of all DL grants (e.g., all early-arriving DL grants) arriving before PUSCH grant 1004, e.g., as shown at 806 of fig. 8. Based on the monitoring of the cDAI, the UE may know that there are two HARQ-ACK/NACK bits of the early-arriving DL grant to be multiplexed with the third PUSCH repetition (e.g., cdai=2). The UE may then compare the HARQ-ACK/NACK bit (e.g., 2) to the value indicated by the tDAI parameter 1006 (e.g., tdai=1), and if there is a difference between the cDAI and tDAI, the UE may insert one or more dummy bits into the HARQ-ACK/NACK bit, such as shown at 814 of fig. 8. For example, when cdai=2 and tdai=1 (which corresponds to 5, 9, 13, etc.), the UE may add three (3) dummy bits to the HARQ-ACK/NACK bits such that the total count of HARQ-ACK/NACK bits that arrive early at the DL grant is five bits (e.g., cdai=2+3=5) that match one of the values associated with tdai=1. Then, as shown at 816 of fig. 8, the UE may monitor for late arriving DL grants based on the cDAI and tDAI in the DL grant. In this example, the UE may detect that HARQ feedback for three late arriving DL grants (e.g., if all DL grants were successfully received and decoded) will be mapped to a third PUSCH repetition, and may determine that the current ACK/NACK count is eight bits (e.g., 5+3=8). The UE may then again compare the current ACK/NACK count to the value indicated by tDAI parameter 1006, as shown at 820 of fig. 8. Since tdai=1 may correspond to HARQ codebook sizes of 1, 5, 9, 13 bits, etc., the UE may round the current count of DL grants to the closest HARQ codebook size supported by adding one or more dummy bits. For example, since the nine-bit HARQ codebook size is closest to the current ACK/NACK count of eight bits, the UE may add dummy bits to the current ACK/NAK count such that the final codebook size is nine bits (e.g., 8+1=9).

In another aspect of the disclosure, to have a consistent determination/calculation of HARQ codebook size by the UE and the base station (e.g., the base station's desired HARQ codebook size matches the UE-determined HARQ codebook size), the UE and the base station may be configured to process/interpret uplink tDAI (e.g., tDAI parameters in UL grant) differently based on the settings. In other words, for a UE to apply tDAI/cDAI checks on early-arriving DL grants and/or late-arriving DL grants, the base station may select the value of uplink tDAI based on a set of rules.

In one aspect (e.g., option 1), when the base station is transmitting a late arrival DL grant to the UE, the base station may be configured to ignore the uplink tDAI. Thus, tDAI of late arriving DL grants may be increased based on previous DL grants and without regard to uplink tDAI. In response, the UE may compare the counted DL grant with the uplink tDAI in the last step prior to determining the codebook size, as described in connection with 920 of fig. 9A.

In another aspect (e.g., option 2), the base station may consider an uplink tDAI before sending the late arriving DL grant to the UE, where the tDAI and the cDAI of the late arriving DL grant may be incremented using the uplink tDAI as a reference. In response, the UE may be configured to perform a tDAI/cDAI check between an early arriving DL grant and a late arriving DL grant, e.g., as described in connection with 814 of fig. 8. In other words, the UE may compare the counted DL grant with the uplink tDAI twice (e.g., at 814 and 820 as shown in fig. 8). This aspect may be useful when the UE fails to receive/decode one or more early arriving DL grants and/or one or more late arriving DL grants.

In another aspect (e.g., option 3), the base station may reset the cDAI across the boundary between the early-arriving DL grant and the late-arriving DL grant, so that there may be two HARQ codebooks that may be concatenated. In other words, the base station may treat the early-arriving DL grant and the late-arriving DL grant as separate entities, and the base station may expect the UE to separately determine HARQ codebooks for the early-arriving DL grant and the late-arriving DL grant. For example, referring back to fig. 7, at slot 14, the UE may form a first HARQ codebook for two early-arriving DL grants based on monitoring the cDAI for early-arriving DL grants and based on comparing the counted values to the uplink tDAI, e.g., as described in connection with 806 and 814 of fig. 8. Then, for subsequent late arriving DL grants, the UE may reset the cDAI and monitor the cDAI for late arriving DL grants, and the UE may form a second codebook for four late arriving DL grants based on monitoring the cDAI for late arriving DL grants. After forming the first codebook and the second codebook for the early-arriving DL grant and the late-arriving DL grant, respectively, the UE may concatenate the first codebook with the second codebook and transmit the combined codebook to the base station. In other words, the UE may reset the cDAI process at the boundary, and the UE may run pseudo code twice, which may be equivalent to having two separate codebooks: one for early grant and the other for late grant.

In another aspect (e.g., option 4), the base station may use the uplink tDAI for the first PUSCH repetition, and the base station and UE may ignore the uplink tDAI for subsequent PUSCH repetitions. In response, the UE may check the uplink tDAI for the first PUSCH retransmission. For subsequent PUSCH repetition transmissions, the UE may rely on the downlink tDAI (e.g., the tDAI parameters in the DL grant) to derive the HARQ codebook size. For example, referring back to fig. 7, in determining the HARQ codebook size for the first PUSCH repetition at slot 04, the UE may rely on the tDAI parameter 706. For second and subsequent PUSCH repetitions (e.g., at slots 09, 14, 19), the UE may be configured to ignore the tDAI parameter 706, and the UE may determine the HARQ codebook size for the second and subsequent PUSCH repetitions based on the tDAI parameter and/or the cDAI parameter in the DL grant. For example, the latest arriving DL grant that can be multiplexed may be based on an N1/N2 timeline determined by the starting symbol of PUSCH/PUCCH.

Fig. 9B is a communication flow 900B illustrating an example of a UE monitoring and tracking one or more incoming DL grants based on a cDAI and tDAI when the UE is configured to multiplex the one or more late arriving DL grants with at least one of the PUSCH repetitions but not perform a cDAI and tDAI check between the early arriving DL grant and the late arriving DL grant, in accordance with aspects of the present disclosure. In this example, the UE may rely on the downlink tDAI (e.g., tDAI parameters in DL grant) to derive the HARQ codebook size (e.g., option 4).

In an aspect, at 936, the UE 932 may be configured to monitor the cDAI parameters of one or more PDSCH grants 938 (e.g., PDSCH grants sent to the UE 932) sent from the base station 934 or a component of the base station 934 that arrived before the PUSCH grant 940 (e.g., one or more PDSCH grants 938 are early arriving PDSCH grants), and the UE 932 may determine whether any HARQ-ACK/NACK bits for early arriving DL grants are to be multiplexed to PUSCH repetition.

At 946, the UE 932 may monitor one or more late arriving DL grants (e.g., PDSCH grant 948) based on the cDAI and tDAI parameters in the one or more late arriving DL grants and determine whether any HARQ-ACK/NACK bits for the late arriving DL grant are to be multiplexed to PUSCH repetition.

At 950, the UE 932 may compare its current count of PDSCH grants (e.g., current calculated/accumulated HARQ-ACK/NACK bits for one or more PDSCH grants 938 (e.g., early arriving PDSCH grants) and one or more PDSCH grants 948 (e.g., late arriving PDSCH grants)) with possible values associated with the tDAI parameters 949 carried in the PDSCH grants 948 and determine a HARQ codebook size 952 of a HARQ codebook to be transmitted to the base station 934, the HARQ codebook carrying HARQ-ACK/NACK bits for one or more PDSCH grants 938 (e.g., early arriving PDSCH grants) and one or more PDSCH grants 948 (e.g., late arriving PDSCH grants). Similarly, at 950, if there is a difference between the current count and the tDAI parameter, the UE 932 may insert dummy bits into the current count of PDSCH grants.

At 954, UE 932 may multiplex HARQ-ACK/NACK bits for one or more PDSCH grants 938 (e.g., early arriving PDSCH grants) and one or more PDSCH grants 948 (e.g., late arriving PDSCH grants) with PUSCH repetition, where the size of the HARQ-ACK/NACK bits may be based on the determined HARQ codebook size 952, and the UE may send PUSCH repetition to base station 934.

Fig. 11 is a flow chart 1100 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 401, 601, 802, 902, 932; apparatus 1302; a processing system, which may include memory 360 and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356, and/or controller/processor 359). The method may enable the UE to repeatedly multiplex HARQ-ACK/NACK bits of DL grant arriving after an uplink grant with PUSCH while keeping track of tDAI.

In one example, the UE may receive one or more DL grants prior to receiving the UL grant, wherein the one or more DL grants are associated with DL cDAI, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 806, the UE 802 may receive one or more PDSCH grants 808 from the base station 804 prior to receiving the PUSCH grant 810, wherein the one or more PDSCH grants 808 are associated with the DL cDAI. The receiving of one or more DL grant(s) prior to receiving a UL grant may be performed by DL grant processing component 1340 and/or receiving component 1330 of device 1302 in fig. 13, for example.

In another example, the UE may determine whether there is a difference between the UL tDAI value and the total number of DL grants sent to the UE until one or more DL grants are received, e.g., as described in connection with fig. 8. For example, at 814, the UE 802 may determine whether there is a difference between the tDAI parameter 812 of the PUSCH grant 810 and the total number of PDSCH grants received until one or more PDSCH grants 818 are received. The determination of whether there is a difference between the UL tDAI value and the total number of DL grants sent to the UE may be performed by, for example, DL grant number verification component 1342 of apparatus 1302 in fig. 13.

In another example, if there is a difference between the UL tDAI value and the total number of DL grants received until one or more DL grants are received, the UE may adjust the total number of DL grants sent to the UE until one or more DL grants are received, e.g., as described in connection with fig. 8. For example, at 814, if there is a difference between the UL tDAI value and the total number of DL grants, the UE 802 may adjust the total number of PDSCH grants received by inserting one or more dummy bits. The adjustment of the total number of DL grants may be performed by the adjustment component 1344 of the apparatus 1302 in fig. 13, for example.

At 1108, the UE may receive at least one DL grant from the base station after receiving the UL grant, wherein the at least one DL grant may be associated with a DL cDAI value and a DL tDAI value, and the UL grant may be associated with a UL tDAI value and schedule multiple PUSCH repetitions, such as described in connection with fig. 8, 9A, and/or 9B. For example, at 816, the UE 802 may receive one or more PDSCH grants 818 from the base station 804 after receiving the PUSCH grant 810, wherein the one or more PDSCH grants 818 are associated with DL cDAI values and DL tDAI values and the PUSCH grant is associated with the tDAI parameter 812. Receiving at least one DL grant after receiving a UL grant may be performed by DL grant processing component 1340 and/or receiving component 1330 of device 1302 in fig. 13, for example. The at least one DL grant may be at least one PDSCH grant and the UL grant may be a PUSCH grant.

In one example, the DL cDAI associated with one or more DL grants may be different from the DL cDAI associated with at least one DL grant.

At 1110, the UE may calculate a total number of DL grants sent to the UE based on the DL cDAI value, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 820, the UE 802 may count the total number of received PDSCH grants based on the DL cDAI value. Calculating the total number of DL grants sent to the UE based on the DL cDAI value may be performed by, for example, DL grant number verification component 1342 of apparatus 1302 in fig. 13.

At 1112, if there is a difference between the total number of DL grants and the UL tDAI value, the UE may adjust the total number of DL grants, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 820, if there is a difference between the current count and the tDAI parameter 812, the UE 802 may adjust the total number of PDSCH grants by inserting dummy bits. The adjustment of the total number of DL grants may be performed by the adjustment component 1344 of the apparatus 1302 in fig. 13, for example.

In one example, if there is a difference between the total number of DL grants sent to the UE and the UL tDAI value, the UE may add one or more counts to the total number of DL grants in order to adjust the total number of DL grants. In such an example, the UE may add one or more padding bits or dummy bits to the HARQ codebook based on one or more counts added to the total number of DL grants.

In another example, the UE may receive at least one repetition of the UL grant from the base station. In such an example, the HARQ codebook may be multiplexed with at least one repetition of the UL grant. In such an example, the PUCCH carrying one or more HARQ feedback bits of the at least one DL grant overlaps with the PUSCH of one of the at least one repetition of the UL grant.

At 1114, the UE may transmit a HARQ codebook in at least one PUSCH repetition of the plurality of PUSCH repetitions to the base station, wherein the size of the HARQ codebook may be based on the total number of adjusted DL grants, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 824, the UE 802 may transmit the HARQ codebook to the base station 804 on a PUSCH/PUSCH repetition based on the HARQ codebook size 822. The transmission of the HARQ codebook may be performed by, for example, HARQ codebook generation component 1346 and/or transmission component 1334 of apparatus 1302 in fig. 13. The HARQ codebook may correspond to a HARQ ACK/NACK codebook.

In one example, the HARQ codebook may be multiplexed with a first repetition of UL grant. In such an example, the UE may determine a size of the HARQ codebook for one or more repetitions after the first repetition for the UL grant based on the DL tDAI value. In such an example, the UE may determine the size of the HARQ codebook for one or more repetitions after the first repetition for the UL grant without the UL tDAI value. In such an example, the UE may discard the UL tDAI value after determining the size of the HARQ codebook or after multiplexing the HARQ codebook with the first repetition of the UL grant.

In another example, the HARQ codebook may be repeatedly multiplexed with one PUSCH.

In another example, the HARQ codebook may be excluded from multiplexing with the first PUSCH repetition.

In another example, before determining the size of the HARQ codebook, the UE may determine whether there is a difference between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant.

Fig. 12 is a flow chart 1200 of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 401, 601, 802, 902, 932; apparatus 1302; a processing system, which may include memory 360 and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356, and/or controller/processor 359). The method may enable the UE to repeatedly multiplex HARQ-ACK/NACK bits of DL grant arriving after an uplink grant with PUSCH while keeping track of tDAI.

At 1202, the UE may receive one or more DL grants prior to receiving the UL grant, wherein the one or more DL grants are associated with DL cDAI, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 806, the UE 802 may receive one or more PDSCH grants 808 from the base station 804 prior to receiving the PUSCH grant 810, wherein the one or more PDSCH grants 808 are associated with the DL cDAI. The receiving of one or more DL grant(s) prior to receiving a UL grant may be performed by DL grant processing component 1340 and/or receiving component 1330 of device 1302 in fig. 13, for example.

At 1204, the UE may determine whether there is a difference between the UL tDAI value and the total number of DL grants sent to the UE until one or more DL grants are received, e.g., as described in connection with fig. 8. For example, at 814, the UE 802 may determine whether there is a difference between the tDAI parameter 812 of the PUSCH grant 810 and the total number of PDSCH grants received until one or more PDSCH grants 818 are received. The determination of whether there is a difference between the UL tDAI value and the total number of DL grants sent to the UE may be performed by, for example, DL grant number verification component 1342 of apparatus 1302 in fig. 13.

At 1206, if there is a difference between the UL tDAI value and the total number of DL grants received until one or more DL grants are received, the UE may adjust the total number of DL grants received until one or more DL grants are received, e.g., as described in connection with fig. 8. For example, at 814, if there is a difference between the UL tDAI value and the total number of DL grants, the UE 802 may adjust the total number of PDSCH grants received by inserting one or more dummy bits. The adjustment of the total number of DL grants may be performed by the adjustment component 1344 of the apparatus 1302 in fig. 13, for example.

At 1208, the UE may receive at least one DL grant from the base station after receiving the UL grant, wherein the at least one DL grant may be associated with a DL cDAI value and a DL tDAI value, and the UL grant may be associated with a UL tDAI value and schedule multiple PUSCH repetitions, such as described in connection with fig. 8, 9A, and/or 9B. For example, at 816, the UE 802 may receive one or more PDSCH grants 818 from the base station 804 after receiving the PUSCH grant 810, wherein the one or more PDSCH grants 818 are associated with DL cDAI values and DL tDAI values and the PUSCH grant is associated with the tDAI parameter 812. Receiving at least one DL grant after receiving a UL grant may be performed by DL grant processing component 1340 and/or receiving component 1330 of device 1302 in fig. 13, for example. The at least one DL grant may be at least one PDSCH grant and the UL grant may be a PUSCH grant.

In one example, the DL cDAI associated with one or more DL grants may be different from the DL cDAI associated with at least one DL grant.

At 1210, the UE may calculate a total number of DL grants sent to the UE based on the DL cDAI value, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 820, the UE 802 may count the total number of received PDSCH grants based on the DL cDAI value. Calculating the total number of DL grants sent to the UE based on the DL cDAI value may be performed by, for example, DL grant number verification component 1342 of apparatus 1302 in fig. 13.

At 1212, if there is a difference between the total number of DL grants and the UL tDAI value, the UE may adjust the total number of DL grants, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 820, if there is a difference between the current count and the tDAI parameter 812, the UE 802 may adjust the total number of PDSCH grants by inserting dummy bits. The adjustment of the total number of DL grants may be performed by the adjustment component 1344 of the apparatus 1302 in fig. 13, for example.

In one example, if there is a difference between the total number of DL grants and the UL tDAI value, the UE may add one or more counts to the total number of DL grants in order to adjust the total number of DL grants. In such an example, the UE may add one or more padding bits or dummy bits to the HARQ codebook based on one or more counts added to the total number of DL grants.

In another example, the UE may receive at least one repetition of the UL grant from the base station. In such an example, the HARQ codebook may be multiplexed with at least one repetition of the UL grant. In such an example, the PUCCH carrying one or more HARQ feedback bits of the at least one DL grant overlaps with the PUSCH of one of the at least one repetition of the UL grant.

At 1214, the UE may transmit a HARQ codebook in at least one PUSCH repetition of the plurality of PUSCH repetitions to the base station, wherein the size of the HARQ codebook may be based on the total number of adjusted DL grants, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 824, the UE 802 may transmit the HARQ codebook to the base station 804 on a PUSCH/PUSCH repetition based on the HARQ codebook size 822. The transmission of the HARQ codebook may be performed by, for example, HARQ codebook generation component 1346 and/or transmission component 1334 of apparatus 1302 in fig. 13. The HARQ codebook may correspond to a HARQ ACK/NACK codebook.

In one example, the HARQ codebook may be multiplexed with a first repetition of UL grant. In such an example, the UE may determine a size of the HARQ codebook for one or more repetitions after the first repetition for the UL grant based on the DL tDAI value. In such an example, the UE may determine the size of the HARQ codebook for one or more repetitions after the first repetition for the UL grant without the UL tDAI value. In such an example, the UE may discard the UL tDAI value after determining the size of the HARQ codebook or after multiplexing the HARQ codebook with the first repetition of the UL grant.

In another example, the HARQ codebook may be repeatedly multiplexed with one PUSCH.

In another example, the HARQ codebook may be excluded from multiplexing with the first PUSCH repetition.

In another example, before determining the size of the HARQ codebook, the UE may determine whether there is a difference between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant.

Fig. 13 is a schematic diagram 1300 illustrating an example of a hardware implementation for an apparatus 1302. The apparatus 1302 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1302 may include a cellular baseband processor 1304 (also referred to as a modem) coupled to a cellular RF transceiver 1322. In some aspects, the apparatus 1302 may further include one or more Subscriber Identity Module (SIM) cards 1320, an application processor 1306 coupled to the Secure Digital (SD) card 1308 and the screen 1310, a bluetooth module 1312, a Wireless Local Area Network (WLAN) module 1314, a Global Positioning System (GPS) module 1316, or a power supply 1318. The cellular baseband processor 1304 communicates with the UE 104 and/or BS102 via a cellular RF transceiver 1322. The cellular baseband processor 1304 may include a computer-readable medium/memory. The computer readable medium/memory may be non-transitory. The cellular baseband processor 1304 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor 1304, causes the cellular baseband processor 1304 to perform the various functions described supra. The computer readable medium/memory can also be used for storing data that is manipulated by the cellular baseband processor 1304 when executing software. Cellular baseband processor 1304 also includes a receive component 1330, a communication manager 1332, and a transmit component 1334. The communications manager 1332 includes one or more of the illustrated components. The components within the communication manager 1332 may be stored in a computer-readable medium/memory and/or configured as hardware within the cellular baseband processor 1304. The cellular baseband processor 1304 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1302 may be a modem chip and include only the baseband processor 1304, and in another configuration, the apparatus 1302 may be an entire UE (e.g., see 350 of fig. 3) and include additional modules of the apparatus 1302.

The communication manager 1332 includes a DL grant processing component 1340 configured to receive one or more DL grants prior to receiving a UL grant, wherein the one or more DL grants are associated with a DL cadai, e.g., as described in connection with 1202 of fig. 12, and/or configured to receive at least one DL grant from a base station after receiving a UL grant, the at least one DL grant being associated with a DL cadai value and a DL tDAI value, the UL grant being associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions, e.g., as described in connection with 1108 of fig. 11 and/or 1208 of fig. 12. The communication manager 1332 also includes a DL grant number verification component 1342 configured to determine whether there is a difference between the UL tDAI value and the total number of DL grants sent to the UE until one or more DL grants are received, e.g., as described in connection with 1204 of fig. 12, and/or configured to calculate the total number of DL grants sent to the UE based on the DL cDAI value, e.g., as described in connection with 1110 of fig. 11 and/or 1210 of fig. 12. The communication manager 1332 further includes an adjustment component 1344 configured to adjust the total number of DL grants received until one or more DL grants are received if there is a difference between the UL tDAI value and the total number of DL grants received until one or more DL grants are received, e.g., as described in connection with 1206 of fig. 12, and/or configured to adjust the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value, e.g., as described in connection with 1112 of fig. 11 and/or 1212 of fig. 12. The communication manager 1332 further includes a HARQ codebook generation component 1346 configured to transmit a HARQ codebook to the base station in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on the total number of adjusted DL grants, e.g., as described in connection with 1114 of fig. 11 and/or 1214 of fig. 12.

The apparatus may include additional components to perform each of the blocks of the algorithms in the flowcharts of fig. 11 and 12. Accordingly, each block in the flowcharts of fig. 11 and 12 may be performed by components, and the apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1302 may include various components configured for various functions. In one configuration, the apparatus 1302 (and in particular, the cellular baseband processor 1304) comprises: means for receiving at least one DL grant from the base station after receiving the UL grant, the at least one DL grant being associated with a DL cDAI value and a DL tDAI value, the UL grant being associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions (e.g., DL grant processing component 1340 and/or receiving component 1330). The apparatus 1302 includes: a means for calculating a total number of DL grants sent to the UE based on the DL cDAI value (e.g., DL grant number verification component 1342). The apparatus 1302 includes: means (e.g., adjustment component 1344) for adjusting the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value. The apparatus 1302 includes: the apparatus includes means for transmitting a HARQ codebook to a base station in at least one PUSCH repetition of a plurality of PUSCH repetitions, the HARQ codebook sized based on a total number of adjusted DL grants (e.g., HARQ codebook generation component 1346). The apparatus 1302 includes: means for receiving one or more DL grants prior to receiving the UL grant, wherein the one or more DL grants are associated with a DL cDAI (e.g., DL grant processing component 1340 and/or receiving component 1330). The apparatus 1302 includes: a means for determining whether there is a difference between the UL tDAI value and a total number of DL grants sent to the UE until one or more DL grants are received (e.g., DL grant number verification component 1342). The apparatus 1302 includes: means (e.g., adjustment component 1344) for adjusting the total number of DL grants received until the one or more DL grants are received if there is a difference between the UL tDAI value and the total number of DL grants received until the one or more DL grants are received.

In one configuration, the DL cDAI associated with one or more DL grants may be different from the DL cDAI associated with at least one DL grant.

In another configuration, the means for adjusting the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value comprises: the apparatus includes means for adding one or more counts to a total number of DL grants. In such a configuration, the apparatus 1302 includes: the apparatus includes means for adding one or more padding or dummy bits to the HARQ codebook based on one or more counts added to a total number of DL grants.

In another configuration, the apparatus 1302 includes: at least one repetition for receiving a UL grant from a base station. In such a configuration, the HARQ codebook may be multiplexed with at least one repetition of the UL grant. In such a configuration, the PUCCH carrying one or more HARQ feedback bits of the at least one DL grant overlaps with the PUSCH of one of the at least one repetition of the UL grant.

In another configuration, the HARQ codebook may be multiplexed with the first repetition of the UL grant. In such a configuration, the apparatus 1302 includes: the apparatus includes means for determining a size of a HARQ codebook for one or more repetitions after a first repetition for a UL grant based on a DL tDAI value. In such a configuration, the apparatus 1302 includes: the apparatus includes means for determining a size of a HARQ codebook for one or more repetitions after a first repetition for a UL grant without a UL tDAI value. In such a configuration, the apparatus 1302 includes: the apparatus may include means for discarding the UL tDAI value after determining the size of the HARQ codebook or after multiplexing the HARQ codebook with a first repetition of the UL grant.

In another configuration, the HARQ codebook may be repeatedly multiplexed with one PUSCH.

In another configuration, the HARQ codebook may be excluded from multiplexing with the first PUSCH repetition.

In another configuration, the apparatus 1302 includes: means for determining whether there is a difference between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant prior to determining the size of the HARQ codebook.

An element may be one or more of the components of the apparatus 1302 configured to perform the functions recited by the element. As described above, the apparatus 1302 may include a TX processor 368, an RX processor 356, and a controller/processor 359. Thus, in one configuration, the elements may be TX processor 368, RX processor 356, and controller/processor 359 configured to perform the functions recited by the elements.

Fig. 14 is a flow chart 1400 of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base stations 102, 310, 403, 603, 804, 904, 934; apparatus 1502; a processing system, which may include memory 376 and may be the entire base station 310 or a component of a base station 310 such as TX processor 316, RX processor 370, and/or controller/processor 375). The method may enable the base station to receive a HARQ codebook in a PUSCH repetition, the HARQ codebook comprising HARQ-ACK/NACK bits of a DL grant transmitted after scheduling an uplink grant of the PUSCH repetition.

At 1402, the base station may transmit one or more DL grants prior to transmitting the UL grant, wherein the one or more DL grant grants may be associated with DL cDAI, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 806, base station 804 may transmit one or more PDSCH grants 808 prior to transmitting PUSCH grant 810, where the one or more PDSCH grant grants may be associated with DL cDAI. Transmitting one or more DL grant(s) prior to transmitting an UL grant may be performed by, for example, the cDAI/tDAI configuration component 1540 and/or the transmit component 1534 of the apparatus 1502 in fig. 15. The at least one DL grant may be at least one PDSCH grant and the UL grant may be a PUSCH grant.

At 1404, the base station may transmit at least one DL grant to the UE after transmitting the UL grant, wherein the at least one DL grant may be associated with a DL cDAI value and a DL tDAI value, and the UL grant may be associated with a UL tDAI value and schedule multiple PUSCH repetitions, such as described in connection with fig. 8, 9A, and/or 9B. For example, at 816, the base station 804 may transmit one or more PDSCH grants 818 to the UE 802 after transmitting the PUSCH grant 810 including the tDAI parameter 812, the one or more PDSCH grants 818 may be associated with DL cDAI values and DL tDAI values. Transmitting the at least one DL grant after transmitting the UL grant may be performed by, for example, the cDAI/tDAI configuration component 1540 and/or the transmit component 1534 of the apparatus 1502 in fig. 15.

In one example, the DL cDAI associated with one or more DL grants may be different from the DL cDAI associated with at least one DL grant. In such examples, the DL cDAI associated with the one or more DL grants may be reset prior to transmitting the at least one DL grant.

In another example, the base station may increment the tDAI value associated with at least one DL grant for each previous DL grant.

In another example, the base station may increment the tDAI value and the cDAI value associated with the at least one DL grant using the UL tDAI value as a reference.

At 1406, the base station may receive a HARQ codebook from the UE in at least one PUSCH repetition of the plurality of PUSCH repetitions, wherein a size of the HARQ codebook may be based at least on the UL tDAI value, e.g., as described in connection with fig. 8, 9A, and/or 9B. For example, at 824, the base station 804 may receive a HARQ codebook from the UE 802 having a HARQ codebook size determined based at least in part on the UL tDAI value. The reception of the HARQ codebook may be performed by, for example, HARQ codebook processing component 1542 and/or reception component 1530 of apparatus 1502 in fig. 15. The HARQ codebook may correspond to a HARQ ACK/NACK codebook.

In one example, the base station may send at least one repetition of the UL grant to the UE. In such an example, the HARQ codebook may be associated with at least one repetition of UL grant. In such an example, the HARQ codebook may be associated with a first repetition of UL grant. In such an example, the base station may discard the UL tDAI value after receiving the HARQ codebook in the first repetition of the UL grant.

In another example, the PUCCH carrying one or more HARQ feedback bits of the at least one DL grant may overlap with the PUSCH of one of the at least one repetition of the UL grant.

Fig. 15 is a schematic diagram 1500 illustrating an example of a hardware implementation for an apparatus 1502. The apparatus 1502 may be a base station, a component of a base station, or may implement a base station functionality. In some aspects, apparatus 1502 may comprise a baseband unit 1504. The baseband unit 1504 may communicate with the UE 104 via a cellular RF transceiver 1522. Baseband unit 1504 may include a computer readable medium/memory. The baseband unit 1504 is responsible for general processing, including the execution of software stored on a computer-readable medium/memory. The software, when executed by baseband unit 1504, causes baseband unit 1504 to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1504 when executing software. Baseband unit 1504 also includes a receive component 1530, a communication manager 1532, and a transmit component 1534. The communication manager 1532 includes one or more of the illustrated components. Components within the communication manager 1532 may be stored in a computer-readable medium/memory and/or configured as hardware within the baseband unit 1504. Baseband unit 1504 may be a component of base station 310 and may include memory 376 and/or at least one of TX processor 316, RX processor 370, and controller/processor 375.

The communication manager 1532 includes a cDAI/tDAI configuration component 1540 that transmits one or more DL grants prior to transmitting UL grants, wherein the one or more DL grant grants can be associated with DL cDAI, e.g., as described in connection with 1402 of fig. 14, and/or at least one DL grant is transmitted to the UE after transmitting UL grant, wherein the at least one DL grant is associated with DL cDAI value and DL tDAI value, and the UL grant is associated with UL tDAI value and schedules multiple PUSCH repetitions, e.g., as described in connection with 1404 of fig. 14. The communication manager 1532 further includes a HARQ codebook processing component 1542 that receives a HARQ codebook from the UE in at least one PUSCH repetition of the plurality of PUSCH repetitions, wherein the size of the HARQ codebook is based at least on the UL tDAI value, e.g., as described in connection with 1406 of fig. 14.

The apparatus may include additional components to perform each of the blocks of the algorithm in the flowchart of fig. 14. Accordingly, each block in the flowchart of fig. 14 may be performed by components, and an apparatus may include one or more of those components. A component may be one or more hardware components specifically configured to perform the process/algorithm, implemented by a processor configured to perform the process/algorithm, stored within a computer readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1502 may include various components configured for various functions. In one configuration, the apparatus 1502 (and in particular, the baseband unit 1504) includes: means for transmitting one or more DL grants prior to transmitting the UL grant, wherein the one or more DL grants may be associated with DL cDAI (e.g., cDAI/tDAI configuration component 1540 and/or transmit component 1534). The apparatus 1402 includes: means for transmitting at least one DL grant to the UE after transmitting the UL grant, wherein the at least one DL grant may be associated with a DL cDAI value and a DL tDAI value, and the UL grant may be associated with a UL tDAI value and schedule multiple PUSCH repetitions (e.g., cDAI/tDAI configuration component 1540 and/or transmit component 1534). The apparatus 1402 includes: means for receiving a HARQ codebook from the UE in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value (e.g., HARQ codebook processing component 1542 and/or reception component 1530).

In one configuration, the DL cDAI associated with one or more DL grants may be different from the DL cDAI associated with at least one DL grant. In such a configuration, DL cDAI associated with one or more DL grants may be reset prior to transmitting at least one DL grant.

In another configuration, the apparatus 1402 includes: the apparatus includes means for incrementing, for each previous DL grant, a tDAI value associated with at least one DL grant.

In another configuration, the apparatus 1402 includes: the apparatus includes means for incrementing a tDAI value and a cDAI value associated with at least one DL grant using the UL tDAI value as a reference.

In another configuration, the apparatus 1402 includes: at least one repetition for transmitting a UL grant to a UE. In such a configuration, the HARQ codebook may be associated with at least one repetition of UL grants. In such a configuration, the HARQ codebook may be associated with a first repetition of UL grants. In such a configuration, the apparatus 1402 includes: the method includes discarding a UL tDAI value after receiving a HARQ codebook in a first repetition of a UL grant.

In another configuration, the PUCCH carrying one or more HARQ feedback bits of the at least one DL grant may overlap with the PUSCH of one of the at least one repetition of the UL grant.

An element may be one or more of the components of apparatus 1502 that are configured to perform the functions recited by the element. As described above, apparatus 1502 may include TX processor 316, RX processor 370, and controller/processor 375. Thus, in one configuration, the elements may be TX processor 316, RX processor 370, and controller/processor 375 configured to perform the functions recited by the elements.

It should be understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. It should be appreciated that the particular order or hierarchy of blocks in the process/flow diagram may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more". Terms such as "if", "when … …" and "at … …" should be interpreted to mean "under … … conditions" rather than meaning an immediate time relationship or reaction. That is, these phrases (e.g., "when … …") do not mean that an action occurs in response to or immediately during the occurrence of the action, but rather only that an action will occur if a condition is met, but do not require specific or immediate time constraints for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects. The term "some" refers to one or more unless specifically stated otherwise. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include multiple a, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B or C", "A, B, or one or more of C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" may be a alone, B alone, C, A and B, A and C, B and C, or a and B and C, wherein any such combination may comprise one or more members of A, B or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known to those of ordinary skill in the art or that are later come to be known are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, the disclosures herein are not intended to be dedicated to the public, regardless of whether such disclosures are explicitly recited in the claims. The words "module," mechanism, "" element, "" device, "and the like may not be a substitute for the word" unit. Thus, no claim element is to be construed as a functional unit unless the element is explicitly recited using the phrase "means for … …".

The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

Aspect 1 is an apparatus for wireless communication, comprising at least one processor coupled to a memory and configured to: receiving at least one DL grant associated with a DL cDAI value and a DL tDAI value after receiving an UL grant associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions; calculating a total number of DL grants sent to the UE based on the DL cDAI value; adjusting the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value; and transmitting a HARQ codebook in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on the total number of adjusted DL grants.

Aspect 2 is the apparatus of aspect 1, further comprising: a transceiver coupled to the at least one processor.

Aspect 3 is the apparatus of any one of aspects 1 and 2, wherein the at least one processor is further configured to: receive one or more DL grants prior to receiving the UL grant, wherein the one or more DL grants are associated with a DL cDAI; determining whether there is a difference between the UL tDAI value and a total number of the DL grants sent to the UE until the one or more DL grants are received; and if there is the difference between the UL tDAI value and the total number of DL grants received until the one or more DL grants are received, adjusting the total number of DL grants received until the one or more DL grants are received.

Aspect 4 is the apparatus of any one of aspects 1-3, wherein the DL cDAI associated with the one or more DL grants is different from the DL cDAI associated with the at least one DL grant.

Aspect 5 is the apparatus of any one of aspects 1-4, wherein, if the difference exists between the total number of DL grants and the UL tDAI value, the at least one processor is further configured to, in order to adjust the total number of DL grants: one or more counts are added to the total number of DL grants.

Aspect 6 is the apparatus of any one of aspects 1-5, wherein the at least one processor is further configured to: one or more padding bits or dummy bits are added to the HARQ codebook based on the one or more counts added to the total number of DL grants.

Aspect 7 is the apparatus of any one of aspects 1-6, wherein the at least one DL grant is at least one PDSCH grant and the UL grant is a PUSCH grant.

Aspect 8 is the apparatus of any one of aspects 1-7, wherein the at least one processor is further configured to: at least one repetition of the UL grant is received.

Aspect 9 is the apparatus according to any one of aspects 1 to 8, wherein the HARQ codebook is repeatedly multiplexed with one PUSCH.

Aspect 10 is the apparatus according to any one of aspects 1 to 9, wherein the HARQ codebook is excluded from multiplexing with a first PUSCH repetition.

Aspect 11 is the apparatus of any one of aspects 1-10, wherein the at least one processor is further configured to: the size of the HARQ codebook for one or more repetitions after the first PUSCH repetition for the UL grant is determined based on the DL tDAI value.

Aspect 12 is the apparatus of any one of aspects 1-11, wherein the at least one processor determines the size of the HARQ codebook for the one or more repetitions of the UL grant after the first PUSCH repetition without the UL tDAI value.

Aspect 13 is the apparatus of any one of aspects 1 to 12, wherein the at least one processor is further configured to: the UL tDAI value is discarded after the size of the HARQ codebook is determined or after the HARQ codebook is multiplexed with the first PUSCH repetition of the UL grant.

Aspect 14 is the apparatus of any one of aspects 1 to 13, wherein a PUCCH carrying one or more HARQ feedback bits of the at least one DL grant overlaps with a PUSCH of one of the at least one repetition of the UL grant.

Aspect 15 is the apparatus according to any one of aspects 1 to 14, wherein the HARQ codebook corresponds to a HARQ ACK/NACK codebook.

Aspect 16 is the apparatus of any one of aspects 1-15, wherein the at least one processor is configured to: before determining the size of the HARQ codebook, it is determined whether the difference exists between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant.

Aspect 17 is a method for implementing wireless communication of any one of aspects 1 to 16.

Aspect 18 is an apparatus for wireless communication, comprising means for implementing any of aspects 1 to 16.

Aspect 19 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 16.

Aspect 20 is an apparatus for wireless communication, comprising at least one processor coupled to a memory and configured to: transmitting at least one DL grant for the UE after transmitting the UL grant, the at least one DL grant being associated with a DL cDAI value and a DL tDAI value, the UL grant being associated with a UL tDAI value and scheduling a plurality of PUSCH repetitions; and receiving a HARQ codebook in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value.

Aspect 21 is the apparatus of aspect 20, further comprising: a transceiver coupled to the at least one processor.

Aspect 22 is the apparatus of any one of aspects 20 and 21, wherein the at least one processor is further configured to: one or more DL grants are sent prior to sending the UL grant, wherein the one or more DL grants are associated with a DL cDAI.

Aspect 23 is the apparatus of any one of aspects 20-22, wherein the DL cDAI associated with the one or more DL grants is different from the DL cDAI associated with the at least one DL grant.

Aspect 24 is the apparatus of any one of aspects 20-23, wherein the DL cDAI associated with the one or more DL grants is being reset prior to transmitting the at least one DL grant.

Aspect 25 is the apparatus of any one of aspects 20-24, wherein the at least one DL grant is at least one PDSCH grant and the UL grant is a PUSCH grant.

Aspect 26 is the apparatus of any one of aspects 20-25, wherein the at least one processor is further configured to: at least one repetition of the UL grant is sent.

Aspect 27 is the apparatus of any one of aspects 20-26, wherein the HARQ codebook is associated with the at least one repetition of the UL grant.

Aspect 28 is the apparatus of any one of aspects 20-27, wherein the HARQ codebook is associated with a first repetition of the UL grant.

Aspect 29 is the apparatus of any one of aspects 20-28, wherein the at least one processor is further configured to: the UL tDAI value is discarded after the HARQ codebook is received in the first repetition of the UL grant.

Aspect 30 is the apparatus of any one of aspects 20-29, wherein a PUCCH carrying one or more HARQ feedback bits of the at least one DL grant overlaps with a PUSCH of one of the at least one repetition of the UL grant.

Aspect 31 is the apparatus according to any one of aspects 20 to 30, wherein the HARQ codebook corresponds to a HARQ ACK/NACK codebook.

Aspect 32 is the apparatus of any one of aspects 20-31, wherein the at least one processor is further configured to: the tDAI value associated with the at least one DL grant is incremented for each previous DL grant.

Aspect 33 is the apparatus of any one of aspects 20-32, wherein the at least one processor is further configured to: the tDAI value and the cDAI value associated with the at least one DL grant are incremented using the UL tDAI value as a reference.

Aspect 34 is a method for implementing wireless communication of any of aspects 20 to 33.

Aspect 35 is an apparatus for wireless communication, comprising means for implementing any of aspects 20 to 33.

Aspect 36 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 20 to 33.

Claims (30)

1. An apparatus for wireless communication at a User Equipment (UE), comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receiving at least one Downlink (DL) grant after receiving an Uplink (UL) grant, the at least one DL grant being associated with a DL current downlink assignment index (cDAI) value and a DL total downlink assignment index (tDAI) value, the UL grant being associated with a UL tDAI value and scheduling a plurality of Physical Uplink Shared Channel (PUSCH) repetitions;

Calculating a total number of DL grants sent to the UE based on the DL cDAI value;

adjusting the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value; and

a hybrid automatic repeat request (HARQ) codebook is transmitted in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on a total number of adjusted DL grants.

2. The apparatus of claim 1, further comprising: a transceiver coupled to the at least one processor.

3. The apparatus of claim 1, wherein the at least one processor is further configured to:

receive one or more DL grants prior to receiving the UL grant, wherein the one or more DL grants are associated with a DL cDAI;

determining whether there is a difference between the UL tDAI value and a total number of the DL grants sent to the UE until the one or more DL grants are received; and

if there is the difference between the UL tDAI value and the total number of DL grants received until the one or more DL grants are received, the total number of DL grants received until the one or more DL grants are received is adjusted.

4. The apparatus of claim 3, wherein the DL cDAI associated with the one or more DL grants is different from the DL cDAI associated with the at least one DL grant.

5. The apparatus of claim 1, wherein, if the difference exists between the total number of DL grants and the UL tDAI value, to adjust the total number of DL grants, the at least one processor is further configured to:

one or more counts are added to the total number of DL grants.

6. The apparatus of claim 5, wherein the at least one processor is further configured to:

one or more padding bits or dummy bits are added to the HARQ codebook based on the one or more counts added to the total number of DL grants.

7. The apparatus of claim 1, wherein the at least one DL grant is at least one Physical Downlink Shared Channel (PDSCH) grant and the UL grant is a PUSCH grant.

8. The apparatus of claim 1, wherein the at least one processor is further configured to:

at least one repetition of the UL grant is received.

9. The apparatus of claim 1, wherein the HARQ codebook is repeatedly multiplexed with one PUSCH.

10. The apparatus of claim 1, wherein the HARQ codebook is excluded from multiplexing with a first PUSCH repetition.

11. The apparatus of claim 10, in which the at least one processor is further configured:

the size of the HARQ codebook for one or more repetitions after the first PUSCH repetition for the UL grant is determined based on the DL tDAI value.

12. The apparatus of claim 11, wherein the at least one processor determines the size of the HARQ codebook for the one or more repetitions of the UL grant after the first PUSCH repetition without the UL tDAI value.

13. The apparatus of claim 10, in which the at least one processor is further configured:

the UL tDAI value is discarded after the size of the HARQ codebook is determined or after the HARQ codebook is multiplexed with the first PUSCH repetition of the UL grant.

14. The apparatus of claim 8, wherein a Physical Uplink Control Channel (PUCCH) carrying one or more HARQ feedback bits of the at least one DL grant overlaps with a PUSCH of one of the at least one repetition of the UL grant.

15. The apparatus of claim 1, wherein the HARQ codebook corresponds to a HARQ Acknowledgement (ACK)/Negative ACK (NACK) codebook.

16. The apparatus of claim 1, wherein the at least one processor is configured to: before determining the size of the HARQ codebook, it is determined whether the difference exists between the total number of DL grants sent to the UE and the UL tDAI value of the UL grant.

17. A method of wireless communication at a User Equipment (UE), comprising:

receiving at least one Downlink (DL) grant after receiving an Uplink (UL) grant, the at least one DL grant being associated with a DL current downlink assignment index (cDAI) value and a DL total downlink assignment index (tDAI) value, the UL grant being associated with a UL tDAI value and scheduling a plurality of Physical Uplink Shared Channel (PUSCH) repetitions;

calculating a total number of DL grants sent to the UE based on the DL cDAI value;

adjusting the total number of DL grants if there is a difference between the total number of DL grants and the UL tDAI value; and

a hybrid automatic repeat request (HARQ) codebook is transmitted in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based on a total number of adjusted DL grants.

18. An apparatus for wireless communication at a network entity, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

transmitting at least one Downlink (DL) grant for a User Equipment (UE) after transmitting an Uplink (UL) grant, the at least one DL grant being associated with a DL current downlink assignment index (cDAI) value and a DL total downlink assignment index (tDAI) value, the UL grant being associated with a UL tDAI value and scheduling a plurality of Physical Uplink Shared Channel (PUSCH) repetitions; and

a hybrid automatic repeat request (HARQ) codebook is received in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value.

19. The apparatus of claim 18, in which the at least one processor is further configured:

one or more DL grants are sent prior to sending the UL grant, wherein the one or more DL grants are associated with a DL cDAI.

20. The apparatus of claim 19, wherein the DL cDAI associated with the one or more DL grants is different from a DL cDAI associated with the at least one DL grant.

21. The apparatus of claim 19, wherein the DL cDAI associated with the one or more DL grants is being reset prior to transmitting the at least one DL grant.

22. The apparatus of claim 18, wherein the at least one DL grant is at least one Physical Downlink Shared Channel (PDSCH) grant and the UL grant is a Physical Uplink Shared Channel (PUSCH) grant.

23. The apparatus of claim 18, in which the at least one processor is further configured:

at least one repetition of the UL grant is sent.

24. The apparatus of claim 23, wherein the HARQ codebook is associated with the at least one repetition of the UL grant.

25. The apparatus of claim 23, wherein the HARQ codebook is associated with a first repetition of the UL grant.

26. The apparatus of claim 25, wherein the at least one processor is further configured to:

the UL tDAI value is discarded after the HARQ codebook is received in the first repetition of the UL grant.

27. The apparatus of claim 23, wherein a Physical Uplink Control Channel (PUCCH) carrying one or more HARQ feedback bits of the at least one DL grant overlaps with a PUSCH of one of the at least one repetition of the UL grant.

28. The apparatus of claim 18, in which the at least one processor is further configured:

the tDAI value associated with the at least one DL grant is incremented for each previous DL grant.

29. The apparatus of claim 18, in which the at least one processor is further configured:

the tDAI value and the cDAI value associated with the at least one DL grant are incremented using the UL tDAI value as a reference.

30. A method of wireless communication at a network entity, comprising:

transmitting at least one Downlink (DL) grant for a User Equipment (UE) after transmitting an Uplink (UL) grant, the at least one DL grant being associated with a DL current downlink assignment index (cDAI) value and a DL total downlink assignment index (tDAI) value, the UL grant being associated with a UL tDAI value and scheduling a plurality of Physical Uplink Shared Channel (PUSCH) repetitions; and

a hybrid automatic repeat request (HARQ) codebook is received in at least one PUSCH repetition of the plurality of PUSCH repetitions, the size of the HARQ codebook being based at least on the UL tDAI value.