WO2023197295A1

WO2023197295A1 - Resource multiplexing for multi-dci based multi-panel simultaneous ul transmission

Info

Publication number: WO2023197295A1
Application number: PCT/CN2022/087053
Authority: WO
Inventors: Bingchao LIU; Ran YUE; Jianfeng Wang; Hongmei Liu; Haiming Wang
Original assignee: Lenovo (Beijing) Limited
Priority date: 2022-04-15
Filing date: 2022-04-15
Publication date: 2023-10-19

Abstract

Methods and apparatuses for resource multiplexing for multi-DCI based multi-panel simultaneous UL transmission are disclosed. In one embodiment, a UE comprises a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to receive, via the transceiver, DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and for each of the overlapped PUCCH resource (s), drop one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

Description

RESOURCE MULTIPLEXING FOR MULTI-DCI BASED MULTI-PANEL SIMULTANEOUS UL TRANSMISSION

FIELD

The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for resource multiplexing for multi-DCI based multi-panel simultaneous UL transmission.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to within the following description: New Radio (NR) , Very Large Scale Integration (VLSI) , Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM or Flash Memory) , Compact Disc Read-Only Memory (CD-ROM) , Local Area Network (LAN) , Wide Area Network (WAN) , User Equipment (UE) , Evolved Node B (eNB) , Next Generation Node B (gNB) , Uplink (UL) , Downlink (DL) , Central Processing Unit (CPU) , Graphics Processing Unit (GPU) , Field Programmable Gate Array (FPGA) , Orthogonal Frequency Division Multiplexing (OFDM) , Radio Resource Control (RRC) , User Entity/Equipment (Mobile Terminal) , Transmitter (TX) , Receiver (RX) , Physical Uplink Control Channel (PUCCH) , Physical Uplink Shared Channel (PUSCH) , Sounding Reference Signal (SRS) , Downlink Control Information (DCI) , transmission reception point (TRP) , Transmission Configuration Indicator (TCI) , Scheduling Request (SR) , Uplink Control Information (UCI) , Hybrid Automatic Repeat Request (HARQ) , Acknowledge (ACK) , Channel State Information (CSI) , control resource set (CORESET) , Physical Downlink Control Channel (PDCCH) , band width part (BWP) .

Panel-selection based UL transmission was specified in NR Release 17 for a UE equipped with multiple panels which can be used for UL transmission. A UE may be equipped with multiple panels, while only one panel can be used for UL transmission at a time instant. It means that only one PUSCH or PUCCH or SRS resource can be scheduled to be transmitted at a time instant in a carrier using one panel.

Advanced UEs can benefit from higher UL coverage and average throughput with simultaneous UL multi-panel transmission. It means that multiple panels (e.g. two panels) can be used for UL transmission at a time instant for a carrier. For multi-DCI based UL transmission, across different panels (e.g. two panels) in a same CC, only PUSCH+PUSCH or PUCCH+PUCCH can be transmitted, while PUSCH+PUCCH or PUCCH+PUSCH is not allowed. It means that, if PUSCH transmission is transmitted by one panel of the two panels at a first given time instant, it is only allowed that another PUSCH transmission can be transmitted by the other panel of the two panels at the first give time instant of a carrier, while any PUCCH transmission is not possible to be transmitted by the other panel of the two panels at the first give time instant. Similarly, if PUCCH transmission is transmitted by one panel of the two panels at a second given time instant in a carrier, it is only allowed that another PUCCH transmission can be transmitted by the other panel of the two panels at the second give time instant, while any PUSCH transmission is not possible to be transmitted by the other panel of the two panels at the second give time instant.

To support multi-DCI based multi-TRP operation with simultaneous multi-panel UL transmission, it is necessary to specify UE behaviors if a PUSCH transmission and a PUCCH resource are scheduled to be transmitted on the same time instant.

This disclosure targets the issue of specifying UE behaviors if a PUSCH transmission and a PUCCH resource are to be transmitted on the same time instant.

BRIEF SUMMARY

Methods and apparatuses for resource multiplexing for multi-DCI based multi-panel simultaneous UL transmission are disclosed.

In one embodiment, a UE comprises a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to receive, via the transceiver, DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and for each of the overlapped PUCCH resource (s) , drop one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In some embodiment, the processor is configured to, for each of the overlapped PUCCH resource (s) , drop the overlapped PUCCH resource; and multiplex the UCI carried in the overlapped PUCCH resource in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.

In some embodiment, if a first PUSCH transmission and the overlapped PUCCH resource are scheduled to be associated with the same coresetPoolIndex value in the one slot, and the first PUSCH transmission is not overlapped with any PUCCH resource, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first PUSCH transmission.

In some embodiment, if the overlapped PUCCH resource is overlapped with only one PUSCH transmission, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one PUSCH transmission.

In some embodiment, if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first of the two PUSCH transmissions.

