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

Abstract

A method, an apparatus, and a computer-readable medium are provided to enable HARQ-ACK multiplexing on a PUSCH in UL CA. The exemplary method includes selecting at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, and the one or more UL grants include one or more UL tDAI values. The exemplary method further includes transmitting to a network entity the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of and priority to U.S. Provisional Application No. 63/186,772, filed May 10, 2021, entitled "HARQ-ACK MULTIPLEXING ON PUSCH IN UL CA," and U.S. Non-Provisional Application No. 17/662,636, filed May 9, 2022, entitled "HARQ-ACK MULTIPLEXING ON PUSCH IN UL CA," which applications are expressly incorporated by reference herein in their entireties.

The present disclosure relates generally to communication systems, and more particularly to wireless communication systems using hybrid automatic repeat request (HARQ) acknowledgment (ACK) multiplexing on a physical uplink shared channel (PUSCH).

Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunications standards that utilize these technologies.

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, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in 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 select at least one of a plurality of PUSCHs for multiplexing one or more uplink control information (UCI) bits therein, where one or more of the plurality of PUSCHs are associated with one or more uplink (UL) grants, and the one or more UL grants include 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 transmit the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs to a network entity.

In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in 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 transmit at least one of one or more downlink (DL) grants or one or more UL grants to the UE, where the one or more UL grants include one or more UL tDAI values. The memory and the at least one processor coupled to the memory may be further configured to receive, from the UE, one or more UCI bits multiplexed with at least one of the multiple PUSCHs.

To the accomplishment of the foregoing and related ends, the 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 the various aspects may be employed and the description is intended to include all such aspects and their equivalents.

FIG. 1 illustrates an example of a wireless communication system and access network. FIG. 2 illustrates an example of a first frame, in accordance with various aspects of the present disclosure. FIG. 1 illustrates an example of a DL channel in a subframe, in accordance with various aspects of the present disclosure. FIG. 13 illustrates an example of a second frame, in accordance with various aspects of the present disclosure. FIG. 1 illustrates an example of a UL channel in a subframe, in accordance with various aspects of the present disclosure. FIG. 1 illustrates an example of a base station and user equipment (UE) in an access network. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. A diagram showing communication between a UE and a base station. 1 is a flow chart of a method of wireless communication. 1 is a flow chart of a method of wireless communication. 1 is a flow chart of a method of wireless communication. FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus. FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus.

The detailed description set forth below with reference to the accompanying 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. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

Below, several aspects of a telecommunications system are presented with reference to various apparatus and methods that are described in the detailed description that follows 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 on the particular application and design constraints imposed on the overall system.

By way of example, an element or any portion of an element or any combination of elements may be implemented as a "processing system" including 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, systems on chips (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

Although aspects and implementations are described in this application by illustrating some examples, those skilled in the art will understand that additional implementations and use cases may arise in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and/or applications may arise with integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described innovations may arise. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involves several components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders/summers, etc.) for analog and digital purposes. It is intended that the innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or non-aggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

Figure 1 illustrates an example of a wireless communication system and access network 100. The 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., 5G core (5GC)). The base station 102 may include a macro cell (high power cellular base station) and/or a small cell (low power cellular base station). The macro cell includes a base station. The small cell includes a femto cell, a pico cell, and a micro cell.

A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 through a second backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions: forwarding of user data, encryption and decryption of radio channels, 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 service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) via 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 stations 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a 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 including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home evolved Node B (eNB) (HeNB) that may serve a restricted group called a Closed Subscriber Group (CSG). A communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102, and/or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The 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 over one or more carriers. The base station 102/UE 104 may use spectrum with bandwidths of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in carrier aggregation with up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation 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).

Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL/UL WWAN spectrum. The D2D communication links 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 various 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 further include a Wi-Fi access point (AP) 150 in communication with a Wi-Fi station (STA) 152, such as in the 5 GHz unlicensed frequency spectrum, via a communication link 154. When communicating in the unlicensed frequency spectrum, the STA 152/AP 150 may perform a clear channel assessment (CCA) before communicating to determine if a channel is available.

The small cell 102' may operate in licensed and/or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell 102' may utilize NR and may use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. A small cell 102' utilizing NR in the unlicensed frequency spectrum may provide increased coverage to and/or increase the capacity of the access network.

The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency/wavelength. For 5G NR, two initial operating bands have been identified with the frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues can arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though it is distinct from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunications Union (ITU).

Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and/or FR2 characteristics, and thus, in effect, extend the features of FR1 and/or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be in FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "mmWave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be in FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be in the EHF band.

The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as the gNB 180, may communicate with the UE 104 and operate in the conventional sub-6 GHz spectrum, at mmWave frequencies, and/or at quasi-mmWave frequencies. When the gNB 180 operates in mmWave frequencies or quasi-mmWave frequencies, the gNB 180 may be referred to as a mmWave base station. The mmWave base station 180 may use beamforming 182 with the UE 104 to compensate for path loss and short distances. 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 a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182''. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive 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 direction and receive direction for the base station 180 may be the same or different. The transmit direction and receive direction for the UE 104 may be the same or different.

The 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. The MME 162 may be in communication 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, the MME 162 handles bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself 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 the BM-SC 170 are connected to the IP Services 176. The IP services 176 may include Internet, intranet, 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 in the Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to base stations 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start/stop) and collecting eMBMS-related charging information.

The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with an integrated 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, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, intranets, 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, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit 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 the UE 104 include a mobile phone, a smartphone, 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 electric meter, a gas pump, a large or small cooking appliance, a health management device, an implant, a sensor/actuator, a display, or any other similar function device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices in a device constellation configuration, etc. One or more of these devices may collectively access the network and/or individually access the network. In some scenarios, the term UE may also be applied to one or more companion devices in a device constellation configuration, etc. One or more of these devices may collectively access the network and/or individually access the network. A network node may be implemented as a base station (i.e., an aggregated base station), a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. 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 a disaggregated base station architecture.

Referring again to FIG. 1, in some aspects, the UE 104 may include a PUSCH component 198. In some aspects, the PUSCH component 198 may be configured to select at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values. In some aspects, the PUSCH component 198 may be further configured to transmit the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs to the base station.

