Overlapping physical uplink control channel transmission and physical uplink shared channel transmission

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control signaling that schedules a physical uplink control channel (PUCCH) transmission and a physical uplink shared channel (PUSCH) transmission that overlap in the time domain. The UE may simultaneously transmit the PUSCH transmission and the PUCCH transmission if the scheduled number of layers for the PUSCH transmission (or the scheduled number of layers for the PUSCH transmission and the PUCCH transmission) does not exceed the indicated maximum number of layers for the PUSCH transmission (or the PUSCH transmission and the PUCCH transmission). For a codebook-based PUSCH transmission, the UE may simultaneously transmit the PUSCH transmission and the PUCCH transmission if the scheduled number of antenna ports for the PUSCH transmission (or the scheduled number of antenna ports for the PUSCH transmission and the PUCCH transmission) does not exceed the indicated maximum number of ports for the PUSCH transmission (or the PUSCH transmission and the PUCCH transmission).

Description

[0001] Cross-references

[0002] This application claims priority to U.S. patent application No. 17 / 946,957, filed by Khoshnevisan et al. on September 16, 2022, entitled “OVERLAPPING PHYSICAL UPLINK CONTROL CHANNEL AND PHYSICAL UPLINK SHARED CHANNELTRANSMISSIONS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications including overlapping physical uplink control channel transmissions and physical uplink shared channel transmissions. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting overlapping physical uplink control channel (PUCCH) transmissions and physical uplink shared channel (PUSCH) transmissions. For example, the described techniques provide for the transmission of overlapping PUCCH transmissions and PUSCH transmissions based on conditions related to how many layers are available for PUSCH transmissions and / or PUCCH transmissions. In some aspects, a user equipment (UE) may receive control signaling from a network that schedules overlapping PUCCH transmissions and PUSCH transmissions in the time domain. In some examples, if the number of layers scheduled for PUSCH transmissions (or the number of layers scheduled for PUSCH transmissions and PUCCH transmissions) does not exceed the indicated maximum number of layers for PUSCH transmissions (or PUSCH transmissions and PUCCH transmissions), the UE may send PUSCH transmissions and PUCCH transmissions simultaneously. In some examples, for codebook-based PUSCH transmissions, if the number of antenna ports scheduled for PUSCH transmissions (or the number of antenna ports scheduled for PUSCH transmissions and PUCCH transmissions) does not exceed the indicated maximum number of ports for PUSCH transmissions (or PUSCH transmissions and PUCCH transmissions), the UE may send PUSCH transmissions and PUCCH transmissions simultaneously.

[0006] A method is described. The method may include: communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first control resource set (CORESET) pool index; receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and transmitting at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0007] A UE is described. The UE may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the UE to: communicate first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; receive second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; receive third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission, transmit at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index.

[0008] Another apparatus is described. The apparatus may include: means for communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; means for receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; means for receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and means for transmitting at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0009] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: communicate first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; receive second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; receive third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and transmit at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0010] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink shared channel transmission includes a codebook-based uplink shared channel transmission.

[0012] Some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; selecting a subset of layers in the number of layers based on the determination, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers; and transmitting the uplink control channel transmission and the uplink shared channel transmission via the subset of layers.

[0013] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, receiving the third control signaling may include operations, features, components, or instructions for: receiving an indication of a sounding reference signal resource set or a demodulation reference signal port set corresponding to the number of layers, and wherein selecting the subset of layers includes selecting a subset of the sounding reference signal resource set or a subset of the demodulation reference signal port set.

[0014] Some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending one of the uplink control channel transmission or the uplink shared channel transmission based on the determination and discarding one of the uplink control channel transmission or the uplink shared channel transmission.

[0015] Some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: selecting to discard one based on that one of the uplink control channel transmission or the uplink shared channel transmission is associated with a fixed CORESET pool index, the one has a lower priority, the one is the uplink control channel transmission and carries a channel state information report, the one is the uplink shared channel transmission and the uplink control channel transmission carrying hybrid automatic repeat request feedback information, the one is scheduled for transmission at a later time, or the one is scheduled for periodic or semi-static transmission.

[0016] Some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; and multiplexing information associated with the uplink control channel transmission onto the uplink shared channel transmission based on the determination, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending the uplink shared channel transmission.

[0017] Some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining, based on a first communication resource associated with the uplink control channel transmission and a second communication resource associated with the uplink shared channel transmission, that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein the second control signaling indicates the first communication resource, wherein the third control signaling indicates the second communication resource, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on the determination.

[0018] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, receiving the third control signaling may include operations, features, components, or instructions for: receiving an indication that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on the indication.

[0019] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: receiving the first control signaling from the network entity.

[0020] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: sending an indication of UE capabilities corresponding to the maximum number of layers.

[0021] In some examples of the methods, UEs, devices, and non-transitory computer-readable media described herein, the maximum number of layers includes a total number of layers used for uplink control channel transmission and uplink shared channel transmission, and the uplink control channel transmission can be associated with one layer.

[0022] A method for wireless communication at a network entity is described. The method may include: communicating first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and receiving at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index from the UE based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0023] A network entity is described. The network entity may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the network entity to: communicate first control signaling with the UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; send second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; send third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and receive at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index from the UE based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0024] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for communicating a first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; a component for sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; a component for sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and a component for receiving at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index from the UE based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0025] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that are executable by a processor to: communicate first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in a time domain; send second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; send third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and receive at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index from the UE based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0026] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0027] In some examples of the methods, network entities, apparatuses, and non-transitory computer-readable media described herein, the uplink shared channel transmission includes a codebook-based uplink shared channel transmission.

[0028] Some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the uplink control channel transmission and the uplink shared channel transmission via a subset of layers in the number of layers, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, and wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers.

[0029] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, sending the third control signaling may include operations, features, components, or instructions for: sending an indication of a sounding reference signal resource set or a demodulation reference signal port set corresponding to the number of layers.

[0030] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, receiving at least one of the uplink control channel transmission or the uplink shared channel transmission may include operations, features, components, or instructions for: receiving one of the uplink control channel transmission or the uplink shared channel transmission, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

[0031] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, receiving at least one of the uplink control channel transmission or the uplink shared channel transmission may include operations, features, components, or instructions for: receiving the uplink shared channel transmission, wherein information associated with the uplink control channel transmission is multiplexed onto the uplink shared channel transmission, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

[0032] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, sending the third control signaling may include operations, features, components, or instructions for: sending an indication that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on the indication.

[0033] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: sending the first control signaling.

[0034] In some examples of the methods, network entities, apparatuses, and non-transitory computer-readable media described herein, communicating the first control signaling may include operations, features, components, or instructions for: receiving an indication of UE capabilities corresponding to the maximum number of layers.

[0035] In some examples of the methods, network entities, devices, and non-transitory computer-readable media described herein, the maximum number of layers includes a total number of layers used for uplink control channel transmission and uplink shared channel transmission, and the uplink control channel transmission can be associated with one layer. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An example of a wireless communication system supporting overlapping physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmissions according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 2 An example of a wireless communication system supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is illustrated.

[0038] Figure 3 An example of a multiple transmission and reception point (TRP) transmission scheme supporting overlapping PUCCH and PUSCH transmission according to one or more aspects of the present disclosure is illustrated.

[0039] Figure 4 An example of a process flow for supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 5 and Figure 6 A block diagram of an apparatus supporting overlapping PUCCH and PUSCH transmissions according to one or more aspects of the present disclosure is shown.

[0041] Figure 7A block diagram of a communication manager supporting overlapping PUCCH and PUSCH transmissions is shown in accordance with one or more aspects of the present disclosure.

[0042] Figure 8 A diagram of a system including a device supporting overlapping PUCCH and PUSCH transmissions is shown in accordance with one or more aspects of the present disclosure.

[0043] Fig. 9 and Fig.10 A block diagram of an apparatus supporting overlapping PUCCH and PUSCH transmissions according to one or more aspects of the present disclosure is shown.

[0044] Fig.11 A block diagram of a communication manager supporting overlapping PUCCH and PUSCH transmissions is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig.12 A diagram of a system including a device supporting overlapping PUCCH and PUSCH transmissions is shown in accordance with one or more aspects of the present disclosure.

[0046] Figures 13 to 16 A flow chart illustrating a method of supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0047] In a wireless communication system, a user equipment (UE) may send a physical uplink shared channel (PUSCH) transmission and a physical uplink control channel (PUCCH) transmission to a network entity. Some UEs may be able to send multiple uplink transmissions that overlap at least partially in the time domain in the same component carrier (CC). For example, a UE may be scheduled to send a PUCCH to a first transmit and receive point (TRP) that overlaps at least partially in time with a scheduled PUSCH transmission to a second TRP. From the UE's perspective, TRP differentiation may be based on a control resource set (CORESET) pool index value associated with each uplink transmission. For both codebook-based PUSCH and non-codebook-based PUSCH, the UE may be configured with a maximum number of layers (e.g., rank) X' for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. For codebook-based PUSCH, the UE may be configured with a maximum number of PUSCH antenna ports for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. PUCCH transmission may be configured to use a single layer (eg, a single antenna port for codebook-based PUCCH).

