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

Abstract

Methods, apparatus, and computer-readable media are provided to enable HARQ-ACK multiplexing on PUSCH in UL CA. An example method includes selecting at least one of a plurality of PUSCHs to multiplex one or more UCI bits, wherein one or more of the plurality of PUSCHs is associated with one or more UL grants, and the one or more UL grants are one or more UL grants. Includes the above UL tDAI values. The example method further includes transmitting one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to the network entity.

Description

HARQ-ACK multiplexing on PUSCH in UL CA

Cross-reference to related applications

This application is related to U.S. Provisional Application No. 63/186,772, entitled “HARQ-ACK MULTIPLEXING on PUSCH in UL CA,” filed May 10, 2021, and “HARQ-ACK MULTIPLEXING on PUSCH in” filed May 9, 2022. Claims the benefit and priority of U.S. Provisional Patent Application No. 17/662,636, entitled “UL CA,” which is expressly incorporated herein by reference in its entirety.

technology field

This disclosure relates generally to communication systems, and more specifically to wireless communication systems with hybrid automatic repeat request (HARQ) acknowledgment (ACK) multiplexing on a physical uplink shared channel (PUSCH). It's about.

Introduction

Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies that can support 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, and single access (SC-FDMA) systems. -Includes a carrier frequency division multiple access) system, and a time division synchronous code division multiple access (TD-SCDMA) system.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different wireless devices to communicate on city, national, regional and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is a continuous mobile technology announced by the Third 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. It is part of the broadband evolution. 5G NR includes services associated with 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 telecommunication standards that employ these technologies.

A brief overview

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

In one aspect of the disclosure, methods, computer-readable media, and devices in user equipment (UE) are provided. The device may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to select at least one of the plurality of PUSCHs to multiplex one or more uplink control information (UCI) bits, the plurality of PUSCHs One or more of the UL grants is 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 at least one processor coupled to the memory may be further configured to transmit one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to a network entity.

In another aspect of the disclosure, a method, computer-readable medium, and apparatus at a network entity are provided. The device may include a memory and at least one processor coupled to the memory. The memory and at least one processor coupled to the memory may be configured to transmit to the UE at least one of one or more downlink (DL) grants or one or more UL grants, where the one or more UL grants are one or more Includes the above UL tDAI values. The memory and 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 plurality of PUSCHs.

To the accomplishment of the foregoing and related objectives, one or more aspects include features fully described below and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features represent only a few of the various ways in which the principles of the various aspects may be employed and this description is intended to encompass all such aspects and their equivalents.

Brief description of the drawings
1 is a diagram illustrating an example of a wireless communication system and access network.
2A is a diagram illustrating an example of a first frame, according to various aspects of the present disclosure.
FIG. 2B is a diagram illustrating an example of DL channels within a subframe, according to various aspects of the present disclosure.
2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
FIG. 2D is a diagram illustrating an example of UL channels within a subframe, according to various aspects of the present disclosure.
3 is a diagram representing an example of a base station and user equipment (UE) in an access network.
4 is a diagram illustrating communications between a UE and a base station.
Figure 5 is a diagram illustrating communications between a UE and a base station.
Figure 6 is a diagram illustrating communications between a UE and a base station.
Figure 7 is a diagram illustrating communications between a UE and a base station.
Figure 8 is a diagram illustrating communications between a UE and a base station.
Figure 9 is a diagram illustrating communications between a UE and a base station.
Figure 10 is a diagram illustrating communications between a UE and a base station.
Figure 11 is a flowchart of a method of wireless communication.
Figure 12 is a flowchart of a method of wireless communication.
Figure 13 is a flowchart of a method of wireless communication.
14 is a diagram illustrating an example hardware implementation for an example device.
15 is a diagram illustrating an example hardware implementation for an example device.

details

The detailed description set forth below in conjunction with 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 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 cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented in hardware or software depends on the specific 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” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, GPUs (Graphics Processing Unit), CPUs (central processing units), application processors, DSPs (digital signal processors), RISC (reduced instruction set computing) processors, and SoCs (System on Chip). , 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 the various functionality described throughout the present disclosure. . One or more processors in a processing system may execute software. Software means instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. It should be broadly interpreted to mean a package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Accordingly, in one or more example embodiments, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of non-limiting example, such computer-readable media include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, and the like. It may include a combination of one type of computer-readable medium, 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 as examples of some examples, those skilled in the art will understand that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may include integrated chip implementations and other non-module-component based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail/ It may occur through purchasing devices, medical devices, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not relate specifically to use cases or applications, broad applicability of the described innovations may arise. Implementations may span the spectrum from chip level or modular components to non-modular, non-chip level implementations, and may further include integrated, distributed, integrated, or integrated implementations incorporating one or more aspects of the described innovations. Or it may range up to original equipment manufacturer (OEM) devices or systems. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals involves multiple components for analog and digital purposes (e.g., antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleaver, adders). /hardware components, including adders, etc.). The innovations described herein may be implemented in a variety of devices, chip-level components, systems, distributed arrangements, integrated or discrete components, end-user devices, etc. of various sizes, shapes and configurations. Existence is intended.

1 is a diagram illustrating an example of a wireless communication system and access network 100. A wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, and an evolved packet core (EPC) 160, and another core network 190 (e.g. For example, 5G Core (5GC)). Base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). Macrocells contain base stations. Small cells include femto cells, pico cells, and micro cells.

Base stations 102 configured for 4G LTE (collectively referred to as the Envolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN)) support backhaul links 132 (e.g. For example, it may interface with EPC 160 via S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 via secondary backhaul links 184. In addition to other functions, base stations 102 may perform one or more of the following functions: transmission of user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g. , handover, dual connectivity), inter-cell interference coordination, connection setup and teardown, load balancing, distribution for NAS (non-access stratum) 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 warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) over third backhaul links 134 (e.g., X2 interface). there is. First backhaul links 132, second backhaul links 184, and third backhaul links 134 may be wired or wireless.

Base stations 102 may communicate wirelessly with UEs 104. Each of base stations 102 may provide communications coverage for a respective geographic coverage area 110 . There may be overlapping geographic coverage areas 110. For example, small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macrocells may be known as a heterogeneous network. The heterogeneous network may also include home evolved Node Bs (eNBs) (HeNBs) that may provide services to a limited group known as a closed subscriber group (CSG). Communication links 120 between base stations 102 and UEs 104 may include UL (also referred to as reverse link) transmissions from UE 104 to base station 102 and/or from base station 102. Downlink (DL) (also referred to as the forward link) transmissions to the UE 104 may be included. Communication links 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. Communication links may be via one or more carriers. Base stations 102/UEs 104 may have Y MHz (e.g., 5, 10, Spectra with bandwidths up to 15, 20, 100, 400 MHz, etc. can also be used. Carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for the DL and UL (eg, more or fewer carriers may be allocated for the DL than for the UL). 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).

Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158 . D2D communication link 158 may use DL/UL WWAN spectrum. The D2D communication link 158 includes a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and one or more sidelink channels, such as a physical sidelink control channel (PSCCH). D2D communication may be via various wireless D2D communication systems such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi, LTE or NR based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154, such as in the 5 GHz unlicensed frequency spectrum. there is. When communicating in an unlicensed frequency spectrum, STAs 152/AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

