Uplink control information multiplexing over frequency division multiplexing channels

Abstract

Methods, systems, and devices for wireless communication are described. The described techniques provide procedures, conditions, and signaling that, when scheduling two frequency division multiplexing (FDM) repetitions for a user equipment (UE), may determine whether to transmit uplink control information (UCI) via a single repetition or via multiple repetitions based on the procedures, the conditions, and the signaling. For example, the network may indicate that the UE will take a first behavior (e.g., transmit UCI via a single repetition) or a second behavior (e.g., transmit UCI via two repetitions). If the UE is configured to transmit the UCI via two repetitions, the UE may determine whether one or more conditions are satisfied. If such a condition is not satisfied, the UE may default the first behavior. The UE may determine which behavior to apply based on explicit signaling from the network, the type of UCI, or a combination thereof.

Description

Technical Field

[0001] The following relates to wireless communications including uplink control information multiplexing on a frequency division multiplexed channel. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, 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 communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting uplink control information (UCI) multiplexing on frequency division multiplexing (FDM) channels. For example, the described technology provides procedures, conditions and signaling, based on which a user equipment (UE) can determine whether to send UCI via a single repetition or via multiple repetitions when two FDM repetitions are scheduled for the UE. For example, the network may indicate that the UE will adopt a first behavior (e.g., sending UCI via a single repetition) or a second behavior (e.g., sending UCI via two repetitions). If the UE is configured to send UCI via two repetitions, the UE may determine whether one or more conditions are met (in which case the UE may adopt the second behavior). If such conditions are not met, the UE may default to the first behavior. In some cases (e.g., based on rules or based on control signaling), the UE may determine which behavior to apply based on explicit signaling from the network, the type of UCI, or a combination thereof. If the UE defaults to or is configured to apply the first behavior, the UE may select one of the two repetitions on which to multiplex the UCI based on one or more conditions (eg, sounding reference (SRS), redundancy version (RV), frequency range, etc.).

[0004] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving control signaling that schedules a first set of resource blocks (RBs) associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval; determining whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs based on the control signaling; and sending UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval; determine based on the control signaling whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs; and send UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval; a component for determining whether to transmit UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs based on the control signaling; and a component for transmitting UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: receive control signaling that schedules a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval; determine based on the control signaling whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs; and send UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and a second set of RBs based on the determination and whether one or more conditions are satisfied.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of RBs in a first set of RBs is equal to a second number of RBs in a second set of RBs.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of PTRS ports associated with a first set of RBs is equal to a second number of PTRS ports associated with a second set of RBs.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and a second set of RBs based on whether a first PTRS density associated with the first set of RBs is equal to a second PTRS density associated with a second set of RBs.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of resource elements of a first set of RBs is equal to a second number of resource elements of a second set of RBs.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether one or more additional UCI messages can be scheduled during the first set of RBs or the second set of RBs.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control signaling that includes an indication of a first trigger state associated with sending UCI via one of the first set of RBs or the second set of RBs and a second trigger state associated with sending UCI via both the first set of RBs and the second set of RBs.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of a first trigger state or a second trigger state in control signaling, and wherein the determination may be based on the indication of the first trigger state or the second trigger state.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI includes aperiodic channel state information or semi-persistent channel state information associated with an uplink shared channel.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determination may include operations, features, components, or instructions for determining whether the type of UCI may be associated with sending the UCI via a first set of RBs or sending the UCI via both the first set of RBs and the second set of RBs.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control signaling that schedules UCI on a physical uplink control channel that temporally overlaps with the first set of RBs and the second set of RBs, wherein a type of the UCI may be associated with the physical uplink control channel.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving third control signaling indicating that the first type of UCI may be associated with sending the UCI via one of the first set of RBs or the second set of RBs, and the second type of UCI may be associated with sending the UCI via both the first set of RBs and the second set of RBs, wherein the determination may be based on whether the type of the UCI may be the first type or the second type.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the type of UCI includes feedback information, a scheduling request, semi-persistent channel state information associated with a physical uplink control channel, or periodic channel state information.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determination may include operations, features, components, or instructions for determining to send UCI via a first set of RBs or one of a second set of RBs, and selecting the first set of RBs or one of the second set of RBs based on the determination, wherein the sending may be based on the selection.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the selection may include operations, features, components, or instructions for the following actions: selecting the first set of RBs based on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, a number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control signaling, via a control channel, that schedules additional UCI, wherein the determination includes determining to send the UCI via both the first set of RBs and the second set of RBs.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI may include operations, features, components, or instructions for sending the UCI and the additional UCI via the first set of RBs.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for sending UCI via a first set of RBs and sending additional UCI via a second set of RBs.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending UCI may include operations, features, components, or instructions for the following actions: sending UCI via both the first set of RBs and the second set of RBs, and sending additional UCI via both the first set of RBs and the second set of RBs.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying an error condition based on receiving control signaling scheduling additional UCI, and refraining from sending the additional UCI based on the error condition.

[0028] A method for wireless communication at a network entity is described. The method may include: sending control signaling that schedules a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval; determining whether to receive UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs based on the control signaling; and receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0029] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send control signaling that schedules a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval; determine based on the control signaling whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs; and receive UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0030] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for sending control signaling to schedule a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval; a component for determining whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs based on the control signaling; and a component for receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0031] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to: send control signaling that schedules a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval; determine based on the control signaling whether to receive UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs; and receive UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving UCI may include operations, features, components, or instructions for receiving UCI via a first set of RBs or via both the first set of RBs and a second set of RBs based on the determination and whether one or more conditions are satisfied.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second control signaling that includes an indication of a first trigger state associated with receiving UCI via one of the first set of RBs or the second set of RBs and a second trigger state associated with receiving UCI via both the first set of RBs and the second set of RBs.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determination may include operations, features, components, or instructions for determining whether the type of UCI may be associated with receiving the UCI via a first set of RBs or receiving the UCI via both the first set of RBs and a second set of RBs.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the determination may include operations, features, components, or instructions for determining that UCI is received via one of a first set of RBs or a second set of RBs, and selecting one of the first set of RBs or the second set of RBs based on the determination, wherein the reception may be based on the selection.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the selection may include operations, features, components, or instructions for the following actions: selecting the first set of RBs based on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, a number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending second control signaling scheduling additional UCI via the control channel, wherein the determination includes determining to receive the UCI via both the first set of RBs and the second set of RBs. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1An example of a wireless communication system supporting uplink control information (UCI) multiplexing on a frequency division multiplexing (FDM) channel according to one or more aspects of the present disclosure is illustrated.

[0039] Figure 2 An example of a wireless communication system supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 3 An example of a timeline supporting UCI multiplexing on an FDM channel in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 4 An example of a process flow for supporting UCI multiplexing on FDM channels according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 5 and Figure 6 A block diagram of a device supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is shown.

[0043] Figure 7 A block diagram of a communication manager supporting UCI multiplexing on an FDM channel is shown in accordance with one or more aspects of the present disclosure.

[0044] Figure 8 A diagram of a system including a device supporting UCI multiplexing on an FDM channel is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig. 9 and Fig.10 A block diagram of a device supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is shown.

[0046] Fig.11 A block diagram of a communication manager supporting UCI multiplexing on an FDM channel is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.12 A diagram of a system including a device supporting UCI multiplexing on an FDM channel is shown in accordance with one or more aspects of the present disclosure.

[0048] Figures 13 to 16 A flow chart illustrating a method of supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0049] Some wireless communication systems may support uplink repetitions of frequency division multiplexing (FDM) in the same time interval (e.g., the same set of time intervals). A first set of resource blocks (RBs) associated with a first beam and a first antenna panel and a second set of RBs associated with a second beam and a second antenna panel may be granted to the UE. The UE may also be triggered to send uplink control information (UCI) (e.g., channel state information (CSI), feedback signaling, etc.) during the same time interval. The UE may not have a mechanism for determining whether to send UCI via two sets of RBs (e.g., multiplexed with two uplink repetitions) or via a single set of RBs (e.g., multiplexed with a single uplink repetition). If the UE determines (e.g., or is commanded) to send UCI via a single set of RBs, the UE may not have a mechanism for determining which set of RBs to select to send UCI. Some wireless communication systems may not support any mechanism for the UE and the network entity to determine whether to send UCI via two repetitions or one repetition or for selecting which repetition to use (e.g., in the case where only one repetition is selected).

[0050] The techniques described herein provide procedures, conditions, and signaling based on which the UE can determine whether to send UCI via a single repetition or via multiple repetitions when two FDM repetitions are scheduled for the UE. For example, the network may indicate that the UE will adopt a first behavior (e.g., sending UCI via a single repetition) or a second behavior (e.g., sending UCI via two repetitions). If the UE is configured to send UCI via two repetitions, the UE may determine whether one or more conditions are met (in which case the UE may adopt the second behavior). If such conditions are not met, the UE may default to one of these behaviors (e.g., the first behavior). In some cases (e.g., rule-based or control signaling-based), the UE may determine which behavior to apply based on explicit signaling from the network, the type of UCI, or a combination thereof. If the UE defaults to or is configured to apply the first behavior, the UE may select one of the two repetitions on which to multiplex the UCI based on one or more conditions (e.g., sounding reference (SRS), redundancy version (RV), frequency range, etc.).