[0048] The present disclosure relates to simultaneous transmission of PUSCH transmissions and PUCCH transmissions and a scheme for managing overlapping PUSCH transmissions and PUCCH transmissions when conditions related to the maximum number of layers and / or the maximum number of antenna ports are not met. The UE may indicate to a network entity (e.g., via capability signaling), or the network entity may indicate to the UE (e.g., via radio resource control (RRC) signaling) the maximum number of layers (e.g., rank) that the UE can support PUSCH transmissions that overlap with PUCCH transmissions in the time domain. For codebook-based PUSCH, the UE may also indicate to the network entity, or the network entity may indicate to the UE the maximum number of antenna ports for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. The UE may receive control signaling that schedules overlapping PUCCH transmissions and PUSCH transmissions in the time domain. The control signaling may indicate the number of layers used for PUSCH transmissions (e.g., or the number of antenna ports used for codebook-based PUSCH).

[0049] In some examples, the UE may not expect the network entity to schedule overlapping PUSCH transmissions and PUCCH transmissions, where the scheduled number of layers (and / or the number of antenna ports used for codebook-based PUSCH) exceeds the maximum number of layers (and / or the maximum number of antenna ports used for codebook-based PUSCH). In some examples, if the scheduled number of PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum value, the UE may reduce the number of scheduled PUSCH layers, for example, by selecting a subset of indicated sounding reference signal (SRS) resources or demodulation reference signal (DMRS) ports to reduce the number of layers to the configured maximum value. In some cases, if the scheduled number of PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum value, the UE may discard the scheduled PUSCH transmission or the scheduled PUCCH transmission. In some examples, if the number of PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum, the UE may multiplex PUCCH content onto PUSCH transmissions and send PUSCH transmissions (instead of PUCCH transmissions).

[0050] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are additionally described by and with reference to a multiple TRP transmission scheme and process flow. Various aspects of the present disclosure are further described by and with reference to apparatus diagrams, system diagrams, and flow charts related to overlapping PUCCH transmissions and PUSCH transmissions.

[0051] Figure 1An example of a wireless communication system 100 supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0052] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0053] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices (such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0054] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0055] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0056] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0057] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a TRP. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0058] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0059] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0060] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0061] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0062] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 via the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0063] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0064] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0065] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0066] The UE 115 and the network entity 105 may use resources associated with one or more carriers to wirelessly communicate with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0068] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0069] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0070] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0071] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0072] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0073] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0074] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0075] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., CORESET) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0076] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0077] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0078] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0079] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0080] The wireless communication system 100 may support synchronous operation or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous operation or asynchronous operation.

[0081] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0082] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0083] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW) or a user plane function (UPF)). The control plane entity may manage non-access layer (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0084] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0085] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region that uses a spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may be facilitated using an antenna array within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

[0086] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0087] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0088] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to the same receiving device; in multi-user MIMO (MU-MIMO), multiple spatial layers are sent to multiple devices.

[0089] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0090] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the network entity 105 (e.g., the base station 140, the RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as the network entity 105), or by a receiving device (such as the UE 115)) the beam direction for later transmission or reception by the network entity 105.

[0091] Some signals, such as data signals associated with a particular receiving device, may be sent by a sending device (e.g., a sending network entity 105, a sending UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as a receiving network entity 105 or a receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0092] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0093] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different reception beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different reception beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0094] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0095] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0096] In the wireless communication system 100, the UE 115 may send PUSCH transmissions and PUCCH transmissions to one or more network entities 105. In some examples, the UE 115 may send multiple uplink transmissions that at least partially overlap in the time domain in the same CC. For example, the UE 115 may be scheduled to send a PUCCH transmission to a first TRP based on a CORESET pool index value associated with each uplink transmission, and the PUCCH transmission overlaps at least partially in time with a scheduled PUSCH transmission to a second TRP. For both codebook-based PUSCH and non-codebook-based PUSCH, the UE 115 may be configured with a maximum number of layers X' for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. For codebook-based PUSCH, the UE 115 may be configured with a maximum number of PUSCH antenna ports for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. The PUCCH transmission may be configured to use a single layer (e.g., a single antenna port for codebook-based PUSCH).

[0097] The UE 115 may indicate to the network entity 105 (e.g., via capability signaling), or the network entity 105 may indicate to the UE 115 (e.g., via RRC signaling) the maximum number of layers that the UE 115 may support for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. For codebook-based PUSCH, the UE 115 may also indicate to the network entity 105, or the network entity 105 may indicate to the UE the maximum number of antenna ports for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. The UE 115 may receive control signaling that schedules PUCCH transmissions and PUSCH transmissions that overlap in the time domain. The control signaling may indicate the number of layers used for PUSCH transmissions (e.g., or the number of antenna ports for codebook-based PUSCH).

[0098] In some examples, UE 115 may not expect network entity 105 to schedule overlapping PUSCH transmissions and PUCCH transmissions where the scheduled number of layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the maximum number of layers. In some examples, if the scheduled number of PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum value, UE 115 may reduce the number of layers of the scheduled PUSCH transmissions, for example by selecting a subset of indicated SRS resources or DMRS ports to reduce the number of layers to the configured maximum value. In some cases, if the scheduled number of PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum value, UE 115 may discard the scheduled PUSCH transmission or the scheduled PUCCH transmission. In some examples, if the number of scheduled PUSCH layers (e.g., or the number of antenna ports used for codebook-based PUSCH) exceeds the configured maximum, the UE 115 may multiplex the PUCCH content onto the PUSCH transmission and send the PUSCH transmission (rather than the PUCCH transmission).

[0099] Figure 2 An example of a wireless communication system 200 that supports overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented or may be implemented to achieve or facilitate aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a, which may be an example of a UE 115 as described herein. The wireless communication system 200 includes a network entity 105-a, which may be an example of a network entity 105 as described herein.

[0100] UE 115-a may communicate with network entity 105-a via TRP 210-a and TRP 210-b using communication link 125-a, which may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a may include a bidirectional link that implements both uplink communication and downlink communication. For example, UE 115-a may send uplink transmission 255 (such as an uplink control signal or an uplink data signal) to network entity 105-a using communication link 125-a via TRP 210-a or TRP 210-b, and network entity 105-a may send downlink transmission 240 (such as a downlink control signal or a downlink data signal) to UE 115-a using communication link 125-a via TRP 210-a or TRP 210-b. In some cases, TRP 210-a and TRP 210-b may be located at or associated with different network entities (e.g., TRP 210-a may be located at or associated with network entity 105-a, and TRP 210-b may be located at or associated with another network entity 105).

[0101] In some examples, UE 115-a and network entity 105-a may support multiple TRP transmissions based on multiple downlink control information (DCI). In some examples, UE 115-a may receive a control message 220-a including a first DCI (sent from TRP 210-a) that schedules a first uplink transmission to TRP 210-a (e.g., PUSCH transmission 250). In some examples, UE 115-a may receive a control message 220-b including a second DCI (sent from TRP 210-b) that schedules a second uplink transmission to TRP 210-b (e.g., PUCCH transmission 260 or another PUSCH transmission).

[0102] In some examples, UE 115-a may perform TRP differentiation based on a CORESET pool index value (e.g., CORESETPoolIndex). For example, control message 220-a and control message 220-b may include an indication of a first SRS resource set 225-a and a second SRS resource set 225-b. The first SRS resource set 225-a may include SRS resources 230-a and SRS resources 230-b. The second SRS resource set 225-b may include SRS resources 230-c and SRS resources 230-d. The network entity 105-a may configure each CORESET (e.g., up to 5 CORESETs) with the value CORESETPoolIndex. The value of CORESETPoolIndex may be 0 or 1. This divides the CORESETs into two groups. TRPs may be associated with the CORESETPoolIndex value. For example, CORESETPoolIndex=0 may be associated with TRP 210-a and CORESETPoolIndex=1 may be associated with TRP 210-b. In some examples, UE 115-a may be configured by a higher layer parameter PDCCH-Config (e.g., in RRC signaling 215) that includes two different values ​​of CORESETPoolIndex in the CORESET for the active BWP of the serving cell.