In some aspects, the base station 180 may include a PUSCH component 199. In some aspects, the 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, where the one or more UL grants include one or more UL tDAI values. In some aspects, the PUSCH component 199 may be further configured to receive from the UE one or more UCI bits multiplexed with at least one of the multiple PUSCHs.

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

Figure 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. Figure 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or may be time division duplex (TDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the example given by FIG. 2A, FIG. 2C, the 5G NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 is configured with slot format 1 (with all UL). Subframes 3 and 4 are shown with slot formats 1 and 28, respectively, but any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL, UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI) or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure, which is TDD.

2A-2D show a frame structure, the aspects of the present disclosure may be applicable to other wireless communication techniques that may have different frame structures and/or different channels. A frame (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may include one or more time slots. A 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. With a normal CP, each slot may include 14 symbols, and with an extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. 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 called Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-limited scenarios, limited to single stream transmission). The number of slots in a subframe is based on the CP and numerology. The numerology defines the subcarrier spacing (SCS), which effectively defines the symbol length/duration, which is equal to 1/SCS.

In the normal CP (14 symbols/slot), the different numerologies μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. In the extended CP, numerology 2 allows 4 slots per subframe. Thus, for the normal CP and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. The subcarrier spacing may be equal to 2 ^μ *15 kHz, where μ is numerology 0-4. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz and numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely proportional to the subcarrier spacing. Figures 2A-2D give an example of a normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

The resource grid can be used to represent the frame structure. Each time slot contains a resource block (RB), also called a physical RB (PRB), that spans 12 consecutive subcarriers. The resource grid is divided into multiple 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 reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (denoted as R for one particular configuration, but other DM-RS configurations are possible), and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam improvement RS (BRRS), and phase tracking RS (PT-RS).

Figure 2B shows an example of various DL channels in a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE containing 6 RE groups (REGs), each REG containing 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in 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 PDCCH monitoring opportunities in the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be at higher and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe/symbol timing and physical layer identification information. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as the system information block (SIB), and paging messages.

As shown in FIG. 2C, some of the REs carry DM-RS (denoted 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 the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

Figure 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be located as shown. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and/or negative ACKs (NACKs)). The PUSCH carries data and may be further used to carry buffer status reports (BSRs), power headroom reports (PHRs), and/or UCI.

Figure 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements Layer 3 and Layer 2 functions. 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. The controller/processor 375 provides RRC layer functions related to broadcasting 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 related to header compression/decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to forwarding of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), separation of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding/decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation/demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles 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 coded and modulated symbols may then be separated 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 domains, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. The channel estimates may be derived from a reference signal 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 TX 318. Each transmitter TX 318 may modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

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

The controller/processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 performs separation between transport and logical channels, packet reassembly, decryption, 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 with respect to DL transmission by base station 310, controller/processor 359 provides RRC layer functions related to system information (e.g., MIB, SIB) collection, RRC connection, and measurement reporting; PDCP layer functions related to header compression/decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to transfer of higher layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, separation of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

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

UE transmissions are processed at the base station 310 in a manner similar to that described for the receiver functions at the UE 350. Each receiver RX 318 receives signals through its respective antenna 320. Each receiver RX 318 recovers the information modulated onto the 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. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 performs separation between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects associated with the PUSCH component 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects associated with the PUSCH component 199 of FIG. 1.

Example aspects provided herein provide HARQ-ACK multiplexing on a PUSCH. In some wireless communication systems, PUSCH selection based on grant type and CC index may be limited to within one PUSCH slot. When the SCS of the PUSCH is greater than the SCS of the PUCCH, there may be multiple PUSCHs in different slots that overlap with one PUCCH. As shown in example 400 of FIG. 4, PUSCH 414A on CC1 may not overlap with PUCCH 412, while PUSCH 414B, PUSCH 414C, and PUSCH 414D may overlap with PUCCH 412. In one example, PUSCH 414B, PUSCH 414C, and PUSCH 414D may be associated with different grant types, such as configured grants or dynamic grants. PUSCH 414A, PUSCH 414B, PUSCH 414C, and PUSCH 414D may be on different component carriers (CCs) or on the same CC. For example, PUCCH 412 may be on CC0, PUSCH 414A may be on CC1, PUSCH 414B may be on CC2, PUSCH 414C may be on CC3, and PUSCH 414D may be on CC4. PUSCH 414A, PUSCH 414B, PUSCH 414C, and PUSCH 414D may be associated with the same PUCCH group, e.g., the PUCCH group associated with PUCCH 412.

For UCI multiplexing within a PUCCH group on a PUSCH, UCI in overlapped PUCCH transmissions may be multiplexed into one PUCCH resource (sometimes referred to as resource Z). The multiplexing may be performed per PUCCH slot. If a PUCCH resource (resource Z) overlaps with at least one PUSCH for UCI in resource Z that does not contain a scheduling request (SR), the UCI that does not contain a SR may be multiplexed into one PUSCH according to a set of priority rules. For example, for HARQ-ACK bits in PUCCH 412 that overlap with PUSCH 414B, PUSCH 414C, and PUSCH 414D, the HARQ-ACK bits may be multiplexed into one PUSCH according to a set of priority rules. PUSCH 414B, PUSCH 414C, and PUSCH 414D that overlap with PUCCH 412 may be collectively referred to as the "set of overlapping PUSCHs." An example set of priority rules may define that a first priority, which may be the highest priority, is associated with a PUSCH with aperiodic CSI (A-CSI) (as long as the PUSCH overlaps with Z).

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

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. The base station 504 may be implemented as an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. The network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near-Real-Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real-Time (Non-RT) RIC.

As shown in FIG. 5, the base station 504 may transmit one or more DL grants 506 to the 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 FIGS. 6-10. The one or more DL grants 506 may be transmitted using time domain resources in a time frame 506A. In some aspects, the base station 504 may attempt to transmit the one or more DL grants, but the UE 502 may fail to receive one or more DL grants in the one or more DL grants 506.

The base station 504 may further 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-FIG. 10. The one or more UL grants 508 may be transmitted using time domain resources in the 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 UL grants in the one or more UL grants 508.

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

The one or more UL grants may schedule one or more PUSCHs 512. For example, as further shown in Figures 6-10, the first UL grant may schedule a first PUSCH, the second UL grant may schedule a second PUSCH, the third UL grant may schedule a third PUSCH, and the fourth UL grant may schedule a fourth PUSCH. Thus, the base station 504 may 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 that may overlap in time with the PUCCH 514 (i.e., the time domain resources in the time frame 514A in which the PUCCH 514 is transmitted). The one or more PUSCHs 512 may be associated with the same PUCCH group that includes the PUCCH 514.