Small cells 102' may operate in licensed and/or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, small cells 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) as used by Wi-Fi AP 150. there is. Small cells 102' employing NR in unlicensed frequency spectrum may boost coverage for the access network 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. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although parts of FR1 are greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. A similar nomenclature issue exists with respect to FR2, which is often (interchangeably) referred to in the literature and papers as "millimeter wave", as is the extremely high frequency (EHF) band, which is identified by the International Telecommunication Union (ITU) as the "millimeter wave" band. ), although it is different from the other bands (30 GHz to 300 GHz), it occasionally occurs.

Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified the operating band for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, thus effectively extending the characteristics of FR1 and/or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range 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 foregoing aspects in mind, unless otherwise specifically stated, the term "sub-6 GHz" and the like, when used herein, may be below 6 GHz, may be within FR1, or may include mid-band frequencies. It should be understood that frequencies may be represented broadly. Additionally, unless specifically stated otherwise, the term "millimeter wave", etc., when used herein, may include mid-band frequencies, or may be within FR2, FR4, FR4-a or FR4-1 and/or FR5. It should be understood that it may broadly represent frequencies that are present and/or may be within the EHF band.

Base station 102 may include and/or be referred to as an eNB, gNodeB (gNB), or other type of base station, whether a small cell 102' or a large cell (e.g., a macro base station). It may be possible. Some base stations, such as gNB 180, may operate in the typical sub-6 GHz spectrum, at millimeter wave frequencies, and/or near millimeter wave frequencies when communicating with UE 104. When gNB 180 operates at millimeter wave or near millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays, to facilitate beamforming.

Base station 180 may transmit a beamformed signal to UE 104 in one or more transmission directions 182'. UE 104 may receive a beamformed signal from base station 180 in one or more reception directions 182''. UE 104 may also transmit a beamformed signal to base station 180 in one or more transmission directions. Base station 180 may receive a beamformed signal from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the best reception and transmission directions for base station 180 / UE 104, respectively. The transmit and receive directions for base station 180 may or may not be the same. The transmit and receive directions for UE 104 may or may not be the same.

EPC 160 includes Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, and Multimedia Broadcast Multicast Service (MBMS) Gateway 168. , a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is a control node that processes signaling between UEs 104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN gateway 172 provides UE IP address allocation, as well as other functions. PDN gateway 172 and BM-SC 170 are connected to IP services 176. IP services 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and/or other IP services. BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. It may also be used. MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting specific services, and May be responsible for managing (start/stop) and collecting billing information related to eMBMS.

Core network 190 may include an access and mobility management function (AMF) 192, another AMF 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that processes signaling between UEs 104 and core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation as well as other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switch (PS) Streaming (PSS) service, and/or other IP services.

A base station may be a gNB, Node B, eNB, access point, base transceiver station, wireless base station, wireless transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or other Other suitable terms may also be included and/or referred to as such. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UEs 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors/actuators, displays, or any other similar functional device. Includes. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station. , may be referred to as an access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or access the network individually. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or access the network individually. Network nodes may be implemented as base stations (i.e., aggregated base stations), separate base stations, integrated access and backhaul (IAB) nodes, relay nodes, sidelink nodes, etc. The network entity may be a base station (i.e. an aggregated base station) or, alternatively, a central unit (CU), distributed unit (DU), radio unit (RU), or near-real time (Near-RT) unit in a separate base station architecture. It can be implemented as a RAN Intelligent Controller (RIC), or a non-real-time (Non-RT) RIC.

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

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

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

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 showing an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD), where subframes in a set of subcarriers are dedicated to DL or UL, for a specific set of subcarriers (carrier system bandwidth), or There may be time division duplexing (TDD) in which subframes in a set of subcarriers are dedicated to both DL and UL (carrier system bandwidth). In the examples provided by FIGS. 2A, 2C, the 5G NR frame structure is assumed to be TDD, and subframe 4 consists of slot format 28 (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 (all UL). Although subframes 3 and 4 are shown in slot formats 1 and 28, respectively, any particular subframe may be configured in any of the various available slot formats 0 through 61. Slot formats 0 and 1 are all DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. UEs are configured (dynamically via DL Control Information (DCI), or semi-statically/statically via Radio Resource Control (RRC) signaling) with a slot format via a received slot format indicator (SFI). . Note that the description below also applies to the 5G NR frame structure that is TDD.

2A-2D illustrate frame structures, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may contain 7, 4, or 2 symbols. Each slot may contain 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. In the case of normal CP, each slot may include 14 symbols, and in the case of extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL are also referred to as CP-OFDM symbols (for high throughput scenarios) or Discrete Fourier Transform (DFT) Spread OFDM (DFT-s-OFDM) symbols (Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) ) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on CP and numerology. Numerology defines the subcarrier spacing (SCS) and the symbol length/duration, effectively equal to 1/SCS.

μ Cyclic prefix 0 15 Regular One 30 Regular 2 60 Regular, extended 3 120 Regular 4 140 Regular

For regular CP (14 symbols/slots), different numerologies (μ) 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, Numerology 2 allows 4 slots per subframe. Therefore, for regular 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 to 4. Likewise, numerology μ=0 has a subcarrier spacing of 15 kHz and numerology μ=4 has a subcarrier spacing of 240 kHz. Symbol length/duration is inversely proportional to subcarrier spacing. 2A-2D provide examples of regular 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 portions (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a specific numerology and CP (normal or extended).

Resource grids can also be used to represent frame structures. Each time slot contains resource blocks (RBs) (also referred to as physical RBs (PRBs)) extending over 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 Figure 2A, some of the REs carry reference (pilot) signals (RS) for the UE. RS includes channel state information reference signals (CSI-RS) and demodulation RS (DM-RS) for channel estimation in the UE (indicated as R for one specific configuration, but other DM-RS configurations are possible) You may. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

Figure 2B shows an example of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries the DCI in one or more control channel elements (CCE) (e.g., 1, 2, 4, 8 or 16 CCE), each CCE comprising a group of 6 REGs (REG ), and each REG includes 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring applications on CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. have Additional BWPs may be located at larger and/or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of certain subframes of the frame. PSS is used by UE 104 to determine subframe/symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of certain subframes of the frame. 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 physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on PCI, the UE can determine the locations of the DM-RS. A Physical Broadcast Channel (PBCH) carrying a Master Information Block (MIB) may be logically grouped with PSS and SSS to form a Synchronization Signal (SS)/PBCH block (also referred to as SS Block (SSB)). there is. The MIB provides the system frame number (SFN) and number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

As shown in Figure 2C, some of the REs carry DM-RS (denoted as R for one specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for Physical Uplink Control Channel (PUCCH) and DM-RS for Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS may be transmitted in the first 1 or 2 symbols of PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the specific PUCCH format used. The UE may transmit sounding reference signals (SRS). SRS may be transmitted in the last symbol of a subframe. SRS may have a comb structure, and the UE may transmit SRS on one of the combs. SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

Figure 2D shows an example of various UL channels within a subframe of a frame. PUCCH may be located as indicated in one configuration. PUCCH includes scheduling requests, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) (HARQ-ACK) feedback ( That is, it carries uplink control information (UCI) such as one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK). PUSCH carries data and may additionally be used to carry a buffer status report (BSR), power headroom report (PHR), and/or UCI.

3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from EPC 160 may be provided to controller/processor 375. Controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and radio. It includes a link control (radio link control (RLC)) layer, and a medium access control (MAC) layer. Controller/processor 375 is responsible for broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), and radio access technology. RRC layer functionality associated with measurement configuration for (RAT) inter-mobility, and UE measurement reports; PDCP layer functionality associated with header compression/decompression, security (encryption, decryption, integrity protection, integrity verification) and handover support functions; Transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and RLC data PDUs. RLC layer functionality associated with reordering; and mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, reporting scheduling information, error correction via HARQ, priority handling, and logical channel priority. Provides MAC layer functionality related to channel prioritization.

Transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, performs error detection on the transport channel, forward error correction (FEC) coding/decoding of the transport channel, interleaving, rate matching, mapping onto physical channels, and physical processing. May include modulation/demodulation of channels, and MIMO antenna processing. The TX processor 316 supports various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-QAM (M Handles mapping to signal constellation based on -quadrature amplitude modulation). Next, the coded and modulated symbols may be split into parallel streams. Each stream may then be mapped onto an OFDM subcarrier, multiplexed in the time and/or frequency domain with a reference signal (e.g., a pilot), and then into a physical signal carrying the time domain OFDM symbol stream. They may also be combined together using an inverse Fast Fourier Transform (IFFT) to create channels. The OFDM stream is spatially precoded to provide multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine coding and modulation schemes as well as for spatial processing. The channel estimate may be derived from a reference signal transmitted by UE 350 and/or channel condition feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 (TX) may modulate a radio frequency (RF) carrier into a separate spatial stream for transmission.

At UE 350, each receiver 354 (RX) receives a signal via its respective antenna 352. Each receiver 354 RX recovers the modulated information onto the RF carrier and provides the information to a receive (RX) processor 356. TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functions. RX processor 356 may perform spatial processing on the information to recover any spatial streams designated for UE 350. If multiple spatial streams are established for UE 350, they may be combined by RX processor 356 into a single OFDM symbol stream. 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 includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by base station 310. These soft decisions may be based on channel estimates calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by base station 310 on the physical channel. Data and control signals are then provided to a controller/processor 359 that implements layer 3 and layer 2 functionality.

Controller/processor 359 may be associated with memory 360, which stores program code and data. Memory 360 may also be referred to as a computer-readable medium. In the UL, controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from EPC 160. do. Controller/processor 359 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

Similar to the functionality described with respect to DL transmission by base station 310, controller/processor 359 is responsible for obtaining system information (e.g., MIB, SIBs), RRC connections, and associated RRC layer with measurement reports. Functional; PDCP layer functionality associated with header compression/decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, reporting scheduling information, error correction via HARQ, priority processing, and logical channel priority. Provides MAC layer functionality associated with ranking.

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

UL transmissions are processed at base station 310 in a manner similar to that described with respect to the receiver functionality at UE 350. Each receiver 318RX receives a signal via its respective antenna 320. Each receiver 318RX restores information modulated on the RF carrier and provides the information to the RX processor 370.

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

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

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

Example aspects provided herein provide HARQ-ACK multiplexing on PUSCHs. In some wireless communication systems, PUSCH selection based on grant type and CC index may be limited within one PUSCH slot. If the SCS of the PUSCH is larger than the SCS of the PUCCH, multiple PUSCHs may exist in different slots overlapping with one PUCCH. As illustrated in example 400 of FIG. 4 , PUSCH 414A on CC1 may not overlap with PUCCH 412, while PUSCH 414B, PUSCH 414C, and PUSCH 414D overlap PUCCH ( 412) can also overlap. In one example, PUSCH 414B, PUSCH 414C, and PUSCH 414D may be associated with different grant types, such as configured grant or dynamic grant. 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, and 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 overlapping PUCCH transmissions may be multiplexed into one PUCCH resource (may be referred to as Resource Z). Multiplexing may be performed on a PUCCH slot basis. If a PUCCH resource (resource Z) overlaps with at least one PUSCH, for UCIs in resource Z that do not contain a scheduling request (SR), UCIs that do not contain an SR are assigned to one PUSCH according to a set of priority rules. It can also be multiplexed. For example, in the case of HARQ-ACK bits in PUCCH 412 overlapping with PUSCH 414B, PUSCH 414C, and PUSCH 414D, the HARQ-ACK bits are assigned to one PUSCH according to a set of priority rules. It can also be multiplexed within. PUSCH 414B, PUSCH 414C, and PUSCH 414D that overlap with PUCCH 412 may be collectively referred to as a “set of overlapping PUSCHs.” An example set of priority rules may define that the first priority, which may be the highest priority, is associated with the PUSCH with aperiodic CSI (A-CSI) (as long as it overlaps Z).

An example set of priority rules may further define that a second priority, which may be the second highest priority, is associated with the earliest (in time) PUSCH slot(s) based on the start of the slots. If there are multiple earliest PUSCH slots overlapping a PUCCH resource (Resource Z), an example set of priority rules would state that a third priority, which may be the third highest priority, is associated with the dynamically granted PUSCHs. Additional definitions may also be provided. That is, dynamically granted PUSCHs may have a higher priority than configured acknowledged PUSCHs or semi-permanent PUSCHs. An example set of priority rules may further define that the 4th priority, which may be the 4th highest priority, may be associated with PUSCHs on a serving cell with a smaller serving cell index. That is, PUSCHs on a serving cell with a smaller serving cell index may have higher priority than PUSCHs on a serving cell with a larger serving cell index. An example set of priority rules may further define that the 5th priority, which may be the 5th highest priority, may be associated with earlier PUSCHs. That is, earlier PUSCHs may have higher priority than later PUSCHs. For example, PUSCH 414B may have a higher priority than PUSCH 414D.

Figure 5 illustrates an example communication flow 500 between UE 502 and base station 504. As illustrated in FIG. 5, base station 504 may be a network entity. A network entity may also be a network node. Base station 504 may be implemented as an aggregated base station, a separate 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 separate base station architecture, and may include a CU, DU, RU, Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), Alternatively, it may include one or more of non-RT (Non-Real Time) RIC.

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

Base station 504 may further transmit one or more UL grants 508 to UE 502. For example, one or more UL approvals 508 may include a first UL approval associated with a first TDAI value, a second UL approval associated with a second TDAI value, and a third UL approval, as further illustrated in FIGS. 6-10. A third UL approval associated with the TDAI value, and a fourth UL approval associated with the fourth TDAI value. One or more UL grants 508 may be transmitted using time domain resources in timeframe 508A. In some aspects, base station 504 may attempt to transmit one or more UL grants, but UE 502 may fail to receive one or more UL grants in 508 .

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

One or more UL grants may schedule one or more PUSCHs 512. For example, as further illustrated in FIGS. 6-10, a first UL grant may schedule a first PUSCH, a second UL grant may schedule a second PUSCH, and a third UL grant may schedule The third PUSCH may be scheduled, and the first UL grant may schedule the first PUSCH. Base station 504 may thus transmit one or more PUSCHs 512 to UE 502. One or more PUSCHs 512 are time domain resources within time frame 512A that may overlap in time with PUCCH 514 (i.e., time domain resources within time frame 514A transmitting PUCCH 514). It may also be transmitted using . One or more PUSCHs 512 may be associated with the same PUCCH group including 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 schedules the PUSCH in the downlink control information (DCI). It may follow the indicated tDAI, or it may multiplex multiple bits indicated by the tDAI. For example, as illustrated in example 600 of FIG. 6 , UE 502 may receive first DL grant 602A and second DL grant 602B, and first DL grant 602A may schedule the first PDSCH 604A and the second DL grant may schedule the 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. UE 502 has a first UL approval 606A associated with the first tDAI, a second UL approval 606B associated with the second tDAI, a third UL approval 606C associated with the third tDAI, and a second UL approval 606C associated with the first tDAI. It may further receive a fourth UL approval (606D). The first UL approval 606A may schedule the first PUSCH 614A, the second UL approval 606B may schedule the second PUSCH 614B, and the third UL approval 606C may schedule the third PUSCH 614B. PUSCH 614C may be scheduled, and a fourth UL grant 606D may schedule a fourth PUSCH 614D. The second PUSCH 614B, third PUSCH 614C, and fourth PUSCH 614D may overlap with PUCCH 612. The first PUSCH 614A, second PUSCH 614B, third PUSCH 614C, fourth PUSCH 614D, and PUCCH 612 may be on different CCs or the same CC. For example, PUCCH 612 may be on CC0, PUSCH 614A may be on CC1, PUSCH 614B may be on CC2, and PUSCH 614C may be on CC3. and PUSCH 614D may be on CC4.

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

