Method and apparatus for uplink transmission to multiple transmission reception points in mobile communication

Abstract

Various solutions are described regarding uplink transmissions by a mobile communication device to multiple transmission reception points. The device can determine that a first physical uplink shared channel (PUSCH) contains a channel state information (CSI) report. The device can determine that a second physical uplink shared channel contains data. The first physical uplink shared channel and the second physical uplink shared channel can be associated with a control resource set (CORESET) pool index value. The device can determine whether the first physical uplink shared channel overlaps in a time domain with the second physical uplink shared channel. The device can transmit the second physical uplink shared channel containing the data if the first physical uplink shared channel overlaps in the time domain with the second physical uplink shared channel.

Description

[0001] Cross-referencing

[0002] This disclosure is part of a non-provisional application claiming priority interest, U.S. Patent Application No. 63 / 518,113, filed August 8, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to uplink transmissions between mobile communication devices and multiple transceiver points. Background Technology

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the claims listed below, and are not recognized as prior art by virtue of being included in this section.

[0005] In Long-Term Evolution (LTE) or New Radio (NR) mobile communications, the concept of a transmission-reception point (TRP) has been introduced. Specifically, a TRP is a network node equipped with a set of geographically co-located antennas (e.g., an antenna array) that supports both transmission point (TP) and / or reception point (RP) functions.

[0006] Furthermore, to enhance communication flexibility, multiple Transmitter Receiver Point (MTRP) technology was developed. Under the MTRP architecture, the serving cell can schedule user equipment (UE) from multiple TRPs to provide better coverage, reliability, and / or data rates. In some scenarios, multiple downlink control information (multi-DCI) is used to schedule UEs under the MTRP architecture, meaning the UE is scheduled by DCIs from different TRPs. Therefore, multiple physical uplink shared channels (PUSCHs) may be scheduled for the UE based on the DCI. However, when scheduled PUSCHs overlap, the UE may not be able to handle this situation, potentially leading to significant transmission errors, especially if the overlapping PUSCHs are associated with the same TRP.

[0007] Therefore, in newly developed wireless communication networks, how to handle the overlapping of PUSCHs scheduled under the MTRP architecture (especially those associated with the same TRP) has become an important issue, and there is an urgent need to provide appropriate solutions to handle this situation. Summary of the Invention

[0008] The following summary is for illustrative purposes only and is not intended to limit in any way. That is, the following summary aims to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further illustrated in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] The objective of this disclosure is to propose a solution or scheme to address the uplink transmission problem to multiple transmitting and receiving points related to mobile communication devices.

[0010] In one aspect, a method may involve a device determining that a first Physical Uplink Shared Channel (PUSCH) contains Channel State Information (CSI) reports. The method may also involve a device determining that a second Physical Uplink Shared Channel contains data. The first and second Physical Uplink Shared Channels may be associated with a Control Resource Set (CORESET) pool index value. The method may further involve a device determining whether the first Physical Uplink Shared Channel overlaps with the second Physical Uplink Shared Channel in the time domain. The method may also involve a device transmitting the second Physical Uplink Shared Channel containing data if the first Physical Uplink Shared Channel overlaps with the second Physical Uplink Shared Channel in the time domain.

[0011] In one aspect, an apparatus may include a transceiver that wirelessly communicates with at least one network node of a wireless network during operation. The apparatus may also include a processor communicatively connected to the transceiver. During operation, the processor may perform operations including determining that a first physical uplink shared channel contains channel state information reports. The processor may also perform operations including determining that a second physical uplink shared channel contains data. The first and second physical uplink shared channels may be associated with a control resource set pool index value. The processor may also perform operations including determining whether the first physical uplink shared channel overlaps with the second physical uplink shared channel in the time domain. The processor may also perform operations including, if the first physical uplink shared channel overlaps with the second physical uplink shared channel in the time domain, transmitting the second physical uplink shared channel containing data via the transceiver.