In some wireless communication systems, after the host PUSCH (i.e., the PUSCH on which the PUCCH HARQ-ACK is multiplexed based on a set of priority rules) is determined, the UE 502 may multiplex the number of bits indicated by the tDAI according to the tDAI indicated in the downlink control information (DCI) that schedules the PUSCH. For example, as shown in the example 600 of FIG. 6, the UE 502 may receive a first DL grant 602A and a second DL grant 602B, where 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 a portion of the PUCCH 712 and the second PDSCH 604B may be associated with another portion of the PUCCH 712. The UE 502 may further 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 a fourth tDAI. The first UL grant 606A may schedule a first PUSCH 614A, the second UL grant 606B may schedule a second PUSCH 614B, the third UL grant 606C may schedule a third PUSCH 614C, and the fourth UL grant 606D may schedule a fourth PUSCH 614D. The second PUSCH 614B, the third PUSCH 614C, and the fourth PUSCH 614D may overlap with the PUCCH 612. The first PUSCH 614A, 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, the PUCCH 612 may be on CC0, the PUSCH 614A may be on CC1, the PUSCH 614B may be on CC2, the PUSCH 614C may be on CC3, and the PUSCH 614D may be on CC4.

Because the first PUSCH 614A does not overlap with the PUCCH 612, the first PUSCH 614A may be excluded from the UCI multiplexing procedure. The second PUSCH 614B, the third PUSCH 614C, and the fourth PUSCH 614D may be determined by the UE 502 to be a set of overlapping PUSCHs. In one example based on the priority rules described with respect to FIG. 4, the HARQ-ACK may be multiplexed on the PUSCH 614B on CC2, and the number of HARQ-ACK bits may follow the second tDAI associated with the second UL grant 606B. In other words, the PUSCH 614B may be the host PUSCH selected by the UE 502 (i.e., the PUSCH on which the PUCCH HARQ-ACK is multiplexed).

Based on the priority rules described with respect to FIG. 4, to select the host PUSCH (i.e., the PUSCH on which the PUCCH HARQ-ACK is multiplexed), the UE 502 may determine a set of PUSCHs that overlap with the PUCCH. However, if one DL grant is missing in the transmission, the base station 504 and the UE 502 may have different understandings regarding the set of PUSCHs. For example, the example 700 of FIG. 7 includes a first DL grant 702A, a second DL grant 702B, a first PDSCH 704A scheduled by the first DL grant 702A, a second PDSCH 704B 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, and a fourth UL grant 706D associated with a fourth tDAI. 7, the second DL grant 702B may include a first PUSCH 714A scheduled by the first UL grant 706A, a second PUSCH 714B scheduled by the second UL grant 706B, a third PUSCH 714C scheduled by the third UL grant 706C, a fourth PUSCH 714D scheduled by the fourth UL grant 706D, and a PUCCH 712 associated with the first PDSCH 704A and the second PDSCH 704B. As shown in FIG. 7, the second DL grant 702B may be missing (i.e., not successfully received by the UE 502), which may cause the second PDSCH 704B to not be 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-ACK in the PUCCH 712 on the second PUSCH 714B, and the number of bits in the HARQ-ACK may be based on the second tDAI. However, since the second PDSCH 704B was not successfully scheduled for the UE 502, the UE 502 may not be aware of the portion 712A of the PUCCH 712 associated with the second PDSCH 704B. Thus, the UE 502 may exclude the PUSCH 714B from the multiplexing procedure because the UE 502 may view the PUSCH 714B as not overlapping with the PUCCH 712. The third PUSCH 714C and the fourth PUSCH 714D may be determined by the UE 502 to be a set of overlapping PUSCHs, and the PUSCH 714B may be excluded from the set of overlapping PUSCHs by the UE 502. The UE 502 may then multiplex the HARQ-ACK in the PUCCH 712 onto the third PUSCH 714C, and the number of bits in the HARQ-ACK may be based on the third tDAI, thus creating a difference between the base station 504's prediction and the UE 502's actual performance. This in turn may cause problems for communication between the base station 504 and the UE 502.

In another example, all DL grants may be missing and the UE 502 may not be able to determine a PUSCH that overlaps with a PUCCH. For example, the example 800 of FIG. 8 includes a first DL grant 802A, a second DL grant 802B, a first PDSCH 804A 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, and a fourth UL grant 806D associated with a fourth tDAI. The PUCCH 812 may include a fourth UL grant 806D scheduled by the first UL grant 806A, 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 fourth UL grant 806D, and a PUCCH 812 associated with the first PDSCH 804A and the second PDSCH 804B. As shown in FIG. 8, the first DL grant 802A and the second DL grant 802B may be missing, which may cause the first PDSCH 804A and the second PDSCH 804B to not be successfully scheduled for the UE 502. Based on the procedure shown in FIG. 6, the base station 504 may expect that the UE 502 will multiplex the HARQ-ACK in the PUCCH 812 onto one PUSCH, such as the second PUSCH 814B, and the number of bits in the HARQ-ACK will be based on a tDAI, such as the second tDAI. However, because neither the first PDSCH 804A nor the second PDSCH 804B was successfully scheduled for the UE 502, the UE 502 may not know when the PUCCH 812 starts or ends, and the set of PUSCHs that overlap with the PUCCH 812 may not be determined by the UE 502.

