Uplink multiplexing for multiple transmit-receive point operations

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive scheduling information for an uplink shared channel transmission, the scheduling information indicating a plurality of transmission configuration indicator (TCI) states. The UE may transmit a first portion of the uplink shared channel multiplexed with uplink control information (UCI) using a first set of resources and according to a first TCI state. Similarly, the UE may transmit a second portion of the uplink shared channel multiplexed with UCI using a second set of resources and according to a second TCI state. The first set of resources and the second set of resources may overlap in time, but not in frequency. A network entity may receive and decode the first portion and the second portion of the uplink shared channel.

Description

Technical Field

[0001] The following relates to wireless communications, including uplink multiplexing for multiple transmit receive point (multi-TRP) operations. 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 communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting uplink multiplexing for multiple transmit receive point (multi-TRP) operations. For example, the described technology enables a user equipment (UE) to transmit portions of an uplink shared channel (e.g., a physical uplink shared channel (PUSCH)) multiplexed with uplink control information (UCI) using multiple transmit configuration indicator (TCI) states. For example, the UE may receive scheduling information indicating multiple TCI states for an uplink shared channel from a network entity. The UE may perform frequency division multiplexing (FDM) operations to transmit different portions of an uplink shared channel concurrently and to different TRPs in a multi-TRP system using different beams (e.g., corresponding TCI states). The UE may multiplex different portions of an uplink shared channel with UCIs, such as the same UCI for different portions or different UCIs for each portion of an uplink shared channel (e.g., different UCI payloads or decoding bits).

[0004] A method for wireless communication at a UE is described. The method may include: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel; sending a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the plurality of TCI states; and sending a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states.

[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 executable by the processor to cause the apparatus to: receive a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel; send a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the multiple TCI states; and send a second portion of the uplink shared channel multiplexed with a second UCI according to a second TCI state in the multiple TCI states and via a second resource set that at least partially overlaps with the first resource set in time.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel; a component for sending a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the plurality of TCI states; and a component for sending a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel; sending a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the multiple TCI states; and sending a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in the multiple TCI states.

[0008] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a second UCI based on the first UCI, where the second UCI may be a copy of the first UCI.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for encoding a first UCI according to a set of encoding parameters associated with a first TCI state, wherein a second UCI may be generated based on the encoded first UCI.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing rate matching for a first UCI according to a rate matching scheme associated with a first TCI state, wherein a second UCI may be generated based on the rate matched first UCI.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for encoding a first UCI according to a first coding scheme; performing rate matching of the first UCI according to a first rate matching scheme after encoding the first UCI; and multiplexing the first UCI with a first portion of an uplink shared channel after performing rate matching of the first UCI.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for encoding a second UCI according to a second coding scheme; performing rate matching of the second UCI according to a second rate matching scheme after encoding the second UCI; and multiplexing the second UCI with a second portion of the uplink shared channel after performing rate matching of the second UCI.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first encoding scheme may be different from the second encoding scheme.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first rate matching scheme may be different from the second rate matching scheme.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a coding and rate matching process of a first set of UCI based on a first coding and rate matching scheme associated with a first TCI state to obtain a first UCI.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing a coding and rate matching process for a first set of UCI may include operations, features, components, or instructions for: determining a number of decoded symbols for each layer of the first set of UCI; omitting one or more bits of the first set of UCI; and determining one or more sequence lengths for different information subsets for the first set of UCI after omitting the one or more bits.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a coding and rate matching process of a second set of UCI based on a coding and rate matching scheme to obtain a second UCI.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing a coding and rate matching process for a second set of UCI may include operations, features, components, or instructions for: determining a number of decoded symbols for each layer of the second set of UCI; omitting one or more bits of the second set of UCI; and determining one or more sequence lengths for different information subsets for the second set of UCI after omitting the one or more bits.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a first portion of an uplink shared channel based on a first redundancy version (RV); and generating a second portion of the uplink shared channel based on a second RV different from the first RV.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating a first portion and a second portion of an uplink shared channel based on a same RV.

[0021] 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 message that configures the UE to operate in FDM mode for uplink shared channel transmission.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for splitting an uplink shared channel into a first portion based on an upper limit function and a number of resource blocks associated with the uplink shared channel; and splitting the uplink shared channel into a second portion based on a lower limit function and a number of resource blocks associated with the uplink shared channel.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first set of resources and the second set of resources may not overlap in frequency.

[0024] A method for wireless communication at a network entity is described. The method may include: sending a control message indicating scheduling information of an uplink shared channel for a UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel; receiving a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the plurality of TCI states; and receiving a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states.

[0025] 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 executable by the processor to cause the apparatus to: send a control message indicating scheduling information for an uplink shared channel for a UE, the scheduling information indicating multiple TCI states for the uplink shared channel; receive a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the multiple TCI states; and receive a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in the multiple TCI states.

[0026] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a control message indicating scheduling information of an uplink shared channel for a UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel; means for receiving a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the plurality of TCI states; and means for receiving a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states.

[0027] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: sending a control message indicating scheduling information of an uplink shared channel for a UE, the scheduling information indicating multiple TCI states for the uplink shared channel; receiving a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in the multiple TCI states; and receiving a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in the multiple TCI states.

[0028] 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 message that configures the UE to operate in FDM mode for uplink shared channel transmission.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: performing a decoding and rate matching process of a first UCI based on a first coding and rate matching scheme associated with a first TCI state; and performing a decoding and rate matching process of a second UCI based on the first coding and rate matching scheme associated with the first TCI state.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first UCI and the second UCI may be the same.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a first decoding and rate matching process for a first UCI based on a first encoding and rate matching scheme associated with a first TCI state.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing a second decoding and rate matching process for a second UCI based on a second encoding and rate matching scheme associated with a second TCI state.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first UCI and the second UCI may be different.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first set of resources and the second set of resources may not overlap in frequency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 and Figure 2 An example of a wireless communication system supporting uplink multiplexing for multiple transmit receive point (multi-TRP) operations according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 3A and Figure 3B An example of a resource map supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 4 An example of a process flow for supporting uplink multiplexing for multi-TRP operation in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 5 and Figure 6 A block diagram of a device supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0039] Figure 7 A block diagram of a communication manager supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0040] Figure 8 A diagram of a system including devices supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0041] Fig. 9 and Fig.10 A block diagram of a device supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0042] Fig.11 A block diagram of a communication manager supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0043] Fig.12 A diagram of a system including devices supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown.

[0044] Figures 13 to 16 A flow chart is shown that illustrates a method for supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0045] In some wireless communication systems, a user equipment (UE) may communicate with a network entity via one or more transmit receive points (TRPs) (such as in a multi-TRP system). The TRP may relay information to and from one or more UEs and one or more network entities, such as uplink and downlink signaling. For example, a network entity may configure communications with a UE in a multi-TRP system according to a frequency division multiplexing (FDM) scheme, so that the UE may use different beams (e.g., time-frequency resources in the spatial direction) in different frequency resources within a given time interval to send or receive data from the TRP. Each beam may have a corresponding transmit configuration indicator (TCI) state, which may define a quasi-co-location (QCL) relationship between antenna ports of a source wireless device and a target or destination wireless device (e.g., a UE and a TRP). In some cases, the UE may multiplex uplink control information (UCI) with an uplink shared channel for transmission to a network entity. However, some multiplexing techniques may not support multiplexing of UCI using different beams (e.g., in a multi-TRP system for FDM), and therefore the UE may not be able to perform such multiplexing.

[0046] As described herein, the UE may multiplex UCI on a split uplink shared channel by generating UCI bits for each portion of the uplink shared channel. For example, the UE may multiplex the UCI with a portion of the uplink shared channel and may multiplex a copy of the UCI for an additional portion of the uplink shared channel. In some other examples, the UE may perform different coding and rate matching to multiplex different UCIs in different portions of the uplink shared channel. The network entity may configure the TCI state (e.g., beam) of each portion of the uplink shared channel via control signaling such as radio resource control (RRC) signaling. The UE may transmit each portion of the uplink shared channel using a beam corresponding to the TCI state of each portion of the uplink shared channel. The UE may transmit portions of the uplink shared channel according to an FDM scheme in which the time resources for transmission may overlap (at least partially) and the frequency resources are independent (e.g., non-overlapping) for each portion of the uplink shared channel.