[0012] It is worth noting that although the descriptions provided herein may be made in the context of certain wireless access technologies, networks, and network topologies (e.g., Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR), Internet of Things (IoT) and Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), and 6G), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of wireless access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0013] The accompanying drawings are included to provide a further understanding of the present disclosure and form part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. It will be understood that the drawings are not necessarily to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the present disclosure.

[0014] Figure 1 This is a schematic diagram based on the implementation scheme disclosed herein.

[0015] Figure 2 This is a schematic diagram based on the implementation scheme disclosed herein.

[0016] Figure 3 This is a schematic diagram based on the implementation scheme disclosed herein.

[0017] Figure 4 This is a schematic diagram based on the implementation scheme disclosed herein.

[0018] Figure 5 This is a block diagram describing an example communication system according to embodiments of the present disclosure.

[0019] Figure 6 This is a flowchart describing an example process according to embodiments of the present disclosure. Detailed Implementation

[0020] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative examples of the claimed subject matter, which can be embodied in various forms. This disclosure can be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are intended to make the description of this disclosure comprehensive and complete, and to fully convey the scope of this disclosure to those skilled in the art. Details of well-known features and techniques may be omitted in the following description to avoid unnecessarily obscuring the presented embodiments and implementations.

[0021] Overview

[0022] The embodiments of this disclosure relate to various technologies, methods, schemes, and / or solutions for multiple transmission-reception point (MTRP) uplink (UL) transmissions associated with mobile communication devices. According to this disclosure, many possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of them may be implemented in one or another combination.

[0023] Regarding this disclosure, a user equipment (UE) compliant with MTRP technology can receive downlink control information (DCI) from a network node. Based on different DCIs, the UE can determine different physical uplink shared channels (PUSCHs). In some cases, one PUSCH may contain channel state information (CSI) reports, another PUSCH may contain data, and both PUSCHs are associated with the same control resource set (CORESET) pool index value (i.e., associated with the same network node such as the TRP). In these cases, the UE can determine whether the PUSCHs overlap in the time domain. If yes, the UE can transmit the PUSCH containing data to the network node (e.g., the TRP) corresponding to the CORESET pool index value. More specifically, the UE can discard the PUSCH containing CSI reports and only transmit the PUSCH containing data to the network node (e.g., the TRP) corresponding to the CORESET pool index value.

[0024] Figure 1 An example scenario 100 is illustrated under a scheme according to an embodiment of this disclosure. Scenario 100 involves at least one network node, a UE, and a TRP, which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Scenario 100 illustrates a current network framework. The UE may connect to the network side. The network side may include one or more network nodes, including one or more TRPs. The UE may be compatible with MTRP technology.

[0025] In some embodiments, the UE can receive the DCI from a network node. For example, the UE receives the DCI directly from the network node (or via at least one TRP). Based on a DCI, the UE can determine a first PUSCH containing a CSI report (e.g., a semi-persistent CSI report). In other words, the UE can determine a first PUSCH for transmitting the CSI report based on the DCI. Based on another DCI, the UE can determine a second PUSCH containing data.

[0026] If it is determined that the first PUSCH and the second PUSCH are associated with the same CORESET pool index value (i.e., it is determined that the first PUSCH and the second PUSCH will be transmitted to the same TRP), the UE can determine whether the first PUSCH overlaps with the second PUSCH in the time domain. If it is determined that the first PUSCH overlaps with the second PUSCH in the time domain, the UE can transmit the second PUSCH containing data to the TRP corresponding to the CORESET pool index value.

[0027] More specifically, since the second PUSCH containing data may have a higher priority than the first PUSCH containing CSI reports, the UE may decide not to transmit the first PUSCH containing CSI reports (i.e., the UE may discard / suspend / delay) and only transmit the second PUSCH containing data to the TRP corresponding to the CORESET pool index value.

[0028] In some implementations, the first PUSCH can be determined not to be transmitted based on the UE's capability information. This is particularly true when the UE's capabilities are limited (e.g., a limited number of transmitting / receiving units), the UE may not be able to transmit all PUSCHs to the same TRP within a specific time interval. Therefore, the first PUSCH with lower priority may be discarded by the UE based on its capability information.

