Dependency of UCI type on UCI multiplexing with overlapping PUSCH

Abstract

A method and apparatus for multiplexing a UCI with an overlapping PUSCH based on a UCI type. The apparatus receives a configuration for a plurality of DCI operations, the configuration including an association with a CORESET configured for the UE, the association including: a CORESET pool index 0 or a CORESET-lacking pool index, and a CORESET pool index 1. The apparatus transmits a UCI multiplexed with a PUSCH from a plurality of overlapping PUSCHs that overlap in a time domain on the same carrier and overlap with the UCI in the time domain, the multiplexing being based on at least one of a type of the UCI, a content of the UCI, a feedback mode, or a carrier configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 485,242, filed on February 15, 2023, entitled “Dependency of UCI Type on UCI Multiplexing with Simultaneous PUSCH,” and U.S. Non-Provisional Patent Application Serial No. 18 / 434,626, filed on February 6, 2023, entitled “Dependency of UCI Type on UCI Multiplexing with Overlapping PUSCH,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to communication systems, and more particularly, to configurations for multiplexing uplink control information (UCI) with a simultaneous physical uplink shared channel (PUSCH) based on UCI type. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. 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 a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the 3rd 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 communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. 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 provides a brief overview of one or more aspects in order to provide a basic understanding of such aspects. This overview is not an extensive review of all contemplated aspects. This overview neither identifies key or important elements of all aspects nor delineates 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 that will be provided later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus receives a configuration for multiple downlink control information (DCI) operations, the configuration including an association with a control resource set (CORESET) configured for the UE, the association including a CORESET pool index of 0 or the absence of a CORESET pool index and a CORESET pool index of 1. The apparatus transmits uplink control information (UCI) multiplexed with PUSCHs from multiple overlapping physical uplink shared channels (PUSCHs), the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the multiplexing being based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network node. The apparatus may be a processor and / or a modem at the network node or the network node itself. The apparatus provides a configuration of multiple downlink control information (DCI) operations for a user equipment (UE), the configuration including an association with a control resource set (CORESET) configured for the UE, the association including a CORESET pool index of 0 or the absence of a CORESET pool index and a CORESET pool index of 1. The apparatus receives uplink control information (UCI) multiplexed with a physical uplink shared channel (PUSCH) from multiple overlapping PUSCHs, the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the UCI multiplexed with the PUSCH based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration.

[0009] To accomplish the foregoing and related ends, one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only a few of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a schematic 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 various 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 various aspects of the present disclosure.

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

[0016] Figure 4 is a diagram illustrating an example of UCI multiplexing.

[0017] Figure 5 is a diagram illustrating an example of UCI multiplexing.

[0018] Figure 6 is a diagram illustrating an example of HARQ-ACK for multiple DCIs.

[0019] Figure 7 is a diagram illustrating an example of overlapping PUSCHs.

[0020] Figures 8A-8B is a diagram illustrating an example of UCI multiplexing based on component carrier configuration.

[0021] Figure 9 is a call flow diagram of signaling between UE and base station.

[0022] Figure 10 is a flow chart of a method of wireless communication.

[0023] Figure 11 is a flow chart of a method of wireless communication.

[0024] Figure 12 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0025] Figure 13 is a flow chart of a method of wireless communication.

[0026] Figure 14 is a schematic diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0027] In wireless communications, certain multiplexing rules may be used to resolve conflicts or time overlaps between different uplink channels, such as when a PUSCH collides with a PUCCH or when a PUCCH collides with another PUCCH. A conflict between a PUCCH and another PUCCH may be due to carrying different data or payloads. In these cases, multiple UCIs may be multiplexed on the PUCCH or on the PUSCH under the assumption of a joint timeline. The determination of which PUSCH to select for UCI multiplexing in the case of multiple PUSCHs in one or more component carriers that overlap with UCI may affect, in part, the manner in which the PUSCH is selected for multiplexing with the UCI due to the multiple PUSCHs in the same component carrier.

[0028] Aspects presented herein provide a configuration for multiplexing UCI with overlapping PUSCH based on at least one of the UCI type, the feedback pattern, or the configuration of the PUCCH cell. At least one advantage of the present disclosure is that such factors can allow selection of PUSCH for multiplexing with UCI. In some aspects, these factors can determine whether UCI is associated with a CORESET pool index and can help determine whether multiplexing UCI on PUSCH to any TRP or a specific TRP is acceptable.

[0029] The detailed description set forth below in conjunction with the accompanying drawings describes various configurations and does not represent the only configurations in which the concepts described herein can be practiced. For the purpose of providing a comprehensive understanding of the various concepts, the detailed description includes 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 obscuring such concepts.

[0030] Several aspects of telecommunications systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described below in the detailed description and illustrated in the accompanying drawings by means of 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" comprising one or more processors. When multiple processors are implemented, the multiple processors can perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other, should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, or any combination thereof.

[0032] Thus, in one or more example aspects, 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. A storage medium may be any available medium that can be accessed by a computer. For example, such a computer-readable medium 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, a combination of computer-readable media of the types described, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0033] Although various aspects, implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, implementations and / or use cases may occur in many different arrangements and scenarios. The aspects, implementations and / or use cases described in this article can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations and / or use cases can be generated via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicability of the examples described. The scope of aspects, implementations and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations and further to the aggregation, distribution or original equipment manufacturer (OEM) equipment or system of one or more technologies incorporated herein. In some actual settings, the equipment incorporated with the described aspects and features can also include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in various devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0034] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. 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 device (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 called a standalone BS or a monolithic BS) or a decomposed base station.

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

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

[0037] Figure 1 1 is a schematic diagram 100 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 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 disaggregated base station elements, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CUs 110 may communicate with one or more DUs 130 via corresponding mid-haul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RUs 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces, or be coupled to one or more interfaces, configured to receive or send signals, data, or information (collectively, 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 the unit, may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface that is configured to receive signals or send signals to one or more of the other units via a wired transmission medium. In addition, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0039] In some aspects, the 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 using an interface configured to transmit signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 may be logically divided 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. The CU 110 may be implemented to communicate with the DU 130 as needed for network control and signaling.

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

[0041] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (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 a functional partitioning (such as a lower layer functional partitioning). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0042] The SMO framework 105 can be configured to support RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. In addition, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 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 .

[0043] The non-RT RIC 115 may be configured to include logic functions that implement 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 implement near-real-time control and optimization of RAN elements and resources via data collection and actions over interfaces connecting one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125 (such as via an E2 interface).

[0044] In some implementations, to generate AI / ML models 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 in 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).

[0045] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated by a dotted line indicates that each component may be included in the base station 102 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 called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also called reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also called forward link) transmissions 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 over one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation for up to a total of Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed over various wireless D2D communication systems, such as, for example, Bluetooth based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi TM (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE or NR.

[0047] 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 the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0048] 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 with the frequency range names FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes arises with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz), which is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0050] In view of the above aspects, unless otherwise specifically stated, the term "sub-6 GHz" and the like (if used herein) 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 specifically stated, the term "millimeter wave" and the like (if used herein) 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.

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

[0052] 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 TRP, a network node, a network entity, a network device, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0053] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (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 processing, access authorization, and subscription management. The one or more location servers 168 are shown as including a gateway mobile location center (GMLC) 165 and a location management function (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, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the position of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional velocity calculation based on the measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signal may be based on one or more of 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 / location systems), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., a 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 other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, 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 device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0055] Reference again Figure 1 In certain aspects, the UE 104 may include a multiplexing component 198 configured to: receive a configuration for multiple DCI operations, the configuration including an association with a CORESET configured for the UE, the association including a CORESET pool index of 0 or a lack of a CORESET pool index and a CORESET pool index of 1; and send UCI multiplexed with PUSCHs from multiple overlapping PUSCHs, the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the multiplexing being based on at least one of a type of UCI, a content of the UCI, a feedback mode, or a carrier configuration.

[0056] Reference again Figure 1 In certain aspects, the base station 102 may include a configuration component 199 configured to: provide a configuration of multiple DCI operations for a UE, the configuration including an association with a CORESET configured for the UE, the association including a CORESET pool index 0 or a lack of a CORESET pool index and a CORESET pool index 1; and receive UCI multiplexed with a PUSCH from a plurality of overlapping PUSCHs, the plurality of overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping in the time domain with the UCI, the UCI being multiplexed with the PUSCH based on at least one of a type of UCI, a content of the UCI, a feedback mode, or a carrier configuration.

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

