CN117296273A - HARQ-ACK multiplexing on PUSCH in UL CA - Google Patents

Abstract

Methods, apparatus, and computer readable media are provided for implementing HARQ-ACK multiplexing on PUSCH in UL CA. An example method includes: at least one PUSCH of the plurality of PUSCHs is selected in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more UL tDAI values. The example method further includes: one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs are transmitted to a network entity.

Description

HARQ-ACK multiplexing on PUSCH in UL CA

Cross Reference to Related Applications

This application claims the benefit and priority of the following applications: U.S. provisional application serial No. 63/186,772 submitted at 5/10 of 2021 and entitled "HARQ-ACK MULTIPLEXING ON PUSCH IN UL CA"; and U.S. non-provisional patent application serial No. 17/662,636 submitted at 5/9 of 2022 and entitled "HARQ-ACK MULTIPLEXING ON PUSCH IN UL CA", 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 communication systems with hybrid automatic repeat request (HARQ) Acknowledgement (ACK) multiplexing on a Physical Uplink Shared Channel (PUSCH).

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., along 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 enhancements 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 an aspect of the disclosure, methods, computer-readable media, and apparatuses at a User Equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to: at least one PUSCH of a plurality of PUSCHs is selected in which to multiplex one or more Uplink Control Information (UCI) bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more Uplink (UL) grants, the one or more UL grants comprising one or more UL total downlink assignment index (tDAI) values. The memory and the at least one processor coupled to the memory may be further configured to: the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs are transmitted to a network entity.

In another aspect of the disclosure, methods, computer-readable media, and apparatuses at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to: at least one of one or more Downlink (DL) grants or one or more UL grants including one or more UL tDAI values are sent to the UE. The memory and the at least one processor coupled to the memory may be further configured to: one or more UCI bits multiplexed with at least one PUSCH of a plurality of PUSCHs are received from the UE.

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 illustrating example communications between a UE and a base station.

Fig. 5 is a diagram illustrating example communications between a UE and a base station.

Fig. 6 is a diagram illustrating example communications between a UE and a base station.

Fig. 7 is a diagram illustrating example communications between a UE and a base station.

Fig. 8 is a diagram illustrating example communications between a UE and a base station.

Fig. 9 is a diagram illustrating example communications between a UE and a base station.

Fig. 10 is a diagram illustrating example communications between a UE and a base station.

Fig. 11 is a flow chart of a method of wireless communication.

Fig. 12 is a flow chart of a method of wireless communication.

Fig. 13 is a flow chart of a method of wireless communication.

Fig. 14 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus.

Fig. 15 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus.

Detailed Description

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is 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. It will be apparent, however, to one skilled in the art that 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 will now be described with reference to various apparatus and methods. These devices and methods will be 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, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names.

Accordingly, in one or more example embodiments, 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, and not limitation, 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 these 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.

While aspects and implementations are described in this application by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases may be produced in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may be produced via integrated chip implementations and other non-module component based devices (e.g., end user equipment, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing 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 variety of applicability of the described innovations. Implementations 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 aspects of the described innovations. In some practical arrangements, a device incorporating the described aspects and features may also include additional components and features for implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disassembled components, end-user devices, and the like, having different sizes, shapes, and configurations.

Fig. 1 is a schematic diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system, also referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G core (5 GC)). Base station 102 may include a macrocell (high power cellular base station) and/or a small cell (low power cellular base station). The macrocell includes a base station. Small cells include femto cells, pico cells, and micro cells.

A base station 102 configured for 4G LTE, which is collectively referred to as an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with the EPC 160 over a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR, which is collectively referred to as a next generation RAN (NG-RAN), may interface with the core network 190 over a second backhaul link 184. Base station 102 may perform, among other functions, one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio Access Network (RAN) sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly (e.g., through the EPC 160 or the core network 190) or indirectly through a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102 'may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. 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), which may provide services to a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include Uplink (UL) (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. Communication link 120 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 the spectrum of up to Y MHz bandwidth (e.g., 5, 10, 15, 20, 100, 400, etc., MHz) 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 for 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).

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 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). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, wiMedia, bluetooth, zigBee, 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 Access Point (AP) 150 that communicates with Wi-Fi Stations (STAs) 152 via a communication link 154 in, for example, a 5GHz unlicensed spectrum or the like. When communicating in the unlicensed spectrum, STA 152/AP 150 may perform Clear Channel Assessment (CCA) prior to communication to determine whether a channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5GHz, etc.) as used by the Wi-FiAP 150. The use of NR small cells 102' in unlicensed spectrum may improve coverage of the access network and/or increase capacity of the access network.

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 referred to as the (interchangeably) "sub-6GHz" (below 6 GHz) frequency band in various documents and articles. With respect to FR2, similar naming problems sometimes occur, FR2 is often (interchangeably) referred to in documents and articles as the "millimeter wave" frequency band, although it is different from the Extremely High Frequency (EHF) frequency band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" frequency 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 for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics and may therefore effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it should be understood that the term "sub-6Ghz" or the like (if used herein) may broadly represent frequencies that may be less than 6Ghz, frequencies that may be within FR1, or frequencies that may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term "millimeter wave" or the like (if used herein) may broadly represent frequencies that may include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or frequencies that may be within the EHF band.

Base station 102, whether small cell 102' or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, next generation node B (gNB), or another type of base station. Some base stations (such as the gNB 180) may operate in the conventional sub 6GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. Millimeter-wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short distance. The base station 180 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and/or antenna arrays) to facilitate beamforming.

The base station 180 may transmit the beamformed signals to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signals from the base station 180 in one or more receive directions 182 ". The UE 104 may also transmit the beamformed signals in one or more transmit directions to the base station 180. The base station 180 may receive the beamformed signals from the UEs 104 in one or more directions. The base station 180/UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180/UE 104. The transmit and receive directions for base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172.MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which serving gateway 166 itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to an IP service 176.IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and collecting eMBMS related charging information.

The core network 190 may include access and mobility management functions (AMFs) 192, other AMFs 193, session Management Functions (SMFs) 194, and User Plane Functions (UPFs) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, AMF 192 provides QoS flows and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. The UPF 195 provides UE IP address assignment as well as other functions. The UPF 195 is connected to an IP service 197.IP services 197 may include internet, intranet, IP Multimedia Subsystem (IMS), packet Switched (PS) streaming (PSs) services, and/or other IP services.

A base station 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 transmission-reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. 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, heart 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, handset, 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 in common and/or individually. 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 in common and/or individually. The network nodes may be implemented as base stations (i.e., aggregated base stations), decomposed base stations, integrated Access and Backhaul (IAB) nodes, relay nodes, sidelink nodes, and the like. The network entity may be implemented as a base station (i.e., an aggregated base station), or alternatively as a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a near real-time (near RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC in an exploded base station architecture.

Referring again to fig. 1, in some aspects, the UE 104 may include a PUSCH component 198. In some aspects, PUSCH component 198 may be configured to select at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more UL tDAI values. In some aspects, the PUSCH component 198 may be further configured to transmit one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs to the base station.

In certain aspects, the base station 180 may include a PUSCH component 199. In some aspects, PUSCH component 199 may be configured to transmit at least one of one or more DL grants or one or more UL grants to the UE, the one or more UL grants comprising one or more UL tDAI values. In some aspects, the PUSCH component 199 may be further configured to receive one or more UCI bits from the UE multiplexed with at least one PUSCH of the plurality of PUSCHs.

Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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 multiplexed (FDD) in which subframes within a set of subcarriers are dedicated to either DL or UL for a particular set of subcarriers (carrier system bandwidth) or time division multiplexed (TDD) in which subframes within a set of subcarriers are dedicated to both DL and UL for a particular set of subcarriers (carrier system bandwidth). In the example provided in fig. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexibly used between DL/UL, and subframe 3 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 symbols, UL symbols, 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). It should be noted that the following description also applies to a 5GNR frame structure as TDD.