[0103] In some examples, the PUSCH transmission 250 is associated with CORESETPoolIndex=0 and is transmitted from a first UE panel toward TRP 210-a using a first beam, a first transmit configuration indicator (TCI) state, a first power control parameter, and / or a first predecoder, and the PUCCH transmission 260 is associated with CORESETPoolIndex=1 and is transmitted from a second UE panel toward TRP 210-b using a second beam, a second TCI state, a second power control parameter, and / or a second predecoder.

[0104] In some examples, uplink transmissions (e.g., PUSCH transmissions 250 and PUCCH transmissions 260) to different TRPs (e.g., TRP 210-a and TRP 210-b) (wherein, from the perspective of the UE, the uplink transmissions are associated with different CORESET pool index values) may be time domain multiplexed (TDM) in a given CC or serving cell. In some examples, as described herein, uplink transmissions (e.g., PUSCH transmissions 250 and PUCCH transmissions 260) to different TRPs (e.g., TRP 210-a and TRP 210-b) (wherein, from the perspective of the UE, the uplink transmissions are associated with different CORESET pool index values) may at least partially overlap in the time domain (non-TDM).

[0105] In some wireless communication systems, when a scheduled PUSCH transmission 250 and a scheduled PUCCH transmission 260 in the same CC or serving cell overlap partially or completely in the time domain, if the PUSCH transmission 250 and the PUCCH transmission 260 are associated with different CORESETPoolIndex values, the UE 115-a may simultaneously transmit the PUSCH transmission 250 and the PUCCH transmission 260. A control message (e.g., control message 220-a and control message 220-b) may indicate the CORESET pool index values ​​associated with the PUSCH transmission 250 and the PUCCH transmission 260. The techniques described herein provide multi-TRP communication based on multi-DCI.

[0106] UE 115-a may use a single layer (e.g., a single antenna port) for PUCCH transmissions 260. In some examples, UE 115-a may support a maximum number of layers X' (e.g., rank) that UE 115-a may use for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. In some examples, for both codebook-based PUSCH transmissions and non-codebook-based PUSCH transmissions, the maximum number of layers X' may not apply to simultaneous PUSCH transmissions (e.g., time-overlapping PUSCH transmissions to different TRPs without time-overlapping PUCCH).

[0107] In some examples, the maximum number of layers may be configured as X'=min(X-1,Y), where X is the total and rank limit (number of layers of PUSCH + 1 ≤ X (because PUCCH is configured to use a single layer)), and Y is the PUSCH rank limit (number of layers of PUSCH ≤ Y). Y corresponds to the maximum rank per CORESET pool index value in the presence of simultaneous transmissions. X', X, and / or Y may be indicated by UE 115-a capabilities or may be RRC configured. For example, UE 115-a may send capability signaling 245 indicating X, Y, or X', or network entity 105-a may send an indication of X, Y, or X' in RRC signaling 215.

[0108] For codebook-based PUSCH transmissions, the UE 115-a may be configured with a maximum number of PUSCH antenna ports P' that the UE 115-a may use for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. In some examples, the maximum number of antenna ports may be configured as P'=min(P-1,Q), where P is the sum port number limit (number of PUSCH ports for PUSCH + 1 ≤ P (because the PUCCH is configured to use a single antenna port)), and Q is the limit on the number of PUSCH ports (number of PUSCH ports for PUSCH ≤ Q). Q corresponds to the maximum number of antenna ports for PUSCH per CORESET pool index value in the presence of simultaneous transmissions with PUCCH. P', P and / or Q may be indicated by the UE 115-a in capability signaling or may be RRC configured. For example, the UE 115-a may send capability signaling 245 indicating P', P, or Q, or the network entity 105-a may send an indication of P', P, or Q in RRC signaling 215.

[0109] UE 115-a and network entity 105-a may communicate control signaling (e.g., RRC signaling 215 or UE capability signaling 245) that indicates the maximum number of layers that UE 115-a can use for PUSCH transmissions that overlap with PUCCH transmissions in the time domain. For example, the control signaling may indicate X', X, and / or Y. In some examples, if the control signaling indicates X and / or Y, UE 115-a (and / or network entity 105-a) may determine X' as X'=min(X-1,Y). In some examples, control signaling (e.g., RRC signaling 215 or UE capability signaling 245) may indicate the maximum number of antenna ports that UE 115-a can use for PUSCH transmissions that overlap with PUCCH transmissions for codebook-based transmissions in the time domain. For example, the control signaling may indicate P', P, and / or Q. In some examples, if the control signaling indicates P and / or Q, the UE 115 - a (and / or the network entity 105 - a ) may determine P′ as P′=min(P−1,Q).

[0110] In some examples, UE 115-a may receive a control message 220-b that schedules a PUCCH transmission 260. The control message 220-b may indicate that the PUCCH transmission 260 is associated with a first CORESET pool index value (e.g., CORESETPoolIndex=1). As a result, network entity 105-a is scheduled to receive the PUCCH transmission 260 via TRP 210-b. For example, the control message 220-b may include one or more SRS resource indicator fields that indicate communication resources such as an SRS resource set 225-b associated with CORESETPoolIndex=1.

[0111] UE 115-a may receive a control message 220-a scheduling a PUSCH transmission 250. The control message 220-a may indicate that the PUSCH transmission 250 is associated with a second CORESET pool index value (e.g., CORESETPoolIndex=0). Therefore, the network entity 105-a is scheduled to receive the PUSCH transmission 250 via the TRP 210-a. For example, the control message 220-a may include one or more SRS resource indicator fields that indicate communication resources such as an SRS resource set 225-a associated with CORESETPoolIndex=0. The control message 220-a scheduling the PUSCH transmission 250 may indicate the number of layers associated with the PUSCH transmission 250. In some examples, for codebook-based PUSCH, the control message 220-a scheduling the PUSCH transmission 250 may indicate the number of antenna ports associated with the PUSCH transmission 250.

[0112] In some examples, UE 115-a may not expect network entity 105-a to schedule PUSCH transmissions 250 and PUCCH transmissions 260 that at least partially overlap in the time domain, where the number of layers scheduled for PUSCH transmission 250 (e.g., or the number of antenna ports if PUSCH transmission 250 is a codebook-based PUSCH transmission) exceeds the configured maximum number of layers (e.g., or the maximum number of antenna ports if PUSCH transmission 250 is a codebook-based PUSCH transmission). In some examples, if the number of scheduled PUSCH layers (e.g., or the number of antenna ports if PUSCH transmission 250 is a codebook-based PUSCH transmission) does not exceed the configured maximum value, UE 115-a may simultaneously send a PUSCH transmission 250 associated with CORESETPoolIndex=0 (e.g., to TRP 210-a) and a PUCCH transmission 260 associated with CORESETPoolIndex=1 (e.g., to TRP 210-b). In some examples, UE 115-a may be configured to not multiplex PUCCH content (e.g., uplink control information (UCI)) in PUSCH transmission 250. For example, UE 115-a may send PUSCH transmission 250 and PUCCH transmission 260 separately and simultaneously (e.g., at least partially overlapping in time).

[0113] In some examples, simultaneous transmission of PUSCH transmission 250 and PUCCH transmission 260 may be used where one or both of PUSCH transmission 250 and PUCCH transmission 260 are dynamically scheduled by DCI (e.g., control message 220-a and / or control message 220-b are DCI) because network entity 105-a may avoid violating maximum layer and / or antenna port restrictions via backhaul communications between TRP 210-a and TRP 210-b. For example, both PUSCH transmission 250 and PUCCH transmission 260 may be scheduled by DCI (e.g., PUSCH transmission 250 may be a dynamic grant (DG) PUSCH and PUCCH transmission 260 may be a dynamic HARQ acknowledgment (Ack)). As another example, only the PUSCH transmission 250 may be scheduled by DCI (e.g., the PUSCH transmission 250 may be a DG-PUSCH and the PUCCH transmission 260 may be a periodic or semi-persistent (SP) scheduled channel state information (CSI) report or scheduling request, or a HARQ-Ack for an SP-scheduled physical downlink shared channel (PDSCH)). As another example, only the PUCCH transmission may be scheduled by DCI (e.g., the PUSCH transmission 250 may be a configuration grant (CG) PUSCH and the PUCCH transmission 260 may be a dynamic HARQ-Ack).

[0114] In some examples, if the control message 220-a schedules the number of layers for the PUSCH transmission 250 in excess of the indicated maximum number of layers, the UE 115-a may reduce the number of layers for the PUSCH transmission 250 to meet the configured maximum number of layers. For example, to reduce the number of layers used for the PUSCH transmission 250, the UE 115-a may select a subset of the indicated SRS resources for non-codebook based PUSCH transmission and a subset of DMRS ports corresponding to the reduced number of layers. For codebook based PUSCH transmission, if the control message 220-a indicates that the number of antenna ports for the PUSCH transmission 250 exceeds the configured maximum number of antenna ports, the UE 115-a may reduce the number of antenna ports, for example, by selecting a subset of the indicated SRS ports and a subset of transmit precoding matrix index (TPMI) rows corresponding to the reduced number of ports.