[0029] In some implementations, the first PUSCH and the second PUSCH can be determined to be associated with the same TRP based on the CORESET pool index value. Figure 2An example scenario 200 is illustrated under a scheme according to an embodiment of this disclosure. For example, based on receiving a first DCI, the UE determines: (1) a CORESET #X, associated with a CORESET pool index value #A, for use in the first TRP; and (2) a first PUSCH scheduled by the first DCI corresponding to CORESET #X transmitted to the first TRP. Therefore, the first PUSCH transmitted to the first TRP is determined to be associated with the CORESET pool index value #A. Based on receiving a second DCI, the UE determines: (1) a CORESET #Y, associated with a CORESET pool index value #B, for use in the second TRP; and (2) a second PUSCH scheduled by the second DCI corresponding to CORESET #Y transmitted to the second TRP. Therefore, the second PUSCH transmitted to the second TRP is determined to be associated with the CORESET pool index value #B.

[0030] Then, if the control resource set pool index value #A and the control resource set pool index value #B are the same (i.e., A=B), this means that control resource set #X and control resource set #Y are the same control resource set. Therefore, the UE determines that the first Transmit Receive Point (TRP) using control resource set #X and the second Transmit Receive Point (TRP) using control resource set #Y are the same TRP. Furthermore, the UE determines that the first Physical Uplink Shared Channel (PUSCH) associated with control resource set pool index value #A and the second Physical Uplink Shared Channel (PUSCH) associated with control resource set pool index value #B will be transmitted to the same TRP (i.e., the first and second PUSCHs are associated with the same TRP).

[0031] In some implementations, the UE may receive higher-level configuration containing control resource set pool index values ​​from a network node (directly or via at least one TRP). The higher-level configuration may include Radio Resource Control (RRC) configuration.

[0032] Figure 3 and Figure 4 Example scenarios 300 and 400 are shown, illustrating implementations according to this disclosure. In some implementations, the first physical uplink shared channel and the second physical uplink shared channel associated with the same control resource set pool index value (i.e., associated with the same TRP) may overlap in one or more symbols on the same carrier. Furthermore, the first physical uplink shared channel and the second physical uplink shared channel overlapping in one or more symbols on the same carrier may: (1) overlap completely or partially in the frequency domain; or (2) not overlap in the frequency domain.

[0033] To illustrate with a detailed example, upon receiving the RRC configuration, the UE configures itself via a parameter (e.g., PDCCH-Config as defined in the 3GPP specification) containing two distinct values ​​(e.g., 0 and 1) for the Control Resource Set Pool Index associated with the two Control Resource Sets. The UE also configures itself via a feature enable parameter (e.g., enableSTx2PofmDCI as defined in the 3GPP specification). When the UE determines that two overlapping Physical Uplink Shared Channels (PLS-S) are associated with the same Control Resource Set Pool Index value (i.e., two overlapping PLS-S associated with the same TRP), only the PLS-S with higher priority will be transmitted, while the PLS-S with lower priority will be discarded. In some cases, if the UE will transmit a first PLS-S containing semi-persistent Channel State Information (SSE) reports and a second PLS-S containing uplink shared channel data on the same carrier, and the transmission of the first PLS-S will overlap with the transmission of the second PLS-S in the time domain, the UE will not transmit the first PLS-S and will instead transmit the second PLS-S. The UE expects the first and second physical uplink shared channel transmissions to satisfy the above timing conditions so that the physical uplink shared channel transmissions overlap in time when at least one first or second physical uplink shared channel transmission is in response to the UE's DCI format detection.

[0034] Example Implementation

[0035] Figure 5 An example communication system 500 is shown, which has an example communication device 510 and an example network device 520, according to an implementation of this disclosure. Each of the communication device 510 and the network device 520 can perform various functions to implement the schemes, techniques, processes and methods described herein, relating to uplink transmissions of network devices in user equipment and mobile communications, including the scenarios / schemes described above and the process 600 described below.