Fig. 2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that 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 schemes. The digital scheme defines a subcarrier spacing (SCS) and effectively defines a symbol length/duration that is equal to 1/SCS.

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. Thus, 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 digital scheme μ=2 with a normal CP of 14 symbols per slot and 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 frame structure may be represented using a resource grid. Each slot includes Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) that extend for 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 an 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 in 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 located within symbol 4 of a particular subframe in the 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 together 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) that are not transmitted over the PBCH, and paging messages.

As shown in fig. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for a Physical Uplink Control Channel (PUCCH) and DM-RS for a Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous or the previous two symbols of the PUSCH. The PUCCHDM-RS may be transmitted in different configurations depending on whether the short PUCCH or the long PUCCH is transmitted and depending on the 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 of 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 an access network in communication with a UE 350. In DL, IP packets from EPC 160 are 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, segmentation and reassembly of RLC Service Data Units (SDUs), 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.

Transmit (TX) processor 316 and Receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, which includes the Physical (PHY) layer, may include error detection on the transport channel, forward Error Correction (FEC) encoding/decoding of the transport channel, interleaving, rate matching, mapping onto the 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 channel estimator 374 may be used to determine the coding and modulation scheme as well as 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 via 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 an RX processor 356. An RX processor 356 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by 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, the controller/processor 359 implementing 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 from the EPC 160. 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, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; 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.

TX processor 368 can select appropriate coding and modulation schemes and facilitate spatial processing using channel estimates derived by channel estimator 358 from reference signals or feedback transmitted by base station 310. 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 processed at the base station 310 in a manner similar to that 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 from UE 350. IP packets from controller/processor 375 may be provided to EPC 160. 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 PUSCH 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 PUSCH component 199 of fig. 1.

Example aspects provided herein provide for HARQ-ACK multiplexing on PUSCH. In some wireless communication systems, PUSCH selection based on grant type and CC index may be limited to one PUSCH slot. When the SCS of PUSCH is greater than that of PUCCH, there may be a plurality of PUSCHs overlapping one PUCCH in different slots. As shown in example 400 of fig. 4, PUSCH414A on CC1 may not overlap PUCCH412, while PUSCH414B, PUSCH414C and PUSCH 412D may overlap PUCCH 412. In one example, PUSCH414B, PUSCH414C and PUSCH414D may be associated with different grant types (such as configured grants or dynamic grants). PUSCH414A, PUSCH414B, PUSCH C and PUSCH414D may be on different Component Carriers (CCs) or the same CC. For example, PUCCH412 may be on CC0, PUSCH414A may be on CC1, PUSCH414B may be on CC2, PUSCH414C may be on CC3, and PUSCH414D may be on CC 4. PUSCH414A, PUSCH414B, PUSCH C and PUSCH414D may be associated with the same PUCCH group (e.g., the PUCCH group associated with PUCCH 412).

For UCI multiplexing, UCI in overlapping PUCCH transmission may be multiplexed into one PUCCH resource (which may be referred to as resource Z) on PUSCH within a PUCCH group. Multiplexing may be performed per PUCCH slot. If the PUCCH resource (resource Z) overlaps with at least one PUSCH, for UCI in resource Z that does not include a Scheduling Request (SR), a set of priority rules may be followed to multiplex UCI that does not include an SR into one PUSCH. For example, for HARQ-ACK bits in PUCCH412 that overlap PUSCH414B, PUSCH 414C and PUSCH414D, the priority rule set may be followed to multiplex the HARQ-ACK bits into one PUSCH. The PUSCH414B, PUSCH 414C and PUSCH414D overlapping the PUCCH412 may be collectively referred to as "overlapping PUSCH sets". An example set of priority rules may define that a first priority (which may be the highest priority) is associated with PUSCH with aperiodic CSI (a-CSI) as long as it overlaps with Z.

The example set of priority rules may also define that the second priority (which may be the second highest priority) is associated with the earliest (in time) PUSCH slots (based on the start of those slots). The example priority rule set may also define that a third priority (which may be the third highest priority) is associated with dynamically granting PUSCH if there are multiple earliest PUSCH slots overlapping with PUCCH resource (resource Z). In other words, the dynamic grant PUSCH may have a higher priority than the configured grant PUSCH or the semi-persistent PUSCH. The example set of priority rules may also define that a fourth priority (which may be a fourth highest priority) may be associated with PUSCH on a serving cell with a smaller serving cell index. In other words, PUSCH on a serving cell with a smaller serving cell index may have a higher priority than PUSCH on a serving cell with a larger serving cell index. The example priority rule set may also define that a fifth priority (which may be a fifth highest priority) may be associated with an earlier PUSCH. In other words, the earlier PUSCH may have a higher priority than the later PUSCH. For example, PUSCH414B may have a higher priority than PUSCH 414D.

Fig. 5 illustrates an example communication flow 500 between a UE 502 and a base station 504. As shown in fig. 5, the base station 504 may be a network entity. The network entity may be a network node. Base station 504 may be implemented as an aggregated base station, a decomposed base station, an Integrated Access and Backhaul (IAB) node, a relay node, a side-link node, or the like. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in an decomposed base station architecture, and may include one or more of a CU, DU, RU, near real-time (near RT) RAN Intelligent Controller (RIC), or non-real-time (non-RT) RIC.

As shown in fig. 5, a base station 504 may send one or more DL grants 506 to a UE 502. For example, the one or more DL grants 506 may include a first DL grant and a second DL grant, as further shown in fig. 6-10. One or more DL grants 506 may be transmitted using time domain resources in time frame 506A. In some aspects, the base station 504 may attempt to transmit one or more DL grants, but the UE 502 may fail to receive one or more of the one or more DL grants 506.

The base station 504 may also transmit one or more UL grants 508 to the UE 502. For example, the one or more UL grants 508 may include a first UL grant associated with a first TDAI value, a second UL grant associated with a second TDAI value, a third UL grant associated with a third TDAI value, and a fourth UL grant associated with a fourth TDAI value, as further shown in fig. 6-10. One or more UL grants 508 may be transmitted using time domain resources in time frame 508A. In some aspects, the base station 504 may attempt to transmit one or more UL grants, but the UE 502 may fail to receive one or more of the one or more UL grants 508.

The one or more DL grants 506 may schedule one or more PDSCH510. For example, a first DL grant may schedule a first PDSCH and a second DL grant may schedule a second PDSCH, as further shown in fig. 6-10. The base station 504 may accordingly transmit one or more PDSCH510 to the UE 502. One or more PDSCH510 may be transmitted using time domain resources in time frame 510A. In some aspects, the base station 504 may attempt to transmit one or more PDSCH, but the UE 502 may fail to receive one or more PDSCH of the one or more PDSCH510.