[0047] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further described in the context of resource diagrams and process flows. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to uplink multiplexing for multi-TRP operation.

[0048] Figure 1An example of a wireless communication system 100 supporting uplink multiplexing for multi-TRP operation 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).

[0049] 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, etc. 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), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0050] 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. Figure 1 As shown, the UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 or network entities 105 .

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

[0052] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul 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 on the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 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), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

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

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

[0055] The functional split between CU 160, DU 165, and RU 170 is flexible and may 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, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., 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 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0056] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include 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 a case, 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.

[0057] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), 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 signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part 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 part of a backhaul link).

[0058] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. 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 the child IAB node 104 or the UE 115.

[0059] For example, the IAB node 104 may be referred to as a parent node that supports child IAB node communications and as a child IAB node associated with an IAB donor. 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 transmission to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmission. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling on 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 .

[0060] 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 uplink multiplexing for multi-TRP operation 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).

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

[0062] 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 1shown.

[0063] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources with a defined physical layer structure to support communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., 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-APro, 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 communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers 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 "sending", "receiving" or "communicating" 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).

[0064] 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 located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0065] 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, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0066] 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 of 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). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on 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 communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0067] The signal waveform sent on the carrier may be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal FDM (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, where the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. 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 UE115.

[0068] One or more parameter sets for a carrier may be supported, where the parameter set 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 the UE 115 may be restricted to the one or more active BWPs.

[0069] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. 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).

[0070] 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 added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0072] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using 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 group of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region to obtain 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 number 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 .

[0073] 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., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) 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 the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

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

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

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

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

[0078] 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 capture information and relay such information to a central server or application that utilizes 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, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0079] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way 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 power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating over a 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.

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

[0081] In some examples, UEs 115 may be able to communicate directly with other UEs 115 over 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 communications 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 communications configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, multiple groups of UEs 115 communicating via D2D communications 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, the network entity 105 may facilitate scheduling resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0082] 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) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. 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) using vehicle-to-network (V2N) communications, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU170), or both.

[0083] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW) or a user plane function (UPF)) for routing packets or interconnecting to an external network. 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 delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

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

[0085] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). 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, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater atmospheric 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.

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

[0087] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can 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, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of 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 have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

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

[0089] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals 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).

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

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

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

[0093] A receiving device (e.g., UE 115) may perform 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 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 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).

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

[0095] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using 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 simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0096] In some examples, one or more UCI multiplexing rules may be defined at or supported by UE 115 such that UE 115 may carry (e.g., multiplex) UCI ​​on an uplink shared channel, such as a physical uplink shared channel (PUSCH). In single TRP operation, the UCI multiplexing rules may define multiplexing of UCI bits with PUSCH bits. In multi-TRP operation (e.g., with multiple TCI states), UE 115 may perform UCI multiplexing in time division multiplexing (TDM) mode. In TDM mode, UE 115 may multiplex UCI using a single TCI state, and transmit the multiplexed UCI on a time resource for one PUSCH that may not overlap with a time resource of a different PUSCH associated with a different TCI state. However, the rules may not be defined, and therefore UE 115 may not support UCI multiplexing for a multi-TRP operation mode of FDM mode, where multiple TCI states may be sent on the same duration (or at least partially overlap in time).

[0097] In some examples, the network entity 105 may define one or more rules for the UE 115 to multiplex UCI on the PUSCH for a multi-TRP scenario (e.g., when the UE 115 is scheduled with a single PUSCH for multiple TCI states). The network entity 105 may schedule a single PUSCH with multiple TCI states, and the UE 115 may split the single PUSCH into multiple parts, which the UE 115 may send simultaneously using different TCI states. In some cases, the UE 115 may encode and rate match the UCI according to one TCI state for each part of the PUSCH, and then the UE 115 may copy and multiplex the coded and rate matched UCI bits with one or more different parts of the PUSCH. The parts of the PUSCH may have the same or different redundancy versions (RVs). The UE 115 may send the UCI multiplexed with the PUSCH in an FDM manner so that the UE 115 may send the TCI states simultaneously. In some other cases, the UE 115 may encode and rate match the UCI separately for each TCI state. For example, the UE 115 may encode and rate match a first UCI according to a first TCI state, and multiplex the encoded and rate matched first UCI with a first portion of the PUSCH for transmission. Additionally or alternatively, the UE 115 may encode and rate match a second UCI according to a second TCI state (e.g., using a different rate matching and coding scheme than the first UCI), and then multiplex the encoded and rate matched second UCI with a second portion of the PUSCH for transmission. The first UCI and the second UCI may have the same UCI payload.

[0098] Figure 2 An example of a wireless communication system 200 that supports uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented or may be implemented to implement aspects of the wireless communication system 100. For example, the wireless communication system 200 illustrates communications between one or more UEs and network entities, such as UE 115-a, TRP 205-a, TRP 205-b, and network entity 105-a, which may be described herein (including references). Figure 1 ) Examples of corresponding devices described in the accompanying drawings. The wireless communication system 200 may support signaling including multiplexing sent from the UE 115-a to the network entity 105-a via TRP 205-a, TRP 205-b, or both in FDM mode.

[0099] In some cases, UE 115-a, TRP 205-a, TRP 205-b, or any combination thereof may communicate with network entity 105-a. For example, network entity 105-a may send control information, data, or both to UE 115-a via a group of one or more TRPs (e.g., TRP 205-a, TRP 205-b, or both in multi-TRP system 210) using a communication link 125-a between TRP 205-a, TRP 205-b, or both and network entity 105-a and a downlink communication link 215 between TRP 205-a, TRP 205-b, or both and UE 115-a. Similarly, UE 115-a may send control information, data, or both to network entity 105-a via TRP 205-a, TRP 205-b, or both using communication link 125-a and uplink communication link 220 between TRP 205-a, TRP 205-b, or both. Communication link 215-a may be as described in reference Figure 1 An example of a communication link 125 is described.

[0100] In some examples, the multi-TRP system 210 may include any number of TRPs, such as TRP 205-a and TRP 205-b. Each TRP in the multi-TRP system 210 may relay information between the network entity 105-a and one or more UEs (e.g., including UE 115-a). Additionally or alternatively, one or more TRPs in the TRP system 210 may have the functionality of a network entity such as network entity 105-a, and may communicate with the UE independently of the network entity 105-a. In some cases, the multi-TRP system 210 may include a vehicle in a V2X system, one or more customer premises equipment (CPE), a fixed wireless access (FWA) system, one or more industrial devices in an IoT system, or any combination thereof.

[0101] In some cases, UE 115-a may use multiple TCI states to communicate with the TRPs in the multi-TRP system 210. Each TCI state may identify a beam with a corresponding communication direction and resource. For example, the network entity 105-a may instruct the UE 115-a to operate in the FDM mode. The UE 115-a may use different beams and frequency resources to perform multiple transmissions concurrently. The TCI state may include one or more downlink TCI states for communication from the network entity 105-a to the UE 115-a. Additionally or alternatively, the TCI state may include one or more uplink TCI states for communication from the UE 115-a to the network entity 105-a. In some cases, the UE 115-a may perform simultaneous multi-panel uplink transmissions to increase the reliability of the uplink throughput and signaling. The UE 115-a may use one or more frequencies in a frequency range (e.g., a frequency range 2 including a frequency band from 24.25 GHz to 52.6 GHz) to perform simultaneous transmissions in the FDM mode.