[0051] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to wireless communication systems, timelines, and process flows. Aspects of the present disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow charts involving UCI multiplexing on FDM channels.

[0052] Figure 1An example of a wireless communication system 100 supporting UCI multiplexing on an FDM channel 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.

[0053] 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).

[0054] 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 communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0055] 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.

[0056] In some examples, the network entities 105 may communicate with the core network 130, or communicate 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 through the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 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 .

[0057] 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).

[0058] 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. The 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 transmit receive point (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)).

[0059] 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 DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 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 can be within the protocol layer (e.g., some functions of the protocol layer can 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 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can 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.

[0060] 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 coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas 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.

[0061] 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 a connection 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), wherein 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 defining a signaling message (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., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0062] 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.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the 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., the IAB donor may relay for transmissions to UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, 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 to the child IAB node 104 or the UE 115 .

[0063] 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 transmissions to the UE 115 via the IAB node 104, or may directly signal the transmissions 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 transmissions (e.g., transmissions 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 .

[0064] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support UCI multiplexing on FDM channels as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0065] 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 terminology, 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.

[0066] 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.

[0067] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting 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 these devices and any part (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 part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0068] 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 used 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 a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0069] 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 an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0070] 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 the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configured to support communications using one of the carrier bandwidths in the 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 the carrier bandwidth.

[0071] 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 employing 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 amount 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 higher amount of resource elements (e.g., in the transmission duration) and a relatively higher modulation scheme order may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0072] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefix. 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.

[0073] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where the sampling period, Δ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).

[0074] 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.

[0075] A subframe, slot, mini-slot, or 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)).

[0076] Carrier multiplexing physical channels may be used for communication according to various techniques. Physical control channels and physical data channels may be multiplexed via downlink carriers for signaling using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of 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., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE115 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 .

[0077] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, 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 (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. 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 may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0078] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user 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.

[0079] 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.

[0080] 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.

[0081] The wireless communication system 100 may support synchronous 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 or asynchronous operation.

[0082] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0083] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other energy-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0084] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private 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.

[0085] In some examples, a 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 or (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of 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.

[0086] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0087] 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 stratum (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 transferred through user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to IP services 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.

[0088] 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). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. 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) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0089] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, 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 facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and 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 vary by country or regulatory agency.

[0090] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). 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 using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0091] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, 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.

[0092] 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 technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0093] 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 conveyed via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed 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).

[0094] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with 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. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0095] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or 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.

[0096] 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 non-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).

[0097] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving 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 receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving 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 receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving 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).

[0098] 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 processing 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.

[0099] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful reception of data. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood 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 throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a 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.

[0100] As described herein, UE 115 may receive uplink DCI (e.g., a DCI message that grants resources for uplink transmission) (e.g., from network entity 105). The DCI may trigger a CSI report on the PUSCH (e.g., an aperiodic (AP) CSI report). Up to 128 trigger states may be configured via RRC signaling (e.g., a higher layer parameter AperiodicTriggerStateList). Each trigger state in the trigger state list may be linked to one or more (e.g., up to 16) CS reporting settings. If the CSI request field (e.g., in a DCI message) has multiple bits (e.g., N bits), up to 2 trigger states may be activated via MAC-CE signaling. N-1The CSI request field may indicate an on trigger state (e.g., it may trigger one or more CSI reports). Thus, the value of the code point of the CSI request field in the uplink DCI may indicate a trigger state (e.g., an aperiodic trigger state for AP CSI reporting) and may trigger one or more CSI reports.

[0101] In some examples, the wireless communication system 100 may support PUSCH repetitions based on a single DCI (e.g., in a time division multiplexing (TDM) manner). Each repetition may correspond to a different set of transmission parameters (e.g., different beams, different spatial relationships, different transmission configuration indicator (TCI) states, different power control parameters, different precoding configurations or predecoders, etc.). Each repetition may be associated with the same transport block (TB). To support such repetitions, the two sets of repetitions may correspond to two different sounding reference signal (SRS) resource sets. The DCI may indicate two sets of transmission parameters (e.g., two beams, two sets of power control parameters, etc.) via two corresponding SRI fields for both codebook-based transmission and non-codebook-based transmission. For codebook-based PUSCH, the DCI may include two TMPI fields to indicate two predecoders for the two sets of repetitions. The two sets of repetitions may be cyclic (e.g., repetitions in a first set of repetitions may alternate in time with repetitions in a second set of repetitions), or the first set of repetitions may precede the second set of repetitions.

[0102] UE 115 may use beam diversity to send uplink control signaling (UCI, such as A-CSI, semi-persistent CSI (SP-CSI), etc.) on PUSCH. Such UCI may be sent on PUSCH and carried only on the first PUSCH repetition (e.g., in the case of a single transmit reception point (TRP) where all repetitions are associated with one SRS resource set). In some examples, the UE may send multiple repetitions in a multi-TRP (mTRP) deployment, in which case the UE may be configured to carry A-CSI or SP-CSI on two PUSCH repetitions. If one or more conditions are met (e.g., if the two repetitions have the same length and if no UCI other than A-CSI is multiplexed on either of the two PUSCH repetitions), A-CSI may be multiplexed on the first repetition from the first set of repetitions and on the first repetition from the second set of repetitions. Otherwise (e.g., based on a fallback or default behavior), A-CSI may be multiplexed on the first repetition. When multiplexing CSI over two repetitions, UE 115 may not expect the number of actual PTRS ports used for the two repetitions to be different.This behavior may be followed when a triggering condition may be enabled for such behavior (eg, indicated in the CSI request field of a DCI message scheduling PUSCH).

[0103] Such conditions may support multiplexing CSI over two PUSCH repetitions (e.g., which are TDM). For UCI, the mother code rate of the polar code (e.g., on which the encoding is based) may be based on the number of resource elements (Res) available for UCI multiplexing. The Rex available for UCI multiplexing may be a function of the available number of Res for PUSCH excluding DMRS symbols (e.g., all Res for DMRS symbols) and PTRS REs and the presence of other UCI (e.g., in addition to A-CSI or SP-CSI requested by the DCI scheduling the PUSCH). If the mother codes of the UCI to be multiplexed over two repetitions are not the same, the receiver (e.g., the network entity 105) may not be able to soft combine the repetitions, and the UE complexity may increase because two rate matching and two encodings may be performed to send the UCI.

[0104] Other UCI that may conflict with the scheduled UCI may refer to UCI that was originally scheduled or configured to be sent on the PUCCH, but because the PUCCH overlaps with one of the TDM PUSCH repetitions, the conflicting UCI may be multiplexed on the PUSCH repetition (e.g., it may be different from the UCI on the PUSCH triggered by the DCI that schedules or activates the PUSCH, such as A-CSI or SP-CSI). Other UCI may include HARQ-Ack signaling, periodic CSI, SP-CSI on the PUCCH (e.g., activated by MAC-CE), scheduling request (SR), etc. TDM PUSCH repetition may not be applied to such UCI (e.g., scheduled on the PUCCH) because the TDM PUSCH repetition may not overlap with such UCI. The techniques for FDM PUSCH repetition described herein may support multiplexing of such UCI in one or both repetitions.

[0105] As described herein, without a mechanism for multiplexing UCI onto one or more PUSCH repetitions over FDM, the UE may fail to send UCI or a network entity may fail to monitor or receive UCI, which may result in increased retransmissions, increased failed data or control signaling, decreased throughput, increased system latency, and a reduced user experience.

[0106] The techniques described herein provide procedures, conditions, and signaling based on which the UE 115 can determine whether to send UCI via a single repetition or via multiple repetitions when two FDM repetitions are scheduled for the UE 115. For example, the network may indicate that the UE 115 will adopt a first behavior (e.g., sending UCI via a single repetition) or a second behavior (e.g., sending UCI via two repetitions). If the UE is configured to send UCI via two repetitions, the UE 115 may determine whether one or more conditions are met (in which case the UE may adopt the second behavior). If such conditions are not met, the UE may default to one of these behaviors (e.g., the first behavior). In some cases (e.g., based on rules or based on control signaling), the UE 115 may determine which behavior to apply based on explicit signaling from the network, the type of UCI, or a combination thereof. If the UE 115 defaults to or is configured to apply the first behavior, the UE 115 may select one of the two repetitions on which the UCI is to be multiplexed based on one or more conditions (e.g., SRS resource set, RV, frequency range, etc.).

[0107] Figure 2An example of a wireless communication system 200 supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include one or more network entities 105 (e.g., network entity 105-a and network entity 105-b) and one or more UEs 115 (e.g., UE 115-a), which may be reference 1. Figure 1 Examples of corresponding devices described. UE 115-a may communicate with network entity 105-a and network entity 105-b. For example, UE 115-a may operate in an mTRP deployment, in which case UE 115-a may send one or more uplink messages (e.g., a first repetition and a second repetition of a TB) to both network entity 105-a and network entity 105-b. In such examples, UE 115-a may send a first repetition to network entity 105-a via beam 205-a and a second repetition to network entity 105-b via beam 205-b.

