Techniques for enhancing reduced HARQ-ACK multiplexing on pusch

By multiplexing the HARQ-ACK feedback bit on the PUSCH and using the bit indicator to determine the repetition amount, the problem of overlapping HARQ feedback and repetition time in 5G NR is solved, improving data rate and spectrum efficiency and optimizing the performance of wireless communication system.

CN118985111APending Publication Date: 2024-11-19QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033011.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-10-31
Filing Date
2023-04-17
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In existing 5G NR technology, the overlap of HARQ feedback and repetition in the uplink transmission leads to low efficiency and makes it difficult to effectively utilize spectrum resources.

Method used

By multiplexing the HARQ-ACK feedback bit on the PUSCH, using bit indicators to determine the amount of repetition, and multiplexing in the time domain, the time overlap problem is solved, and the data rate and spectral efficiency are improved.

Benefits of technology

It improves data rate and spectral efficiency, solves the inefficiency problem caused by HARQ feedback and repetition time overlap, and optimizes the performance of wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985111A_ABST
    Figure CN118985111A_ABST
Patent Text Reader

Abstract

Disclosed herein are apparatuses, methods, and computer readable media for facilitating multiplexing with repeated HARQ feedback on a PUSCH. An example method for wireless communication at a UE includes receiving an uplink grant that schedules uplink transmissions associated with a repetition amount, the uplink grant including a bit indicator. The example method also includes transmitting a first repetition of the uplink transmission. The first repetition may include multiplexing of an amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH for which scheduling is granted by a downlink, and the amount of HARQ-ACK feedback bits may be based on the bit indicator. The first repetition and the HARQ-ACK feedback may overlap in the time domain.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 363,424, filed on April 22, 2022, entitled “TECHNIQUES TO ENHANCE HARQ-ACK MULTIPLEXING ON PUSCH WITH REPETITIONS,” and U.S. Non-Provisional Patent Application Serial No. 18 / 051,491, filed on October 31, 2022, entitled “TECHNIQUES TO ENHANCE HARQ-ACK MULTIPLEXING ON PUSCH WITH REPETITIONS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications utilizing uplink transmission grants with repetition. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication are provided. An apparatus may include a user equipment (UE). The example apparatus may receive an uplink grant that schedules an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator. The example apparatus may also send a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for a hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback for a physical downlink shared channel (PDSCH) scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of these HARQ-ACK feedback bits based on the bit indicator.

[0008] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication are provided. An apparatus may include a network entity, such as a base station. The example apparatus outputs an uplink grant that schedules an uplink transmission associated with an amount of repetitions at a UE, the uplink grant including a bit indicator. The example apparatus may also obtain a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of a PDSCH scheduled by a downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of these HARQ-ACK feedback bits based on the bit indicator.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features described in full below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 An example communication flow between a base station and a UE according to the teachings disclosed herein is illustrated.

[0017] Figure 5 is a diagram illustrating a timeline of a UE performing hybrid automatic retransmission (HARQ) feedback multiplexing with repetition on a physical uplink shared channel (PUSCH) in accordance with the teachings disclosed herein.

[0018] Fig. 6A is a diagram illustrating a timeline for a UE to perform multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a base station in accordance with the teachings disclosed herein.

[0019] Figure 6B is a diagram illustrating a timeline for a UE to perform multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a base station in accordance with the teachings disclosed herein.

[0020] Figure 7is a diagram illustrating a timeline for a UE to perform multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a base station in accordance with the teachings disclosed herein.

[0021] Figure 8 is a diagram illustrating a timeline for a UE to perform multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a base station in accordance with the teachings disclosed herein.

[0022] Fig. 9 An example communication flow between a base station and a UE according to the teachings disclosed herein is illustrated.

[0023] Fig.10 is a diagram illustrating a timeline for a UE to perform multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a base station in accordance with the teachings disclosed herein.

[0024] Fig.11 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0025] Fig.12 is a flow chart of a method of wireless communication at a UE according to the teachings disclosed herein.

[0026] Fig.13 is a diagram illustrating an example of a hardware implementation of an example network entity.

[0027] Fig.14 is a flow chart of a method of wireless communication at a network entity according to the teachings disclosed herein.

[0028] Fig.15 is a flow chart of a method of wireless communication at a network entity according to the teachings disclosed herein.

[0029] Fig.16 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0030] The wireless communication system may support data transmission using HARQ, for example, to improve reliability. For HARQ, the sending device may transmit the initial transmission of the message, and if necessary, may transmit one or more additional transmissions of the message until a termination event occurs. For example, the termination event may include an indication that the message is correctly decoded by the receiving device or that the maximum transmission amount of the message has occurred. After each transmission of the message, if the message is correctly decoded, the receiving device may transmit an acknowledgment (ACK), or if the message is incorrectly decoded or missed, the receiving device may transmit a negative acknowledgment (NACK). If a NACK is received, the sending device may transmit another transmission of the message, and if an ACK is received, the sending device may terminate the transmission of the message. As used herein, a "message" may also be referred to as a transport block, a packet, a codeword, a data block, etc.

[0031] In some examples, a sending device may transmit one or more transmissions of a message based on the scheduling information. For example, a sending device such as a UE may receive an uplink grant that schedules the UE to send an uplink message such as on a PUSCH. Additionally or alternatively, a receiving device may receive one or more transmissions of a message based on the scheduling information. For example, a receiving device such as a UE may receive a downlink grant that schedules the UE to receive a downlink message such as on a PDSCH.

[0032] In some scenarios, a device may be configured to send a first message and receive a second message. For example, a UE may receive a downlink grant that schedules the UE to receive a downlink message, and may also receive an uplink grant that schedules one or more transmissions of the UE to send an uplink message. In some such examples, repetition of the uplink message may overlap in time with the transmission of HARQ feedback associated with the downlink message.

[0033] The various aspects disclosed herein provide techniques for improving HARQ feedback multiplexing with repetitions on PUSCH. The disclosed techniques can provide higher data rates, improve capacity and / or improve spectral efficiency. For example, the various aspects disclosed herein can configure a UE to determine to perform multiplexing on repetitions, regardless of whether the repetitions overlap in time with HARQ feedback. Additionally, the UE can perform multiplexing based on the amount of bits indicated by an uplink grant. By determining to perform multiplexing based on the amount of bits indicated by an uplink grant (e.g., a bit indicator) and regardless of whether there is an overlap in time, the UE can solve problems associated with missed downlink grants. In some examples, the bit indicator may include a bit indicator set, which includes multiple bit indicators. For example, the amount of bit indicators in the bit indicator set may correspond to the amount of repetitions configured for an uplink message. The amount of repetitions may be indicated via an uplink grant and / or via radio resource control (RRC) signaling. In some such examples, the UE can use the corresponding bit indicators in the bit indicator set to determine the amount of z bits to be multiplexed on the corresponding repetitions. In other examples, the set of bit indicators may include a one-bit indicator applied to each repetition of the uplink message.

[0034] On the other hand, the UE may be configured to determine whether to perform multiplexing on the repetition based on the bit indicator included in the uplink grant. For example, when the value of the bit indicator meets the threshold (e.g., x bits of the bit indicator are greater than or equal to the threshold), the UE may perform multiplexing on the repetition, regardless of whether the repetition overlaps in time with the HARQ feedback scheduled by the downlink grant. In an example where the value of the bit indicator does not meet the threshold (e.g., x bits are less than the threshold), when the repetition overlaps in time with the HARQ feedback, the UE may multiplex x bits of the HARQ feedback on the repetition. When the repetition does not overlap in time with the HARQ feedback, the UE may also skip multiplexing or multiplex zero bits on the repetition.

[0035] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0036] Several aspects of the telecommunication system are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0037] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0038] Therefore, in one or more example aspects, specific implementations and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-accessible instructions or data structures in the form of computer executable code.

[0039] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described 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 necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0040] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0041] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0042] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0043] Figure 1 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs (e.g., CU 110), which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more decomposed base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) (e.g., near RT RIC 125) via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework (e.g., SMO framework 105), or both. CU 110 may communicate with one or more DUs (e.g., DU 130) via corresponding mid-haul links (such as F1 interfaces). DU 130 may communicate with one or more RUs (e.g., RU 140) via corresponding outbound links. RU 140 may communicate with corresponding UEs (e.g., UE 104) via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served by multiple RUs simultaneously.

[0044] Units (i.e., CUs (e.g., CU 110), DUs (e.g., DU 130), RUs (e.g., RU 140), and near-RT RICs (e.g., near-RT RIC 125), non-RT RICs (e.g., non-RT RIC 115) and each of the SMO framework 105 may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals from one or more of the other units or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units on a wireless transmission medium.

[0045] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). If necessary, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0046] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0047] Lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 140 may be implemented to handle air (OTA) communications with one or more UEs (e.g., UE 104). In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communications with the RU 140 may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0049] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs, one or more DUs, or both, and the O-eNB with the near-RT RIC 125.

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

[0051] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between a RU (e.g., RU 140) and a UE (e.g., UE 104) may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier 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).

[0052] Certain UEs may communicate with each other using device-to-device (D2D) communications (e.g., D2D communication links 158). The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communications may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0053] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / Wi-Fi AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0054] The electromagnetic spectrum is typically subdivided into various categories, 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 a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0055] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

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

[0057] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0058] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0059] The core network 120 may include an access and mobility management function (AMF) (e.g., AMF 161), a session management function (SMF) (e.g., SMF 162), a user plane function (UPF) (e.g., UPF 163), a unified data management (UDM) (e.g., UDM 164), one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) (e.g., GMLC 165) and a location management function (LMF) (e.g., LMF 166). However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or a serving base station (e.g., base station 102). The measured signal can be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or one or more of other systems / signals / sensors.

[0060] Examples of UE include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, 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 equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.

[0061] Reference again Figure 1 In certain aspects, a device in communication with a network entity, such as a UE 104 in communication with a base station 102 or a component of a base station (e.g., CU 110, DU 130, and / or RU 140), may be configured to manage one or more aspects of wireless communication. For example, the UE 104 may include a repetition component 198 configured to facilitate performing HARQ feedback multiplexing with repetitions on a PUSCH.

[0062] In certain aspects, the repetition component 198 may be configured to receive an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator. The example repetition component 198 may also be configured to send a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits based on the bit indicator.

[0063] In another configuration, a network entity such as the base station 102 or a component of the base station (e.g., the CU 110, the DU 130, and / or the RU 140) may be configured to manage one or more aspects of wireless communication. For example, the base station 102 may include a scheduling component 199 configured to facilitate performing HARQ feedback multiplexing with repetitions on the PUSCH.

[0064] In certain aspects, the scheduling component 199 may be configured to output an uplink grant that schedules an uplink transmission associated with an amount of repetitions at the UE, the uplink grant comprising a bit indicator. The example scheduling component 199 may also be configured to obtain a first repetition of the uplink transmission, the first repetition multiplexing an amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits being based on the bit indicator.

[0065] Various aspects disclosed herein provide techniques for improving HARQ feedback multiplexing with repetition on PUSCH. The disclosed techniques may provide higher data rates, increase capacity and / or increase spectral efficiency.

[0066] Although the following description provides examples for 5G NR (and more specifically, for a single uplink transmission grant with repetitions), the concepts described herein may be applicable to other similar areas (such as, LTE, LTE-A, CDMA, GSM, and / or other wireless technologies) where the UE may multiplex HARQ feedback and PUSCH with repetitions.

[0067] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within the subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0068] FIG. 2A to FIG. 2D The frame structure is illustrated, and various 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 (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a micro-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is regular or extended. For a regular CP, each time slot may include 14 symbols, and for an extended CP, each time 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 may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see

[0069] Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0070]

[0071] Table 1: Parameter set, SCS and CP

[0072] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μAs shown in Table 1, the subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a conventional CP is provided, where there are 14 symbols per slot, and the parameter set μ=2, where there are 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 frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0073] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0074] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0075] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a 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., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0076] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0077] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0078] Figure 3 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 3 In the illustrated example of , the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. Figure 3 As shown in , base station 310 includes a transmit processor (TX processor 316), a transmitter 318Tx, a receiver 318Rx, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. Example UE 350 includes antenna 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, base station 310 and / or UE 350 may include additional or alternative components.

[0079] In the DL, Internet Protocol (IP) packets may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0080] The TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by UE 350. Each spatial stream may then be provided to a different antenna in antenna 320 via a separate transmitter (e.g., transmitter 318Tx). Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0081] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna in the antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal 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 point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

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

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

[0084] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different ones of the antennas 352 via separate transmitters (e.g., transmitter 354Tx). Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0085] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding one of the antennas 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0087] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The repeating component 198 performs various aspects.

[0088] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The scheduling component 199 performs various aspects.