[0102] In some examples, UE 115-a and network entity 105-a may implement pre-decoding techniques, wherein the transmitting device may transmit the decoded information to the receiving device so that the receiving device may determine information about the communication channel. Therefore, the transmitting device and the receiving device may communicate on the communication channel using a common codebook. For example, UE 115-a may send an uplink pre-decoding indication for uplink shared channel transmission, where there may not be different codebooks for simultaneous transmission of multiple panels under the FDM scheme. In some cases, the total number of signaling layers on all transmission panels at UE 115-a may be up to four, and the total number of codewords on the panel may be up to two. UE 115-a and network entity 105-a may configure multi-TRP operation using a single downlink control information (DCI) message or multiple DCI messages. In some examples, UE 115-a may send an uplink beam indication for an uplink control channel, an uplink shared channel, or both (e.g., a physical uplink control channel (PUCCH) and a PUSCH). For multi-TRP operation based on multiple DCI messages, UE 115-a can send two PUSCHs or two PUCCHs across two panels in the same component carrier (CC).

[0103] In some examples, the network entity 105-a may define one or more rules or procedures for the UE 115-a to support multiplexing of UCI with an uplink shared channel for communication in the multi-TRP system 210. The network entity 105-a may send the scheduling information 225 to the UE 115-a in control signaling, such as a DCI message, RRC signaling, a medium access control-control element (MAC-CE), etc. In some cases, the network entity 105-a may send the scheduling information 225 via one or more TRPs in the multi-TRP system 210 (such as via TRP 205-a, TRP 205-b, or both) using the communication link 125-a and the downlink communication link 215. In some other cases, the network entity 105-a may send the scheduling information 225 directly to the UE 115-a.

[0104] Scheduling information 225 may schedule uplink shared channel transmissions, including one or more portions of an uplink shared channel (e.g., uplink shared channel portion 230-a, uplink shared channel portion 230-b, or both). For example, scheduling information 225 may indicate one or more time-frequency resources for UE 115-a to use for uplink shared channel transmissions. Additionally or alternatively, scheduling information 225 may include one or more TCI states for UE 115-a to use for uplink shared channel transmissions. Network entity 105-a may instruct UE 115-a to use one TCI state per TRP in a multi-TRP system. That is, the scheduling information 225 may indicate a TCI state 235-a for UE 115-a to be used when sending the uplink shared channel portion 230-a to UE 115-a via TRP 205-a, and a TCI state 235-b for UE 115-a to be used when sending the uplink shared channel portion 230-b to UE 115-a via TRP 205-b.

[0105] In some examples, scheduling information 225 may define one or more splitting rules for the time-frequency resource allocation of each portion for uplink shared channel transmission. For example, UE 115-a may apply a first upper limit ceil (N PRB / 2), which has a number of physical resource blocks (PRBs) split into a first frequency domain resource allocation (FDRA) for the uplink shared channel (e.g., to determine the PRBs for the uplink shared channel portion 230-a for TRP 205-a and TCI state 235-a), where N PRB is the total number of PRBs allocated to UE 115-a in the FDRA. Similarly, UE 115-a may apply a remaining lower limit floor(N PRB / 2) to determine the number of PRBs for the second FDRA split of the uplink shared channel (e.g., to determine the PRBs for the uplink shared channel portion 230-b for TRP205-b and TCI state 235-b).

[0106] The network entity 105-a may instruct the UE 115-a to operate in the FDM transmission mode. In some cases, the network entity 105-a may include an explicit indication in the control signaling including the scheduling information 225. In some other cases, the UE 115-a may infer from the scheduling information 225 that the UE 115-a will operate in the FDM transmission mode. For example, if the scheduling information 225 includes one or more overlapping time resources for the uplink shared channel portion 230-a and the uplink shared channel portion 230-b, and different frequency resources for the uplink shared channel portion 230-a and the uplink shared channel portion 230-b, the UE 115-a may perform uplink shared channel transmission in the FDM transmission mode.

[0107] In some cases, UE 115-a may be configured to piggyback or multiplex UCI on a scheduled uplink shared channel transmission, such that UE 115-a may transmit an uplink shared channel 240 with a UCI message. UE 115-a may receive higher layer signaling indicating that the UE multiplexes UCI on an uplink shared channel transmission. Additionally or alternatively, the multiplexing of the uplink shared channel with UCI may be defined in other ways (e.g., predetermined or predefined at UE 115-a). In some examples, scheduling information 225 may use one or more FDRA indicators to split the uplink shared channel for transmission in different frequency resources. For example, FDRA may split the uplink shared channel message into portions for each TRP in a multi-TRP system 210 (e.g., an uplink shared channel portion 230-a for TRP 205-a and an uplink shared channel portion 230-b for TRP 205-b). UE 115 - a may include the same UCI payload in different portions of the split uplink shared channel.

[0108] In some cases, at 245, UE 115-a may multiplex portions of an uplink shared channel with UCI. For example, UE 115-a may perform UCI encoding and rate matching based on a single TRP 205-a or TRP 205-b. That is, UE 115-a may determine a lower FDRA (e.g., for a lower frequency range) for the split uplink shared channel, such as the FDRA for uplink shared channel portion 230-b. UE 115-a may encode and rate match UCI with uplink shared channel portion 230-b based on the uplink shared channel portion 230-b having the lower FDRA. UE 115-a may copy and repeat the same UCI coding bits for other portions of the uplink shared channel message to different TRPs, such as uplink shared channel portion 230-a to TRP 205-a having a higher FDRA. If the uplink shared channel includes multiple RVs in different parts of the uplink shared channel, the UE 115- may copy and repeat the same UCI decoding bits. For example, if the uplink shared channel portion 230-b includes a first RV of an uplink shared channel message and the uplink shared channel portion 230-a includes a subsequent (e.g., second) RV of the uplink shared channel message, the UE 115- may copy and repeat the UCI on the uplink shared channel portion 230-a and the uplink shared channel portion 230-b. Additionally or alternatively, if the uplink shared channel portion 230-b includes an RV of an uplink shared channel message and the uplink shared channel portion 230-a includes the same RV of the uplink shared channel message, the UE 115- may copy and repeat the UCI on the uplink shared channel portion 230-a and the uplink shared channel portion 230-b.

[0109] In some other examples, UE 115-a may perform encoding and rate matching of UCI separately for different TRPs in multi-TRP system 210. UE 115-a may perform UCI encoding and rate matching based on the lowest or highest FDRA for the portion of the uplink shared channel message. That is, UE 115-a may determine that uplink shared channel portion 230-b has the lowest FDRA, uplink shared channel portion 230-a has the highest FDRA, or both. UE 115-a may multiplex a portion of the bits of UCI with uplink shared channel portion 230-a based on determining the lowest FDRA, the highest FDRA, or both, and multiplex different portions of the bits of UCI with uplink shared channel portion 230-b. If different portions of the uplink shared channel message include multiple RVs, UE 115-a may perform separate UCI encoding and rate matching. In some examples, UE 115-a may determine (e.g., via configuration or pre-configuration) that UCI on different TRPs can be the same, combinable, or both.

[0110] In some examples, UE 115-a may multiplex UCI with an uplink shared channel using a coding and rate matching scheme. UE 115-a may determine the multiplexing and rate matching scheme based on one or more parameters, such as the number of decoded symbols per layer for UCI transmission (e.g., where a symbol is a dynamically scheduled unit for time resources), UCI omission for UCI transmission, rate matching output sequence lengths for different UCIs, or any combination thereof. In some cases, UE 115-a may omit one or more UCI bits, such as for different parts of channel state information (CSI) (e.g., CSI part 1, CSI part 2, or both). Similarly, the rate matching output sequence length may be different for feedback messages (e.g., acknowledgment (ACK) or negative acknowledgment (NACK) (A / N)), CSI part 1, CSI part 2, or any combination thereof. UE 115-a may determine one or more time-frequency resources for UCI transmission based on the following: which is the scheduling bandwidth for uplink shared channel transmission and is expressed as a portion of the FDRA used for uplink shared channel transmission and the number of subcarriers corresponding to the TRP; and It is the number of resource elements that UE 115-a can use to send UCI in a symbol (e.g., OFDM symbol) of a FDRA that is part of the uplink shared channel transmission and corresponds to the TRP. That is, UE 115-a can determine the number of resource elements used for uplink shared channel transmission based on performing FDRA splitting on different TRPs in multi-TRP system 210. The value of .

[0111] UE 115-a may determine the number of per-layer coded symbols for UCI transmission according to Formula 1:

