Transmission for overlapping physical uplink control channel and physical uplink shared channel

By determining overlapping PUCCHs with different control resource set pool indices and performing UCI multiplexing, the method optimizes data transmission in wireless communication systems by addressing resource conflicts and enhancing efficiency.

CN119096630APending Publication Date: 2024-12-06QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095069.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-28
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing overlapping physical uplink control channels (PUCCH) and physical uplink shared channels (PUSCH) due to resource conflicts, leading to inefficiencies in data transmission.

Method used

The method involves determining overlapping PUCCHs with different control resource set pool indices and performing a UCI multiplexing procedure to allow simultaneous transmission or partial discarding of channels to optimize data communication.

Benefits of technology

This approach enhances data transmission efficiency by enabling simultaneous or staggered transmission of overlapping channels, reducing resource conflicts and improving overall communication performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096630A_ABST
    Figure CN119096630A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can determine that a first physical uplink control channel (PUCCH) at least partially overlaps a second PUCCH, and determine that the first PUCCH and the second PUCCH can be simultaneously transmitted. The UE can also determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs). The UE can transmit communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based, at least in part, on at least one of: multiplexing uplink control information with at least one PUSCH, or discarding communications associated with at least one of the first PUCCH, the second PUCCH, or the one or more PUSCHs. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for transmissions for overlapping physical uplink control channels and physical uplink shared channels. Background Art

[0002] 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 that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In order to be able to understand the above features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0006] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0007] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0008] Figure 3 is a diagram illustrating an example of an open radio access network architecture according to the present disclosure.

[0009] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0010] Figure 5 is a diagram illustrating an example of uplink control information multiplexing according to the present disclosure.

[0011] Figure 6 2 is a diagram illustrating an example of performing transmission and reception point differentiation at a UE based at least in part on a control resource set pool index according to the present disclosure.

[0012] Figures 7 to 12 is a diagram illustrating an example of transmission using overlapping physical uplink control channels and physical uplink shared channels according to the present disclosure.

[0013] Fig.13 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0014] Fig.14 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0015] Figure 15 to Figure 16 is a diagram of an example apparatus for wireless communications according to the present disclosure. Summary of the invention

[0016] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include determining that a first physical uplink control channel (PUCCH) at least partially overlaps with a second PUCCH in a time domain, and determining that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The method may include determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain. The method may include sending communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0017] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include determining that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determining that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The method may include determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The method may include receiving a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0018] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to determine that a first PUCCH at least partially overlaps with a second PUCCH in a time domain, and determine that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The one or more processors may be configured to determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The one or more processors may be configured to send communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0019] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to determine that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determine that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The one or more processors may be configured to determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The one or more processors may be configured to receive a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to determine that a first PUCCH at least partially overlaps with a second PUCCH in a time domain, and determine that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The instruction set, when executed by one or more processors of the UE, may cause the UE to determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The instruction set, when executed by one or more processors of the UE, may cause the UE to send communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to determine that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determine that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for determining that a first PUCCH at least partially overlaps with a second PUCCH in a time domain, and determining that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The apparatus may include means for determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The apparatus may include means for sending communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for determining that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determining that the UE is capable of simultaneously sending the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering a UCI multiplexing procedure for overlapping PUCCHs. The apparatus may include a component for determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The apparatus may include a component for receiving a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0024] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.

[0025] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0026] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). In addition, although the base station 110 is in Figure 1 10 is shown as an integral unit, but aspects of the present disclosure are not limited thereto. In some aspects, the functionality of base station 110 can be decomposed according to an open radio access network (O-RAN) architecture, etc., which is combined with Figure 3 Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0031] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0032] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0033] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, etc.

[0034] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0036] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a car component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0037] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0042] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term 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 explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may determine that a first physical uplink control channel (PUCCH) at least partially overlaps with a second PUCCH in the time domain, and determine that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein the first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, the second PUCCH includes second UCI associated with a second CORESET pool index, and determine that the first PUCCH and the second PUCCH can be transmitted simultaneously after performing a UCI multiplexing procedure for overlapping PUCCHs. The communication manager 140 may include: determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; and sending communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] In some aspects, a network entity described elsewhere herein may correspond to or may be associated with a base station 110. The network entity may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may determine that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determine that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering a UCI multiplexing procedure for overlapping PUCCHs; determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain; and receive a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1Other examples can be found in the Figure 1 The examples described are different.

[0046] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0047] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 7 to 16 ) or any aspects of any of the methods described herein.

[0052] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 7 to 16 ) or any aspects of any of the methods described herein.

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the may perform one or more techniques associated with transmission using overlapping PUCCH and PUSCH, as described in more detail elsewhere herein. In some aspects, the network entity described herein is Figure 2 The base station 110 shown is included in the base station 110, or includes one or more components of the base station 110. The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Fig.13 The process of 1300 Fig.14 1400 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig.13 The process of 1300 Fig.14 The process 1400 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0054] In some aspects, UE 120 includes: a component for determining that a first PUCCH at least partially overlaps with a second PUCCH in the time domain, and determining that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs; and / or a component for determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain; and / or a component for sending communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of the following: a component for multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or a component for discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs. Means for UE 120 to perform operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0055] In some aspects, a network entity described elsewhere herein includes: a component for determining that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determining that the UE is capable of simultaneously sending the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering a UCI multiplexing procedure for overlapping PUCCHs; and / or a component for determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain; and / or a component for receiving communications from the UE based at least in part on the determination, wherein the communications include at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0056] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.

[0058] Figure 3 3 is a diagram illustrating an example 300 of an O-RAN architecture according to the present disclosure. Figure 3As shown, the O-RAN architecture may include a centralized unit (CU) 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links. The DUs 330 may each communicate with one or more radio units (RUs) 340 via corresponding fronthaul links, and the RUs 340 may each communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DU 330 and the RU 340 may also be referred to as O-RAN DU (O-DU) 330 and O-RAN RU (O-RU) 340, respectively.

[0059] In some aspects, the DU 330 and the RU 340 may be implemented according to a functional split architecture, wherein the functionality of a base station 110 (e.g., an eNB or gNB) is provided by the DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, the base station 110 may include a DU 330 and one or more RUs 340, which may be co-located or geographically distributed. In some aspects, the DU 330 and associated RUs 340 may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0060] Thus, the DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, in some aspects, the DU 330 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. Based at least in part on the lower layer functional split, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering). Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture.

[0061] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.

[0062] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown, the downlink channel and the downlink reference signal may carry information from base station 110 to UE 120 , and the uplink channel and the uplink reference signal may carry information from UE 120 to base station 110 .

[0063] As shown in the figure, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown in the figure, the uplink channel may include a PUCCH carrying UCI, a PUSCH carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, the UE 120 may send an acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH. In addition, in some aspects, the UE 120 may send channel state information (CSI) (such as a CSI report) and / or a scheduling request (SR) in the UCI on the PUCCH and / or PUSCH.

[0064] As further shown in the figure, the downlink reference signal may include a synchronization signal block (SSB), a CSI reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0065] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the base station 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0066] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other things. The base station 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP, among other things, to the base station 110 (e.g., in a CSI report). The base station 110 may use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0067] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and can be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0068] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0069] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the base station 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may require detecting downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive the PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the base station 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0070] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The base station 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured usages, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The base station 110 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0071] In some aspects, one or more channels and / or one or more transmissions in the downlink or uplink may overlap with each other. If the base station 110 or the UE 120 cannot transmit one or more channels and / or one or more transmissions simultaneously, the corresponding entity may multiplex the communications into a single channel or resolve which transmissions should be communicated and which should be discarded. Figure 5 Aspects of overlapping channels and transmissions are described in more detail.

[0072] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.

[0073] Figure 5 is a diagram illustrating an example 500 of UCI multiplexing according to the present disclosure.

[0074] exist Figure 5In the depicted example, multiple PUCCHs and PUSCHs are scheduled for use by a UE (e.g., UE 120), with at least some of the PUCCHs and PUSCHs overlapping in the time domain. For example, as indicated at reference numeral 505, UE 120 may be scheduled with four PUCCHs (indexed as PUCCH1, PUCCH2, PUCCH3, and PUCCH4 in this example) and two PUSCHs (indexed as PUSCH1 and PUSCH2 in this example). Each of these PUCCHs may be scheduled to carry UCI, such as hybrid automatic repeat request (HARQ) feedback (e.g., HARQ-ACK or HARQ-NACK), CSI (e.g., CSI report), and / or SR. More specifically, in the depicted example, PUCCH1 is scheduled to carry a first UCI (indexed as UCI1) including a first CSI (indexed as CSI1), PUCCH2 is scheduled to carry a second UCI (indexed as UCI2) including a second CSI (indexed as CSI2), PUCCH3 is scheduled to carry a third UCI (indexed as UCI3) including HARQ-ACK feedback, and PUCCH4 is scheduled to carry a fourth UCI (indexed as UCI4) including SR.

[0075] As shown, some of these channels overlap with other channels. More specifically, PUCCH1 and PUCCH2 partially overlap each other and further overlap with PUSCH1, PUCCH2 partially overlaps with PUSCH2, and PUCCH4 does not overlap with any other channel. In such aspects, UE 120 may not be able to send overlapping channels at the same time, but may be able to multiplex UCI in one or more PUCCHs and / or PUSCHs to send all scheduled communications. More specifically, UE 120 may first parse the overlapping PUCCH resources for UCI multiplexing. For example, PUCCH1 overlaps at least partially with PUCCH3, and therefore UE 120 may be able to multiplex associated UCI (e.g., UCI1 and UCI3, respectively) in a single PUCCH. Therefore, as shown in reference numeral 510, UCI1 and UCI3 have been multiplexed into the fifth PUCCH indexed as PUCCH5. PUCCH5 may be determined based at least in part on the total payload size of UCI1 and UCI3. And PUCCH 5 may be the same or a different PUCCH resource as one of PUCCH 1 and PUCCH 3. More specifically, in the depicted example, PUCCH 5 may be based at least in part on resources associated with PUCCH 3. Furthermore, because UCI 1 has been multiplexed in PUCCH 5, a PUCCH (e.g., PUCCH 1) that was originally scheduled to carry UCI 1 may not be transmitted (e.g., PUCCH 1) (e.g., in FIG. 1 ). Figure 5Indicated by “Not Txd” in the