[0089] The wireless communication system may support data transmission using HARQ, for example, to improve reliability. For HARQ, a sending device may transmit an initial transmission of a message and, if necessary, may transmit one or more additional transmissions of the message until a termination event occurs. For example, a termination event may include an indication that a message is correctly decoded by a receiving device or that a maximum transmission of a message has occurred. After each transmission of a message, the receiver may transmit an ACK (sometimes referred to as a HARQ-ACK) if the message is correctly decoded, or a NACK (sometimes referred to as a HARQ-NACK) if the message is incorrectly decoded or missed. If a NACK is received, the sending device may transmit another transmission of the message, and if an ACK is received, the sending device may terminate the transmission of the message.

[0090] In some examples, a sending device may transmit one or more transmissions of a message based on the scheduling information. For example, a sending device such as a UE may receive an uplink grant that schedules the UE to send an uplink message such as on a PUSCH. Additionally or alternatively, a receiving device may receive one or more transmissions of a message based on the scheduling information. For example, a receiving device such as a UE may receive a downlink grant that schedules the UE to receive a downlink message such as on a PDSCH.

[0091] In some scenarios, a device may be configured to send a first message and receive a second message. For example, a UE may receive a downlink grant that schedules the UE to receive a downlink message and an uplink grant that schedules the UE to send one or more transmissions of an uplink message. In some such examples, repetition of an uplink message may overlap in time with the transmission of HARQ feedback associated with the downlink message.

[0092] Figure 4 An example communication flow 400 between a network entity 402 and a UE 404 as presented herein is illustrated. One or more aspects described with respect to the network entity 402 may be performed by a component of a base station, such as a CU, DU, and / or RU. In the illustrated example, the communication flow 400 facilitates the UE 404 to perform HARQ feedback multiplexing with repetition on a PUSCH. Aspects of the network entity 402 may be performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 404 may be implemented by base station 310. Figure 1 UE 104 and / or Figure 3 UE 350. Figure 4 Not shown in the illustrated example, but in additional or alternative examples, the network entity 402 and / or the UE 404 may communicate with one or more other base stations or UEs.

[0093] like Figure 4 As shown, the network entity 402 may send a downlink grant 410 that is received by the UE 404. The network entity 402 may send the downlink grant 410 on the PDCCH. The downlink grant 410 may include information related to the downlink message 420, such as PDSCH resources 412 allocated for monitoring opportunities associated with one or more transmissions of the downlink message 420. The downlink grant 410 may also include information related to HARQ feedback 432 (e.g., ACK or NACK) for the downlink message 420. For example, the downlink grant 410 may indicate the HARQ resources 414 allocated to the UE 404 for sending the HARQ feedback 432, and include a downlink bit indicator 416 indicating the amount of ACK / NACK bits allocated for the HARQ feedback 432. In some aspects, the downlink bit indicator 416 may include a downlink assignment index (DAI) that may be used to facilitate determining the amount of bits for the HARQ feedback 432.

[0094] The network entity 402 may send a downlink message 420 that is received by the UE 404. The network entity 402 may send the downlink message 420 on the PDSCH. The UE 404 may receive the downlink message 420 based on the PDSCH resources 412 indicated by the downlink grant 410. For example, the PDSCH resources 412 may indicate a first monitoring opportunity 422, and the UE 404 may monitor resources associated with the first monitoring opportunity 422 to receive the downlink message 420. The first monitoring opportunity 422 may be associated with a time resource and / or a frequency resource.

[0095] exist Figure 4 In the example of , the UE 404 may perform a generation process 430 to generate HARQ feedback 432 based on the downlink message 420. For example, the UE 404 may generate uplink control information (UCI) with ACK or NACK based on whether the UE 404 decodes the downlink message 420 at the first monitoring opportunity 422.

[0096] like Figure 4As shown, the UE 404 may send HARQ feedback 432 associated with the downlink message 420. The UE 404 may use resources allocated by the downlink grant 410 for the HARQ feedback 432. For example, the HARQ resources 414 may indicate time resources and / or frequency resources associated with the HARQ opportunity 434. The UE 404 may send the HARQ feedback 432 based on the HARQ opportunity 434. Additionally, the payload size of the HARQ feedback 432 may be based on the downlink bit indicator 416 of the downlink grant 410. The UE 404 may send the HARQ feedback 432 using UCI on a physical uplink control channel (PUCCH).

[0097] exist Figure 4 In the example of , UE 404 may also be configured to send an uplink message received by network entity 402. For example, network entity 402 may send an uplink grant 440 received by UE 404. Network entity 402 may send uplink grant 440 on PDCCH. Uplink grant 440 may include information related to the uplink message, such as PUSCH resources 442 (e.g., time resources and / or frequency resources) allocated to UE 404 for transmission of the uplink message. Uplink grant 440 may also include a repetition indicator 444 indicating the amount of repetition of the uplink message. For example, based on uplink grant 440, UE 404 may determine to send k repetitions of the uplink message, may determine the first resource allocated to the initial transmission of the uplink message, and may determine the subsequent resources allocated for k-1 repetitions of the uplink message. As described above, UE 404 may send up to k repetitions of the uplink message until a termination event occurs.

[0098] although Figure 4 An example of includes a repetition indicator 444 with the uplink grant 440, but in other examples, the UE 404 may receive the repetition indicator 444 via RRC signaling. For example, the network entity 402 may send RRC signaling 436 that is received by the UE 404. The RRC signaling 436 may include a repetition indicator 444 indicating an amount of repetitions of the uplink message.

[0099] In some examples, the repetition of the uplink message may coincide in time with (e.g., overlap) the transmission of the HARQ feedback. In examples where the uplink message repetition and the HARQ feedback overlap, the UE 404 may multiplex the HARQ feedback with the repetition. The UE 404 may perform a determination process 450 to determine whether the UCI carrying the HARQ feedback 432 overlaps with the repetition of the uplink message. For example, the UE 404 may determine that the first repetition 452 of the uplink message does not overlap with the HARQ opportunity 434. In such examples, the UE 404 may send the first repetition 452 of the uplink message received by the network entity 402. The UE 404 may send the first repetition 452 while skipping multiplexing on the first repetition 452 or by multiplexing zero bits on the first repetition 452. The UE 404 may send the first repetition 452 on the PUSCH.

[0100] In examples where uplink message repetitions overlap with HARQ feedback, the UE 404 may multiplex the HARQ feedback and the repetitions. For example, when performing the determination process 450, the UE 404 may determine that the second repetition 456 overlaps in time with the HARQ opportunity 434. In such examples, the UE 404 may perform a multiplexing process 454 to multiplex the HARQ feedback 432 with the repetitions (e.g., the second repetition 456).

[0101] In some examples, the UE 404 may multiplex the x bits of the HARQ feedback 432 with the second repetition 456. The UE 404 may receive the amount of bits of the HARQ feedback 432 to be multiplexed with the second repetition 456 via the uplink grant 440. For example, the uplink grant 440 may include a bit indicator 446 indicating the amount of bits to be multiplexed (e.g., x bits). In such examples, when the UE 404 determines that the uplink message repetition and the HARQ feedback overlap in time, the UE 404 may multiplex the x bits of the HARQ feedback 432 indicated by the bit indicator 446 with the second repetition 456. In some aspects, the bit indicator 446 may correspond to a total DAI (TDAI) that may be used to facilitate determining the amount of bits of the HARQ feedback 432 to be multiplexed. The TDAI may be referred to as "UL-TDAI" or any other name.

[0102] In the example where the bit indicator 446 indicates a quantity of bits less than or equal to a threshold, the UE 404 may truncate repetitions of x bits. In the example where the bit indicator 446 indicates a quantity of bits greater than a threshold, the UE 404 may multiplex the HARQ feedback 432 by rate matching corresponding repetitions of uplink messages.

[0103] like Figure 4As shown, UE 404 may send a second repetition 456 of the uplink message received by network entity 402. UE 404 may send second repetition 456 on PUSCH. Second repetition 456 may be a repetition of the uplink message multiplexed by x bits of HARQ feedback 432.

[0104] Figure 5 is a diagram illustrating a timeline 500 of a UE 504 performing HARQ feedback multiplexing with repetition on a PUSCH as presented herein. Figure 5 In the illustrated example of FIG. 5 , UE 504 may receive scheduling information for downlink messages and for uplink messages from network entity 502. Aspects of network entity 502 may be provided by Figure 4 Various aspects of UE 504 may be implemented by Figure 4 UE 404 is implemented.

[0105] exist Figure 5 In the illustrated example of FIG. 5 , UE 504 may receive a downlink grant 510 from network entity 502 at time T1. Aspects of downlink grant 510 may be provided by Figure 4 The downlink grant 510 may be implemented by receiving a downlink grant 410. The downlink grant 510 may provide information for receiving a PDSCH 512. Various aspects of the PDSCH 512 may be provided by Figure 4 The downlink grant 510 may include a PDSCH resource 510a, such as PDSCH resource 412, indicating a monitoring opportunity associated with time T2. The downlink grant 510 may also indicate HARQ resources 510b, such as HARQ resource 414, indicating a HARQ opportunity for the UE 504 to send HARQ feedback 514 associated with the PDSCH 512. For example, the downlink grant 510 may include a HARQ resource indicating a HARQ opportunity at time T6. When the UE 504 decodes the PDSCH 512, the HARQ feedback 514 may include an ACK, otherwise it may include a NACK.

[0106] like Figure 5 As shown, UE 504 may receive an uplink grant 520 from network entity 502 at time T3. Aspects of uplink grant 520 may be provided by Figure 4 For example, the uplink grant 520 may indicate a PUSCH resource 520a (such as PUSCH resource 442), a repetition indicator 520b (such as repetition indicator 444), and a bit indicator 520c (such as bit indicator 446). Figure 5In the example of , repetition indicator 520b may indicate that UE 504 is to send four repetitions of the uplink message. For example, and based on PUSCH resources 520a of uplink grant 520, UE 504 may determine to send a first repetition 522 ("PUSCH repetition 1") at time T4, a second repetition 524 ("PUSCH repetition 2") at time T5, a third repetition 526 ("PUSCH repetition 3") at time T6, and a fourth repetition 528 ("PUSCH repetition 4") at time T7.

[0107] exist Figure 5 In the example of , when the HARQ feedback scheduled by the downlink grant overlaps with the corresponding repetition, the UE 504 can use the bit indicator 520c of the uplink grant 520 to multiplex x bits on the repetition. For example, based on the HARQ opportunity associated with the HARQ feedback 514 and the PUSCH resource 520a associated with the repetition of the uplink message, the UE 504 can determine that the first repetition 522, the second repetition 524, and the fourth repetition 528 do not overlap in time with the HARQ opportunity. In such an example, the UE 504 can send the corresponding repetition without multiplexing, such as in combination with Figure 4 The determination process 450 and the first repetition 452 are described above.

[0108] In an example where the UE 504 determines that the HARQ opportunity and the repetition overlap in time (e.g., the third repetition 526 at time T6 and the HARQ opportunity associated with the HARQ feedback 514), the UE 504 may multiplex x bits of the HARQ feedback 514 on the corresponding repetition, such as in combination with Figure 4 The multiplexing process 454 and the second repetition 456 are described. For example, the uplink grant 520 includes a bit indicator 520c ("TDAI") indicating the amount of x bits to be multiplexed. In such an example, the UE 504 may multiplex the x bits of the HARQ feedback 514 with the third repetition 526. As described above, multiplexing the x bits of the HARQ feedback 514 with the third repetition 526 may include puncturing the x bits of the third repetition 526 or rate matching the third repetition 526.

[0109] The network entity 502 may receive repetitions of the uplink message based on the expected multiplexing of bits for each repetition. Figure 5In the example of , UE 504 may multiplex {0,0,x,0} bits for corresponding repetitions of the uplink message. Since the network entity 502 may schedule HARQ opportunities associated with the HARQ feedback 514 and repetitions of the uplink message, the network entity 502 may perform demultiplexing of each repetition based on a determination that the first repetition 522, the second repetition 524, and the fourth repetition 528 do not overlap with the HARQ opportunity and the third repetition 526 overlaps with the HARQ opportunity. That is, based on the scheduled transmission and HARQ opportunity of the repetition, the network entity 502 may determine that the third repetition 526 is a multiplexed repetition and that the remaining repetitions are non-multiplexed repetitions. Additionally, since the network entity 502 provides an uplink grant 520 (e.g., TDAIx bits) to the bit indicator 520c, the network entity 502 has the ability to determine that x bits of the HARQ feedback 514 are multiplexed with the third repetition 526. That is, to receive repetitions of an uplink message, the network entity 502 may apply {0,0,x,0} demultiplexing bits to the corresponding repetitions of the uplink message.