One or more UL grants may schedule one or more PUSCHs 512. For example, the first UL grant may schedule the first PUSCH, the second UL grant may schedule the second PUSCH, the third UL grant may schedule the third PUSCH, and the first UL grant may schedule the first PUSCH, as further shown in fig. 6-10. The base station 504 may accordingly transmit one or more PUSCHs 512 to the UE 502. The one or more PUSCHs 512 may be transmitted using time domain resources in the time frame 512A, and the one or more PUSCHs 512 may overlap in time with the PUCCH 514 (i.e., the time domain resources of the transmit PUCCH 514 in the time frame 514A). One or more PUSCHs 512 may be associated with the same PUCCH group including PUCCH 514.

In some wireless communication systems, after determining a host (host) PUSCH (i.e., a PUSCH on which PUCCH HARQ-ACKs are multiplexed based on a priority rule set), the UE 502 may follow the tDAI indicated in Downlink Control Information (DCI) of the scheduled PUSCH and multiplex the number of bits indicated by the tDAI. For example, as shown in example 600 of fig. 6, UE 502 may receive a first DL grant 602A and a second DL grant 602B, the first DL grant 602A may schedule a first PDSCH 604A, and the second DL grant may schedule a second PDSCH 604B. The first PDSCH 604A may be associated with one portion of the PUCCH 712 and the second PDSCH 604B may be associated with another portion of the PUCC 712. The UE 502 may also receive a first UL grant 606A associated with a first tDAI, a second UL grant 606B associated with a second tDAI, a third UL grant 606C associated with a third tDAI, and a fourth UL grant 606D associated with the first tDAI. The first UL grant 606A may schedule the first PUSCH614A, the second UL grant 606B may schedule the second PUSCH 614B, the third UL grant 606C may schedule the third PUSCH 614C, and the fourth UL grant 606D may schedule the fourth PUSCH 614D. The second PUSCH 614B, the third PUSCH 614C, and the fourth PUSCH 614D may overlap with the PUCCH 612. The first PUSCH614A, the second PUSCH 614B, the third PUSCH 614C, the fourth PUSCH 614D, and the PUCCH 612 may be on different CCs or the same CC. For example, PUCCH 612 may be on CC0, PUSCH614A may be on CC1, PUSCH 614B may be on CC2, PUSCH 614C may be on CC3, and PUSCH 614D may be on CC 4.

Because the first PUSCH 614A does not overlap with the PUCCH 612, the first PUSCH 614A may be excluded from the UCI multiplexing process. The UE 502 may determine the second PUSCH 614B, the third PUSCH 614C, and the fourth PUSCH 614D as overlapping PUSCH sets. In one example based on the priority rules described in connection with fig. 4, HARQ-ACKs may be multiplexed on PUSCH 614B on CC2, and the number of HARQ-ACK bits may follow a second tDAI associated with a second UL grant 606B. In other words, PUSCH 614B may be the host PUSCH selected by UE 502 (i.e., the PUSCH on which PUCCH HARQ-ACKs are multiplexed).

Based on the priority rules described in connection with fig. 4, to select the host PUSCH (i.e., the PUSCH on which PUCCH HARQ-ACKs are multiplexed), the UE 502 may determine the PUSCH set overlapping the PUCCH. However, if one DL grant is missed in a transmission, the base station 504 and the UE 502 may have different understandings about the PUSCH set. For example, the example 700 of fig. 7 may include a first DL grant 702A, a second DL grant 702B, a first PDSCH704A scheduled by the first DL grant 702A, a second PDSCH704B scheduled by the second DL grant 702B, a first UL grant 706A associated with a first tDAI, a second UL grant 706B associated with a second tDAI, a third UL grant 706C associated with a third tDAI, a fourth UL grant 706D associated with a fourth tDAI, a first PUSCH 714A scheduled by the first UL grant 706A, a second PUSCH714B scheduled by the second UL grant 706B, a third PUSCH714C scheduled by the third UL grant 706C, a fourth PUSCH714D scheduled by the third UL grant 706D, and PUCCHs associated with the first PDSCH704A and the second PDSCH 704B. As shown in fig. 7, the second DL grant 702B may be missed (i.e., not successfully received by the UE 502), which may result in the second PDSCH704B not being successfully scheduled for the UE 502. Based on the procedure shown in fig. 6, the base station 504 may expect the UE 502 to multiplex the HARQ-ACKs in the PUCCH712 on the second PUSCH714B, and the number of bits in the HARQ-ACKs may be based on the second tDAI. However, because the second PDSCH704B was not successfully scheduled for the UE 502, the UE 502 may not be aware of the portion 712A of the PUCCH712 associated with the second PDSCH 704B. Accordingly, UE 502 may exclude PUSCH714B from the multiplexing process because UE 502 may consider PUSCH714B as non-overlapping with PUCCH712. The UE 502 may determine the third PUSCH714C and the fourth PUSCH714D as overlapping PUSCH sets, and the UE 502 may exclude the PUSCH714B from the overlapping PUSCH sets. Then, the UE 502 may multiplex the HARQ-ACKs in the PUCCH712 on the third PUSCH714C, and the number of bits in the HARQ-ACKs may be based on the third tDAI, resulting in a difference between the expected of the base station 504 and the actual execution of the UE 502. In turn, this may lead to problems for communication between the base station 504 and the UE 502.

In another example, all DL grants may be missed and the UE 502 may not be able to determine the PUSCH overlapping the PUCCH. For example, example 800 of fig. 8 may include a first DL grant 802A, a second DL grant 802B, a first PDSCH804A scheduled by the first DL grant 802A, a second PDSCH 804B scheduled by the second DL grant 802B, a first UL grant 806A associated with a first tDAI, a second UL grant 806B associated with a second tDAI, a third UL grant 806C associated with a third tDAI, a fourth UL grant 806D associated with a fourth tDAI, a first PUSCH 814A scheduled by the first UL grant 806A, a second PUSCH 814B scheduled by the second UL grant 806B, a third PUSCH 814C scheduled by the third UL grant 806C, a fourth PUSCH 814D scheduled by the third UL grant 806D, and a PUCCH 812 associated with the first PDSCH804A and the second PDSCH 804B. As shown in fig. 8, the first DL grant 802A and the second DL grant 802B may miss, which may result in the first PDSCH804A and the second PDSCH 804B not being successfully scheduled for the UE 502. Based on the procedure shown in fig. 6, the base station 504 may expect the UE 502 to multiplex the HARQ-ACKs in the PUCCH 812 on one PUSCH (such as the second PUSCH 814B), and expect the number of bits in the HARQ-ACKs to be based on the tDAI (such as the second tDAI). However, because neither the first PDSCH804A nor the second PDSCH 804B is successfully scheduled for the UE 502, the UE 502 may not know when the PUCCH 812 starts or ends, and the UE 502 may not be able to determine the PUSCH set overlapping the PUCCH 812.