[0076] Once the UE 120 has resolved the overlapping PUCCH resources for UCI multiplexing, the remaining PUCCHs with UCI will be non-overlapping, as shown in reference numeral 510. However, one or more PUCCHs may still overlap with one or more PUSCHs. More specifically, as shown in reference numeral 510, PUCCH5 (e.g., a PUCCH scheduled to carry UCI1 and UCI3) partially overlaps with PUSCH1, and PUCCH2 (e.g., a PUCCH scheduled to carry UCI2) partially overlaps with PUSCH2. In such a case, the UE 120 may multiplex the UCI from the partially overlapping PUCCHs in the corresponding PUSCH, and thus the PUCCH is not sent. More specifically, as shown in reference numeral 515, UCI1 and UCI3 may be multiplexed in PUSCH2, and UCI2 may be multiplexed in PUSCH2, and thus PUCCH5 and PUCCH2 are not sent. In some aspects, the UE 120 may be able to multiplex UCI associated with partially overlapping PUCCH and PUSCH (e.g., PUCCH5 and PUSCH2, or PUCCH2 and PUSCH2) when the partially overlapping PUCCH and PUSCH are in the same component carrier, and when the partially overlapping PUCCH and PUSCH are in different component carriers. In addition, in some aspects, the network entity may signal certain parameters to the UE 120 to enable multiplexing of UCI in PUSCH. For example, a beta offset signaled in an uplink grant (e.g., signaled in a DCI format 0_1 ​​or 0_2 communication) and / or a parameter configured via RRC communication may be used to control rate matching behavior (e.g., may be used by the UE 120 to determine how to multiplex PUCCH on PUSCH, such as determining the number of resources that a UCI payload may occupy on PUSCH, etc.). In some aspects, if at least one of the partially overlapping PUCCH or PUSCH is a dynamically scheduled channel (e.g., a channel scheduled by DCI), then when multiplexing UCI in PUCCH or PUSCH, UE 120 can meet the joint timeline rules specified in the wireless communication standard, such as the joint timeline rules specified in section 9.2.5 of 3GPP technical specification 38.213. Therefore, as shown by reference numeral 515, UE 120 may not have overlapping PUCCH and PUSCH, and thus may send the remaining channels accordingly (e.g., UE 120 may send PUSCH1 including UCI1 and UCI3, may send PUSCH2 including UCI2, and may send PUCCH4 including UCI4).

[0077] In some other aspects, the UE 120 may be capable of certain simultaneous PUCCH and PUSCH transmissions. For example, if the PUCCH and PUSCH are on different cells in inter-band carrier aggregation, and the PUCCH and PUSCH are associated with different physical layer priority values ​​(e.g., one of the PUCCH and PUSCH is associated with high priority communications, and the other of the PUCCH and PUSCH is associated with low priority communications), the UE 120 may be capable of simultaneous PUCCH and PUSCH transmissions. However, in such aspects, the UE 120 may not be capable of simultaneous transmissions if the PUCCH and PUSCH are on the same cell, if the PUCCH and PUSCH are on different CCs in intra-band carrier aggregation (CA), or if the PUCCH and PUSCH are on different CCs in inter-band CA but are associated with the same physical layer priority value. In aspects where PUSCH may be transmitted concurrently with PUCCH (e.g., when PUCCH and PUSCH are on different cells in inter-band carrier aggregation and are associated with different physical layer priority values), PUSCH may be excluded from overlapping channels for UCI multiplexing and / or prioritization rules (such as the UCI multiplexing rules described above in conjunction with reference numerals 505, 510, and 515), and PUSCH may not be subject to intra-UE multiplexing timeline requirements.

[0078] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.

[0079] Figure 6 600 is a diagram illustrating an example of TRP differentiation at a UE based at least in part on a CORESET pool index according to the present disclosure. Figure 5 The PUCCH and PUSCH described herein may be associated with different TRPs. In some aspects, the UE 120 may use a CORESET pool index (or CORESETPoolIndex) value to identify a TRP associated with an uplink grant received on the PDCCH (e.g., to identify a TRP associated with the PUCCH and / or PUSCH).

[0080] A CORESET may refer to a control region that is structured to support efficient use of resources, such as by flexible configuration or reconfiguration of resources for one or more PDCCHs associated with a UE. In some aspects, a CORESET may occupy the first symbol of an OFDM slot, the first two symbols of an OFDM slot, or the first three symbols of an OFDM slot. Thus, a CORESET may include multiple resource blocks (RBs) in the frequency domain, and one, two, or three symbols in the time domain. In 5G, the number of resources included in a CORESET may be flexibly configured, such as by using RRC signaling to indicate the frequency domain region (e.g., the number of resource blocks) or the time domain region (e.g., the number of symbols) of the CORESET.

[0081] like Figure 6 As shown, UE 120 may be configured to have multiple CORESETs in a given bandwidth portion of a serving cell. Each CORESET configured for UE 120 may be associated with a CORESET identifier (CORESET ID). For example, a first CORESET configured for UE 120 may be associated with CORESET ID 1, a second CORESET configured for UE 120 may be associated with CORESET ID 2, a third CORESET configured for UE 120 may be associated with CORESET ID 3, and a fourth CORESET configured for UE 120 may be associated with CORESET ID 4.

[0082] like Figure 6 As further shown, two or more (e.g., up to five) CORESETs may be grouped into CORESET pools. Each CORESET pool may be associated with a CORESET pool index. For example, CORESET ID 1 and CORESET ID 2 may be grouped into CORESET pool index 0, and CORESET ID 3 and CORESET ID 4 may be grouped into CORESET pool index 1. In a multi-TRP configuration, each CORESET pool index may be associated with a particular TRP 605. For example, Figure 6As shown, the first TRP 605 (TRP A) may be associated with CORESET pool index 0, and the second TRP 605 (TRP B) may be associated with CORESET pool index 1. The UE 120 may be configured with information identifying the association between the TRP and the CORESET pool index assigned to the TRP via a higher layer parameter, such as PDCCH-Config. Thus, the UE may identify the TRP that sent the DCI uplink grant by determining the CORESET ID of the CORESET in which the PDCCH carrying the DCI uplink grant was sent, determining the CORESET pool index associated with the CORESET pool in which the CORESET ID is included, and identifying the TRP associated with the CORESET pool index. In some aspects, the CORESET pool index of the CORESET in which the DCI was received may be used by the UE 120 for different purposes, such as for providing HARQ-ACK feedback.

[0083] In some aspects, UE 120 may be configured to send simultaneous PUCCH (e.g., at least partially overlapping PUCCH) associated with DCI received from different TRPs (e.g., DCI associated with different CORESET pool indices, sometimes referred to as a multi-DCI scenario). For example, UE 120 may be able to send at least partially overlapping PUCCH in one CC for providing separate HARQ feedback, etc. In such aspects, UE 120 may be configured with a feedback mode parameter (sometimes referred to as ackNackFeedbackMode) indicating that UE 120 may send at least partially overlapping PUCCH for providing separate HARQ feedback (e.g., UE 120 may be configured with ackNackFeedbackMode as "separate"). However, UE 120 may not be able to send overlapping PUCCH simultaneously with PUSCH.

[0084] For example, UE 120 may be scheduled with two time-domain overlapping PUCCHs (e.g., PUCCH1 and PUCCH2), which may be transmitted simultaneously according to a UCI multiplexing rule for overlapping PUCCH resources (such as the above-described rule). For example, UE 120 may be configured with a feedback mode parameter (e.g., ackNackFeedbackMode) indicating that PUCCH1 and PUCCH2 may be transmitted simultaneously for providing separate HARQ feedback, etc. In such aspects, the PUCCHs may be associated with different TRPs or CORESET pool indexes. For example, PUCCH1 may include a first HARQ feedback communication (e.g., HARQ-ACK1) and may be associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), and PUCCH2 may include a second HARQ feedback communication (e.g., HARQ-ACK2) and may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1). In addition, the PUSCH may at least partially overlap with both PUCCH1 and PUCCH2, and may be associated with the same CORESET pool index (e.g., CORESETPoolIndex 0) as PUCCH1. In such aspects, the UE 120 may be associated with the CORESETPoolIndex 0 as described above. Figure 5 The described UCI multiplexing rules multiplex the UCI associated with PUCCH1 (e.g., HARQ-ACK1) on the PUSCH because PUCCH1 and PUSCH are associated with the same CORESET pool index. However, the UE 120 may discard the UCI associated with PUCCH2 (e.g., HARQ-ACK2) because the UE 120 may not be able to perform PUCCH and PUSCH transmissions simultaneously unless the PUCCH and PUSCH meet the above combined conditions. Figure 5 Certain conditions described (e.g., when PUCCH and PUSCH are on different cells in inter-band carrier aggregation and are associated with different physical layer priority values). This may be undesirable because the UCI associated with PUCCH2 (e.g., HARQ-ACK2) may be more important than communications associated with PUSCH. Therefore, when the overlapping PUCCH also overlaps with PUSCH, UE 120 may discard certain high priority communications (e.g., in the above example, UE 120 may discard PUCCH2) and / or may delay the transmission of certain high priority communications (e.g., UE 120 may delay the transmission of communications associated with the overlapping PUCCH or may delay communications associated with PUSCH). This may result in unreliable wireless communications, reduced throughput, increased latency, and overall inefficient use of network resources.