[0036] Communication device 510 may be part of an electronic device, which may be a UE (e.g., a portable or mobile device, a wearable device, a wireless communication device, or a computing device). For example, communication device 510 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. Communication device 510 may also be part of a machine-type device, which may be an Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) device, such as a stationary or fixed device, a home device, a wired communication device, or a computing device. For example, communication device 510 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, communication device 510 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. Communication device 510 may include Figure 5 At least some components shown in the diagram (e.g., processor 512). The communication device 510 may also include one or more other components unrelated to the scheme of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, these components of the communication device 510 are not... Figure 5 The text shown is not described below to keep it concise and brief.

[0037] Network device 520 may be part of a network device, which may be a network node such as a satellite, base station, TRP, small cell, router, or gateway. For example, network device 520 may be implemented in an eNodeB in an LTE network, in a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or in a satellite or base station in a 6G network. Alternatively, network device 520 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 520 may include... Figure 5 At least some components are shown, such as processor 522. Network device 520 may also include one or more other components unrelated to the proposed solutions of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, for simplicity and brevity, these components of network device 520 are not listed in the above description. Figure 5 The text is not shown below.

[0038] In one aspect, each of processors 512 and 522 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 512 and 522, each of processors 512 and 522 may include multiple processors in some implementations of this disclosure, and may include a single processor in other implementations. In another aspect, each of processors 512 and 522 may be implemented in hardware (and optionally, firmware) in which electronic components include, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, which are configured and arranged to achieve a particular purpose according to this disclosure. In other words, in at least some implementations, each of processors 512 and 522 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including autonomous reliability enhancements in devices (e.g., represented by communication device 510) and networks (e.g., represented by network device 520), according to various implementations of this disclosure.

[0039] In some implementations, communication device 510 may further include a transceiver 516 connected to processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, communication device 510 may further include a memory 514 connected to processor 512 and capable of being accessed by processor 512 and storing data. In some implementations, network device 520 may further include a transceiver 526 connected to processor 522 and capable of wirelessly transmitting and receiving data. In some implementations, network device 520 may further include a memory 524 connected to processor 522 and capable of being accessed by processor 522 and storing data. Therefore, communication device 510 and network device 520 can wirelessly communicate via transceiver 516 and transceiver 526, respectively. To aid in better understanding, the following description of the operation, functions, and capabilities of communication device 510 and network device 520 is provided in the context of a mobile communication environment, where communication device 510 is implemented as or acts as a communication device or UE, and network device 520 is implemented as or acts as a network node and / or TRP of a communication network.

[0040] In some implementations, processor 512 can determine that the first physical uplink shared channel contains channel state information reports. Processor 512 can determine that the second physical uplink shared channel contains data. The first and second physical uplink shared channels can be associated with a control resource set pool index value. Processor 512 can determine whether the first physical uplink shared channel overlaps with the second physical uplink shared channel in the time domain. If the first physical uplink shared channel overlaps with the second physical uplink shared channel in the time domain, processor 512 can transmit the second physical uplink shared channel containing data to the network node corresponding to the control resource set pool index value via transceiver 516.

[0041] In some implementations, processor 512 may determine not to send the first physical uplink shared channel containing a channel state information report.

[0042] In some implementations, the first physical uplink shared channel can be determined not to transmit based on the capability information of the communication device 510.

[0043] In some implementations, the capability information of the communication device 510 may include the number of transmitting units and the number of receiving units.

[0044] In some implementations, processor 512 can receive high-level configuration containing control resource set pool index values ​​via transceiver 516.

[0045] In some implementations, higher-level configurations may include Radio Resource Control (RRC) configurations.

[0046] In some implementations, channel state information reports may include semi-persistent channel state information reports.

[0047] In some implementations, the first physical uplink shared channel may overlap with the second physical uplink shared channel in one or more symbols on the same carrier.

[0048] In some implementations, the first physical uplink shared channel may completely or partially overlap with the second physical uplink shared channel in the frequency domain.

[0049] In some implementations, the first physical uplink shared channel does not overlap with the second physical uplink shared channel in the frequency domain.

[0050] Example process