[0110] exist Figure 5 In the example of , UE 504 is configured with one HARQ opportunity at time T6 and is provided with a bit indicator (e.g., bit indicator 520c of uplink grant 520), which UE 504 uses to determine how many bits of HARQ feedback 514 to multiplex when the HARQ opportunity overlaps with the repetition in time. In some examples, the UE may be configured with multiple HARQ opportunities for different corresponding downlink grants. Additionally, one or more of the HARQ opportunities may overlap in time with corresponding repetitions of the uplink message.

[0111] Fig. 6A and Figure 6B is a diagram illustrating a corresponding timeline for performing HARQ feedback multiplexing with repetition on a PUSCH.

[0112] Fig. 6A 6 is a diagram illustrating a timeline 600 of a UE 604 performing multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a network entity 602 as presented herein. Fig. 6A In the example of , UE 604 may receive scheduling information for multiple downlink messages and for uplink messages from network entity 602. Aspects of network entity 602 may be Figure 4 Various aspects of UE 604 may be implemented by Figure 4 UE 404 is implemented.

[0113] exist Fig. 6AIn the illustrated example of , the network entity 602 may send three downlink grants that are received by the UE 604. The three downlink grants may schedule three downlink messages and three HARQ opportunities for sending corresponding HARQ feedback. Fig. 6A As shown, UE 604 may be configured with a first HARQ opportunity at time T2 for sending a first HARQ feedback 610 ("DL grant 1 ACK / NACK"), a second HARQ opportunity at time T4 for sending a second HARQ feedback 612 ("DL grant 2 ACK / NACK"), and a third HARQ opportunity at time T5 for sending a third HARQ feedback 614 ("DL grant 3 ACK / NACK"). Fig. 6A In the example shown, it is understood that the first HARQ feedback 610 is associated with the first downlink message at the first monitoring opportunity, such as in combination with Figure 5 The HARQ feedback 514 and the PDSCH 512 are described. In a similar manner, the second HARQ feedback 612 may be associated with the second downlink message at the second monitoring opportunity, and the third HARQ feedback 614 may be associated with the third downlink message at the third monitoring opportunity.

[0114] Similar to Figure 5 For example, Fig. 6A UE 604 may receive an uplink grant 620 from network entity 602 at time T1. Fig. 6A In the illustrated example of , UE 604 determines the amount of repetitions of the uplink message to schedule at the corresponding time based on the repetition indicator and the PUSCH resource of the uplink grant 620. For example, UE 604 may schedule four repetitions of the uplink message. Fig. 6A In the example, UE 604 may, based on the uplink grant 620, schedule a first repetition 622 ("PUSCH repetition 1") at time T2, a second repetition 624 ("PUSCH repetition 2") at time T3, a third repetition 626 ("PUSCH repetition 3") at time T4, and a fourth repetition 628 ("PUSCH repetition 4") at time T5.

[0115] exist Fig. 6AIn the example of , the uplink grant 620 includes a bit indicator 621 ("TDAI") that indicates that 2 bits are multiplexed when a temporal overlap occurs between a HARQ opportunity scheduled by a downlink grant and a repetition. Additionally, each of the downlink grants associated with the first HARQ feedback 610, the second HARQ feedback 612, and the third HARQ feedback 614 includes a respective downlink bit indicator indicating a payload size of each respective HARQ feedback. For example, the payload size of the first HARQ feedback 610 is one bit, the payload size of the second HARQ feedback 612 is two bits, and the payload size of the third HARQ feedback 614 is three bits.

[0116] exist Fig. 6A In the example of , when the PUSCH repetition does not overlap with the HARQ feedback scheduled by the downlink grant, the UE 604 ignores the bit indicator 621 of the uplink grant 620 and multiplexes 0 bits on the PUSCH repetition. For example, the UE 604 may multiplex 0 bits on the second repetition 624 at time T3.

[0117] In an example where PUSCH repetitions overlap with HARQ feedback scheduled by a downlink grant, the UE 604 may multiplex z bits on the PUSCH repetitions. The value of the z bits may be determined based on a relationship between the bit indicator 621 (e.g., x bits) of the uplink grant 620 and the downlink bit indicator (e.g., y bits payload size for each HARQ feedback) of each downlink grant associated with the corresponding HARQ feedback.

[0118] For example, UE 604 may use Equation 1 (below) to determine the z bits.

[0119] Formula 1: z = 4T + x bits, where T = 0, 1, 2, ...

[0120] In Formula 1, term z represents the amount of bits to be multiplexed on PUSCH repetitions, term x represents the value of bit indicator 621, and term T represents the modification amount. The value of modification amount T may be determined as the smallest integer that satisfies Formula 2 (below).

[0121] Formula 2: ceil(4T+x≥y), where T=0,1,2,…

[0122] In Equation 2, the term x represents the value of the bit indicator 621, the term y represents the payload size of the HARQ feedback, and the term T represents the modification amount. The UE 604 may determine the value of the modification amount T as the smallest integer that satisfies Equation 2. In an example where the value of the bit indicator 621 (e.g., x bits) is greater than or equal to the value of the downlink bit indicator of the HARQ feedback (e.g., y bits) (e.g., x bits ≥ y bits), the value of the modification amount T is zero, then Equation 1 can be simplified, and the UE 604 may use Equation 3 (below) to determine the value of z bits.

[0123] Equation 3: z = x bits

[0124] That is, when the value of the bit indicator 621 (e.g., x bits) is greater than or equal to the value of the downlink bit indicator of the HARQ feedback (e.g., y bits) (e.g., x bits ≥ y bits), the UE 604 uses the x bits indicated by the bit indicator 621 to multiplex on the PUSCH repetition. For example, regarding the first repetition 622 and the first HARQ feedback 610, the 2 bits indicated by the bit indicator 621 are greater than the 1-bit payload size of the first HARQ feedback 610, and thus, the UE 604 multiplexes two bits on the first repetition 622 at time T2. In a similar manner, and regarding the third repetition 626 and the second HARQ feedback 612, the 2 bits indicated by the bit indicator 621 are equal to the 2-bit payload size of the second HARQ feedback 612, and thus, the UE 604 multiplexes two bits on the second repetition 624 at time T4. It can be understood that when the value of the bit indicator 621 is greater than the value of the downlink bit indicator of the HARQ feedback, the UE 604 may use one or more dummy bits during multiplexing, such as adding a dummy bit when multiplexing on the first repetition 622 at time T2. Examples of dummy bits include NACK indicators.

[0125] In an example where the value of the bit indicator 621 is less than the value of the downlink bit indicator of the HARQ feedback (e.g., x bits < y bits), then the UE 604 uses Equation 2 (above) to determine the value of the term T, and then uses Equation 1 (above) to determine the value of z bits. For example, and regarding the fourth repetition 628 at time T5 (e.g., x is 2 bits) and the third HARQ feedback 614 (e.g., y payload size is 3 bits), the value of the modification amount T is one.

[0126] Equation 2:

[0127] ceil(4T+(2)≥(3))

[0128] ceil(4T≥1)

[0129]

[0130] T=1

[0131] Using the value of the modifier T as one, the UE 604 may determine the value of the z bits using Formula 1. For example, using Formula 1, the UE 604 may determine that the value of the z bits is 6 bits.

[0132] Formula 1:

[0133] z=4(1)+(2)

[0134] z=6

[0135] That is, with respect to the transmission at time T5, the UE 604 may multiplex six bits on the fourth repetition 628. Similar to the example of the transmission at time T2, when the z bits are larger than the payload size of the corresponding HARQ feedback, the UE 604 may add dummy bits. For example, the UE 604 may add three dummy bits (e.g., three NACK indicators) to the three bits of the third HARQ feedback 614 to satisfy the multiplexing of six bits on the fourth repetition 628.

[0136] Therefore, if Fig. 6A As shown, UE 604 may multiplex {2, 0, 2, 6} bits for repetitions of uplink messages at times T2, T3, T4, and T5, respectively. Additionally, network entity 602 may expect repetitions of uplink messages to be multiplexed with expected multiplexing bits {2, 0, 2, 6} bits. Network entity 602 may use the expected multiplexing bits to demultiplex the corresponding repetitions, such as in conjunction with Figure 5 as described in the examples.

[0137] Figure 6B 6 is a diagram illustrating a timeline 650 of a UE 604 performing multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a network entity 602 as presented herein. Fig. 6A , the network entity 602 may send scheduling information for multiple downlink messages and for an uplink message to the UE 604. For example, the network entity 602 may send an uplink grant 660 that is received by the UE 604 at time T3. Based on the uplink grant 660, the UE 604 may schedule four repetitions of the uplink message. For example, the UE 604 may schedule a first repetition 662 ("PUSCH repetition 1") at time T4, a second repetition 664 ("PUSCH repetition 2") at time T5, a third repetition 666 ("PUSCH repetition 3") at time T6, and a fourth repetition 668 ("PUSCH repetition 4") at time T7.

[0138] exist Figure 6BIn the example of FIG. 6 , the network entity 602 sends a first downlink grant 670 and a third downlink grant 674 at time T1. The first downlink grant 670 schedules a first HARQ feedback 672 at time T4, and the third downlink grant 674 schedules a third HARQ feedback 676 at time T7. The network entity 602 also sends a second downlink grant 680 at time T2. The second downlink grant 680 schedules a second HARQ feedback 682 at time T7. Although Figure 6B The example illustrates that the first downlink grant 670 and the third downlink grant 674 are sent at the same time (eg, at time T1), but in other examples, the first downlink grant 670 and the third downlink grant 674 may be sent by the network entity 602 at different times.

[0139] exist Figure 6B In the example of , UE 604 receives a second downlink grant 680 at time T2 and is therefore scheduled to send a second HARQ feedback 682 at time T6. Figure 6B In the example of , the UE 604 does not receive the first downlink grant 670 and the third downlink grant 674 at time T1 and is therefore not scheduled to send the first HARQ feedback 672 at time T4 and the third HARQ feedback 676 at time T7, respectively.

[0140] Similar to Fig. 6A In the example of the uplink grant 660, the uplink grant 660 includes a bit indicator 661 indicating 2 bits (eg, TDAI is 2 bits), and Figure 6B The payload size associated with the HARQ feedback is Fig. 6A That is, the payload size of the first HARQ feedback 672 is one bit, the payload size of the second HARQ feedback 682 is two bits, and the payload size of the third HARQ feedback 676 is three bits.

[0141] As described above, when the repetition does not overlap in time with the HARQ feedback scheduled by the downlink grant, the UE sends the repetition without multiplexing or by multiplexing zero bits. For example, with respect to time T5, the UE 604 may determine that there is no overlap between the second repetition 664 and the HARQ feedback, and thus may send the second repetition 664 without multiplexing or by multiplexing zero bits. Additionally, the network entity 602 expects no multiplexing with the second repetition 664 at time T5, and thus expects zero multiplexed bits at time T5.

[0142] Similar to Fig. 6A For example, Figure 6BThe UE 604 may determine to multiplex two bits for the transmission at time T6 based on the second HARQ feedback 682 overlapping in time with the third repetition 666. Additionally, the network entity 602 expects the transmission at time T6 to be multiplexed with two bits.

[0143] like Figure 6B As shown, UE 604 does not receive the first downlink grant 670 and the third downlink grant 674. For example, due to poor channel conditions or the downlink channel associated with the downlink grant is an unreliable channel, UE 604 may not receive the downlink grant. In such a scenario, UE 604 is also not scheduled with the HARQ opportunities associated with the first HARQ feedback 672 and the third HARQ feedback 676. For example, since UE 604 did not receive the first downlink grant 670, UE 604 did not receive the PDSCH resources associated with the corresponding downlink message, and did not receive the HARQ resources associated with the first HARQ feedback 672.

[0144] Therefore, UE 604 determines that the first repetition 662 and the fourth repetition 668 do not overlap in time with the HARQ feedback scheduled by the downlink grant. Therefore, UE 604 can send the first repetition 662 at time T4 and send the fourth repetition 668 at time T7 without multiplexing or by multiplexing zero bits.

[0145] However, compared to the example of the second repetition 664 at time T5, the network entity 602 expects a temporal overlap between the first repetition 662 and the first HARQ feedback 672 at time T4 and a temporal overlap between the fourth repetition 668 and the third HARQ feedback 676 at time T7. Thus, the network entity 602 expects the transmission at time T4 to be multiplexed with two bits and the transmission at time T7 to be multiplexed with six bits, as respectively combined with Fig. 6A The sending at time T2 and the sending at time T5 are described.

[0146] like Fig. 6A and Figure 6B As shown in the example of , UE 604 can determine whether to perform multiplexing on repetitions or skip multiplexing based on the downlink grant successfully received for scheduling HARQ feedback. Figure 6B In the example of , UE 604 missed the first downlink grant 670 and the third downlink grant 674, and therefore determined not to perform multiplexing on the repetitions at time T4 and time T7. However, network entity 602 may not know that UE 604 missed the corresponding downlink grants and expects to multiplex the corresponding repetitions. Figure 6BIn the example of , UE 604 may multiplex {0,0,2,0} bits for repetition of uplink message at time T4, T5, T6 and T7, respectively. Additionally, network entity 602 may expect repetition of uplink message to be multiplexed with expected multiplexing bits {2,0,2,6} bits. When the multiplexing bits and expected multiplexing bits are different, such as Figure 6B As shown, the network entity 602 may be unable to decode repetitions and HARQ feedback for misaligned transmissions.