[0085] Some techniques and apparatuses described herein enable enhanced transmission determination when two or more time-domain overlapping PUCCHs overlap with one or more PUSCHs, thereby maintaining high priority communications, etc. In some aspects, a UE (e.g., UE 120) may determine that two time-domain overlapping PUCCH resources may be transmitted simultaneously with a first PUCCH (including one or more UCIs (UCI1) associated with a first CORESET pool index) in the two time-domain overlapping PUCCH resources and with a second PUCCH (including one or more UCIs associated with a second CORESET pool index) in the two time-domain overlapping PUCCH resources. In some aspects, the first PUCCH and the second PUCCH may be determined after applying a UCI multiplexing procedure for overlapping PUCCHs. The UE may also determine that one or more PUSCHs overlap with at least one of the PUCCHs, and the UE may therefore determine whether to multiplex the UCI with the one or more PUSCHs, or whether to discard the UCI or the one or more PUSCHs. Thus, UE 120 may maintain certain high priority communications when the overlapping PUCCH also overlaps with the PUSCH, resulting in reliable wireless communications, increased throughput, reduced latency, and overall efficient use of network resources.

[0086] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.

[0087] Figure 7 is a diagram illustrating an example 700 of transmission using overlapping PUCCH and PUSCH according to the present disclosure.

[0088] exist Figure 7 In the example shown, UE 120 may determine two PUCCH resources that overlap in the time domain (in Figure 7 1 and PUCCH2) may be transmitted simultaneously in a CC or cell (such as in a primary cell (PCell), a PUCCH secondary cell (PUCCH-SCell), etc.). For example, UE 120 may transmit the PUCCH information based at least in part on the above in combination with Figures 5 and 6 The rules described herein determine that PUCCH1 and PUCCH2 may be sent simultaneously in a CC. More specifically, in some aspects, UE 120 may determine that PUCCH1 and PUCCH2 may be sent simultaneously in a CC based at least in part on UE 120 being configured with a feedback mode parameter (e.g., ackNackFeedbackMode), which indicates that UE 120 may send at least partially overlapping PUCCHs for providing separate HARQ feedback. In this regard, PUCCH1 may be communicated with a first HARQ feedback (in Figure 7 The UCI (shown as HARQ-ACK1) in Figure 7 1) and PUCCH2 may be associated with a second HARQ feedback communication (shown as UCI1 in Figure 7 The UCI (shown as HARQ-ACK2) in Figure 7 However, aspects of the present disclosure are not limited thereto, and in some other aspects, as an alternative or in addition to HARQ-ACK1, UCI1 may include CSI (e.g., CSI report), SR, or a combination thereof (e.g., HARQ-ACK1+CSI or HARQ-ACK1+SR or HARQ-ACK1+SR+CSI). Similarly, as an alternative or in addition to HARQ-ACK2, UCI2 may include CSI (e.g., CSI report), SR, or a combination thereof (e.g., HARQ-ACK2+CSI or HARQ-ACK2+SR or HARQ-ACK2+SR+CSI). And as described above in combination Figure 6 As described, PUCCH1 and / or UCI1 may be associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), and PUCCH2 and / or UCI2 may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1). In some aspects, the UCI multiplexing procedure for overlapping PUCCHs (such as in conjunction with Figure 5 PUCCH1 and PUCCH2 are then determined as described in the UCI multiplexing procedure for overlapping PUCCH, etc.

[0089] UE 120 may also determine that one or more PUSCHs (which may be in the same CC as PUCCH1 and PUCCH2, or which may be in a different CC than PUCCH1 and PUCCH2) at least partially overlap with at least one of PUCCH1 or PUCCH2. Figure 7 In the example, there are two PUSCHs shown as PUSCH1 and PUSCH2. In this example, the two PUSCHs at least partially overlap with at least one PUCCH. More specifically, as shown in reference numeral 705, both PUSCH1 and PUSCH2 at least partially overlap with both PUCCH1 and PUCCH2. Furthermore, in this example, PUSCH1 may be associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), and PUSCH2 may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1). In other words, in Figure 7In the example shown, one or more PUSCHs associated with CORESETPoolIndex 0 (eg, PUSCH1) overlap with PUCCH1, and one or more PUSCHs associated with CORESETPoolIndex 1 (eg, PUSCH2) overlap with PUCCH2.

[0090] In such aspects, as shown by reference numeral 710, the UE 120 may multiplex the UCI associated with PUCCH1 (eg, UCI1) on PUSCH1 and thus may not transmit PUCCH1 (eg, Figure 7 In some aspects, when multiple PUSCHs associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) overlap at least partially with PUCCH1, the UE 120 may select one of the PUSCHs (e.g., PUSCH1) for multiplexing UCI1 based at least in part on a prioritization rule. In some aspects, the prioritization rule may cause the UE 120 to first select the PUSCH associated with the lowest CC index and then (if more than one PUSCH is associated with the lowest CC index) select the PUSCH associated with the earliest start time. Similarly, the UE 120 may multiplex the UCI associated with PUCCH2 (e.g., UCI2) on PUSCH2 and may therefore not transmit PUCCH2. And, in a manner similar to that described above, when multiple PUSCHs associated with a second CORESET pool index (e.g., CORESETPoolIndex1) at least partially overlap with PUCCH2, UE 120 may select one of the PUSCHs (e.g., PUSCH2) for multiplexing UCI2 based at least in part on a prioritization rule, such as first selecting the PUSCH associated with the lowest CC index and then (if more than one PUSCH is associated with the lowest CC index) selecting the PUSCH associated with the earliest start time.

[0091] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.

[0092] Figure 8 is a diagram illustrating an example 800 of transmission using overlapping PUCCH and PUSCH according to the present disclosure.

[0093] exist Figure 8 In the depicted example, as shown by reference numeral 805, UE 120 may determine two PUCCH resources that overlap in the time domain (in Figure 8PUCCH1 and PUCCH2) can be combined with the above Figure 7 In this regard, however, the UE may determine that one or more PUSCHs associated with a first CORESET pool index (e.g., CORESETPoolIndex0) (which may be in the same CC as PUCCH1 and PUCCH2, or which may be in a different CC than PUCCH1 and PUCCH2) at least partially overlap with PUCCH1, but the PUSCH associated with the first CORESET pool index (e.g., CORESETPoolIndex 0) does not overlap with PUCCH2, and the PUSCH associated with the second CORESET pool index (e.g., CORESETPoolIndex 1) does not overlap with PUCCH2. For example, in Figure 8 In FIG, there is one PUSCH shown as PUSCH1, which is associated with the first CORESET pool index (e.g., CORESETPoolIndex 0) and at least partially overlaps with PUCCH1. However, the PUSCH associated with the first CORESET pool index (e.g., CORESETPoolIndex 0) or the second CORESET pool index (e.g., CORESETPoolIndex 1) does not overlap with PUSCH2.

[0094] In such aspects, as shown in reference numeral 810, the UE 120 may multiplex the UCI associated with PUCCH1 (e.g., UCI1) on PUSCH1 and may therefore not transmit PUCCH1. In some aspects, when multiple PUSCHs associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) overlap at least partially with PUCCH1, the UE 120 may select one of the PUSCHs (e.g., PUSCH1) for multiplexing UCI1 based at least in part on a prioritization rule, as described. More specifically, in some aspects, the prioritization rule may cause the UE 120 to first select the PUSCH associated with the lowest CC index and then (if more than one PUSCH is associated with the lowest CC index) select the PUSCH associated with the earliest start time. In addition, because there is no PUSCH that overlaps with PUCCH2, the UE 120 may transmit PUCCH2. More specifically, UE 120 may transmit UCI associated with PUCCH2 (eg, UCI2) on PUCCH2.

[0095] Although combined with the above Figure 8In the described examples, the PUSCH is described as being associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) and at least partially overlapping with PUCCH1, but in some other aspects, the PUSCH may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) and the UE 120 may act in a manner similar to that described above. For example, based at least in part on one or more PUSCHs being associated with the second CORESET pool index and overlapping with PUCCH2, the PUSCH associated with the first CORESET pool index not overlapping with PUCCH1, and the PUSCH associated with the second CORESET pool index not overlapping with PUCCH1, the UE 120 may multiplex UCI2 on the PUSCH and transmit UCI1 in PUCCH1.

[0096] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.

[0097] Fig. 9 and Fig.10 are diagrams illustrating examples 900 , 1000 of transmission using overlapping PUCCH and PUSCH according to the present disclosure.

[0098] exist Fig. 9 In the depicted example, as shown by reference numeral 905, UE 120 may determine two PUCCH resources that overlap in the time domain (in Fig. 9 PUCCH1 and PUCCH2) can be combined with the above Figure 7 and Figure 8 In one embodiment, the UE 120 may transmit simultaneously in a CC or cell in a manner similar to that described above. However, in this regard, the UE 120 may determine that one or more PUSCHs associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) (which may be in the same CC as PUCCH1 and PUCCH2, or which may be in a different CC than PUCCH1 and PUCCH2) at least partially overlap with PUCCH1, one or more PUSCHs associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) (which may be in the same CC as PUCCH1 and PUCCH2, or which may be in a different CC than PUCCH1 and PUCCH2) at least partially overlap with PUCCH2, but a PUSCH associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) does not overlap with PUCCH2. For example, in Fig. 9In FIG. 1 , there is one PUSCH shown as PUSCH1, which is associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) and at least partially overlaps with PUCCH1 and PUCCH2. However, a PUSCH associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) does not overlap with PUCCH2.

[0099] In such aspects, the UE 120 may drop one or more PUCCHs or PUSCHs (e.g., may not transmit communications associated with one or more PUCCHs or PUSCHs) in order to avoid simultaneous transmission of PUCCHs and PUSCHs. For example, as shown by reference numeral 910, the UE 120 may drop PUSCH1 (indicated using cross-hatching). More specifically, the UE 120 may drop all PUSCHs associated with the first CORESET pool index (e.g., CORESETPoolIndex 0, which is PUSCH1 in this example), and the UE 120 may transmit PUCCH1 and PUCCH2 simultaneously.