[0112]

[0113] where Q′ CSI-2 is the number of decoded symbols for CSI part 2, Q′ CSI-1 is the number of decoded symbols for CSI part 1, Q′ ACK / CG-UCI is the number of decoded modulation symbols for A / N with UCI, O CSI is the number of CSI bits, L CSI is the number of CRC bits used for CSI, is the number of offset bits used for PUSCH, is the total number of symbols allocated for PUSCH, K r is the rth code block size of the uplink shared channel used for PUSCH transmission, C UL-SCH is the number of code blocks of the uplink shared channel used for PUSCH transmission, and α is configured by a higher layer parameter scaling. The formula can be applied based on the portion of the uplink shared channel transmission associated with the corresponding TRP.

[0114] When UE 115-a is scheduled to send a transport block (TB) on an uplink shared channel (e.g., not using repetition type B multiplexed with one or more CSI reports), UE 115-a may Greater than In some cases, UE 115-a may omit CSI Part 2 in a step-by-step manner, such as starting with the lowest priority level (e.g., until the lowest priority level is reached), which may result in Less than or equal to

[0115] In some examples, once UE 115-a multiplexes UCI with portions of an uplink shared channel, such as uplink shared channel portion 230-a and uplink shared channel portion 230-b, UE 115-a may send an uplink shared channel 240 with a UCI message to network entity 105-a via a TRP (e.g., TRP 205-a and TRP 205-b). For example, UE 115-a may send uplink shared channel portion 230-a with UCI to TRP 205-a using a TCI state specific to TRP 205-a, and may send uplink shared channel portion 230-b with UCI to TRP 205-b using a TCI state specific to TRP 205-b. TRP 205-a and TRP 205-b may relay uplink shared channel portion 230-a and uplink shared channel portion 230-b, respectively, to network entity 105-a via communication link 125-a. Network entity 105-a may perform decoding and rate matching processes to obtain information in the uplink shared channel and UCI.

[0116] FIG3 illustrates examples of resource maps 300-a and 300-b, respectively, supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure. In some examples, resource maps 300-a and 300-b may implement aspects of wireless communication system 100 and wireless communication system 200. For example, resource maps 300-a and 300-b may be implemented by a wireless communication system in which a UE multiplexes UCI with different portions of an uplink shared channel to send to a network entity via multiple TRPs, wherein the network entity, the TRP, and the UE may be as described in reference to FIG3. Figure 1 and Figure 2 Examples of corresponding devices described.

[0117] In some examples, the network entity may define one or more rules or procedures for the UE to support multiplexing of UCI with the uplink shared channel for communication in a multi-TRP system. The network entity may send scheduling information to the UE to schedule one or more parts of the uplink shared channel message and indicate one or more TCI states for use by the UE. For example, the scheduling information may indicate one or more FDRAs to the UE, which may indicate that the UE uses a portion of the frequency resources for the uplink shared channel portion 305-a and the uplink shared channel portion 305-b, and a different portion of the frequency resources for the uplink shared channel portion 305-c and the uplink shared channel portion 305-d. The frequency resources may span one or more TBs. For example, as Figure 3AAs illustrated, the frequency resources for the uplink shared channel portion 305-a may span across TB 310-a, while the frequency resources for the uplink shared channel portion 305-c may span across TB 310-b. In some other examples, such as Figure 3B As illustrated, the frequency resources for the uplink shared channel portion 305-b and the uplink shared channel portion 305-d may span a single TB 310-c.

[0118] In some cases, such as Figure 3A , the scheduling indication may map the TB to the uplink shared channel portion based on one or more RVs of the uplink shared channel. For example, the uplink shared channel portion 305-a may include a first RV of the uplink shared channel, and the uplink shared channel portion 305-c may include a second RV of the uplink shared channel. Thus, the network entity may configure the UE to use TB 310-a for the first RV of the uplink shared channel and to use TB 310-b (e.g., uplink shared channel portion 305-a and uplink shared channel portion 305-c) for the second RV of the uplink shared channel. In some other cases, such as for Figure 3B , when the uplink shared channel parts are not different RVs, the scheduling indication may continuously map one TB for the uplink shared channel parts, so that TB 310-c may span the uplink shared channel part 305-b and the uplink shared channel part 305-d.

[0119] In some examples, the scheduling indication may indicate that the UE uses the TCI state 315-a for the uplink shared channel portion 305-c or the uplink shared channel portion 305-d for the first TRP, and uses the TCI state 315-b for the uplink shared channel portion 305-a or the uplink shared channel portion 305-b for the second TRP. That is, the UE may use different TCI states to transmit to different TRPs to increase beam diversity, which can achieve higher reliability at the UE. The UE may generate one or more UCI bits based on the uplink shared channel. For example, the UE may generate one or more bits for UCI 320-a for the uplink shared channel portion 305-a, UCI 320-b for the uplink shared channel portion 305-b, UCI 320-c for the uplink shared channel portion 305-c, and UCI 320-d for the uplink shared channel portion 305-d. In some examples, generating the UCI bits may include duplicating a single set of bits, splitting the UCI bits into multiple different sets, or both. The UE may omit one or more bits of the rate matching sequence that may be propagated to each duplicate set of UCI bits. Figure 1As described, the rate matching sequence including UCI omission may be calculated according to Formula 1.

[0120] Figure 4 An example of a process flow 400 for supporting uplink multiplexing for multi-TRP operation in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 may implement aspects of the wireless communication system 100, the wireless communication system 200, the resource map 300-a, and the resource map 300-b. The process flow 400 may illustrate an example in which a UE 115-b multiplexes UCI with different portions of an uplink shared channel to transmit to a network entity 105-b via multiple TRPs (e.g., TRP 405-a and TRP 405-b). The network entity 105-b, TRP 405-a, TRP 405-b, and UE 115-b may be as described in reference to Figure 1 and Figure 2 The examples of network entity 105, TRP 205 and UE 115 described above. The following alternative examples may be implemented, in which some of the processes are performed or not performed in an order different from the description. In some cases, each process may include additional features not mentioned below, or further processes may be added.

[0121] At 405, network entity 105-b may send a control message (e.g., a DCI message) indicating scheduling information for an uplink shared channel for UE 115-b. The scheduling information may include multiple TCI states for the uplink shared channel. For example, the scheduling information may include a TCI state for a first portion of the uplink shared channel to TRP 405-a and a different TCI state for a second portion of the uplink shared channel to TRP 405-b. In some cases, UE 115-b may split the uplink shared channel into a first portion and a second portion based on an upper limit function and a lower limit function, respectively, and the number of resource blocks allocated to the uplink shared channel (e.g., in the scheduling information).

[0122] In some cases, at 410, the network entity 105-b may send an additional control message that configures the UE 115-b to operate in FDM mode for uplink shared channel transmission. The additional control message may be an additional DCI message, or may be included in a DCI message carrying scheduling information. Additionally or alternatively, the network entity 105-b may send the FDM indicator prior to the scheduling information, such as in RRC signaling, MAC-CE, etc.

[0123] In some examples, at 415, UE 115-b may generate UCI based on receiving the scheduling information. For example, UE 115-b may generate UCI for the second portion of the uplink shared channel based on the UCI for the first portion of the uplink shared channel, such as by copying the UCI for the first portion of the uplink shared channel.

[0124] At 420, UE 115-b may encode the UCI. For example, UE 115-b may encode a first UCI for multiplexing with a first portion of the uplink shared channel using a set of coding parameters for a corresponding TCI state (e.g., assigned to a first portion of the uplink shared channel). UE 115-b may generate a second UCI for multiplexing with a second portion of the uplink shared channel based on encoding the first UCI. Additionally or alternatively, UE 115-b may encode the first UCI for multiplexing with the first portion of the uplink shared channel using a different coding scheme than a coding scheme for the second UCI multiplexed with the second portion of the uplink shared channel. The first UCI and the second UCI may have the same UCI payload (e.g., the same set of A / N bits, the same set of CSI reports, or both).