In some aspects, UE 502 may not determine the set of overlapping PUSCHs based on whether the PUSCHs actually overlap with the PUCCH. Instead, all PUSCHs may be included in the set of overlapping PUSCHs by UE 502, regardless of whether they actually overlap with the PUCCH HARQ-ACK, as long as their tDAI associated with the UL grant that schedules the PUSCH indicates a non-zero number of HARQ-ACK bits. In other words, UE 502 may not determine whether a PUSCH overlaps with a PUCCH and then determine UCI multiplexing, but UE 502 may include all PUSCHs in the UCI multiplexing procedure as long as the UL grant that schedules the PUSCH is associated with a non-zero tDAI. For example, if the tDAI indicates that a zero HARQ-ACK bit is multiplexed on the first PUSCH, the first PUSCH may be excluded in the UCI multiplexing procedure. If the tDAI indicates that a non-zero number of HARQ-ACK bits are multiplexed on the second PUSCH, the second PUSCH is included in the set of overlapping PUSCHs, regardless of whether it actually overlaps with the determined PUCCH HARQ-ACK. In other words, if the tDAI indicates that a non-zero number of HARQ-ACK bits are multiplexed on the second PUSCH, the second PUSCH is included in the UCI multiplexing procedure. For example, the example 900 of FIG. 9 includes 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, and a fourth UL grant 906D associated with a fourth tDAI. 9, the second DL grant 902B may include a first PUSCH 914A 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 missing (i.e., not successfully received by the UE 502), which may cause the second PDSCH 904B to not be successfully scheduled for the UE 502. In some aspects, the UE 502 may select the first PUSCH 914A as the hosted PUSCH and multiplex one or more HARQ-ACK bits onto the first PUSCH 914A, where the number of bits is based on the first tDAI in the first UL grant 906A that schedules the first PUSCH 914A. Even if the first DL grant 902A is also missing (which may cause the first PDSCH 904A and the second PDSCH 904B to not be successfully scheduled for the UE 502), the UE may nevertheless select the first PUSCH 914A as the hosted PUSCH and multiplex one or more HARQ-ACK bits onto the first PUSCH 914A, where the number of bits is 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 missing, UE 502 may use a reference PUCCH HARQ-ACK resource in the PUCCH resource set to determine the set of overlapping PUSCHs. In some aspects, the reference PUCCH HARQ-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 HARQ-ACK resource may be a PUCCH that spans an entire slot or sub-slot. For example, the example 1000 of FIG. 10 includes a first DL grant 1002A, a second DL grant 1002B, a first PDSCH 1004A scheduled by the first DL grant 1002A, a second PDSCH 1004B 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, and a fourth UL grant 1006D associated with a fourth tDAI. The PUCCH 1012 may include a fourth UL grant 1006D scheduled by the first UL grant 1006A, a first PUSCH 1014A 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 be missing, which may cause the first PDSCH 1004A and the second PDSCH 1004B to not be successfully scheduled for the UE 502. Because neither the first PDSCH 1004A nor the second PDSCH 1004B was successfully scheduled for the UE 502, the UE 502 cannot 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, where the number of bits is based on the second tDAI associated with the UL grant 1006B that schedules 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 multiplexing a non-zero number of HARQ bits (such as HARQ-ACK bits) on a PUSCH. The HARQ-ACK bits may be multiplexed on a PUSCH scheduled by an UL grant associated with a non-zero tDAI. In some aspects, UL grants in the same slot may be associated with the same (i.e., same value) tDAI. In some aspects, using a subslot-based HARQ codebook (CB), the UE 502 may multiplex HARQ-ACK bits in one subslot, and the UE 502 may receive exactly one UL grant associated with a non-zero tDAI. The HARQ-ACK bits may be multiplexed on a PUSCH scheduled by an UL grant associated with a non-zero tDAI. In some aspects, UL grants in the same subslot may be associated with the same (i.e., same value) tDAI.

In some aspects, UE 502 may receive two or more UL grants with non-zero tDAI in one slot, and UE 502 may multiplex the PUCCH HARQ-ACK on the PUSCH scheduled by the UL grant associated with the tDAI indicating the maximum number of HARQ-ACK bits.

In some aspects, UE 502 may receive two or more UL grants with non-zero tDAI in a slot, and UE 502 may multiplex a PUCCH HARQ-ACK on a PUSCH scheduled by the last received (i.e., last received in time) or first received UL grant among the UL grants that schedule a PUSCH in a slot. In some aspects, UE 502 may choose to select a PUSCH in a slot on which to multiplex a PUCCH HARQ-ACK.

In some aspects, UE502 may take the maximum value of tDAI and multiplex it on each PUSCH. In some aspects, UE502 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, in the case of slot-based HARQ CB or subslot-based HARQ CB, each PUSCH with a grant including tDAI may carry x bits of UCI. UE502 may choose to have one PUSCH per slot or subslot or each PUSCH with a grant including tDAI (where tDAI is equal to x) that may carry x bits of UCI.

In some aspects, UE 502 may take the PUCCH configuration into account when selecting a PUSCH. For example, even if UE 502 misses a DL grant/DCI, when UE 502 selects a PUSCH on which to multiplex HARQ bits, the selected PUSCH may correspond to a scheduling scenario that would have occurred if the DL grant/DCI had not been missed. For example, if the UE selects a PUSCH on which to multiplex X bits, there may be PUCCH resources that are configured and overlap with the PUSCH that may carry x bits.

In some aspects, a timeline may be defined across PUSCHs scheduled in the same slot/subslot. In one non-limiting example, a grant that schedules a second PUSCH with a different tDAI than the first PUSCH may be no later than a defined time, such as N4, from the starting or ending symbol of the first PUSCH. In some aspects, the defined time, such as N4, may be the latest time at which a PUSCH with a different tDAI may be scheduled in a given slot/subslot, the reference may be from the starting symbol of the first PUSCH with the tDAI. For example, an association between a PUSCH and a subslot may be defined based on the starting symbol of each PUSCH. In some aspects, the timeline may be applied across PUSCHs scheduled by UL grants indicating a non-zero tDAI. For example, the timeline may be applied across all PUSCHs in a slot or subslot, regardless of the tDAI value associated with the PUSCH or regardless of whether a tDAI is configured in the UL grant that schedules the PUSCH.

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

FIG. 11 is a flowchart 1100 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502, device 1402).

At 1102, the UE may select at least one of a plurality of PUSCHs into which to multiplex one or more UCI bits, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values. For example, the UE 502 may select at least one of the multiple PUSCHs 512 for multiplexing one or more UCI bits therein, where each of the multiple PUSCHs, such as PUSCH 614A/B/C/D, PUSCH 714A/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 706A/B/C/D, UL grant 806A/B/C/D, UL grant 906A/B/C/D, or UL grant 1006A/B/C/D, where the one or more UL grants include one or more UL tDAI values. In some aspects, the subsets of PUSCHs may each be associated with a subset of UL grants, each associated with a UL tDAI 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 a UL tDAI value. In some aspects, 1102 may be performed by the selection component 1444 of FIG. 14.