[0108] The wireless communication system 200 may support single DCI FDM physical uplink shared channel (PUSCH) signaling. In some examples of FDM PUSCH communication, a single DCI may schedule a PUSCH having two sets of RBs (e.g., a first set 210-a of RBs and a second set 210-b of RBs). The DCI may schedule a first repetition to be sent by a UE 115-a via a first antenna panel using a first beam 205-a (e.g., using a first pre-decoder, a first set of power control parameters, etc.), and a second repetition to be sent by a UE 115-b via a second antenna panel using a second beam 205-b (e.g., using a second pre-decoder, a second set of power control parameters, etc.). Each of the first set 210-a of RBs and the second set 210-b of RBs may be associated with a different set of SRS resources. In some examples, the first set 210-a of RBs and the second set 210-b of RBs may be associated with a single RV (e.g., for joint rate matching across the first set 210-a of RBs and the second set 210-b of RBs), or the first set 210-a of RBs may be associated with a first RV and the second set 210-b of RBs may be associated with a second RV (e.g., to support repetition and separate rate matching across the first set 210-a of RBs and the second set 210-b of RBs). The DCI may include an SRS resource set indicator field, two SRS fields, and two TPMI fields (e.g., for the two repetitions).

[0109] The two repetitions may at least partially overlap in time (e.g., may occupy one or more time intervals in the same time interval, such as one or more symbols). In some examples, the UE 115-a may also be configured to send UCI during one or more symbols of the first set of RBs 210-a and the second set of RBs 210-b that are scheduled (e.g., triggered to send UCI such as non-periodic CSI or semi-persistent channel state information (SP-CSI), or the UCI may be scheduled in a physical uplink control channel (PUCCH) that overlaps in time with the first set of RBs 210-a and the second set of RBs 210-b). In the absence of configuration information from the network entity 105 or rules or both, the UE 115-a may not be able to successfully multiplex UCI with the first set of RBs 210-a, the second set of RBs 210-b, or both. As described herein, the UE 115-a may be configured to send UCI via both the first set 210-a of RBs and the second set 210-b of RBs, but may not be able to do so based on the number of RBs allocated to each PUSCH repetition, the PTRS frequency density, the actual number of PTRS ports in each of the two sets 210 of RBs, or based on other conflicting UCI. In such examples, the UE 115-a may fall back to a default behavior (e.g., may send UCI via one of the first set 210-a of RBs or the second set 210-b of RBs). However, if configured to send UCI via only one of the two sets 210 of RBs, or if the default behavior is fallen back to despite being configured to send UCI via both sets 210 of RBs, the UE 115-a may not have information indicating which of the two sets 210 of RBs the UE 115-a is to select. For UCI signaling (e.g., for UCI that was originally scheduled on the PUCCH but is re-multiplexed with the PUSCH due to overlap in time or frequency or both), the UE 115-a may determine whether to multiplex the additional UCI on two PUSCH repetitions or on only one PUSCH repetition. In the event of a conflict with such additional UCI (e.g., some UCI is to be multiplexed on two repetitions and some UCI is to be multiplexed on a single repetition), the UE may determine a transmission configuration for all UCI. The techniques described herein provide rules, conditions, signaling, or a combination thereof that support such a determination by the UE 115-a (e.g., the UE 115-a may determine when to send UCI via two repetitions and when to send UCI via a single repetition).

[0110] For an FDM PUSCH consisting of two sets 210 of RBs (e.g., a first set 210-a of RBs and a second set 210-b of RBs) corresponding to two PUSCH repetitions (e.g., associated with different SRS resources and different sets of transmission parameters (such as different beams 205 and different sets of transmission parameters)), the UE 115-a may be configured to multiplex one or more UCIs on two PUSCH repetitions (e.g., this may be referred to as behavior 1), or may be configured to multiplex one or more UCIs on only one PUSCH repetition (e.g., this may be referred to as behavior 0). As described herein, the configuration of whether the UE 115-a multiplexes the UCI with one repetition or two repetitions may be indicated to the UE 115-a via control signaling (e.g., RRC signaling, MAC-CE signaling, DCI signaling, or any combination thereof).

[0111] If UE 115-a is configured to multiplex one or more UCIs across two PUSCH repetitions (e.g., via a first set of RBs 210-a and a second set of RBs 210-b) (e.g., behavior 1), UE 115-a may determine whether one or more conditions are met. If these conditions are met, UE 115-a may multiplex UCIs across two repetitions (e.g., according to the configured behavior 1). However, if one or more of these conditions are not met, UE 115-a may fall back to a default behavior (e.g., behavior 0).

[0112] For example, if the first set of RBs 210-a and the second set of RBs 210-b have the same number of RBs (e.g., satisfying the first condition), the UE 115-a may adopt behavior 1. In some examples, if the first set of RBs 210-a and the second set of RBs 210-b do not have the same number of RBs (e.g., not satisfying the first condition), the UE 115-a may default to behavior 0. In some cases, the RBs may be assigned based on a frequency domain resource allocation (FDRA) field in a scheduling DCI message, which may indicate the number of RBs allocated for the PUSCH (e.g., N), with a first number of RBs (e.g., N / 2 RBs) assigned to the first set of RBs and a remaining number of RBs (e.g., N / 2 RBs) assigned to the second set of RBs. In such examples, if N is an odd value (e.g., not an even value), the two sets of RBs do not have an equal number of RBs (e.g., the UE 115-a may determine that the first condition is not satisfied).

[0113] In some examples, if the first set 210-a of RBs and the second set 210-b of RBs are associated with the same number of PTRS ports (e.g., each of the two sets 210 of RBs has 0 PRS ports, 1 PTRS port, or 2 PTRS ports) (e.g., the second condition is met), the UE 115-a may adopt behavior 1. If the two sets 210 of RBs are associated with different numbers of RBs (e.g., the second condition is not met), the UE 115-a may default to behavior 0 (e.g., despite being configured to send UCI via both sets 210 of RBs). The actual number of PTRS ports associated with each set 210 of RBs may depend on the corresponding indicated SRI or TPMI of the respective set 210 of RBs. Considering that the DCI message may indicate two SRIs, two TPMIs, or both for the two sets 210 of RBs, there may be different actual numbers of PTRS ports (e.g., in this case, the second condition may not be met).

[0114] In some examples, if the first set 210-a of RBs and the second set 210-b of RBs are associated with the same PTRS frequency density (e.g., satisfying the third condition), UE 115-a may adopt behavior 1. In some cases, it is possible that the first set 210-a of RBs has a different PTRS frequency domain density than the second set 210-b of RBs. If the first set 210-a of RBs and the second set 210-b of RBs are associated with different PTRS frequency densities (e.g., not satisfying the third condition), UE 115-a may adopt behavior 0.

[0115] In some examples, if the available number of resource elements for the PUSCH (e.g., excluding one or more resources, such as DMRS symbols and PTRS resource elements) is the same for the first set of RBs 210-a and the second set of RBs 210-b (e.g., the fourth condition is satisfied), the UE 115-a may adopt behavior 1. In some examples, one or more other conditions may not be satisfied, but if the fourth condition is satisfied, the UE 115-a may still adopt behavior 1. For example, one or more of the first condition (e.g., the first set of RBs 210-a and the second set of RBs 210-b have the same number of RBs), the second condition (e.g., the first set of RBs 210-a and the second set of RBs 210-b are associated with the same number of PTRS ports), and the third condition (e.g., the first set of RBs 210-a and the second set of RBs 210-b are associated with the same PTRS frequency density) may not be satisfied. However, if the fourth condition is satisfied, the UE 115-a may still adopt behavior 1. Similarly, if the first condition, the second condition, and the third condition are met, the UE 115-a may determine that the fourth condition is also met. Therefore, in some examples, the UE 115-a may determine whether to adopt behavior 1 or behavior 0 (e.g., when configured to adopt behavior 1) based on whether any or all of the first condition, the second condition, or the third condition are met (e.g., as indicated via control signaling, or as defined in one or more standard documents, etc.). In some examples, the UE 115-a may determine whether to adopt behavior 1 or behavior 0 based on whether the fourth condition is met (e.g., without reference to the first condition, the second condition, or the third condition) (e.g., as indicated via control signaling, or as defined in one or more standard documents, etc.).

[0116] In some examples, if the one or more scheduled UCIs are the only UCIs multiplexed on either of the PUSCH repetitions corresponding to the first set of RBs 210-a and the second set of RBs 210-b (e.g., satisfying the fifth condition), the UE 115-a may adopt behavior 1. For example, if another UCI is scheduled or triggered for transmission via the first set of RBs 210-a or the second set of RBs 210-b, or both, the fifth condition may not be satisfied. The fifth condition may ensure that no other UCI is multiplexed on only one of the PUSCH repetitions (e.g., on only one of the first set of RBs 210-a and the second set of RBs 210-b). In some examples, such as reference Figure 3 Described in more detail, based on detecting additional UCI scheduled for transmission via the first set of RBs 210-a or the second set of RBs 210-b or both, the UE 115-a may drop one or more UCIs, or may multiplex one or more UCIs, or a combination thereof.

[0117] Although described with reference to five conditions, UE 115-a may use any number of conditions (e.g., which may be the same or different than the conditions described herein) to determine whether to employ behavior 1 or behavior 0. UE 115-a may consider one, more, all, or some of these conditions when determining which behavior to employ.