[0115] UE 115-a may determine that PUSCH transmission 250 at least partially overlaps in time with PUCCH transmission 260. In some examples, UE 115-a may determine that PUSCH transmission 250 at least partially overlaps in time with PUCCH transmission 260 based on a grant or configuration that schedules PUSCH transmission 250 and PUCCH transmission 260 (e.g., based on determining that time resources scheduled for PUSCH transmission 250 overlap with time resources scheduled for PUCCH transmission 260). In some examples, control message 220-a scheduling PUSCH transmission 250 may be a DCI, and the DCI may indicate that the PUSCH transmission at least partially overlaps in time with PUCCH transmission 260. For example, in a case where the PUCCH transmission 260 is also scheduled by DCI (e.g., the control message 220-b is DCI and the PUCCH transmission 260 is a dynamic HARQ-Ack) and the DCI scheduling the PUCCH transmission is omitted, the UE 115-a may incorrectly determine the number of layers and / or antenna ports to use for the PUSCH transmission because the UE 115-a may incorrectly determine that there is no PUSCH / PUCCH overlap in the absence of an explicit indication in the DCI scheduling the PUSCH transmission 250 (and thus, in some cases, the PUSCH transmission may not be received by the network entity 105-a). In some cases, if the PUSCH transmission 250 is a DG-PUSCH (e.g., in the control message 220-a), the network entity 105-a may indicate to the UE 115-a to reduce the number of layers or antenna ports in the DCI scheduling the PUSCH transmission 250. In some examples, the network entity 105-a may assume that the UE 115-a autonomously reduces the number of layers and / or ports of the PUSCH transmission 250 to meet the configured maximum number of layers and / or maximum number of ports for PUSCH transmissions overlapping with the PUCCH transmissions. For this assumption, the PUSCH transmission 250 and the PUCCH transmission 260 are in the same CC (or the same band or the same frequency range), the PUSCH transmission 250 is associated with a first CORESET pool index value and the PUCCH transmission 260 is associated with a different second CORESET pool index value, and the UE 115-a is configured not to multiplex PUCCH or UCI information onto the overlapping PUSCH (e.g., instead, the UE 115-a is configured to transmit both PUSCH and PUCCH separately and concurrently).

[0116] Reducing the number of PUSCH layers (or the number of PUSCH antenna ports) may be useful for situations where both the PUSCH transmission 250 and the PUCCH transmission 260 are semi-statically scheduled (not dynamically scheduled) (e.g., if the PUSCH transmission 250 is a DG-PUSCH and the PUCCH transmission 260 is a periodic or SP-scheduled CSI report or scheduling request or HARQ-ACK for an SP-scheduled physical downlink data channel transmission). In such situations, both the PUSCH transmission 250 and the PUCCH transmission 260 are sent periodically (possibly with different periodicities), and the network entity 105-a may not be able to ensure that the configured maximum PUSCH layer / antenna port limit is not violated (e.g., unless the number of PUSCH layers and / or the number of antenna ports are limited to the configured maximum value, regardless of whether the PUSCH overlaps with the PUCCH, which may result in performance degradation). In some examples, even when one or both of a PUSCH transmission 250 and a PUCCH transmission 260 are dynamically scheduled by a DCI, in order not to increase the DCI payload, the reduction in the number of layers and / or antenna ports may be determined by UE 115-a based on overlap (e.g., based on the scheduled resources) rather than having such reduction indicated by the DCI scheduling the PUSCH transmission 250.

[0117] In some examples, if the number of layers scheduled by the control message 220-a for the PUSCH transmission 250 exceeds the indicated maximum number of layers (e.g., or if for a codebook-based PUSCH transmission, the control message 220-a indicates that the number of antenna ports used for the PUSCH transmission 250 exceeds the configured maximum number of antenna ports), the UE 115-a may discard the PUSCH transmission 250 or the PUCCH transmission 260. In some cases, the UE 115-a may be configured to always discard PUCCH transmissions. In some cases, the UE 115-a may be configured to always discard PUSCH transmissions. In some examples, a PUCCH or PUSCH associated with a fixed CORESETPoolIndex value is discarded (e.g., a transmission associated with a second CORESETPoolIndex is discarded and a transmission associated with a first CORESETPoolIndex is sent). In some examples, a PUCCH transmission 260 or PUSCH transmission 250 associated with a lower priority (e.g., a PHY layer priority associated with a channel) is discarded. In some examples, PUCCH transmission 260 or PUSCH transmission 250 is discarded based on the UCI type of PUCCH transmission 260 (the priority of the payload in the PUCCH) (e.g., if PUCCH transmission 260 carries HARQ-Ack, PUSCH transmission 250 is discarded; if PUCCH transmission 260 carries a CSI report, PUCCH transmission 260 is discarded). In some examples, if only one of the PUSCH transmission 250 or the PUCCH transmission 260 is scheduled by DCI (e.g., dynamically scheduled), the semi-statically configured or activated (not scheduled by DCI) transmission is discarded (e.g., if the PUSCH transmission 250 is a DG-PUSCH and the PUCCH transmission 260 is a periodic or SP-scheduled CSI report or scheduling request or HARQ-Ack for an SP-scheduled PDSCH, the PUCCH transmission 260 is discarded; or if the PUSCH transmission 250 is a CG-PUSCH and the PUCCH transmission 260 is a dynamic HARQ-Ack, the PUSCH transmission 250 is discarded). In some examples, the PUSCH transmission 250 or PUCCH transmission 260 that starts later in time is discarded.In some examples, the assumptions that trigger dropping one of the PUSCH transmission 250 or the PUCCH transmission 260 may include: the PUSCH transmission 250 and the PUCCH transmission 260 are in the same CC (or the same band or the same frequency range), the PUSCH transmission 250 is associated with a first CORESET pool index value and the PUCCH transmission 260 is associated with a different second CORESET pool index value, or the UE 115-a is configured not to multiplex PUCCH or UCI information onto an overlapping PUSCH (for example, alternatively, the UE 115-a is configured to send both PUSCH and PUCCH separately and simultaneously).

[0118] In some examples, if the control message 220-a schedules the number of layers for the PUSCH transmission 250 exceeds the indicated maximum number of layers (e.g., or if for a codebook-based PUSCH transmission, the control message 220-a indicates that the number of antenna ports used for the PUSCH transmission 250 exceeds the configured maximum number of antenna ports), the UE 115-a may multiplex the content of the PUCCH transmission 260 (e.g., UCI) onto the PUSCH transmission 250 and only send the PUSCH transmission 250 (and not send the PUCCH transmission 260). In some examples, the multiplexing procedure may be followed based on the content of the PUCCH transmission 260 (e.g., UCI payload type). For example, in the case of HARQ-Ack, the UE 115-a may multiplex only the content of the PUCCH transmission 260 onto the PUSCH transmission 250, and if the PUCCH content is a CSI report, a different course of action may be followed (e.g., discarding the PUCCH transmission). In some examples, the assumption that triggers the dropping of one of the PUSCH transmission 250 or the PUCCH transmission 260 may include: the PUSCH transmission 250 and the PUCCH transmission 260 are in the same CC (or the same band or the same frequency range), the PUSCH transmission 250 is associated with a first CORESET pool index value and the PUCCH transmission 260 is associated with a different second CORESET pool index value.

[0119] Figure 3An example of a multi-TRP transmission scheme 300 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is illustrated. The multi-TRP transmission scheme 300 may be implemented or may be implemented to implement or facilitate various aspects of the wireless communication system 100 or the wireless communication system 200. For example, the multi-TRP transmission scheme 300 includes a UE 115-b, which may be an example of a UE 115 as described herein. The multi-TRP transmission scheme 300 includes a network entity 105-b, which may be an example of a UE 115 as described herein. The multi-TRP transmission scheme 300 includes a TRP 210-c and a TRP 210-d, which may be examples of TRPs as described herein.