At 1104, the UE may transmit to the base station one or more UCI bits multiplexed with at least one of the multiple PUSCHs. For example, the UE 502 may transmit to the base station 504 one or more UCI bits multiplexed with at least one of the multiple PUSCHs, such as PUSCH614A/B/C/D, PUSCH714A/B/C/D, PUSCH814A/B/C/D, PUSCH914A/B/C/D, or PUSCH1014A/B/C/D. In some aspects, 1104 may be performed by the PUSCH component 198. The base station may be a network entity, such as a network node.

FIG. 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 502, device 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 a base station 504. In some aspects, 1202 may be performed by the grant component 1442 of FIG. 14. The base station may be a network node.

At 1204, the UE may select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein, each of the multiple PUSCHs may be associated with an UL grant, the one or more UL grants including one or more UL tDAI values. For example, the UE 502 may select at least one of the multiple PUSCHs 512 for multiplexing one or more UCI bits therein, where each of the multiple PUSCHs, such as PUSCH 614A/B/C/D, PUSCH 714A/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 706A/B/C/D, UL grant 806A/B/C/D, UL grant 906A/B/C/D, or UL grant 1006A/B/C/D, where the one or more UL grants include one or more UL tDAI values. In some aspects, 1204 may be performed by the selecting component 1444 of FIG. 14. In some aspects, at least one of the multiple PUSCHs at least partially overlaps with a PUCCH. In some aspects, at least one of the multiple PUSCHs may be associated with a non-zero UL tDAI value. In some aspects, the one or more UCI bits may be one or more HARQ-ACK bits. In some aspects, the one or more HARQ-ACK bits may correspond to a PUCCH, such as PUCCH 514, PUCCH 612, PUCCH 712, PUCCH 812, PUCCH 912, or PUCCH 1012. In some aspects, at least one of the multiple PUSCHs may be selected based on a UL tDAI value of an associated UL grant, such as UL grant 506A/B/C/D, UL grant 606A/B/C/D, UL grant 706A/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 of the multiple PUSCHs based on a non-zero UL tDAI value, the non-zero UL tDAI value being associated with an UL grant associated with each of the at least one selected PUSCH. In some aspects, at least one of the multiple PUSCHs may be excluded based on a zero UL tDAI value, the zero UL tDAI value representing that HARQ bits may not be multiplexed on a PUSCH associated with an UL grant associated with each of the at least one excluded PUSCH. For example, the zero UL tDAI value may represent that HARQ bits may not be multiplexed on a PUSCH scheduled by an UL grant associated with the zero UL tDAI value. In some aspects, the UL tDAI value may represent a number of HARQ-ACK bits. In some aspects, the subsets of PUSCHs may each be associated with a subset of UL grants, each associated with a UL tDAI 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 a UL tDAI value. In some aspects, the UE may select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein based on not detecting DL DCI with HARQ in the same slot or subslot associated with at least one of the multiple PUSCHs, and the UE may select one of the multiple PUSCHs (e.g., any one of the multiple PUSCHs).

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

At 1206, the UE may transmit to the base station one or more UCI bits multiplexed with at least one of the multiple PUSCHs. For example, the UE 502 may transmit to the base station 504 one or more UCI bits multiplexed with at least one of the multiple PUSCHs, such as PUSCH614A/B/C/D, PUSCH714A/B/C/D, PUSCH814A/B/C/D, PUSCH914A/B/C/D, or PUSCH1014A/B/C/D. In some aspects, 1206 may be performed by the PUSCH component 1446 of FIG. 14. The base station may be a network entity, such as a network node.

FIG. 13 is a flowchart 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, device 1502). The 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, where the one or more UL grants include 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, where the one or more UL grants include one or more UL tDAI values. In some aspects, 1302 may be performed by the grant component 1542 of FIG. 15. In some aspects, one or more UL grants transmitted in the same slot may be associated with the same tDAI value. In some aspects, the base station may be configured with a subslot-based HARQ codebook, and the base station may transmit one UL grant associated with a non-zero tDAI value in one subslot without receiving an additional UL grant in the one subslot. In some aspects, the PUSCH associated with the UL grant may be associated with one subslot based on the starting symbol of the PUSCH. In some aspects, one or more UL grants transmitted in the same slot may be associated with the same tDAI value. In some aspects, the base station may be configured with a subslot-based HARQ codebook, and one or more UL grants transmitted in the same subslot may be associated with the same tDAI value. In some aspects, a subset of the UL grants may each be associated with a UL tDAI value. In some aspects, a subset of one or more UL grants may be associated with one or more UL tDAI values, and another subset of one or more UL grants may not be associated with a UL tDAI value.

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

FIG. 14 is a diagram 1400 illustrating an example of a hardware implementation for the device 1402. The device 1402 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the device 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 device 1402 may further 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 the BS 102/180 through the cellular RF transceiver 1422. The cellular baseband processor 1404 may include computer readable media/memory. The computer readable media/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 media/memory. The software, when executed by the cellular baseband processor 1404, causes the cellular baseband processor 1404 to perform the various functions described above. The computer readable media/memory may be used to store data that is manipulated by the cellular baseband processor 1404 when executing the software. The cellular baseband processor 1404 further includes a receiving component 1430, a communications manager 1432, and a transmitting component 1434. The communications manager 1432 includes one or more of the illustrated components. The components in the communications manager 1432 may be stored in the computer readable media/memory and/or configured as hardware in the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the device 1402 may be a modem chip and may include only the baseband processor 1404, and in another configuration, the device 1402 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the device 1402.

The communications manager 1432 may 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, for example, as described with respect to 1202 of FIG. 12. The communications manager 1432 may further include a selection component 1444 that may be configured to select at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, for example, as described with respect to 1102 of FIG. 11 and 1204 of FIG. 12, where one or more of the plurality of PUSCHs are associated with one or more UL grants, and the one or more UL grants include one or more UL tDAI values. The communications manager 1432 may further include a PUSCH component 1446 that may be configured to transmit one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to a base station, for example, as described with respect to 1104 of FIG. 11 and 1206 of FIG. 12.