[0100] In some other aspects, UE 120 may drop one or more PUCCHs instead of one or more PUSCHs. Fig.10 As shown in the reference numeral 1005 in FIG. 1 , the UE 120 may determine that two time-domain overlapping PUCCH resources (e.g., PUCCH1 and PUCCH2) may be transmitted simultaneously in a manner similar to that described above in conjunction with reference numeral 905, one or more PUSCHs (e.g., PUSCH1) associated with the first CORESET pool index at least partially overlap with PUCCH1, one or more PUSCHs (e.g., PUSCH1) associated with the first CORESET pool index at least partially overlap with PUCCH2, and the PUSCH associated with the second CORESET pool index does not overlap with PUCCH2. However, in this regard, as shown in the reference numeral 1010, the UE 120 may drop PUCCH2 and thus drop UCI2 (e.g., PUCCH associated with the second CORESET pool index and associated UCI) instead of dropping PUSCH (e.g., PUSCH1, as shown in conjunction with FIG. 1 ). Fig. 9 As described), UCI1 can be multiplexed with one PUSCH of one or more PUSCHs associated with CORESETPoolIndex 0 (e.g., PUSCH1 in the depicted example).

[0101] In some other aspects, UE 120 may not expect to be scheduled with resources that result in two time-domain overlapping PUCCH resources (e.g., PUCCH1 and PUCCH2) being simultaneously transmitted, where one or more PUSCHs associated with a first CORESET pool index (e.g., PUSCH1) at least partially overlap with PUCCH1, one or more PUSCHs associated with a first CORESET pool index (e.g., PUSCH1) at least partially overlap with PUCCH2, and a PUSCH associated with a second CORESET pool index does not overlap with PUCCH2 (as described above). Thus, UE 120 may determine that an error condition has occurred, rather than dropping the PUSCH (e.g., in conjunction with Fig. 9 described) or discarding PUCCH (as combined with Fig.10 described).

[0102] In some aspects, the UE 120 may be configured to drop the PUSCH in the scenarios described in conjunction with reference numerals 905 and 1005 (e.g., in conjunction with Fig. 9 ), or dropping the PUCCH in the scenario described in conjunction with reference numerals 905 and 1005 (as described in conjunction with Fig.10 More specifically, a network entity (e.g., base station 110, CU 310, DU 330, RU 340, or a similar network entity) may send an RRC message, etc. to UE 120 to indicate whether to drop PUCCH or PUSCH in the scenario described in conjunction with reference numerals 905 and 1005. Additionally or alternatively, UE 120 may determine to drop PUSCH in the scenario described in conjunction with reference numerals 905 and 1005 (e.g., in conjunction with reference numerals 1005). Fig. 9 ), it can be determined that the PUCCH is discarded in the scenario described in conjunction with reference numerals 905 and 1005 (as described in conjunction with Fig.10 ), or may determine that an error condition has occurred in the above scenario based at least in part on the UCI payload, the UCI priority, or the like. For example, the UE 120 may determine to drop the PUSCH in the scenario described in conjunction with reference numerals 905 and 1005 based at least in part on UCI2 including a HARQ-ACK (e.g., HARQ-ACK2) (which may have a higher transmission priority than the PUSCH (e.g., PUSCH1)), and thus transmit PUCCH2 and thus UCI2 (as described in conjunction with Fig. 9In addition, the UE 120 may determine to drop the PUCCH in the scenario described in conjunction with reference numerals 905 and 1005 based at least in part on UCI2 including periodic or semi-persistent CSI or based at least in part on PUSCH1 including aperiodic CSI, and thus transmit PUSCH1 multiplexed with UCI1 without transmitting PUCCH2 and thus UCI2 (as described in conjunction with Fig.10 As described above, this is because aperiodic CSI may have a higher transmission priority than periodic or semi-persistent CSI. In addition, UE 120 may determine to drop PUSCH in the scenario described in conjunction with reference numerals 905 and 1005 based at least in part on PUSCH1 being associated with a configuration grant (CG) PUSCH (CG-PUSCH), and thus transmit PUCCH2 and thus UCI2 (as described in conjunction with Fig. 9 described), but may determine in other ways that an error condition has occurred (eg, UE 120 may determine that an error condition has occurred when PUSCH1 is not associated with CG-PUSCH).

[0103] Although combined with the above Fig. 9 and Fig.10 In the described examples, the PUSCH is described as being associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) and at least partially overlapping with PUCCH1 and PUCCH2, but in some other aspects, the PUSCH may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) and the UE 120 may act in a manner similar to that described above. For example, based at least in part on the PUSCH being associated with the second CORESET pool index and overlapping with PUCCH1 and PUCCH2, the UE 120 may drop the PUSCH (similar to the case in which the PUSCH is associated with the second CORESET pool index). Fig. 9 described example), PUCCH1 can be dropped and UCI2 can be multiplexed on PUSCH (similar to combining Fig. 9 examples described), or it may be determined that an error condition has occurred.

[0104] As indicated above, Fig. 9 and Fig.10 Other examples can be found in the Fig. 9 and Fig.10 The examples described are different.

[0105] Fig.11 is a diagram illustrating an example 1100 of transmission using overlapping PUCCH and PUSCH according to the present disclosure.

[0106] exist Fig.11In the depicted aspect, as shown by reference numeral 1105, UE 120 may determine two PUCCH resources that overlap in the time domain (in Fig.11 PUCCH1 and PUCCH2) can be combined with the above Figures 7 to 10 UE 120 may also identify one or more PUSCHs (which may be in the same CC as PUCCH1 and PUCCH2, or may be in a different CC than PUCCH1 and PUCCH2) associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) that overlap with PUCCH1 (e.g., a PUCCH associated with the first CORESET pool index), in which example, the one or more PUSCHs include PUSCH1 and PUSCH2. Additionally, UE 120 may identify any PUSCH that overlaps with PUCCH2 (e.g., a PUCCH associated with a second CORESET pool index or CORESETPoolIndex 1) in addition to at least partially overlapping with PUCCH1. As shown at reference numeral 1105, in this example, any PUSCH is only PUSCH1.

[0107] In such aspects, if there are any remaining PUSCHs other than the PUSCH identified as at least partially overlapping with both PUCCH1 and PUCCH2, the UE 120 may discard the PUSCH identified as at least partially overlapping with both PUCCH1 and PUCCH2, multiplex the UCI associated with PUCCH1 (e.g., UCI1) with one of the remaining PUSCHs, and send the remaining PUSCHs (including the PUSCH multiplexed with the UCI) as well as PUCCH2 (which will not overlap with the remaining one or more PUSCHs). For example, as shown in figure numeral 1110, UE 120 may discard PUSCH1 (indicated using cross hatching) because PUSCH1 is identified as at least partially overlapping with both PUCCH1 and PUCCH2, may multiplex UCI1 with one of the remaining PUSCHs (PUSCH2 in this example) and thus not send PUCCH1 (indicated using "Not Txd"), and may send non-overlapping PUCCH2 (including UCI2) and PUSCH2 (including UCI1).

[0108] In some aspects, when there are multiple candidate PUSCHs for multiplexing UCI (e.g., when there are multiple remaining PUSCHs other than the PUSCH identified as at least partially overlapping with both PUCCH1 and PUCCH2), UE 120 may select one of the PUSCHs based at least in part on a prioritization rule (e.g., Fig.11 More specifically, in some aspects, the prioritization rule may cause the UE 120 to first select the PUSCH associated with the lowest CC index and then (if more than one PUSCH is associated with the lowest CC index) select the PUSCH associated with the earliest start time. In aspects where there are no remaining PUSCHs other than the PUSCH identified as at least partially overlapping with both PUCCH1 and PUCCH2, the UE 120 may select the PUSCH associated with the lowest CC index first and then (if more than one PUSCH is associated with the lowest CC index) select the PUSCH associated with the earliest start time. Fig. 9 and Fig.10 as described (e.g., may be performed as in conjunction with Fig. 9 PUSCH is dropped as described, such as in conjunction with Fig.10 The PUCCH is discarded as described, or it is determined that an error condition has occurred).

[0109] Although combined with the above Fig.11 In the described examples, the PUSCH identified as at least partially overlapping both PUCCH1 and PUCCH2 is described as being associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), but in some other aspects, the PUSCH identified as at least partially overlapping both PUCCH1 and PUCCH2 may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1), and the UE 120 may act in a manner similar to that described above. For example, based at least in part on the PUSCH identified as at least partially overlapping both PUCCH1 and PUCCH2 being associated with the second CORESET pool index, the UE 120 may drop the PUSCH identified as at least partially overlapping both PUCCH1 and PUCCH2 and associated with the second CORESET pool index, may multiplex UCI2 on one of the remaining PUSCHs, and may send UCI1 in PUCCH1.

[0110] In addition, if combined Figure 5As described, in some aspects, UE 120 may be capable of certain simultaneous PUCCH and PUSCH transmissions. For example, if PUCCH and PUSCH are on different cells in inter-band carrier aggregation, and PUCCH and PUSCH are associated with different physical layer priority values ​​(e.g., one of PUCCH and PUSCH is associated with high priority communications, and the other of PUCCH and PUSCH is associated with low priority communications), then UE 120 may be capable of simultaneous PUCCH and PUSCH transmissions. In such aspects, for the purpose of combining Figures 7 to 11 For the purposes of the described procedures, UE 120 may only consider PUSCHs in the same CC as the CCs of PUCCH1 and PUCCH2 (e.g., PUSCHs associated with a first CORESET pool index and PUSCHs associated with a second CORESET pool index), or in the same frequency band as PUCCH1 and PUCCH2. In other words, insofar as UE 120 is capable of simultaneous PUCCH and PUSCH transmission, UE 120 may not consider UCI multiplexing of PUSCHs in CCs and / or frequency bands other than CCs and / or frequency bands associated with PUCCH1 and PUCCH2. Additionally or alternatively, for purposes of combining Figures 7 to 11 For purposes of the described aspects, UE 120 may consider only PUSCHs (e.g., PUSCHs associated with a first CORESET pool index and PUSCHs associated with a second CORESET pool index) associated with a particular physical layer priority (e.g., the same physical layer priority as PUCCH1 and / or PUCCH2). More specifically, in some aspects, for purposes of combining Figures 7 to 11 For purposes of the described aspects, the UE 120 may consider one or more PUSCHs in CCs and / or frequency bands other than the CCs and / or frequency bands associated with PUCCH1 and PUCCH2, as long as the physical layer priority of the one or more PUSCHs is the same as the physical layer priority of PUCCH1 and / or PUCCH2.