In some aspects, the UE 502 may not be able to determine the overlapping PUSCH set based on whether the PUSCH actually overlaps the PUCCH. Instead, the UE 502 may include all PUSCHs (whether or not actually overlapping PUCCH HARQ-ACKs) in the overlapping PUSCH set, as long as its tDAI associated with the UL grant scheduling PUSCH indicates a number of non-zero HARQ-ACK bits. In other words, while the UE 502 may not be able to determine whether the PUSCH overlaps with the PUCCH and then determine UCI multiplexing, the UE 502 may include all PUSCHs in the UCI multiplexing process as long as UL grants that schedule the PUSCH are associated with non-zero tDAI. For example, if tDAI indicates zero HARQ-ACK bits are multiplexed on the first PUSCH, the first PUSCH may be excluded from UCI multiplexing. If tDAI indicates multiplexing a non-zero number of HARQ-ACK bits on the second PUSCH, the second PUSCH is included in the overlapping PUSCH set, regardless of whether it actually overlaps with the determined PUCCHHARQ-ACK. In other words, if tDAI indicates multiplexing a non-zero number of HARQ-ACK bits on the second PUSCH, the second PUSCH is included in the UCI multiplexing procedure. For example, example 900 of fig. 9 may include a first DL grant 902A, a second DL grant 902B, a first PDSCH 904A scheduled by the first DL grant 902A, a second PDSCH 904B scheduled by the second DL grant 902B, a first UL grant 906A associated with a first tDAI, a second UL grant 906B associated with a second tDAI, a third UL grant 906C associated with a third tDAI, a fourth UL grant 906D associated with a fourth tDAI, a first PUSCH914A scheduled by the first UL grant 906A, a second PUSCH 914B scheduled by the second UL grant 906B, a third PUSCH 914C scheduled by the third UL grant 906C, a fourth PUSCH 914D scheduled by the fourth UL grant 906D, and a PUCCH 912 associated with the first PDSCH 904A and the second PDSCH 904B. As shown in fig. 9, the second DL grant 902B may be missed (i.e., not successfully received by the UE 502), which may result in the second PDSCH 904B not being successfully scheduled for the UE 502. In some aspects, the UE 502 may select the first PUSCH914A as the host PUSCH and multiplex one or more HARQ-ACK bits on the first PUSCH914A, the number of bits being based on a first tDAI in the first UL grant 906A scheduling the first PUSCH 914A. Even though the first DL grant 902A also misses, which may result in the first PDSCH 904A and the second PDSCH 904B not being successfully scheduled for the UE 502, the UE may still select the first PUSCH914A as the host PUSCH and multiplex one or more HARQ-ACK bits on the first PUSCH914A, the number of bits being based on the first tDAI in the first UL grant 906A that schedules the first PUSCH 914A.

In some aspects, if all DL grants are missed, the UE 502 may use the reference PUCCH HARQ-ACK resources in the PUCCH resource set to determine the overlapping PUSCH set. In some aspects, the reference PUCCH hharq-ACK resource may be the first resource in the PUCCH resource set or the resource with the longest duration. In some aspects, the reference PUCCH hharq-ACK resource may be a PUCCH that spans an entire slot or sub-slot. For example, example 1000 of fig. 10 may include a first DL grant 1002A, a second DL grant 1002B, a first PDSCH 1004A scheduled by the first DL grant 1002A, a second PDSCH1004B scheduled by the second DL grant 1002B, a first UL grant 1006A associated with a first tDAI, a second UL grant 1006B associated with a second tDAI, a third UL grant 1006C associated with a third tDAI, a fourth UL grant 1006D associated with a fourth tDAI, a first PUSCH1014A scheduled by the first UL grant 1006A, a second PUSCH 1014B scheduled by the second UL grant 1006B, a third PUSCH 1014C scheduled by the third UL grant 1006C, a fourth PUSCH 1014D scheduled by the fourth UL grant 1006D, and a PUCCH 1012 associated with the first PDSCH 1004A and the second PDSCH 1004B. As shown in fig. 10, the first DL grant 1002A and the second DL grant 1002B may miss, which may result in the first PDSCH 1004A and the second PDSCH1004B not being successfully scheduled for the UE 502. Because neither the first PDSCH 1004A nor the second PDSCH1004B was successfully scheduled for the UE 502, the UE 502 may not know when the PUCCH actually starts or ends. The UE 502 may then use the reference PUCCH 1012 to determine where the PUCCH starts and ends. Based on the reference PUCCH 1012, the ue 502 may determine that the second PUSCH 1014B, the third PUSCH 1014C, and the fourth PUSCH 1014D overlap with the reference PUCCH 1012. The UE 502 may multiplex HARQ-ACK bits on the second PUSCH 1014B, the number of bits being based on a second tDAI associated with scheduling UL grant 1006B of the second PUSCH 1014B. In some aspects, the reference PUCCH 1012 may be the first resource in the PUCCH resource set or the resource with the longest duration.

In some aspects, the UE 502 may multiplex HARQ-ACK bits in one slot, and the UE 502 may receive exactly one UL grant associated with a non-zero tDAI representing a non-zero number of HARQ bits (such as HARQ-ACK bits) multiplexed on the PUSCH. The HARQ-ACK bits may be multiplexed on PUSCH scheduled by the UL grant associated with the non-zero tDAI. In some aspects, UL grants in the same time slot may be associated with the same (i.e., same value) tDAI. In some aspects, in the case of a sub-slot based HARQ Codebook (CB), the UE 502 may multiplex the HARQ-ACK bits in one sub-slot and the UE 502 may receive exactly one UL grant associated with a non-zero tDAI. The HARQ-ACK bits may be multiplexed on PUSCH scheduled by the UL grant associated with the non-zero tDAI. In some aspects, UL grants in the same sub-slot may be associated with the same (i.e., same value) tDAI.

In some aspects, the UE 502 may receive more than one UL grant with a non-zero tDAI in one slot, and the UE 502 may multiplex PUCCH HARQ-ACKs on the PUSCH as follows: the PUSCH is scheduled by the UL grant associated with the tDAI indicating the maximum number of HARQ-ACK bits.

In some aspects, the UE 502 may receive more than one UL grant with a non-zero tDAI in one slot, and the UE 502 may multiplex PUCCH HARQ-ACKs on the PUSCH as follows: the PUSCH is scheduled by the last received (i.e., last received in time) or first received UL grant among UL grants of the scheduled PUSCH in the one slot. In some aspects, the UE 502 may decide to select a PUSCH in one slot on which to multiplex PUCCH HARQ-ACKs.

In some aspects, the UE 502 may take the maximum value of tDAI and multiplex it on each PUSCH. In some aspects, the UE 502 may consider mod 4 operation when taking the maximum value of tDAI. In some aspects, each PUSCH with a grant including tDAI may carry x bits of UCI, where tDAI is equal to x. For example, for a slot-based HARQ CB or a sub-slot-based HARQ CB, each PUSCH with a grant including tDAI may carry x bits of UCI. The UE 502 may choose between having one PUSCH per slot or sub-slot or having every PUSCH with a grant including tDAI (which may carry x bits of UCI, where tDAI is equal to x).

In some aspects, the UE 502 may consider PUCCH configuration when selecting PUSCH. For example, even if the UE 502 has missed DL grant/DCI, when the UE 502 selects a PUSCH on which to multiplex HARQ bits, the selected PUSCH may correspond to a scheduling scenario that may occur without missing DL grant/DCI. For example, if the UE selects PUSCH on which X bits are to be multiplexed, there may be PUCCH resources configured and overlapped with PUSCH that may carry X bits.

In some aspects, the timeline may be defined across PUSCHs scheduled in the same slot/sub-slot. In one non-limiting example, the quasi-grant for a second PUSCH having a tDAI different from the first PUSCH may be scheduled no later than a defined time, such as N4, from a beginning or ending symbol of the first PUSCH. In some aspects, the defined time (such as N4) may be the latest time that PUSCH with a different tDAI may be scheduled in a given slot/sub-slot, and the reference may be from the starting symbol of the first PUSCH with a tDAI. For example, the association between PUSCH and sub-slots may be defined based on the starting symbol of each PUSCH. In some aspects, the timeline may be applied across PUSCH scheduled by a UL grant indicating a non-zero tDAI. For example, the timeline may apply across all PUSCHs in a slot or sub-slot, independent of tDAI values associated with the PUSCHs, or independent of whether tDAI is configured in a UL grant that schedules the PUSCHs.