The apparatus may include additional components that perform each of the blocks of the algorithms in the flowcharts of FIG. 11 and FIG. 12. Thus, each block in the flowcharts of FIG. 11 and FIG. 12 may be performed by a component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process/algorithm, implemented by a processor configured to perform the described process/algorithm, stored in 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, particularly the cellular baseband processor 1404, may include means for selecting at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, and the one or more UL grants include one or more UL tDAI values. The cellular baseband processor 1404 may further include means for transmitting to a network entity one or more UCI bits multiplexed with at least one of the plurality of PUSCHs. The cellular baseband processor 1404 may further include means for receiving from a base station one or more DL grants or at least one of the one or more UL grants. The means may be one or more of the components of the apparatus 1402 configured to perform the functions recited by the means. As described above, the apparatus 1402 may include a TX processor 368, a RX processor 356, and a controller/processor 359. Thus, in one configuration, the means may be a TX processor 368, an RX processor 356, and a controller/processor 359 configured to perform the functions recited by the means.

15 is a diagram 1500 illustrating an example of a hardware implementation of the device 1502. The device 1502 may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the base station 1402 may include a baseband unit 1504. The baseband unit 1504 may communicate with the UE 104 via a cellular RF transceiver 1522. The 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 the computer-readable medium/memory. The software, when executed by the baseband unit 1504, causes the baseband unit 1504 to perform the various functions described above. The computer-readable medium/memory may be used to store data that is manipulated by the baseband unit 1504 when executing the software. The baseband unit 1504 further includes a receiving component 1530, a communication manager 1532, and a transmitting component 1534. The communications manager 1532 includes one or more of the illustrated components. The components in the communications manager 1532 may be stored in a computer-readable medium/memory and/or configured as hardware in the baseband unit 1504. The baseband unit 1504 may be a component of the base station 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communications manager 1532 may include a grant component 1542 that may transmit at least one of one or more DL grants or one or more UL grants to the UE, where the one or more UL grants include one or more UL tDAI values, as described, for example, with respect to 1302 of FIG. 13. The communications manager 1532 may further include a PUSCH component 1544 that may receive, from the UE, one or more UCI bits multiplexed with at least one of the multiple PUSCHs, as described, for example, with respect to 1304 of FIG. 13.

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 13. Thus, each block in the flowchart of FIG. 13 may be performed by a component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process/algorithm, implemented by a processor configured to perform the described process/algorithm, stored in 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, particularly the baseband unit 1504, may include means for selecting at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, and the one or more UL grants include one or more UL tDAI values. The baseband unit 1504 may further include means for transmitting to the base station one or more UCI bits multiplexed with at least one of the plurality of PUSCHs. The means may be one or more of the components of the apparatus 1502 configured to perform the functions recited by the means. As described above, the apparatus 1502 may include the TX processor 316, the RX processor 370, and the controller/processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller/processor 375 configured to perform the functions recited by the means.

It is understood that the particular order or hierarchy of blocks in the disclosed processes/flowcharts is illustrative of example approaches. Based on design preferences, it is understood that the particular order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the particular order or hierarchy presented.

The above 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 general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the widest scope consistent with the claim language, and references to elements in the singular do not mean "one and only," unless so expressly stated, but rather mean "one or more." Terms such as "if," "when," and "while" should be construed to mean "under the condition that," rather than implying an immediate time relationship or reaction. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but merely imply that an action occurs when a condition is met, but without requiring a specific or immediate time constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other embodiments. Unless otherwise specified, the term "some" refers to one or more. 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," "A, B, C, or any combination thereof" include any combination of A, B, and/or C and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or that later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is made public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no claim element should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

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

Aspect 1 is an apparatus for wireless communications in a UE, the apparatus including: a memory; and at least one processor coupled to the memory, the at least one processor configured to: select at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values; and transmit to a network entity the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs.

Aspect 2 is the device of aspect 1, in which at least one of the multiple PUSCHs at least partially overlaps with the PUCCH.

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

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

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

Aspect 6 is the device of any of aspects 1 to 5, in which one or more HARQ-ACK bits correspond to a PUCCH.

Aspect 7 is the apparatus of any of aspects 1 to 6, in which at least one of the multiple PUSCHs is selected based on a UL tDAI value of an associated UL grant.

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

Aspect 9 is the apparatus of any of aspects 1-8, wherein at least one of the multiple 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 an UL grant associated with each of the at least one excluded PUSCH.

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

Aspect 11 is the apparatus of any of aspects 1-10, wherein the UE is scheduled to transmit a PUSCH in a slot or subslot, the UE does not receive a DL grant associated with transmitting a HARQ-ACK in the associated slot or subslot, and at least one processor coupled to the memory is further configured to select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein based on a reference PUCCH HARQ-ACK resource in the PUCCH resource set.

Aspect 12 is the apparatus of any of aspects 1 to 11, wherein the reference PUCCH HARQ-ACK resource is a first resource in the PUCCH resource set.

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

Aspect 14 is the apparatus of any of aspects 1 to 13, in which the reference PUCCH HARQ-ACK resource is a PUCCH that spans an entire slot or subslot.

Aspect 15 is the apparatus of any of aspects 1 to 14, in which the UE receives one UL grant associated with a non-zero tDAI value in one slot without receiving an additional UL grant in the one slot.

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

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

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

Aspect 19 is the apparatus of any of aspects 1-18, wherein the at least one processor coupled to the memory is further configured to select at least one of the plurality of PUSCHs for multiplexing one or more UCI bits therein based on a maximum number associated with the UL tDAI value.

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

Aspect 21 is the apparatus of any of aspects 1-20, wherein at least one processor coupled to the memory is further configured to select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein based on not detecting DL DCI with HARQ in the same slot or subslot associated with at least one of the multiple PUSCHs.

Aspect 22 is the apparatus of any of aspects 1-21, wherein at least one processor coupled to the memory is further configured to select at least one of the plurality of PUSCHs for multiplexing one or more UCI bits therein based on an initially received UL grant associated with at least one of the plurality of PUSCHs.

Aspect 23 is the apparatus of any of aspects 1 to 22, wherein at least one processor coupled to the memory is further configured to multiplex a maximum of the tDAI values on each PUSCH of the multiple PUSCHs.

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

Aspect 25 is the apparatus of any of aspects 1-24, wherein at least one processor coupled to the memory is further configured to select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein based at least in part on a PUCCH configuration representing a maximum number of bits that the PUCCH resource can carry.

Aspect 26 is the apparatus of any of aspects 1 to 25, wherein at least one processor coupled to the memory is further configured to select at least one of the multiple PUSCHs for multiplexing one or more UCI bits therein based on a defined timeline within the slot or subslot.