[0051] Figure 6An example process 600 according to an embodiment of this disclosure is illustrated. Process 600 may be part or all of the above-described scenario / scheme, involving uplink transmission to multiple network nodes containing the TRP of this disclosure. Process 600 may represent one aspect of the implementation of features of communication device 510. Process 600 may include one or more operations, actions, or functions shown by one or more blocks from block 610 to block 640. Although shown as discrete blocks, the individual blocks of process 600 may be divided into more blocks, merged into fewer blocks, or eliminated as required by the desired implementation. Furthermore, the blocks of process 600 may be arranged according to... Figure 6 The process can be executed in the order shown, or in a different order. Process 600 can be implemented by communication device 510 or any suitable UE or machine type device. For illustrative purposes only and without limitation, process 600 is described below in the context of communication device 510. Process 600 may begin with block 610.

[0052] In block 610, process 600 may involve the processor 512 of communication device 510 determining that the first PUSCH contains a CSI report. Process 600 can proceed from block 610 to block 620.

[0053] In block 620, process 600 may involve the processor 512 of communication device 510 determining that the second PUSCH contains data. The first and second PUSCHs may be associated with CORESET pool index values. Process 600 may proceed from block 620 to block 630.

[0054] In block 630, process 600 may involve the processor 512 of communication device 510 determining whether the first PUSCH overlaps with the second PUSCH in the time domain. Process 600 can proceed from block 630 to block 640.

[0055] In block 640, process 600 may involve the processor 512 of communication device 510 transmitting a second PUSCH containing data when the first PUSCH overlaps with the second PUSCH in the time domain.

[0056] In some embodiments, process 600 may involve the processor 512 of communication device 510 determining not to send a first PUSCH containing a channel state information report.

[0057] In some embodiments, the first PUSCH may be determined not to be transmitted based on the capability information of the communication device 510.

[0058] In some embodiments, the capability information of the communication device 510 may include the number of transmitting units and the number of receiving units.

[0059] In some embodiments, process 600 may involve the processor 512 of communication device 510 receiving a higher-level configuration containing a control resource set pool index value.

[0060] In some embodiments, the higher-level configuration may include a Radio Resource Control (RRC) configuration.

[0061] In some embodiments, the channel state information report may include a semi-persistent channel state information report.

[0062] In some embodiments, the first PUSCH may overlap with the second PUSCH in one or more symbols on the same carrier.

[0063] In some embodiments, the first PUSCH may completely or partially overlap with the second PUSCH in the frequency domain.

[0064] In some embodiments, the first PUSCH does not overlap with the second PUSCH in the frequency domain.

[0065] Additional Notes

[0066] The topics described herein sometimes demonstrate different components contained within or connected to different other components. It should be understood that the architectures shown are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” in order to achieve the desired functionality. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” in order to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operationally connected” or “operationally coupled” to achieve the desired functionality, and any two components that can be suchly associated can also be considered “operationally coupled” to achieve the desired functionality. Specific examples of operational coupling include, but are not limited to, physically connectable and / or physically interactive components and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0067] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those with technical skills may appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. Various singular / plural arrangements can be explicitly listed here for clarity.

[0068] Furthermore, those skilled in the art will understand that, in general, the terms used herein, particularly in the appended claims, such as the body of the appended claims, are typically considered "open" terms. For example, the term "comprising" should be interpreted as "comprising but not limited to," the term "having" should be interpreted as "having at least," and the term "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also further understand that if a particular quantity introduced in a claim is intentional, such intention will be explicitly stated in the claim, and where there is no such statement, such intention does not exist. For example, to aid understanding, the appended claims below may contain the use of introductory phrases "at least one" and "one or more" to introduce the claim statement. However, the use of these phrases should not be construed as implying that introducing the claim statement with the indefinite article "a" or "an" would limit any particular claim containing such an introductory claim statement to containing only one such statement, even if the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to the use of definite articles used to introduce the claim statement. Furthermore, even if a specific number is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated number. For example, the simple statement "two statements" without other modifiers means at least two statements, or two or more statements. Additionally, when using conventions such as "at least one A, B, and C," generally, this structure is understood by those skilled in the art to mean the convention. For example, "a system having at least one A, B, and C" includes, but is not limited to, a system having only A, a system having only B, a system having only C, a system with A and B together, a system with A and C together, a system with B and C together, and / or a system with A, B, and C together, etc. Similarly, when using conventions such as "at least one A, B, or C," generally, this structure is understood by those skilled in the art to mean the convention. For example, "a system having at least one A, B, or C" includes, but is not limited to, a system having only A, a system having only B, a system having only C, a system with A and B together, a system with A and C together, a system with B and C together, and / or a system with A, B, and C together, etc. Those skilled in the art will further understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to include the possibility of one, any, or both terms. For example, the phrase “A or B” would be understood to include the possibility of “A” or “B” or “A and B”.