[0125] At 425, as part of the rate matching and encoding process or both, the UE 115-b may rate match the UCI after encoding. For example, the UE 115-b may perform rate matching on the first UCI using a rate matching scheme for the TCI of the first portion of the uplink shared channel. The UE 115-b may generate a second UCI for multiplexing with the second portion of the uplink shared channel based on rate matching the first UCI. Additionally or alternatively, the UE 115-b may rate match the first UCI after encoding the first UCI using a rate matching scheme different from the rate matching scheme used for the second UCI.

[0126] In some cases, UE 115-b may perform a coding and rate matching process using a coding and rate matching scheme for a corresponding TCI state (e.g., a first portion allocated to an uplink shared channel) to obtain a first UCI. For example, UE 115-b may determine a number of per-layer decoding symbols for a first UCI, omit one or more bits of the first UCI, and may determine one or more sequence lengths for different information subsets for the first UCI after omitting the one or more bits (e.g., according to Formula 1). Similarly, UE 115-b may perform a coding and rate matching process using a different coding and rate matching scheme to obtain a second UCI. UE 115-b may determine a number of per-layer decoding symbols for a second UCI, omit one or more bits of the second UCI, and may determine one or more sequence lengths for different information subsets for the second UCI after omitting the one or more bits (e.g., according to Formula 1).

[0127] At 430, UE 115-b may generate an uplink shared channel for transmission to TRP 405-a, TRP 405-b, or both. For example, UE 115-b may generate a first portion of the uplink shared channel having a first RV of the uplink shared channel and a second portion of the uplink shared channel having a second RV of the uplink shared channel (e.g., different from the first RV). In some other examples, UE 115-b may generate the first portion and the second portion of the uplink shared channel having the same RV (e.g., consecutive on the uplink shared channel portion).

[0128] At 435, UE 115-b may multiplex portions of an uplink shared channel (e.g., a first portion and a second portion of the uplink shared channel) with UCI according to different TCI states. For example, UE 115-b may multiplex the first UCI with the first portion of the uplink shared channel after performing rate matching for the first UCI. Similarly, UE 115-b may multiplex the second UCI with the second portion of the uplink shared channel after performing rate matching for the second UCI.

[0129] At 440, UE 115-b may use the TCI state for TRP 405-a to send a first portion of an uplink shared channel multiplexed with a first UCI to network entity 105-b. UE 115-b may use a set of time-frequency resources to send the first portion of the uplink shared channel, wherein the time resources overlap with a second transmission of a second portion of the uplink shared channel. The time-frequency resources may not overlap in frequency. UE 115-b may use the TCI state for TRP 405-b to send a second portion of the uplink shared channel multiplexed with a second UCI to network entity 105-b. In some examples, TRP 405-a and TRP 405-b may relay the first portion and the second portion of the uplink shared channel to network entity 105-b. In some other examples, TRP 405-a and TRP 405-b may serve as network entities.

[0130] At 445, network entity 105-b may perform a decoding process, a rate matching process, or both for the first UCI, the second UCI, or both based on the coding and rate matching scheme used by UE 115-b for the corresponding TCI state (e.g., the TCI state for TRP 405-a and the TCI state for TRP 405-b). Each TCI state may indicate a corresponding beam for UE 115-b to use when sending portions of the uplink shared channel multiplexed with the UCI. In some cases, if UE 115-b generates the second UCI by copying the first UCI, the first UCI and the second UCI may be the same.

[0131] Figure 5 A block diagram 500 of a device 505 supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown. The device 505 can 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).

[0132] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with uplink multiplexing for multi-TRP operation). 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.

[0133] 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 (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 uplink multiplexing for multi-TRP operation). 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.

[0134] 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 uplink multiplexing for multi-TRP operation 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.

[0135] 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, which is configured to or otherwise supports means 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).

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

[0137] In some examples, communication manager 520 can 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 can 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.

[0138] 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 a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The communication manager 520 may be configured to or otherwise support a component for sending a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The communication manager 520 may be configured to or otherwise support a component for sending a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in a plurality of TCI states.

[0139] By including or configuring a communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) can support a technique in which the UE multiplexes UCI with different portions of an uplink shared channel for transmission to a network entity via multiple TRPs, which can reduce processing, reduce power consumption, more efficiently utilize communication resources, and the like.

[0140] Figure 6 A block diagram 600 of a device 605 supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown. The device 605 can 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).

[0141] 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 associated with uplink multiplexing for multi-TRP operation). 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.

[0142] 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 (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 uplink multiplexing for multi-TRP operation). 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.

[0143] Device 605 or its various components may be examples of components for performing various aspects of uplink multiplexing for multi-TRP operation as described herein. For example, communication manager 620 may include scheduling component 625, multiplexing component 630, or any combination thereof. Communication manager 620 may be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 610, transmitter 615, or both or otherwise collaborate with them. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0144] According to the examples disclosed herein, the communication manager 620 may support wireless communication at the UE. The scheduling component 625 may be configured to or otherwise support a component for receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The multiplexing component 630 may be configured to or otherwise support a component for sending a first portion of the uplink shared channel multiplexed with the first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The multiplexing component 630 may be configured to or otherwise support a component for sending a second portion of the uplink shared channel multiplexed with the second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in a plurality of TCI states.

[0145] Figure 7A block diagram 700 of a communication manager 720 supporting uplink multiplexing for multi-TRP operation in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects of both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of uplink multiplexing for multi-TRP operation as described herein. For example, the communication manager 720 may include a scheduling component 725, a multiplexing component 730, a UCI component 735, an uplink shared channel component 740, an FDM component 745, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0146] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The scheduling component 725 may be configured to or otherwise support a component for receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The multiplexing component 730 may be configured to or otherwise support a component for sending a first portion of the uplink shared channel multiplexed with the first UCI via a first resource set according to a first TCI state in a plurality of TCI states. In some examples, the multiplexing component 730 may be configured to or otherwise support a component for sending a second portion of the uplink shared channel multiplexed with the second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in a plurality of TCI states.

[0147] In some examples, UCI component 735 may be configured or otherwise support components for generating a second UCI based on a first UCI, where the second UCI is a copy of the first UCI.

[0148] In some examples, UCI component 735 may be configured or otherwise support means for encoding a first UCI according to a set of encoding parameters associated with a first TCI state, wherein a second UCI is generated based on the encoded first UCI.

[0149] In some examples, UCI component 735 may be configured or otherwise support means for performing rate matching for a first UCI according to a rate matching scheme associated with a first TCI state, wherein a second UCI is generated based on the rate matched first UCI.

[0150] In some examples, multiplexing component 730 may be configured or otherwise support components for encoding the first UCI according to a first coding scheme. In some examples, multiplexing component 730 may be configured or otherwise support components for performing rate matching on the first UCI according to a first rate matching scheme after encoding the first UCI. In some examples, multiplexing component 730 may be configured or otherwise support components for multiplexing the first UCI with a first portion of an uplink shared channel after performing rate matching on the first UCI.

[0151] In some examples, the multiplexing component 730 may be configured or otherwise support components for encoding the second UCI according to the second coding scheme. In some examples, the multiplexing component 730 may be configured or otherwise support components for performing rate matching on the second UCI according to the second rate matching scheme after encoding the second UCI. In some examples, the multiplexing component 730 may be configured or otherwise support components for multiplexing the second UCI with the second portion of the uplink shared channel after performing rate matching on the second UCI.

[0152] In some examples, the first encoding scheme is different from the second encoding scheme.

[0153] In some examples, the first rate matching scheme is different from the second rate matching scheme.

[0154] In some examples, multiplexing component 730 may be configured or otherwise support means for performing a coding and rate matching process for a first set of UCI based on a first coding and rate matching scheme associated with a first TCI state to obtain a first UCI.

[0155] In some examples, to support performing a coding and rate matching process for a first set of UCI, the UCI component 735 may be configured to or otherwise support a component for determining a number of per-layer decoding symbols for the first set of UCI. In some examples, to support performing a coding and rate matching process for a first set of UCI, the UCI component 735 may be configured to or otherwise support a component for omitting one or more bits of the first set of UCI. In some examples, to support performing a coding and rate matching process for a first set of UCI, the UCI component 735 may be configured to or otherwise support a component for determining one or more sequence lengths for different information subsets for the first set of UCI after omitting one or more bits.