[0147] Additionally, in examples where UE 604 determines to perform multiplexing over repetitions, UE 604 may receive a common bit indicator in the uplink grant that is applicable to each repetition. Fig. 6A In the example of , UE 604 uses the value of bit indicator 621 to determine how many bits to multiplex on the first repetition 622 at time T2, on the third repetition 626 at time T4, and on the fourth repetition 628 at time T5. However, in some such examples, when determining the z bits to multiplex, UE 604 may determine to add one or more dummy bits for multiplexing. For example, with respect to Fig. 6A For the transmission at time T5, UE 604 determines to multiplex six bits, but the payload size of the third HARQ feedback 614 is three bits, and therefore UE 604 adds three dummy bits.

[0148] Various aspects disclosed herein provide techniques for improving multiplexing of HARQ feedback with repetitions on PUSCH. The disclosed techniques may provide higher data rates, increased capacity, and / or increased spectral efficiency. For example, various aspects disclosed herein may configure a UE to determine to perform multiplexing on a repetition regardless of whether the repetition overlaps in time with the HARQ feedback. Additionally, the UE may perform multiplexing based on an amount of bits indicated by an uplink grant. By determining to perform multiplexing based on an amount of bits indicated by an uplink grant (e.g., a bit indicator) and regardless of whether there is an overlap in time, the UE may resolve issues associated with missed downlink grants, such as in conjunction with Figure 6B As described in the example of . In some examples, the bit indicator may include a bit indicator set, which includes multiple bit indicators. For example, the amount of bit indicators in the bit indicator set may correspond to the amount of repetitions configured for the uplink message. The amount of repetitions may be indicated via an uplink grant and / or via RRC signaling. In some such examples, the UE may use the corresponding bit indicators in the bit indicator set to determine the amount of z bits to be multiplexed on the corresponding repetition. In other examples, the bit indicator set may include a one-bit indicator applied to each repetition of the uplink message.

[0149] On the other hand, the UE may be configured to determine whether to perform multiplexing on repetitions based on a bit indicator included in the uplink grant. For example, when the value of the bit indicator satisfies a threshold value (e.g., the x bits indicated by the bit indicator are greater than or equal to the threshold value), the UE may perform multiplexing on repetitions, regardless of whether the repetitions overlap in time with the HARQ feedback scheduled by the downlink grant. In an example where the value of the bit indicator does not satisfy the threshold value (e.g., the x bits are less than the threshold value), the UE may multiplex the x bits of the HARQ feedback on the repetitions when the repetitions overlap in time with the HARQ feedback. The UE may also skip multiplexing or multiplex zero bits on the repetitions when the repetitions do not overlap in time with the HARQ feedback.

[0150] Figure 7 7 is a diagram illustrating a timeline 700 of a UE 704 performing multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a network entity 702 as presented herein. One or more aspects described with respect to the network entity 702 may be performed by a base station or a component of the network entity (e.g., a CU, DU, and / or RU). Various aspects of the network entity 702 may be performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 704 may be implemented by base station 310. Figure 1 UE 104 and / or Figure 3 This is achieved with the UE350.

[0151] Despite Figure 7 Not shown in the example of , the network entity 702 may send a downlink grant that is received by the UE 704. The network entity 702 may send a downlink grant on the PDCCH. The downlink grant may schedule a corresponding HARQ opportunity for sending HARQ feedback. For example, the UE 704 may be configured to send a first HARQ feedback 730 with a payload size of one bit at time T2 ("DL grant 1 ACK / NACK"), may be configured to send a second HARQ feedback 732 with a payload size of two bits at time T3 ("DL grant 2 ACK / NACK"), and may be configured to send a third HARQ feedback 734 with a payload size of three bits at time T5 ("DL grant 3 ACK / NACK").

[0152] exist Figure 7 In the example of , network entity 702 sends an uplink grant 710 that is received by UE 704 at time T1. Uplink grant 710 may include a single uplink transmission grant with repetitions. For example, uplink grant 710 may schedule k repetitions of an uplink message. Figure 7In the example of , the uplink grant 710 includes a repetition indicator 712 indicating that four repetitions of the uplink message are to be sent. The uplink grant 710 also includes PUSCH resources 714 indicating time resources and / or frequency resources associated with each of the repetitions of sending the uplink message. For example, the PUSCH resources 714 may allocate resources for sending a first repetition 720 ("PUSCH repetition 1") at time T2, resources for sending a second repetition 722 ("PUSCH repetition 2") at time T3, resources for sending a third repetition 724 ("PUSCH repetition 3") at time T4, and resources for sending a fourth repetition 726 ("PUSCH repetition 4") at time T5.

[0153] The uplink grant 710 also includes a bit indicator such as Figure 4 The bit indicator 446. Figure 7 In the example of , the bit indicator includes a bit indicator set 716, which includes a plurality of bit indicators. Figure 7 The bit indicator set 716 includes the same number of bit indicators (e.g., 4 bit indicators) as the k repetitions indicated by the repetition indicator 712. Each of the different bit indicators in the bit indicator set 716 can be associated with a respective repetition. For example, Figure 7 The bit indicator set 716 includes a set of four bit indicators {2, 0, 3, 3}, and wherein the first bit indicator "2" is associated with the first repetition 720, the second bit indicator "0" is associated with the second repetition 722, the third bit indicator "3" is associated with the third repetition 724, and the fourth bit indicator "3" is associated with the fourth repetition 726. Aspects of the bit indicators can be implemented by UL-TDAI parameters. In some examples, the UL-TDAI parameters may include N fields corresponding to the number of bit indicators included in the bit indicator set 716.

[0154] exist Figure 7In the example of , UE 704 is configured to multiplex the bit indicators in bit indicator set 716 with the corresponding repetitions of the uplink message. UE 704 multiplexes the amount of bits indicated by the bit indicators, regardless of whether the corresponding repetition overlaps with the HARQ feedback in time. For example, based on the first bit indicator in bit indicator set 716, UE 704 multiplexes 2 bits of the first HARQ feedback 730 on the first repetition 720. That is, UE 704 may send a first transmission 740 including two bits of the first HARQ feedback 730 multiplexed on the first repetition 720 at time T2. In a similar manner, UE 704 may send a second transmission 742 including zero bits multiplexed with the second repetition 722 at time T3 based on the second bit indicator “0” in the bit indicator set 716, may send a third transmission 744 including three bits of the second HARQ feedback 732 multiplexed with the third repetition 724 at time T4 based on the third bit indicator “3” in the bit indicator set 716, and may send a fourth transmission 746 including three bits of the third HARQ feedback 734 multiplexed with the fourth repetition 726 at time T5 based on the fourth bit indicator “3” in the bit indicator set 716.

[0155] like Figure 7 As shown, by receiving a bit indicator set 716 having a bit indicator corresponding to the number of k repetitions of an uplink message, the UE 704 can skip determining whether to perform HARQ feedback multiplexing on a PUSCH repetition based on a downlink grant that may or may not have been missed. Figure 7 As shown, UE 704 may multiplex {2, 0, 3, 3} bits for repetitions of uplink messages at times T2, T3, T4, and T5, respectively. Additionally, network entity 702 may expect repetitions of uplink messages to be multiplexed with the expected multiplexing {2, 0, 3, 3} bits. Network entity 702 may use the corresponding expected multiplexing bits to demultiplex the corresponding transmissions and recover the corresponding repetitions and the corresponding HARQ feedback (if any), as combined with Figure 5 as described in the examples.

[0156] exist Figure 7 , the UE 704 may use the value of the bit indicator to determine the number of bits to be multiplexed for the corresponding repetition. However, in the example where the downlink grant indicates the payload size of the corresponding HARQ feedback, the UE 704 may use Formula 1 (above) and Formula 2 (above) to determine the z bits to be multiplexed. For example, if the fourth bit indicator in the bit indicator set 716 is "2" bits, then the fourth transmission 746 will include six bits of the third HARQ feedback 734 multiplexed with the fourth repetition 726 based on the fourth bit indicator "2" in the bit indicator set 716, as combined Fig. 6AIn such an example, UE 704 may include one or more dummy bits to satisfy the multiplexing of z bits.

[0157] It is appreciated that since the network entity 702 may provide scheduling information for downlink grants and uplink grants, the network entity 702 may configure the bit indicators in the bit indicator set 716 such that each respective bit indicator is at least equal to the payload size of the corresponding HARQ feedback.

[0158] Figure 7 The example helps to alleviate issues regarding HARQ feedback multiplexing on PUSCH repetitions when a downlink grant is missed (e.g., which may cause a misalignment between the number of bits multiplexed by the UE and the expected number of multiplexed bits multiplexed at the base station). However, the example bit indicator set 716 includes overhead associated with each bit indicator in the bit indicator set 716. For example, in the case of four repetitions of an uplink message, the uplink grant also provides four bit indicators for use with the corresponding repetitions. That is, the cost of employing the bit indicator set 716 is the increased overhead of the downlink control channel (e.g., DCI on the PDCCH) due to the N bit indicators included in the bit indicator set 716.

[0159] Figure 8 800 is a diagram illustrating a timeline 800 of a UE 804 performing multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a network entity 802 as presented herein. One or more aspects described with respect to the network entity 802 may be performed by a base station or a component of the network entity (e.g., a CU, a DU, and / or a RU). Various aspects of the network entity 802 may be performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 804 may be implemented by base station 310. Figure 1 UE 104 and / or Figure 3 UE350 is implemented. Figure 8 804, but the network entity 802 may send a downlink grant that may be received by the UE 804 or that the UE 804 may miss, such as in conjunction with Figure 6B The network entity 802 may send a downlink grant on the PDCCH. The downlink grant may schedule a corresponding HARQ opportunity for sending HARQ feedback.

[0160] Similar to Figure 6BIn the example of , UE 804 may miss receiving the first downlink grant, may receive the second downlink grant, and may miss receiving the third downlink grant. Based on the three downlink grants sent by the network entity 802, the network entity 802 may expect to receive the first HARQ feedback 830 with a payload size of one bit ("DL grant 1 ACK / NACK") at time T2, may expect to receive the second HARQ feedback 832 with a payload size of two bits at time T3 ("DL grant 2 ACK / NACK"), and may expect to receive the third HARQ feedback 834 with a payload size of three bits at time T5 ("DL grant 3 ACK / NACK"). However, based on the downlink grant received by UE 804 (e.g., the second downlink grant), UE 804 may determine the HARQ timing for sending the second HARQ feedback 832 at time T4.

[0161] exist Figure 8 In the example of , network entity 802 sends an uplink grant 810 that is received by UE 804 at time T1. Uplink grant 810 may include a single uplink transmission grant with repetitions. For example, uplink grant 810 may schedule k repetitions of an uplink message. Figure 8 In the example of , the uplink grant 810 includes a repetition indicator 812 indicating the amount of four repetitions associated with the uplink message. The uplink grant 810 also includes PUSCH resources 814 indicating the time resources and / or frequency resources associated with each of the repetitions of sending the uplink message. For example, the PUSCH resources 814 may allocate resources for sending a first repetition 820 ("PUSCH repetition 1") at time T2, resources for sending a second repetition 822 ("PUSCH repetition 2") at time T3, resources for sending a third repetition 824 ("PUSCH repetition 3") at time T4, and resources for sending a fourth repetition 826 ("PUSCH repetition 4") at time T5.

[0162] although Figure 8 An example of includes a repeat indicator 812 with the uplink grant 810, but in other examples, the UE 804 may communicate via RRC signaling (such as Figure 4 436) to receive the repeat indicator 812.

[0163] The uplink grant 710 also includes a bit indicator 816. Figure 8 In the example of , bit indicator 816 is a common bit indicator indicating the amount of x bits to be multiplexed over the repetitions. Figure 8In the example of , the bit indicator 816 indicates that three bits are multiplexed on the repetition. Aspects of the bit indicator may be implemented by UL-TDAI parameters or common UL-TDAI parameters.

[0164] exist Figure 8 In the example of , UE 804 is configured to multiplex x bits on repetitions, regardless of whether the repetitions overlap in time with HARQ feedback. It can be appreciated that by multiplexing x bits regardless of whether the repetitions overlap in time with HARQ feedback, the example technique solves the problem associated with missed downlink grants.