Aspect 27 is the device of any of aspects 1 to 26, further including a transceiver coupled to the at least one processor.

Aspect 28 is an apparatus for wireless communication in a network entity, the apparatus including: a memory; and at least one processor coupled to the memory, the at least one processor configured to transmit, for a UE, at least one of one or more DL grants or one or more UL grants, where the one or more UL grants include one or more UL tDAI values; and receive one or more UCI bits multiplexed with at least one of a plurality of PUSCHs.

Aspect 29 is the apparatus of aspect 28, in which at least one of the multiple PUSCHs at least partially overlaps with the PUCCH.

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

Aspect 31 is the apparatus of any 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 of aspects 28-31, in which the one or more HARQ-ACK bits correspond to a PUCCH.

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

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

Aspect 35 is the apparatus of any of aspects 28-34, wherein the network entity is configured with a subslot-based HARQ codebook, the network entity transmits one UL grant associated with a non-zero tDAI value in one subslot without receiving an additional UL grant in the one subslot, and the PUSCH associated with the UL grant is associated with the one subslot based on a starting symbol of the PUSCH.

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

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

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

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

Aspect 40 is a method of wireless communication in a UE, comprising the steps of: selecting at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values; and transmitting to a network entity the one or more UCI bits multiplexed with at least one of the plurality of PUSCHs.

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 communications in a UE, comprising: means for selecting at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values; and means for transmitting to a network entity the one or more UCI bits multiplexed with at least one of the plurality of PUSCHs.

Aspect 43 is the device of aspect 42, further including a transceiver.

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

Aspect 45 is a computer-readable medium storing computer-executable code in a UE, which, when executed by a processor, causes the processor to select at least one of a plurality of PUSCHs for multiplexing one or more UCI bits therein, where one or more of the plurality of PUSCHs are associated with one or more UL grants, the one or more UL grants including one or more UL tDAI values, and to transmit to a network entity the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs.

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

Aspect 47 is a method of wireless communication in a network entity, comprising: transmitting at least one of one or more DL grants or one or more UL grants for a UE, the one or more UL grants including one or more UL tDAI values; and receiving one or more UCI bits multiplexed with at least one of a 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 in a network entity, the apparatus including: means for transmitting at least one of one or more DL grants or one or more UL grants for a UE, the one or more UL grants including one or more UL tDAI values; and means for receiving one or more UCI bits multiplexed with at least one of a plurality of PUSCHs.

Aspect 50 is the device of aspect 49, further including a transceiver.

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

Aspect 52 is a computer-readable medium storing computer-executable code in a network entity, which, when executed by a processor, causes the processor to transmit at least one of one or more DL grants or one or more UL grants for a UE, where the one or more UL grants include one or more UL tDAI values, and to receive one or more UCI bits multiplexed with at least one of the multiple PUSCHs.

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

100 Wireless communication systems and access networks
102 Base station, macro base station, BS
102' Small Cell
104UE
110 Coverage Area
110' Coverage Area
120 Communication Links
132 1st backhaul link
134 3rd Backhaul Link
150 Wi-Fi access points (AP)
152 Wi-Fi stations (STA)
154 Communication Links
158 Device-to-Device (D2D) Communication Links
160 Evolved Packet Core (EPC)
162 Mobility Management Entity (MME)
164 MME
166 Serving Gateway
168 Multimedia Broadcast Multicast Service (MBMS) Gateway
170 Broadcast Multicast Service Center (BM-SC)
172 Packet Data Network (PDN) Gateway
174 Home Subscriber Server (HSS)
176 IP Services
180 gNB, mmWave base station, base station, BS
182 Beamforming
182' Sending direction
182'' receiving direction
184 Second Backhaul Link
190 Core Network
192 Access and Mobility Management Function (AMF)
193 AMF
194 Session Management Facility (SMF)
195 User Plane Function (UPF)
196 Unified Data Management (UDM)
197 IP Services
198 PUSCH components
199 PUSCH components
200 Figures
230 Figure
250 Figures
280 Figures
310 Base Station
316 Transmit (TX) Processor
318 Transmitter TX, Receiver RX
320 Antenna
350UE
352 Antenna
354 Receiver RX, Transmitter TX
356 Receive (RX) Processor
358 Channel Estimator
359 Controller/Processor
360 Memory
368 TX Processor
370 Receive (RX) Processor
374 Channel Estimator
375 Controller/Processor
376 Memory
400 Examples
412 PUCCH
414A PUSCH
414B PUSCH
414C PUSCH
414D PUSCH
500 Communication Flow
502UE
504 Base Station
506 DL Grant
506A Time Frame
508 UL Grant
508A Time Frame
510 PDSCH
510A Time Frame
512 PUSCH
512A Time Frame
514 PUCCH
514A Time Frame
600 Examples
602A 1st DL Grant
602B 2nd DL Grant
606A 1st UL Grant
606B Second UL Grant
606C 3rd UL Grant
606D 4th UL Grant
612 PUCCH
614A 1st PUSCH, PUSCH
614B 2nd PUSCH, PUSCH
614C 3rd PUSCH, PUSCH
614D 4th PUSCH, PUSCH
700 Examples
702A 1st DL Grant
702B 2nd DL Grant
706A 1st UL Grant
706B Second UL Grant
706C 3rd UL Grant
706D 4th UL Grant
712 PUCCH
712A part
714A 1st PUSCH, PUSCH
714B 2nd PUSCH, PUSCH
714C 3rd PUSCH, PUSCH
714D 4th PUSCH, PUSCH
800 Examples
802A 1st DL Grant
802B 2nd DL Grant
806A 1st UL Grant
806B Second UL Grant
806C 3rd UL Grant
806D 4th UL Grant
812 PUCCH
814A 1st PUSCH, PUSCH
814B 2nd PUSCH, PUSCH
814C 3rd PUSCH, PUSCH
814D 4th PUSCH, PUSCH
900 Examples
902A 1st DL Grant
902B 2nd DL Grant
906A 1st UL Grant
906B Second UL Grant
906C 3rd UL Grant
906D 4th UL Grant
912 PUCCH
914A 1st PUSCH, PUSCH
914B 2nd PUSCH, PUSCH
914C 3rd PUSCH, PUSCH
914D 4th PUSCH, PUSCH
1000 Examples
1002A 1st DL Grant
1002B 2nd DL Grant
1004A 1st PDSCH
1004B 2nd PDSCH
1006A 1st UL Grant
1006B Second UL Grant
1006C 3rd UL Grant
1006D 4th UL Grant
1012 PUCCH, Reference PUCCH
1014A 1st PUSCH, PUSCH
1014B 2nd PUSCH, PUSCH
1014C 3rd PUSCH, PUSCH
1014D 4th PUSCH, PUSCH
1100 Flowchart
1200 Flowchart
1300 Flowchart
1400 Figures
1402 Equipment
1404 Cellular Baseband Processor
1406 Application Processor
1408 Secure Digital (SD) Card
1410 Screen
1412 Bluetooth Module
1414 Wireless Local Area Network (WLAN) Module
1416 Global Positioning System (GPS) Module
1418 Power supply
1420 Subscriber Identity Module (SIM) Card
1422 Cellular RF Transceiver
1430 Receiving Component
1432 Communications Manager
1434 Transmission Component
1502 Equipment
1504 Baseband unit
1522 Cellular RF Transceiver
1530 Receiving Component
1532 Communications Manager
1542 Grant Components
1544 PUSCH components