[0120] In some examples, the multi-TRP transmission scheme 300 may support PUSCH transmissions and PUCCH transmissions of multiple TRPs (e.g., TRP 210-c and TRP 210-d) from a single UE 115-b to a network entity 105-b via different directional beams (including beam 320-a and beam 320-b), where the different beams may be associated with different SRS resource sets, different transmit configuration indicator (TCI) states, different layers, different PUSCH ports, or different panels of UE 115-b, or any combination thereof. The multi-TRP transmission scheme 300 may illustrate examples of PUSCH transmissions and PUCCH transmissions that at least partially overlap in time. The multi-TRP transmission scheme 300 may illustrate examples of multiple PUSCH and PUCCH transmission schemes (e.g., PUSCH-PUCCH transmission scheme 330-a, PUSCH-PUCCH transmission scheme 330-b, PUSCH-PUCCH transmission scheme 330-c, and PUSCH-PUCCH transmission scheme 330-d). Figure 3 As depicted in the example of , UE 115-b and network entity 105-b may support a multi-TRP framework based on multiple DCIs, where PUSCH transmissions and PUCCH transmissions are associated with different CoresetPoolIndex values. The PUSCH transmission (associated with a CoresetPoolIndex value of 0) may be associated with a first SRS resource set 325-a and may be transmitted using a first beam or TCI state or power control parameters or predecoder. Similarly, the PUCCH transmission (associated with a CoresetPoolIndex value of 1) may be associated with a second SRS resource set 325-b and may be transmitted using a second beam or TCI state or power control parameters or predecoder.

[0121] In some examples, the PUSCH transmission and the PUCCH transmission are in the same serving cell or CC and may partially or completely overlap at least in the time domain. The PUSCH transmission and the PUCCH transmission may or may not overlap in the frequency domain. In the example of the PUSCH-PUCCH transmission scheme 330-a, the PUSCH transmission and the PUCCH transmission may overlap in both time and frequency. In the example of the PUSCH-PUCCH transmission scheme 330-b, the PUSCH transmission and the PUCCH transmission overlap in time but do not overlap in frequency. In the example of the PUSCH-PUCCH transmission scheme 330-c, the PUSCH transmission and the PUCCH transmission partially overlap in time but do not overlap in frequency. In the example of the PUSCH-PUCCH transmission scheme 330-d, the PUSCH transmission and the PUCCH transmission partially overlap in time and frequency. UE 115-b may interpret the control message according to the techniques described herein and may send an uplink message using at least one of the PUSCH-PUCCH transmission scheme 330-a, the PUSCH-PUCCH transmission scheme 330-b, the PUSCH-PUCCH transmission scheme 330-c, and the PUSCH-PUCCH transmission scheme 330-d.

[0122] Figure 4 An example of a process flow 400 for supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is illustrated. The process flow 400 may include a UE 115-c, which may be an example of a UE 115 as described herein. The process flow 400 may include a network entity 105-c, which may be an example of a network entity 105 as described herein. The process flow 400 includes a TRP 210-e and a TRP 210-f, which may be examples of TRPs as described herein. In the following description of the process flow 400, operations between the network entity 105-c, the UE 115-c, the TRP 210-e, and the TRP 210-f may be sent in an order different from the example order shown, or operations performed by the network entity 105-c, the UE 115-c, the TRP 210-e, and the TRP 210-f may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 400 , and other operations may be added to the process flow 400 .

[0123] At 405, the UE 115-c and the network entity 105-c may communicate first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE 115-c in the time domain. In some examples, the network entity 105-c sends the first control signaling (e.g., RRC signaling) to the UE 115-c. In some examples, the UE 115-c sends an indication of UE capabilities corresponding to the maximum number of layers. In some cases, the maximum number of layers may be the total number of layers used for uplink control channel transmissions and uplink shared channel transmissions, and the uplink control channel transmission is associated with one layer.

[0124] At 410, the UE 115-c may receive control signaling from the network entity 105-c (via the TRP 210-e) that schedules an uplink control channel transmission associated with a first CORESET pool index. The first CORESET pool index may be associated with the TRP 210-e.

[0125] At 415, the UE 115-c may receive third control signaling from the network entity 105-c (via the TRP 210-f) that schedules an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain. The second CORESET pool index may be associated with the TRP 210-f.

[0126] At 420, based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission, the UE 115-c may send, and the network entity 105-c may receive (via TRP 210-e and TRP 210-f, respectively) at least one of an uplink control channel transmission indexed according to the first CORESET pool or an uplink shared channel transmission indexed according to the second CORESET pool.

[0127] In some examples, communicating the first control signaling includes communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates a number of antenna ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the maximum number of antenna ports and the number of antenna ports associated with the uplink shared channel transmission. In some examples, the uplink shared channel transmission is a codebook-based uplink shared channel transmission.

[0128] In some examples, UE 115-c may determine that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers. UE 115-c may select a subset of layers in the number of layers based on determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers. At 420, UE 115-c may send an uplink control channel transmission and an uplink shared channel transmission via the subset of layers. In some examples, receiving the third control signaling at 415 includes receiving an indication of an SRS resource set or a DMRS port set corresponding to the number of layers, and selecting the subset of layers includes selecting a subset of the SRS resource set or a subset of the DMRS port set.

[0129] In some cases, the UE 115-c may determine that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, and sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending one of the uplink control channel transmission or the uplink shared channel transmission and discarding one of the uplink control channel transmission or the uplink shared channel transmission based on determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers. In some cases, the UE 115-c may select to discard one of the uplink control channel transmission or the uplink shared channel transmission based on the one of the uplink control channel transmission or the uplink shared channel transmission being associated with a fixed CORESET pool index, the one having a lower priority, the one being an uplink control channel transmission and carrying a channel state information report, the one being an uplink shared channel transmission carrying hybrid automatic repeat request feedback information and an uplink control channel transmission, the one being scheduled for transmission at a later time, or the one being scheduled for periodic or semi-static transmission.

[0130] In some cases, UE 115-c may determine that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers. UE 115-c may multiplex information associated with the uplink control channel transmission onto the uplink shared channel transmission based on determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, and sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending the uplink shared channel transmission.

[0131] In some cases, UE 115-c may determine that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain based on a first communication resource associated with the uplink control channel transmission and a second communication resource associated with the uplink shared channel transmission. The second control signaling may indicate the first communication resource, the third control signaling may indicate the second communication resource, and sending at least one of the uplink control channel transmission or the uplink shared channel transmission may be based on determining that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain.

[0132] Figure 5 A block diagram 500 of a device 505 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0133] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to overlapping PUCCH transmissions and PUSCH transmissions). The information may be passed to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0134] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to overlapping PUCCH transmissions and PUSCH transmissions), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0135] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0136] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0137] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0138] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0139] For example, the communications manager 520 may be configured to or otherwise support means for communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The communications manager 520 may be configured to or otherwise support means for receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The communications manager 520 may be configured to or otherwise support means for receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The communication manager 520 may be configured or otherwise support means for transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0140] By including or configuring a communication manager 520 according to examples as described herein, a device 505 (e.g., a processor controlling or otherwise coupled to a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0141] Figure 6 A block diagram 600 of a device 605 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0142] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to overlapping PUCCH transmissions and PUSCH transmissions). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0143] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to overlapping PUCCH transmissions and PUSCH transmissions), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0144] The device 605 or its various components may be examples of components for performing various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, the communication manager 620 may include a maximum layer manager 625, an uplink control channel scheduling manager 630, an uplink shared channel scheduling manager 635, an uplink transmission manager 640, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0145] The maximum layers manager 625 may be configured to or otherwise support means for communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The uplink control channel scheduling manager 630 may be configured to or otherwise support means for receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The uplink shared channel scheduling manager 635 may be configured to or otherwise support means for receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The uplink transmission manager 640 may be configured to or otherwise support means for transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0146] Figure 7 A block diagram 700 of a communication manager 720 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, the communication manager 720 may include a maximum layer manager 725, an uplink control channel scheduling manager 730, an uplink shared channel scheduling manager 735, an uplink transmission manager 740, a maximum port manager 745, a layer comparison manager 750, a layer selection manager 755, an uplink transmission multiplexing manager 760, an overlapped transmission detection manager 765, a UE capability manager 770, an uplink transmission selection manager 775, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0147] The maximum layer manager 725 may be configured to or otherwise support means for communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The uplink control channel scheduling manager 730 may be configured to or otherwise support means for receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The uplink shared channel scheduling manager 735 may be configured to or otherwise support means for receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The uplink transmission manager 740 may be configured to or otherwise support means for transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0148] In some examples, to support communicating a first control signaling, the maximum port manager 745 may be configured as or otherwise support components for communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE, wherein a third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0149] In some examples, the uplink shared channel transmission includes codebook based uplink shared channel transmission.

[0150] In some examples, layer comparison manager 750 may be configured or otherwise support means for determining that the number of layers associated with an uplink shared channel transmission exceeds a maximum number of layers. In some examples, layer selection manager 755 may be configured or otherwise support means for selecting a subset of layers in the number of layers based on the determination, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers. In some examples, uplink transmission manager 740 may be configured or otherwise support means for transmitting an uplink control channel transmission and an uplink shared channel transmission via a subset of layers.