[0118] When UE 115-a is configured to multiplex one or more UCIs on two PUSCH repetitions (e.g., via a first set of RBs 210-a and a second set of RBs 210-b) but one or more conditions (e.g., one, more, all, or any of the first, second, third, fourth, and fifth conditions described herein) are not satisfied, UE 115-a may adopt a fallback behavior (e.g., behavior 0) and may send one or more UCIs via a single set 210 of RBs (e.g., rather than via two sets 210 of RBs). Alternatively, UE 115-a may be configured to multiplex one or more UCIs via only one of the PUSCH repetitions (e.g., behavior 0). In any such examples, UE 115-a may determine with which of the PUSCH repetitions (e.g., which of the first set of RBs 210-a and the second set of RBs 210-b) to multiplex the UCI.

[0119] In some examples, UE 115-a may select a set of RBs 210 on which to send one or more UCIs based on the SRS resource sets associated with the corresponding sets of RBs 210. For example, UE 115-a may select a set of RBs 210 associated with a first SRS resource set.

[0120] The UE 115-a may select a set 210 of RBs on which to send one or more UCIs based on a frequency range associated with each set 210 of RBs. For example, the UE 115-a may send one or more UCIs via a set 210 of RBs having a higher frequency (e.g., a first set 210-a of RBs) or a set 210 of RBs having a lower frequency (e.g., a second set 210-b of RBs).

[0121] The UE 115-a may select a set 210 of RBs on which to send one or more UCIs based on the RV value associated with each PUSCH repetition. For example, a first set 210-a of RBs may be associated with a first RV (e.g., RV=0), and a second set 210-b of RBs may be associated with a second RV (e.g., RV=2). The UE 115-a may multiplex the UCI to a set 210 of RBs having a higher RV value (e.g., the second set 210-b of RBs) because RV=0 may carry systematic bits associated with the PUSCH, and multiplexing the UCI with the repetitions of the PUSCH using RV=0 may reduce the number of systematic bits used for the PUSCH payload.

[0122] The UE 115-a may select a set 210 of RBs on which to send one or more UCIs based on which repetition is associated with a larger number of RBs or a larger number of available resource elements (e.g., excluding DMRS symbols and PTRS resource elements). The UE 115-a may select a set 210 of RBs having a larger number of available resource elements or a smaller number of PTRS resource elements. This may occur, for example, where the UE 115-a defaults to a fallback behavior (e.g., behavior 0) because one of these conditions is not met.

[0123] UE 115-a may select a set 210 of RBs on which to send one or more UCIs based on determining which set 210 of RBs does not include one or more additional UCIs (e.g., in addition to the one or more UCIs for which UE 115-a is determining the set 210 of RBs. For example, UE 115-a may determine that one or more conditions are not satisfied (e.g., another UCI is scheduled or triggered during a time interval associated with the first set 210-a of RBs and the second set 210-b of RBs) and may default to behavior 0. In such examples, UE 115-a may select a set 210 of RBs on which to send the initial UCI to balance the UCI payload multiplexed on each of the two PUSCH repetitions. In some examples, UE 115-a may select a set 210 of RBs on which to schedule additional UCIs (e.g., colliding UCIs) to keep all UCIs in the same PUSCH repetition (e.g., this may support joint coding of UCIs).

[0124] As described herein, the network (e.g., via one or more TRPs) may configure behavior 1 or behavior 0 to UE 115-a (e.g., and if one or more conditions are not met, UE 115-a may default to behavior 0 even if configured with behavior 1). The network may configure one of these behaviors to UE 115-a via control signaling (e.g., RRC signaling, MAC-CE signaling, DCI signaling, or any combination thereof), or UE 115-a may apply a fixed behavior based on the UCI type. As described herein, configuration may refer to configuration performed by the network (e.g., via control signaling), or may refer to a fixed behavior defined in one or more standard documents, which may be applicable to a specific type of UCI behavior.

[0125] In some examples, the UCI may include non-periodic CSI or SP-CSI on the PUSCH. In such examples, RRC signaling may enable behavior 1 for each trigger state, and a DCI message (e.g., a DCI message that schedules PUSCH and triggers CSI) may indicate the trigger state. For example, UE 115-a may receive RRC signaling that enables (e.g., activates or configures) behavior 1 (e.g., supports sending triggered UCI via both the first set of RBs 210-a and the second set of RBs 210-b). In such examples, the RRC signaling may also indicate that behavior 1 is associated with the trigger state. Subsequently, UE 115-a may receive a DCI message indicating the trigger state associated with behavior 1 (e.g., as indicated in the RRC signaling that enables behavior 1). If the DCI message indicates that a trigger state for behavior 1 is enabled, UE 115-a may send UCI (e.g., non-periodic CSI) via both the first set of RBs 210-a and the second set of RBs 210-b (e.g., the non-periodic CSI may be multiplexed over two repetitions unless one or more conditions are not met, in which case UE 115-a may apply a fallback behavior, such as behavior 0). In some examples, if the indicated trigger state is not enabled for behavior 1 (e.g., a second trigger state associated with behavior 0 as configured via RRC signaling, or the absence of a trigger state associated with behavior 1, etc.), UE 115-a may apply behavior 0.

[0126] In some examples, the UCI may include feedback signaling (e.g., HARQ-ACK signaling, scheduling request (SR), SP-CSI on PUCCH, or periodic CSI). In such examples, the behavior configuration of the UCI may be common to all such UCI types (e.g., UCI initially scheduled on a PUCCH that at least partially overlaps in time with a set 210 of RBs). For example, UE 115-a may multiplex any UCI type that was initially scheduled on a PUCCH and multiplexed with a PUSCH due to overlap according to a behavior associated with such UCI. For example, behavior 1 or behavior 0 may be associated with any UCI scheduled or triggered on a PUCCH that partially overlaps with a set of RBs. Such a rule or condition may be indicated via control signaling (e.g., RRC signaling) or may be included in one or more standard documents. Therefore, for any UCI scheduled or triggered on a PUCCH that overlaps in time with a set 210 of RBs, UE 115-a may adopt a behavior associated with such UCI.

[0127] In some examples, the behavior configuration of the UCI may be UCI type specific (e.g., UE 115-a may be configured to multiplex HARQ-ACK on two repetitions, but multiplex periodic CSI on only one repetition, etc.). For example, for UCI that includes HARQ-ACK, UE 115-a may adopt a fixed behavior associated with the HARQ-ACK UCI (e.g., behavior 1 or behavior 0). The behavior of the HARQ-ACK UCI may be RRC configured or included in one or more standard documents, or may be indicated in a DCI message that schedules PUCCH for HARQ-ACK (e.g., a DCI message that is different from a DCI message that schedules FDM PUSCH for set 210 of RBs). For UCI that includes SP-CSI on PUCCH, UE 115-a may adopt a fixed behavior associated with the SP-CSI on PUCCH (e.g., behavior 1 or behavior 0). The behavior of the SP-CSI may be RRC configured, indicated in one or more standard documents, or indicated in a MAC-CE that activates the SP-CSI. For UCI including periodic CSI, UE 115-a may adopt a fixed behavior associated with periodic CSI (eg, behavior 1 or behavior 0). The behavior of SP-CSI may be RRC configured or indicated in one or more standard documents.

[0128] As reference Figure 3Described in more detail, UE 115-a may identify a certain conflict between a first set of one or more UCIs configured with behavior 1 and an additional (e.g., second) set of one or more UCIs configured with behavior 0. In some examples, UE 115-a may resolve the conflict by defaulting to behavior 0 for both UCIs. For example, UE 115-a may apply a fallback behavior (e.g., behavior 0) to one or more UCIs (e.g., because the fifth condition is not satisfied). In such examples, UE 115-a may send a first set of one or more UCIs and a second set of one or more (e.g., conflicting) UCIs according to behavior 0 (e.g., UE 115-a may send a first set of UCIs via a first set 210-a of RBs and a second set of UCIs via a second set 210-b of RBs, or may send both a first set and a second set of UCIs via one of the sets 210 of RBs). In some examples, UE 115-a may ensure that the fifth condition is satisfied by applying behavior 1 to both sets of UCIs. In such an example, UE 115-a may multiplex the first set and the second set of UCI via two PUSCH repetitions to resolve the conflict. In some examples, UE 115-a may determine that this scenario is an error condition (e.g., the fifth condition is not satisfied) and may not send UCI via either set 210 of RBs (e.g., one or both sets of UCI may be discarded).

[0129] Figure 3 An example of a timeline 300 for supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure is illustrated. The timeline 300 may implement or be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, one or more network entities 105 (e.g., one or more TRPs in an mTRP deployment) and one or more UEs 115 (which may be reference Figure 1 to Figure 2 Examples of corresponding devices described herein) can communicate with each other according to timeline 300.

[0130] As described herein, in some cases, a UE may receive a DCI 305 that may schedule a first PUSCH repetition 310-a (e.g., via a first set of RBs 210-a) and a second PUSCH repetition 310-b (e.g., via a second set of RBs 210-b). In some cases, the DCI may schedule or trigger one or more UCIs that may be configured to be transmitted according to behavior 1 or behavior 0. In some examples, the UCI may be scheduled on a PUCCH 315 and may be configured for behavior 0 or behavior 1. In some cases, the UCI associated with behavior 1 may conflict with the UCI associated with behavior 0.

[0131] For example, the first PUCCH 315-a may carry a HARQ-ACK UCI configured for behavior 1, and the second PUCCH 315-b may carry a SR or CSI configured for behavior 0 (e.g., via control signaling, or according to a fixed behavior defined in a standard document, such as reference Figure 2 ). Both the first PUCCH 315 - a and the second PUCCH 315 - b may overlap in time (eg, at least partially) with the PUSCH repetition 310 .

[0132] In some examples, DCI 305 may trigger aperiodic CSI (e.g., or SP CSI) to be multiplexed on an FDM PUSCH (e.g., PUSCH repetition 310), and a CSI triggering state may be enabled (e.g., via RRC signaling) for behavior 1. There may also be a PUCCH (e.g., a first PUCCH 315-a) carrying HARQ-ACK, SR, or CSI that at least partially overlaps in time with the PUSCH, where the UCI of the first PUCCH 315-a may be configured with behavior 0.

[0133] In some examples, DCI 305 may trigger aperiodic CSI (e.g., or SP-CSI) to be multiplexed on an FDM PUSCH (e.g., PUSCH repetition 310), and the indicated CSI triggering state may not enable behavior 1 (e.g., in this case, PUSCH repetition 310 is configured with behavior 0). There may also be a PUCCH carrying HARQ-ACK, SR, or CSI that at least partially overlaps in time with the PUSCH (e.g., a first PUCCH 315-a), and the UCI of the first PUCCH 315-a may be configured with behavior 1.

[0134] In examples of conflicting UCI actions, such as reference Figure 3As described above, the UE may resolve the conflict by sending UCI configured for behavior 1 according to behavior 0, sending UCI configured for behavior 0 according to behavior 1, or treating the conflict as an error condition. For example, the UE may determine that a first set of one or more UCIs is configured to be multiplexed on both the first PUSCH repetition 310-a and the second PUSCH repetition 310-b according to behavior 1, but may determine that a second set of one or more UCIs is configured to be multiplexed with only one PUSCH repetition 310 according to behavior 0. In some examples, the UE may multiplex the first set of one or more UCIs on only one of the PUSCH repetitions 310 (e.g., may fall back to behavior 0 due to failure to meet the fifth condition). In such examples, the UE may send a first set of one or more UCIs and a second set of one or more UCIs according to behavior 0. The UE may send a first set of one or more UCIs via a first PUSCH repetition 310-a and a second set of one or more UCIs via a second PUSCH repetition 310-b, or may select one of the two PUSCH repetitions 310 and send both the first set and the second set of UCIs via the selected single PUSCH repetition 310. In some examples, the UE may multiplex both the first set of one or more UCIs and the second set of one or more UCIs via both the first PUSCH repetition 310-a and the second PUSCH repetition 310-b according to behavior 1. In some examples, the UE may not expect to identify such a conflict (e.g., the UE may interpret this situation as an error situation). In some examples, one or more standard documents may define such a conflict as an error situation, and the network may avoid scheduling UCI based on the error situation.

[0135] Figure 4 An example of a process flow 400 for supporting UCI multiplexing on an FDM channel in accordance with one or more aspects of the present disclosure is illustrated. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, and the timeline 300. For example, the process flow 400 may include the network entity 105-c and the UE 115-b, which may be referenced herein. Figures 1 to 3 Examples of corresponding devices described.

[0136] At 410, UE 115-b may receive control signaling (e.g., from network entity 105-c) that may include scheduling information. For example, the control signaling may schedule a first set of RBs associated with a first transmit beam (e.g., first set of RBs 210-a) and a second set of RBs associated with a second transmit beam (e.g., second set of RBs 210-b), where the first set of RBs and the second set of RBs occur during a first time interval.

[0137] At 415, UE 115-b may determine whether to send UCI via one of the first set of RBs or the second set of RBs (e.g., via a single set of RBs according to behavior 0) or via both the first set of RBs and the second set of RBs (e.g., via two sets of RBs according to behavior 1) based at least in part on the control signaling received at 410. At 420, UE 115-b may send UCI via at least one of the first set of RBs or the second set of RBs (e.g., according to behavior 0 or behavior 1) based at least in part on the determination at 415.

[0138] In some examples, at 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether one or more conditions are satisfied. At 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether a first number of RBs in a first set of RBs is equal to a second number of RBs in a second set of RBs (e.g., based on whether the first condition is satisfied). In some examples, at 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether a first number of PTRS ports associated with the first set of RBs is equal to a second number of PTRS ports associated with the second set of RBs (e.g., based on whether the second condition is satisfied). At 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether a first PTRS density associated with the first set of RBs is equal to a second PTRS density associated with the second set of RBs (e.g., based on whether a third condition is satisfied). In some examples, at 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether the first number of resource elements of the first set of RBs is equal to the second number of resource elements of the second set of RBs (e.g., based on whether the fourth condition is satisfied). In some examples, at 415, UE 115-b may determine whether to send UCI according to behavior 1 or behavior 0 based at least in part on whether one or more additional UCI messages are scheduled during the first set of RBs or the second set of RBs (e.g., based on whether the fifth condition is satisfied).

[0139] In some examples, at 405, UE 115-b may receive (e.g., from network entity 105-c) second control signaling (e.g., RRC signaling) that includes an indication of a first trigger state associated with sending UCI via one of the first set of RBs or the second set of RBs and a second trigger state associated with sending UCI via both the first set of RBs and the second set of RBs. In such examples, UE 115-b may receive an indication of the first trigger state or the second trigger state in the control signaling (e.g., a DCI message) at 410, and wherein the determination is based at least in part on the indication of the first trigger state or the second trigger state (e.g., enabling behavior 0 or behavior 1). In such examples, the trigger state may be associated with UCI including aperiodic CSI, SP-CSI associated with PUSCH, and the like.

[0140] In some examples, at 415, UE 115 may determine whether the type of UCI is associated with transmitting UCI via a first set of RBs (e.g., behavior 0) or associated with transmitting UCI via both the first set of RBs and the second set of RBs (e.g., behavior 1). In some such examples, UE 115-b may (e.g., at 405) receive control signaling (e.g., second control signaling) that schedules UCI on a PUCCH that overlaps in time with the first set of RBs and the second set of RBs. The type of UCI may be associated with the PUCCH. UE 115-b may also receive control signaling (e.g., third control signaling) that indicates that the first type of UCI is associated with transmitting UCI via one of the first set of RBs or the second set of RBs, and the second type of UCI is associated with transmitting UCI via both the first set of RBs and the second set of RBs, wherein the determination is based at least in part on whether the type of UCI is the first type or the second type. The type of UCI may be feedback information (HARQ-ACK), SR, SP-CSI associated with PUSCH, or periodic CSI.

[0141] In some examples, where UE 115-b determines to send UCI via one of a first set of RBs or a second set of RBs (e.g., configured with or defaulting to behavior 0), UE 115-b may select the first set of RBs based at least in part on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, a number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0142] In some examples, (e.g., at 405), UE 115-b may receive second control signaling via the control channel scheduling additional UCI, where the determination includes determining to send UCI via both the first set of RBs and the second set of RBs. In such examples, UE 115-b may send the UCI and the additional UCI via the first set of RBs or the second set of RBs, or may send the UCI via the first set of RBs and send the additional UCI via the second set of RBs, or may refrain from sending the additional UCI based at least in part on an error condition.