[0058] Figure 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D 280 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), a subframe within a subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within a subcarrier set is dedicated to both DL and UL). Figure 2A 、 2C In the example provided, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily with DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling) via the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure as TDD.

[0059] Figures 2A-2DA frame structure is shown, and aspects of the present disclosure can be applied to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-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 normal or extended. For a normal 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 numeric scheme. The numeric scheme defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may be proportional to 1 / SCS.

[0060]

[0061] Table 1: Digital scheme, SCS and CP

[0062] For normal CP (14 symbols / time slot), different digital schemes μ0 to 6 allow 1, 2, 4, 8 and 16 time slots per subframe respectively. For extended CP, digital scheme 2 allows 4 time slots per subframe. Therefore, for normal CP and digital scheme μ, there are 14 symbols / time slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is the digital scheme 0 to 6. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=6 has a subcarrier spacing of 960kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for a normal CP with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific number scheme and CP (normal or extended).

[0063] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which includes 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0065] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs within one OFDM symbol of the RB. The 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., common search space, UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at larger and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the position 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 not sent through the PBCH (such as the system information block (SIB)), and paging messages.

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

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

[0068] Figure 33 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation of RLC service data units (SDUs), segmentation and reassembly, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, MAC Multiplexing of SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0069] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. 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-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded 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 produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived based on a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0070] At the UE 350, each receiver 354Rx receives a signal via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they 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 and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point transmitted 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.

[0071] The controller / processor 359 may be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, 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.

[0072] 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: transmission 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.

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

[0074] 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 antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0075] The controller / processor 375 may be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and 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.

[0076] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Aspects related to the reuse component 198.

[0077] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Aspects related to the configuration component 199.

[0078] In wireless communications, certain multiplexing rules may be used to resolve conflicts or time overlaps between different uplink channels, such as when a PUSCH and a PUCCH conflict or when a PUCCH conflicts with another PUCCH. A conflict between a PUCCH and another PUCCH may be due to carrying different data or payloads, such as, for example, a conflict between a PUCCH for HARQ-ACK and a PUCCH for a scheduling request (SR), a conflict between a PUCCH for HARQ-ACK and a PUCCH for channel state information (CSI), a conflict between a PUCCH for SR and a PUCCH for SCI, or a conflict between a PUCCH for HARQ-ACK and a PUCCH for SCI and a PUCCH for SR. In these cases, multiple UCIs may be multiplexed on the PUCCH or on the PUSCH under the assumption of a joint timeline, such as, for example, in Figure 4 In some cases, when one of the conflicting channels is a PUSCH, UCI can be multiplexed on the PUSCH. For example, Figure 4Schematic diagram 400 includes PUSCH1 402, PUCCH1 404 including a first UCI for HARQ-ACK, and PUCCH2 406 including a second UCI for CSI. PUSCH1 402, PUCCH1 404, and PUCCH2 406 may overlap or partially overlap in time. PUCCH1 404 and PUCCH2 406 may be multiplexed to form PUCCH3 408, which includes the first UCI from PUCCH1 404 and the second UCI from PUCCH2 406. PUCCH3 408 and PUSCH1 402 may also overlap or partially overlap. PUCCH3 408 and PUSCH1 402 may be multiplexed to form PUSCH1 402, which includes the first UCI for PUCCH1 404 and the second UCI for PUCCH2 406. The general rules for multiplexing may include: CSI multiplexing on PUCCH for the case where multiple CSI reports are in a time slot, then HARQ-ACK / SR / CSI multiplexing on PUCCH when multiple CSI reports overlap in the time domain, and UCI multiplexing with PUSCH when multiple CSI reports overlap in the frequency domain.

[0079] In some cases (such as when UCI overlaps with multiple PUSCHs in one or more uplink component carriers), if one of the PUSCHs has AP-CSI, the UE selects the PUSCH with AP-CSI to multiplex the UCI. The UE does not expect more than one PUSCH with AP-CSI to overlap with the UCI. If each of more than one PUSCH includes aperiodic CSI report, the UE does not expect the PUCCH resources resulting from multiplexing overlapping PUCCH resources (if applicable) to overlap with more than one PUSCH. If the UE multiplexes aperiodic CSI in the PUSCH and the UE will multiplex UCI including HARQ-ACK information in the PUCCH that overlaps with the PUSCH, and the timing conditions for overlapping PUCCH and PUSCH are met, the UE multiplexes only the HARQ-ACK information in the PUSCH and does not send the PUCCH. In some cases, the dynamically granted PUSCH (DG-PUSCH) is considered or has higher priority than the configured granted PUSCH (CG-PUSCH). The UE determines the PUSCH for UCI multiplexing, and if the candidate PUSCHs include a first PUSCH scheduled by the DCI format and a second PUSCH configured by the corresponding ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE is to multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCH meets the conditions for UCI multiplexing, the UE multiplexes UCI in the PUSCH from the first PUSCH. In some cases, the PUSCH on the smallest component carrier index among multiple PUSCHs may be considered for multiplexing. The UE multiplexes UCI in the PUSCH of the serving cell with the smallest ServCellIndex. In some cases, if there are multiple PUSCHs in the component carrier with the smallest index, the PUSCH that starts earliest in time may be considered for multiplexing. The UE multiplexes UCI in the earliest PUSCH sent by the UE in the time slot. However, PUSCHs may not overlap in the time domain within the same component carrier, such as for the case where more than one PUSCH is in a CC and is transmitted in a time division multiplexed manner.

[0080] refer to Figure 5, diagram 500 provides an example of PUSCH candidates that may be considered for multiplexing. Diagram 500 includes a first component carrier CC0, a second component carrier CC1, and a third component carrier CC2. PUSCH1 502, including a configured grant, and PUCCH 504, including UCI, are within CC0. PUSCH2 506, including a dynamic grant, and PUSCH3 508, including a dynamic grant, are within CC1. PUSCH4 510, including a dynamic grant, and PUSCH5 512, including a configured grant, are within CC2. Based on the above rules, PUSCH1 502 is not considered for UCI multiplexing, in part due to the presence of dynamic grants (e.g., PUSCH2 506, PUSCH3 508, PUSCH4 510). Furthermore, PUSCH5 512 is also not considered for UCI multiplexing, in part due to the presence of dynamic grants (e.g., PUSCH2 506, PUSCH3 508, PUSCH4 510). The UE may select PUSCH2 506 to multiplex UCI because the second component carrier CC1 has the lowest index among the dynamic grants without including aperiodic CSI, and because PUSCH2 506 starts earlier in time.

[0081] For instances of HARQ-ACK feedback for multiple TRPs based on multiple DCI (e.g., HARQ-ACK for PDSCH), joint feedback or separate feedback may be configured. Joint ACK / NACK feedback carried on the same PUCCH resource may be used for ideal backhaul instances, such that data for different TRPs may be provided to one TRP and relayed to another TRP. Separate ACK / NACK feedback carried on the same PUCCH resource may be utilized in both ideal and non-ideal backhaul instances, but may be primarily utilized in non-ideal backhaul instances. For example, the HARQ-ACK reporting process is performed separately for CORESET pool indices 0 and 1. PUCCH resources containing HARQ-ACK for different CORESET pool index values ​​may be in the same time slot, but may not overlap, and should be time division multiplexed, such as in Figure 6 As shown in the schematic diagram 600 of .

[0082] In the case where PUSCHs with multiple DCIs overlap in the time domain, may or may not overlap in the frequency domain, this can be enabled by the multi-DCI based mTRP framework, where the two PUSCHs are associated with different CORESET pool index values. For example, the first PUSCH 704 can be associated with coresetPoolIndex value 0 and can be associated with the first SRS resource set and can be transmitted using the first beam, TCI state, power control parameter or precoder, as in Figure 7As shown in diagram 700 of FIG. A second PUSCH 702 may be associated with a CORESET pool index value of 1, may be associated with a second SRS resource set, and may be transmitted using a second beam, TCI state, power control parameter, or precoder.

[0083] In the case where multiple PUSCHs overlap with UCI in the time domain on one or more component carriers, the determination of which PUSCH to select for UCI multiplexing may affect the way in which the PUSCH is selected for multiplexing with UCI, partly due to multiple PUSCHs in the same component carrier. In some cases, the configuration may be arranged to consider a group of UCI and PUSCH (e.g., CORESET pool index), or may be arranged to perform the selection of one of the PUSCHs to break a tie if a unique PUSCH is not determined. However, there may be other ways of selecting a PUSCH for UCI multiplexing.