[0165] For example, based on the three bits indicated by the bit indicator 816, the UE 804 multiplexes three bits on the first repetition 820. That is, the UE 804 may send a first transmission 840 including the three multiplexed bits on the first repetition 820 at time T2. In a similar manner, the UE 804 may send a second transmission 842 including three bits multiplexed with the second repetition 822 at time T3, may send a third transmission 844 including three bits of the second HARQ feedback 832 multiplexed with the third repetition 824 at time T4, and may send a fourth transmission 846 including three bits multiplexed with the fourth repetition 826 at time T5. In an example where the x bits indicated by the bit indicator 816 are larger than the payload size of the HARQ feedback, the UE 804 may add one or more dummy bits (such as one or more NACK indicators) so that each transmission includes x bits multiplexed on the corresponding repetition. In an example in which a downlink grant is missed and therefore UE 804 is not scheduled with a corresponding HARQ opportunity (e.g., a missed HARQ opportunity associated with the first HARQ feedback 830 is not scheduled at time T2, and a missed HARQ opportunity associated with the third HARQ feedback 834 is not scheduled at time T5), or when the repetition and the HARQ feedback do not overlap in time (e.g., at time T3), the x bits that UE 804 multiplexes with each corresponding repetition may be one or more dummy bits (e.g., one or more NACK indicators).

[0166] Therefore, if Figure 8 As shown, UE 804 may multiplex {3,3,3,3} bits for repetitions of uplink messages at times T2, T3, T4, and T5, respectively. Additionally, network entity 802 may expect repetitions of uplink messages to be multiplexed with the expected multiplexing {3,3,3,3} bits. As described above, network entity 802 may use the corresponding expected multiplexing bits to demultiplex the corresponding transmissions and recover the corresponding repetitions and the corresponding HARQ feedback (if any), as described in conjunction with Figure 5 as described in the examples.

[0167] exist Figure 8, UE 804 uses the value of bit indicator 816 to determine the number of bits to be multiplexed for repetition. However, in the example where the downlink grant indicates the payload size of the corresponding HARQ feedback, UE 804 can use Formula 1 (above) and Formula 2 (above) to determine the z bits to be multiplexed. For example, if Figure 8 The bit indicator of the uplink grant 810 is "2" bits, then the UE 804 may multiplex the six bits of the third HARQ feedback 834 with the fourth repetition 826 when sending the fourth transmission 846, such as in combination with Fig. 6A In such an example, UE 804 may include one or more dummy bits to satisfy the multiplexing of z bits.

[0168] Figure 8 The example improves HARQ feedback multiplexing on PUSCH repetitions when a downlink grant is missed (e.g., which may cause a misalignment between the number of bits multiplexed by the UE and the expected number of multiplexed bits multiplexed at the base station). Additionally, the bit indicator 816 is common (e.g., shared) for each repetition, which reduces the overhead associated with adding multiple bit indicators to the bit indicator set, such as in conjunction with Figure 7 as described in the examples.

[0169] Fig. 9 An example communication flow 900 between a network entity 902 and a UE 904 as presented herein is illustrated. One or more aspects described with respect to the network entity 902 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. Various aspects of the network entity 902 may be performed by Figure 1 Base station 102 and / or Figure 3 Various aspects of UE 904 may be implemented by Figure 1 UE 104 and / or Figure 3 UE 350. Fig. 9 Not shown in the illustrated example, but in additional or alternative examples, the network entity 902 and / or the UE 904 may communicate with one or more other base stations or UEs.

[0170] In the illustrated example, the communication flow 900 facilitates the UE 904 to perform HARQ feedback multiplexing with repetitions on the PUSCH. For example, the UE 904 may be configured to determine whether to perform multiplexing on repetitions based on the bit indicator included in the uplink grant. In some examples, when the value of the bit indicator meets the threshold value (e.g., x bits are greater than or equal to the threshold value), the UE 904 may perform multiplexing on repetitions regardless of whether the repetitions overlap with the HARQ feedback in time. In an example where the value of the bit indicator does not meet the threshold value (e.g., x bits are less than the threshold value), when the repetition overlaps with the HARQ feedback in time, the UE may multiplex x bits on the repetition. When the repetition does not overlap with the HARQ feedback in time, the UE may also skip multiplexing or multiplex zero bits on the repetition.

[0171] like Fig. 9 As shown, the network entity 902 may send a downlink grant 910 that is received by the UE 904. The network entity 902 may send the downlink grant 910 in a DCI on the PDCCH. Aspects of the downlink grant 910 may be similar to Figure 4 For example, the downlink grant 910 may include information related to the downlink message 920 and the HARQ feedback 932 associated with the downlink message 920, such as PDSCH resources 912 allocated for monitoring opportunities associated with one or more transmissions of the downlink message 920, HARQ resources 914 allocated to the UE 904 for sending the HARQ feedback 932, and a downlink bit indicator 916 indicating the amount of ACK / NACK bits used for the HARQ feedback. In some aspects, the downlink bit indicator 916 may include a TDAI that may be used to facilitate determining the amount of bits used for the HARQ feedback 932.

[0172] The network entity 902 may send a downlink message 920 that is received by the UE 904. The network entity 902 may send the downlink message 920 on the PDSCH. Aspects of the downlink message 920 may be similar to Figure 4 The UE 904 may receive the downlink message 920 based on the PDSCH resources 912 indicated by the downlink grant 910. For example, the PDSCH resources 912 may indicate a first monitoring opportunity 922, and the UE 904 may monitor the resources associated with the first monitoring opportunity 922 to receive the downlink message 920. The first monitoring opportunity 922 may be associated with a time resource and / or a frequency resource.

[0173] The UE 904 may perform a generation process 930 to generate HARQ feedback 932 based on the downlink message 920. For example, the UE 904 may generate UCI with ACK or NACK based on whether the UE 904 decodes the downlink message 920 at the first monitoring occasion 922. Aspects of the HARQ feedback 932 may be similar to Figure 4 HARQ feedback 432.

[0174] like Fig. 9 As shown, the UE 904 may send HARQ feedback 932 associated with the downlink message 920. The UE 904 may use resources allocated by the downlink grant 910 for the HARQ feedback 932. For example, the HARQ resources 914 may indicate time resources and / or frequency resources associated with the HARQ opportunity 934. The UE 904 may send the HARQ feedback 932 based on the HARQ opportunity 934. Additionally, the payload size of the HARQ feedback 932 may be based on the downlink bit indicator 916 of the downlink grant 910. The UE 904 may send the HARQ feedback 932 using UCI on the PUCCH.

[0175] like Fig. 9 As shown, UE 904 may also be configured to send an uplink message received by network entity 902. For example, network entity 902 may send an uplink grant 940 received by UE 904. Network entity 902 may send uplink grant 940 on PDCCH. Aspects of uplink grant 940 may be similar to Figure 4 940. For example, the uplink grant 940 may include information related to the uplink message, such as PUSCH resources 942 allocated to the UE 904 for transmission of the uplink message, a repetition indicator 944 indicating the amount of repetitions of the uplink message, and a bit indicator 946 indicating the amount of bits to be multiplexed with the repetitions of the uplink message (e.g., x bits). In some aspects, the bit indicator 946 may correspond to a TDAI that can be used to facilitate determining the amount of bits of the HARQ feedback 932 to be multiplexed. As described above, the UE 904 may send up to k repetitions of the uplink message until a termination event occurs.

[0176] although Fig. 9 An example includes a repeat indicator 944 with an uplink grant 940, but in other examples, the UE 904 may communicate via RRC signaling (such as Figure 4 Example RRC signaling 436) to receive a repeat indicator 944.

[0177] In one aspect, UE 904 may improve HARQ feedback multiplexing with repetitions on PUSCH based on the value of bit indicator 946 of uplink grant 940. For example, UE 904 may determine whether the x bits indicated by bit indicator 946 are greater than a threshold amount of bits. In some examples, the threshold amount of bits may be two bits. For example, when x bits are less than or equal to two bits, UE 904 may multiplex x bits on repetitions by puncturing x bits of repetitions. Network entity 902 may have the ability to decode a transmission including zero bits, one bit, or two bits of punctured repetitions. However, when x bits are greater than a threshold value (e.g., greater than two bits), UE 904 multiplexes x bits by rate matching the repetitions. When (e.g., at UE 904) the amount of multiplexed bits is different from (e.g., at network entity 902) the amount of expected multiplexed bits, network entity 902 may have difficulty in attempting to decode a transmission including rate matching.

[0178] exist Fig. 9 In the example of , the UE 904 may perform a determination process 950 to determine whether the x bits indicated by the bit indicator 946 are greater than a threshold amount of bits (e.g., are the x bits>2 bits?). If the UE 904 determines that the x bits are greater than the threshold amount, the UE 904 performs a multiplexing process 952 to multiplex the z bits on the repeat. The UE 904 may use Formula 1, Formula 2, and / or Formula 3 (reproduced below) to determine the value of the z bits.

[0179] Formula 1: z = 4T + x bits, where T = 0, 1, 2, ...

[0180] Formula 2: ceil(4T+x≥y), where T=0,1,2,…

[0181] Formula 3: z = x digits

[0182] like Fig. 9 As shown, UE 904 may send a first transmission 954 that is received by network entity 902. UE 904 may send the first transmission 954 on a PUSCH. The first transmission 954 may include multiplexing of z bits on repetitions. UE 904 may multiplex the z bits regardless of whether the repetitions overlap in time with the HARQ feedback. By multiplexing the z bits regardless of the overlapping state of the repetitions, the multiplexing does not depend on whether the HARQ feedback scheduled by the downlink grant overlaps. Thus, in a scenario where UE 904 misses a downlink grant, for example, as combined with Figure 6B Timeline 650 and / or Figure 8 As described in timeline 800, the amount of multiplexing bits (e.g., at UE 904) is aligned with the expected amount of multiplexing bits (e.g., at network entity 902), and therefore, network entity 902 can decode the first transmission 954 to receive repetitions and HARQ feedback (if any).

[0183] If the UE 904 determines via the determination process 950 that x bits do not satisfy a threshold (e.g., x bits are less than or equal to a threshold amount of bits), the UE 904 may perform bit multiplexing on the repetitions based on whether the repetitions overlap in time with the HARQ feedback. For example, the UE 904 may perform a determination process 960 to determine whether the UCI carrying the HARQ feedback 932 overlaps in time with the repetitions of the uplink message. For example, the UE 904 may determine that the repetitions of the uplink message do not overlap with the HARQ opportunity 934. In such an example, the UE 904 may send a second transmission 962 that is received by the network entity 902. The UE 904 may send the second transmission 962 while skipping multiplexing on the repetitions or by multiplexing zero bits on the repetitions. The UE 904 may send the second transmission 962 on the PUSCH.

[0184] In an example where repetition overlaps with HARQ feedback, the UE 904 may multiplex the HARQ feedback and the repetition. For example, the UE 904 may determine, via the determination process 960, that the repetition overlaps with the HARQ opportunity 934 in time. In such an example, the UE 904 may perform a multiplexing process 964 to multiplex the x bits of the HARQ feedback 932 with the repetition. As described above in conjunction with the determination process 950, the value of the x bits is less than or equal to a threshold amount of bits (e.g., 2 bits). Therefore, the UE 904 may truncate the x bits of the repetition via the multiplexing process 964.

[0185] like Fig. 9 As shown, the UE 904 may transmit a third transmission 966 that is received by the network entity 902. The UE 904 may transmit the third transmission 966 on the PUSCH. The third transmission 966 may include x bits of the HARQ feedback 932 multiplexed over repetitions.

[0186] Fig.10 1 is a diagram of a timeline 1000 illustrating that a UE 1004 performs multiplexing with repeated HARQ feedback on a PUSCH based on scheduling information from a network entity 1002 as presented herein. One or more aspects described with respect to the network entity 1002 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. Various aspects of the network entity 1002 may be performed by Figure 1 Base station 102, Figure 3 Base station 310 and / or Fig. 9 1004. Figure 1 UE 104, Figure 3 UE 350 and / or Fig. 9 The UE 904 is used to implement the above.

[0187] Despite Fig.10 1004, but the network entity 1002 may send a downlink grant that may be received by the UE 1004 or may be missed by the UE 1004, such as in conjunction with Figure 6B and Figure 8 The network entity 1002 may send a downlink grant on the PDCCH. The downlink grant may schedule a corresponding HARQ opportunity for sending HARQ feedback.

[0188] Similar to Figure 8 In the example of , UE 1004 may miss receiving the first downlink grant, may receive the second downlink grant, and may miss receiving the third downlink grant. Based on the three downlink grants sent by network entity 1002, network entity 1002 may expect to receive a first HARQ feedback 1030 with a payload size of one bit ("DL grant 1 ACK / NACK") at time T2, may expect to receive a second HARQ feedback 1032 with a payload size of two bits at time T4 ("DL grant 2 ACK / NACK"), and may expect to receive a third HARQ feedback 1034 with a payload size of three bits at time T5 ("DL grant 3 ACK / NACK"). However, based on the downlink grant (e.g., the second downlink grant) received by UE 1004, UE 1004 may determine a HARQ timing for sending the second HARQ feedback 1032 at time T4.