[0143] Figure 5 A block diagram 500 of a device 505 supporting UCI multiplexing on an FDM channel 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).

[0144] 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 related to UCI multiplexing on FDM channels, data channels, information channels). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0145] 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., a control channel related to UCI multiplexing on an FDM channel, a data channel, an information channel), 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.

[0146] 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 UCI multiplexing on FDM channels 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.

[0147] 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 to 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).

[0148] 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 (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0149] 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.

[0150] According to the examples disclosed herein, the communication manager 520 may support wireless communication at the UE. For example, the communication manager 520 may be configured to or otherwise support a component for receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The communication manager 520 may be configured to or otherwise support a component for determining, based on the control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The communication manager 520 may be configured to or otherwise support a component for sending UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0151] By including or configuring a communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof or otherwise coupled thereto) can support techniques for UCI signaling to more efficiently use available system resources, make control signaling more reliable, increase the reliability of communications, and improve the user experience.

[0152] Figure 6 A block diagram 600 of a device 605 supporting UCI multiplexing on an FDM channel 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).

[0153] 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 UCI multiplexing on FDM channels). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0154] 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., a control channel related to UCI multiplexing on an FDM channel, a data channel, an information channel), 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.

[0155] The device 605 or its various components may be examples of components for performing various aspects of UCI multiplexing on FDM channels as described herein. For example, the communication manager 620 may include a scheduling manager 625, a UCI multiplexing manager 630, a UCI transmission manager 635, 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, send). 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.

[0156] According to examples as disclosed herein, the communication manager 620 may support wireless communication at a UE. The scheduling manager 625 may be configured to or otherwise support components for receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The UCI multiplexing manager 630 may be configured to or otherwise support components for determining, based on the control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The UCI transmission manager 635 may be configured to or otherwise support components for sending UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0157] Figure 7 A block diagram 700 of a communication manager 720 supporting UCI multiplexing on an FDM channel 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 UCI multiplexing on an FDM channel as described herein. For example, the communication manager 720 may include a scheduling manager 725, a UCI multiplexing manager 730, a UCI transmission manager 735, a UCI condition manager 740, a control signaling manager 745, a UCI type manager 750, a UCI RB selection manager 755, a UCI conflict manager 760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0158] According to examples as disclosed herein, the communication manager 720 may support wireless communication at a UE. The scheduling manager 725 may be configured to or otherwise support a component for receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The UCI multiplexing manager 730 may be configured to or otherwise support a component for determining, based on the control signaling, whether to transmit UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The UCI transmission manager 735 may be configured to or otherwise support a component for transmitting UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0159] In some examples, to support sending UCI, UCI condition manager 740 may be configured or otherwise support components for sending UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based on the determination and whether one or more conditions are met.