In some embodiment, if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, and one of the two PUSCH transmissions is in response to a DCI format detection and the other of the two PUSCH transmissions is not in response to a DCI format detection, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one of the two PUSCH transmissions that is in response to a DCI format detection.

In some embodiment, if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is in response to a DCI format detection, the UCI includes HARQ-ACK and/or CSI information, and if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is not in response to a DCI format detection, the UCI only includes CSI information.

In another embodiment, a method performed at a UE comprises receiving DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and dropping, for each of the overlapped PUCCH resource (s) , one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In still another embodiment, a base unit comprises a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to transmit, via the transceiver, DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and for each of the overlapped PUCCH resource (s) , receive, via the transceiver, one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In yet another embodiment, a method performed at a base unit comprises transmitting DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and receiving, for each of the overlapped PUCCH resource (s) , one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 illustrates an example for simultaneous multi-panel UL transmission without PUCCH and PUSCH overlapping;

Figure 2 illustrates an example for simultaneous multi-panel UL transmission with PUCCH and PUSCH overlapping;

Figure 3 illustrates an example of PUCCH and PUSCH overlapping in Case 1-1;

Figure 4 illustrates an example of PUCCH and PUSCH overlapping in Case 1-2;

Figure 5 illustrates an example of PUCCH and PUSCH overlapping in Case 2-1;

Figure 6 illustrates an example of PUCCH and PUSCH overlapping in Case 2-2;

Figure 7 illustrates an example of PUCCH and PUSCH overlapping in Case 3;

Figure 8 illustrates an example of PUCCH and PUSCH overlapping in Case 4-1;

Figure 9 illustrates an example of PUCCH and PUSCH overlapping in Case 4-2;

Figure 10 illustrates an example of PUCCH and PUSCH overlapping in Case 5;

Figure 11 illustrates an example of PUCCH and PUSCH overlapping with a combination of Case 2-1 and Case 4-1;

Figure 12 illustrates an example of PUCCH and PUSCH overlapping with a combination of Case 1-1 and another Case 1-1;

Figure 13 is a schematic flow chart diagram illustrating an embodiment of a method;

Figure 14 is a schematic flow chart diagram illustrating an embodiment of another method; and

Figure 15 is a schematic block diagram illustrating apparatuses according to one embodiment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” . The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain functional units described in this specification may be labeled as “modules” , in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment” , “an embodiment” , or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” , “in an embodiment” , and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including” , “comprising” , “having” , and variations thereof mean “including but are not limited to” , unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a” , “an” , and “the” also refer to “one or more” unless otherwise expressly specified.

Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.

Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