Based on the priority rules described in relation 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 the PUCCH. . However, if one DL grant is missing from the transmission, base station 504 and UE 502 may have a different understanding of the set of PUSCHs. For example, example 700 of FIG. 7 shows a first DL grant 702A, a second DL grant 702B, a first PDSCH 704A scheduled by the first DL grant 702A, and a second DL grant. A second PDSCH 704B scheduled by 702B, a first UL grant 706A associated with the first tDAI, a second UL grant 706B associated with the second tDAI, a third UL grant associated with the third tDAI ( 706C), a fourth UL approval (706D) associated with a fourth tDAI, a first PUSCH (714A) scheduled by a first UL approval (706A), a second PUSCH (714B) scheduled by a second UL approval (706B) ), the third PUSCH (714C) scheduled by the third UL grant (706C), the fourth PUSCH (714D) scheduled by the third UL grant (706D), and the first PDSCH (704A) and the second PDSCH ( It may also include a PUCCH 712 associated with 704B). As illustrated in FIG. 7 , the second DL grant 702B may be missing (i.e., not successfully received by the UE 502), which means that the second PDSCH 704B may be This may prevent it from being scheduled successfully. Based on the procedure illustrated in FIG. 6, base station 504 may expect UE 502 to multiplex the HARQ-ACK on PUCCH 712 on second PUSCH 714B, and the bits in the HARQ-ACK Their number may be based on the second tDAI. However, because the second PDSCH 704B was not successfully scheduled for the UE 502, the UE 502 may not recognize the portion 712A of the PUCCH 712 that is associated with the second PDSCH 704B. there is. Accordingly, UE 502 may view PUSCH 714B as not overlapping with PUCCH 712 and thus UE 502 may exclude PUSCH 714B from the multiplexing procedure. The third PUSCH 714C and fourth PUSCH 714D may be determined by the UE 502 to be a set of overlapping PUSCHs, and the PUSCH 714B may be excluded by the UE 502 from the set of overlapping PUSCHs. It may be possible. UE 502 may then multiplex the HARQ-ACK on PUCCH 712 on third PUSCH 714C, and the number of bits of the HARQ-ACK may be based on the third tDAI, thus base station 504 ) causes a difference between the expectations and the actual performance of the UE 502. In turn, this may cause problems with communications between base station 504 and UE 502.

In another example, all DL grants may be missed and the UE 502 may not be able to determine PUSCHs that overlap the PUCCH. For example, example 800 of FIG. 8 shows a first DL grant 802A, a second DL grant 802B, a first PDSCH 804A scheduled by the first DL grant 802A, and a second DL grant. A second PDSCH 804B scheduled by 802B, a first UL grant 806A associated with the first tDAI, a second UL grant 806B associated with the second tDAI, a third UL grant associated with the third tDAI ( 806C), a fourth UL approval (806D) associated with a fourth tDAI, a first PUSCH (814A) scheduled by a first UL approval (806A), a second PUSCH (814B) scheduled by a second UL approval (806B) ), the third PUSCH (814C) scheduled by the third UL grant (806C), the fourth PUSCH (814D) scheduled by the third UL grant (806D), and the first PDSCH (804A) and the second PDSCH ( It may also include a PUCCH 812 associated with 804B). As illustrated in FIG. 8 , the first DL grant 802A and the second DL grant 802B may be missing, which means that the first PDSCH 804A and the second PDSCH 804B are present for the UE 502. This may prevent it from being scheduled successfully. Based on the procedure illustrated in FIG. 6, base station 504 may expect UE 502 to multiplex HARQ-ACK on PUCCH 812 on one PUSCH, such as second PUSCH 814B, and HARQ The number of bits in -ACK may be expected to be based on a tDAI, such as the second tDAI. However, since 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, The set of PUSCHs that overlap PUCCH 812 may not be determined by UE 502.

In some aspects, the UE 502 may not be able to determine the set of overlapping PUSCHs based on whether the PUSCHs actually overlap a PUCCH. Instead, all PUSCHs are a set of overlapping PUSCHs, regardless of whether they actually overlap with a PUCCH HARQ-ACK, as long as its tDAI associated with the UL grant scheduling the PUSCH indicates a non-zero number of HARQ-ACK bits. may be included by the UE 502. That is, the UE 502 may not be able to determine whether the PUSCH overlaps the PUCCH and then determine UCI multiplexing, but the UE 502 may not be able to determine whether the UL grant scheduling the PUSCH is non-zero tDAI. It may include all PUSCHs in the UCI multiplexing procedure as long as they are associated with. For example, if tDAI indicates that zero HARQ-ACK bits are multiplexed on the first PUSCH, the first PUSCH may be excluded from the UCI multiplexing procedure. If 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. That is, if 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, example 900 of FIG. 9 shows a first DL grant 902A, a second DL grant 902B, a first PDSCH 904A scheduled by the first DL grant 902A, and a second DL grant. A second PDSCH 904B scheduled by 902B, a first UL grant 906A associated with the first tDAI, a second UL grant 906B associated with the second tDAI, a third UL grant associated with the third tDAI ( 906C), a fourth UL approval (906D) associated with a fourth tDAI, a first PUSCH (914A) scheduled by a first UL approval (906A), a second PUSCH (914B) scheduled by a second UL approval (906B) ), the third PUSCH (914C) scheduled by the third UL grant (906C), the fourth PUSCH (914D) scheduled by the fourth UL grant (906D), and the first PDSCH (904A) and the second PDSCH ( It may also include a PUCCH 912 associated with 904B). As illustrated in FIG. 9 , the second DL grant 902B may be missing (i.e., not successfully received by UE 502), which means that the second PDSCH 904B may be present for UE 502. This may prevent it from being scheduled successfully. In some aspects, UE 502 may select the first PUSCH 914A as the host PUSCH and multiplex one or more HARQ-ACK bits on the first PUSCH 914A, with the number of bits being equal to the first PUSCH 914A. ) based on the first tDAI in the first UL approval 906A scheduling. Even though the first DL grant 902A may also be missing, causing the first PDSCH 904A and the second PDSCH 904B to not be successfully scheduled for the UE 502, the UE may nevertheless receive the first PUSCH 914A ) as the host PUSCH and multiplex one or more HARQ-ACK bits on the first PUSCH 914A, the number of bits being equal to the first UL grant 906A scheduling the first PUSCH 914A. Based on tDAI.