[0111] As indicated above, Fig.11 Other examples can be found in the Fig.11 The examples described are different.

[0112] Fig.12 1 is a diagram of an example 1200 associated with transmission using overlapping PUCCH and PUSCH according to the present disclosure. Fig.12As shown, UE 1205 (e.g., UE 120), first network entity 1210 (e.g., base station 110, CU 310, DU 330, RU 340, TRP 605, or a similar network entity), and second network entity 1215 (e.g., base station 110, CU 310, DU 330, RU 340, TRP 605, or a similar network entity) can communicate with each other. In some aspects, UE 1205, first network entity 1210, and second network entity 1215 can be part of a wireless network (e.g., wireless network 100). UE 1205, first network entity 1210, and second network entity 1215 can be part of a wireless network (e.g., wireless network 100). Fig.12 In some aspects, UE 1205, first network entity 1210, and second network entity 1215 may operate in a multi-TRP and / or multi-DCI scenario. In such aspects, first network entity 1210 may correspond to a first TRP (e.g., in conjunction with Figure 6 The TRP A described above), and the second network entity 1215 may correspond to the second TRP (e.g., in conjunction with Figure 6 TRP B described above). Additionally or alternatively, the first network entity 1210 may be associated with a first CORESET pool index (eg, CORESETPoolIndex 0), and the second network entity 1215 may correspond to a second CORESET pool index (eg, CORESETPoolIndex 1).

[0113] As shown by reference numeral 1220, UE 1205 may receive information from a network entity (e.g., Fig.12 In some aspects, the UE 1205 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 1205 (e.g., known to the UE 1205 and / or previously indicated by a network node or other network device) and / or explicit configuration information for the UE 1205 to use to configure the UE 1205, etc.

[0114] In some aspects, the configuration information may indicate that based at least in part on the UE 1205 being scheduled with overlapping physical channels (e.g., overlapping PUCCH and / or PUSCH), the UE 1205 multiplexes the UCI with the PUSCH and / or drops communications associated with the PUCCH and / or PUSCH. For example, the configuration information may configure the UE 1205 to perform a combined Figures 7 to 11One or more of the described operations. The UE 1205 may configure itself based at least in part on the configuration information.

[0115] As shown by reference numeral 1225, the UE 1205 may determine that the first PUCCH at least partially overlaps with the second PUCCH in the time domain, and determine that the first PUCCH and the second PUCCH may be transmitted simultaneously. Figures 7 to 11 The described PUCCH1 and PUCCH2 overlap at least partially in the time domain. In addition, UE 1205 may determine that PUCCH1 and PUCCH2 may be sent simultaneously based at least in part on configuration information (such as configuration information received via the configuration described in conjunction with reference numeral 1220). For example, the configuration information may include a feedback mode parameter (e.g., ackNackFeedbackMode) indicating that UE 120 may send at least partially overlapping PUCCHs for providing separate HARQ feedback (e.g., UE 120 may be configured with ackNackFeedbackMode as "separate"). In such aspects, UE 120 may determine that PUCCH1 and PUCCH2 may be sent simultaneously based at least in part on the UCI associated with PUCCH1 (e.g., UCI) including a first HARQ feedback communication (e.g., HARQ-ACK1) and the UCI associated with PUCCH2 (e.g., UCI2) including a second HARQ feedback communication (e.g., HARQ-ACK2). In addition, in some aspects, the UE 1205 may determine that UCI1 is associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), and / or the UE 1205 may determine that UCI2 is associated with a second CORESET pool index (e.g., CORESETPoolIndex 1). In some aspects, the UE 1205 may determine that UCI1 is associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), and / or the UE 1205 may determine that UCI2 is associated with a second CORESET pool index (e.g., CORESETPoolIndex 1). Figure 5 PUCCH1 and PUCCH2 are determined after the UCI multiplexing procedure described above.

[0116] As shown by reference numeral 1230, the UE 1205 may determine that at least one of PUCCH1 or PUCCH2 at least partially overlaps with one or more PUSCHs in the time domain. Figures 7 to 11 One of the described PUSCHs overlaps.

[0117] In some aspects, one or both of the network entities 1210, 1215 may perform substantially similar determinations as described above in conjunction with reference numerals 1225 and 1230, instead of or in addition to the UE 1205. For example, as shown in reference numeral 1235, in some aspects, the first network entity 1210 may determine that PUCCH1 at least partially overlaps with PUCCH2 in the time domain, and determine that the UE 1205 is capable of simultaneously transmitting PUCCH1 and PUCCH2, wherein PUCCH1 includes UCI1 associated with a first CORESET pool index (e.g., CORESETPoolIndex 0), PUCCH2 includes UCI2 associated with a second CORESET pool index (e.g., CORESETPoolIndex 1), and determine PUCCH1 and PUCCH2 after considering a UCI multiplexing procedure for overlapping PUCCHs. In addition, as indicated by reference numeral 1240 , the first network entity 1210 may determine that at least one of PUCCH1 or PUCCH2 at least partially overlaps with one or more PUSCHs in the time domain.

[0118] As shown by reference numerals 1245 and 1250, the UE 1205 may use PUCCH1, PUCCH2, and one or more PUSCHs to send communications to the first network entity 1210 and / or the second network entity 1215. In some aspects, the UE 1205 may use less than all of PUCCH1, PUCCH2, and one or more PUSCHs to send communications based at least in part on at least one of the following: multiplexing at least one of UCI1 or UCI2 with at least one of the one or more PUSCHs, or dropping communications associated with PUCCH1, PUCCH2, or at least one of the one or more PUSCHs. For example, the UE 1205 may use less than all of PUCCH1, PUCCH2, and one or more PUSCHs to send communications based at least in part on at least one of the following: multiplexing at least one of UCI1 or UCI2 with at least one of the one or more PUSCHs, or dropping communications associated with at least one of PUCCH1, PUCCH2, or at least one of the one or more PUSCHs. Figures 7 to 11 The described manner sends communications to one or both of the first network entity 1210 and the second network entity 1215. In this regard, as described, in some aspects, PUCCH1 and PUCCH2 can be associated with a first CC, and one or more PUSCHs can be associated with the first CC or with a second CC different from the first CC.

[0119] In addition, as mentioned above Figure 7As described, in some aspects, a first PUSCH (e.g., one of PUSCH1 or PUSCH2 shown at reference numeral 705) may be associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) and may at least partially overlap with PUCCH1 in the time domain, and a second PUSCH (e.g., the other of PUSCH1 or PUSCH2) may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) and may at least partially overlap with PUCCH2 in the time domain. In such aspects, as described above in conjunction with reference numeral 710, a first PUSCH (e.g., Figure 7 UCI1 may be multiplexed on a second PUSCH (e.g., Figure 7 UCI2 is multiplexed on PUSCH2 in the communication channel.

[0120] In some aspects, the additional PUSCH may overlap with one or more of the PUCCHs. For example, the third PUSCH may also be associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) and may at least partially overlap with PUCCH1 in the time domain. In such aspects, UCI1 may be multiplexed on the first PUSCH (rather than the third PUSCH) based at least in part on UCI multiplexing prioritization rules, etc. For example, UCI1 may be multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower CC index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same CC.

[0121] Alternatively, the third PUSCH may be associated with a second CORESET pool index (e.g., CORESETPoolIndex 1) and may at least partially overlap in the time domain with PUCCH 2. In such aspects, UCI 2 may be multiplexed on the second PUSCH (rather than on the third PUSCH) based at least in part on one of the following: the second PUSCH is associated with a lower CC index than the third PUSCH, or the second PUSCH starts earlier than the third PUSCH and the second PUSCH and the third PUSCH are associated with the same CC.

[0122] In some aspects, such as combining Figure 8As described, a PUSCH (e.g., PUSCH1) associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) may at least partially overlap with PUCCH1 in the time domain, and the PUSCH may not overlap with PUCCH2 in the time domain. In such aspects, a PUSCH (e.g., PUSCH2) associated with a first CORESET pool index and at least partially overlapping with PUCCH1 in the time domain may be overlapped with PUCCH1 in the time domain. Figure 8 UCI1 may be multiplexed on PUSCH1 in the first CORESET pool index, and UCI2 may be sent using PUCCH2, as described in conjunction with reference numeral 810. Similarly, when one or more additional PUSCHs associated with the first CORESET pool index overlap with PUCCH1, UCI1 may be multiplexed on PUSCH1 (rather than on another overlapping PUSCH) based at least in part on one of the following: PUSCH1 is associated with a lower CC index than one or more other PUSCHs, or PUSCH1 starts earlier than one or more other PUSCHs and PUSCH1 and the one or more other PUSCHs are associated with the same CC.