[0189] exist Fig.10 In the example of , network entity 1002 sends an uplink grant 1010 that is received by UE 1004 at time T1. Uplink grant 1010 may include a single uplink transmission grant with repetitions. For example, uplink grant 1010 may schedule k repetitions of an uplink message. Fig.10 In the example of , the uplink grant 1010 includes a repetition indicator 1012 indicating that four repetitions of the uplink message are to be sent. The uplink grant 1010 also includes PUSCH resources 1014 indicating time resources and / or frequency resources associated with each of the repetitions of sending the uplink message. For example, the PUSCH resources 1014 may allocate resources for sending a first repetition 1020 ("PUSCH repetition 1") at time T2, resources for sending a second repetition 1022 ("PUSCH repetition 2") at time T3, resources for sending a third repetition 1024 ("PUSCH repetition 3") at time T4, and resources for sending a fourth repetition 1026 ("PUSCH repetition 4") at time T5.

[0190] although Fig.10An example includes a repeat indicator 1012 with the uplink grant 1010, but in other examples, the UE 1004 may provide a repeat indicator 1012 via RRC signaling (such as Figure 4 Example RRC signaling 436) to receive the repeat indicator 1012.

[0191] The uplink grant 1010 also includes a bit indicator 1016. Fig.10 In the example of , bit indicator 1016 is a common bit indicator indicating the amount of x bits to be multiplexed over repetitions. Fig.10 In the example of , the bit indicator 1016 indicates that 2 bits are multiplexed on the repetition. Aspects of the bit indicator may be implemented by UL-TDAI parameters or common UL-TDAI parameters.

[0192] exist Fig.10 In the example of , UE 1004 is configured to determine whether to perform multiplexing on repetition in two steps, such as combining Fig. 9 For example, UE 1004 may first determine whether the amount of x bits meets the threshold amount of bits, such as in combination with Fig. 9 For example, the UE 1004 may determine whether the 2 bits indicated by the bit indicator 1016 are greater than a threshold amount of bits. Fig.10 In the example of , the threshold amount of bits is two bits, which is the same amount of bits that the UE 1004 uses to determine whether to perform multiplexing on the repetitions by puncturing the repetitions or by rate matching.

[0193] exist Fig.10 In the example of , UE 1004 may determine that x bits do not satisfy the threshold amount of bits (e.g., 2 bits indicated by bit indicator 1016 are not greater than the threshold amount of bits (2 bits)). In such a scenario, UE 1004 may then determine whether to multiplex x bits on the repetition based on whether the repetition overlaps with the HARQ feedback, such as in combination with Fig. 9 For example, regarding the first repetition 1020 at time T2, the second repetition 1022 at time T3, and the fourth repetition 1026 at time T5, the UE 1004 may determine that there is no overlap with the HARQ feedback. Therefore, the UE 1004 may determine to send the first transmission 1040 at time T2, the second transmission 1042 at time T3, and the fourth transmission 1046 at time T5 based on skipping multiplexing or multiplexing zero bits on the corresponding repetitions, as combined with Fig. 9 The second transmission 962 is described.

[0194] exist Fig.10In the example of , UE 1004 may determine that the third repetition 1024 at time T4 overlaps in time with the second HARQ feedback 1032. In such a scenario, UE 1004 may multiplex x bits on the third repetition 1024. For example, UE 1004 may send a third transmission 1044 at time T4 including two bits multiplexed on the third repetition 1024, as combined with Fig. 9 As described above, when the value of the x bits is less than or equal to two bits, the UE 1004 multiplexes the x bits by puncturing repetitions. For example, the UE 1004 may puncture two bits of the third repetition 1024.

[0195] Therefore, if Fig.10 As shown, UE 1004 may multiplex {0,0,2,0} bits for the repetition of uplink messages at time T2, T3, T4 and T5, respectively. Additionally, network entity 1002 may expect the repetition of uplink messages to be multiplexed with {2,0,2,2} bits of expected multiplexing. Although the amount of multiplexed bits (e.g., at UE 1004) and the amount of expected multiplexed bits (e.g., at network entity 1002) are not aligned, the impact of the asynchronization between UE 1004 and network entity 1002 is small, because network entity 1002 expects the first transmission 1040 at time T2 and the fourth transmission 1046 at time T5 to include the first repetition 1020 and the fourth repetition 1026, respectively, to include two punctured bits. However, as described above, the transmission including punctured zero bits, one bit or two bits has almost no negative impact on the ability of network entity 1002 to decode the transmission. Thus, a misalignment of the amount of multiplexed bits (eg, at UE 1004) and the expected amount of multiplexed bits (eg, at network entity 1002) may be acceptable and still provide improvements when performing multiplexing with repeated HARQ feedback on PUSCH.

[0196] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.13 The method may facilitate higher data rates, improved capacity and / or improved spectrum efficiency by enabling the UE to perform HARQ feedback multiplexing with repetition on the PUSCH based on a bit indicator included in the uplink grant.

[0197] At 1102, the UE receives an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10The uplink grant 1010 of FIG. 1102 may be received by Fig.13 The cellular RF transceiver 1322 / repeating component 198 of the device 1304 is implemented.

[0198] At 1104, the UE transmits a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of the PDSCH scheduled by the downlink grant, the first repetition overlapping with the HARQ-ACK feedback in the time domain, the amount of HARQ-ACK feedback bits based on the bit indicator, as combined with Figure 7 Uplink transmission, Figure 8 Uplink transmission, Fig. 9 Uplink transmission and / or Fig.10 The first repetition of the uplink transmission sent at 1104 may be Fig.13 The cellular RF transceiver 1322 / repeating component 198 of the device 1304 is implemented.

[0199] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Fig.13 The method may facilitate higher data rates, improved capacity and / or improved spectrum efficiency by enabling the UE to perform HARQ feedback multiplexing with repetition on the PUSCH based on a bit indicator included in the uplink grant.

[0200] At 1204, the UE receives an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10 The uplink grant 1010 is described. The uplink grant received at 1204 may be Fig.13 The cellular RF transceiver 1322 / repeating component 198 of the device 1304 is implemented.

[0201] At 1212, the UE transmits a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of the PDSCH scheduled by the downlink grant, the first repetition overlapping with the HARQ-ACK feedback in the time domain, the amount of HARQ-ACK feedback bits based on the bit indicator, as combined with Figure 7 Uplink transmission, Figure 8 Uplink transmission, Fig. 9Uplink transmission and / or Fig.10 The first repetition of the uplink transmission sent at 1212 may be Fig.12 The cellular RF transceiver 1322 / repeating component 198 of the device 1304 is implemented.

[0202] In some examples, at 1212, the downlink grant may include a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of HARQ-ACK feedback bits may be the same amount as the bit indicator, as described in conjunction with Formula 3 (above). In some examples, when the downlink bit indicator is greater than the bit indicator, the amount of HARQ-ACK feedback bits may be based on a relationship between the bit indicator and the downlink bit indicator, as described in conjunction with Formula 1 (above) and Formula 2 (above).

[0203] In some examples, at 1204, the uplink grant may include an indication of the amount of repetitions, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10 In some examples, at 1202, the UE may receive an indication of a repetition amount associated with an uplink message via RRC signaling, such as in conjunction with Figure 4 The indication received at 1202 may be Fig.13 The device 1304 is executed by repeating component 198.

[0204] In some examples, at 1204, the bit indicator may be a first bit indicator in a bit indicator set including a plurality of bit indicators, such as in combination with Figure 7 In some examples, the amount of repetition and the number of bit indicators may be the same amount, such as in combination with Figure 7 The repeat indicator 712 and the bit indicator set 716 are described.

[0205] In an example where the bit indicator is included in a bit indicator set, at 1206, the UE may multiplex each repetition of the uplink transmission with the amount of HARQ-ACK feedback bits associated with a corresponding bit indicator in the bit indicator set, as combined with Figure 7 In some examples, the multiplexing of each repetition may be based on rate matching. The multiplexing of each repetition sent at 1206 for the uplink may be performed by Fig.13 The device 1304 is executed by repeating component 198.

[0206] In some examples, at 1208, the UE may multiplex each repetition of the uplink transmission with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in conjunction with Figure 8 An example of a repeat and bit indicator 816 and / or Fig. 9 In some examples, the second repetition of the uplink transmission may not overlap in the time domain with the second HARQ-ACK feedback scheduled by the second downlink grant, such as in conjunction with Figure 8 The three multiplexing bits on the second transmission 842 and the second repetition 822 are described. In some examples, the multiplexing of each repetition can be based on rate matching. The multiplexing of each repetition at 1208 can be performed by Fig.13 The repeating component 198 of the device 1304 is executed.

[0207] In some examples, at 1210, when the value of the bit indicator is greater than a threshold, the UE may multiplex each repetition of the uplink transmission with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in combination with Fig. 9 The determination process 950, the multiplexing process 952, and the first transmission 954 are described. In some examples, the threshold can be two bits. In some examples, the second repetition of the uplink transmission may not overlap with the second HARQ-ACK feedback scheduled by the second downlink grant in the time domain, such as in combination with Figure 8 The three multiplexing bits on the second transmission 842 and the second repetition 822 are described. In some examples, the multiplexing of each repetition can be based on rate matching. The multiplexing of each repetition at 1210 can be performed by Fig.13 The repeating component 198 of the device 1304 is executed.

[0208] In some examples, at 1214, the UE may receive a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant including a second bit indicator. At 1216, the UE may also send a second uplink transmission repetition, the second uplink transmission repetition and the second HARQ-ACK feedback scheduled by the second downlink grant overlapping in the time domain. In some such examples, at 1218, when the value of the second bit indicator is less than a threshold, the UE may skip multiplexing of the second amount of HARQ-ACK feedback bits for the second HARQ-ACK feedback. In some examples, the threshold may be two bits. The reception of the second uplink grant at 1214, the sending of the second uplink transmission repetition at 1216, and the skipping of the multiplexing at 1218 may be caused by Fig.13 The device 1304 is executed by repeating component 198.

[0209] In some examples, when the second repetition of the uplink transmission overlaps in the time domain with the second HARQ-ACK feedback scheduled by the second downlink grant and the value of the bit indicator is less than or equal to the threshold, the UE may be configured to multiplex the second repetition with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in combination with Fig. 9 The determination process 960, the multiplexing process 964 and the third transmission 966 are described. In some examples, the UE may multiplex the second repetition by puncturing the second repetition based on the amount of HARQ-ACK feedback bits indicated by the bit indicator.

[0210] Fig.131300 is an example of a hardware implementation of an example device 1304. The device 1304 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1304 may include a cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1322). The cellular baseband processor 1324 may include on-chip memory 1325. In some aspects, the device 1304 may also include one or more subscriber identity module (SIM) cards 1320 and an application processor 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1307. In some aspects, the device 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio for positioning, and / or other technologies), an additional memory module 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or communicate using one or more antennas 1380. The cellular baseband processor 1324 communicates with the UE 104 and / or with the RU associated with the network entity 1302 via one or more antennas 1380 through a transceiver (e.g., a cellular RF transceiver 1322). The cellular baseband processor 1324 and the application processor 1306 may each include a computer-readable medium / memory, such as an on-chip memory 1325 and an on-chip memory 1307, respectively. The additional memory module 1326 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., on-chip memory 1325, on-chip memory 1307, and / or additional memory module 1326) may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, enables the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1324 / application processor 1306 when executing software.The cellular baseband processor 1324 / application processor 1306 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1304 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1324 and / or the application processor 1306, while in another configuration, the device 1304 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1304.

[0211] As discussed above, the repetition component 198 is configured to receive an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator. The repetition component 198 may also be configured to send a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits based on the bit indicator.

[0212] The repeating component 198 may be within the cellular baseband processor 1324, the application processor 1306, or both the cellular baseband processor 1324 and the application processor 1306. The repeating component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0213] As shown, the device 1304 may include various components configured for various functions. For example, the repeating component 198 may include executing Fig.11 and / or Fig.12 Each block of the algorithm in the flowchart is one or more hardware components.

[0214] In one configuration, the apparatus 1304, and specifically the cellular baseband processor 1324 and / or the application processor 1306, includes means for receiving an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant including a bit indicator. The example apparatus 1304 also includes means for sending a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits being based on the bit indicator.

[0215] In another configuration, the example apparatus 1304 further includes means for multiplexing each repetition of the uplink transmission with a bit quantity of HARQ-ACK feedback bits associated with a corresponding bit indicator in the set of bit indicators.

[0216] In another configuration, the example apparatus 1304 further includes means for multiplexing each repetition of the uplink transmission with an amount of HARQ-ACK feedback bits indicated by the bit indicator.