[0084] Aspects presented herein provide a configuration for multiplexing UCI with overlapping PUSCH based on at least one of the UCI type, the mode of feedback, or the configuration of the PUCCH cell. At least one advantage of the present disclosure is that such factors can allow selection of PUSCH for multiplexing with UCI. In some aspects, these factors can determine whether the UCI is associated with a CORESET pool index and can help determine whether it is acceptable to multiplex UCI on PUSCH to any TRP or a specific TRP. For example, if the backhaul between two TRPs is ideal, the network configures joint ACK / NACK. Therefore, the feedback type can be used to determine which factor to utilize to select PUSCH for multiplexing with UCI. As another example, if the UCI is periodic or semi-persistent CSI on PUCCH (e.g., dynamic HARQ-ACK is not included in the UCI), then the TRP can be aware of such semi-static PUCCH resources even in the case of non-ideal backhaul.

[0085] In some cases, for a first CORESET on the active downlink bandwidth portion of a component carrier, a CORESET pool index value of 0 may be provided to the UE, or no CORESET pool index value may be provided to the UE. For a second CORESET on the active downlink bandwidth portion of the serving cell, a CORESET pool index value of 1 may be provided to the UE. This may ensure that multi-DCI based operation is configured and two sets of CORESETs are configured across one or more component carriers. In some cases, if the UE is configured with two SRS resource sets for codebook-based or non-codebook-based PUSCH in at least one component carrier, or is configured with an RRC configuration that implements time-domain overlapping PUSCH in at least one subcarrier, this may ensure that at least one component carrier is enabled with time-domain overlapping PUSCH with multiple DCI. In some cases, at least two of the PUSCHs that overlap with UCI also overlap with each other and are in the same component carrier and associated with different CORESET pool index values.

[0086] In the case where UCI is associated with a CORESET pool index value, the UE may only consider PUSCHs associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI from among multiple overlapping PUSCHs with the UCI. For example, in some aspects, the CORESET pool index may have the highest weight or priority, while in some aspects, the CORESET pool index may have a decreasing weight or priority. For example, the CORESET pool index may be considered first, followed by a dynamic grant or a configured grant, then the lowest component carrier index, and then the earliest start time in the same component carrier. In some aspects, such as when the CORESET pool index has a decreasing weight or priority, the dynamic grant or the configured grant may be considered first, then the CORESET pool index, then the lowest component carrier index, and then the earliest start time in the same component carrier. In some aspects, the dynamic grant or the configured grant may be considered first, then the lowest component carrier index, then the CORESET pool index, and then the earliest start time in the same component carrier. It would be desirable not to end up multiplexing UCI associated with a CORESET pool index value on PUSCHs associated with different CORESET pool index values ​​due to non-ideal backhaul between TRPs.

[0087] In the case where UCI is not associated with a CORESET pool index value, and if two dynamically granted PUSCHs without AP-CSI in the lowest component carrier index start simultaneously, the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESETPoolIndex value 0) among the two PUSCHs with the same start time in the same component carrier. This may correspond to the UE first considering the dynamic grant, then the lowest component carrier index, then the earliest start time in the same component carrier, compared to the configured grant, and then selecting the PUSCH associated with CORESET pool index value 0. It would be desirable to multiplex UCI on PUSCHs associated with CORESET pool index values ​​due to ideal backhaul between TRPs or if UCI is semi-static, but also include a tie-breaking mechanism in the event that a unique PUSCH is not determined.

[0088] In some aspects, when multiple PUSCHs overlap with UCI in the time domain on one or more CCs, the type or content of the UCI plays a role in the selection of a PUSCH for UCI multiplexing. If the UCI includes HARQ-ACK associated with two CORESET pool index values, the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESET pool index value 0) among two PUSCHs with the same start time in the same component carrier. If the UCI type does not include HARQ-ACK and only includes CSI (e.g., periodic or semi-persistent CSI on PUCCH), the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESET pool index value 0) among two PUSCHs with the same start time in the same component carrier. If the UCI includes HARQ-ACK associated with only one CORESET pool index value, the UE only considers, among multiple overlapping PUSCHs with UCI, the PUSCH associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI.

[0089] In some aspects, when multiple PUSCHs overlap with UCI in the time domain on one or more CCs, the feedback type mode (e.g., ackNackFeedbackMode) may play a role in selecting the PUSCH for UCI multiplexing. If the feedback type mode is configured as joint, the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESET pool index value 0) among two PUSCHs with the same start time in the same component carrier. If the feedback type mode is configured as separate, the UE only considers the PUSCH associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI among the multiple overlapping PUSCHs with UCI.

[0090] In some aspects, such as if the feedback type mode is not configured, the UE may follow the behavior of the case where the feedback type mode is joint, and then the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESET pool index value 0) among two PUSCHs with the same start time in the same component carrier. In some aspects, such as if the feedback type mode is not configured, the UE may follow the behavior of the case where the feedback type mode is individual, and then the UE only considers the PUSCH associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI among multiple overlapping PUSCHs with UCI. In some aspects, if the feedback type mode is not configured, when multiple PUSCHs overlap with UCI in the time domain on one or more CCs, the type or content of the UCI plays a role in the selection of the PUSCH for UCI multiplexing. In some aspects, depending on the scheduling, HARQ-ACK may be associated with only one CORESET pool index value, or may be associated with two CORESET pool index values. In this case, when multiple PUSCHs overlap with UCI in the time domain on one or more CCs, the type or content of the UCI plays a role in selecting a PUSCH for UCI multiplexing.

[0091] In some aspects, when multiple PUSCHs overlap with UCI in the time domain on one or more component carriers, the configuration of the component carrier associated with the UCI (e.g., PUCCH cell) may play a role in the selection of the PUSCH for UCI multiplexing. If the PUCCH cell is configured with two CORESET pool index values ​​for applying two indicated TCI states, or two timing advance groups (TAGs), or two groups of PUCCH resources, the UE only considers the PUSCH associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI among the multiple overlapping PUSCHs with the UCI, otherwise, the UE may select the PUSCH associated with a fixed CORESET pool index value (e.g., CORESET pool index value 0) among the two PUSCHs with the same start time in the same component carrier. Reference Figure 8A In the diagram 800, a first component carrier CC0 is configured with two CORESET pool indices or configured with two TAGs. The first component carrier CC0 includes a PUCCH 802, which includes a UCI associated with a CORESET pool index value of 1 or a second TAG. The diagram 800 also includes a second component carrier CC1, which includes a PUSCH1 804 and a PUSCH2 806. PUCCH 802 and PUSCH2 806 are associated with the same CORESET pool index value, so that PUCCH 802 can be multiplexed with PUSCH2 806 because both are associated with the same CORESET pool index value. Figure 8B In the schematic diagram 810 , the first component carrier CC0 is not configured with two CORESET pool indexes and / or is not configured with two TAGs. Figure 8B The first component carrier CC0 includes a PUCCH 812 including UCI that is not explicitly associated with a CORESET pool index value. The second component carrier CC1 includes PUSCH1 814 and PUSCH2 816. The UE may select PUSCH1 814 for multiplexing with PUCCH 812 based on the association of PUSCH1 814 with the first CORESET pool index value.

[0092] In some aspects, such as for UCI multiplexing, when multiple PUSCHs overlap with UCI in the time domain on one or more component carriers and at least one of the PUSCHs includes AP-CSI, if the UCI and the PUSCH with AP-CSI are associated with the same CORESET pool index value, the UE may multiplex the UCI on the PUSCH. If the UCI and the PUSCH with AP-CSI are not associated with the same CORESET pool index value, the UE may multiplex the UCI on another PUSCH among the multiple PUSCHs associated with the same CORESET pool index value as the CORESET pool index value associated with the UCI. If the UCI and the PUSCH with AP-CSI are not associated with the same CORESET pool index value, the UE may discard the UCI. If the UCI and the PUSCH with AP-CSI are not associated with the same CORESET pool index value, the UE does not expect the UCI to overlap with the PUSCH including AP-CSI if the UCI and the PUSCH are not associated with the same CORESET pool index value. In some aspects, if one of the multiple PUSCHs includes AP-CSI, the UE multiplexes UCI on the PUSCH with the AP-CSI without regard to the association of the PUSCH with the CORESET pool index value.