[0123] In some aspects, such as combining Figures 9 and 10 As described, at least one PUSCH (eg, Fig. 9 and Fig.10 The PUSCH1 in the CORESET pool index may at least partially overlap with the PUCCH1 in the time domain, and at least one PUSCH associated with the first CORESET pool index (e.g., Fig. 9 and Fig.10 In this case, the UE 1205 may alternatively perform in one of several ways.

[0124] In some aspects, as described in conjunction with reference numeral 910, a PUSCH associated with a first CORESET pool index (eg, Fig. 9In some aspects, UE 1205 may receive a configuration indicating that one or more PUSCHs associated with a first CORESET pool index should be discarded, which may be included as part of the configuration information described in conjunction with reference numeral 1220. Additionally or alternatively, one or more PUSCHs associated with the first CORESET pool index may be discarded based at least in part on the type of communication associated with the PUCCH or PUSCH. More specifically, a HARQ-ACK message (e.g., UCI2) may be included based at least in part on UCI2. Fig. 9 In some embodiments, the one or more PUSCHs associated with the first CORESET pool index may be dropped based at least in part on the HARQ-ACK2 in the HARQ-ACK message, which may have a higher priority than the PUSCH. Additionally or alternatively, the one or more PUSCHs associated with the first CORESET pool index may be dropped based at least in part on the one or more PUSCHs associated with the first CORESET pool index being associated with a CG-PUSCH, which may have a lower priority than the PUCCH.

[0125] In some other aspects, as described in conjunction with reference numeral 1010, UCI2 can be dropped and UCI1 can be associated with one of the one or more PUSCHs associated with the first CORESET pool index (eg, Fig.10 In some aspects, the UE 1205 may receive a configuration indicating that UCI2 should be discarded, which may be included as part of the configuration information described in conjunction with reference numeral 1220. Additionally or alternatively, UCI2 may be discarded based at least in part on a CSI type associated with the PUCCH or PUSCH. More specifically, UCI2 may be discarded based at least in part on at least one of the following: UCI2 includes a periodic or semi-persistent CSI report, or at least one PUSCH of one or more PUSCHs associated with the first CORESET pool index (e.g., Fig.10 PUSCH1) in includes non-periodic CSI reporting.

[0126] In some other aspects, the UE 1205 may not desire that at least one PUSCH (e.g., CORESETPoolIndex 0) associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) Fig. 9 and Fig.10In the embodiment of the present invention, the UE 1205 may determine that an error condition has occurred when faced with the situations shown at reference numerals 905 and 1005. In the embodiment of the present invention, the UE 1205 may determine that an error condition has occurred when faced with the situations shown at reference numerals 905 and 1005. In the embodiment of the present invention, the UE 1205 may determine that an error condition has occurred when faced with the situations shown at reference numerals 905 and 1005. In the embodiment of the present invention, the UE 1205 may determine that an error condition has occurred when faced with the situations shown at reference numerals 905 and 1005.

[0127] In some aspects, such as combining Fig.11 As described, UE 1205 may identify at least one PUSCH (eg, Fig.11 , and after excluding at least one PUSCH at least partially overlapping with both PUCCH1 and PUCCH2, one or more remaining PUSCHs (e.g., CORESETPoolIndex 0) associated with a first CORESET pool index (e.g., CORESETPoolIndex 0) that overlap with PUCCH1 may be identified. Fig.11 In such aspects, the UE 1205 may discard communications associated with at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH (e.g., the UE 1205 may discard communications associated with at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH). Fig.11 ), UCI1 is associated with a PUSCH in one or more remaining PUSCHs (e.g., Fig.11 The UE 1205 may multiplex UCI1 with the PUSCH associated with the lowest CC index if more than one remaining PUSCH is available for multiplexing with UCI1, or may multiplex UCI1 with the PUSCH having the earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same CC, as described.

[0128] As indicated above, Fig.12 Other examples can be found in the Fig.12 The examples described are different.

[0129] Fig.13is a diagram illustrating an example process 1300 performed, for example, by a UE in accordance with the present disclosure. Example process 1300 is an example in which a UE (eg, UE 1205) performs operations associated with transmission using overlapping PUCCH and PUSCH.

[0130] like Fig.13 As shown, in some aspects, process 1300 may include determining that a first PUCCH at least partially overlaps with a second PUCCH in the time domain, and determining that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after performing a UCI multiplexing procedure for overlapping PUCCHs (block 1310). For example, a UE (e.g., using Fig.15 The communication manager 1508 and / or determination component 1510 depicted in the figure can determine that a first PUCCH at least partially overlaps with a second PUCCH in the time domain, and determine that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs, as described above.

[0131] like Fig.13 As further shown, in some aspects, process 1300 may include determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain (block 1320). Fig.15 The communication manager 1508 and / or the determining component 1510 depicted in FIG. 1 may determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain, as described above.

[0132] like Fig.13 As further shown, in some aspects, process 1300 may include sending communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one of the one or more PUSCHs, or dropping communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs (block 1330). For example, a UE (e.g., using Fig.15The communication manager 1508 and / or the sending component 1504 depicted in the figure may use less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs to send communications based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs, as described above.

[0133] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0134] In a first aspect, a first PUCCH and a second PUCCH are associated with a first component carrier.

[0135] In a second aspect, alone or in combination with the first aspect, one or more PUSCHs are associated with the first component carrier.

[0136] In a third aspect, alone or in combination with the first aspect, the one or more PUSCHs are associated with a second component carrier different from the first component carrier.

[0137] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first PUSCH among one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with a first PUCCH in a time domain, a second PUSCH among one or more PUSCHs is associated with a second CORESET pool index and at least partially overlaps with a second PUCCH in a time domain, a first UCI is multiplexed on the first PUSCH, and a second UCI is multiplexed on the second PUSCH.

[0138] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a third PUSCH of one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and a first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0139] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, a third PUSCH of the one or more PUSCHs is associated with a second CORESET pool index and at least partially overlaps with a second PUCCH in the time domain, and a second UCI is multiplexed on the second PUSCH based at least in part on one of the following: the second PUSCH is associated with a lower component carrier index than the third PUSCH, or the second PUSCH starts earlier than the third PUSCH and the second PUSCH and the third PUSCH are associated with the same component carrier.

[0140] In the seventh aspect, alone or in combination with one or more aspects from the first to the sixth aspects, a first PUSCH among one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with a first PUCCH in the time domain, the PUSCH does not overlap with a second PUCCH in the time domain, a first UCI is multiplexed on the first PUSCH, and a second UCI is sent using a second PUCCH.

[0141] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, a third PUSCH of the one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and a first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0142] In the ninth aspect, alone or in combination with one or more aspects of the first to eighth aspects, at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and the PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

[0143] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, communications associated with a PUSCH associated with a first CORESET pool index are discarded, a first UCI is sent using a first PUCCH, and a second UCI is sent using a second PUCCH.

[0144] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 1300 includes receiving a configuration indicating that a PUSCH associated with a first CORESET pool index should be dropped.

[0145] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a PUSCH associated with a first CORESET pool index is dropped based at least in part on the second UCI including a hybrid automatic repeat request acknowledgement message.

[0146] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a PUSCH associated with the first CORESET pool index is dropped based at least in part on the PUSCH associated with the first CORESET pool index being associated with a configuration grant PUSCH.

[0147] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the second UCI is dropped and the first UCI is multiplexed with one of the one or more PUSCHs associated with the first CORESET pool index that overlaps with the first PUCCH.

[0148] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the process 1300 includes receiving a configuration indicating that a second UCI should be dropped.

[0149] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the second UCI is discarded based at least in part on at least one of the following: the second UCI includes a periodic or semi-persistent CSI report, or at least one PUSCH of one or more PUSCHs includes an aperiodic CSI report.

[0150] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, a UE determines that an error condition has occurred.

[0151] In the eighteenth aspect, alone or in combination with one or more aspects of the first to seventeenth aspects, process 1300 includes: identifying at least one PUSCH among one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and performing the following actions at least partially based on the existence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: discarding communications associated with at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH; multiplexing the first UCI with the PUSCH among the one or more remaining PUSCHs; and using the second PUCCH to send communications associated with the one or more remaining PUSCHs and the second UCI.

[0152] In the nineteenth aspect, alone or in combination with one or more aspects from the first to the eighteenth aspects, multiplexing the first UCI with a PUSCH in one or more remaining PUSCHs also includes: multiplexing the first UCI with a PUSCH associated with a lowest component carrier index in the one or more remaining PUSCHs; or multiplexing the first UCI with a PUSCH having an earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same component carrier.

[0153] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 The blocks depicted in the process 1300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1300. Additionally or alternatively, two or more blocks in the blocks of the process 1300 may be performed in parallel.

[0154] Fig.14 is a diagram illustrating an example process 1400 performed, for example, by a network entity in accordance with the present disclosure. Example process 1400 is an example in which a network entity (eg, network entity 1210 or network entity 1215) performs operations associated with transmission using overlapping PUCCH and PUSCH.

[0155] like Fig.14As shown, in some aspects, process 1400 may include determining that a first PUCCH associated with a UE (e.g., UE 1205) at least partially overlaps with a second PUCCH in the time domain, and determining that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after considering a UCI multiplexing procedure for overlapping PUCCHs (block 1410). For example, a network entity (e.g., using Fig.16 The communication manager 1608 and / or determination component 1610 depicted in the figure can determine that a first PUCCH associated with the UE at least partially overlaps with a second PUCCH in the time domain, and determine that the UE is capable of simultaneously sending the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering the UCI multiplexing procedure for overlapping PUCCHs, as described above.

[0156] like Fig.14 As further shown, in some aspects, process 1400 may include determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain (block 1420). Fig.16 The communication manager 1608 and / or the determining component 1610 depicted in FIG. 1 may determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain, as described above.

[0157] like Fig.14 As further shown, in some aspects, process 1400 may include receiving a communication from a UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs (block 1430). Fig.16 The communication manager 1608 and / or receiving component 1602 depicted in the figure can receive a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one PUSCH of one or more PUSCHs, as described above.

[0158] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0159] In a first aspect, a first PUCCH and a second PUCCH are associated with a first component carrier.

[0160] In a second aspect, alone or in combination with the first aspect, one or more PUSCHs are associated with the first component carrier.

[0161] In a third aspect, alone or in combination with the first aspect, the one or more PUSCHs are associated with a second component carrier different from the first component carrier.

[0162] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a first PUSCH among one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with a first PUCCH in a time domain, a second PUSCH among one or more PUSCHs is associated with a second CORESET pool index and at least partially overlaps with a second PUCCH in a time domain, a first UCI is multiplexed on the first PUSCH, and a second UCI is multiplexed on the second PUSCH.

[0163] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a third PUSCH of one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and a first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0164] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, a first PUSCH among one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with a first PUCCH in the time domain, the PUSCH does not overlap with a second PUCCH in the time domain, and the network entity receives at least one of a first UCI multiplexed on the first PUSCH or a second UCI in a second PUCCH.

[0165] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, a third PUSCH of the one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and a first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0166] In the eighth aspect, alone or in combination with one or more aspects from the first to the seventh aspects, at least a first PUSCH of the one or more PUSCHs is associated with a first CORESET pool index and at least partially overlaps with a first PUCCH in the time domain, at least a second PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with a second PUCCH in the time domain, and a PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

[0167] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, a network entity receives a first UCI multiplexed with one of a first PUSCH or a second PUSCH.

[0168] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the process 1400 includes sending a configuration to the UE indicating that the second UCI should be discarded.

[0169] In the eleventh aspect, alone or in combination with one or more aspects of the first to tenth aspects, process 1400 includes: identifying at least one PUSCH among one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and performing at least one of the following based at least in part on the presence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: receiving a first UCI in a PUSCH among the one or more remaining PUSCHs, or receiving a second UCI in a second PUCCH.

[0170] In the twelfth aspect, alone or in combination with one or more aspects of the first to eleventh aspects, receiving the first UCI in a PUSCH in one or more remaining PUSCHs also includes: receiving the first UCI in a PUSCH associated with a lowest component carrier index in the one or more remaining PUSCHs; or receiving the first UCI in a PUSCH with an earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same component carrier.

[0171] although Fig.14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Fig.14 The blocks depicted in the process 1400 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1400. Additionally or alternatively, two or more blocks in the blocks of the process 1400 may be performed in parallel.

[0172] Fig.15 1 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a UE (e.g., UE 1205), or a UE may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508. Communication manager 1508 may include one or more of a determining component 1510 and an identifying component 1512, among others.

[0173] In some aspects, the apparatus 1500 may be configured to perform Figures 7 to 12 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.13 The process 1300. In some aspects, Fig.15 The apparatus 1500 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.15 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0174] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1506. The receiving component 1502 may provide the received communications to one or more other components of the apparatus 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1500. In some aspects, the receiving component 1502 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0175] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the depicted UE 120. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0176] The determining component 1510 may determine that a first PUCCH at least partially overlaps with a second PUCCH in the time domain, and determine that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs. The determining component 1510 may determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The transmitting component 1504 may transmit communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0177] Receiving component 1502 may receive a configuration indicating that a PUSCH associated with a first CORESET pool index should be dropped.