In some aspects, if all DL grants are missing, the UE 502 may use the 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 or the resource with the longest duration in the PUCCH resource set. In some aspects, the reference PUCCH HARQ-ACK resource may be a PUCCH that spans an entire slot or subslot. For example, example 1000 of FIG. 10 shows a first DL grant 1002A, a second DL grant 1002B, a first PDSCH 1004A scheduled by the first DL grant 1002A, and a second DL grant. A second PDSCH (1004B) scheduled by (1002B), a first UL grant (1006A) associated with the first tDAI, a second UL grant (1006B) associated with the second tDAI, a third UL grant (1006B) associated with the third tDAI ( 1006C), a fourth UL approval (1006D) associated with a fourth tDAI, a first PUSCH (1014A) scheduled by a first UL approval (1006A), a second PUSCH (1014B) scheduled by a second UL approval (1006B) ), the third PUSCH (1014C) scheduled by the third UL grant (1006C), the fourth PUSCH (1014D) scheduled by the fourth UL grant (1006D), and the first PDSCH (1004A) and the second PDSCH ( It may also include a PUCCH 1012 associated with 1004B). As illustrated in FIG. 10 , the first DL grant 1002A and the second DL grant 1002B may be missing, which means that the first PDSCH 1004A and the second PDSCH 1004B are present for UE 502. This may prevent it from being scheduled successfully. Because neither the first PDSCH 1004A nor the second PDSCH 1004B was successfully scheduled for the UE 502, the UE 502 may not know when the PUCCH actually starts or ends. The UE 502 may then use the reference PUCCH 1012 to determine where the PUCCH begins and ends. Based on reference PUCCH 1012, UE 502 may determine that the second PUSCH 1014B, third PUSCH 1014C, and fourth PUSCH 1014D overlap with reference PUCCH 1012. UE 502 may multiplex the HARQ-ACK bits on the second PUSCH 1014B, with the number of bits based on the second tDAI associated with the UL grant 1006B scheduling the second PUSCH 1014B. In some aspects, reference PUCCH 1012 may be the first resource or the resource with the longest duration in the set of PUCCH resources.

In some aspects, the UE 502 may multiplex the HARQ-ACK bits in one slot, and the UE 502 may multiplex a non-zero number of HARQ bits (such as HARQ-ACK bits) on the PUSCH. may receive exactly one UL approval associated with a non-zero tDAI indicating that HARQ-ACK bits may be multiplexed on the PUSCH scheduled by the UL grant associated with 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, with a subslot-based HARQ codebook (CB), the UE 502 may multiplex the HARQ-ACK bits in one subslot, and the UE 502 may select exactly one UL associated with a non-zero tDAI. You can also receive approval. HARQ-ACK bits may be multiplexed on the PUSCH scheduled by the UL grant associated with 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, the UE 502 may receive more than one UL grant with a non-zero tDAI in one slot, and the UE 502 may receive the tDAI indicating the largest number of HARQ-ACK bits and PUCCH HARQ-ACK may be multiplexed on PUSCH scheduled by the associated UL grant.

In some aspects, the UE 502 may receive more than one UL grant with non-zero tDAI in one slot, and the UE 502 may receive the last of the UL grants scheduling PUSCHs in a slot. The PUCCH HARQ-ACK may be multiplexed on the PUSCH scheduled by the received (i.e., last received on time) or first received UL grant. In some aspects, the UE 502 may choose to select the PUSCH in one slot to multiplex the PUCCH HARQ-ACK.

In some aspects, UE 502 may take the maximum of tDAI and multiplex it on each PUSCH. In some aspects, UE 502 may consider mod 4 operation when maximizing tDAI. In some aspects, each PUSCH with an grant that includes tDAI may carry x bits of UCI, where tDAI is equal to x. For example, for slot-based HARQ CB or subslot-based HARQ CB, each PUSCH with an grant containing tDAI may carry x bits of UCI. The UE 502 may choose between having one PUSCH per slot or subslot or having each PUSCH with an grant that includes tDAI, where tDAI may carry x bits of the UCI equal to x. .

In some aspects, UE 502 may consider PUCCH configurations when selecting PUSCH. For example, even if the UE 502 is missing DL grants/DCIs, when the UE 502 selects a PUSCH to multiplex the HARQ bits, the selected PUSCH may have occurred had the DL grants/DCIs not been missing. It can also respond to existing scheduling scenarios. For example, if the UE selects a PUSCH to multiplex X bits, there may be a PUCCH resource that configures and overlaps with the PUSCH that may carry x bits.

In some aspects, a timeline may be defined over PUSCHs scheduled in the same slot/subslot. In one non-limiting example, the grant to schedule the second PUSCH with a different tDAI than the first PUSCH may be no later than a defined time, such as N4, from the start or end symbol of the first PUSCH. In some aspects, a defined time, such as N4, may be the latest time at which PUSCHs with different tDAIs may be scheduled in a given slot/subslot, with the reference being from the start symbol of the first PUSCH with tDAI. It may be possible. For example, the association between PUSCHs and subslots may be defined based on the start symbol of each PUSCH. In some aspects, a timeline may be applied across PUSCHs scheduled with a UL grant indicating non-zero tDAI. For example, a timeline may be applied across all PUSCHs in a slot or subslot independently of the tDAI value associated with the PUSCH or independently of whether tDAI is configured in the UL grant scheduling the PUSCH.

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

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

At 1102, the UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits, where one or more of the plurality of PUSCHs is associated with one or more UL grants, and one or more UL grants are associated with one or more UL tDAI Contains values. For example, the UE 502 may select at least one of a plurality of PUSCHs 512 to multiplex one or more UCI bits, and may select a plurality of 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) are each UL approved, e.g. Approved (606A/B/C/D), UL Approved (806A/B/C/D), UL Approved (806A/B/C/D), UL Approved (906A/B/C/D), or UL Approved (1006A/B/C/D), one or more UL approvals include one or more UL tDAI values. In some aspects, a subset of PUSCHs may each be associated with a subset of UL grants each associated with a UL tDAI value. In some aspects, one or more subsets of 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 UL tDAI values. In some aspects, 1102 may be performed by selection component 1444 of FIG. 14 .

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

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

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

At 1204, the UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits, each of the plurality of PUSCHs may be associated with a UL grant, and one or more UL grants include one or more UL tDAI values. do. For example, the UE 502 may select at least one of a plurality of PUSCHs 512 to multiplex one or more UCI bits, and may select a plurality of 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) are each UL approved, e.g. Approved (606A/B/C/D), UL approved (806A/B/C/D), UL approved (806A/B/C/D), UL approved (906A/B/C/D), UL approved ( 1006A/B/C/D), one or more UL approvals include one or more UL tDAI values. In some aspects, 1204 may be performed by selection component 1444 of FIG. 14 . In some aspects, at least one of the plurality of PUSCHs at least partially overlaps 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, one or more UCI bits may be one or more HARQ-ACK bits. In some aspects, one or more HARQ-ACK bits may correspond to a PUCCH, such as PUCCH 514, PUCCH 612, PUCCH 712, PUCCH 812, PUCCH 912, or PUCCH 1012. In some aspects, at least one of the plurality of PUSCHs has an associated UL approval, such as UL approval (506A/B/C/D), UL approval (606A/B/C/D), UL approval (806A/B/ C/D), UL Approved (806A/B/C/D), UL Approved (906A/B/C/D), or UL Approved (1006A/B/C/D). It may be possible. In some aspects, the UE may detect at least one PUCCH based on at least one DL grant. In some aspects, a UE may select at least one of a plurality of PUSCHs based on a non-zero UL tDAI value associated with a UL grant associated with each of the at least one selected PUSCHs. In some aspects, at least one of the plurality of PUSCHs is excluded based on a zero UL tDAI value indicating that no HARQ bits may be multiplexed on the PUSCH associated with the UL grant associated with each of the at least one excluded PUSCH. It could be. For example, a zero UL tDAI value may indicate that no HARQ bits may be multiplexed on the PUSCH scheduled by the UL grant associated with the zero UL tDAI value. In some aspects, the UL tDAI value may indicate the number of HARQ-ACK bits. In some aspects, a subset of PUSCHs may each be associated with a subset of UL grants each associated with a UL tDAI value. In some aspects, one or more subsets of 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 UL tDAI values. In some aspects, the UE selects at least one of a plurality of PUSCHs to multiplex one or more UCI bits based on not detecting a DL DCI with HARQ in the same slot or the same subslot associated with at least one of the plurality of PUSCHs. You can choose; The UE may select one (eg, any one) of multiple PUSCHs.