[0069] As can be understood from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: A processor of a device determines a first physical uplink shared channel containing a channel state information report; The processor determines that a second physical uplink shared channel contains data, wherein the first physical uplink shared channel and the second physical uplink shared channel are associated with a control resource set pool index value; The processor determines whether the first physical uplink shared channel and the second physical uplink shared channel overlap in the time domain; and When the first physical uplink shared channel and the second physical uplink shared channel overlap in the time domain, the processor transmits the second physical uplink shared channel containing the data.

2. The method of claim 1, further comprising: The processor determines not to transmit the first physical uplink shared channel containing the channel status information report.

3. The method of claim 2, wherein the first physical uplink shared channel is determined not to transmit based on a capability information of the device.

4. The method of claim 3, wherein the capability information of the device includes the number of transmitting units and the number of receiving units.

5. The method of claim 1, further comprising: The processor receives a higher-level configuration containing the index value of the control resource set pool.

6. The method of claim 5, wherein the higher-level configuration includes a radio resource control configuration.

7. The method of claim 1, wherein the channel state information report comprises a semi-persistent channel state information report.

8. The method of claim 1, wherein the first physical uplink shared channel and the second physical uplink shared channel overlap in one or more symbols on the same carrier.

9. The method of claim 8, wherein the first physical uplink shared channel and the second physical uplink shared channel completely or partially overlap in the frequency domain.

10. The method of claim 8, wherein the first physical uplink shared channel and the second physical uplink shared channel do not overlap in the frequency domain.

11. An apparatus comprising: A transceiver that communicates wirelessly with a network node during operation; as well as A processor communicatively coupled to the transceiver enables the processor to perform a number of operations during operation, including: A first physical uplink shared channel is identified, which includes a channel state information report. A second physical uplink shared channel is determined to contain data, wherein the first physical uplink shared channel and the second physical uplink shared channel are associated with a control resource set pool index value; Determine whether the first physical uplink shared channel and the second physical uplink shared channel overlap in the time domain; and When the first physical uplink shared channel and the second physical uplink shared channel overlap in the time domain, the transceiver transmits the second physical uplink shared channel containing the data.

12. The device of claim 11, wherein during operation, the processor further performs the following operations: It is determined that the first physical uplink shared channel containing the channel status information report will not be transmitted.

13. The device of claim 12, wherein the first physical uplink shared channel is determined to not transmit based on a capability information of the device.

14. The device of claim 13, wherein the capability information of the device includes the number of transmitting units and the number of receiving units.

15. The device of claim 11, wherein during operation, the processor further performs the following operations: The processor receives a higher-level configuration containing the index value of the control resource set pool.

16. The device of claim 15, wherein the higher-level configuration includes a wireless resource control configuration.

17. The apparatus of claim 11, wherein the channel state information report includes a semi-persistent channel state information report.

18. The device of claim 11, wherein the first physical uplink shared channel and the second physical uplink shared channel completely or partially overlap in one or more symbols on the same carrier.

19. The device of claim 18, wherein the first physical uplink shared channel and the second physical uplink shared channel completely or partially overlap in the frequency domain.

20. The device of claim 18, wherein the first physical uplink shared channel and the second physical uplink shared channel do not overlap in the frequency domain.

Images