[0160] In some examples, to support sending UCI, the UCI condition manager 740 may be configured to or otherwise support components for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of RBs in the first set of RBs is equal to a second number of RBs in the second set of RBs.

[0161] In some examples, to support sending UCI, the UCI condition manager 740 may be configured to or otherwise support components for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of PTRS ports associated with the first set of RBs is equal to a second number of PTRS ports associated with the second set of RBs.

[0162] In some examples, to support sending UCI, the UCI condition manager 740 may be configured to or otherwise support components for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first PTRS density associated with the first set of RBs is equal to a second PTRS density associated with the second set of RBs.

[0163] In some examples, to support sending UCI, the UCI condition manager 740 may be configured to or otherwise support components for sending UCI via a first set of RBs or via both the first set of RBs and the second set of RBs based on whether a first number of resource elements of the first set of RBs is equal to a second number of resource elements of the second set of RBs.

[0164] In some examples, to support sending UCI, the UCI condition manager 740 may be configured to or otherwise support components for sending UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based on whether one or more additional UCI messages are scheduled during the first set of RBs or the second set of RBs.

[0165] In some examples, the control signaling manager 745 may be configured to or otherwise support components for receiving second control signaling that includes an indication of a first trigger state associated with sending UCI via one of the first set of RBs or the second set of RBs and a second trigger state associated with sending UCI via both the first set of RBs and the second set of RBs.

[0166] In some examples, the control signaling manager 745 may be configured or otherwise support components for receiving an indication of a first trigger state or a second trigger state in control signaling, and wherein the determination is based on the indication of the first trigger state or the second trigger state.

[0167] In some examples, the UCI includes aperiodic channel state information or SP-CSI associated with an uplink shared channel.

[0168] In some examples, to support the determination, UCI type manager 750 may be configured or otherwise support components for determining whether the type of UCI is associated with transmitting the UCI via the first set of RBs or transmitting the UCI via both the first set of RBs and the second set of RBs.

[0169] In some examples, the UCI type manager 750 may be configured or otherwise support components for receiving second control signaling that schedules UCI on a PUCCH that temporally overlaps with a first set of RBs and a second set of RBs, wherein the type of the UCI is associated with the PUCCH.

[0170] In some examples, the UCI type manager 750 may be configured to or otherwise support components for receiving third control signaling indicating that the first type of UCI is associated with sending the UCI via one of the first set of RBs or the second set of RBs, and the second type of UCI is associated with sending the UCI via both the first set of RBs and the second set of RBs, wherein the determination is based on whether the type of the UCI is the first type or the second type.

[0171] In some examples, the type of UCI includes feedback information, scheduling request, SP-CSI associated with PUCCH, or periodic channel state information.

[0172] In some examples, to support the determination, the UCI RB selection manager 755 may be configured or otherwise support components for determining to send UCI via one of the first set of RBs or the second set of RBs. In some examples, to support the determination, the UCI RB selection manager 755 may be configured or otherwise support components for selecting one of the first set of RBs or the second set of RBs based on the determination, wherein the sending is based on the selection.

[0173] In some examples, to support selection, the UCI RB selection manager 755 may be configured to or otherwise support components for selecting a first set of RBs based on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, a number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0174] In some examples, the UCI conflict manager 760 may be configured or otherwise support components for receiving second control signaling scheduling additional UCI via the control channel, wherein the determining includes determining to transmit the UCI via both the first set of RBs and the second set of RBs.

[0175] In some examples, to support transmitting UCI, UCI conflict manager 760 may be configured or otherwise support components for transmitting UCI and additional UCI via the first set of RBs.

[0176] In some examples, to support sending UCI, UCI conflict manager 760 may be configured or otherwise support components for sending UCI via a first set of RBs. In some examples, to support sending UCI, UCI conflict manager 760 may be configured or otherwise support components for sending additional UCI via a second set of RBs.

[0177] In some examples, to support sending UCI, UCI conflict manager 760 may be configured or otherwise support components for sending UCI via both the first set of RBs and the second set of RBs. In some examples, to support sending UCI, UCI conflict manager 760 may be configured or otherwise support components for sending additional UCI via both the first set of RBs and the second set of RBs.

[0178] In some examples, UCI conflict manager 760 may be configured or otherwise support components for identifying an error condition based on receiving control signaling scheduling additional UCI. In some examples, UCI conflict manager 760 may be configured or otherwise support components for refraining from sending additional UCI based on the error condition.

[0179] Figure 8 A diagram of a system 800 including a device 805 supporting UCI multiplexing on an FDM channel 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).

[0180] 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.

[0181] 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.

[0182] 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, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0183] 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 UCI multiplexing on an FDM channel). 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.

[0184] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured to or otherwise support a component for receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The communication manager 820 may be configured to or otherwise support a component for determining, based on the control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The communication manager 820 may be configured to or otherwise support a component for sending UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0185] By including or configuring a communication manager 820 according to examples as described herein, the device 805 can support techniques for UCI signaling to more efficiently use available system resources, make control signaling more reliable, increase communication reliability, reduce system latency, and improve user experience.

[0186] 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 UCI multiplexing on FDM channels as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0187] Fig. 9 A block diagram 900 of a device 905 supporting UCI multiplexing on an FDM channel 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).

[0188] 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 communicated to other components of device 905. In some examples, receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, 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.

[0189] The transmitter 915 may provide a 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.

[0190] 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 UCI multiplexing on FDM channels 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.

[0191] 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).

[0192] 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 (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0193] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) 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 in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0194] 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 sending control signaling for scheduling a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. The communication manager 920 may be configured to or otherwise support components for determining, based on the control signaling, whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The communication manager 920 may be configured to or otherwise support components for receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0195] By including or configuring a communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or otherwise coupled thereto) may support techniques for UCI signaling to more efficiently use available system resources, make control signaling more reliable, increase reliability of communications, and improve user experience.

[0196] Fig.10A block diagram 1000 of a device 1005 supporting UCI multiplexing on an FDM channel 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).

[0197] 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 communicated 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.

[0198] The transmitter 1015 may provide a means for outputting (e.g., sending, 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.

[0199] The device 1005 or its various components may be examples of components for performing various aspects of UCI multiplexing on FDM channels as described herein. For example, the communication manager 1020 may include a scheduling manager 1025, a UCI resource manager 1030, a UCI reception manager 1035, 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 be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0200] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at a network entity. The scheduling manager 1025 may be configured to or otherwise support components for sending control signaling for scheduling a first set of RBs associated with a first transmit beam of the UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. The UCI resource manager 1030 may be configured to or otherwise support components for determining, based on the control signaling, whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The UCI reception manager 1035 may be configured to or otherwise support components for receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0201] Fig.11A block diagram 1100 of a communication manager 1120 supporting UCI multiplexing on FDM channels is shown in accordance with one or more aspects of the present disclosure. 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 UCI multiplexing on FDM channels as described herein. For example, the communication manager 1120 may include a scheduling manager 1125, a UCI resource manager 1130, a UCI reception manager 1135, a UCI condition manager 1140, a control signaling manager 1145, a UCI type manager 1150, a UCI conflict 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 the 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.

[0202] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The scheduling manager 1125 may be configured to or otherwise support components for sending control signaling for scheduling a first set of RBs associated with a first transmit beam of the UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. The UCI resource manager 1130 may be configured to or otherwise support components for determining, based on the control signaling, whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The UCI reception manager 1135 may be configured to or otherwise support components for receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0203] In some examples, to support receiving UCI, UCI condition manager 1140 may be configured or otherwise support components for sending UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based on the determination and whether one or more conditions are met.

[0204] In some examples, the control signaling manager 1145 may be configured to or otherwise support components for sending second control signaling that includes an indication of a first trigger state associated with receiving UCI via one of the first set of RBs or the second set of RBs and a second trigger state associated with receiving UCI via both the first set of RBs and the second set of RBs.

[0205] In some examples, to support the determination, UCI type manager 1150 may be configured or otherwise support components for determining whether the type of UCI is associated with receiving UCI via a first set of RBs or receiving UCI via both the first set of RBs and a second set of RBs.

[0206] In some examples, to support the determination, the UCI resource manager 1130 may be configured or otherwise support means for determining to receive the UCI via one of the first set of RBs or the second set of RBs. In some examples, to support the determination, the UCI resource manager 1130 may be configured or otherwise support means for selecting one of the first set of RBs or the second set of RBs based on the determination, wherein the receiving is based on the selection.

[0207] In some examples, to support selection, the UCI resource manager 1130 may be configured to or otherwise support components for selecting a first set of RBs based on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, a number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0208] In some examples, the UCI conflict manager 1155 may be configured or otherwise support components for sending second control signaling via the control channel scheduling additional UCI, wherein the determining includes determining to receive the UCI via both the first set of RBs and the second set of RBs.

[0209] Fig.12A diagram of a system 1200 including a device 1205 supporting UCI multiplexing on an FDM channel 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 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 receive 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).