In some aspects, a UE may be scheduled to transmit PUSCH in a slot or subslot, and the UE may not receive a DL grant associated with transmission of HARQ-ACK in the associated slot or subslot. In some aspects, a UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits 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 of the PUCCH resource set. In some aspects, the reference PUCCH HARQ-ACK resource may include the longest duration resource in the PUCCH resource set. In some aspects, the reference PUCCH HARQ-ACK resource may be a PUCCH that spans an entire slot or subslot. In some aspects, a UE may receive one UL grant associated with a non-zero tDAI value in one slot without receiving additional UL grants in that slot. In some aspects, a UE may be configured with a subslot-based HARQ codebook, wherein the UE may receive one UL associated with a non-zero tDAI value in one subslot without receiving additional UL grants in that one subslot. An acknowledgment may be received, and the PUSCH associated with the UL grant is associated with one subslot based on the start symbol of the PUSCH. In some aspects, more than one UL grant received in the same slot may be associated with the same tDAI value. In some aspects, a 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 a plurality of PUSCHs to multiplex one or more UCI bits based on the maximum number associated with the UL tDAI value. In some aspects, a UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits based on the last received UL grant associated with at least one of the plurality of PUSCHs. In some aspects, a UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits based on an initially received UL grant associated with at least one of the plurality of PUSCHs. In some aspects, the UE may multiplex the maximum tDAI value on each PUSCH of a plurality of PUSCHs. In some aspects, each PUSCH of the plurality of PUSCHs may carry X bits of UCI, where X may be equal to the associated tDAI value. In some aspects, a UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits based at least in part on a PUCCH configuration that indicates the maximum number of bits that the PUCCH resource can carry. In some aspects, a UE may select at least one of a plurality of PUSCHs to multiplex one or more UCI bits based on a defined timeline within a slot or subslot.

At 1206, the UE may transmit one or more UCI bits to the base station that are multiplexed with at least one of the plurality of PUSCHs. For example, UE 502 has PUSCH (614A/B/C/D), PUSCH (714A/B/C/D), PUSCH (814A/B/C/D), PUSCH (914A/B/C/ D), or one or more UCI bits multiplexed with at least one of a plurality of PUSCHs, such as PUSCH (1014A/B/C/D), may be transmitted to the base station 504. In some aspects, 1206 may be performed by PUSCH component 1446 of FIG. 14. A base station may also be a network entity, such as a network node.

Figure 13 is a flow chart 1300 of a method of wireless communication. The method may be performed by a base station (e.g., base station 102/180, base station 504; device 1502). A base station may also 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 to the UE 502 at least one of one or more DL grants 506 or one or more UL grants 508, where the one or more UL grants correspond to one or more UL tDAI values. includes them. In some aspects, 1302 may be performed by approval component 1542 of FIG. 15 . In some aspects, more than one UL grant transmitted in the same slot may be associated with the same tDAI value. In some aspects, a base station may be configured with a subslot-based HARQ codebook, wherein the base station can transmit one UL associated with a non-zero tDAI value in one subslot without receiving additional UL grants in that subslot. Approval can also be sent. In some aspects, a PUSCH associated with a UL grant may be associated with one subslot based on the start symbol of the PUSCH. In some aspects, more than one UL grant transmitted in the same slot may be associated with the same tDAI value. In some aspects, a base station may be configured with a subslot-based HARQ codebook, and more than one UL grant transmitted in the same subslot may be associated with the same tDAI value. In some aspects, a subset of UL grants may each be associated with a UL tDAI value. In some aspects, one or more subsets of 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 UL tDAI values.

At 1304, the base station may receive one or more UCI bits from the UE that are multiplexed with at least one of a plurality of PUSCHs. For example, base station 504 may receive, from UE 502, PUSCH (614A/B/C/D), PUSCH (714A/B/C/D), PUSCH (814A/B/C/D), PUSCH ( 914A/B/C/D), or one or more UCI bits multiplexed with at least one of a plurality of PUSCHs, such as PUSCH (1014A/B/C/D). In some aspects, 1304 may be performed by PUSCH component 1544 of FIG. 15. In some aspects, at least one of the plurality of PUSCHs can at least partially overlap 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, one or more UCI bits may be one or more HARQ-ACK bits. In some aspects, one or more HARQ-ACK bits may correspond to PUCCH. In some aspects, the UL tDAI value may indicate the number of HARQ-ACK bits. In some aspects, each PUSCH of the plurality of 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 hardware implementation for device 1402. Device 1402 may be a UE, a component of a UE, or implement UE functionality. In some aspects, 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, device 1402 includes one or more subscriber identity module (SIM) cards 1420, a secure digital (SD) card 1408, and an applications processor 1406 coupled to a screen 1410, a Bluetooth module ( 1412), a wireless local area network (WLAN) module 1414, a global positioning system (GPS) module 1416, and a power supply 1418. Cellular baseband processor 1404 communicates with UE 104 and/or BS 102/180 via cellular RF transceiver 1422. Cellular baseband processor 1404 may include computer-readable media/memory. Computer-readable media/memory may be non-transitory. Cellular baseband processor 1404 is responsible for general processing, including execution of software stored on computer-readable media/memory. The software, when executed by cellular baseband processor 1404, causes cellular baseband processor 1404 to perform various functions described above. Computer-readable media/memory may also be used to store data that is manipulated by cellular baseband processor 1404 when executing software. Cellular baseband processor 1404 further includes a receive component 1430, a communications manager 1432, and a transmit component 1434. Communications manager 1432 includes one or more illustrated components. Components within communications manager 1432 may be stored on computer-readable media/memory and/or configured as hardware within cellular baseband processor 1404. Cellular baseband processor 1404 may be a component of UE 350 and includes memory 360, and/or at least one of TX processor 368, RX processor 356, and controller/processor 359. You may. In one configuration, device 1402 may be a modem chip or include only a baseband processor 1404, and in another configuration, device 1402 may be an entire UE (e.g., see 350 in FIG. 3). and may include additional modules of device 1402.