[0093] In some aspects, such as if two PUSCHs out of a plurality of PUSCHs include AP-CSI such that the two PUSCHs are associated with different CORESET pool index values, then the UE does not expect more than one PUSCH with AP-CSI to overlap with UCI can be relaxed, but maintained according to the CORESET pool index value. For example, the PUSCH associated with the same CORESET pool index as the UCI is selected for multiplexing with the UCI. In some aspects, the PUSCH associated with a fixed CORESET pool index value (e.g., value 0) is selected for multiplexing with the UCI. In some aspects, the UCI includes at least HARQ-ACK, and if the UCI includes only periodic or semi-periodic CSI, the UCI is completely discarded due to the higher priority of AP-CSI on the PUSCH. If the UCI includes HARQ-ACK and CSI, only the HARQ-ACK portion is multiplexed on the PUSCH.

[0094] Figure 9 900 is a call flow diagram of signaling between a UE 902 and a base station 904. The base station 904 may be configured to provide at least one cell. The UE 902 may be configured to communicate with the base station 904. For example, Figure 1In the context of , base station 904 may correspond to base station 102, and UE 902 may correspond to at least UE 104. In another example, Figure 3 In the context of , base station 904 can correspond to base station 310, and UE 902 can correspond to UE 350.

[0095] At 906, base station 904 may provide configurations for multiple DCI operations for the UE, such as in conjunction with Figure 5-8B As shown in any of the figures. Base station 904 may provide a configuration for multiple DCI operations to UE 902. UE 902 may receive the configuration for multiple DCI operations. The configuration for multiple DCI operations for the UE may include an association with a CORESET configured for the UE. The association may include a CORESET pool index of 0 or a lack of a CORESET pool index and a CORESET pool index of 1.

[0096] At 908, the UE may multiplex the UCI with the PUSCH. For example, at 910, the UE may multiplex the UCI with the PUSCH based on a first rule under the first condition or a second rule under the second condition, such as in combination with Figure 5-8BAs shown in any of the figures. For example, the UE may multiplex UCI with PUSCH using a first rule based on a first condition. In another example, the UE may multiplex UCI with PUSCH using a second rule based on a second condition. In some aspects, the UE may multiplex UCI with PUSCH from multiple overlapping PUSCHs based on the type of UCI or the content of UCI. In such aspects, the UE may multiplex UCI with PUSCH based on a first rule under a first condition, the first condition being that the content of UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with multiple CORESET pool indices of multiple groups or that the UCI does not include HARQ-ACK. In some aspects, the UE multiplexes UCI with PUSCH from multiple overlapping PUSCHs based on a feedback mode. The UE may multiplex UCI with PUSCH based on a first rule under a first condition, the first condition being that the UE is configured with a joint ACKNACK feedback mode. In some aspects, such as in the absence of an ACKNACK feedback mode, the UE may multiplex UCI with PUSCH based on a first rule applied to the joint ACKNACK feedback mode. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on the carrier configuration for the component carrier (CC) associated with the UCI. For example, the UE may multiplex UCI with PUSCH based on a first rule under a first condition, where the CC associated with the UCI is configured with a single CORESET pool index, a single timing advance group (TAG), or a physical uplink control channel (PUCCH) resource for a single transmission configuration indicator (TCI) state. In some aspects, the UE may multiplex UCI with PUSCH from multiple overlapping PUSCHs based on the type of UCI or the content of the UCI. In such an aspect, the UE may multiplex UCI with PUSCH based on a second rule under a second condition, where the content of the UCI includes HARQ-ACK associated with a single CORESET pool index. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on a feedback mode. For example, in such aspects, the UE may multiplex UCI with PUSCH based on a second rule under a second condition, the second condition being that the UE is configured with a separate ACK NACK feedback mode. In some aspects, such as in the absence of an ACK NACK feedback mode, the UE may multiplex UCI with PUSCH based on a second rule applied to a separate ACK NACK feedback mode or a rule based on the type of UCI or the content of the UCI. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on the carrier configuration for the component carrier (CC) associated with the UCI.In such an aspect, for example, the UE may multiplex UCI with PUSCH based on a second rule under a second condition, where the second condition is that the CC associated with the UCI is configured with multiple CORESET pool indices, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

[0097] In some aspects, for example, at 912, the UE may further multiplex UCI on the first PUSCH based on the first PUSCH including aperiodic channel state information (AP-CSI) and being associated with the same CORESET pool index as the UCI, such as in conjunction with Figure 5-8B As shown in any of the figures. In some aspects, a first PUSCH in the plurality of overlapping PUSCHs includes AP-CSI. At 914, the UE may discard UCI. The UE may discard the UCI based on the first PUSCH being associated with a CORESET pool index that is different from the UCI. At 916, the UE may identify an error condition. The UE may identify the error condition based on the overlap in the time domain of the UCI with the first PUSCH having a CORESET pool index that is different from the UCI.

[0098] In some aspects, for example at 918, the UE may further multiplex UCI on the first PUSCH based on the first PUSCH including AP-CSI and being associated with a different CORESET pool index than the UCI, such as in conjunction with Figure 5-8B In some aspects, a first PUSCH in the plurality of overlapping PUSCHs includes AP-CSI.

[0099] In some aspects, for example at 920, the UE may multiplex UCI on a PUSCH associated with the same CORESET pool index as the UCI, such as in conjunction with Figure 5-8B In some aspects, at least two of the multiple overlapping PUSCHs include AP-CSI. At 922, the UE may multiplex UCI on a PUSCH associated with a defined CORESET pool index, as in conjunction with Figure 5-8B any one of the diagrams shown.

[0100] At 924, the UE may transmit UCI multiplexed with PUSCHs from multiple overlapping physical uplink shared channels (PUSCHs), the multiple overlapping PUSCHs overlapping in the time domain on one or more carriers and overlapping with the UCI in the time domain, as in conjunction with Figure 5-8B The multiplexing may be based on at least one of the UCI type, the UCI content, the feedback mode, or the carrier configuration.

[0101] Figure 101000 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 1204). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure a multiplexing rule for the UE based on UCI type / payload, feedback mode (e.g., joint or individual), or PUCCH cell configuration.

[0102] At 1002, a UE may receive a configuration for multiple DCI operations, the configuration including an association with a CORESET configured for the UE, such as in conjunction with Figure 5-8B For example, 1002 may be performed by the multiplexing component 198 of the device 1204. The association may include a CORESET pool index of 0 or a lack of a CORESET pool index and a CORESET pool index of 1.

[0103] At 1004, the UE may transmit UCI multiplexed with PUSCH from multiple overlapping PUSCHs that overlap in the time domain on the same carrier and overlap with the UCI in the time domain, as in conjunction with Figure 5-8B For example, 1004 may be performed by the multiplexing component 198 of the apparatus 1204. The multiplexing may be based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration.

[0104] Figure 11 1100 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 1204). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure a multiplexing rule for the UE based on UCI type / payload, feedback mode (e.g., joint or separate), or PUCCH cell configuration.

[0105] At 1102, the UE may receive a configuration for multiple DCI operations, the configuration including an association with a CORESET configured for the UE, such as in conjunction with Figure 5-8B For example, 1102 may be performed by the multiplexing component 198 of the device 1204. The association may include a CORESET pool index of 0 or a lack of a CORESET pool index and a CORESET pool index of 1.

[0106] At 1104, the UE may multiplex the UCI with the PUSCH based on the first rule under the first condition, such as in combination with Figure 5-8BAs shown in any of the figures. For example, 1104 can be performed by the multiplexing component 198 of the device 1204. In some aspects, the UE can multiplex UCI with PUSCH from multiple overlapping PUSCHs based on the type of UCI or the content of UCI. In such an aspect, the UE can multiplex UCI with PUSCH based on a first rule under a first condition, the first condition being that the content of UCI includes hybrid automatic repeat request acknowledgment (HARQ-ACK) associated with multiple CORESET pool indices of multiple groups or the UCI does not include HARQ-ACK. In some aspects, the UE multiplexes UCI with PUSCH from multiple overlapping PUSCHs based on a feedback mode. The UE can multiplex UCI with PUSCH based on a first rule under a first condition, the first condition being that the UE is configured with a joint ACK NACK feedback mode. In some aspects, such as in the absence of a configured ACK NACK feedback mode, the UE can multiplex UCI with PUSCH based on a first rule applied to the joint ACK NACK feedback mode. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on the carrier configuration for the component carrier (CC) associated with the UCI. For example, the UE may multiplex the UCI with the PUSCH based on a first rule under a first condition, where the CC associated with the UCI is configured with a single CORESET pool index, a single timing advance group (TAG), or a physical uplink control channel (PUCCH) resource for a single transmission configuration indicator (TCI) state.