In some aspects, if at least one PUSCH (e.g., at least one PUSCH of PUSCHs 512) indicates that HARQ may be reported, but UE 502 has not detected any PDSCH with HARQ reporting in the same time slot as the PUSCH, UE 502 may select one of the PUSCHs (such as one PUSCH of PUSCHs 512) to multiplex HARQ bits thereon. In some aspects, if at least one PUSCH (e.g., at least one PUSCH of PUSCHs 512) indicates that HARQ may be reported, but UE 502 has not detected any PDSCH with HARQ reporting in the same time slot as the PUSCH, UE 502 may select one of the PUSCHs with a tDAI value indicating HARQ reporting to multiplex HARQ bits thereon.

Fig. 11 is a flow chart 1100 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502; apparatus 1402).

At 1102, the UE may select at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more UL tDAI values. For example, UE 502 may select at least one PUSCH of multiple PUSCHs 512 in which to multiplex one or more UCI bits, each PUSCH of multiple PUSCHs (such as PUSCH614A/B/C/D, PUSCH a/B/C/D, PUSCH814A/B/C/D, PUSCH914A/B/C/D or PUSCH 1014A/B/C/D) is associated with a UL grant (such as UL grant 606A/B/C/D, UL grant 806A/B/C/D, UL grant 806A/B/C/D, UL grant 906A/B/C/D, or UL grant 1006A/B/C/D), the one or more UL grants including one or more ULtDAI values. In some aspects, subsets of PUSCH may be associated with subsets of UL grants, respectively, each associated with a ULtDAI value. In some aspects, a subset of the one or more UL grants may be associated with one or more ULtDAI values, and another subset of the one or more UL grants may not be associated with ULtDAI values. In some aspects, 1102 may be performed by the selection component 1444 of fig. 14.

At 1104, the UE may send one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs to the base station. For example, the UE 502 may send one or more UCI bits multiplexed with at least one PUSCH of multiple PUSCHs (such as PUSCH614A/B/C/D, PUSCH 714A/B/C/D, PUSCH 814A/B/C/D, PUSCH 914A/B/C/D or PUSCH 1014A/B/C/D) to the base station 504. In some aspects, 1104 may be performed by PUSCH component 198. A base station may be a network entity such as a network node.

Fig. 12 is a flow chart 1200 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502; apparatus 1402).

At 1202, the UE may receive at least one of one or more DL grants or one or more UL grants from a base station. For example, the UE 502 may receive at least one of one or more DL grants 506 or one or more UL grants 508 from the base station 504. In some aspects 1202 may be performed by grant component 1442 of fig. 14. The base station may be a network node.

At 1204, the UE may select at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, each PUSCH of the plurality of PUSCHs may be associated with a UL grant, the one or more UL grants including one or more UL tDAI values. For example, UE 502 may select at least one PUSCH of multiple PUSCHs 512 in which to multiplex one or more UCI bits, each PUSCH of multiple PUSCHs (such as PUSCH614A/B/C/D, PUSCH a/B/C/D, PUSCH 814A/B/C/D, PUSCH 914A/B/C/D or PUSCH 1014A/B/C/D) is associated with a UL grant (such as UL grant 606A/B/C/D, UL grant 806A/B/C/D, UL grant 806A/B/C/D, UL grant 906A/B/C/D, UL grant 1006A/B/C/D), the one or more UL grants including one or more ULtDAI values. In some aspects, 1204 may be performed by selection component 1444 of fig. 14. In some aspects, at least one PUSCH of the plurality of PUSCHs at least partially overlaps with the PUCCH. In some aspects, at least one PUSCH of the plurality of PUSCHs may be associated with a non-zero ULtDAI value. In some aspects, the one or more UCI bits may be one or more HARQ-ACK bits. In some aspects, one or more HARQ-ACK bits may correspond to a PUCCH, such as PUCCH514, PUCCH612, PUCCH712, PUCCH812, PUCCH912, or PUCCH 1012. In some aspects, at least one PUSCH of the plurality of PUSCHs may be selected based on an associated UL tDAI value of UL grant (such as UL grant 506A/B/C/D, UL grant 606A/B/C/D, UL grant 806A/B/C/D, UL grant 806A/B/C/D, UL grant 906A/B/C/D or UL grant 1006A/B/C/D). In some aspects, the UE may detect at least one PUCCH based on at least one DL grant. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs based on a non-zero UL tDAI value associated with a UL grant associated with each of the at least one selected PUSCH. In some aspects, at least one PUSCH of the plurality of PUSCHs may be excluded based on a zero ULtDAI value, the zero ULtDAI value indicating that HARQ bits may not be multiplexed on PUSCHs associated with UL grants associated with each PUSCH of the at least one excluded PUSCH. For example, a zero ULtDAI value may indicate that HARQ bits may not be multiplexed on PUSCH scheduled by the UL grant associated with the zero ULtDAI value. In some aspects, the ULtDAI value may represent the number of HARQ-ACK bits. In some aspects, subsets of PUSCH may be associated with subsets of UL grants, respectively, each associated with a ULtDAI value. In some aspects, a subset of the one or more UL grants may be associated with one or more ULtDAI values, and another subset of the one or more UL grants may not be associated with ULtDAI values. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on: no dl dci with HARQ is detected in the same slot or the same sub-slot associated with at least one PUSCH of the plurality of PUSCHs; and the UE may select one PUSCH (such as any one of them) among the plurality of PUSCHs.

In some aspects, the UE may be scheduled to transmit PUSCH in a slot or sub-slot, and the UE may not receive DL grant associated with transmission of HARQ-ACKs in the associated slot or sub-slot. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on a reference PUCCH hharq-ACK resource in the PUCCH resource set. In some aspects, the reference PUCCH hharq-ACK resource may be a first resource in the PUCCH resource set. In some aspects, the reference PUCCH HARQ-ACK resources may include the longest duration resource in the PUCCH resource set. In some aspects, the reference PUCCH HARQ-ACK resource may be a PUCCH spanning an entire slot or sub-slot. In some aspects, the UE may receive one UL grant associated with a non-zero tDAI value in one time slot without receiving additional UL grants in the one time slot. In some aspects, the UE may be configured with a sub-slot based HARQ codebook, and the UE may receive one UL grant associated with a non-zero tDAI value in one sub-slot, and no additional UL grant is received in the one sub-slot, the PUSCH associated with the UL grant being associated with the one sub-slot based on a starting symbol of the PUSCH. In some aspects, one or more UL grant received in the same time slot may be associated with the same tDAI value. In some aspects, the UE may be configured with a sub-slot based HARQ codebook and one or more UL grants received in the same sub-slot may be associated with the same tDAI value. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on the maximum number associated with the UL tDAI value. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on: the last received UL grant associated with at least one PUSCH of the plurality of PUSCHs. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on: a first received UL grant associated with at least one PUSCH of the plurality of PUSCHs. In some aspects, the UE may multiplex the maximum value of tDAI values on each PUSCH of the plurality of PUSCHs. In some aspects, each PUSCH of the plurality of PUSCHs may carry an UCI of X bits, and X may be equal to an associated tDAI value. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based at least in part on a PUCCH configuration that represents a maximum number of bits that the PUCCH resource may be capable of carrying. In some aspects, the UE may select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits based on a defined timeline within a slot or sub-slot.