[0210] 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 (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for: modulating a signal; providing a modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving a modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating a 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 transmitting operations or output 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 that are operable to perform the following operations: perform or support operations based on received or obtained information or signals; or 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).

[0211] 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 include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0212] 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., memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks that support UCI multiplexing on an FDM channel). 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, and the processor 1235 and the memory 1225 are 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 other systems or components (e.g., 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, the 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 a chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that device 1205 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0213] In some examples, bus 1240 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1205 or between different components of device 1205 that may be co-located or may be 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).

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

[0215] 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 sending control signaling for scheduling a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. The communication manager 1220 may be configured to or otherwise support components for determining, based on the control signaling, whether to receive UCI via one of the first set of RBs or the second set of RBs or via both the first set of RBs and the second set of RBs. The communication manager 1220 may be configured to or otherwise support components for receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination.

[0216] By including or configuring a communication manager 1220 according to the examples described herein, the device 1205 can support techniques for UCI signaling to more efficiently use available system resources, make control signaling more reliable, improve communication reliability, reduce system latency, and improve user experience.

[0217] 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 UCI multiplexing on FDM channels as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0218] Fig.13 1 is a flowchart illustrating a method 1300 for supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure. 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 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.

[0219] At 1305, the method may include receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The operations of 1305 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described schedule manager 725 is executed.

[0220] At 1310, the method may include determining, based on control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs. 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 7The described UCI multiplexing manager 730 is performed.

[0221] At 1315, the method may include sending the UCI via at least one of the first set of RBs or the second set of RBs based on the determination. 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 UCI transmission manager 735 is executed.

[0222] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure. 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.

[0223] At 1405, the method may include receiving control signaling for scheduling a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described schedule manager 725 is executed.

[0224] At 1410, the method may include determining, based on control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs. 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 described UCI multiplexing manager 730 is performed.

[0225] At 1415, the method may include sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based on the determination and whether one or more conditions are satisfied. 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 UCI condition manager 740 is executed.

[0226] Fig.151 is a flowchart illustrating a method 1500 for supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure. 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 The network entity described herein may be executed by the network entity described herein. 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.

[0227] At 1505, the method may include sending control signaling to schedule a first set of RBs associated with a first transmit beam of the UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. 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 schedule manager 1125 is executed.

[0228] At 1510, the method may include determining, based on the control signaling, whether to receive the UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs. 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 UCI resource manager 1130 is executed.

[0229] At 1515, the method may include receiving UCI via at least one of the first set of RBs or the second set of RBs based on the determination. 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 UCI reception manager 1135 is executed.

[0230] Fig.16 1 is a flowchart illustrating a method 1600 for supporting UCI multiplexing on an FDM channel according to one or more aspects of the present disclosure. 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 The network entity described herein may be executed by the network entity described herein. 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.

[0231] At 1605, the method may include sending control signaling to schedule a first set of RBs associated with a first transmit beam of the UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described schedule manager 1125 is executed.

[0232] At 1610, the method may include determining, based on the control signaling, whether to receive the UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs. 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.11 The described UCI resource manager 1130 is executed.

[0233] At 1615, the method may include receiving UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based on the determination and whether one or more conditions are satisfied. 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 UCI condition manager 1140 is executed.

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

[0235] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving control signaling that schedules a first set of RBs associated with a first transmit beam and a second set of RBs associated with a second transmit beam, wherein the first set of RBs and the second set of RBs occur during a first time interval; determining, at least in part based on the control signaling, whether to send UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs; and sending the UCI via at least one of the first set of RBs or the second set of RBs based at least in part on the determination.

[0236] Aspect 2: The method according to aspect 1, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on the determination and whether one or more conditions are met.

[0237] Aspect 3: A method according to Aspect 2, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on whether the first number of RBs in the first set of RBs is equal to the second number of RBs in the second set of RBs.

[0238] Aspect 4: A method according to any one of Aspects 2 to 3, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on whether the first number of PTRS ports associated with the first set of RBs is equal to the second number of PTRS ports associated with the second set of RBs.

[0239] Aspect 5: A method according to any one of Aspects 2 to 4, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on whether a first PTRS density associated with the first set of RBs is equal to a second PTRS density associated with the second set of RBs.

[0240] Aspect 6: A method according to any one of Aspects 2 to 5, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on whether the first number of resource elements of the first set of RBs is equal to the second number of resource elements of the second set of RBs.

[0241] Aspect 7: A method according to any one of Aspects 2 to 6, wherein sending the UCI includes: sending the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on whether one or more additional UCI messages are scheduled during the first set of RBs or the second set of RBs.

[0242] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: receiving second control signaling, the second control signaling including an indication of a first trigger state associated with sending the UCI via one of the first set of RBs or the second set of RBs, and a second trigger state associated with sending the UCI via both the first set of RBs and the second set of RBs.

[0243] Aspect 9: According to the method of Aspect 8, the method also includes: receiving an indication of the first trigger state or the second trigger state in the control signaling, and wherein the determination is at least partially based on the indication of the first trigger state or the second trigger state.

[0244] Aspect 10: The method according to any one of aspects 8 to 9, wherein the UCI comprises aperiodic channel state information or semi-persistent channel state information associated with an uplink shared channel.

[0245] Aspect 11: The method according to any one of aspects 1 to 10, wherein the determining comprises: determining whether the type of the UCI is associated with transmitting the UCI via the first set of RBs or transmitting the UCI via both the first set of RBs and the second set of RBs.

[0246] Aspect 12: According to the method according to Aspect 11, the method also includes: receiving a second control signaling, the second control signaling scheduling the UCI on a physical uplink control channel that temporally overlaps with the first set of RBs and the second set of RBs, wherein the type of the UCI is associated with the physical uplink control channel.

[0247] Aspect 13: According to the method described in any one of Aspects 11 to 12, the method further includes: receiving a third control signaling, the third control signaling indicating that the first type of UCI is associated with sending the UCI via one of the first set of RBs or the second set of RBs, and the second type of UCI is associated with sending the UCI via both the first set of RBs and the second set of RBs, wherein the determination is at least partially based on whether the type of the UCI is the first type or the second type.

[0248] Aspect 14: The method according to any one of Aspects 11 to 13, wherein the type of the UCI includes feedback information, a scheduling request, semi-persistent channel state information associated with a physical uplink control channel, or periodic channel state information.

[0249] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the determination includes: determining that the UCI is to be sent via one of the first set of RBs or the second set of RBs; and selecting one of the first set of RBs or the second set of RBs based at least in part on the determination, wherein the sending is based at least in part on the selection.

[0250] Aspect 16: A method according to Aspect 15, wherein the selection includes: selecting the first set of RBs based at least in part on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, the number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0251] Aspect 17: According to any one of aspects 1 to 16, the method further includes: receiving second control signaling scheduling additional UCI via a control channel, wherein the determination includes determining to send the UCI via both the first set of RBs and the second set of RBs.

[0252] Aspect 18: The method according to aspect 17, wherein sending the UCI comprises: sending the UCI and the additional UCI via the first set of RBs.

[0253] Aspect 19: The method according to any one of aspects 17 to 18, wherein sending the UCI comprises: sending the UCI via the first set of RBs; and sending the additional UCI via the second set of RBs.

[0254] Aspect 20: The method according to any one of aspects 17 to 19, wherein sending the UCI comprises: sending the UCI via both the first set of RBs and the second set of RBs; and sending the additional UCI via both the first set of RBs and the second set of RBs.

[0255] Aspect 21: The method according to any one of aspects 17 to 20, further comprising: identifying an error condition based at least in part on receiving the control signaling scheduling the additional UCI; and refraining from sending the additional UCI based at least in part on the error condition.

[0256] Aspect 22: A method for performing wireless communications at a network entity, the method comprising: sending control signaling that schedules a first set of RBs associated with a first transmit beam of a UE and a second set of RBs associated with a second transmit beam of the UE, wherein the first set of RBs and the second set of RBs occur during a first time interval; determining, at least in part based on the control signaling, whether to receive UCI via one of the first set of RBs or the second set of RBs, or via both the first set of RBs and the second set of RBs; and receiving the UCI via at least one of the first set of RBs or the second set of RBs based at least in part on the determination.

[0257] Aspect 23: The method according to aspect 22, wherein receiving the UCI includes: receiving the UCI via the first set of RBs or via both the first set of RBs and the second set of RBs based at least in part on the determination and whether one or more conditions are met.

[0258] Aspect 24: According to the method described in any one of Aspects 22 to 23, the method also includes: sending a second control signaling, the second control signaling including an indication of a first trigger state associated with receiving the UCI via one of the first set of RBs or the second set of RBs, and a second trigger state associated with receiving the UCI via both the first set of RBs and the second set of RBs.

[0259] Aspect 25: The method according to any one of aspects 22 to 24, wherein the determining comprises determining whether the type of the UCI is associated with receiving the UCI via the first set of RBs or receiving the UCI via both the first set of RBs and the second set of RBs.

[0260] Aspect 26: A method according to any one of Aspects 22 to 25, wherein the determination includes: determining that the UCI is received via one of the first set of RBs or the second set of RBs; and selecting one of the first set of RBs or the second set of RBs based at least in part on the determination, wherein the reception is based at least in part on the selection.