[0107] At 1106, the UE may multiplex the UCI with the PUSCH based on a second rule under the second condition, such as in combination with Figure 5-8BAs shown in any of the figures. For example, 1106 can be performed by the multiplexing component 198 of the device 1204. In some aspects, the UE can multiplex UCI with PUSCH from multiple overlapping PUSCHs based on the type of UCI or the content of the UCI. In such an aspect, the UE can multiplex UCI with PUSCH based on a second rule under a second condition, the second condition being that the content of the UCI includes HARQ-ACK associated with a single CORESET pool index. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on a feedback mode. For example, in such an aspect, the UE can multiplex UCI with PUSCH based on a second rule under a second condition, the second condition being that the UE is configured with a separate ACK NACK feedback mode. In some aspects, such as in the absence of a configured ACK NACK feedback mode, the UE can multiplex UCI with PUSCH based on a second rule applied to the separate ACK NACK feedback mode or a rule based on the type of UCI or the content of the UCI. In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on the carrier configuration for the component carrier (CC) associated with the UCI. In such aspects, for example, the UE may multiplex UCI with PUSCH based on a second rule under a second condition, where the CC associated with the UCI is configured with multiple CORESET pool indices, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

[0108] At 1108, the UE may further multiplex the UCI on the first PUSCH based on the first PUSCH including AP-CSI and being associated with the same CORESET pool index as the UCI. For example, 1108 may be performed by the multiplexing component 198 of the apparatus 1204. In some aspects, the first PUSCH of the multiple overlapping PUSCHs includes AP-CSI.

[0109] At 1110, the UE may discard the UCI. For example, 1110 may be performed by the multiplexing component 198 of the apparatus 1204. The UE may discard the UCI based on the first PUSCH being associated with a different CORESET pool index than the UCI.

[0110] At 1112, the UE may identify an error condition. For example, 1112 may be performed by the multiplexing component 198 of the apparatus 1204. The UE may identify the error condition based on an overlap in the time domain of the UCI with a first PUSCH having a different CORESET pool index than the UCI.

[0111] At 1114, the UE may further multiplex UCI on the first PUSCH based on the first PUSCH including AP-CSI and being associated with a CORESET pool index different from the UCI, as in conjunction with Figure 5-8B For example, 1114 may be performed by the multiplexing component 198 of the apparatus 1204. In some aspects, a first PUSCH of the plurality of overlapping PUSCHs includes AP-CSI.

[0112] At 1116, the UE may multiplex the UCI on a PUSCH associated with the same CORESET pool index as the UCI, as in conjunction with Figure 5-8B For example, 1116 may be performed by the multiplexing component 198 of the apparatus 1204. In some aspects, at least two of the plurality of overlapping PUSCHs include AP-CSI.

[0113] At 1118, the UE may multiplex UCI on a PUSCH associated with a defined CORESET pool index, as in conjunction with Figure 5-8B For example, 1116 can be performed by the multiplexing component 198 of the device 1204.

[0114] At 1120, the UE may transmit UCI multiplexed with PUSCH from multiple overlapping PUSCHs that overlap in the time domain on the same carrier and overlap with the UCI in the time domain, as in conjunction with Figure 5-8B For example, 1120 may be performed by the multiplexing component 198 of the apparatus 1204. The multiplexing may be based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration.

[0115] Figure 1212 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1204. The apparatus 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1204 may include at least one cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., a cellular RF transceiver). The cellular baseband processor 1224 may include at least one on-chip memory 1224′. In some aspects, the apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 and at least one application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206′. In some aspects, the device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., a barometric 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, and / or other technologies for positioning), an additional memory module 1226, a power supply 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or utilize an antenna 1280 for communication. The cellular baseband processor 1224 communicates with the UE 104 and / or RUs associated with the network entity 1202 via one or more antennas 1280 through the transceiver 1222. The cellular baseband processor 1224 and the application processor 1206 may each include computer-readable media / memory 1224', 1206', respectively. The additional memory module 1226 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1224', 1206', 1226 may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, which includes executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1224 / application processor 1206, the software enables the cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or at least one memory 360. In one configuration, the apparatus 1204 may be at least one processor chip (modem and / or applications) and include only the cellular baseband processor 1224 and / or the application processor 1206, while in another configuration, the apparatus 1204 may be the entire UE (e.g., see ). Figure 3 UE 350) and includes additional modules of device 1204.

[0116] As described above, component 198 can be configured to: receive a configuration for multiple DCI operations, the configuration including an association with a CORESET configured for the UE, the association including a CORESET pool index of 0 or the absence of a CORESET pool index and a CORESET pool index of 1; and transmit UCI multiplexed with PUSCH from multiple overlapping PUSCHs on the same carrier, the multiple overlapping PUSCHs overlapping in the time domain and overlapping with the UCI in the time domain, the multiplexing being based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration. Component 198 can be within the cellular baseband processor 1224, the application processor 1206, or both the cellular baseband processor 1224 and the application processor 1206. Component 198 can be one or more hardware components specifically configured to perform the described process / algorithm, implemented by one or more processors configured to perform the described process / algorithm, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors can perform the described process / algorithm individually or in combination. As shown, apparatus 1204 may include various components configured for various functions. In one configuration, apparatus 1204 (particularly cellular baseband processor 1224 and / or application processor 1206) may include means for receiving a configuration for multiple DCI operations, the configuration including an association with a CORESET configured for a UE, the association including a CORESET pool index 0 or the absence of a CORESET pool index and a CORESET pool index 1. The apparatus includes means for transmitting UCI multiplexed with PUSCH from multiple overlapping PUSCHs, the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the multiplexing being based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration. The apparatus also includes means for multiplexing the UCI with the PUSCH based on a first rule under a first condition, the first condition being that the content of the UCI includes HARQ-ACK associated with multiple CORESET pool indices of the multiple groups or that the UCI does not include HARQ-ACK. The apparatus further includes means for multiplexing UCI with PUSCH based on a second rule under a second condition, wherein the second condition is that the content of the UCI includes HARQ-ACK associated with a single CORESET pool index. The apparatus further includes means for multiplexing UCI with PUSCH based on a first rule under a first condition, wherein the first condition is that the UE is configured with a joint ACK NACK feedback mode. The apparatus further includes means for multiplexing UCI with PUSCH based on a second rule under a second condition, wherein the second condition is that the UE is configured with a separate ACK NACK feedback mode.The apparatus also includes means for multiplexing UCI with a PUSCH based on a first rule under a first condition, the first condition being that the CC associated with the UCI is configured with a single CORESET pool index, a single TAG, or a PUCCH resource for a single TCI state. The apparatus also includes means for multiplexing UCI with a PUSCH based on a second rule under a second condition, the second condition being that the CC associated with the UCI is configured with multiple CORESET pool indexes, multiple TAGs, or multiple PUCCH resources for multiple TCI states. The apparatus also includes means for multiplexing UCI on the first PUSCH based further on the first PUSCH including AP-CSI and being associated with the same CORESET pool index as the UCI. The apparatus also includes means for discarding UCI based on the first PUSCH being associated with a CORESET pool index different from that of the UCI. The apparatus also includes means for identifying an error condition based on an overlap in the time domain of the UCI with the first PUSCH having a different CORESET pool index than that of the UCI. The apparatus further includes means for multiplexing UCI on the first PUSCH, further based on the first PUSCH including AP-CSI and being associated with a different CORESET pool index than the UCI. The apparatus further includes means for multiplexing UCI on a PUSCH associated with the same CORESET pool index as the UCI. The apparatus further includes means for multiplexing UCI on a PUSCH associated with a defined CORESET pool index. These means may be the component 198 of the apparatus 1204 configured to perform the functions recited by these means. As described above, the apparatus 1204 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, these means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by these means.

[0117] Figure 13 1300 is a flow chart of a method for wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1402). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure a multiplexing rule for a UE based on UCI type / payload, feedback mode (e.g., joint or individual), or PUCCH cell configuration.

[0118] At 1302, a network entity may provide configurations for multiple DCI operations for a UE, such as in conjunction with Figure 5-8BAs shown in any of the figures. For example, 1302 can be performed by the configuration component 199 of the network entity 1402. The configuration of multiple DCI operations for the UE can include an association with the CORESET configured for the UE. The association can include a CORESET pool index of 0 or a lack of a CORESET pool index and a CORESET pool index of 1.