Claims (30)

An apparatus for wireless communication in a user equipment (UE), comprising:
Memory,
and at least one processor coupled to the memory, the at least one processor comprising:
selecting at least one of a plurality of physical uplink shared channels (PUSCHs) into which to multiplex one or more uplink control information (UCI) bits, wherein one or more of the plurality of PUSCHs are associated with one or more uplink (UL) grants, the one or more UL grants including one or more UL total downlink allocation index (tDAI) values;
and transmitting, to a network entity, the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs. The apparatus of claim 1, wherein at least one of the plurality of PUSCHs at least partially overlaps with a physical uplink control channel (PUCCH). The apparatus of claim 1, wherein at least one 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. the at least one processor coupled to the memory;
10. The apparatus of claim 1, further configured to receive at least one of one or more downlink (DL) grants or one or more UL grants from the network entity. 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. The apparatus of claim 5, wherein the one or more HARQ-ACK bits correspond to a physical uplink control channel (PUCCH). The apparatus of claim 1, wherein the at least one of the plurality of PUSCHs is selected based on the UL tDAI value of an associated UL grant. The UE detects at least one physical uplink control channel (PUCCH) based on at least one DL grant, and the at least one processor coupled to the memory:
2. The apparatus of claim 1, further configured to: select the at least one of the plurality of PUSCHs based on a non-zero UL tDAI value associated with the UL grant associated with each of the at least one selected PUSCH. The apparatus of claim 8, wherein at least one of the plurality of PUSCHs is excluded based on a zero UL tDAI value, the zero UL tDAI value representing that no hybrid automatic repeat request (HARQ) bits are to be multiplexed on the PUSCH associated with the UL grant associated with each of the at least one excluded PUSCH. The apparatus of claim 8, wherein the UL tDAI value represents a number of Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) (HARQ-ACK) bits. The apparatus of claim 1, wherein the UE is scheduled to transmit a PUSCH in a slot or subslot, the UE does not receive a DL grant associated with a transmission of a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) (HARQ-ACK) in an associated slot or subslot, and the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on a reference physical uplink control channel (PUCCH) HARQ-ACK resource in a PUCCH resource set. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resource is a first resource in the PUCCH resource set. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resource comprises a longest duration of resources in the PUCCH resource set. The apparatus of claim 11, wherein the reference PUCCH HARQ-ACK resource is a PUCCH that spans an entire slot or subslot. The apparatus of claim 1, wherein the UE receives one UL grant associated with a non-zero tDAI value in a slot without receiving additional UL grants in the slot. The apparatus of claim 1, wherein the UE is configured with a subslot-based hybrid automatic repeat request (HARQ) codebook, the UE receives one UL grant associated with a non-zero tDAI value in one subslot without receiving an additional UL grant in the one subslot, and a PUSCH associated with the UL grant is associated with the one subslot based on a starting symbol of the PUSCH. The apparatus of claim 1, wherein one or more UL grants received in the same slot are associated with the same tDAI value. The apparatus of claim 1, wherein the UE is configured with a subslot-based Hybrid Automatic Repeat Request (HARQ) codebook, and one or more UL grants received in the same subslot are associated with the same tDAI value. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on a maximum number associated with the UL tDAI value. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on a last received UL grant associated with the at least one of the plurality of PUSCHs. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on not detecting a downlink (DL) downlink control information (DCI) having a hybrid automatic repeat request (HARQ) in a same slot or subslot associated with the at least one of the plurality of PUSCHs. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on an initially received UL grant associated with the at least one of the plurality of PUSCHs. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to multiplex the maximum of the tDAI values on each PUSCH of the plurality of PUSCHs. The apparatus of claim 1, wherein each PUSCH of the plurality of PUSCHs carries X bits of UCI, where X is equal to the associated tDAI value. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based at least in part on a physical uplink control channel (PUCCH) configuration representing a maximum number of bits a PUCCH resource can carry. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs for multiplexing the one or more UCI bits therein based on a defined timeline within a slot or subslot. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor. An apparatus for wireless communication in a network entity, comprising:
Memory,
and at least one processor coupled to the memory, the at least one processor comprising:
transmitting at least one of one or more downlink (DL) grants or one or more uplink (UL) grants for a user equipment (UE), the one or more UL grants including one or more UL total downlink allocation index (tDAI) values;
and receiving one or more uplink control information (UCI) bits multiplexed with at least one of a plurality of physical uplink shared channels (PUSCHs). 1. A method of wireless communication in a user equipment (UE), comprising:
selecting at least one of a plurality of physical uplink shared channels (PUSCHs) into which to multiplex one or more uplink control information (UCI) bits, wherein one or more of the plurality of PUSCHs are associated with one or more uplink (UL) grants, the one or more UL grants including one or more UL total downlink allocation index (tDAI) values;
and transmitting, to a network entity, the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs. 1. A method of wireless communication in a network entity, comprising:
transmitting at least one of one or more downlink (DL) grants or one or more uplink (UL) grants for a user equipment (UE), the one or more UL grants including one or more UL total downlink allocation index (tDAI) values;
and receiving one or more uplink control information (UCI) bits multiplexed with at least one of a plurality of physical uplink shared channels (PUSCHs).