[0156] In some examples, multiplexing component 730 may be configured or otherwise support means for performing a coding and rate matching process on the second set of UCI based on the coding and rate matching scheme to obtain second UCI.

[0157] In some examples, to support performing a coding and rate matching process for the second set of UCI, the UCI component 735 may be configured to or otherwise support a component for determining the number of per-layer decoding symbols for the second set of UCI. In some examples, to support performing a coding and rate matching process for the second set of UCI, the UCI component 735 may be configured to or otherwise support a component for omitting one or more bits of the second set of UCI. In some examples, to support performing a coding and rate matching process for the second set of UCI, the UCI component 735 may be configured to or otherwise support a component for determining one or more sequence lengths for different information subsets for the second set of UCI after omitting one or more bits.

[0158] In some examples, uplink shared channel component 740 may be configured or otherwise support components for generating a first portion of an uplink shared channel based on a first redundancy version. In some examples, uplink shared channel component 740 may be configured or otherwise support components for generating a second portion of an uplink shared channel based on a second redundancy version different from the first redundancy version.

[0159] In some examples, uplink shared channel component 740 may be configured or otherwise support components for generating the first portion and the second portion of the uplink shared channel based on the same redundancy version.

[0160] In some examples, FDM component 745 may be configured or otherwise support means for receiving a second control message that configures the UE to operate in a frequency division multiplexing mode for uplink shared channel transmission.

[0161] In some examples, uplink shared channel component 740 can be configured or otherwise support components for splitting the uplink shared channel into a first portion based on an upper limit function and the number of resource blocks associated with the uplink shared channel. In some examples, uplink shared channel component 740 can be configured or otherwise support components for splitting the uplink shared channel into a second portion based on a lower limit function and the number of resource blocks associated with the uplink shared channel.

[0162] In some examples, the first set of resources and the second set of resources do not overlap in frequency.

[0163] Figure 8A diagram of a system 800 including a device 805 supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown. The device 805 can be an example of a device 505, a device 605, or a UE 115 as described herein or include components thereof. The device 805 can 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).

[0164] I / O controller 810 can manage input 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 a computer such as a , or other known operating systems. 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.

[0165] 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, wired or wireless links, 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 to provide 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.

[0166] 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 include a basic I / O system (BIOS), etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] 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., memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting uplink multiplexing for multi-TRP operation). 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, the processor 840 and the memory 830 being configured to perform the various functions described herein.

[0168] 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 a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The communication manager 820 may be configured to or otherwise support a component for sending a first portion of the uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The communication manager 820 may be configured to or otherwise support a component for sending a second portion of the uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in a plurality of TCI states.

[0169] By including or configuring a communication manager 820 according to the examples described herein, the device 805 can support technology for the UE to multiplex UCI with different parts of the uplink shared channel to send to a network entity via multiple TRPs, which can improve communication reliability, reduce latency, improve user experience related to reduced processing, reduce power consumption, more efficiently utilize communication resources, improve coordination between devices, extend battery life, improve utilization of processing power, and so on.

[0170] 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 uplink multiplexing for multi-TRP operation as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0171] Fig. 9 A block diagram 900 of a device 905 supporting uplink multiplexing for multi-TRP operation 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).

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

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

[0174] 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 uplink multiplexing for multi-TRP operation 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.

[0175] 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 configured as or otherwise supporting components for performing the functions described in this 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).

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

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

[0178] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a network entity. For example, the communication manager 920 may be configured to or otherwise support a component for sending a control message indicating scheduling information for an uplink shared channel for a UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The communication manager 920 may be configured to or otherwise support a component for receiving a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The communication manager 920 may be configured to or otherwise support a component for receiving a second portion of an uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps with the first resource set in time according to a second TCI state in a plurality of TCI states.

[0179] By including or configuring a communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support a technique in which the UE multiplexes UCI with different portions of an uplink shared channel to send to a network entity via multiple TRPs, which can reduce processing, reduce power consumption, more efficiently utilize communication resources, and so on.

[0180] Fig.10 A block diagram 1000 of a device 1005 supporting uplink multiplexing for multi-TRP operation 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 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).

[0181] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the 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.

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

[0183] Device 1005 or its various components may be examples of components for performing various aspects of uplink multiplexing for multi-TRP operation as described herein. For example, communication manager 1020 may include scheduling manager 1025, multiplexing manager 1030, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 1010, transmitter 1015, or both or otherwise collaborate with them. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0184] According to the examples 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 a component for sending a control message indicating scheduling information for an uplink shared channel for a UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. The multiplexing manager 1030 may be configured to or otherwise support a component for receiving a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The multiplexing manager 1030 may be configured to or otherwise support a component for receiving a second portion of an uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in a plurality of TCI states.

[0185] Fig.11 A block diagram 1100 of a communication manager 1120 supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of the communication manager 920, the communication manager 1020, or aspects of both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of uplink multiplexing for multi-TRP operation as described herein. For example, the communication manager 1120 may include a scheduling manager 1125, a multiplexing manager 1130, an FDM manager 1135, a decoding manager 1140, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0186] According to examples as disclosed herein, the communication manager 1120 may support wireless communication at a network entity. The scheduling manager 1125 may be configured to or otherwise support a component for sending a control message indicating scheduling information for an uplink shared channel for a UE, the scheduling information indicating multiple TCI states for the uplink shared channel. The multiplexing manager 1130 may be configured to or otherwise support a component for receiving a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. In some examples, the multiplexing manager 1130 may be configured to or otherwise support a component for receiving a second portion of an uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in a plurality of TCI states.

[0187] In some examples, FDM manager 1135 may be configured or otherwise support components for sending a second control message that configures the UE to operate in frequency division multiplexing mode for uplink shared channel transmission.

[0188] In some examples, the decoding manager 1140 may be configured or otherwise support components for performing a decoding and rate matching process for the first UCI based on a first coding and rate matching scheme associated with the first TCI state. In some examples, the decoding manager 1140 may be configured or otherwise support components for performing a decoding and rate matching process for the second UCI based on the first coding and rate matching scheme associated with the first TCI state.

[0189] In some examples, the first UCI and the second UCI are the same.

[0190] In some examples, decoding manager 1140 may be configured or otherwise support components for performing a first decoding and rate matching process for a first UCI based on a first coding and rate matching scheme associated with a first TCI state.

[0191] In some examples, decoding manager 1140 may be configured or otherwise support components for performing a second decoding and rate matching process for the second UCI based on a second encoding and rate matching scheme associated with the second TCI state.

[0192] In some examples, the first UCI and the second UCI are different.

[0193] In some examples, the first set of resources and the second set of resources do not overlap in frequency.

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

[0195] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215 that are capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and demodulating the signal. Where applicable, the transceiver 1210 or the transceiver 1210 and one or more antennas 1215 or a wired interface may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or any component thereof as described herein. In some examples, the transceiver is operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0197] 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 device, a discrete hardware component, or any combination thereof). In some cases, 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 processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., various functions or tasks supporting the technology for TRP reporting). For example, device 1205 or a component of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform the various functions described herein. Processor 1235 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1230) to perform the functions of device 1205.

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

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

[0200] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a component for sending a control message indicating scheduling information for an uplink shared channel for a UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. The communication manager 1220 may be configured to or otherwise support a component for receiving a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The communication manager 1220 may be configured to or otherwise support a component for receiving a second portion of an uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in a plurality of TCI states.

[0201] By including or configuring a communication manager 1220 according to the examples described herein, the device 1205 can support technology for the UE to multiplex UCI with different parts of the uplink shared channel to send to a network entity via multiple TRPs, which can improve communication reliability, reduce latency, improve user experience related to reduced processing, reduce power consumption, more efficiently utilize communication resources, improve coordination between devices, extend battery life, improve utilization of processing power, and so on.