[0217] In another configuration, the example apparatus 1304 further includes means for multiplexing each repetition of the uplink transmission with an amount of HARQ-ACK feedback bits indicated by the bit indicator when the value of the bit indicator is greater than a threshold.

[0218] In another configuration, the example apparatus 1304 further includes means for receiving a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant including a second bit indicator. The example apparatus 1304 further includes means for sending the second uplink transmission repetition, the second uplink transmission repetition and the second HARQ-ACK feedback scheduled by the second downlink grant overlapping in the time domain. The example apparatus 1304 further includes means for skipping multiplexing of bits of the second amount of the second HARQ-ACK feedback when the value of the second bit indicator is less than a threshold.

[0219] In another configuration, the example apparatus 1304 further includes means for receiving an indication of the amount of repetitions via RRC signaling.

[0220] The means may be a repeating component 198 of the apparatus 1304 configured to perform the functions recited by the means. As described above, the apparatus 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the means.

[0221] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network node or by one or more components of a network node (eg, base station 102, base station 310; CU 110; DU 130; RU 140; and / or Fig.16 The method may facilitate higher data rates, improved capacity, and / or improved spectrum efficiency by enabling the UE to perform HARQ feedback multiplexing with repetition on the PUSCH based on a bit indicator included in the uplink grant.

[0222] At 1402, the network node outputs an uplink grant scheduling an uplink transmission associated with a repetition amount at a UE, the uplink grant including a bit indicator, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10 In some aspects, the network node may send an uplink grant that schedules an uplink transmission associated with a repetition amount at the UE. The output of the uplink grant at 1402 may be obtained by Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0223] At 1404, the network node obtains a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of the PDSCH scheduled by the downlink grant, the first repetition overlapping with the HARQ-ACK feedback in the time domain, the amount of the HARQ-ACK feedback bits based on the bit indicator, such as in combination with Figure 7 Uplink transmission, Figure 8 Uplink transmission, Fig. 9 Uplink transmission and / or Fig.10 In some aspects, the network node may receive a first repetition of the uplink transmission. The first received acquisition at 1404 may be performed by Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0224] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a network node or by one or more components of a network node (eg, base station 102, base station 310; CU 110; DU 130; RU 140; and / or Fig.16 The method may facilitate higher data rates, improved capacity, and / or improved spectrum efficiency by enabling the UE to perform HARQ feedback multiplexing with repetition on the PUSCH based on a bit indicator included in the uplink grant.

[0225] At 1504, the network node outputs an uplink grant scheduling an uplink transmission associated with a repetition amount at the UE, the uplink grant including a bit indicator, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10In some aspects, the network node may send an uplink grant that schedules an uplink transmission associated with a repetition amount at the UE. The output of the uplink grant at 1504 may be Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0226] At 1506, the network node obtains a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of the PDSCH scheduled by the downlink grant, the first repetition overlapping with the HARQ-ACK feedback in the time domain, the amount of the HARQ-ACK feedback bits based on the bit indicator, as combined with Figure 7 Uplink transmission, Figure 8 Uplink transmission, Fig. 9 Uplink transmission and / or Fig.10 In some aspects, the network node may receive a first repetition of the uplink transmission. The first received acquisition at 1506 may be performed by Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0227] In some examples, at 1506, the downlink grant may include a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of HARQ-ACK feedback bits may be the same amount as the bit indicator, as described in conjunction with Formula 3 (above). In some examples, when the downlink bit indicator is greater than the bit indicator, the amount of HARQ-ACK feedback bits may be based on a relationship between the bit indicator and the downlink bit indicator, as described in conjunction with Formula 1 (above) and Formula 2 (above).

[0228] In some examples, at 1504, the uplink grant may include an indication of the amount of repetitions, such as in conjunction with Figure 7 Uplink grant 710, Figure 8 Uplink grant 810, Fig. 9 Uplink Grant 940 and / or Fig.10 In some examples, at 1502, the network node may output an indication of a repetition amount associated with the uplink message via RRC signaling, such as in conjunction with Figure 4 The output indicated at 1502 may be Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0229] In some examples, at 1504, the bit indicator may be a first bit indicator in a bit indicator set including a plurality of bit indicators, such as in combination with Figure 7In some examples, the amount of repetition and the number of bit indicators may be the same amount, such as in combination with Figure 7 The repeat indicator 712 and the bit indicator set 716 are described.

[0230] In an example where the bit indicator of 1504 is included in a bit indicator set, each repetition of the uplink transmission may be multiplexed with a bit quantity of HARQ-ACK feedback bits associated with a corresponding bit indicator in the bit indicator set, such as in combination with Figure 7 The multiplexing bits of the transmission are described. In some examples, the multiplexing for each repetition can be based on rate matching.

[0231] In some examples, at 1506, each repetition of the uplink transmission may be multiplexed with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in conjunction with Figure 8 An example of a repeat and bit indicator 816 and / or Fig. 9 In some examples, the second repetition of the uplink transmission may not overlap in the time domain with the second HARQ-ACK feedback scheduled by the second downlink grant, such as in conjunction with Figure 8 The three multiplexing bits on the second transmission 842 and the second repetition 822 are described. In some examples, the multiplexing for each repetition can be based on rate matching.

[0232] In some examples, at 1506, when the value of the bit indicator is greater than a threshold, each repetition of the uplink transmission may be multiplexed with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in combination with Fig. 9 The determination process 950, the multiplexing process 952, and the first transmission 954 are described. In some examples, the threshold can be two bits. In some examples, when the second repetition of the uplink transmission does not overlap with the second HARQ-ACK feedback scheduled by the second downlink grant in the time domain, the second repetition of the uplink transmission can be multiplexed with the amount of HARQ-ACK feedback bits indicated by the bit indicator, as combined with Figure 8 The three multiplexing bits on the second transmission 842 and the second repetition 822 are described. In some examples, the multiplexing for each repetition can be based on rate matching.

[0233] In some examples, at 1508, the network node may output a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant including a second bit indicator. As an example, the network node may send a second uplink grant scheduling a second uplink transmission associated with a second repetition amount. At 1510, the network node may obtain a second uplink transmission repetition, the second uplink transmission repetition and the second HARQ-ACK feedback scheduled by the second downlink grant overlapping in the time domain. In some such examples, when the value of the second bit indicator is less than a threshold, the second uplink transmission repetition may exclude multiplexing of a second amount of HARQ-ACK feedback bits for the second HARQ-ACK feedback. In some examples, the threshold may be two bits. The output of the second uplink grant at 1508 and the acquisition of the second uplink transmission repetition at 1510 may be determined by Fig.16 The scheduling component 199 of the network entity 1602 is executed.

[0234] In some examples, when a second repetition of the uplink transmission overlaps in the time domain with a second HARQ-ACK feedback scheduled by a second downlink grant and the value of the bit indicator is less than or equal to a threshold, the second repetition may be multiplexed with the amount of HARQ-ACK feedback bits indicated by the bit indicator, such as in combination with Fig. 9 The determination process 960, the multiplexing process 964 and the third transmission 966 are described. In some examples, the second repetition can be multiplexed by puncturing the second repetition based on the amount of HARQ-ACK feedback bits indicated by the bit indicator.

[0235] Fig.161600 is a diagram illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the scheduling component 199, the network entity 1602 may include a CU 1610; both a CU 1610 and a DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both a DU 1630 and a RU 1640; or a RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1613. In some aspects, an additional memory module 1614 and a communication interface 1618 may also be included. CU 1610 communicates with DU 1630 via a midhaul link, such as an F1 interface. DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1633. In some aspects, DU 1630 may also include additional memory modules 1634 and a communication interface 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1643. In some aspects, RU 1640 may also include additional memory modules 1644, one or more transceivers 1646, an antenna 1680, and a communication interface 1648. RU 1640 communicates with UE 104. On-chip memory (e.g., on-chip memory 1613, on-chip memory 1633, and / or on-chip memory 1643) and / or additional memory modules (e.g., additional memory module 1614, additional memory module 1634, and / or additional memory module 1644) may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the CU processor 1612, the DU processor 1632, and the RU processor 1642 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0236] As discussed above, the scheduling component 199 is configured to output an uplink grant scheduling an uplink transmission associated with an amount of repetitions at the UE, the uplink grant including a bit indicator. The scheduling component 199 may also be configured to obtain a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of HARQ-ACK feedback bits for HARQ-ACK feedback of the PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits based on the bit indicator.

[0237] The scheduling component 199 may be within one or more processors of one or more of the CU 1610, DU 1630, and RU 1640. The scheduling component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof.

[0238] The network entity 1602 may include various components configured for various functions. For example, the scheduling component 199 may include executing Fig.14 and / or Fig.15 Each block of the algorithm in the flowchart is one or more hardware components.

[0239] In one configuration, the network entity 1602 includes means for outputting an uplink grant scheduling an uplink transmission associated with an amount of repetitions at the UE, the uplink grant including a bit indicator. The example network entity 1602 also includes means for obtaining a first repetition of the uplink transmission, the first repetition multiplexing an amount of HARQ-ACK feedback bits for HARQ-ACK feedback for a PDSCH scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits being based on the bit indicator.

[0240] In another configuration, the example network entity 1602 further includes means for outputting a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant including a second bit indicator. The example network entity 1602 further includes means for obtaining a second uplink transmission repetition, the second uplink transmission and a second HARQ-ACK feedback scheduled by the second downlink grant overlapping in the time domain, wherein when the value of the second bit indicator is less than a threshold, the second uplink transmission repetition excludes multiplexing of bits of the second amount of the second HARQ-ACK feedback.

[0241] In another configuration, the example network entity 1602 further includes means for outputting an indication of the amount of repetitions via RRC signaling.

[0242] The means may be a scheduling component 199 of the network entity 1602 configured to perform the functions recited by the means. As described above, the network entity 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

[0243] The various aspects disclosed herein provide techniques for improving HARQ feedback multiplexing with repetitions on PUSCH. The disclosed techniques can provide higher data rates, improve capacity and / or improve spectral efficiency. For example, the various aspects disclosed herein can configure a UE to determine to perform multiplexing on repetitions, regardless of whether the repetitions overlap in time with HARQ feedback. Additionally, the UE can perform multiplexing based on the amount of bits indicated by an uplink grant. By determining to perform multiplexing based on the amount of bits indicated by an uplink grant (e.g., a bit indicator) and regardless of whether there is an overlap in time, the UE can solve problems associated with missed downlink grants. In some examples, the bit indicator may include a bit indicator set, which includes multiple bit indicators. For example, the amount of bit indicators in the bit indicator set may correspond to the amount of repetitions configured for an uplink message. The amount of repetitions may be indicated via an uplink grant and / or via radio resource control (RRC) signaling. In some such examples, the UE can use the corresponding bit indicators in the bit indicator set to determine the amount of z bits to be multiplexed on the corresponding repetitions. In other examples, the set of bit indicators may include a one-bit indicator applied to each repetition of the uplink message.

[0244] On the other hand, the UE may be configured to determine whether to perform multiplexing on the repetition based on the bit indicator included in the uplink grant. For example, when the value of the bit indicator meets the threshold (e.g., x bits of the bit indicator are greater than or equal to the threshold), the UE may perform multiplexing on the repetition, regardless of whether the repetition overlaps in time with the HARQ feedback scheduled by the downlink grant. In an example where the value of the bit indicator does not meet the threshold (e.g., x bits are less than the threshold), when the repetition overlaps in time with the HARQ feedback, the UE may multiplex x bits of the HARQ feedback on the repetition. When the repetition does not overlap in time with the HARQ feedback, the UE may also skip multiplexing or multiplex zero bits on the repetition.

[0245] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0246] The foregoing 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a condition is met, but no specific or immediate time limit is required for the occurrence of an action. The wording "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data can be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a set of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0247] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0248] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.

[0249] Aspect 1 is a method for performing wireless communications at a UE, the method comprising: receiving an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant comprising a bit indicator; and sending a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, and the amount of the HARQ-ACK feedback bits being based on the bit indicator.

[0250] Aspect 2 is a method according to aspect 1, the method further comprising: the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, and the repetition amount and the number of the bit indicators are the same amount.

[0251] Aspect 3 is a method according to any one of Aspects 1 and 2, the method further comprising: associating each repetition multiplexing of the uplink transmission with the bit quantity of the HARQ-ACK feedback bit with a corresponding bit indicator in the bit indicator set.

[0252] Aspect 4 is a method according to any one of aspects 1 to 3, the method further comprising: multiplexing each repetition based on rate matching.

[0253] Aspect 5 is a method according to any one of aspects 1 to 4, the method further comprising: multiplexing each repetition of the uplink transmission with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

[0254] Aspect 6 is a method according to any one of aspects 1 to 5, the method further comprising: a second repetition of the uplink transmission does not overlap with a second HARQ-ACK feedback scheduled by a second downlink grant in the time domain.

[0255] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: multiplexing each repetition based on rate matching.