[0151] In some examples, to support receiving third control signaling, the uplink shared channel scheduling manager 735 may be configured as or otherwise support components for receiving an indication of an SRS resource set or a DMRS port set corresponding to a number of layers, and wherein selecting a subset of layers includes selecting a subset of the SRS resource set or a subset of the DMRS port set.

[0152] In some examples, the layer comparison manager 750 may be configured to or otherwise support components for determining that a number of layers associated with an uplink shared channel transmission exceeds a maximum number of layers, wherein sending at least one of an uplink control channel transmission or an uplink shared channel transmission includes sending one of the uplink control channel transmission or the uplink shared channel transmission based on the determination and discarding one of the uplink control channel transmission or the uplink shared channel transmission.

[0153] In some examples, the uplink transmission selection manager 775 may be configured to or otherwise support components for selecting to discard one of the uplink control channel transmissions or the uplink shared channel transmissions based on the one of the uplink control channel transmissions or the uplink shared channel transmissions being associated with a fixed CORESET pool index, the one having a lower priority, the one being the uplink control channel transmission and carrying a channel state information report, the one being an uplink shared channel transmission and an uplink control channel transmission carrying hybrid automatic repeat request feedback information, the one being scheduled for transmission at a later time, or the one being scheduled for periodic or semi-static transmission.

[0154] In some examples, layer comparison manager 750 may be configured or otherwise support means for determining that the number of layers associated with an uplink shared channel transmission exceeds a maximum number of layers. In some examples, uplink transmission multiplexing manager 760 may be configured or otherwise support means for multiplexing information associated with an uplink control channel transmission onto an uplink shared channel transmission based on the determination, wherein transmitting at least one of the uplink control channel transmission or the uplink shared channel transmission includes transmitting the uplink shared channel transmission.

[0155] In some examples, the overlap transmission detection manager 765 may be configured to or otherwise support components for determining that an uplink shared channel transmission at least partially overlaps with an uplink control channel transmission in the time domain based on a first communication resource associated with the uplink control channel transmission and a second communication resource associated with the uplink shared channel transmission, wherein the second control signaling indicates the first communication resource, wherein the third control signaling indicates the second communication resource, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the determination.

[0156] In some examples, to support receiving third control signaling, the overlap transmission detection manager 765 may be configured to or otherwise support components for receiving an indication that an uplink shared channel transmission at least partially overlaps with an uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the indication.

[0157] In some examples, to support communicating the first control signaling, maximum layer manager 725 may be configured or otherwise support components for receiving the first control signaling from a network entity.

[0158] In some examples, to support communicating the first control signaling, the UE capability manager 770 may be configured or otherwise support components for sending an indication of UE capabilities corresponding to a maximum number of layers.

[0159] In some examples, the maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission. In some examples, the uplink control channel transmission is associated with one layer.

[0160] Figure 8 A diagram of a system 800 including a device 805 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0161] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0162] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired or wireless link, as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

[0163] The memory 830 may include random access memory (RAM) and read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 835 may not be directly executable by the processor 840, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 830 may also include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0164] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks that support overlapping PUCCH transmissions and PUSCH transmissions). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0165] For example, the communications manager 820 may be configured to or otherwise support means for communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The communications manager 820 may be configured to or otherwise support means for receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with the first CORESET pool index. The communications manager 820 may be configured to or otherwise support means for receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with the second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The communication manager 820 may be configured to or otherwise support means for transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0166] By including or configuring a communication manager 820 according to examples as described herein, the device 805 can support techniques for improving communication reliability, more efficiently utilizing communication resources, and improving coordination between devices.

[0167] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that are executable by the processor 840 to cause the device 805 to perform various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0168] Fig. 9 A block diagram 900 of a device 905 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0169] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0170] The transmitter 915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0171] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0172] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0173] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0174] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0175] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support components for communicating a first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The communication manager 920 may be configured to or otherwise support components for sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The communication manager 920 may be configured to or otherwise support components for sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The communications manager 920 may be configured to or otherwise support means for receiving, from the UE, at least one of an uplink control channel transmission indexed according to a first CORESET pool or an uplink shared channel transmission indexed according to a second CORESET pool, based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0176] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled to a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0177] Fig.10 A block diagram 1000 of a device 1005 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0178] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0179] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0180] The device 1005 or its various components may be examples of components for performing various aspects of overlapping PUCCH transmission and PUSCH transmission as described herein. For example, the communication manager 1020 may include a maximum layer manager 1025, an uplink control channel scheduling manager 1030, an uplink shared channel scheduling manager 1035, an uplink transmission manager 1040, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0181] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The maximum layer manager 1025 may be configured to or otherwise support components for communicating a first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The uplink control channel scheduling manager 1030 may be configured to or otherwise support components for sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The uplink shared channel scheduling manager 1035 may be configured to or otherwise support components for sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The uplink transmission manager 1040 may be configured to or otherwise support means for receiving, from the UE, at least one of an uplink control channel transmission indexed according to a first CORESET pool or an uplink shared channel transmission indexed according to a second CORESET pool, based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0182] Fig.11 A block diagram 1100 of a communication manager 1120 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein. For example, the communication manager 1120 may include a maximum layer manager 1125, an uplink control channel scheduling manager 1130, an uplink shared channel scheduling manager 1135, an uplink transmission manager 1140, a maximum port manager 1145, an overlap transmission indication manager 1150, a UE capability manager 1155, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0183] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The maximum layer manager 1125 may be configured to or otherwise support components for communicating a first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The uplink control channel scheduling manager 1130 may be configured to or otherwise support components for sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The uplink shared channel scheduling manager 1135 may be configured to or otherwise support components for sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The uplink transmission manager 1140 may be configured to or otherwise support means for receiving, from the UE, at least one of an uplink control channel transmission indexed according to a first CORESET pool or an uplink shared channel transmission indexed according to a second CORESET pool, based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0184] In some examples, to support communicating a first control signaling, the maximum port manager 1145 may be configured as or otherwise support components for communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein a third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0185] In some examples, the uplink shared channel transmission includes codebook based uplink shared channel transmission.

[0186] In some examples, the uplink transmission manager 1140 may be configured to or otherwise support components for receiving uplink control channel transmissions and uplink shared channel transmissions via a subset of layers in a number of layers, wherein the number of layers associated with the uplink shared channel transmissions exceeds a maximum number of layers, and wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers.

[0187] In some examples, to support sending the third control signaling, the uplink shared channel scheduling manager 1135 may be configured or otherwise support components for sending an indication of an SRS resource set or a DMRS port set corresponding to a number of layers.

[0188] In some examples, to support receiving at least one of an uplink control channel transmission or an uplink shared channel transmission, the uplink transmission manager 1140 may be configured as or otherwise support components for receiving one of an uplink control channel transmission or an uplink shared channel transmission, where the number of layers associated with the uplink shared channel transmission exceeds a maximum number of layers.

[0189] In some examples, to support receiving at least one of an uplink control channel transmission or an uplink shared channel transmission, the uplink transmission manager 1140 may be configured as or otherwise support components for receiving an uplink shared channel transmission, wherein information associated with the uplink control channel transmission is multiplexed onto the uplink shared channel transmission, wherein the number of layers associated with the uplink shared channel transmission exceeds a maximum number of layers.

[0190] In some examples, to support sending a third control signaling, the overlap transmission indication manager 1150 may be configured as or otherwise support components for sending an indication that an uplink shared channel transmission at least partially overlaps with an uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the indication.

[0191] In some examples, to support communicating the first control signaling, maximum layer manager 1125 may be configured or otherwise support components for sending the first control signaling.

[0192] In some examples, to support communicating the first control signaling, the UE capability manager 1155 may be configured or otherwise support components for receiving an indication of UE capabilities corresponding to a maximum number of layers.

[0193] In some examples, the maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission. In some examples, the uplink control channel transmission is associated with one layer.

[0194] Fig.12A diagram of a system 1200 including a device 1205 supporting overlapping PUCCH transmissions and PUSCH transmissions according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0195] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0196] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1225 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0197] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1225) to enable the device 1205 to perform various functions (e.g., functions or tasks that support overlapping PUCCH transmissions and PUSCH transmissions). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, the processor 1235 and the memory 1225 being configured to perform the various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that can host functions (e.g., by executing code 1230) to perform functions of the device 1205. The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as in the memory 1225). In some specific implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to, for example, other systems or components of the device 1205). For example, the processing system of the device 1205 may refer to a system including various other components or subcomponents of the device 1205 (such as the processor 1235, or the transceiver 1210, or the communication manager 1220, or other components or combinations of components of the device 1205). The processing system of device 1205 can be docked with other components of device 1205, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1205 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1205 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0198] In some examples, bus 1240 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1205, or communications performed between different components of device 1205 that may be co-located or located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