[0202] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (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 processor 1235, the memory 1225, the code 1230, the transceiver 1210, 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 uplink multiplexing for multi-TRP operation as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0203] Fig.13 A flow chart is shown that illustrates a method 1300 for supporting uplink multiplexing for multi-TRP operation 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 UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0204] At 1305, the method may include: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The described scheduling component 725 is executed.

[0205] At 1310, the method may include: sending a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. 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 Figure 7 The multiplexing component 730 executes.

[0206] At 1315, the method may include: sending a second portion of the uplink shared channel multiplexed with the second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states. 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 multiplexing component 730 executes.

[0207] Fig.14 A flow chart is shown that illustrates a method 1400 for supporting uplink multiplexing for multi-TRP operation 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 UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0208] At 1405, the method may include: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The described scheduling component 725 is executed.

[0209] At 1410, the method may include: generating a second UCI based on the first UCI, wherein the second UCI is a copy of the first UCI. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference Figure 7 The UCI component 735 is used to execute.

[0210] At 1415, the method may include: sending a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. 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 multiplexing component 730 executes.

[0211] At 1420, the method may include: sending a second portion of the uplink shared channel multiplexed with the second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0212] Fig.15 A flow chart is shown that illustrates a method 1500 for supporting uplink multiplexing for multi-TRP operation according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0213] At 1505, the method may include: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. 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 Figure 7 The described scheduling component 725 is executed.

[0214] At 1510, the method may include encoding the first UCI according to a first coding scheme. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0215] At 1515, the method may include: performing rate matching on the first UCI according to the first rate matching scheme after encoding the first UCI. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0216] At 1520, the method may include: multiplexing the first UCI with a first portion of an uplink shared channel after performing rate matching for the first UCI. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0217] At 1525, the method may include: sending a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0218] At 1530, the method may include: sending a second portion of the uplink shared channel multiplexed with the second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states. The operations of 1530 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1530 may be performed as described in reference to Figure 7 The multiplexing component 730 executes.

[0219] Fig.16 A flow chart is shown that illustrates a method 1600 for supporting uplink multiplexing for multi-TRP operation 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 herein. Figures 1 to 4 as well as Figures 9 to 12 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0220] At 1605, the method may include: sending a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of TCI states for the uplink shared channel. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The described schedule manager 1125 is executed.

[0221] At 1610, the method may include receiving a first portion of an uplink shared channel multiplexed with a first UCI via a first resource set according to a first TCI state in a plurality of TCI states. 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 multiplexing manager 1130 executes.

[0222] At 1615, the method may include receiving a second portion of an uplink shared channel multiplexed with a second UCI via a second resource set that at least partially overlaps in time with the first resource set according to a second TCI state in the plurality of TCI states. 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 multiplexing manager 1130 executes.

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

[0224] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating multiple transmission configuration indicator states for the uplink shared channel; sending a first part of the uplink shared channel multiplexed with first uplink control information via a first resource set according to a first transmission configuration indicator state among the multiple transmission configuration indicator states; and sending a second part of the uplink shared channel multiplexed with second uplink control information via a second resource set that at least partially overlaps with the first resource set in time according to a second transmission configuration indicator state among the multiple transmission configuration indicator states.

[0225] Aspect 2: According to the method according to aspect 1, the method also includes: generating the second uplink control information based at least in part on the first uplink control information, wherein the second uplink control information is a copy of the first uplink control information.

[0226] Aspect 3: According to the method of Aspect 2, the method also includes: encoding the first uplink control information according to a set of coding parameters associated with the first transmission configuration indicator state, wherein the second uplink control information is generated at least in part based on the encoded first uplink control information.

[0227] Aspect 4: According to the method described in any one of Aspects 2 to 3, the method further includes: performing rate matching for the first uplink control information according to a rate matching scheme associated with the first transmission configuration indicator state, wherein the second uplink control information is generated at least in part based on the rate matched first uplink control information.

[0228] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: encoding the first uplink control information according to a first coding scheme; performing rate matching on the first uplink control information according to a first rate matching scheme after encoding the first uplink control information; and multiplexing the first uplink control information with the first part of the uplink shared channel after performing rate matching on the first uplink control information.

[0229] Aspect 6: According to the method described in Aspect 5, the method also includes: encoding the second uplink control information according to a second coding scheme; performing rate matching on the second uplink control information according to a second rate matching scheme after encoding the second uplink control information; and multiplexing the second uplink control information with the second part of the uplink shared channel after performing rate matching on the second uplink control information.

[0230] Aspect 7: The method according to aspect 6, wherein the first encoding scheme is different from the second encoding scheme.

[0231] Aspect 8: The method according to any one of aspects 6 to 7, wherein the first rate matching scheme is different from the second rate matching scheme.

[0232] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method also includes: performing a coding and rate matching process for a first group of uplink control information at least partially based on a first coding and rate matching scheme associated with the first transmission configuration indicator state to obtain the first uplink control information.

[0233] Aspect 10: A method according to Aspect 9, wherein performing the coding and rate matching process for the first group of uplink control information includes: determining the number of decoding symbols per layer for the first group of uplink control information; omitting one or more bits of the first group of uplink control information; and determining one or more sequence lengths for different information subsets of the first group of uplink control information after omitting the one or more bits.

[0234] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: performing a coding and rate matching process on a second set of uplink control information at least in part based on a coding and rate matching scheme to obtain the second uplink control information.

[0235] Aspect 12: A method according to Aspect 11, wherein performing the coding and rate matching process for the second set of uplink control information includes: determining the number of decoding symbols per layer for the second set of uplink control information; omitting one or more bits of the second set of uplink control information; and determining one or more sequence lengths for different information subsets of the second set of uplink control information after omitting the one or more bits.

[0236] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method also includes: generating the first part of the uplink shared channel at least partially based on a first redundant version; and generating the second part of the uplink shared channel at least partially based on a second redundant version different from the first redundant version.

[0237] Aspect 14: The method according to any one of aspects 1 to 12, the method further comprising: generating the first part and the second part of the uplink shared channel based at least in part on the same redundancy version.

[0238] Aspect 15: According to the method according to any one of Aspects 1 to 14, the method further includes: receiving a second control message, wherein the second control message configures the UE to operate in a frequency division multiplexing mode for uplink shared channel transmission.

[0239] Aspect 16: According to the method described in any one of Aspects 1 to 15, the method also includes: splitting the uplink shared channel into the first part at least partially based on an upper limit function and the number of resource blocks associated with the uplink shared channel; and splitting the uplink shared channel into the second part at least partially based on a lower limit function and the number of resource blocks associated with the uplink shared channel.

[0240] Aspect 17: The method according to any one of aspects 1 to 16, wherein the first resource set and the second resource set do not overlap in frequency.

[0241] Aspect 18: A method for performing wireless communications at a network entity, the method comprising: sending a control message indicating scheduling information of an uplink shared channel for a UE, the scheduling information indicating multiple transmission configuration indicator states for the uplink shared channel; receiving a first part of the uplink shared channel multiplexed with first uplink control information via a first resource set according to a first transmission configuration indicator state among the multiple transmission configuration indicator states; and receiving a second part of the uplink shared channel multiplexed with second uplink control information via a second resource set that at least partially overlaps with the first resource set in time according to a second transmission configuration indicator state among the multiple transmission configuration indicator states.

[0242] Aspect 19: The method according to aspect 18 further comprises: sending a second control message, wherein the second control message configures the UE to operate in a frequency division multiplexing mode for uplink shared channel transmission.

[0243] Aspect 20: According to the method described in any one of Aspects 18 to 19, the method also includes: performing a decoding and rate matching process for the first uplink control information at least partially based on a first coding and rate matching scheme associated with the first transmission configuration indicator state; and performing the decoding and rate matching process for the second uplink control information at least partially based on the first coding and rate matching scheme associated with the first transmission configuration indicator state.

[0244] Aspect 21: The method according to aspect 20, wherein the first uplink control information and the second uplink control information are the same.

[0245] Aspect 22: According to the method described in any one of Aspects 18 to 21, the method also includes: performing a first decoding and rate matching process for the first uplink control information at least in part based on a first coding and rate matching scheme associated with the first transmission configuration indicator state.