[0178] Receiving component 1502 may receive a configuration indicating that the second UCI should be discarded.

[0179] The identifying component 1512 may identify at least one PUSCH of the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain.

[0180] The determining component 1510 and / or the sending component 1504 can perform the following actions based at least in part on the existence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: discarding communications associated with at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH; multiplexing the first UCI with a PUSCH in the one or more remaining PUSCHs; and using the second PUCCH to send communications associated with the one or more remaining PUSCHs and the second UCI.

[0181] Fig.15 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.15 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.15Two or more components shown in may be implemented in a single component, or Fig.15 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.15 One or more functions performed by another set of components shown in FIG.

[0182] Fig.16 1 is a diagram of an example apparatus 1600 for wireless communication according to the present disclosure. Apparatus 1600 may be a network entity (e.g., network entity 1210 or network entity 1215), or a network entity may include apparatus 1600. In some aspects, apparatus 1600 includes a receiving component 1602 and a sending component 1604 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using receiving component 1602 and sending component 1604. As further shown, apparatus 1600 may include a communication manager 1608. Communication manager 1608 may include one or more of determining component 1610 or identifying component 1612, etc.

[0183] In some aspects, the apparatus 1600 may be configured to perform Figures 7 to 12 Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Fig.14 The process 1400. In some aspects, Fig.16 The apparatus 1600 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described base station 110. Additionally or alternatively, Fig.16 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0184] The receiving component 1602 may receive communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1600. In some aspects, the receiving component 1602 may include combining Figure 2 The base station 110 is depicted as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0185] Transmit component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1606. In some aspects, one or more other components of device 1600 may generate communications and may provide the generated communications to transmit component 1604 for transmission to device 1606. In some aspects, transmit component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1606. In some aspects, transmit component 1604 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described base station 110. In some aspects, the transmit component 1604 can be co-located with the receive component 1602 in a transceiver.

[0186] The determining component 1610 may determine that a first PUCCH associated with the UE at least partially overlaps with a second PUCCH in the time domain, and determine that the UE is capable of simultaneously transmitting the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering a UCI multiplexing procedure for overlapping PUCCHs. The determining component 1610 may determine that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain. The receiving component 1602 may receive a communication from the UE based at least in part on the determination, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0187] Transmitting component 1604 may transmit a configuration to the UE indicating that the second UCI should be discarded.

[0188] The identifying component 1612 may identify at least one PUSCH of the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain.

[0189] The receiving component 1602 can perform at least one of the following based at least in part on the presence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: receiving the first UCI in a PUSCH in the one or more remaining PUSCHs, or receiving the second UCI in the second PUCCH.

[0190] Fig.16 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.16 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.16 Two or more components shown in may be implemented in a single component, or Fig.16 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.16 One or more functions performed by another set of components shown in FIG.

[0191] The following provides an overview of some aspects of the disclosure:

[0192] Aspect 1: A method of wireless communication performed by a UE, comprising: determining that a first PUCCH at least partially overlaps with a second PUCCH in a time domain, and determining that the first PUCCH and the second PUCCH can be sent simultaneously, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after performing a UCI multiplexing procedure for overlapping PUCCHs; and determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain; and using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs to send communications based at least in part on at least one of the following: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or discarding communications associated with the first PUCCH, the second PUCCH, or at least one of the one or more PUSCHs.

[0193] Aspect 2: The method according to aspect 1, wherein the first PUCCH and the second PUCCH are associated with a first component carrier.

[0194] Aspect 3: The method according to aspect 2, wherein the one or more PUSCHs are associated with the first component carrier.

[0195] Aspect 4: The method according to aspect 2, wherein the one or more PUSCHs are associated with a second component carrier different from the first component carrier.

[0196] Aspect 5: A method according to any one of Aspects 1 to 4, wherein a first PUSCH among the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH among the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

[0197] Aspect 6: A method according to Aspect 5, wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH at least partially based on one of the following: the first PUSCH is associated with a component carrier index lower than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0198] Aspect 7: A method according to Aspect 5, wherein a third PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein the second UCI is multiplexed on the second PUSCH at least partially based on one of the following: the second PUSCH is associated with a component carrier index lower than the third PUSCH, or the second PUSCH starts earlier than the third PUSCH and the second PUSCH and the third PUSCH are associated with the same component carrier.

[0199] Aspect 8: A method according to aspect 1, wherein a first PUSCH among the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second PUCCH is used to send the second UCI.

[0200] Aspect 9: A method according to Aspect 8, wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH at least partially based on one of the following: the first PUSCH is associated with a component carrier index lower than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0201] Aspect 10: A method according to aspect 1, wherein at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein the PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

[0202] Aspect 11: The method according to aspect 10, wherein communications associated with the PUSCH associated with the first CORESET pool index are discarded, wherein the first UCI is sent using the first PUCCH, and wherein the second UCI is sent using the second PUCCH.

[0203] Aspect 12: The method according to aspect 11 further includes: receiving a configuration indicating that the PUSCH associated with the first CORESET pool index should be discarded.

[0204] Aspect 13: The method according to any one of aspects 11 to 12, wherein the PUSCH associated with the first CORESET pool index is dropped based at least in part on the second UCI including a hybrid automatic repeat request acknowledgement message.

[0205] Aspect 14: The method according to any one of aspects 11 to 13, wherein the PUSCH associated with the first CORESET pool index is dropped based at least in part on the PUSCH associated with the first CORESET pool index being associated with a configuration grant PUSCH.

[0206] Aspect 15: The method according to aspect 10, wherein the second UCI is dropped, and wherein the first UCI is multiplexed with one of the one or more PUSCHs associated with the first CORESET pool index that overlaps with the first PUCCH.

[0207] Aspect 16: The method according to aspect 15, further comprising: receiving a configuration indicating that the second UCI should be discarded.

[0208] Aspect 17: A method according to any one of Aspects 15 to 16, wherein the second UCI is discarded at least in part based on at least one of the following: the second UCI includes a periodic or semi-persistent CSI report, or at least one of the one or more PUSCHs includes an aperiodic CSI report.

[0209] Aspect 18: The method according to aspect 10, wherein the UE determines that an error condition has occurred.

[0210] Aspect 19: The method according to Aspect 10 also includes: identifying at least one PUSCH among the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and performing the following actions at least partially based on the existence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding the at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: discarding communications associated with the at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH; multiplexing the first UCI with a PUSCH among the one or more remaining PUSCHs; and using the second PUCCH to send communications associated with the one or more remaining PUSCHs and the second UCI.

[0211] Aspect 20: A method according to Aspect 19, wherein multiplexing the first UCI with the PUSCH in the one or more remaining PUSCHs further comprises: multiplexing the first UCI with the PUSCH associated with the lowest component carrier index in the one or more remaining PUSCHs; or multiplexing the first UCI with the PUSCH with the earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same component carrier.

[0212] Aspect 21: A method of wireless communication performed by a network entity, comprising: determining that a first PUCCH associated with a UE at least partially overlaps with a second PUCCH in a time domain, and determining that the UE is capable of simultaneously sending the first PUCCH and the second PUCCH, wherein the first PUCCH includes a first UCI associated with a first CORESET pool index, the second PUCCH includes a second UCI associated with a second CORESET pool index, and the first PUCCH and the second PUCCH are determined after considering a UCI multiplexing procedure for overlapping PUCCHs; and determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more PUSCHs in the time domain; and receiving communications from the UE based at least in part on the determination, wherein the communications include at least one of the first UCI or the second UCI multiplexed with at least one of the one or more PUSCHs.

[0213] Aspect 22: The method according to aspect 21, wherein the first PUCCH and the second PUCCH are associated with a first component carrier.

[0214] Aspect 23: The method according to aspect 22, wherein the one or more PUSCHs are associated with the first component carrier.

[0215] Aspect 24: The method according to aspect 22, wherein the one or more PUSCHs are associated with a second component carrier different from the first component carrier.

[0216] Aspect 25: A method according to any one of Aspects 21 to 24, wherein a first PUSCH among the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH among the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