[0199] In some examples, the communication manager 1220 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1220 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in collaboration with the other network entities 105. In some examples, the communication manager 1220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0200] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support components for communicating a first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps in the time domain with an uplink control channel transmission for the UE. The communication manager 1220 may be configured to or otherwise support components for sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index. The communication manager 1220 may be configured to or otherwise support components for sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps in the time domain with the uplink control channel transmission. The communications manager 1220 may be configured to or otherwise support means for receiving, from the UE, at least one of an uplink control channel transmission indexed according to a first CORESET pool or an uplink shared channel transmission indexed according to a second CORESET pool, based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0201] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 can support techniques for improving communication reliability, more efficiently utilizing communication resources, and improving coordination between devices.

[0202] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions that are executable by the processor 1235 to cause the device 1205 to perform various aspects of overlapping PUCCH transmissions and PUSCH transmissions as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0203] Fig.13A flow chart illustrating a method 1300 for supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0204] At 1305, the method may include communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps an uplink control channel transmission for the UE in the time domain. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The maximum layer manager 725 described is executed.

[0205] At 1310, the method may include receiving second control signaling from a network entity, the second control signaling scheduling an uplink control channel transmission associated with the first CORESET pool index. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The described uplink control channel scheduling manager 730 is executed.

[0206] At 1315, the method may include receiving a third control signaling from a network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The described uplink shared channel scheduling manager 735 is executed.

[0207] At 1320, the method may include transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 7 The described uplink transmission manager 740 is performed.

[0208] Fig.14 A flow chart illustrating a method 1400 for supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0209] At 1405, the method may include communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps an uplink control channel transmission for the UE in the time domain. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The maximum layer manager 725 described is executed.

[0210] At 1410, the method may include communicating an indication of a maximum number of ports associated with uplink shared channel transmissions that overlap in the time domain with uplink control channel transmissions for the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The maximum port manager 745 described is implemented.

[0211] At 1415, the method may include receiving second control signaling from a network entity, the second control signaling scheduling an uplink control channel transmission associated with the first CORESET pool index. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The described uplink control channel scheduling manager 730 is executed.

[0212] At 1420, the method may include receiving a third control signaling from a network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, wherein the third control signaling indicates a number of ports associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described with reference to Figure 7 The described uplink shared channel scheduling manager 735 is executed.

[0213] At 1425, the method may include transmitting at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on a maximum number of layers and a number of layers associated with the uplink shared channel transmission, and wherein transmitting at least one of the uplink control channel transmission or the uplink shared channel transmission is based on a maximum number of ports and a number of ports associated with the uplink shared channel transmission. The operations of 1425 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed by as described in reference to Figure 7 The described uplink transmission manager 740 is performed.

[0214] Fig.15 A flow chart illustrating a method 1500 for supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 as well as Figures 9 to 12 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1505, the method may include communicating first control signaling with the UE, the first control signaling indicating a maximum number of layers associated with uplink shared channel transmissions that overlap in the time domain with uplink control channel transmissions for the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The described maximum layer manager 1125 is executed.

[0216] At 1510, the method may include sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with the first CORESET pool index. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The described uplink control channel scheduling manager 1130 is executed.

[0217] At 1515, the method may include sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with the second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The described uplink shared channel scheduling manager 1135 is executed.

[0218] At 1520, the method may include receiving, from the UE, at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.11 The described uplink transmission manager 1140 is performed.

[0219] Fig.16 A flow chart illustrating a method 1600 for supporting overlapping PUCCH transmission and PUSCH transmission according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 as well as Figures 9 to 12 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0220] At 1605, the method may include communicating first control signaling with the UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described maximum layer manager 1125 is executed.

[0221] At 1610, the method may include communicating an indication of a maximum number of ports associated with uplink shared channel transmissions that overlap in the time domain with uplink control channel transmissions for the UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11The maximum port manager 1145 described is implemented.

[0222] At 1615, the method may include sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with the first CORESET pool index. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The described uplink control channel scheduling manager 1130 is executed.

[0223] At 1620, the method may include sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with the second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, wherein the third control signaling indicates a number of ports associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.11 The described uplink shared channel scheduling manager 1135 is executed.

[0224] At 1625, the method may include receiving, from the UE, at least one of an uplink control channel transmission according to a first CORESET pool index or an uplink shared channel transmission according to a second CORESET pool index based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission, and wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission is based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed by as described in reference to Fig.11 The described uplink transmission manager 1140 is performed.

[0225] The following provides an overview of various aspects of the disclosure:

[0226] Aspect 1: A method for wireless communication at a UE, the method comprising: communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; receiving second control signaling from the network entity, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; receiving third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and transmitting at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index based at least in part on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0227] Aspect 2: A method according to Aspect 1, wherein conveying the first control signaling includes: conveying an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is at least partially based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0228] Aspect 3: The method according to aspect 2, wherein the uplink shared channel transmission comprises codebook-based uplink shared channel transmission.

[0229] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; selecting a subset of layers in the number of layers based at least in part on the determination, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers; and sending the uplink control channel transmission and the uplink shared channel transmission via the subset of layers.

[0230] Aspect 5: A method according to Aspect 4, wherein receiving the third control signaling includes: receiving an indication of an SRS resource set or a DMRS port set corresponding to the number of layers, and wherein selecting the subset of layers includes selecting a subset of the SRS resource set or a subset of the DMRS port set.

[0231] Aspect 6: According to the method described in any one of Aspects 1 to 3, the method further includes: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending one of the uplink control channel transmission or the uplink shared channel transmission at least partially based on the determination and discarding one of the uplink control channel transmission or the uplink shared channel transmission.

[0232] Aspect 7: According to the method described in Aspect 6, the method also includes: selecting to discard the one based at least in part on the fact that one of the uplink control channel transmission or the uplink shared channel transmission is associated with a fixed CORESET pool index, the one has a lower priority, the one is the uplink control channel transmission and carries a channel state information report, the one is the uplink shared channel transmission and the uplink control channel transmission carrying hybrid automatic repeat request feedback information, the one is scheduled for transmission at a later time, or the one is scheduled for periodic or semi-static transmission.

[0233] Aspect 8: According to the method described in any one of Aspects 1 to 3, the method further includes: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; and at least partially based on the determination, multiplexing the information associated with the uplink control channel transmission onto the uplink shared channel transmission, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission includes sending the uplink shared channel transmission.

[0234] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: determining that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain based at least in part on a first communication resource associated with the uplink control channel transmission and a second communication resource associated with the uplink shared channel transmission, wherein the second control signaling indicates the first communication resource, wherein the third control signaling indicates the second communication resource, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is at least in part based on the determination.

[0235] Aspect 10: A method according to any one of Aspects 1 to 9, wherein receiving the third control signaling includes: receiving an indication that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is at least partially based on the indication.

[0236] Aspect 11: The method according to any one of aspects 1 to 10, wherein communicating the first control signaling includes: receiving the first control signaling from the network entity.

[0237] Aspect 12: The method according to any one of aspects 1 to 11, wherein communicating the first control signaling includes: sending an indication of UE capabilities corresponding to the maximum number of layers.

[0238] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission, and the uplink control channel transmission is associated with one layer.

[0239] Aspect 14: A method for wireless communication at a network entity, the method comprising: communicating first control signaling with a UE, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain; sending a second control signaling to the UE, the second control signaling scheduling an uplink control channel transmission associated with a first CORESET pool index; sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second CORESET pool index, wherein the third control signaling indicates the number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; and receiving at least one of the uplink control channel transmission according to the first CORESET pool index or the uplink shared channel transmission according to the second CORESET pool index from the UE based at least in part on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

[0240] Aspect 15: A method according to Aspect 14, wherein conveying the first control signaling includes: conveying an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission is at least partially based on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

[0241] Aspect 16: The method according to aspect 15, wherein the uplink shared channel transmission comprises codebook-based uplink shared channel transmission.

[0242] Aspect 17: According to the method described in any one of Aspects 14 to 16, the method further includes: receiving the uplink control channel transmission and the uplink shared channel transmission via a subset of layers in the number of layers, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, and wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers.

[0243] Aspect 18: The method according to Aspect 17, wherein sending the third control signaling includes: sending an indication of an SRS resource set or a DMRS port set corresponding to the number of layers.

[0244] Aspect 19: A method according to any one of Aspects 14 to 16, wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission includes: receiving one of the uplink control channel transmission or the uplink shared channel transmission, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

[0245] Aspect 20: A method according to any one of Aspects 14 to 16, wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission includes: receiving the uplink shared channel transmission, wherein information associated with the uplink control channel transmission is multiplexed onto the uplink shared channel transmission, and wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