[0246] Aspect 23: According to the method according to aspect 22, the method also includes: performing a second decoding and rate matching process for the second uplink control information based at least in part on a second coding and rate matching scheme associated with the second transmission configuration indicator state.

[0247] Aspect 24: The method according to aspect 23, wherein the first uplink control information and the second uplink control information are different.

[0248] Aspect 25: The method according to any one of aspects 18 to 24, wherein the first resource set and the second resource set do not overlap in frequency.

[0249] Aspect 26: 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 17.

[0250] Aspect 27: 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 17.

[0251] Aspect 28: 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 the method according to any one of aspects 1 to 17.

[0252] Aspect 29: 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 18 to 25.

[0253] Aspect 30: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 18 to 25.

[0254] Aspect 31: 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 18 to 25.

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

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

[0257] The information and signals described herein may be represented using any of a variety of different techniques 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.

[0258] 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 combination with a DSP core, or any other such configuration).

[0259] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent on 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 any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

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

[0261] 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, such 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."

[0262] 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 similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

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

[0264] 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 technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of transmit configuration indicator states for the uplink shared channel; transmitting a first portion of the uplink shared channel multiplexed with first uplink control information via a first resource set according to a first transmission configuration indicator state among the plurality of transmission configuration indicator states; as well as A second portion of the uplink shared channel multiplexed with second uplink control information is transmitted via a second resource set at least partially overlapping in time with the first resource set according to a second transmission configuration indicator state of the plurality of transmission configuration indicator states.

2. The method according to claim 1, further comprising: The second uplink control information is generated based at least in part on the first uplink control information, wherein the second uplink control information is a copy of the first uplink control information.

3. The method according to claim 2, further comprising: The first uplink control information is encoded according to a set of encoding parameters associated with the first transmission configuration indicator state, wherein the second uplink control information is generated based at least in part on the encoded first uplink control information.

4. The method according to claim 2, further comprising: Rate matching is performed on the first uplink control information according to a rate matching scheme associated with the first transmission configuration indicator state, wherein the second uplink control information is generated based at least in part on the rate matched first uplink control information.

5. The method according to claim 1, further comprising: encoding the first uplink control information according to a first coding scheme; performing rate matching on the first uplink control information according to a first rate matching scheme after encoding the first uplink control information; as well as The first uplink control information is multiplexed with the first portion of the uplink shared channel after performing rate matching on the first uplink control information.

6. The method according to claim 5, further comprising: encoding the second uplink control information according to a second coding scheme; performing rate matching on the second uplink control information according to a second rate matching scheme after encoding the second uplink control information; as well as The second uplink control information is multiplexed with the second portion of the uplink shared channel after performing rate matching on the second uplink control information. The method of claim 6 , wherein the first encoding scheme is different from the second encoding scheme. The method of claim 6 , wherein the first rate matching scheme is different from the second rate matching scheme.

9. The method according to claim 1, further comprising: A coding and rate matching process is performed on a first set of uplink control information based at least in part on a first coding and rate matching scheme associated with the first transmission configuration indicator state to obtain the first uplink control information.

10. The method of claim 9, wherein performing the coding and rate matching process for the first set of uplink control information comprises: determining a number of per-layer decoded symbols for the first set of uplink control information; omitting one or more bits of the first set of uplink control information; as well as One or more sequence lengths for different information subsets of the first set of uplink control information are determined after omitting the one or more bits.

11. The method according to claim 1, further comprising: A coding and rate matching process is performed on a second set of uplink control information based at least in part on a coding and rate matching scheme to obtain the second uplink control information.

12. The method of claim 11, wherein performing the coding and rate matching process for the second set of uplink control information comprises: determining a number of per-layer decoded symbols for the second set of uplink control information; omitting one or more bits of the second set of uplink control information; as well as One or more sequence lengths for different information subsets of the second set of uplink control information are determined after omitting the one or more bits.

13. The method according to claim 1, further comprising: generating the first portion of the uplink shared channel based at least in part on a first redundancy version; as well as The second portion of the uplink shared channel is generated based at least in part on a second redundancy version different than the first redundancy version.

14. The method according to claim 1, further comprising: The first portion and the second portion of the uplink shared channel are generated based at least in part on a same redundancy version.

15. The method according to claim 1, further comprising: A second control message is received, the second control message configuring the UE to operate in a frequency division multiplexing mode for uplink shared channel transmission.

16. The method according to claim 1, further comprising: splitting the uplink shared channel into the first portion based at least in part on an upper limit function and a number of resource blocks associated with the uplink shared channel; as well as The uplink shared channel is split into the second portion based at least in part on a floor function and the number of resource blocks associated with the uplink shared channel.

17. The method of claim 1, wherein the first set of resources and the second set of resources do not overlap in frequency.

18. A method for wireless communication at a network entity, the method comprising: transmitting a control message indicating scheduling information for an uplink shared channel for a user equipment (UE), the scheduling information indicating a plurality of transmit configuration indicator states for the uplink shared channel; receiving, via a first resource set, a first portion of the uplink shared channel multiplexed with first uplink control information according to a first transmission configuration indicator state among the plurality of transmission configuration indicator states; as well as A second portion of the uplink shared channel multiplexed with second uplink control information is received via a second resource set at least partially overlapping in time with the first resource set according to a second transmission configuration indicator state of the plurality of transmission configuration indicator states.

19. The method according to claim 18, further comprising: A second control message is sent, the second control message configuring the UE to operate in a frequency division multiplexing mode for uplink shared channel transmission.

20. The method according to claim 18, further comprising: performing a decoding and rate matching process for the first uplink control information based at least in part on a first coding and rate matching scheme associated with the first transmit configuration indicator state; as well as The decoding and rate matching process is performed for the second uplink control information based at least in part on the first coding and rate matching scheme associated with the first transmission configuration indicator state.

21. The method of claim 20, wherein the first uplink control information and the second uplink control information are the same.

22. The method according to claim 18, further comprising: A first decoding and rate matching process is performed for the first uplink control information based at least in part on a first coding and rate matching scheme associated with the first transmission configuration indicator state.

23. The method according to claim 22, further comprising: A second decoding and rate matching process is performed for the second uplink control information based at least in part on a second coding and rate matching scheme associated with the second transmission configuration indicator state.

24. The method of claim 23, wherein the first uplink control information and the second uplink control information are different.

25. The method of claim 18, wherein the first set of resources and the second set of resources do not overlap in frequency.

26. 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 a control message indicating scheduling information for an uplink shared channel for the UE, the scheduling information indicating a plurality of transmit configuration indicator states for the uplink shared channel; transmitting a first portion of the uplink shared channel multiplexed with first uplink control information via a first resource set according to a first transmission configuration indicator state among the plurality of transmission configuration indicator states; as well as A second portion of the uplink shared channel multiplexed with second uplink control information is transmitted via a second resource set at least partially overlapping in time with the first resource set according to a second transmission configuration indicator state of the plurality of transmission configuration indicator states.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: The second uplink control information is generated based at least in part on the first uplink control information, wherein the second uplink control information is a copy of the first uplink control information.

28. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: encoding the first uplink control information according to a first coding scheme; performing rate matching on the first uplink control information according to a first rate matching scheme after encoding the first uplink control information; and The first uplink control information is multiplexed with the first portion of the uplink shared channel after performing rate matching on the first uplink control information.

29. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: A coding and rate matching process is performed on a first set of uplink control information based at least in part on a first coding and rate matching scheme associated with the first transmission configuration indicator state to obtain the first uplink control information.

30. 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 a control message indicating scheduling information for an uplink shared channel for a user equipment (UE), the scheduling information indicating a plurality of transmit configuration indicator states for the uplink shared channel; receiving, via a first resource set, a first portion of the uplink shared channel multiplexed with first uplink control information according to a first transmission configuration indicator state among the plurality of transmission configuration indicator states; as well as A second portion of the uplink shared channel multiplexed with second uplink control information is received via a second resource set at least partially overlapping in time with the first resource set according to a second transmission configuration indicator state of the plurality of transmission configuration indicator states.

Images