[0119] At 1304, the network entity may receive UCI multiplexed with PUSCH from multiple overlapping PUSCHs that overlap in the time domain on the same carrier and overlap with the UCI in the time domain, as in conjunction with Figure 5-8B As shown in any of the figures. For example, 1304 can be performed by the configuration component 199 of the network entity 1402. The UCI multiplexed with the PUSCH can be based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration. In some aspects, the UCI is multiplexed with the PUSCH from multiple overlapping PUSCHs based on the type of UCI or the content of the UCI. In such aspects, the UCI is multiplexed with the PUSCH based on a first rule under a first condition, the first condition being that the content of the UCI includes a hybrid automatic repeat request acknowledgment (HARQ-ACK) associated with multiple CORESET pool indexes of the multiple groups or the UCI does not include HARQ-ACK. In some aspects, the UCI is multiplexed with the PUSCH based on a second rule under a second condition, the second condition being that the content of the UCI includes a HARQ-ACK associated with a single CORESET pool index.

[0120] In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on a feedback mode. In some aspects, UCI is multiplexed with PUSCH based on a first rule under a first condition, where the first condition is that the UE is configured with a joint acknowledgement (ACK) negative acknowledgement (NACK) feedback mode. In some aspects, UCI is multiplexed with PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK / NACK feedback mode. When an ACK / NACK feedback mode is not configured, UCI is multiplexed with PUSCH based on one of the first rule applied to the joint ACK / NACK feedback mode, the second rule applied to the separate ACK / NACK feedback mode, or a rule based on the type of UCI or the content of the UCI.

[0121] In some aspects, UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on the carrier configuration for the component carrier (CC) associated with the UCI. In some aspects, UCI is multiplexed with PUSCH based on a first rule under a first condition, where the CC associated with the UCI is configured with a single CORESET pool index, a single timing advance group (TAG), or PUCCH resources for a single TCI state. In some aspects, UCI is multiplexed with PUSCH based on a second rule under a second condition, where the CC associated with the UCI is configured with multiple CORESET pool indices, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

[0122] In some aspects, a first PUSCH in the plurality of overlapping PUSCHs includes aperiodic channel state information (AP-CSI). UCI is multiplexed on the first PUSCH based on the first PUSCH including AP-CSI and being associated with the same CORESET pool index as the UCI. In some aspects, scheduling the UCI to overlap in the time domain with a first PUSCH having a different CORESET pool index than the UCI can be avoided. In some aspects, a first PUSCH in the plurality of overlapping PUSCHs includes AP-CSI. The UCI is further multiplexed on the first PUSCH based on the first PUSCH including AP-CSI and being associated with a different CORESET pool index than the UCI. In some aspects, at least two PUSCHs in the plurality of overlapping PUSCHs include AP-CSI. In this case, the UCI is multiplexed on a PUSCH associated with the same CORESET pool index as the UCI or on a PUSCH associated with a defined CORESET pool index.

[0123] Figure 1414 is a diagram illustrating an example of a hardware implementation for a network entity 1402. Network entity 1402 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1402 may include at least one of a CU 1410, a DU 1430, or a RU 1440. For example, depending on the layer functionality handled by component 199, network entity 1402 may include a CU 1410; both a CU 1410 and a DU 1430; each of a CU 1410, a DU 1430, and a RU 1440; a DU 1430; both a DU 1430 and a RU 1440; or a RU 1440. CU 1410 may include at least one CU processor 1412. CU processor 1412 may include on-chip memory 1412′. In some aspects, CU 1410 may also include an additional memory module 1414 and a communication interface 1418. The CU 1410 communicates with the DU 1430 over a mid-haul link, such as an F1 interface. The DU 1430 may include at least one DU processor 1432. The DU processor 1432 may include on-chip memory 1432′. In some aspects, the DU 1430 may also include an additional memory module 1434 and a communication interface 1438. The DU 1430 communicates with the RU 1440 over a fronthaul link. The RU 1440 may include at least one RU processor 1442. The RU processor 1442 may include on-chip memory 1442′. In some aspects, the RU 1440 may also include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. The RU 1440 communicates with the UE 104. On-chip memory 1412', 1432', 1442' and additional memory modules 1414, 1434, 1444 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1412, 1432, 1442 is responsible for general processing, which includes the execution of software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0124] As described above, component 199 can be configured to: provide a configuration of multiple DCI operations for a UE, the configuration including an association with a CORESET configured for the UE, the association including a CORESET pool index of 0 or the absence of a CORESET pool index and a CORESET pool index of 1; and receive UCI multiplexed with a PUSCH from multiple overlapping PUSCHs, the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping in the time domain with the UCI, the UCI multiplexed with the PUSCH based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration. Component 199 can be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 can be one or more hardware components specifically configured to perform the described process / algorithm, implemented by one or more processors configured to perform the described process / algorithm, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors can perform the described process / algorithm individually or in combination. The network entity 1402 may include various components configured for various functions. In one configuration, the network entity 1402 may include means for providing a configuration of multiple DCI operations for a UE, the configuration including an association with a CORESET configured for the UE, the association including a CORESET pool index of 0 or the absence of a CORESET pool index and a CORESET pool index of 1. The network entity includes means for receiving UCI multiplexed with a PUSCH from multiple overlapping PUSCHs, the multiple overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping in the time domain with UCI, the UCI multiplexed with the PUSCH based on at least one of the type of UCI, the content of the UCI, the feedback mode, or the carrier configuration. The means may be the component 199 of the network entity 1402 configured to perform the functions recited by the means. As described above, the network entity 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be the TX Processor 316, the RX Processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0125] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative of example methods. Based on design preferences, it should be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged. In addition, some blocks can be merged or omitted. The accompanying methods require that the current elements of the various blocks be presented in a sample order and are not limited to the specific order or hierarchy presented.