At 1206, the UE may send one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs to the base station. For example, the UE 502 may send one or more UCI bits multiplexed with at least one PUSCH of multiple PUSCHs (such as PUSCH 614A/B/C/D, PUSCH714A/B/C/D, PUSCH 814A/B/C/D, PUSCH914A/B/C/D or PUSCH 1014A/B/C/D) to the base station 504. In some aspects, 1206 may be performed by PUSCH component 1446 of fig. 14. A base station may be a network entity such as a network node.

Fig. 13 is a flow chart 1300 of a method of wireless communication. The method may be performed by a base station (e.g., base station 102/180, base station 504; apparatus 1502). A base station may be a network entity such as a network node.

At 1302, the base station may transmit at least one of one or more DL grants or one or more UL grants to the UE, the one or more UL grants including one or more UL tDAI values. For example, the base station 504 may transmit at least one of one or more DL grants 506 or one or more UL grants 508 to the UE 502, the one or more UL grants including one or more UL tDAI values. In some aspects, 1302 can be performed by grant component 1542 of fig. 15. In some aspects, one or more UL grant transmitted in the same time slot may be associated with the same tDAI value. In some aspects, the base station may be configured with a sub-slot based HARQ codebook, and the base station may transmit one UL grant associated with a non-zero tDAI value in one sub-slot without receiving additional UL grants in the one sub-slot. In some aspects, the PUSCH associated with the UL grant may be associated with the one sub-slot based on a starting symbol of the PUSCH. In some aspects, one or more UL grant transmitted in the same time slot may be associated with the same tDAI value. In some aspects, a base station may be configured with a sub-slot based HARQ codebook and one or more UL grants sent in the same sub-slot may be associated with the same tDAI value. In some aspects, a subset of UL grants may each be associated with a ULtDAI value. In some aspects, a subset of the one or more UL grants may be associated with one or more UL tDAI values, and another subset of the one or more UL grants may not be associated with UL tDAI values.

At 1304, the base station may receive one or more UCI bits from the UE multiplexed with at least one PUSCH of the plurality of PUSCHs. For example, the base station 504 may receive one or more UCI bits from the UE 502 multiplexed with at least one PUSCH of a plurality of PUSCHs (such as PUSCH 614A/B/C/D, PUSCH714A/B/C/D, PUSCH814A/B/C/D, PUSCH914A/B/C/D or PUSCH 1014A/B/C/D). In some aspects, 1304 may be performed by PUSCH component 1544 of fig. 15. In some aspects, at least one PUSCH of the plurality of PUSCHs may at least partially overlap with the PUCCH. In some aspects, at least one PUSCH of the plurality of PUSCHs may be associated with a non-zero ULtDAI value. In some aspects, the one or more UCI bits may be one or more HARQ-ACK bits. In some aspects, one or more HARQ-ACK bits may correspond to PUCCH. In some aspects, the ULtDAI value may represent the number of HARQ-ACK bits. In some aspects, each PUSCH of the plurality of PUSCHs may carry an UCI of X bits, and X may be equal to an associated tDAI value.

Fig. 14 is a schematic diagram 1400 illustrating an example of a hardware implementation for the apparatus 1402. The apparatus 1402 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1402 may include a cellular baseband processor 1404 (also referred to as a modem) coupled to a cellular RF transceiver 1422. In some aspects, the apparatus 1402 may also include one or more Subscriber Identity Module (SIM) cards 1420, an application processor 1406 coupled to a Secure Digital (SD) card 1408 and a screen 1410, a bluetooth module 1412, a Wireless Local Area Network (WLAN) module 1414, a Global Positioning System (GPS) module 1416, or a power source 1418. The cellular baseband processor 1404 communicates with the UE 104 and/or BS102/180 via a cellular RF transceiver 1422. The cellular baseband processor 1404 may include a computer readable medium/memory. The computer readable medium/memory may be non-transitory. The cellular baseband processor 1404 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 1404, causes the cellular baseband processor 1404 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 1404 when executing software. The cellular baseband processor 1404 also includes a receive component 1430, a communication manager 1432, and a transmit component 1434. The communications manager 1432 includes one or more of the illustrated components. Components within the communications manager 1432 may be stored in a computer-readable medium/memory and/or configured as hardware within the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 350 and may include at least one of a TX processor 368, an RX processor 356, and a controller/processor 359, and/or the memory 360. In one configuration, the apparatus 1402 may be a modem chip and include only the baseband processor 1404, while in another configuration, the apparatus 1402 may be an entire UE (e.g., see 350 of fig. 3) and include additional modules of the apparatus 1402.

The communication manager 1432 can include a grant component 1442 configured to receive at least one of one or more DL grants or one or more UL grants from a network entity, e.g., as described in connection with 1202 in fig. 12. The communication manager 1432 may further include a selection component 1444 that may be configured to select at least one PUSCH of the plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants including one or more ULtDAI values, as described in connection with 1102 in fig. 11 and 1204 in fig. 12. The communication manager 1432 may further include a PUSCH component 1446, which may be configured to transmit one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs to the base station, e.g., as described in connection with 1104 in fig. 11 and 1206 in 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 1402 may include various components configured for various functions. In one configuration, the apparatus 1402 (and in particular, the cellular baseband processor 1404) may include means for selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more ULtDAI values. The cellular baseband processor 1404 may also include means for transmitting, to the network entity, one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs. The cellular baseband processor 1404 may also include means for receiving at least one of one or more DL grants or one or more UL grants from a base station. The unit may be one or more of the components of the apparatus 1402 configured to perform the functions recited by the unit. As described above, the apparatus 1402 may include a TX processor 368, an RX processor 356, and a controller/processor 359. As such, 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. 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 1402 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 at least one of TX processor 316, RX processor 370, and controller/processor 375, and/or memory 376.

The communication manager 1532 can include a grant component 1542 that can transmit at least one of one or more DL grants or one or more UL grants to the UE, the one or more UL grants including one or more UL tDAI values, e.g., as described in connection with 1302 in fig. 13. The communication manager 1532 may also include a PUSCH component 1544 that may receive one or more UCI bits from the UE multiplexed with at least one PUSCH of the plurality of PUSCHs, e.g., as described in connection with 1304 in fig. 13.

The apparatus may include additional components to perform each of the blocks of the algorithm in the flowchart of fig. 13. Accordingly, each block in the flowchart of fig. 13 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 1502 may include various components configured for various functions. In one configuration, the apparatus 1502 (and in particular, the baseband unit 1504) may include means for selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values. The baseband unit 1504 may also include a unit for transmitting one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs to the base station. The elements may be one or more of the components of apparatus 1502 configured to perform the functions recited by the elements. As described above, the apparatus 1502 may include a TX processor 316, an RX processor 370, and a controller/processor 375. As such, 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 is to be understood that the specific order or hierarchy of blocks in the processes/flow diagrams disclosed is merely illustrative 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. Further, 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 implying an immediate time relationship or reaction. That is, these phrases (e.g., "when … …") do not imply an immediate action in response to or during the occurrence of an action, but rather simply imply: if the condition is met, the action will occur, but no specific or immediate time constraint for the action to occur is required. 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 multiples of a, multiples of B, or multiples of C. Specifically, 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" 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 or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The terms "module," mechanism, "" element, "" device, "and the like may not be a substitute for the term" unit. As such, no claim element is to be construed as a functional module 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 at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to: selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more UL tDAI values; and transmitting the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs to a network entity.

Aspect 2 is the apparatus of aspect 1, wherein at least one PUSCH of the plurality of PUSCHs at least partially overlaps with PUCCH.