“Multi-TRP” means that a serving cell can have multiple (e.g. two) TRPs. “Multi-panel” means that a UE can have multiple (e.g. two) panels. In the condition that a UE with two panels (e.g. panel#1 and panel#2) transmits UL signal (PUSCH transmissions and/or PUCCH resources) on a serving cell with two TRPs (e.g. TRP#1 and TRP#2) , the UE may use one panel (e.g. panel#1) to transmit UL signal to one TRP (e.g. TRP#1) of the serving cell and use the other panel (e.g. panel#2) to transmit UL signal to another TRP (e.g. TRP#2) of the serving cell. So, one panel is associated with one TRP. For example, panel#1 is associated with TRP#1, and panel#2 is associated with TRP#2. So, multi-panel multi-TRP scenario can be described as multi-panel/TRP.

Incidentally, in the following description, ‘PUSCH transmission’ may be abbreviated as ‘PUSCH’ , and ‘PUCCH resource’ may be abbreviated as ‘PUCCH’ .

For multi-DCI based multi-panel/TRP UL transmission, each TRP may independently send DCI scheduling PUSCH or PUCCH from the corresponding TRP. A UE may receive, from different TRPs, multiple (e.g. two) DCIs scheduling multiple fully-overlapped or partial-overlapped or non-overlapped PUSCH or PUCCH transmissions in one slot. A RRC parameter coresetPoolIndex with value 0 or 1 is configured for a CORESET for TRP differential. For example, all CORESETs configured for TRP#1 is configured with coresetPoolIndex with value 0, and all the CORESETs configured for TRP#2 is configured with coresetPoolIndex with value 1.

“Multi-panel/TRP simultaneous UL transmission” means the UE transmit UL signals from multiple panels (e.g. two panels) to multiple TRPs (e.g. two TRPs) simultaneously.

“Multi-DCI based multi-panel/TRP simultaneous UL transmission” means that the UL signals (PUSCH or PUCCH) transmitted from multiple (e.g. two) panels to multiple TRPs (e.g. two TRPs) simultaneously are scheduled by multiple (e.g. two) DCIs. For example, the UL signal (PUSCH or PUCCH) transmitted from panel#1 to TRP#1 is scheduled by one DCI associated with coresetPoolIndex with value 0 (e.g. from TRP#1) , and the UL signal (PUSCH or PUCCH) transmitted from panel#2 to TRP#2 is scheduled by another DCI associated with coresetPoolIndex with value 1 (e.g. from TRP#2) on the same symbol (s) .

Two UL (or joint) TCI states associated with different coresetPoolIndex values are activated or indicated for UL signal transmitted from two panels to two TRPs, and are referred to as two indicated UL TCI states. Each PUSCH or PUCCH may be associated with one of the two indicated UL TCI states. For example, a PUSCH or PUCCH scheduled by a DCI associated with coresetPoolIndex value 0 is transmitted from panel#1 to TRP#1 associated with coresetPoolIndex value 0 by using the first indicated UL TCI state associated with coresetPoolIndex value 0, and a PUSCH or PUCCH scheduled by a DCI associated with coresetPoolIndex value 1 is transmitted from panel#2 to TRP#2 by using the second indicated UL TCI state associated with coresetPoolIndex value 1.

UCI is uplink control information carried in PUCCH. UCI includes HARQ-ACK, CSI and/or SR. The UCI may be multiplexed in PUSCH, which means that the UCI carried by PUCCH may be transmitted by using the resources for the PUSCH transmission. The conditions for multiplexing UCI (e.g. HARQ-ACK and/or CSI) of PUCCH (s) in PUSCH are specified in clause 9.2.5 of 3GPP technical specification TS38.213 v17.0.0. The UE can only multiplex the HARQ-ACK and/or CSI information of the PUCCH in one PUSCH and does not transmit SR as specified in 3GPP technical specification TS38.213. If the UCI is determined to be multiplexed in a PUSCH transmission that is in response to a DCI format detection, the UE multiplexes CSI and HARQ-ACK in the PUSCH transmission. When the PUSCH transmission is not in response to a DCI format detection and the UE multiplexes only CSI reports, the timing conditions are not applicable.

As mentioned in the background part, the UE can only simultaneously transmit multiple (e.g. two) PUSCHs or multiple (e.g. two) PUCCHs from different (e.g. two) panels to different (e.g. two) TRPs in a carrier. For multi-DCI based multi-TRP/panel UL transmission, different values of coresetPoolIndex are configured for different CORESETs in a PDCCH configuration for a BWP of a cell. The UE can be scheduled by DCIs carried in PDCCHs from CORESETs configured with different values of coresetPoolIndex to transmit multiple PUSCHs and/or PUCCHs that are fully-overlapped or partially-overlapped or non-overlapped in time domain (e.g. in one slot) . However, the PUSCH and the PUCCH overlapped in the time domain (e.g. in one slot) associated with different values of coresetPoolIndex cannot be transmitted simultaneously. That is, PUSCH associated with a coresetPoolIndex value and PUCCH associated with the other coresetPoolIndex value cannot be overlapped in time domain in a carrier.

For all of PUSCH (s) and PUCCH (s) scheduled to be transmitted in one slot, the UE shall first prepare PUSCH (s) and PUCCH (s) in the one slot per panel (or per TRP) to ensure the PUSCH (s) and PUCCH (s) associated with a same panel (or a same TRP) can be transmitted in the one slot. For example, the UE may determine one PUSCH and one PUCCH, or two PUSCHs, or two PUCCHs associated with one panel/TRP in the one slot to be transmitted on non-overlapped symbols, and determine one PUSCH and one PUCCH, or two PUSCHs, or two PUCCHs associated with the other panel/TRP in the one slot to be transmitted on non-overlapped symbols.

The UE further checks whether the PUSCH (s) and PUCCH (s) associated with different panels/TRPs are overlapped (e.g. fully-overlapped or partially-overlapped) in the time domain (e.g. in the one slot) . If any of the PUSCH (s) associated with one panel/TRP is not overlapped with any of the PUCCH (s) associated with the other panel/TRP in time domain (e.g. in the one slot) , all PUSCH (s) and PUCCH (s) are transmitted.

Figure 1 illustrates an example for simultaneous multi-panel UL transmission in a carrier. PUSCH transmission#1 (PUSCH#1-1) and PUCCH resource#1 (PUCCH#1-1) are associated with Panel#1/TRP#1. PUSCH#1-1 associated with Panel#1/TRP#1 means that PUSCH#1-1 is transmitted from panel#1 to TRP#1. PUSCH transmission#2 (PUSCH#2-1) and PUCCH resource#2 (PUCCH#2-1) are associated with Panel#2/TRP#2. PUSCH#1-1 and PUSCH#2-1 are overlapped in time domain, and PUCCH#1-1 and PUCCH#2-1 are overlapped in time domain. On the other hand, any of PUSCH#1-1 and PUSCH#2-1 is not overlapped in time domain with any of PUCCH#1-1 and PUCCH#2-1. Accordingly, all of PUSCH#1-1, PUSCH#2-1, PUCCH#1-1 and PUCCH#2-1 can be transmitted.

Figure 2 illustrates an example in which there are PUSCH (s) and PUCCH (s) associated with different panels/TRPs overlapped in time domain (in the one slot) . The one slot in which at least one PUSCH associated with one panel/TRP is overlapped with at least one PUCCH associated with the other panel/TRP is referred to as overlapping slot. As shown in Figure 2, one PUCCH resource (e.g. PUCCH#1-1) associated with one panel/TRP (e.g. Panel#1/TRP#1) is overlapped (e.g. partially-overlapped) with a PUSCH transmission (e.g. PUSCH#2-1) associated with another panel/TRP (e.g. Panel#2/TRP#2) in slot n (i.e. overlapping slot n) .

Considering that the PUSCH and the PUCCH that are overlapped cannot be simultaneously transmitted, when a PUCCH (e.g. associated with one panel/TRP) overlaps with a PUSCH (e.g. associated with the other panel/TRP) in time domain (e.g. in one slot) , one of the overlapped PUCCH and the overlapped PUSCH shall be dropped.

If the overlapped PUCCH is dropped, the UCI (s) carried in the overlapped PUCCH may be multiplexed in a PUSCH in the same slot as the overlapped PUCCH (i.e. a PUSCH in the overlapping slot) if conditions for multiplexing UCI in the PUSCH is fulfilled.

The UE can transmit up to two PUSCHs or PUCCHs (e.g. two PUSCHs, or two PUCCHs, or one PUSCH and one PUCCH) associated with one panel/TRP in one slot. So, when there are PUSCH (s) and PUCCH (s) associated with different panels/TRPs overlapped in time domain in the overlapping slot, there can be different cases.

Case 1: one PUCCH associated with one panel/TRP is overlapped with one PUSCH associated with the other panel/TRP, and there is only one PUSCH associated with the other panel/TRP. That is, the only one PUSCH associated with the other panel/TRP is overlapped with the one PUCCH associated with the one panel/TRP. There can be no PUCCH or one PUCCH associated with the other panel/TRP.

Case 1-1: there is only one PUCCH associated with the one panel/TRP. Figure 3 illustrates an example of Case 1-1. PUCCH#1 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-1 associated with Panel#2/TRP#2.

Case 1-2: In addition to one PUCCH associated with the one panel/TRP, one PUSCH is associated with the same panel/TRP (i.e. the one panel/TRP) associated with the one PUCCH. Figure 4 illustrates an example of Case 1-2. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-1 associated with Panel#2/TRP#2. Another PUSCH transmission (PUSCH#1-1) is associated with the same panel/TRP (Panel#1/TRP#1) as PUCCH#1-1.

Case 2: one PUCCH associated with one panel/TRP is overlapped with one PUSCH associated with the other panel/TRP, and there are two PUSCHs associated with the other panel/TRP.

Case 2-1: there is only one PUCCH associated with the one panel/TRP. Figure 5 illustrates an example of Case 2-1. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-2 associated with Panel#2/TRP#2. PUSCH#2-1 is also associated with Panel#2/TRP#2. PUCCH#1-1 is not overlapped with PUSCH#2-1.

Case 2-2: In addition to one PUCCH associated with the one panel/TRP, one PUSCH is associated with the same panel/TRP (i.e. the one panel/TRP) associated with the one PUCCH. Figure 6 illustrates an example of Case 2-2. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-2 associated with Panel#2/TRP#2. PUSCH#2-1 is also associated with Panel#2/TRP#2. PUCCH#1-1 is not overlapped with PUSCH#2-1. Another PUSCH transmission (PUSCH#1-1) is associated with the same panel/TRP (Panel#1/TRP#1) as PUCCH#1-1.

Case 3: two PUCCHs associated with one panel/TRP are respectively overlapped with one PUSCH associated with the other panel/TRP, and there are two PUSCH transmissions associated with the other panel/TRP. Figure 7 illustrates an example of Case 3. Each of PUCCH#1-1 and PUCCH#1-2, both are associated with Panel#1/TRP#1, is overlapped with PUSCH#2-2 associated with Panel#2/TRP#2. PUSCH#2-1 is also associated with Panel#2/TRP#2. PUCCH#1-1 or PUCCH#1-2 is not overlapped with PUSCH#2-1.

Case 4: one PUCCH associated with one panel/TRP is overlapped with two PUSCHs associated with another panel/TRP.

Case 4-1: there is only one PUCCH associated with the one panel/TRP. Figure 8 illustrates an example of Case 4-1. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with both PUSCH#2-1 and PUSCH#2-2 associated with Panel#2/TRP#2.

Case 4-2: In addition to one PUCCH associated with the one panel/TRP, one PUSCH is associated with the same panel/TRP (i.e. the one panel/TRP) associated with the one PUCCH. Figure 9 illustrates an example of Case 4-2. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with both PUSCH#2-1 and PUSCH#2-2 associated with Panel#2/TRP#2. Another PUSCH transmission (PUSCH#1-1) is associated with the same panel/TRP (Panel#1/TRP#1) as PUCCH#1-1.

Case 5: one PUCCH associated with one panel/TRP is overlapped with one PUSCH associated with the other panel/TRP; and the other PUCCH associated with the one panel/TRP is overlapped with the other PUSCH associated with the other panel/TRP. Figure 10 illustrates an example of Case 5. PUCCH#1-1 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-1 associated with Panel#2/TRP#2. PUCCH#1-2 associated with Panel#1/TRP#1 is overlapped with PUSCH#2-2 associated with Panel#2/TRP#2.

There may be other cases in which there are two PUCCHs overlapped with PUSCHs. For these cases, each overlapped PUCCH belongs to one of the above-described cases.

For example, for a case illustrated in Figure 11, PUCCH#1-1 associated with panel#1/TRP#1 is overlapped with PUSCH#2-1 associated with panel#2/TRP#2, and PUCCH#1-2 associated with panel#1/TRP#1 is overlapped with both PUSCH#2-1 and PUSCH#2-2 associated with panel#2/TRP#2. If PUCCH#1-1 and PUCCH#1-2 are separately considered separately considered PUCCH#1-1 (it means that if it is assumed that PUCCH#1-2 does not exist (i.e. only PUCCH#1-1 is associated with panel#1/TRP#1) ) belongs to Case 2-1 (Figure 5) , and similarly, separately considered PUCCH#1-2 belongs to Case 4-1 (Figure 8) .

For another example, for a case illustrated in Figure 12, PUCCH#1-1 associated with panel#1/TRP#1 is overlapped with PUSCH#2-1 associated with panel#2/TRP#2, and PUCCH#2-1 associated with panel#2/TRP#2 is overlapped with PUSCH#1-1 associated with panel#1/TRP#1. PUCCH#1-1 belongs to Case 1-1 (Figure 3) . PUCCH#2-1 also belongs to Case 1-1 (Figure 3) if panel#2/TRP#2 is considered as the one panel/TRP and panel#1/TRP#1 is considered as the other panel/TRP.

Incidentally, if each overlapped PUCCH is separately considered, for Case 3 (Figure 7) , each of PUCCH#1-1 and PUCCH#1-2 may belong to Case 2-1 (Figure 5) . For Case 5 (Figure 10) , each of PUCCH#1-1 and PUCCH#1-2 can belong to Case 2-1 (Figure 5) .

For all of the cases, at least one PUCCH is overlapped with at least one PUSCH in one slot. Each PUCCH that is overlapped with at least one PUSCH is referred to as overlapped PUCCH. Each PUSCH that is overlapped with at least one PUCCH is referred to as overlapped PUSCH. The slot in which at least one PUCCH is overlapped with at least one PUSCH is referred to as overlapping slot.

The overlapped PUCCH may be a PUCCH with repetition or a PUCCH without repetition.

A first embodiment is related to the situation that the overlapped PUCCH is a PUCCH without repetition.

According to the first embodiment, the overlapped PUCCH is dropped (i.e. the overlapped PUSCH is transmitted) . In addition, when a condition for multiplexing the UCI carried in the overlapped PUCCH in a PUSCH is fulfilled, the UCI carried in the overlapped PUCCH is multiplexed in the PUSCH. On the other hand, if the condition for multiplexing the UCI carried in the overlapped PUCCH in the PUSCH is not fulfilled, the UCI carried in the overlapped PUCCH is not multiplexed in the PUSCH. In the first embodiment, it is assumed that the PUSCH in which the UCI carried in the overlapped PUCCH is multiplexed is a PUSCH without repetition. Different solutions for determining the PUSCH in which the UCI carried in the overlapped PUCCH is multiplexed are proposed.

Solution 1: if there is a PUSCH (referred to as first PUSCH) associated with the same panel/TRP as the overlapped PUCCH in the overlapping slot and the first PUSCH is not overlapped with any PUCCH, the UCI carried in the overlapped PUCCH is multiplexed in the first PUSCH, if the condition to multiplex the UCI carried in the overlapped PUCCH in the first PUSCH is fulfilled.

Solution 1 applies to Case 1-2 (Figure 4) , Case 2-2 (Figure 6) , and Case 4-2 (Figure 9) , as illustrated by “Solution 1” in each of Figures 4, 6, and 9.

Solution 2: if the overlapped PUCCH is overlapped with only one PUSCH (referred to as second PUSCH) , the UCI carried in the overlapped PUCCH is multiplexed in the second PUSCH if the condition to multiplex the UCI carried in the overlapped PUCCH in the second PUSCH is fulfilled. Solution 2 requires UE capability that can multiplex UCI associated with one panel/TRP in a PUSCH associated with the other panel/TRP.

Solution 2 applies to Case 1-1 (Figure 3) , Case 1-2 (Figure 4) , Case 2-1 (Figure 5) , Case 2-2 (Figure 6) , Case 3 (Figure 7: for each of PUCCH#1-1 and PUCCH#1-2) , and Case 5 (Figure 10: for each of PUCCH#1-1 and PUCCH#1-2) , as illustrated by “Solution 2” in each of Figures 3, 4, 5, 6, 7, and 10.

Solution 3: if there are multiple (e.g. two) PUSCHs associated with the other panel/TRP transmitted in the overlapping slot, the UCI carried in the overlapped PUCCH (which is associated with one panel/TRP) is multiplexed in the first of the multiple PUSCHs associated with the other panel/TRP transmitted in the overlapping slot (which may be referred to as third PUSCH) if the condition to multiplex the UCI carried in the overlapped PUCCH in the third PUSCH is fulfilled. Solution 3 requires UE capability that can multiplex UCI associated with a panel/TRP in a PUSCH associated with the other panel/TRP.

Solution 3 applies to Case 2-1 (Figure 5) , Case 2-2 (Figure 6) , Case 3 (Figure 7: for each of PUCCH#1-1 and PUCCH#1-2) , Case 4-1 (Figure 8) , Case 4-2 (Figure 9) and Case 5 (Figure 10: for each of PUCCH#1-1 and PUCCH#1-2) , as illustrated by “Solution 3” in each of Figures 5 to 10.

Note that, if there are multiple (e.g. two) PUSCHs associated with the other panel/TRP transmitted in the overlapping slot and the overlapped PUCCH is overlapped with the first of the multiple PUSCH, the second PUSCH and the third PUSCH may refer to the same PUSCH. For example, in Figure 11, for PUCCH#1-1, PUSCH#2-1 is both the second PUSCH (the only one PUSCH overlapped with PUCCH#1-1) and the third PUSCH (the first of the multiple PUSCHs associated with the other panel/TRP transmitted in the overlapping slot) .

Solution 4: if there are multiple (e.g. two) PUSCHs associated with the other panel/TRP transmitted in the overlapping slot and one PUSCH (referred to as fourth PUSCH) is in response to a DCI format detection and the other PUSCH is not in response to a DCI format detection, the UCI carried in the overlapped PUCCH (which is associated with one panel/TRP) is multiplexed in the fourth PUSCH in response to a DCI format detection if the condition to multiplex the UCI carried in the overlapped PUCCH in the fourth PUSCH is fulfilled. In particular, the HARQ-ACK and/or CSI information contained in the UCI carried in the overlapped PUCCH are multiplexed in the fourth PUSCH in response to a DCI format detection. Solution 4 requires UE capability that can multiplex UCI associated with a panel/TRP in a PUSCH associated with another panel/TRP.

Solution 4 may apply to Case 2-1 (Figure 5) , Case 2-2 (Figure 6) , Case 3 (Figure 7) , Case 4-1 (Figure 8) , Case 4-2 (Figure 9) and Case 5 (Figure 10) , if one of PUSCH#2-1 and PUSCH#2-2 is in response to a DCI format detection and the other of PUSCH#2-1 and PUSCH#2-2 is not in response to a DCI format detection.

For each of solutions 1 to 3, if the PUSCH (e.g. the first PUSCH, the second PUSCH, or the third PUSCH) in which the UCI carried in the overlapped PUCCH is multiplexed is a PUSCH in response to a DCI format detection, the HARQ-ACK and/or CSI information contained in the UCI carried in the overlapped PUCCH are multiplexed in the PUSCH. On the other hand, if the PUSCH (e.g. the first PUSCH, the second PUSCH, or the third PUSCH) in which the UCI carried in the overlapped PUCCH is multiplexed is a PUSCH not in response to a DCI format detection, only the CSI information is multiplexed in the PUSCH.

A second embodiment is related to the situation that the overlapped PUCCH is a PUCCH without repetition and the PUSCH in which the UCI carried in the overlapped PUCCH is multiplexed is a PUSCH with repetition.

According to the second embodiment, the overlapped PUCCH is dropped (and the overlapped PUSCH is transmitted) . In addition, one of the first PUSCH, the second PUSCH, the third PUSCH and the fourth PUSCH determined in the first embodiment is determined as a fifth PUSCH in which the UCI carried in the overlapped PUCCH is multiplexed if a condition for multiplexing the UCI carried in the overlapped PUCCH in the fifth PUSCH is fulfilled. The fifth PUSCH is a PUSCH with repetition. The UCI carried in the overlapped PUCCH is only multiplexed in the fifth PUSCH in the overlapping slot, but not in other repetitions of the fifth PUSCH, where the other repetitions of the fifth PUSCH refer to the repetitions of the fifth PUSCH in other slot (s) other than the overlapping slot.

A third embodiment is related to the situation that the overlapped PUCCH is a PUCCH with repetition, and the PUSCH candidate (i.e. one of the first PUSCH, the second PUSCH, the third PUSCH and the fourth PUSCH determined in the first embodiment) in which the UCI carried in the overlapped PUCCH may be multiplexed is a PUSCH without repetition.

According to the third embodiment, the overlapped PUCCH, which is a PUCCH with repetition, is dropped (and the overlapped PUSCH is transmitted) . The UCI carried in the overlapped PUCCH is not multiplexed in the PUSCH candidate which is a PUSCH without repetition.

A fourth embodiment is related to the situation that the overlapped PUCCH is a PUCCH with repetition, and the PUSCH candidate (i.e. one of the first PUSCH, the second PUSCH, the third PUSCH and the fourth PUSCH determined in the first embodiment) in which the UCI carried in the overlapped PUCCH may be multiplexed is also a PUSCH with repetition.

According to the fourth embodiment, if the PUSCH candidate in which the UCI carried in the overlapped PUCCH is multiplexed, which is also a PUSCH with repetition, is the overlapped PUSCH (e.g. the second PUSCH determined according to solution 2) , one of the overlapped PUCCH and the overlapped PUSCH is dropped (and the other of overlapped PUCCH and the overlapped PUSCH is transmitted) . For example, the overlapped PUSCH that has a lower priority than the overlapped PUCCH is dropped. If the PUSCH candidate in which the UCI carried in the overlapped PUCCH is multiplexed, which is also a PUSCH with repetition, is not the overlapped PUSCH (e.g. determined according to solution 1 or solution 3 or Solution 4) , the overlapped PUCCH is dropped (and the overlapped PUSCH is transmitted) . The UCI carried in the overlapped PUCCH is not multiplexed in the PUSCH candidate.

Figure 13 is a schematic flow chart diagram illustrating an embodiment of a method 1300 according to the present application. In some embodiments, the method 1300 is performed by an apparatus, such as a remote unit (e.g. UE) . In certain embodiments, the method 1300 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 1300 is a method performed at a UE, comprising: 1302 receiving DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and 1304 dropping, for each of the overlapped PUCCH resource (s) , one of the overlapped PUCCH resource and the overlapped PUSCH transmission. One of the overlapped PUCCH resource and the overlapped PUSCH transmission for each of the overlapped PUCCH resource (s) being dropped means that when the scheduled PUCCH resource (s) and PUSCH transmission (s) in the one slot are transmitted, one of the overlapped PUCCH resource and the overlapped PUSCH transmission for each of the overlapped PUCCH resource (s) is not transmitted (which implies that the other of the overlapped PUCCH resource and the overlapped PUSCH transmission for each of the overlapped PUCCH resource (s) is transmitted) .

In one embodiment, the method comprises, for each of the overlapped PUCCH resource (s) , dropping the overlapped PUCCH resource, and the method further comprise multiplexing the UCI carried in the overlapped PUCCH resource in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.

In particular, if a first PUSCH transmission and the overlapped PUCCH resource are scheduled to be associated with the same coresetPoolIndex value in the one slot, and the first PUSCH transmission is not overlapped with any PUCCH resource, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first PUSCH transmission.

If the overlapped PUCCH resource is overlapped with only one PUSCH transmission, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one PUSCH transmission.

If two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first of the two PUSCH transmissions.

If two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, and one of the two PUSCH transmissions is in response to a DCI format detection and the other of the two PUSCH transmissions is not in response to a DCI format detection, then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one of the two PUSCH transmissions that is in response to a DCI format detection.

Figure 14 is a schematic flow chart diagram illustrating an embodiment of a method 1400 according to the present application. In some embodiments, the method 1400 is performed by an apparatus, such as a base unit. In certain embodiments, the method 1400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 1400 may comprise 1402 transmitting DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and 1404 receiving, for each of the overlapped PUCCH resource (s) , one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In one embodiment, the method comprises receiving, for each of the overlapped PUCCH resource (s) , the overlapped PUSCH transmission, and further comprises receiving the UCI carried in the overlapped PUCCH resource multiplexed in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.

Referring to Figure 15, the UE (i.e. the remote unit) includes a processor, a memory, and a transceiver. The processor implements a function, a process, and/or a method which are proposed in Figure 13.

The UE comprises a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to receive, via the transceiver, DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and for each of the overlapped PUCCH resource (s) , drop one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In one embodiment, the processor is configured to, for each of the overlapped PUCCH resource (s) , drop the overlapped PUCCH resource; and multiplex the UCI carried in the overlapped PUCCH resource in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.

The gNB (i.e. the base unit) includes a processor, a memory, and a transceiver. The processor implements a function, a process, and/or a method which are proposed in Figure 14.

The base unit comprises a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to transmit, via the transceiver, DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and for each of the overlapped PUCCH resource (s) , receive, via the transceiver, one of the overlapped PUCCH resource and the overlapped PUSCH transmission.

In one embodiment, the processor is configured to, for each of the overlapped PUCCH resource (s) , receive, via the transceiver, the overlapped PUSCH transmission; and receive, via the transceiver, the UCI carried in the overlapped PUCCH resource multiplexed in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.

Layers of a radio interface protocol may be implemented by the processors. The memories are connected with the processors to store various pieces of information for driving the processors. The transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.

The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.

In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.

The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated in the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

A user equipment (UE) , comprising:

a transceiver; and

a processor coupled to the transceiver, wherein the processor is configured to receive, via the transceiver, DCIs associated with two different values of

coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and

for each of the overlapped PUCCH resource (s) , drop one of the overlapped PUCCH resource and the overlapped PUSCH transmission.
The UE of claim 1, wherein, the processor is configured to, for each of the overlapped PUCCH resource (s) ,

drop the overlapped PUCCH resource; and

multiplex the UCI carried in the overlapped PUCCH resource in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.
The UE of claim 2, wherein,

if a first PUSCH transmission and the overlapped PUCCH resource are scheduled to be associated with the same coresetPoolIndex value in the one slot, and

the first PUSCH transmission is not overlapped with any PUCCH resource,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first PUSCH transmission.
The UE of claim 2, wherein,

if the overlapped PUCCH resource is overlapped with only one PUSCH transmission,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one PUSCH transmission.
The UE of claim 2, wherein,

if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first of the two PUSCH transmissions.
The UE of claim 2, wherein,

if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, and

one of the two PUSCH transmissions is in response to a DCI format detection and the other of the two PUSCH transmissions is not in response to a DCI format detection,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one of the two PUSCH transmissions that is in response to a DCI format detection.
The UE of claim 2, wherein, if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is in response to a DCI format detection, the UCI includes HARQ-ACK and/or CSI information, and if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is not in response to a DCI format detection, the UCI only includes CSI information.
A method performed at a user equipment (UE) , comprising:

receiving DCIs associated with two different values of coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and

dropping, for each of the overlapped PUCCH resource (s) , one of the overlapped PUCCH resource and the overlapped PUSCH transmission.
A base unit, comprising:

a transceiver; and

a processor coupled to the transceiver, wherein the processor is configured to transmit, via the transceiver, DCIs associated with two different values of

coresetPoolIndex scheduling, in a same BWP with a same SCS, UL transmissions in one slot, wherein, the scheduled UL transmissions in the one slot include one or two UL transmissions associated with one coresetPoolIndex value and one or two UL transmissions associated with another coresetPoolIndex value, each UL transmission is a PUSCH transmission or PUCCH resource, and at least one PUCCH resource associated with one coresetPoolIndex value is overlapped with at least one PUSCH transmission associated with the other coresetPoolIndex value; and

for each of the overlapped PUCCH resource (s) , receive, via the transceiver, one of the overlapped PUCCH resource and the overlapped PUSCH transmission.
The base unit of claim 9, wherein, the processor is configured to, for each of the overlapped PUCCH resource (s) ,

receive, via the transceiver, the overlapped PUSCH transmission; and

receive, via the transceiver, the UCI carried in the overlapped PUCCH resource multiplexed in a PUSCH transmission transmitted in the one slot, if a condition for multiplexing the UCI carried in the overlapped PUCCH resource in the PUSCH transmission is fulfilled.
The base unit of claim 10, wherein,

if a first PUSCH transmission and the overlapped PUCCH resource are scheduled to be associated with the same coresetPoolIndex value in the one slot, and

the first PUSCH transmission is not overlapped with any PUCCH resource,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first PUSCH transmission.
The base unit of claim 10, wherein,

if the overlapped PUCCH resource is overlapped with only one PUSCH transmission,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one PUSCH transmission.
The base unit of claim 10, wherein,

if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the first of the two PUSCH transmissions.
The base unit of claim 10, wherein,

if two PUSCH transmissions are scheduled to be associated with the other coresetPoolIndex value, and

one of the two PUSCH transmissions is in response to a DCI format detection and the other of the two PUSCH transmissions is not in response to a DCI format detection,

then, the UCI carried in the overlapped PUCCH resource is multiplexed in the one of the two PUSCH transmissions that is in response to a DCI format detection.
The base unit of claim 10, wherein, if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is in response to a DCI format detection, the UCI includes HARQ-ACK and/or CSI information, and if the PUSCH transmission in which the UCI carried in the overlapped PUCCH resource is multiplexed is not in response to a DCI format detection, the UCI only includes CSI information.