[0256] Aspect 8 is a method according to any one of Aspects 1 to 7, and the method further includes: when the value of the bit indicator is greater than a threshold, multiplexing each repetition of the uplink transmission by the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

[0257] Aspect 9 is a method according to any one of aspects 1 to 8, the method further comprising: the threshold is two bits.

[0258] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: a second repetition of the uplink transmission does not overlap with a second HARQ-ACK feedback scheduled by a second downlink grant in the time domain.

[0259] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: multiplexing each repetition based on rate matching.

[0260] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: receiving a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant comprising a second bit indicator; sending a second uplink transmission repetition, the second uplink transmission repetition and the second HARQ-ACK feedback scheduled by the second downlink grant overlap in the time domain; and when the value of the second bit indicator is less than a threshold, skipping multiplexing of bits of the second amount of the second HARQ-ACK feedback

[0261] Aspect 13 is a method according to any one of aspects 1 to 12, the method further comprising: the threshold is two bits.

[0262] Aspect 14 is a method according to any one of Aspects 1 to 13, the method further comprising: the downlink grant includes a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of the HARQ-ACK feedback bits is the same amount as the bit indicator.

[0263] Aspect 15 is a method according to any one of Aspects 1 to 14, the method further comprising: when the downlink bit indicator is greater than the bit indicator, the amount of the HARQ-ACK feedback bit is based on the relationship between the bit indicator and the downlink bit indicator.

[0264] Aspect 16 is a method according to any one of aspects 1 to 15, the method further comprising: the uplink grant includes an indication of the repetition amount.

[0265] Aspect 17: According to any one of aspects 1 to 16, the method further comprises: receiving an indication of the repetition amount via radio resource control (RRC) signaling.

[0266] Aspect 18 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 1 to 17.

[0267] In aspect 19, according to the apparatus of aspect 18, the apparatus further comprises: at least one antenna, the at least one antenna coupled to the at least one processor.

[0268] In aspect 20, the apparatus according to aspect 18 or 19, the apparatus further comprises: a transceiver coupled to the at least one processor.

[0269] Aspect 21 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 17.

[0270] In aspect 22, according to the apparatus of aspect 21, the apparatus further comprises: at least one antenna coupled to the means for performing the method according to any one of aspects 1 to 17.

[0271] In aspect 23, according to the apparatus of aspect 21 or 22, the apparatus further comprises: a transceiver coupled to the means for performing the method according to any one of aspects 1 to 17.

[0272] Aspect 24 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 17.

[0273] Aspect 25 is a method for performing wireless communications at a network node, the method comprising: outputting an uplink grant for an uplink transmission associated with a repetition amount at a user equipment (UE) and the uplink grant comprising a bit indicator; and obtaining a first repetition of the uplink transmission, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by the downlink grant, the first repetition and the HARQ-ACK feedback overlapping in the time domain, the amount of the HARQ-ACK feedback bits being based on the bit indicator.

[0274] Aspect 26 is a method according to aspect 25, the method further comprising: the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, the repetition amount and the number of the bit indicators are the same amount.

[0275] Aspect 27 is a method according to any one of aspects 25 and 26, the method also comprising: each repetition of the uplink transmission is multiplexed with the bit quantity of the HARQ-ACK feedback bit associated with the corresponding bit indicator in the bit indicator set.

[0276] Aspect 28 is a method according to any one of aspects 25 to 27, the method further comprising: multiplexing each repetition based on rate matching.

[0277] Aspect 29 is a method according to any one of aspects 25 to 28, the method also including: each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

[0278] Aspect 30 is a method according to any one of aspects 25 to 29, the method further comprising: a second repetition of the uplink transmission does not overlap with a second HARQ-ACK feedback scheduled by a second downlink grant in the time domain.

[0279] Aspect 31 is a method according to any one of aspects 25 to 30, the method further comprising: multiplexing each repetition based on rate matching.

[0280] Aspect 32 is a method according to any one of Aspects 25 to 31, the method further comprising: when the value of the bit indicator is greater than a threshold, each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

[0281] Aspect 33 is a method according to any one of aspects 25 to 32, the method further comprising: the threshold is two bits.

[0282] Aspect 34 is a method according to any one of aspects 25 to 33, the method also including: the second repetition of the uplink transmission does not overlap with the second HARQ-ACK feedback scheduled by the second downlink grant in the time domain.

[0283] Aspect 35 is a method according to any one of aspects 25 to 34, the method further comprising: multiplexing of each repetition is based on rate matching.

[0284] Aspect 36 is a method according to any one of Aspects 25 to 35, the method further comprising: outputting a second uplink grant for scheduling a second uplink transmission associated with a second repetition quantity, the second uplink grant comprising a second bit indicator; and obtaining a second uplink transmission repetition, the second uplink transmission and a second HARQ-ACK feedback scheduled by the second downlink grant overlapping in the time domain, wherein when the value of the second bit indicator is less than a threshold, the second uplink transmission repetition excludes multiplexing of bits of the second quantity of the second HARQ-ACK feedback.

[0285] Aspect 37 is a method according to any one of aspects 25 to 36, the method further comprising: the threshold is two bits.

[0286] Aspect 38 is a method according to any one of Aspects 25 to 37, the method further comprising: the downlink grant includes a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of the HARQ-ACK feedback bits is the same amount as the bit indicator.

[0287] Aspect 39 is a method according to any one of Aspects 25 to 38, and the method also includes: when the downlink bit indicator is greater than the bit indicator, the amount of the HARQ-ACK feedback bit is based on the relationship between the bit indicator and the downlink bit indicator.

[0288] Aspect 40 is a method according to any one of aspects 25 to 39, the method further comprising: the uplink grant includes an indication of the repetition amount.

[0289] Aspect 41: According to any one of aspects 25 to 40, the method further comprises: outputting an indication of the repetition amount via radio resource control (RRC) signaling.

[0290] Aspect 42 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of Aspects 25 to 41.

[0291] In aspect 43, according to the apparatus of aspect 42, the apparatus further comprises: at least one antenna, the at least one antenna coupled to the at least one processor.

[0292] In aspect 44, the apparatus according to aspect 42 or 43, the apparatus further comprises: a transceiver coupled to the at least one processor.

[0293] Aspect 45 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 25 to 41.

[0294] In aspect 46, according to the apparatus of aspect 45, the apparatus further comprises: at least one antenna coupled to the means for performing the method according to any one of aspects 25 to 41.

[0295] In aspect 47, according to the apparatus of aspect 45 or 46, the apparatus further comprises: a transceiver coupled to the means for performing the method according to any one of aspects 25 to 41.

[0296] Aspect 48 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 25 to 41.

Claims

1. A device for wireless communication at a user equipment (UE), the device include: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant comprising a bit indicator; and A first repetition of the uplink transmission is sent, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by a downlink grant, the first repetition and the HARQ-ACK feedback overlap in the time domain, and the amount of the HARQ-ACK feedback bits is based on the bit indicator. 2 . The apparatus according to claim 1 , wherein the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, and the repetition amount and the number of bit indicators are the same amount.

3. The apparatus of claim 2, wherein the at least one processor is further configured to: Each repetition of the uplink transmission is multiplexed with a bit quantity of the HARQ-ACK feedback bits associated with a corresponding bit indicator in the set of bit indicators.

4. The apparatus of claim 1 , wherein the at least one processor is further configured to: Each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

5. The apparatus of claim 4, wherein a second repetition of the uplink transmission does not overlap in the time domain with a second HARQ-ACK feedback scheduled by a second downlink grant.

6. The apparatus of claim 1, wherein the at least one processor is further configured to: When the value of the bit indicator is greater than a threshold, each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator. The apparatus of claim 6 , wherein the threshold is two bits.

8. The apparatus of claim 6, wherein a second repetition of the uplink transmission does not overlap in the time domain with a second HARQ-ACK feedback scheduled by a second downlink grant.

9. The apparatus of claim 1 , wherein the at least one processor is further configured to: receiving a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant comprising a second bit indicator; sending a second uplink transmission repetition, wherein the second uplink transmission repetition overlaps with a second HARQ-ACK feedback scheduled by a second downlink grant in the time domain; and When the value of the second bit indicator is less than a threshold, multiplexing of a second amount of bits of the second HARQ-ACK feedback is skipped.

10. The apparatus of claim 1, wherein the downlink grant comprises a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of the HARQ-ACK feedback bits is the same amount as the bit indicator.

11. The apparatus of claim 10, wherein when the downlink bit indicator is greater than the bit indicator, the amount of the HARQ-ACK feedback bits is based on a relationship between the bit indicator and the downlink bit indicator.

12. The device according to claim 1, further comprising: include: A transceiver is coupled to the at least one processor.

13. A method for wireless communication at a user equipment (UE), the method include: receiving an uplink grant scheduling an uplink transmission associated with a repetition amount, the uplink grant comprising a bit indicator; as well as A first repetition of the uplink transmission is sent, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by a downlink grant, the first repetition and the HARQ-ACK feedback overlap in the time domain, and the amount of the HARQ-ACK feedback bits is based on the bit indicator. 14 . The apparatus of claim 13 , wherein the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, and the repetition amount and the number of bit indicators are the same amount.

15. The method according to claim 14, further comprising: include: Each repetition of the uplink transmission is multiplexed with a bit quantity of the HARQ-ACK feedback bits associated with a corresponding bit indicator in the set of bit indicators.

16. The method according to claim 13, further comprising: include: Each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

17. The method according to claim 13, further comprising: include: When the value of the bit indicator is greater than a threshold, each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

18. The method according to claim 13, further comprising: include: receiving a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant comprising a second bit indicator; Sending a second uplink transmission repetition, wherein the second uplink transmission repetition overlaps with a second HARQ-ACK feedback scheduled by a second downlink grant in the time domain; as well as When the value of the second bit indicator is less than a threshold, multiplexing of a second amount of bits of the second HARQ-ACK feedback is skipped.

19. An apparatus for wireless communication at a network node, the apparatus include: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: outputting an uplink grant scheduling an uplink transmission associated with a repetition amount at a user equipment (UE), the uplink grant comprising a bit indicator; and A first repetition of the uplink transmission is obtained, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by a downlink grant, the first repetition and the HARQ-ACK feedback overlap in the time domain, and the amount of the HARQ-ACK feedback bits is based on the bit indicator.

20. The apparatus of claim 19, wherein the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, and the repetition amount and the number of bit indicators are the same amount.

21. The apparatus of claim 19, wherein each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

22. The apparatus of claim 19, wherein the at least one processor is further configured to: outputting a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant comprising a second bit indicator; and A second uplink transmission repetition is obtained, wherein the second uplink transmission and a second HARQ-ACK feedback scheduled by a second downlink grant overlap in the time domain, wherein when the value of the second bit indicator is less than a threshold, the second uplink transmission repetition excludes multiplexing of a second amount of bits of the second HARQ-ACK feedback.

23. The apparatus of claim 19, wherein the downlink grant comprises a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of the HARQ-ACK feedback bits is the same amount as the bit indicator.

24. The device according to claim 19, further comprising: include: A transceiver is coupled to the at least one processor.

25. A method for wireless communication at a network node, the method include: outputting an uplink grant scheduling an uplink transmission associated with a repetition amount at a user equipment (UE), the uplink grant comprising a bit indicator; as well as A first repetition of the uplink transmission is obtained, the first repetition multiplexing a certain amount of hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) feedback bits for a physical downlink shared channel (PDSCH) scheduled by a downlink grant, the first repetition and the HARQ-ACK feedback overlap in the time domain, and the amount of the HARQ-ACK feedback bits is based on the bit indicator.

26. The apparatus of claim 25, wherein the bit indicator is a first bit indicator in a bit indicator set including a plurality of bit indicators, and the repetition amount and the number of bit indicators are the same amount.

27. The method of claim 25, wherein each repetition of the uplink transmission is multiplexed with the amount of the HARQ-ACK feedback bits indicated by the bit indicator.

28. The method according to claim 25, further comprising: include: outputting a second uplink grant scheduling a second uplink transmission associated with a second repetition amount, the second uplink grant comprising a second bit indicator; as well as A second uplink transmission repetition is obtained, wherein the second uplink transmission and a second HARQ-ACK feedback scheduled by a second downlink grant overlap in the time domain, wherein when the value of the second bit indicator is less than a threshold, the second uplink transmission repetition excludes multiplexing of a second amount of bits of the second HARQ-ACK feedback.

29. The method of claim 25, wherein the downlink grant includes a downlink bit indicator, and when the bit indicator is greater than or equal to the downlink bit indicator, the amount of the HARQ-ACK feedback bits is the same amount as the bit indicator.

30. The method of claim 29, wherein when the downlink bit indicator is greater than the bit indicator, the amount of the HARQ-ACK feedback bits is based on a relationship between the bit indicator and the downlink bit indicator.