[0261] Aspect 27: A method according to Aspect 26, wherein the selection includes: selecting the first set of RBs based at least in part on a first sounding reference signal resource set associated with the first set of RBs, a frequency range associated with the first set of RBs, a repeated redundant version associated with the first set of RBs, the number of RBs or resource elements associated with the first set of RBs, one or more additional UCI messages scheduled for the first set of RBs and the second set of RBs, or any combination thereof.

[0262] Aspect 28: The method according to any one of aspects 22 to 27, the method further comprising: sending second control signaling scheduling additional UCI via a control channel, wherein the determining comprises determining to receive the UCI via both the first set of RBs and the second set of RBs.

[0263] Aspect 29: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 21.

[0264] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing a method according to any one of aspects 1 to 21.

[0265] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 21.

[0266] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 22 to 28.

[0267] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 22 to 28.

[0268] Aspect 34: 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 22 to 28.

[0269] 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.

[0270] 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 described techniques 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.

[0271] 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.

[0272] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an 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).

[0273] 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 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 various parts of the functions are implemented at different physical locations.

[0274] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates 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 any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, 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, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic 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 discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0275] 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."

[0276] 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.

[0277] 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 reference label or other subsequent reference labels.

[0278] 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 "advantageous over other examples." The specific implementation includes 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.

[0279] 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling to schedule a first set of resource blocks associated with a first transmit beam and a second set of resource blocks associated with a second transmit beam, wherein the first set of resource blocks and the second set of resource blocks occur during a first time interval; determining, based at least in part on the control signaling, whether to send uplink control information via one of the first set of resource blocks or the second set of resource blocks, or via both the first set of resource blocks and the second set of resource blocks; as well as The uplink control information is sent via at least one of the first set of resource blocks or the second set of resource blocks based at least in part on the determination.

2. The apparatus of claim 1 , wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on the determination and whether one or more conditions are satisfied.

3. The apparatus of claim 2, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on whether a first number of resource blocks in the first set of resource blocks is equal to a second number of resource blocks in the second set of resource blocks.

4. The apparatus of claim 2, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on whether a first number of PTRS ports associated with the first set of resource blocks is equal to a second number of PTRS ports associated with the second set of resource blocks.

5. The apparatus of claim 2, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on whether a first PTRS density associated with the first set of resource blocks is equal to a second PTRS density associated with the second set of resource blocks.

6. The apparatus of claim 2, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on whether a first number of resource elements of the first set of resource blocks is equal to a second number of resource elements of the second set of resource blocks.

7. The apparatus of claim 2, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is sent via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on whether one or more additional uplink control information messages are scheduled during the first set of resource blocks or the second set of resource blocks.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Receive second control signaling, the second control signaling including an indication of a first trigger state associated with sending the uplink control information via one of the first set of resource blocks or the second set of resource blocks, and a second trigger state associated with sending the uplink control information via both the first set of resource blocks and the second set of resource blocks.

9. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the first trigger state or the second trigger state is received in the control signaling, and wherein the determining is based at least in part on the indication of the first trigger state or the second trigger state.

10. The apparatus of claim 8, wherein the uplink control information comprises aperiodic channel state information or semi-persistent channel state information associated with an uplink shared channel.

11. The apparatus of claim 1 , wherein the instructions for determining are executable by the processor to cause the apparatus to: Determining whether the type of the uplink control information is associated with sending the uplink control information via the first set of resource blocks or sending the uplink control information via both the first set of resource blocks and the second set of resource blocks.

12. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is received, which schedules the uplink control information on a physical uplink control channel that overlaps in time with the first set of resource blocks and the second set of resource blocks, wherein the type of the uplink control information is associated with the physical uplink control channel.

13. The apparatus of claim 11, wherein the instructions are further executable by the processor to cause the apparatus to: receiving third control signaling indicating that first type of uplink control information is associated with sending the uplink control information via one of the first set of resource blocks or the second set of resource blocks, and second type of uplink control information is associated with sending the uplink control information via both the first set of resource blocks and the second set of resource blocks, wherein the determination is based at least in part on whether the type of the uplink control information is the first type or the second type.

14. The apparatus of claim 11, wherein the type of the uplink control information comprises: Feedback information, scheduling request, semi-persistent channel state information associated with a physical uplink control channel, or periodic channel state information.

15. The apparatus of claim 1, wherein the instructions for determining are executable by the processor to cause the apparatus to: determining to send the uplink control information via one of the first set of resource blocks or the second set of resource blocks; and One of the first set of resource blocks or the second set of resource blocks is selected based at least in part on the determining, wherein the sending is based at least in part on the selecting.

16. The apparatus of claim 15, wherein the instructions for selecting are executable by the processor to cause the apparatus to: The first set of resource blocks is selected based at least in part on a first sounding reference signal resource set associated with the first set of resource blocks, a frequency range associated with the first set of resource blocks, a repeated redundant version associated with the first set of resource blocks, a number of resource blocks or resource elements associated with the first set of resource blocks, one or more additional uplink control information messages scheduled for the first set of resource blocks and the second set of resource blocks, or any combination thereof.

17. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling scheduling additional uplink control information is received via a control channel, wherein the determining includes determining to send the uplink control information via both the first set of resource blocks and the second set of resource blocks.

18. The apparatus of claim 17, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: The uplink control information and the additional uplink control information are sent via the first set of resource blocks.

19. The apparatus of claim 17, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: sending the uplink control information via the first set of resource blocks; and The additional uplink control information is sent via the second set of resource blocks.

20. The apparatus of claim 17, wherein the instructions for sending the uplink control information are executable by the processor to cause the apparatus to: transmitting the uplink control information via both the first set of resource blocks and the second set of resource blocks; and The additional uplink control information is sent via both the first set of resource blocks and the second set of resource blocks.

21. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: identifying an error condition based at least in part on receiving the control signaling scheduling the additional uplink control information; and Refraining from sending the additional uplink control information based at least in part on the error condition.

22. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting control signaling to schedule a first set of resource blocks associated with a first transmit beam of a user equipment (UE) and a second set of resource blocks associated with a second transmit beam of the UE, wherein the first set of resource blocks and the second set of resource blocks occur during a first time interval; determining, based at least in part on the control signaling, whether to receive uplink control information via one of the first set of resource blocks or the second set of resource blocks, or via both the first set of resource blocks and the second set of resource blocks; as well as The uplink control information is received via at least one of the first set of resource blocks or the second set of resource blocks based at least in part on the determination.

23. The apparatus of claim 22, wherein the instructions for receiving the uplink control information are executable by the processor to cause the apparatus to: The uplink control information is received via the first set of resource blocks or via both the first set of resource blocks and the second set of resource blocks based at least in part on the determination and whether one or more conditions are satisfied.

24. The apparatus of claim 22, wherein the instructions are further executable by the processor to cause the apparatus to: Sending second control signaling, the second control signaling including an indication of a first trigger state associated with receiving the uplink control information via one of the first set of resource blocks or the second set of resource blocks, and a second trigger state associated with receiving the uplink control information via both the first set of resource blocks and the second set of resource blocks.

25. The apparatus of claim 22, wherein the instructions for determining are executable by the processor to cause the apparatus to: Determining whether the type of the uplink control information is associated with receiving the uplink control information via the first set of resource blocks or receiving the uplink control information via both the first set of resource blocks and the second set of resource blocks.

26. The apparatus of claim 22, wherein the instructions for determining are executable by the processor to cause the apparatus to: determining to receive the uplink control information via one of the first set of resource blocks or the second set of resource blocks; and One of the first set of resource blocks or the second set of resource blocks is selected based at least in part on the determining, wherein the receiving is based at least in part on the selecting.

27. The apparatus of claim 26, wherein the instructions for selecting are executable by the processor to cause the apparatus to: The first set of resource blocks is selected based at least in part on a first sounding reference signal resource set associated with the first set of resource blocks, a frequency range associated with the first set of resource blocks, a repeated redundant version associated with the first set of resource blocks, a number of resource blocks or resource elements associated with the first set of resource blocks, one or more additional uplink control information messages scheduled for the first set of resource blocks and the second set of resource blocks, or any combination thereof.

28. The apparatus of claim 22, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling for scheduling additional uplink control information is sent via the first set of resource blocks or the second set of resource blocks, or via both the first set of resource blocks and the second set of resource blocks, wherein the determination includes determining to receive the uplink control information via both the first set of resource blocks and the second set of resource blocks.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling to schedule a first set of resource blocks associated with a first transmit beam and a second set of resource blocks associated with a second transmit beam, wherein the first set of resource blocks and the second set of resource blocks occur during a first time interval; determining, based at least in part on the control signaling, whether to send uplink control information via one of the first set of resource blocks or the second set of resource blocks, or via both the first set of resource blocks and the second set of resource blocks; as well as The uplink control information is sent via at least one of the first set of resource blocks or the second set of resource blocks based at least in part on the determination.

30. A method for wireless communication at a network entity, the method comprising: transmitting control signaling to schedule a first set of resource blocks associated with a first transmit beam of a user equipment (UE) and a second set of resource blocks associated with a second transmit beam of the UE, wherein the first set of resource blocks and the second set of resource blocks occur during a first time interval; determining, based at least in part on the control signaling, whether to receive uplink control information via one of the first set of resource blocks or the second set of resource blocks, or via both the first set of resource blocks and the second set of resource blocks; as well as The uplink control information is received via at least one of the first set of resource blocks or the second set of resource blocks based at least in part on the determination.

Images