[0217] Aspect 26: A method according to Aspect 25, wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH at least partially based on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0218] Aspect 27: A method according to Aspect 21, wherein a first PUSCH among the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH and the second UCI is received in the second PUCCH.

[0219] Aspect 28: A method according to Aspect 27, wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH at least partially based on one of the following: the first PUSCH is associated with a component carrier index lower than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

[0220] Aspect 29: A method according to Aspect 21, wherein at least a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein at least a second PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein the PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

[0221] Aspect 30: The method according to aspect 29, wherein the first UCI is multiplexed on one PUSCH of one or more PUSCHs overlapping with the first UCI.

[0222] Aspect 31: The method according to aspect 30 further includes: sending a configuration to the UE indicating that the second UCI should be discarded.

[0223] Aspect 32: The method according to Aspect 29 also includes: identifying at least one PUSCH among the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and performing at least one of the following based at least in part on the existence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding the at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: receiving the first UCI in a PUSCH among the one or more remaining PUSCHs, or receiving the second UCI in the second PUCCH.

[0224] Aspect 33: A method according to Aspect 32, wherein receiving the first UCI in the PUSCH among the one or more remaining PUSCHs further comprises: receiving the first UCI in a PUSCH associated with a lowest component carrier index among the one or more remaining PUSCHs; or receiving the first UCI in a PUSCH with an earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same component carrier.

[0225] Aspect 34: An apparatus for performing wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 20.

[0226] Aspect 35: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 20.

[0227] Aspect 36: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 20.

[0228] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 20.

[0229] Aspect 38: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 1 to 20.

[0230] Aspect 39: An apparatus for performing wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 21 to 33.

[0231] Aspect 40: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 21 to 33.

[0232] Aspect 41: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 21 to 33.

[0233] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 21 to 33.

[0234] Aspect 43: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 21 to 33.

[0235] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0236] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the system or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code to describe the operation and behavior of the system and / or method herein, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0237] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0238] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0239] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items connected to the article "the" mentioned, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as one or more processors coupled to the memory and configured to: determining that a first physical uplink control channel (PUCCH) at least partially overlaps with a second PUCCH in the time domain, and determining that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein The first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, The second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after performing a UCI multiplexing procedure for overlapping PUCCHs; as well as determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; as well as and transmitting communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or Communications associated with at least one of the first PUCCH, the second PUCCH, or the one or more PUSCHs are discarded. 2 . The apparatus of claim 1 , wherein the first PUCCH and the second PUCCH are associated with a first component carrier. 3 . The apparatus of claim 2 , wherein the one or more PUSCHs are associated with the first component carrier. 4 . The apparatus of claim 2 , wherein the one or more PUSCHs are associated with a second component carrier different from the first component carrier.

5. The apparatus of claim 1 , wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

6. The apparatus of claim 5 , wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

7. The apparatus of claim 5 , wherein a third PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein the second UCI is multiplexed on the second PUSCH based at least in part on one of the following: the second PUSCH is associated with a lower component carrier index than the third PUSCH, or the second PUSCH starts earlier than the third PUSCH and the second PUSCH and the third PUSCH are associated with the same component carrier.

8. The apparatus of claim 1 , wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is sent using the second PUCCH.

9. The apparatus of claim 8, wherein a third PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, and wherein the first UCI is multiplexed on the first PUSCH based at least in part on one of the following: the first PUSCH is associated with a lower component carrier index than the third PUSCH, or the first PUSCH starts earlier than the third PUSCH and the first PUSCH and the third PUSCH are associated with the same component carrier.

10. The apparatus of claim 1, wherein at least a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein at least a second PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein a PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

11. The apparatus of claim 10, wherein communications associated with the PUSCH associated with the first CORESET pool index are discarded, wherein the first UCI is sent using the first PUCCH, and wherein the second UCI is sent using the second PUCCH.

12. The apparatus of claim 11, wherein the one or more processors are further configured to receive a configuration indicating that the PUSCH associated with the first CORESET pool index should be dropped.

13. The apparatus of claim 11, wherein the PUSCH associated with the first CORESET pool index is dropped based at least in part on the second UCI comprising a hybrid automatic repeat request acknowledgement message.

14. The apparatus of claim 11, wherein the PUSCH associated with the first CORESET pool index is dropped based at least in part on the PUSCH associated with the first CORESET pool index being associated with a configuration-granted PUSCH.

15. The apparatus of claim 10, wherein the second UCI is dropped, and wherein the first UCI is multiplexed with one of one or more PUSCHs associated with the first CORESET pool index that overlaps with the first PUCCH. 16 . The apparatus of claim 15 , wherein the one or more processors are further configured to receive a configuration indicating that the second UCI should be discarded.

17. The apparatus of claim 15, wherein the second UCI is discarded based at least in part on at least one of: The second UCI comprises a periodic or semi-persistent channel state information (CSI) report, or At least one PUSCH of the one or more PUSCHs includes an aperiodic CSI report.

18. The apparatus of claim 10, wherein the UE determines that an error condition has occurred.

19. The apparatus of claim 10, wherein the one or more processors are further configured to: identifying at least one PUSCH of the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and Based at least in part on the presence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding the at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH: discarding communications associated with the at least one PUSCH at least partially overlapping with both the first PUCCH and the second PUCCH; multiplexing the first UCI with a PUSCH in the one or more remaining PUSCHs; and Communications associated with the one or more remaining PUSCHs and the second UCI are sent using the second PUCCH.

20. The UE of claim 19, wherein multiplexing the first UCI with the PUSCH in the one or more remaining PUSCHs further comprises: multiplexing the first UCI with a PUSCH associated with a lowest component carrier index among the one or more remaining PUSCHs; or The first UCI is multiplexed with a PUSCH having an earliest start time based at least in part on the one or more remaining PUSCHs being associated with the same component carrier.

21. An apparatus for wireless communication at a network entity, comprising: Memory; as well as one or more processors coupled to the memory and configured to: determining that a first physical uplink control channel (PUCCH) associated with a user equipment (UE) at least partially overlaps with a second PUCCH in the time domain, and determining that the UE is capable of transmitting the first PUCCH and the second PUCCH simultaneously, wherein The first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, The second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after considering a UCI multiplexing procedure for overlapping PUCCHs; as well as determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; as well as Based at least in part on the determination, a communication is received from the UE, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one PUSCH of the one or more PUSCHs.

22. The apparatus of claim 21 , wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

23. The apparatus of claim 21, wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and the second UCI is received in the second PUCCH.

24. The apparatus of claim 21, wherein at least a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein at least a second PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein a PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

25. The apparatus of claim 24, wherein the first UCI is multiplexed on one PUSCH of one or more PUSCHs overlapping with the first UCI.

26. The apparatus of claim 25, wherein the one or more processors are further configured to send a configuration to the UE indicating that the second UCI should be discarded.

27. The apparatus of claim 24, wherein the one or more processors are further configured to: identifying at least one PUSCH of the one or more PUSCHs that at least partially overlaps with both the first PUCCH and the second PUCCH in the time domain; and Based at least in part on the presence of one or more remaining PUSCHs associated with the first CORESET pool index and overlapping with the first PUCCH after excluding the at least one PUSCH that at least partially overlaps with both the first PUCCH and the second PUCCH, at least one of: receiving the first UCI in a PUSCH of the one or more remaining PUSCHs, or The second UCI is received in the second PUCCH.

28. A method of wireless communication performed by a user equipment (UE), comprising: determining that a first physical uplink control channel (PUCCH) at least partially overlaps with a second PUCCH in the time domain, and determining that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein The first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, The second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after performing a UCI multiplexing procedure for overlapping PUCCHs; as well as determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; as well as and transmitting communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or Communications associated with at least one of the first PUCCH, the second PUCCH, or the one or more PUSCHs are discarded.

29. The method of claim 28, wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

30. The method of claim 28, wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is sent using the second PUCCH.

31. The method of claim 28, wherein at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein at least one of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, and wherein the PUSCH associated with the second CORESET pool index does not overlap with the second PUCCH in the time domain.

32. A method of wireless communication performed by a network entity, comprising: determining that a first physical uplink control channel (PUCCH) associated with a user equipment (UE) at least partially overlaps with a second PUCCH in the time domain, and determining that the UE is capable of transmitting the first PUCCH and the second PUCCH simultaneously, wherein The first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, The second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after considering a UCI multiplexing procedure for overlapping PUCCHs; as well as determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; as well as Based at least in part on the determination, a communication is received from the UE, wherein the communication includes at least one of the first UCI or the second UCI multiplexed with at least one PUSCH of the one or more PUSCHs.

33. The method of claim 32, wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein a second PUSCH of the one or more PUSCHs is associated with the second CORESET pool index and at least partially overlaps with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is multiplexed on the second PUSCH.

34. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: determining that a first physical uplink control channel (PUCCH) at least partially overlaps with a second PUCCH in the time domain, and determining that the first PUCCH and the second PUCCH can be transmitted simultaneously, wherein The first PUCCH includes first uplink control information (UCI) associated with a first control resource set (CORESET) pool index, The second PUCCH includes a second UCI associated with a second CORESET pool index, and determining the first PUCCH and the second PUCCH after performing a UCI multiplexing procedure for overlapping PUCCHs; as well as determining that at least one of the first PUCCH or the second PUCCH at least partially overlaps with one or more physical uplink shared channels (PUSCHs) in the time domain; as well as and transmitting communications using less than all of the first PUCCH, the second PUCCH, and the one or more PUSCHs based at least in part on at least one of: multiplexing at least one of the first UCI or the second UCI with at least one PUSCH of the one or more PUSCHs, or Communications associated with at least one of the first PUCCH, the second PUCCH, or the one or more PUSCHs are discarded.

35. The non-transitory computer-readable medium of claim 34, wherein a first PUSCH of the one or more PUSCHs is associated with the first CORESET pool index and at least partially overlaps with the first PUCCH in the time domain, wherein the PUSCH does not overlap with the second PUCCH in the time domain, wherein the first UCI is multiplexed on the first PUSCH, and wherein the second UCI is sent using the second PUCCH.