[0126] The foregoing description is provided so that any person skilled in the art can 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 are to be given the full scope consistent with the language claims. Unless explicitly stated otherwise, reference to a singular element does not mean "one and only one", but "one or more". Terms such as "if", "when ... when" and "when ... while" do not imply a direct temporal relationship or reaction. That is, these phrases (e.g., "when ... when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of the action, but only imply that if the condition is met, the action will occur, but does not require a specific or immediate time constraint for the occurrence of the action. The word "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 advantageous over other aspects. Unless otherwise explicitly stated, 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 multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may include only A, only B, only C, A and B, A and C, B and C, or A, B, and C, where any such combination may include 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 X, X will include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor is configured to perform the set of functions, either individually or in any combination. Thus, each of the at least one processor can be configured to perform a specific subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. If a first device receives data from a second device or sends data to a second device, the data can be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a set of devices. A device configured to "output" data (such as a transmission, signal, or message) can, for example, use a transceiver to send data, or can send data to a device that sends data. A device configured to "obtain" data (such as a transmission, signal, or message) can, for example, use a transceiver to receive data, or can obtain data from a device that receives data.The information stored in the memory includes instructions and / or data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be known to those of ordinary skill in the art are expressly incorporated herein by reference and are included by the claims. In addition, the content disclosed herein is not dedicated to the public, regardless of whether such disclosure is clearly recorded in the claims. The words "module", "mechanism", "element", "device" and the like may not be substitutes for the word "unit". Thus, no claim element is to be interpreted as a functional unit unless the element is explicitly recorded using the phrase "unit for ..."

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

[0128] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, and are not limited thereto.

[0129] Aspect 1 is a method of wireless communication at a UE, the method comprising: receiving a configuration for multiple DCI operations, the configuration comprising an association with a CORESET configured for the UE, the association comprising a CORESET pool index 0 or a lack of a CORESET pool index and a CORESET pool index 1; and sending UCI multiplexed with a PUSCH from a plurality of overlapping PUSCHs, the plurality of overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the UCI being multiplexed with the PUSCH based on at least one of a type of UCI, a content of the UCI, a feedback mode, or a carrier configuration.

[0130] Aspect 2 is the method according to aspect 1, further comprising: UCI is multiplexed with PUSCHs from multiple overlapping PUSCHs based on the type of UCI or the content of UCI.

[0131] Aspect 3 is a method according to any one of Aspects 1 and 2, further comprising: multiplexing UCI with PUSCH based on a first rule under a first condition, where the first condition is that the content of the UCI includes HARQ-ACK associated with multiple CORESET pool indexes of multiple groups or the UCI does not include HARQ-ACK; or multiplexing UCI with PUSCH based on a second rule under a second condition, where the second condition is that the content of the UCI includes HARQ-ACK associated with a single CORESET pool index.

[0132] Aspect 4 is a method according to any one of aspects 1-3, further comprising: UCI is multiplexed with PUSCHs from multiple overlapping PUSCHs based on a feedback mode.

[0133] Aspect 5 is a method according to any one of Aspects 1-4, further including: multiplexing UCI with PUSCH based on a first rule under a first condition, where the first condition is that the UE is configured with a joint ACK NACK feedback mode; or multiplexing UCI with PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK NACK feedback mode.

[0134] Aspect 6 is a method according to any one of aspects 1-5, further including: in the absence of a configured acknowledgment (ACK) or negative acknowledgment (NACK) feedback mode, the device also includes multiplexing UCI with PUSCH based on a first rule applied to a joint ACK NACK feedback mode, a second rule applied to a separate ACK NACK feedback mode, or one of a rule based on the type of UCI or the content of UCI.

[0135] Aspect 7 is a method according to any one of aspects 1-6, further comprising: UCI is multiplexed with PUSCHs from multiple overlapping PUSCHs based on a carrier configuration for a CC associated with the UCI.

[0136] Aspect 8 is a method according to any one of Aspects 1-7, further comprising: multiplexing UCI with PUSCH based on a first rule under a first condition, where the first condition is that the CC associated with the UCI is configured with a single CORESET pool index, a single TAG, or a PUCCH resource for a single TCI state; or multiplexing UCI with PUSCH based on a second rule under a second condition, where the second condition is that the CC associated with the UCI is configured with multiple CORESET pool indexes, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

[0137] Aspect 9 is a method according to any one of aspects 1-8, further including a first PUSCH in a plurality of overlapping PUSCHs including AP-CSI, further including: multiplexing UCI on the first PUSCH based on the first PUSCH including AP-CSI and being associated with the same CORESET pool index as the UCI; discarding UCI based on the first PUSCH being associated with a CORESET pool index different from the UCI; or identifying an error condition based on the overlap in the time domain of the UCI with the first PUSCH having a CORESET pool index different from the UCI.

[0138] Aspect 10 is a method according to any one of Aspects 1-9, further including a first PUSCH among multiple overlapping PUSCHs including AP-CSI, and further including: further multiplexing UCI on the first PUSCH based on the first PUSCH including AP-CSI and being associated with a CORESET pool index different from UCI.

[0139] Aspect 11 is a method according to any one of aspects 1-10, further comprising at least two PUSCHs of the multiple overlapping PUSCHs including AP-CSI, and further comprising: multiplexing UCI on a PUSCH associated with the same CORESET pool index as the UCI; or multiplexing UCI on a PUSCH associated with a defined CORESET pool index.

[0140] Aspect 12 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1-11.

[0141] Aspect 13 is an apparatus for wireless communication at a UE, the apparatus comprising means for implementing any one of aspects 1-11.

[0142] Aspect 14 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1-11.

[0143] Aspect 15 is a method of wireless communication at a network node, the method comprising: providing a configuration of multiple DCI operations for a UE, the configuration comprising an association with a CORESET configured for the UE, the association comprising a CORESET pool index 0 or a lack of a CORESET pool index and a CORESET pool index 1; and receiving UCI multiplexed with a PUSCH from a plurality of overlapping PUSCHs, the plurality of overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping with the UCI in the time domain, the UCI being multiplexed with the PUSCH based on at least one of a type of UCI, a content of the UCI, a feedback mode, or a carrier configuration.

[0144] Aspect 16 is a method according to aspect 15, further comprising: UCI is multiplexed with PUSCHs from multiple overlapping PUSCHs based on the type of UCI or the content of UCI.

[0145] Aspect 17 is a method according to any one of aspects 15 and 16, further comprising one of the following: UCI is multiplexed with PUSCH based on a first rule under a first condition, the first condition being that the content of UCI includes HARQ-ACK associated with multiple CORESET pool indexes of multiple groups or the UCI does not include HARQ-ACK; or UCI is multiplexed with PUSCH based on a second rule under a second condition, the second condition being that the content of UCI includes HARQ-ACK associated with a single CORESET pool index.

[0146] Aspect 18 is a method according to any one of aspects 15-17, further comprising: UCI is multiplexed with PUSCHs from multiple overlapping PUSCHs based on the feedback mode.

[0147] Aspect 19 is a method according to any one of aspects 15-18, further including one of the following: UCI is multiplexed with PUSCH based on a first rule under a first condition, and the first condition is that the UE is configured with a joint ACK NACK feedback mode; or UCI is multiplexed with PUSCH based on a second rule under a second condition, and the UE is configured with a separate ACK NACK feedback mode.

[0148] Aspect 20 is a method according to any one of aspects 15-19, further comprising: not configuring an ACK NACK feedback mode, and wherein the UCI is multiplexed with the PUSCH based on one of a first rule applied to the joint ACK NACK feedback mode, a second rule applied to the individual ACK NACK feedback mode, or a rule based on the type of UCI or the content of the UCI.

[0149] Aspect 21 is a method according to any one of aspects 15-20, further comprising: UCI is multiplexed with PUSCH from multiple overlapping PUSCHs based on a carrier configuration for a CC associated with the UCI.

[0150] Aspect 22 is a method according to any one of aspects 15-21, further comprising one of the following: UCI is multiplexed with PUSCH based on a first rule under a first condition, where the first condition is that the CC associated with the UCI is configured with a single CORESET pool index, a single TAG, or a PUCCH resource for a single TCI state; or UCI is multiplexed with PUSCH based on a second rule under a second condition, where the second condition is that the CC associated with the UCI is configured with multiple CORESET pool indices, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

[0151] Aspect 23 is a method according to any one of aspects 15-22, further comprising: a first PUSCH in a plurality of overlapping PUSCHs includes AP-CSI, wherein one of the following: UCI is multiplexed on the first PUSCH based on the first PUSCH including AP-CSI and being associated with the same CORESET pool index as the UCI; or avoiding scheduling the UCI to overlap with the first PUSCH having a different CORESET pool index than the UCI in the time domain.

[0152] Aspect 24 is a method according to any one of aspects 15-23, further comprising: a first PUSCH in the multiple overlapping PUSCHs includes AP-CSI, wherein UCI is further multiplexed on the first PUSCH based on the first PUSCH including AP-CSI and being associated with a CORESET pool index different from the UCI.

[0153] Aspect 25 is a method according to any one of aspects 15-24, further comprising: at least two PUSCHs of the multiple overlapping PUSCHs include AP-CSI, wherein one of the following items: UCI is multiplexed on a PUSCH associated with the same CORESET pool index as the UCI; or UCI is multiplexed on a PUSCH associated with a defined CORESET pool index.

[0154] Aspect 26 is an apparatus for wireless communication at a network entity, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 15-25.

[0155] Aspect 27 is an apparatus for wireless communication at a network entity, the apparatus comprising means for implementing any one of aspects 15-25.

[0156] Aspect 28 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any of aspects 15-25.

[0157] Aspect 29 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory, the at least one processor configured to implement any one of aspects 1-11.

[0158] Aspect 30 is an apparatus for wireless communication at a network entity, the apparatus comprising at least one processor coupled to a memory, the at least one processor configured to implement any of aspects 15-25.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: receiving a configuration for a plurality of downlink control information (DCI) operations, the configuration comprising an association with a control resource set (CORESET) configured for the UE, the association comprising: CORESET pool index 0 or missing CORESET pool index, and CORESET pool index 1; as well as Transmitting uplink control information (UCI) multiplexed with physical uplink shared channels (PUSCHs) from a plurality of overlapping PUSCHs, the plurality of overlapping PUSCHs overlapping in the time domain on one or more carriers and overlapping in the time domain with the UCI, the UCI being multiplexed with the PUSCH based on at least one of a type of the UCI, content of the UCI, a feedback mode, or a carrier configuration.

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

3. The device according to claim 1, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the type of the UCI or the content of the UCI.

4. The device according to claim 3, wherein The at least one processor is configured to: multiplexing the UCI with the PUSCH based on a first rule under a first condition, the first condition being that the content of the UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with a plurality of CORESET pool indexes of a plurality of groups or the UCI does not include the HARQ-ACK; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, wherein the second condition is that the content of the UCI includes the HARQ-ACK associated with a single CORESET pool index.

5. The device according to claim 1, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the feedback mode.

6. The device according to claim 5, wherein The at least one processor is configured to: multiplexing the UCI with the PUSCH based on a first rule under a first condition, wherein the first condition is that the UE is configured with a joint acknowledgement (ACK) negative acknowledgement (NACK) feedback mode; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK NACK feedback mode.

7. The device according to claim 5, wherein In the absence of a configured acknowledgement (ACK) or negative acknowledgement (NACK) feedback mode, the at least one processor is further configured to multiplex the UCI with the PUSCH based on one of: The first rule applied to the joint ACK NACK feedback mode is, The second rule applies to the separate ACK NACK feedback mode, or A rule based on the type of the UCI or the content of the UCI.

8. The device according to claim 1, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the carrier configuration for a component carrier (CC) associated with the UCI.

9. The device according to claim 8, wherein The at least one processor is configured to: multiplexing the UCI with the PUSCH based on a first rule under a first condition, the first condition being that the CC associated with the UCI is configured with a physical uplink control channel (PUCCH) resource having a single CORESET pool index, a single timing advance group (TAG), or a single transmission configuration indicator (TCI) state; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the CC associated with the UCI is configured with multiple CORESET pool indexes, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

10. The device according to claim 1, wherein A first PUSCH of the plurality of overlapping PUSCHs includes aperiodic channel state information (AP-CSI), wherein the at least one processor is configured to: further based on the first PUSCH including the AP-CSI and being associated with the same CORESET pool index as the UCI, multiplexing the UCI on the first PUSCH; discarding the UCI based on that the first PUSCH is associated with a CORESET pool index different from that of the UCI; or An error condition is identified based on an overlap of the UCI with the first PUSCH having a different CORESET pool index than the UCI in the time domain.

11. The device according to claim 1, wherein A first PUSCH of the plurality of overlapping PUSCHs includes aperiodic channel state information (AP-CSI), wherein the at least one processor is configured to: Further based on the first PUSCH including the AP-CSI and being associated with a CORESET pool index different from the UCI, the UCI is multiplexed on the first PUSCH.

12. The device according to claim 1, wherein At least two PUSCHs of the plurality of overlapping PUSCHs include aperiodic channel state information (AP-CSI), wherein the at least one processor is configured to: multiplexing the UCI on the PUSCH associated with the same CORESET pool index as the UCI; or The UCI is multiplexed on the PUSCH associated with a defined CORESET pool index.

13. A method of wireless communication at a UE, comprising: receiving a configuration for a plurality of downlink control information (DCI) operations, the configuration comprising an association with a control resource set (CORESET) configured for the UE, the association comprising: CORESET pool index 0 or missing CORESET pool index, and CORESET pool index 1; and Transmitting uplink control information (UCI) multiplexed with physical uplink shared channels (PUSCHs) from a plurality of overlapping PUSCHs, the plurality of overlapping PUSCHs overlapping in the time domain on the same carrier and overlapping in the time domain with the UCI, the UCI being multiplexed with the PUSCH based on at least one of a type of the UCI, content of the UCI, a feedback mode, or a carrier configuration.

14. The method according to claim 13, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the type of the UCI or the content of the UCI, the method further comprising: multiplexing the UCI with the PUSCH based on a first rule under a first condition, the first condition being that the content of the UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with a plurality of CORESET pool indexes of a plurality of groups or the UCI does not include the HARQ-ACK; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, wherein the second condition is that the content of the UCI includes the HARQ-ACK associated with a single CORESET pool index.

15. The method according to claim 13, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the feedback mode, further comprising: multiplexing the UCI with the PUSCH based on a first rule under a first condition, wherein the first condition is that the UE is configured with a joint acknowledgement (ACK) negative acknowledgement (NACK) feedback mode; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK NACK feedback mode.

16. An apparatus for wireless communication at a network node, comprising: Memory; as well as at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: A configuration of multiple downlink control information (DCI) operations for a user equipment (UE) is provided, the configuration including an association with a control resource set (CORESET) configured for the UE, the association including: CORESET pool index 0 or missing CORESET pool index, and CORESET pool index 1; as well as Receiving uplink control information (UCI) multiplexed with physical uplink shared channels (PUSCHs) from a plurality of overlapping PUSCHs that overlap in the time domain on the same carrier and overlap with the UCI in the time domain, the UCI being multiplexed with the PUSCH based on at least one of a type of the UCI, content of the UCI, a feedback mode, or a carrier configuration.

17. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor.

18. The device according to claim 16, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the type of the UCI or the content of the UCI.

19. The device according to claim 18, wherein One of the following: The UCI is multiplexed with the PUSCH based on a first rule under a first condition, wherein the first condition is that the content of the UCI includes a hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with a plurality of CORESET pool indexes of a plurality of groups or the UCI does not include the HARQ-ACK; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the content of the UCI includes the HARQ-ACK associated with a single CORESET pool index.

20. The apparatus according to claim 16, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the feedback mode.

21. The device according to claim 20, wherein One of the following: The UCI is multiplexed with the PUSCH based on a first rule under a first condition, where the first condition is that the UE is configured with a joint acknowledgement (ACK) negative acknowledgement (NACK) feedback mode; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK NACK feedback mode.

22. The device according to claim 20, wherein An acknowledgement (ACK) or negative acknowledgement (NACK) feedback mode is not configured, and wherein the UCI is multiplexed with the PUSCH based on one of the following: The first rule applied to the joint ACK NACK feedback mode is, The second rule applies to the separate ACK NACK feedback mode, or A rule based on the type of the UCI or the content of the UCI.

23. The apparatus according to claim 16, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the carrier configuration for a component carrier (CC) associated with the UCI.

24. The device according to claim 23, wherein One of the following: The UCI is multiplexed with the PUSCH based on a first rule under a first condition, wherein the first condition is that the CC associated with the UCI is configured with a single CORESET pool index, a single timing advance group (TAG), or a physical uplink control channel (PUCCH) resource for a single transmission configuration indicator (TCI) state; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the CC associated with the UCI is configured with multiple CORESET pool indexes, multiple TAGs, or multiple PUCCH resources for multiple TCI states.

25. The apparatus according to claim 16, wherein A first PUSCH of the plurality of overlapping PUSCHs includes aperiodic channel state information (AP-CSI), wherein one of: The UCI is multiplexed on the first PUSCH further based on the first PUSCH including the AP-CSI and being associated with the same CORESET pool index as the UCI; or Avoid scheduling the UCI to overlap with the first PUSCH having a CORESET pool index different from that of the UCI in the time domain.

26. The apparatus according to claim 16, wherein A first PUSCH of the multiple overlapping PUSCHs includes aperiodic channel state information (AP-CSI), wherein the UCI is multiplexed on the first PUSCH further based on the first PUSCH including the AP-CSI and being associated with a different CORESET pool index than the UCI.

27. The apparatus according to claim 16, wherein At least two PUSCHs of the plurality of overlapping PUSCHs include aperiodic channel state information (AP-CSI), wherein one of the following: The UCI is multiplexed on the PUSCH associated with the same CORESET pool index as the UCI; or The UCI is multiplexed on the PUSCH associated with a defined CORESET pool index.

28. A method of wireless communication at a network node, comprising: A configuration of multiple downlink control information (DCI) operations for a user equipment (UE) is provided, the configuration including an association with a control resource set (CORESET) configured for the UE, the association including: CORESET pool index 0 or missing CORESET pool index, and CORESET pool index 1; and Receiving uplink control information (UCI) multiplexed with physical uplink shared channels (PUSCHs) from a plurality of overlapping PUSCHs that overlap in the time domain on the same carrier and overlap with the UCI in the time domain, the UCI being multiplexed with the PUSCH based on at least one of a type of the UCI, content of the UCI, a feedback mode, or a carrier configuration.

29. The method according to claim 28, wherein The UCI is multiplexed with the PUSCH from the plurality of overlapping PUSCHs based on the type of the UCI or the content of the UCI, wherein one of the following: The UCI is multiplexed with the PUSCH based on a first rule under a first condition, wherein the first condition is that the content of the UCI includes a hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with a plurality of CORESET pool indexes of a plurality of groups or the UCI does not include the HARQ-ACK; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the content of the UCI includes the HARQ-ACK associated with a single CORESET pool index.

30. The method of claim 28, wherein The UCI is multiplexed with a PUSCH from the plurality of overlapping PUSCHs based on the feedback mode, wherein one of the following: The UCI is multiplexed with the PUSCH based on a first rule under a first condition, where the first condition is that the UE is configured with a joint acknowledgement (ACK) negative acknowledgement (NACK) feedback mode; or The UCI is multiplexed with the PUSCH based on a second rule under a second condition, where the second condition is that the UE is configured with a separate ACK NACK feedback mode.

Images