Aspect 3 is the apparatus of any one of aspects 1-2, wherein at least one PUSCH of the plurality of PUSCHs is associated with a non-zero UL tDAI value, the non-zero UL tDAI value representing multiplexing a non-zero number of HARQ bits on the PUSCH.

Aspect 4 is the apparatus of any one of aspects 1-3, wherein the at least one processor coupled to the memory is further configured to: at least one of one or more DL grants or one or more UL grants are received from the network entity.

Aspect 5 is the apparatus of any one of aspects 1-4, wherein the one or more UCI bits are one or more HARQ-ACK bits.

Aspect 6 is the apparatus of any one of aspects 1-5, wherein the one or more HARQ-ACK bits correspond to PUCCH.

Aspect 7 is the apparatus of any one of aspects 1-6, wherein the at least one PUSCH of the plurality of PUSCHs is selected based on an associated UL grant UL tDAI value.

Aspect 8 is the apparatus of any one of aspects 1-7, wherein the UE detects at least one PUCCH based on at least one DL grant, and wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs based on: a non-zero ULtDAI value associated with UL grant associated with each of the at least one selected PUSCH.

Aspect 9 is the apparatus of any one of aspects 1-8, wherein at least one PUSCH of the plurality of PUSCHs is excluded based on a zero UL tDAI value, the zero UL tDAI value indicating that no HARQ bits are to be multiplexed on a PUSCH associated with a UL grant associated with each PUSCH of the at least one excluded PUSCH.

Aspect 10 is the apparatus according to any one of aspects 1-9, wherein the UL tDAI value represents a number of HARQ-ACK bits.

Aspect 11 is the apparatus of any one of aspects 1-10, wherein the UE is scheduled to transmit PUSCH in a slot or sub-slot, wherein the UE does not receive DL grant associated with transmission of HARQ-ACKs in the associated slot or sub-slot, and wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of puscharq-ACK resources in which the one or more UCI bits are to be multiplexed is selected based on a reference PUCCH hharq-ACK resource in the PUCCH resource set.

Aspect 12 is the apparatus of any one of aspect 11, wherein the reference PUCCH hharq-ACK resource is a first resource in the set of PUCCH resources.

Aspect 13 is the apparatus according to any one of aspects 1-12, wherein the reference PUCCH hharq-ACK resource comprises a longest duration resource in the set of PUCCH resources.

Aspect 14 is the apparatus according to any one of aspects 1-13, wherein the reference PUCCHHARQ-ACK resource is a PUCCH spanning an entire slot or sub-slot.

Aspect 15 is the apparatus of any one of aspects 1-14, wherein the UE receives one UL grant associated with a non-zero tDAI value in one time slot and does not receive additional UL grants in the one time slot.

Aspect 16 is the apparatus of any one of aspects 1-15, wherein the UE is configured with a sub-slot based HARQ codebook, and wherein the UE receives one UL grant associated with a non-zero tDAI value in one sub-slot and no additional UL grant in the one sub-slot, a PUSCH associated with the UL grant being associated with the one sub-slot based on a starting symbol of the PUSCH.

Aspect 17 is the apparatus of any one of aspects 1-16, wherein one or more UL grants received in the same time slot are associated with the same tDAI value.

Aspect 18 is the apparatus of any one of aspects 1-17, wherein the UE is configured with a sub-slot based HARQ codebook, and wherein one or more UL grants received in the same sub-slot are associated with the same tDAI value.

Aspect 19 is the apparatus of any one of aspects 1-18, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which the one or more UCI bits are to be multiplexed is selected based on a maximum number associated with the ULtDAI value.

Aspect 20 is the apparatus of any one of aspects 1-19, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: a last received UL grant associated with the at least one PUSCH of the plurality of PUSCHs.

Aspect 21 is the apparatus of any one of aspects 1-20, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: DL DCI with HARQ is not detected in the same slot or the same sub-slot associated with the at least one PUSCH of the plurality of PUSCHs.

Aspect 22 is the apparatus of any one of aspects 1-21, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: a first received UL grant associated with the at least one PUSCH of the plurality of PUSCHs.

Aspect 23 is the apparatus of any one of aspects 1-22, wherein the at least one processor coupled to the memory is further configured to: multiplexing a maximum value of the tDAI value on each PUSCH of the plurality of PUSCHs.

Aspect 24 is the apparatus of any one of aspects 1-23, wherein each PUSCH of the plurality of PUSCHs carries an UCI of X bits, X being equal to an associated tDAI value.

Aspect 25 is the apparatus of any one of aspects 1-24, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits is selected based at least in part on a PUCCH configuration representing a maximum number of bits that a PUCCH resource can carry.

Aspect 26 is the apparatus of any one of aspects 1-25, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which the one or more UCI bits are to be multiplexed is selected based on a defined timeline within a slot or sub-slot.

Aspect 27 is the apparatus of any one of aspects 1-26, further comprising: a transceiver coupled to the at least one processor.

Aspect 28 is 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, for a UE, at least one of one or more DL grants or one or more UL grants, the one or more UL grants comprising one or more UL tDAI values; and receiving one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs.

Aspect 29 is the apparatus of aspect 28, wherein at least one PUSCH of the plurality of PUSCHs at least partially overlaps with PUCCH.

Aspect 30 is the apparatus of any one of aspects 28-29, wherein at least one PUSCH of the plurality of PUSCHs is associated with a non-zero UL tDAI value.

Aspect 31 is the apparatus of any one of aspects 28-30, wherein the one or more UCI bits are one or more HARQ-ACK bits.

Aspect 32 is the apparatus of any one of aspects 28-31, wherein the one or more HARQ-ACK bits correspond to PUCCH.

Aspect 33 is the apparatus of any one of aspects 28-32, wherein the UL tDAI value represents a number of HARQ-ACK bits.

Aspect 34 is the apparatus of any one of aspects 28-33, wherein one or more UL grants sent in the same time slot are associated with the same tDAI value.

Aspect 35 is the apparatus of any one of aspects 28-34, wherein the network entity is configured with a sub-slot based HARQ codebook, and wherein the network entity transmits one UL grant associated with a non-zero tDAI value in one sub-slot, and does not receive additional UL grants in the one sub-slot, a PUSCH associated with the UL grant being associated with the one sub-slot based on a starting symbol of the PUSCH.

Aspect 36 is the apparatus of any one of aspects 28-35, wherein one or more UL grants sent in the same time slot are associated with the same tDAI value.

Aspect 37 is the apparatus of any one of aspects 28-36, wherein the network entity is configured with a sub-slot based HARQ codebook, and wherein one or more UL grants sent in the same sub-slot are associated with the same tDAI value.

Aspect 38 is the apparatus of any one of aspects 28-37, wherein each PUSCH of the plurality of PUSCHs carries an UCI of X bits, X being equal to an associated tDAI value.

Aspect 39 is the apparatus of any one of aspects 28-38, further comprising: a transceiver coupled to the at least one processor.

Aspect 40 is a method of wireless communication at a UE, comprising: selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more ULtDAI values; and transmitting the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs to a network entity.

Aspect 41 is the method of aspect 40, further comprising a method for implementing any of aspects 2-27.

Aspect 42 is an apparatus for wireless communication at a UE, comprising: means for selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more UL tDAI values; and means for transmitting the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs to a network entity.

Aspect 43 is the apparatus of aspect 42, further comprising a transceiver.