Communications manager 1432 may be configured to receive at least one of one or more DL grants or one or more UL grants from a network entity, e.g., as described with respect to 1202 in FIG. 12 . ) may also be included. Communication manager 1432 may be configured to select at least one of a plurality of PUSCHs to multiplex one or more UCI bits, e.g., as described with respect to 1102 in FIG. 11 and 1204 in FIG. 12. It may further include a selection component 1444, wherein 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. Communications manager 1432 may be configured to transmit one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to the base station, e.g., as described with respect to 1104 in FIG. 11 and 1206 in FIG. 12. It may further include a PUSCH component 1446.

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowcharts of FIGS. 11 and 12 . Likewise, each block in the flowcharts of FIGS. 11 and 12 may be performed by a component and the device may include one or more of these components. The components may be one or more hardware components specifically configured to perform the mentioned processes/algorithms, implemented by a processor configured to perform the mentioned processes/algorithms, stored in a computer-readable medium for implementation by the processor, or , or it may be some combination thereof.

As shown, device 1402 may include various components configured for various functions. In one configuration, the apparatus 1402, and in particular the cellular baseband processor 1404, may include means for selecting at least one of a plurality of PUSCHs to multiplex one or more UCI bits, one of the plurality of PUSCHs. One or more is associated with one or more UL approvals, and one or more UL approvals include one or more UL tDAI values. Cellular baseband processor 1404 may further include means for transmitting one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to a network entity. Cellular baseband processor 1404 may further include means for receiving, from a base station, at least one of one or more DL grants or one or more UL grants. The means may be one or more of the components of device 1402 configured to perform the functions recited by the means. As described above, device 1402 may include a TX processor 368, RX processor 356, and controller/processor 359. As such, 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 enumerated by the means.

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

Communications manager 1532 may have an grant component 1542 that may transmit at least one of one or more DL grants or one or more UL grants to the UE, e.g., as described with respect to 1302 in FIG. 13 . and one or more UL approvals include one or more UL tDAI values. Communication manager 1532 may receive a PUSCH component 1544 from a UE that may receive one or more UCI bits multiplexed with at least one of a plurality of PUSCHs, e.g., as described with respect to 1304 in FIG. 13 ) may further be included.

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 13. Likewise, each block in the flowcharts of FIG. 13 may be performed by a component and the device may include one or more of the components. The components may be one or more hardware components specifically configured to perform the mentioned processes/algorithms, implemented by a processor configured to perform the mentioned processes/algorithms, stored in a computer-readable medium for implementation by the processor, or , or it may be some combination thereof.

As shown, device 1502 may include various components configured for various functions. In one configuration, the apparatus 1502, and in particular the baseband unit 1504, may include means for selecting at least one of a plurality of PUSCHs to multiplex one or more UCI bits, one of the plurality of PUSCHs The above is associated with one or more UL approvals, and the one or more UL approvals include one or more UL tDAI values. Baseband unit 1504 may further include means for transmitting one or more UCI bits multiplexed with at least one of the plurality of PUSCHs to the base station. The means may be one or more of the components of device 1502 configured to perform the functions recited by the means. As described above, device 1502 may include a TX processor 316, RX processor 370, and controller/processor 375. As such, in one configuration, the means may be a TX processor 316, an RX processor 370, and a controller/processor 375 configured to perform the functions recited by the means.

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

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein references to an element in the singular refer to "one and only" unless specifically so stated. It is not intended to mean “only one”, but rather “one or more”. Terms such as “if,” “when,” and “while” should be interpreted to mean “under those conditions” rather than implying an immediate temporal relationship or response. That is, these phrases, such as “when,” do not imply immediate action on or during the occurrence of the action; the action will occur if the condition is met; but there are no specific or immediate time constraints for the action to occur. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" does not necessarily mean It should not be construed as preferable or advantageous over other aspects. Unless explicitly stated otherwise, the term "some" refers to one or more: "at least one of A, B, or C", "A, B, or one or more of C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C or any combination thereof" are , B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, “at least one of A, B, or C”; “One or more of A, B, or C,” “At least one of A, B, and C,” “One or more of A, B, and C,” and “A, B, C, or any combination thereof.” Combinations such as A only, B only, C only, A and B, A and C, B and C, or A and B and C may be wherein any such combination may be one or more of A, B, or C. All structural and functional equivalents to elements of the various aspects described throughout this disclosure known or later to become known to those skilled in the art are expressly incorporated herein by reference and encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. "Module", "mechanism", "element", "device" Words such as "may not replace the word "means". Thus, claim elements should not be construed as means plus function unless the element is explicitly recited using the phrase “means for.”

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

Aspect 1 is an apparatus for wireless communication in a UE, comprising: memory; and at least one processor coupled to the memory, wherein the at least one processor selects at least one of a plurality of PUSCHs to multiplex one or more UCI bits, and wherein at least one of the plurality of PUSCHs is one associated with one or more UL approvals, said one or more UL approvals comprising one or more UL tDAI values; and transmit the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs to a network entity.

Aspect 2 is the device of Aspect 1, wherein at least one of the plurality of PUSCHs at least partially overlaps a PUCCH.

Aspect 3 is the apparatus of any of aspects 1-2, wherein at least one of the plurality of PUSCHs is associated with a non-zero UL tDAI value indicating 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, from a network entity, at least one of one or more DL grants or one or more UL grants. It consists of

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

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

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

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

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

Aspect 10 is the apparatus of any of aspects 1-9, wherein the UL tDAI value represents the 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, and wherein the UE receives a DL grant associated with transmission of the HARQ-ACK in the associated slot or subslot. and 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 based on a reference PUCCH HARQ-ACK resource in the PUCCH resource set. It is composed.

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

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

Aspect 14 is the apparatus of any of aspects 1-13, wherein 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-14, wherein the UE receives no additional UL grants in one slot and receives one UL grant associated with a non-zero tDAI value in that one slot. .

Aspect 16 is the apparatus of any of aspects 1-15, wherein the UE is configured with a subslot-based HARQ codebook, wherein the UE does not receive additional UL grants in one subslot and Receives one UL grant associated with a non-zero tDAI value, and the PUSCH associated with the UL grant is associated with one subslot based on the start symbol of the PUSCH.

Aspect 17 is the apparatus of any of aspects 1-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-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 at least one processor coupled to memory is configured to configure at least one of a plurality of PUSCHs to multiplex one or more UCI bits based on a maximum number associated with a UL tDAI value. It is further configured to select one.

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

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

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

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

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

Aspect 25 is the apparatus of any of aspects 1-24, wherein at least one processor coupled to memory comprises one based at least in part on a PUCCH configuration indicating a maximum number of bits that the PUCCH resource can carry. It is further configured to select at least one of the plurality of PUSCHs to multiplex the above UCI bits.

Aspect 26 is the apparatus of any of aspects 1-25, wherein at least one processor coupled to memory comprises a plurality of PUSCHs to multiplex one or more UCI bits based on a defined timeline within a slot or subslot. It is further configured to select at least one of the following.

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

Aspect 28 is an apparatus for wireless communication in a network entity, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor transmits, to the UE, at least one of one or more DL grants or one or more UL grants, the one or more UL grants Contains one or more UL tDAI values -; And it is configured to receive one or more UCI bits multiplexed with at least one of the plurality of PUSCHs.

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

Aspect 30 is the apparatus of any of aspects 28-29, wherein at least one of the plurality of 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, wherein one or more HARQ-ACK bits correspond to a PUCCH.

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

Aspect 34 is the apparatus of any of aspects 28-33, wherein 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, and wherein the network entity does not receive additional UL grants in one subslot and Transmit one UL grant associated with a non-zero tDAI value in a subslot, and the PUSCH associated with the UL grant is associated with one subslot based on the start 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 wherein 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 a UCI, and X is equal to the associated tDAI value.

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

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

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

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

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

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