[0246] Aspect 21: A method according to any one of Aspects 14 to 20, wherein sending the third control signaling includes: sending an indication that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is at least partially based on the indication.

[0247] Aspect 22: The method according to any one of aspects 14 to 21, wherein communicating the first control signaling includes: sending the first control signaling.

[0248] Aspect 23: The method according to any one of aspects 14 to 22, wherein communicating the first control signaling includes: receiving an indication of UE capabilities corresponding to the maximum number of layers.

[0249] Aspect 24: The method according to any one of Aspects 14 to 23, wherein the maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission, and the uplink control channel transmission is associated with one layer.

[0250] Aspect 25: A UE comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the UE to perform a method according to any one of aspects 1 to 13.

[0251] Aspect 26: An apparatus comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0252] Aspect 27: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0253] Aspect 28: A network entity, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the network entity to perform a method according to any one of aspects 14 to 24.

[0254] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 14 to 24.

[0255] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 14 to 24.

[0256] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0257] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0258] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0259] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0260] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0261] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes computer program to be transferred from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0262] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0263] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0264] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0265] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0266] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission overlapping with an uplink control channel transmission for the UE in the time domain; receiving second control signaling from the network entity, the second control signaling scheduling uplink control channel transmission associated with the first control resource set pool index; receiving a third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second control resource set pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; as well as At least one of the uplink control channel transmission according to the first control resource set pool index or the uplink shared channel transmission according to the second control resource set pool index is transmitted based at least in part on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

2. The method of claim 1 , wherein communicating the first control signaling comprises: and communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

3. The method of claim 2, wherein the uplink shared channel transmission comprises a codebook-based uplink shared channel transmission.

4. The method according to claim 1, further comprising: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; selecting a subset of layers in the number of layers based at least in part on the determining, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers; as well as The uplink control channel transmission and the uplink shared channel transmission are transmitted via the subset of layers.

5. The method according to claim 4, wherein receiving the third control signaling comprises: An indication of a set of sounding reference signal resources or a set of demodulation reference signal ports corresponding to the number of layers is received, and wherein selecting the subset of layers comprises selecting a subset of the set of sounding reference signal resources or a subset of the set of demodulation reference signal ports.

6. The method according to claim 1, further comprising: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission comprises sending one of the uplink control channel transmission or the uplink shared channel transmission based at least in part on the determination and discarding one of the uplink control channel transmission or the uplink shared channel transmission.

7. The method according to claim 6, further comprising: The one is selected to be discarded based at least in part on the fact that one of the uplink control channel transmission or the uplink shared channel transmission is associated with a fixed control resource set pool index, the one has a lower priority, the one is the uplink control channel transmission and carries a channel state information report, the one is the uplink shared channel transmission and the uplink control channel transmission carrying hybrid automatic repeat request feedback information, the one is scheduled for transmission at a later time, or the one is scheduled for periodic or semi-static transmission.

8. The method according to claim 1, further comprising: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; as well as Based at least in part on the determination, information associated with the uplink control channel transmission is multiplexed onto the uplink shared channel transmission, wherein transmitting at least one of the uplink control channel transmission or the uplink shared channel transmission comprises transmitting the uplink shared channel transmission.

9. The method according to claim 1, further comprising: Based at least in part on a first communication resource associated with an uplink control channel transmission and a second communication resource associated with an uplink shared channel transmission, it is determined that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein the second control signaling indicates the first communication resource, wherein the third control signaling indicates the second communication resource, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the determination.

10. The method according to claim 1, wherein receiving the third control signaling comprises: An indication is received that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the indication.

11. The method of claim 1 , wherein communicating the first control signaling comprises: The first control signaling is received from the network entity.

12. The method of claim 1, wherein communicating the first control signaling comprises: An indication of UE capabilities corresponding to the maximum number of layers is sent.

13. The method of claim 1, wherein: The maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission, and The uplink control channel transmission is associated with a layer.

14. A method for wireless communication at a network entity, the method comprising: communicating first control signaling with a user equipment (UE), the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission overlapping in the time domain with an uplink control channel transmission for the UE; Sending a second control signaling to the UE, where the second control signaling schedules the sending of an uplink control channel associated with the first control resource set pool index; Sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second control resource set pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; as well as At least partly based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission, receiving from the UE at least one of the uplink control channel transmission according to the first control resource set pool index or the uplink shared channel transmission according to the second control resource set pool index.

15. The method of claim 14, wherein communicating the first control signaling comprises: communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

16. The method of claim 15, wherein the uplink shared channel transmission comprises a codebook-based uplink shared channel transmission.

17. The method according to claim 14, further comprising: The uplink control channel transmission and the uplink shared channel transmission are received via a subset of layers in the number of layers, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers, and wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers.

18. The method according to claim 17, wherein sending the third control signaling comprises: An indication of a sounding reference signal resource set or a demodulation reference signal port set corresponding to the number of layers is sent.

19. The method of claim 14, wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission comprises: One of the uplink control channel transmission or the uplink shared channel transmission is received, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

20. The method of claim 14, wherein receiving at least one of the uplink control channel transmission or the uplink shared channel transmission comprises: The uplink shared channel transmission is received, wherein information associated with the uplink control channel transmission is multiplexed onto the uplink shared channel transmission, wherein the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers.

21. The method according to claim 14, wherein sending the third control signaling comprises: An indication is sent that the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain, wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the indication.

22. The method of claim 14, wherein communicating the first control signaling comprises: Send the first control signaling.

23. The method of claim 14, wherein communicating the first control signaling comprises: An indication of UE capabilities corresponding to the maximum number of layers is received.

24. The method of claim 14, wherein: The maximum number of layers includes the total number of layers used for uplink control channel transmission and uplink shared channel transmission, and The uplink control channel transmission is associated with a layer.

25. A user equipment (UE), the user equipment (UE) comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the UE to: communicating first control signaling with a network entity, the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission overlapping with an uplink control channel transmission for the UE in the time domain; receiving second control signaling from the network entity, the second control signaling scheduling uplink control channel transmission associated with the first control resource set pool index; receiving a third control signaling from the network entity, the third control signaling scheduling an uplink shared channel transmission associated with a second control resource set pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; as well as At least one of the uplink control channel transmission according to the first control resource set pool index or the uplink shared channel transmission according to the second control resource set pool index is transmitted based at least in part on the maximum number of layers and the number of layers associated with the uplink shared channel transmission.

26. The UE of claim 25, wherein the instructions for communicating the first control signaling are executable by the processor to cause the UE to: and communicating an indication of a maximum number of ports associated with an uplink shared channel transmission that overlaps with an uplink control channel transmission for the UE in the time domain, wherein the third control signaling indicates the number of ports associated with the uplink shared channel transmission, and wherein sending at least one of the uplink control channel transmission or the uplink shared channel transmission is based at least in part on the maximum number of ports and the number of ports associated with the uplink shared channel transmission.

27. The UE of claim 26, wherein the uplink shared channel transmission comprises a codebook-based uplink shared channel transmission.

28. The UE of claim 25, wherein the instructions are further executable by the processor to cause the UE to: determining that the number of layers associated with the uplink shared channel transmission exceeds the maximum number of layers; selecting a subset of layers in the number of layers based at least in part on the determining, wherein a second number of layers corresponding to the subset of layers corresponds to the maximum number of layers; as well as The uplink control channel transmission and the uplink shared channel transmission are transmitted via the subset of layers.

29. The UE of claim 28, wherein the instructions for receiving the third control signaling are executable by the processor to cause the UE to: An indication of a set of sounding reference signal resources or a set of demodulation reference signal ports corresponding to the number of layers is received, and wherein selecting the subset of layers comprises selecting a subset of the set of sounding reference signal resources or a subset of the set of demodulation reference signal ports.

30. A network entity, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the network entity to: communicating first control signaling with a user equipment (UE), the first control signaling indicating a maximum number of layers associated with an uplink shared channel transmission overlapping in the time domain with an uplink control channel transmission for the UE; Sending a second control signaling to the UE, where the second control signaling schedules sending of an uplink control channel associated with the first control resource set pool index; Sending a third control signaling to the UE, the third control signaling scheduling an uplink shared channel transmission associated with a second control resource set pool index, wherein the third control signaling indicates a number of layers associated with the uplink shared channel transmission, and wherein the uplink shared channel transmission at least partially overlaps with the uplink control channel transmission in the time domain; as well as At least partly based on the maximum number of layers and the number of layers associated with the uplink shared channel transmission, receiving from the UE at least one of the uplink control channel transmission according to the first control resource set pool index or the uplink shared channel transmission according to the second control resource set pool index.

Images