Aspect 44 is an apparatus for wireless communication according to any of aspects 42-43, further comprising means for implementing any of aspects 2-27.

Aspect 45 is a computer-readable medium storing computer-executable code at a UE, which when executed by a processor causes the processor to: selecting at least one PUSCH of a plurality of PUSCHs in which to multiplex one or more UCI bits, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more UL grants, the one or more UL grants comprising one or more ULtDAI values; and transmitting the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs to a network entity.

Aspect 46 is the computer-readable medium of aspect 45, wherein the code, when executed by the processor, causes the processor to implement any one of aspects 2-27.

Aspect 47 is a method of wireless communication at a network entity, comprising: transmitting, for a UE, at least one of one or more DL grants or one or more UL grants, the one or more UL grants comprising one or more UL tDAI values; and receiving one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs.

Aspect 48 is the method of aspect 47, further comprising a method for implementing any of aspects 29-39.

Aspect 49 is an apparatus for wireless communication at a network entity, comprising: means for transmitting at least one of one or more DL grants or one or more UL grants to the UE, the one or more UL grants comprising one or more UL tDAI values; and means for receiving one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs.

Aspect 50 is the apparatus of aspect 49, further comprising a transceiver.

Aspect 51 is an apparatus for wireless communication according to any of aspects 49-50, further comprising means for implementing any of aspects 29-39.

Aspect 52 is a computer-readable medium at a network entity storing computer-executable code which, when executed by a processor, causes the processor to: transmitting, for a UE, at least one of one or more DL grants or one or more UL grants, the one or more UL grants comprising one or more ULtDAI values; and receiving one or more UCI bits multiplexed with at least one PUSCH of the plurality of PUSCHs.

Aspect 53 is the computer-readable medium of aspect 52, wherein the code, when executed by the processor, causes the processor to implement any of aspects 29-39.

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:

selecting at least one Physical Uplink Shared Channel (PUSCH) of a plurality of PUSCHs in which one or more Uplink Control Information (UCI) bits are to be multiplexed, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more Uplink (UL) grants, the one or more UL grants comprising one or more UL total downlink assignment index (tDAI) values; and

the one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs are transmitted to a network entity.

2. The apparatus of claim 1, wherein at least one PUSCH of the plurality of PUSCHs at least partially overlaps with a Physical Uplink Control Channel (PUCCH).

3. The apparatus of claim 1, wherein at least one PUSCH of the plurality of PUSCHs is associated with a non-zero UL tDAI value representing multiplexing a non-zero number of hybrid automatic repeat request (HARQ) bits on the PUSCH.

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

at least one of one or more Downlink (DL) grants or one or more UL grants are received from the network entity.

5. The apparatus of claim 1, wherein the one or more UCI bits are one or more hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) bits.

6. The apparatus of claim 5, wherein the one or more HARQ-ACK bits correspond to a Physical Uplink Control Channel (PUCCH).

7. The apparatus of claim 1, wherein the at least one PUSCH of the plurality of PUSCHs is selected based on an associated UL grant UL tDAI value.

8. The apparatus of claim 1, wherein the UE detects at least one Physical Uplink Control Channel (PUCCH) based on at least one DL grant, and wherein the at least one processor coupled to the memory is further configured to:

selecting the at least one PUSCH of the plurality of PUSCHs based on: a non-zero UL tDAI value associated with a UL grant associated with each of the at least one selected PUSCH.

9. The apparatus of claim 8, wherein at least one PUSCH of the plurality of PUSCHs is excluded based on a zero UL tDAI value, the zero UL tDAI value indicating that no hybrid automatic repeat request (HARQ) bits are to be multiplexed on a PUSCH associated with a UL grant associated with each PUSCH of the at least one excluded PUSCH.

10. The apparatus of claim 8, wherein the UL tDAI value represents a number of hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) bits.

11. The apparatus of claim 1, wherein the UE is scheduled to transmit PUSCH in a slot or sub-slot, wherein the UE does not receive a DL grant associated with transmission of a hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) in an associated slot or sub-slot, and wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which the one or more UCI bits are to be multiplexed is selected based on a reference PUCCH HARQ-ACK resource in a Physical Uplink Control Channel (PUCCH) resource set.

12. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resource is a first resource in the set of PUCCH resources.

13. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resources comprise longest duration resources in the set of PUCCH resources.

14. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resource is a PUCCH spanning an entire slot or sub-slot.

15. The apparatus of claim 1, wherein the UE receives one UL grant associated with a non-zero tDAI value in one time slot and does not receive additional UL grants in the one time slot.

16. The apparatus of claim 1, wherein the UE is configured with a sub-slot based hybrid automatic repeat request (HARQ) codebook, and wherein the UE receives one UL grant associated with a non-zero tDAI value in one sub-slot and no additional UL grant in the one sub-slot, a PUSCH associated with the UL grant being associated with the one sub-slot based on a starting symbol of the PUSCH.

17. The apparatus of claim 1, wherein one or more UL grants received in a same time slot are associated with a same tDAI value.

18. The apparatus of claim 1, wherein the UE is configured with a sub-slot based hybrid automatic repeat request (HARQ) codebook, and wherein one or more UL grants received in a same sub-slot are associated with a same tDAI value.

19. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which the one or more UCI bits are to be multiplexed is selected based on a maximum number associated with the UL tDAI value.

20. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: a last received UL grant associated with the at least one PUSCH of the plurality of PUSCHs.

21. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: no Downlink (DL) Downlink Control Information (DCI) with a hybrid automatic repeat request (HARQ) is detected in the same slot or the same sub-slot associated with the at least one PUSCH of the plurality of PUSCHs.

22. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits based on: a first received UL grant associated with the at least one PUSCH of the plurality of PUSCHs.

23. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to: multiplexing a maximum value of the tDAI value on each PUSCH of the plurality of PUSCHs.

24. The apparatus of claim 1, wherein each PUSCH of the plurality of PUSCHs carries an UCI of X bits, X being equal to an associated tDAI value.

25. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which to multiplex the one or more UCI bits is selected based at least in part on a Physical Uplink Control Channel (PUCCH) configuration that represents a maximum number of bits that a PUCCH resource can carry.

26. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to: the at least one PUSCH of the plurality of PUSCHs in which the one or more UCI bits are to be multiplexed is selected based on a defined timeline within a slot or sub-slot.

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

28. 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, for a User Equipment (UE), at least one of one or more Downlink (DL) grants or one or more Uplink (UL) grants, the one or more UL grants comprising one or more UL total downlink assignment index (tDAI) values; and

one or more Uplink Control Information (UCI) bits multiplexed with at least one Physical Uplink Shared Channel (PUSCH) of a plurality of PUSCHs are received.

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

selecting at least one Physical Uplink Shared Channel (PUSCH) of a plurality of PUSCHs in which one or more Uplink Control Information (UCI) bits are to be multiplexed, the one or more PUSCHs of the plurality of PUSCHs being associated with one or more Uplink (UL) grants, the one or more UL grants comprising one or more UL total downlink assignment index (tDAI) values; and

The one or more UCI bits multiplexed with the at least one PUSCH of the plurality of PUSCHs are transmitted to a network entity.

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

transmitting, for a User Equipment (UE), at least one of one or more Downlink (DL) grants or one or more Uplink (UL) grants, the one or more UL grants comprising one or more UL total downlink assignment index (tDAI) values; and

one or more Uplink Control Information (UCI) bits multiplexed with at least one Physical Uplink Shared Channel (PUSCH) of a plurality of PUSCHs are received.