Aspect 45 is a computer-readable medium storing computer-executable code in a UE, which code, 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; One or more of the plurality of PUSCHs is associated with one or more UL grants, and the one or more UL grants include one or more UL tDAI values; And one or more UCI bits multiplexed with at least one of the plurality of PUSCHs are transmitted to the network entity.

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

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

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

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

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

Aspect 52 is a computer-readable medium storing computer-executable code at a network entity, which code, when executed by a processor, causes the processor to: for a UE, obtain at least one of one or more DL approvals or one or more UL approvals; transmit - one or more UL approvals include one or more UL tDAI values; One or more UCI bits multiplexed with at least one of a plurality of PUSCHs are received.

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

Claims (30)

A device for wireless communication in user equipment (UE), comprising:
Memory; and
At least one processor coupled to the memory,
The at least one processor:
Selecting at least one of a plurality of physical uplink shared channels (PUSCH) to multiplex one or more uplink control information (UCI) bits, wherein one or more of the plurality of PUSCHs receives one or more uplink (UL) grants. and wherein the one or more UL grants include one or more UL Aggregate Downlink Allocation Index (tDAI) values; and
To transmit the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs to a network entity.
A device for wireless communication in user equipment, comprising: According to claim 1,
wherein at least one of the plurality of PUSCHs at least partially overlaps a physical uplink control channel (PUCCH). According to claim 1,
wherein at least one of the plurality of PUSCHs is associated with a non-zero UL tDAI value indicating multiplexing a non-zero number of Hybrid Automatic Repeat Request (HARQ) bits on the PUSCH. According to claim 1,
The at least one processor coupled to the memory further:
An apparatus for wireless communication in user equipment, configured to receive, from the network entity, at least one of one or more downlink (DL) grants or one or more UL grants. According to claim 1,
The one or more UCI bits are one or more hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) bits. According to claim 5,
The one or more HARQ-ACK bits correspond to a physical uplink control channel (PUCCH). According to claim 1,
and wherein the at least one of the plurality of PUSCHs is selected based on the UL tDAI value of an associated UL grant. According to claim 1,
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 further:
and 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 PUSCHs. According to claim 8,
At least one of the plurality of PUSCHs is excluded based on a zero UL tDAI value indicating that no hybrid automatic repeat request (HARQ) bits will be multiplexed on the PUSCH associated with the UL grant associated with each of the at least one excluded PUSCH. A device for wireless communication in user equipment. According to claim 8,
The UL tDAI value indicates the number of Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) (HARQ-ACK) bits. According to claim 1,
The UE is scheduled to transmit a PUSCH in a slot or subslot, and the UE does not receive a DL grant associated with the transmission of a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) (HARQ-ACK) in the associated slot or subslot. and the at least one processor coupled to the memory further configures the plurality of PUSCHs to multiplex the one or more UCI bits based on a reference Physical Uplink Control Channel (PUCCH) HARQ-ACK resource in a PUCCH resource set. An apparatus for wireless communication in user equipment, configured to select at least one of the above. According to claim 11,
The reference PUCCH HARQ-ACK resource is a first resource in the PUCCH resource set. According to claim 11,
The reference PUCCH HARQ-ACK resource includes the longest duration resources in the PUCCH resource set. According to claim 11,
The reference PUCCH HARQ-ACK resource is a PUCCH spanning the entire slot or subslot, an apparatus for wireless communication in user equipment. According to claim 1,
wherein the UE receives one UL grant associated with a non-zero tDAI value in one slot and does not receive additional UL grants in the one slot. According to claim 1,
The UE is configured with a subslot-based Hybrid Automatic Repeat Request (HARQ) codebook, wherein the UE receives one UL grant associated with a non-zero tDAI value in one subslot and receives an additional UL grant in the one subslot. and wherein the PUSCH associated with the UL grant is associated with the one subslot based on the start symbol of the PUSCH. According to claim 1,
Apparatus for wireless communication in user equipment, wherein more than one UL grant received in the same slot is associated with the same tDAI value. According to claim 1,
The UE is configured with a subslot-based Hybrid Automatic Repeat Request (HARQ) codebook, and wherein more than one UL grant received in the same subslot is associated with the same tDAI value. According to claim 1,
The at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs to multiplex the one or more UCI bits based on a maximum number associated with the UL tDAI value. A device for wireless communication in equipment. According to claim 1,
The at least one processor coupled to the memory further includes the at least one of the plurality of PUSCHs to multiplex the one or more UCI bits based on a last received UL grant associated with the at least one of the plurality of PUSCHs. A device for wireless communication in user equipment, configured to select one. According to claim 1,
The at least one processor coupled to the memory further performs downlink (DL) downlink control with Hybrid Automatic Repeat Request (HARQ) in the same slot or same subslot associated with the at least one of the plurality of PUSCHs. and select the at least one of the plurality of PUSCHs to multiplex the one or more UCI bits based on not detecting information (DCI). According to claim 1,
The at least one processor coupled to the memory further includes the at least one of the plurality of PUSCHs to multiplex the one or more UCI bits based on a first received UL grant associated with the at least one of the plurality of PUSCHs. A device for wireless communication in user equipment, configured to select one. According to claim 1,
wherein the at least one processor coupled to the memory is further configured to multiplex a maximum of the tDAI value on each PUSCH of the plurality of PUSCHs. According to claim 1,
Each PUSCH of the plurality of PUSCHs carries a UCI of X bits, where X is equal to the associated tDAI value. According to claim 1,
The at least one processor coupled to the memory further multiplexes the one or more UCI bits based at least in part on a Physical Uplink Control Channel (PUCCH) configuration that indicates a maximum number of bits that a PUCCH resource can carry. Apparatus for wireless communication in user equipment, configured to select the at least one of the plurality of PUSCHs to use. According to claim 1,
The at least one processor coupled to the memory is further configured to select the at least one of the plurality of PUSCHs to multiplex the one or more UCI bits based on a defined timeline within a slot or subslot. A device for wireless communication in user equipment. According to claim 1,
An apparatus for wireless communication in user equipment, further comprising a transceiver coupled to the at least one processor. A device for wireless communication in a network entity, comprising:
Memory; and
At least one processor coupled to the memory,
The at least one processor:
For a user equipment (UE), transmitting at least one of one or more downlink (DL) grants or one or more uplink (UL) grants, wherein the one or more UL grants correspond to one or more UL total downlink allocation index ( tDAI) values; and
To receive one or more uplink control information (UCI) bits multiplexed with at least one of a plurality of physical uplink shared channels (PUSCH)
A device for wireless communication in a network entity, configured. 1. A method of wireless communication in user equipment (UE), comprising:
Selecting at least one of a plurality of physical uplink shared channels (PUSCH) to multiplex one or more uplink control information (UCI) bits, wherein one or more of the plurality of PUSCHs grants one or more uplink (UL) and wherein the one or more UL grants include one or more UL Aggregate Downlink Allocation Index (tDAI) values; and
Transmitting the one or more UCI bits multiplexed with the at least one of the plurality of PUSCHs to a network entity. A method of wireless communication in a network entity, comprising:
Transmitting, for a user equipment (UE), at least one of one or more downlink (DL) grants or one or more uplink (UL) grants, wherein the one or more UL grants correspond to one or more UL aggregate downlink allocation indexes. said transmitting comprising (tDAI) values; and
A method of wireless communication in a network entity comprising receiving one or more uplink control information (UCI) bits multiplexed with at least one of a plurality of physical uplink shared channels (PUSCH).

Images