Uplink single frequency network operation in unified transmission configuration indication framework

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control signaling that enables uplink communication with a network via a first transmit and receive point (TRP) using a first set of antenna elements of the UE and via a second TRP using a second set of antenna elements of the UE during a same set of time and frequency resources according to a single frequency network (SFN) configuration. The control signaling may include a set of parameters that enable the uplink communication with the network via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The control signaling may also include a set of control resources including an indication for the UE to transmit according to an SFN transmission scheme. The UE may transmit the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, including uplink single frequency network (SFN) operations in a unified transmission configuration indication (TCI) framework. 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 for a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting uplink single frequency network (SFN) operations in a unified transmission configuration indication (TCI) framework. For example, the described techniques provide for utilizing one or more parameters at a user equipment (UE) that may allow the UE to perform uplink SFN operations supporting a unified TCI framework. For example, the UE may receive signaling that uses SFN-based transmission configuration for one or more uplink channel types (e.g., a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a combination thereof). In some examples, the UE may perform SFN transmission for the PUSCH using a pre-decoder associated with one or more sounding reference signal (SRS) resource sets. In some cases, the UE may determine to implement SFN operation for at least one uplink channel based on a control resource set (CORESET) associated with RRC signaling that includes a flag indicating the use of a unified TCI. In an example where SFN operation may be implemented for at least one uplink channel, the UE may receive an indication of a TCI code point associated with two or more respective uplink TCI states for transmission to respective transmission and reception points (TRPs). If the UE is capable of SFN operation, the UE may dynamically switch between a non-SFN transmission scheme and a SFN transmission scheme.

[0004] A method for wireless communication at a UE is described. The method may include: receiving control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

[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 are executable by the processor to cause the apparatus to: receive control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and send the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and means for sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

[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: receive control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and send the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing the following operations: receiving a parameter set that enables the uplink communication with the network via the PUCCH or the PUSCH; and sending the uplink communication to the network via the PUCCH or the PUSCH according to the parameter set.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: selecting one or more SRS sets based on receiving the control signaling that enables the uplink communication with the network according to the SFN configuration.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the one or more SRS sets may include operations, features, components, or instructions for performing the following operations: selecting a first SRS set and a second SRS set configured at the UE; and receiving downlink control information (DCI) or a configured grant (CG), the configured grant (CG) including a first resource indicator associated with the first SRS set and a second resource indicator associated with the second SRS set; wherein the first resource indicator and the second resource indicator may be an SRS resource indicator (SRI), a transmit precoding matrix index (TPMI), or a combination thereof.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first resource indicator and the second resource indicator may have the same indicator rank and share the same set of demodulation reference signal (DMRS) ports.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the one or more SRS sets may include operations, features, components, or instructions for performing the following operations: receiving a first reference signal indicating a first SRS set and a second reference signal indicating a second SRS set; and receiving a DCI or a CG, the CG including a first resource indicator associated with the first SRS set and a second resource indicator associated with the second SRS set; wherein the first resource indicator and the second resource indicator may be SRIs.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first resource indicator and the second resource indicator may have the same indicator rank and share the same set of DMRS ports.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing the following operations: receiving a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to the SFN transmission scheme.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for performing the following operations: receiving a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to a transmission scheme different from the SFN transmission scheme.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving one or more messages indicating a first TCI code point including one or more TCIs based on receiving the control signaling that enables the uplink communication with the network.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the one or more messages may include operations, features, components, or instructions for performing the following operations: receiving a medium access control-control element (MAC-CE) that activates a set of multiple transmit configuration indicator code points configured at the UE; and receiving a DCI that includes a TCI that indicates the first TCI code point from the set of multiple activated TCI code points.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the one or more messages may include operations, features, components, or instructions for performing the following operations: receiving a MAC-CE that activates a single TCI code point from a set of multiple transmit configuration indicator code points configured at the UE.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first TCI code point includes a TCI, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following operations: sending the uplink communication to the network via the first TRP according to the SFN configuration, wherein the SFN configuration may be a non-SFN transmission scheme.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first TCI code point includes two or more TCIs, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following operations: sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration, wherein the SFN configuration may be a SFN transmission scheme.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first TCI code point includes two or more TCIs, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following operations: receiving a DCI including a TRP switching indication indicating the use of a first TCI associated with the first TRP; and sending the uplink communication to the network via the first TRP according to the SFN configuration, wherein the SFN configuration includes a non-SFN transmission scheme.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first TCI code point includes two or more TCIs, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following operations: receiving a DCI including a TRP switching indication indicating the use of the two or more TCIs; and sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration, wherein the SFN configuration includes a SFN sending scheme.

[0023] A method of wireless communication at a network entity is described. The method may include: sending control signaling that enables a UE to perform uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and receiving the uplink communication of the network via the first TRP, the second TRP, or a combination thereof according to the SFN configuration.

[0024] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send control signaling that enables a UE to perform uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and receive the uplink communication of the network via the first TRP, the second TRP, or a combination thereof according to the SFN configuration.

[0025] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending control signaling that enables a UE to perform uplink communications with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and means for receiving the uplink communications of the network via the first TRP, the second TRP, or a combination thereof according to the SFN configuration.

[0026] 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: send control signaling that enables a UE to perform uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during a same set of time and frequency resources according to an SFN configuration; and receive the uplink communication of the network via the first TRP, the second TRP, or a combination thereof according to the SFN configuration.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for performing the following operations: sending a parameter set that enables the uplink communication with the network via the PUCCH or PUSCH; and receiving the uplink communication via the PUCCH or the PUSCH based on the parameter set.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for performing the following operations: sending a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to the SFN transmission scheme.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for performing the following operations: sending a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to a transmission scheme different from the SFN transmission scheme.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending one or more messages indicating a first TCI code point including one or more TCIs based on receiving the control signaling that enables the uplink communication with the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 An example of a wireless communication system supporting uplink single frequency network (SEN) operation in a unified transmission configuration indication (TCI) framework according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 2 An example of a network architecture supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 3 An example of a wireless communication system supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 4 An example of a process flow for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 5 An example of a process flow for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 6 and Figure 7 A block diagram of an apparatus supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown.

[0037] Figure 8 A block diagram of a communication manager supporting uplink SFN operations in a unified TCI framework is shown in accordance with one or more aspects of the present disclosure.

[0038] Fig. 9 A diagram of a system including devices supporting uplink SFN operation in a unified TCI framework is shown in accordance with one or more aspects of the present disclosure.

[0039] Fig.10 and Fig.11 A block diagram of an apparatus supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown.

[0040] Fig.12A block diagram of a communication manager supporting uplink SFN operations in a unified TCI framework is shown in accordance with one or more aspects of the present disclosure.

[0041] Fig.13 A diagram of a system including devices supporting uplink SFN operation in a unified TCI framework is shown in accordance with one or more aspects of the present disclosure.

[0042] Figures 14 to 17 A flow chart illustrating a method for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0043] Some wireless communication systems may support a unified transmission configuration indicator (TCI) framework, where different unified TCI types may be used to improve channel utilization between wireless devices. For example, a wireless communication system may support multiple downlink and uplink TCI states that may facilitate communication between a user equipment (UE) and multiple transmit and receive points (TRPs) associated with one or more network entities. In some cases, the UE may communicate with a TRP, and each TRP may use different beams (e.g., using the same time and frequency resources, but using different spatial resources) to send the same signal to the UE, which may be referred to as a single frequency network (SFN) communication. Therefore, the UE may receive downlink SFN communications based on the unified TCI framework. However, currently, wireless communication systems may not support technology for applying a unified TCI type to uplink SFN communications.

[0044] Thus, utilizing one or more parameters at the UE may allow the UE to perform uplink SFN operation supporting a unified TCI framework. For example, the UE may receive radio resource control (RRC) signaling that configures SFN-based transmission for one or more uplink channel types (e.g., a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a combination thereof). In some examples, the UE may perform SFN transmission for the PUSCH using a precoder indication associated with one or more sounding reference signal (SRS) resource sets. In some cases, the UE may determine to implement SFN operation for at least one uplink channel based on a control resource set (CORESET) associated with the RRC signaling, the control resource set including a flag (e.g., followUnifiedTCI flag) indicating the use of a unified TCI (e.g., a bit, a set of bits, a signal, a sequence, a field value, or other indicator).

[0045] In an example where SFN operation may be implemented for at least one uplink channel, the UE may receive an indication of a TCI code point associated with two or more respective uplink TCI states for transmission to a respective TRP. In some cases, the TCI code point may be indicated via downlink control information (DCI), a medium access control-control element (MAC-CE), or other control signaling indicating a TCI code point from a set of TCI code points.

[0046] If the UE is capable of SFN operation, the UE may switch (e.g., dynamically) between a non-SFN transmission scheme and a SFN transmission scheme for uplink communications. The non-SFN transmission scheme may be any transmission scheme (a second transmission scheme) used by the UE for the uplink other than the same SFN transmission scheme, such as a single TRP transmission scheme, a multiple TRP transmission scheme (e.g., using single DCI scheduling, multiple DCI scheduling, DCI repetition), or PUCCH and / or PUSCH repetition, or other transmission schemes described herein. For example, if the received TCI code point is associated with a single uplink feasible TCI state, the UE may operate according to the non-SFN transmission scheme, and if the received TCI code point is associated with two or more uplink feasible TCI states, the UE may operate according to the SFN transmission scheme. Additionally or alternatively, in the case where the UE receives a TCI code point associated with two TCI states, the UE may receive a DCI including a dedicated TRP switching indication field. Thus, the TRP switching indication may instruct the UE to use the first TCI state (e.g., for a non-SFN transmission scheme), to use the second TCI state (e.g., for a non-SFN transmission scheme), or to use both the first TCI state and the second TCI state (e.g., for SFN transmission).

[0047] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described by and with reference to a network architecture and process flows. 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 SFN operations in a unified TCI framework.

[0048] Figure 1An example of a wireless communication system 100 supporting uplink SFN operation in a unified TCI framework 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, and the network entity 105 and the UE 115 may support signal communication over the geographic area 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. 1. The UEs 115 described herein may be able to communicate with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[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 directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[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, standalone) base station architecture, which may be configured to utilize a protocol stack that is 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, or 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., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 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 the other 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 the 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 host entities or IAB hosts. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) 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 host. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0057] 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 SFN operations in a unified TCI framework as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0059] 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, relay base stations, etc. Figure 1 shown.

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

[0061] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that employs MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and 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 for 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, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0062] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. 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).

[0063] 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 multiple 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 multiple 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 containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0064] A subframe, a slot, a mini-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 transmit 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 bursts of shortened TTIs (sTTIs)).

[0065] 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., CORESET) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

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

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

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

[0070] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for 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 via 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.

[0071] 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). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is 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 the waves may be sufficient to penetrate structures so that macro cells provide service 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.

[0072] 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 use 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 network entities 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0073] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that 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, 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 transmitted via the antenna ports.

[0074] The network entity 105 or the UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, 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.

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

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

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

[0078] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may 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).

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

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

[0081] In the wireless communication system 100, the UE 115 may communicate with the network via two or more TRPs. The wireless communication system 100 may apply a unified TCI state framework. In some cases, three types of unified TCI states may be defined. The first type of TCI state (e.g., type 1) may include a joint TCI state to indicate a common beam for at least one downlink channel or reference signal and at least one uplink channel or reference signal (e.g., including a UE-specific physical downlink control channel (PDCCH), a UE-specific physical downlink shared channel (PDSCH), a UE-specific PUCCH, and a UE-specific PUSCH). The second type of TCI state (e.g., type 2) may include a downlink TCI state to indicate a common beam for more than one downlink channel or reference signal (e.g., including at least a UE-specific PDCCH and a UE-specific PDSCH). The third type of TCI state (e.g., type 3) may include an uplink TCI state to indicate a common beam for more than one uplink channel or reference signal (e.g., including at least a UE-specific PUCCH and a UE-specific PUSCH). For example, the network may indicate multiple downlink or uplink states for multiple TRPs to UE 115. In some examples, the TCI applicable to the uplink may be a joint TCI or an uplink TCI.

[0082] In some cases, UE 115 may be configured to send uplink communications via a SFN configuration. In the SFN configuration, UE 115 may send the same uplink signal to two or more TRPs using different beams via different antenna panels at UE 115 in the same time and frequency resources. Example applications of uplink SFN configurations may include client equipment, fixed wireless broadband, or industrial equipment. In some cases, in order to facilitate simultaneous multi-panel uplink transmissions to obtain higher uplink throughput and reliability (e.g., focusing on FR2 and multiple TRPs), an uplink precoding indication for PUSCH may be specified, where no new codebook is introduced for simultaneous transmission of multiple panels. In some cases, considering multi-TRP operations based on single DCI and multiple DCI, the total number of layers across all panels may be up to four, and the total number of codewords across all panels may be up to two. In some cases, in order to facilitate simultaneous multi-panel uplink transmissions for higher uplink throughput and reliability (e.g., focusing on FR2 and multiple TRPs), uplink beam indications for PUCCH or PUSCH may be specified, where a unified TCI framework may be assumed to take into account multi-TRP operations based on single DCI and multiple DCIs. For the case of multi-TRP operation based on multiple DCIs, in some examples, PUSCH+PUSCH or PUCCH+PUCCH may be transmitted on two panels in the same component carrier. In some cases, timing advances for uplink multi-DCIs for multi-TRP operation may be specified. In some cases, power control for uplink single DCIs for multi-TRP operation may be applied.

[0083] Thus, utilizing one or more parameters at UE 115 may allow UE 115 to perform uplink SFN operation supporting a unified TCI framework. For example, UE 115 may receive RRC signaling that configures SFN-based transmission for one or more uplink channel types. In some examples, UE 115 may perform SFN transmission for PUSCH using a precoder indication associated with one or more SRS resource sets received from network entity 105. In some cases, UE 115 may determine to implement SFN operation for at least one uplink channel based on a CORESET associated with RRC signaling that includes a flag indicating the use of unified TCI.

[0084] In an example where SFN operation may be implemented for at least one uplink channel, UE 115 may receive an indication of a TCI code point associated with two or more corresponding uplink applicable TCI states for transmission to a corresponding TRP. In some cases, the TCI code point may be indicated via a DCI, MAC-CE, other control signaling, or a combination thereof indicating a TCI code point from a set of TCI code points.

[0085] If the UE 115 is capable of SFN operation, the UE 115 may dynamically switch between a non-SFN transmission scheme and a SFN transmission scheme. For example, if the received TCI code point is associated with a single uplink applicable TCI state, the UE 115 may operate according to the non-SFN transmission scheme, and if the received TCI code point is associated with two or more uplink applicable TCI states, the UE 115 may operate according to the SFN transmission scheme. Additionally or alternatively, in the case where the UE 115 receives a TCI code point associated with two uplink applicable TCI states, the UE 115 may receive a DCI including a dedicated TRP switching indication field. Therefore, the TRP switching indication may indicate that the UE 115 uses a first TCI state (e.g., for a non-SFN transmission scheme), uses a second TCI state (e.g., for a non-SFN transmission scheme), or uses both the first TCI state and the second TCI state (e.g., for SFN transmission).

[0086] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting uplink SFN operations in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly communicate with the core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served simultaneously by multiple RUs 170-a.

[0087] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0088] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0089] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional splits, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0090] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0091] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) to perform network entity lifecycle management (e.g., instantiating virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate (e.g., via an O1 interface) with components configured according to a 4G RAN. Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0092] The non-RT RIC 175-a may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b.

[0093] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (e.g., an A1 policy).

[0094] Figure 3 An example of a wireless communication system 300 that supports uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 may implement one or more aspects of the wireless communication system 100. For example, the UE 115-b, the network entity 105-a, and the geographic coverage area 110-b may be as described in reference Figure 1 100 and 106. The wireless communication system 300 may support uplink SFN operation at the UE 115-b via one or more uplink channels in accordance with the unified TCI framework.

[0095] In some examples of wireless communication system 300, UE 115-b may communicate with one or more TRPs 305 (e.g., TRP 305-a and TRP 305-b) associated with one or more network entities 105. Figure 3 While TRP 305-a and TRP 305-b are illustrated as being associated with network entity 105-a, it should be understood that UE 115-b may communicate with multiple TRPs 305 associated with one or more network entities 105. That is, UE 115-b may communicate with respective TRPs 305 associated with separate devices (e.g., different network entities 105).

[0096] In single DCI multi-TRP operation or multi-DCI multi-TRP operation, UE 115-b may communicate with the first TRP 305-a and the second TRP 305-b using space division multiplexing, frequency division multiplexing, or time division multiplexing, or a combination thereof. The wireless communication system may support DCI repetition (e.g., across CORESETs associated with the first TRP 305-a and the second TRP 305-b), PUSCH and PUCCH repetition, downlink SFN configuration, or uplink SFN configuration. For example, in the downlink, UE 115-b may receive PDSCH or PDCCH messages according to the SFN configuration. For example, UE 115-b may receive the same downlink signal (e.g., PDSCH or PDCCH message) from the first TRP 305-a and the second TRP 305-b on different beams using different antenna panels at UE 115-b. In the uplink, UE 115-b may send PUSCH or PUCCH messages according to the SFN configuration. For example, UE 115-b may send the same uplink signal to the first TRP 305-a and the second TRP 305- on different beams using different antenna panels at UE 115-b.

[0097] In some examples, the wireless communication system 300 supports a unified TCI framework in which different unified TCI types can be used to improve channel utilization between wireless devices. For example, the wireless communication system may support multiple downlink and uplink TCI states that can facilitate communication between UE 115-b and TRP 305 associated with one or more network entities 105. For example, a first TCI type can be a joint TCI state to indicate a common beam for at least one downlink channel (e.g., PDCCH or PDSCH) or reference signal, and at least one uplink channel (e.g., PUCCH or PUSCH) or reference signal. Additionally or alternatively, a second TCI type can be a separate downlink TCI state to indicate a common beam for one or more downlink channels (e.g., PDCCH or PDSCH) or reference signals. Additionally or alternatively, a third TCI type can be a separate uplink TCI state to indicate a common beam for one or more uplink channels (e.g., PUCCH or PUSCH) or reference signals. In some examples, the TCI applicable to the uplink may be a joint TCI or an uplink TCI.

[0098] According to the techniques described herein, the wireless communication system 300 may implement an SFN scheme for the uplink of multi-TRP operation. For example, the network entity 105-a may send an uplink SFN scheme message 310 to the UE 115-b, which may configure the UE 115-b with one or more parameters according to the uplink SFN operation. For example, the uplink SFN scheme message 310 may include an RRC parameter (e.g., sfnPUCCH) that enables SFN-based PUCCH transmission. Additionally or alternatively, the uplink SFN scheme message 310 may include an RRC parameter (e.g., sfnPUSCH) that implements SFN-based PUSCH transmission. In some examples, the network entity 105-a may configure the UE 115-b with the sfnPUCCH parameter or the sfnPUSCH parameter. In some examples, the uplink SFN scheme message 310 may include an RRC parameter (e.g., sfnUL) that implements both SFN-based PUCCH and PUSCH transmission.

[0099] In some examples, where the SFN scheme is implemented at UE 115-b for PUSCH transmission, the network entity 105-a may schedule the PUSCH via DCI (e.g., DCI 0_0). In some examples, the SFN scheme may be applied to a PUSCH scheduled by DCI of any DCI format (e.g., scheduled by DCI 0_0, DCI 0_1, or DCI 0_2). In some other examples, the SFN scheme may be applied to a PUSCH that is not scheduled by DCI 0_0 (e.g., scheduled by DCI 0_1 or DCI 0_2). In some examples, the network entity 105-a may configure UE 115-b with one or more resource sets associated with an uplink pre-decoder indication according to an uplink SFN scheme. For example, UE 115-b may use one or two SRS resource sets configured at UE 115-b whose usage is set to "codebook", which may implement uplink SFN transmission according to codebook-based MIMO transmission. In some examples, UE 115-b may receive a resource set configuration message 315 to configure one or two SRS resource sets whose usage is configured as "codebook". Additionally or alternatively, UE 115-b may use one or two SRS resource sets whose usage is set to "non-codebook", which may implement uplink SFN transmission based on non-codebook based MIMO transmission. For example, UE 115-b may receive a resource set configuration message 315 that may include two SRS resource sets whose usage is set to "non-codebook", wherein the first SRS resource set may be associated with a first channel state information reference signal (CSI-RS) and the second SRS resource set may be associated with a second CSI-RS. For some other examples, UE 115-b may receive a resource set configuration message 315 that may include an SRS resource set whose usage is set to "non-codebook", wherein the SRS resource set may be associated with a CSI-RS.

[0100] In some cases, each SRS resource set in an SRS resource set may be associated with a corresponding predecoder indication field. For example, the resource set configuration message 315 may include a DCI (e.g., DCI 0_1 or DCI 0_2) or a configured grant (CG) configuration (e.g., for CG PUSCH) having two predecoder indication fields. Two predecoders may be applied with two uplink applicable TCIs in SFN transmissions for PUSCH. In the example of two SRS resource sets whose usage is set to "non-codebook" (e.g., for non-codebook-based uplink MIMO transmissions), the two predecoder indication fields may be examples of two SRS resource indicator (SRI) fields, each of which may indicate a predecoder associated with an SRS resource set. In the example of two SRS resource sets whose usage is set to "codebook" (e.g., for codebook-based uplink MIMO transmissions), the two precoder indication fields may be examples of two SRI fields, two transmit precoding matrix index (TPMI) fields, or a combination thereof, each of which indicates a precoder associated with an SRS resource set. In some aspects, the two precoder indications in a DCI or CG configuration may have the same number of spatial layers (i.e., the same rank) and share the same set of demodulation reference signal (DMRS) antenna ports indicated in the same DCI or CG configuration. In the example of a single SRS resource set whose usage is set to "codebook", there may be a single precoder indication field for the SRI, which indicates a precoder associated with the SRS resource set and may be applied with two uplink applicable TCIs in SFN transmissions for PUSCH. In the example of a single SRS resource set whose usage is set to "non-codebook", there may be a single precoder indication field for SRI and / or TPMI, where the field indicates the precoder associated with the SRS resource set and may be applied together with two uplink applicable TCIs in SFN transmissions for PUSCH.

[0101] In some cases, the UE 115-b may apply an uplink SFN to at least one uplink channel based on a flag associated with the uplink SFN scheme message 310. For example, as part of the uplink SFN scheme message 310, the UE 115-b may receive an associated scheduling CORESET, wherein the CORESET includes a flag indicating uplink SFN operation according to a unified TCI (e.g., a followUnifiedTCI flag). Therefore, if the flag of the CORESET that schedules the uplink channel indicates to follow the unified TCI (e.g., the followUnifiedTCI flag is configured), then when the uplink channel is scheduled by the DCI received in the CORESET, the UE 115-b may apply the uplink SFN transmission to the uplink channel. For example, if CORESET0 (CORESET zero) is configured with the followUnifiedTCI flag, then when the PUCCH or PUSCH is scheduled by the DCI received in CORESET0, the UE 115-b may apply the uplink SFN to the PUCCH or PUSCH. Additionally or alternatively, if CORESET0 is not configured with the followUnifiedTCI flag, then when PUCCH or PUSCH is scheduled by CORESET0, UE 115-b may not apply uplink SFN to PUCCH or PUSCH, even if SFN transmission is implemented as PUCCH or PUSCH transmission.

[0102] In an example in which UE 115-b implements SFN operation for at least one uplink channel, UE 115-b may receive a TCI code point indication 320 from network entity 105-a. For example, TCI code point indication 320 may indicate a TCI code point for use at UE 115-b, the TCI code point being associated with two uplink applicable TCI states (e.g., an uplink TCI state or a joint TCI state). In some examples, TCI code point indication 320 may include one or more messages. For example, UE 115-b may receive a TCI activation MAC-CE that activates multiple TCI code points configured at UE 115-b, and receive a DCI including a TCI indication field that may select a TCI code point from the multiple code points activated by the MAC-CE. Additionally or alternatively, UE 115-b may receive a TCI activation MAC-CE that activates a single TCI code point from multiple TCI code points configured at UE 115-b.

[0103] In an example in which UE 115-b determines not to apply SFN operation to an uplink channel, UE 115-b may select a TCI state from the selected TCI code point for use in the uplink channel. For example, a first TCI state of two TCI states in the indicated TCI code point may be selected for uplink transmissions that determine not to use SFN operation. In some aspects, when network entity 105-a has not configured the uplink channel for SFN operation, UE 115-b may determine not to apply SFN operation to the uplink channel. In some other aspects, when network entity 105-a has configured the uplink channel for SFN operation, UE 115-b may determine not to apply SFN operation to the uplink channel, but the uplink channel is dynamically indicated as not applying SFN operation, such as scheduling via fallback DCI (e.g., fallback DCI 0_0) or being scheduled as single TRP operation.

[0104] In some examples, UE 115-b may be implemented to switch between a non-SFN transmission scheme (e.g., for single TRP (sTRP) transmission) and a SFN transmission scheme (e.g., for multi-TRP transmission) based on a capability of UE 115-b (e.g., dynamic SFN capability). Thus, the number of uplink applicable TCI states associated with the selected TCI code point may determine whether UE 115-b operates according to a SFN transmission scheme or a non-SFN transmission scheme. For example, if the selected TCI code point includes a single uplink applicable TCI state, UE 115-b may operate according to a non-SFN transmission scheme. If the selected TCI code point includes two uplink applicable TCI states, UE 115-b may operate according to a SFN transmission scheme. In some aspects, if UE 115-b does not provide UE capability of "dynamicSFN", UE 115-b may be indicated by a TCI code point of two TCIs sent for SFN, or may be indicated by a TCI code point of a single TCI sent for non-SFN.

[0105] In some examples, UE 115-b may receive a TRP switch indication 325 from network entity 105-a. For example, when two uplink applicable TCIs in a TCI code point are indicated to UE 115-b, the TRP switch indication 325 may be a field included in the DCI that schedules the uplink channel. For example, if the TRP switch indication 325 in the DCI indicates the use of a first TCI state in the TCI code point, the UE 115-b may operate according to a non-SFN transmission scheme to transmit the uplink channel using the first TCI state. If the TRP switch indication 325 indicates the use of a second TCI state in the TCI code point, the UE 115-b may operate according to a non-SFN transmission scheme to transmit the uplink channel using the second TCI state. If the TRP switch indication 325 indicates the use of both the first TCI state and the second TCI state, the UE 115-b may operate according to an SFN transmission scheme to transmit the uplink channel using both TCI states. In some examples, the TRP switching indication 325 may be included in the scheduling DCI for the uplink channel used (e.g., DCI 0_1 or DCI 0_2 for scheduling PUSCH, DCI1_1 or DCI 1_2 for scheduling PUCCH).

[0106] UE 115-b may configure UE 115-a based on network entity 105-a using an uplink SFN transmission scheme, and UE 115-b may send one or more uplink messages 330 to the network entity according to the SFN configuration. For example, UE 115-b may concurrently send a first uplink message 330 to two TRPs 305-a using a first set of antenna elements at UE 115-b, and send the first uplink message to TRP 305-b using a second set of antenna elements at UE 115-b.

[0107] Figure 4 An example of a process flow 400 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, or a combination thereof. The process flow 400 includes a UE 115-c and a network entity 105-b, which can be as described in reference Figures 1 to 3105 and the corresponding examples of the UE 115 and the network entity 105 described above. The following alternative examples may be implemented, in which some of the steps are performed in a different order than the order described or are not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added. In addition, although the process flow 400 shows the process between a single UE 115 and a single network entity 105, it should be understood that these processes may occur between any number of network devices and network device types.

[0108] At 405, UE 115-c may receive control signaling from network entity 105-b that enables uplink communication with the network via a first TRP using a first set of antenna elements of UE 115-c and via a second TRP-c using a second set of antenna elements of UE 115 during the same set of time and frequency resources in accordance with the SFN configuration. In some examples, the first TRP and the second TRP may be associated with network entity 105-b, or may be associated with multiple respective network entities 105.

[0109] At 410, UE 115-c may send uplink communications to the network via the first TRP and the second TRP according to the SFN configuration.

[0110] Figure 5 An example of a process flow 500 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, or a combination thereof. The process flow 500 includes a UE 115-d and a network entity 105-c, which can be as described in reference Figures 1 to 3 105 and the corresponding examples of the UE 115 and the network entity 105 described above. The following alternative examples may be implemented, in which some of the steps are performed in a different order than the order described or are not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added. In addition, although the process flow 500 shows the process between a single UE 115 and a single network entity 105, it should be understood that these processes may occur between any number of network devices and network device types.

[0111] At 505, UE 115-d may receive control signaling from network entity 105-c that enables uplink communication with the network via a first TRP using a first set of antenna elements of UE 115-d and via a second TRP-d using a second set of antenna elements of UE 115 during the same set of time and frequency resources according to the SFN configuration. In some examples, the first TRP and the second TRP may be associated with network entity 105-c, or may be associated with respective network entities 105. In some examples, the control signaling may include a parameter set that enables uplink communication with the network via PUCCH or PUSCH. Accordingly, UE 115-d may send uplink communications to the network via PUCCH or PUSCH according to the parameter set.

[0112] In some examples, as part of receiving the control signaling, UE 115-d may also receive a CORESET associated with the control signaling, the control resource set including an indication for UE 115-d to send uplink communications to the network according to the SFN transmission scheme. Additionally or alternatively, the CORESET may include an indication for UE 115-d to send uplink communications to the network according to a transmission scheme different from the SFN transmission scheme.

[0113] At 510 , the UE 115 - d may select one or more SRS resource sets based on receiving control signaling that enables uplink communication with the network according to the SFN configuration.

[0114] In some examples, UE 115-d may select a first SRS resource set and a second SRS resource set configured at UE 115-d. Thus, at 515, UE 115-d may receive a DCI or a CG, the CG including a first resource indicator associated with the first SRS resource set and a second resource indicator associated with the second SRS resource set, wherein the first resource indicator and the second resource indicator may be SRI, TPMI, or a combination thereof.

[0115] In some examples, UE 115-d may receive a first reference signal (e.g., a first CSI-RS) indicating a first SRS resource set and a second reference signal (e.g., a second CSI-RS) indicating a second SRS resource set. Thus, at 515, UE 115-d may receive a DCI or a CG, the CG including a first resource indicator associated with the first SRS resource set and a second resource indicator associated with the second SRS resource set, wherein the first resource indicator and the second resource indicator may be SRIs.

[0116] In some examples, the first resource indicator and the second resource indicator may have the same indicator rank and may share the same set of DMRS ports.

[0117] At 520, the UE 115-d may receive one or more messages indicating a first TCI code point including one or more TCIs based on receiving control signaling that enables uplink communication with the network. For example, the UE 115-d may receive a MAC-CE that activates a set of TCI code points configured at the UE 115-d, and receive a DCI that includes a TCI that indicates a first TCI code point from the set of activated TCI code points. Additionally or alternatively, the UE 115-d may receive a MAC-CE that activates a first TCI code point in the set of TCI code points configured at the UE 115-d.

[0118] At 525, UE 115-d may receive an SFN switching indication that may indicate that UE 115-d is switching from a first SFN configuration to a second SFN configuration. For example, if the first TCI code point may include two or more TCIs, UE 115-d may receive a DCI including a TRP switching indication indicating the use of a first TCI associated with a first TRP or a second TRP. Thus, UE 115-d may send uplink communications to the network via the first TRP or the second TRP according to the SFN configuration, wherein the SFN configuration may include a non-SFN transmission scheme. Additionally or alternatively, UE 115-d may receive a DCI including a TRP switching indication indicating the use of two or more TCIs. Thus, UE 115-d may send uplink communications to the network via the first TRP and the second TRP according to the SFN configuration, wherein the SFN configuration may include a SFN transmission scheme.

[0119] At 530, UE 115-d may send uplink communications to the network via the first TRP and the second TRP according to the SFN configuration. For example, if the first TCI code point includes one TCI valid for uplink transmission, UE 115-d may send uplink communications to the network via the first TRP according to the SFN configuration, where the SFN configuration is a non-SFN transmission scheme. If the first TCI code point includes two or more TCIs valid for uplink transmission, UE 115-d may send uplink communications to the network via the first TRP and the second TRP according to the SFN configuration, where the SFN configuration is a SFN transmission scheme.

[0120] Figure 6A block diagram 600 of a device 605 supporting uplink SFN operations in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the 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 one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that can be executed by the one or more processors to enable the one or more processors to perform uplink SFN operations in the unified TCI framework discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink SFN operation in a unified TCI framework), user data, control information, or any combination thereof. 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.

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

[0123] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0124] In some examples, the communication manager 620, the receiver 610, the transmitter 615, 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, configured to or otherwise support components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0125] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0126] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or integrate in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0127] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support components for receiving control signaling that enables uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The communication manager 620 may be configured to or otherwise support components for sending uplink communications to the network via the first transmit and receive point and the second transmit and receive point according to the SFN configuration.

[0128] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for more efficiently utilizing communication resources by configuring uplink SFN operations in a TCI framework.

[0129] Figure 7 A block diagram 700 of a device 705 supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0130] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to uplink SFN operation in a unified TCI framework), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0131] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to uplink SFN operation in a unified TCI framework), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0132] The device 705 or its various components may be examples of components for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 720 may include a control signal receiving component 725, an uplink SFN transmitting component 730, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0133] According to examples as disclosed herein, the communication manager 720 can support wireless communications at the UE. The control signal receiving component 725 can be configured to or otherwise support components for receiving control signaling that enables uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The uplink SFN transmitting component 730 can be configured to or otherwise support components for transmitting uplink communications to the network via the first transmit and receive point and the second transmit and receive point according to the SFN configuration.

[0134] In some cases, the control signal receiving component 725 and the uplink SFN transmitting component 730 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal receiving component 725 and the uplink SFN transmitting component 730 discussed herein. The transceiver processor may be co-located with and / or in communication with (e.g., directing the operation of) a transceiver of a device. The radio processor may be co-located with and / or in communication with (e.g., directing the operation of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of a device. The transmitter processor may be co-located with and / or in communication with (e.g., directing the operation of) a transmitter of a device. The receiver processor may be co-located with and / or in communication with (e.g., directing the operation of) a receiver of a device. "

[0135] Figure 8A block diagram 800 of a communication manager 820 supporting uplink SFN operations in a unified TCI framework is shown in accordance with one or more aspects of the present disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of means for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 820 may include a control signal receiving component 825, an uplink SFN transmitting component 830, a resource set selecting component 835, an uplink transmitting component 840, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0136] According to examples as disclosed herein, the communication manager 820 can support wireless communications at the UE. The control signal receiving component 825 can be configured to or otherwise support components for receiving control signaling that enables uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The uplink SFN transmitting component 830 can be configured to or otherwise support components for transmitting uplink communications to the network via the first transmit and receive point and the second transmit and receive point according to the SFN configuration.

[0137] In some examples, to support receiving control signaling, control signal receiving component 825 can be configured or otherwise support means for receiving a parameter set that enables uplink communication with a network via a physical uplink control channel or a physical uplink shared channel. In some examples, to support receiving control signaling, uplink SFN transmitting component 830 can be configured or otherwise support means for transmitting uplink communication to a network via a physical uplink control channel or a physical uplink shared channel in accordance with the parameter set.

[0138] In some examples, resource set selection component 835 may be configured or otherwise support components for selecting one or more sets of sounding reference signals based on receiving control signaling that enables uplink communication with the network according to the SFN configuration.

[0139] In some examples, to support selection of one or more sounding reference signal sets, resource set selection component 835 may be configured to or otherwise support components for selecting a first sounding reference signal set and a second sounding reference signal set configured at the UE. In some examples, to support selection of one or more sounding reference signal sets, control signal reception component 825 may be configured to or otherwise support components for receiving downlink control information or a configured grant, the configured grant including a first resource indicator associated with a first sounding reference signal set and a second resource indicator associated with a second sounding reference signal set; wherein the first resource indicator and the second resource indicator are sounding reference signal resource indicators, transmit precoding matrix indices, or a combination thereof.

[0140] In some examples, the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

[0141] In some examples, to support selection of one or more sounding reference signal sets, control signal receiving component 825 may be configured to or otherwise support means for receiving a first reference signal indicating a first sounding reference signal set and a second reference signal indicating a second sounding reference signal set. In some examples, to support selection of one or more sounding reference signal sets, control signal receiving component 825 may be configured to or otherwise support means for receiving a grant of downlink control information or a configuration, the grant of the configuration including a first resource indicator associated with the first sounding reference signal set and a second resource indicator associated with the second sounding reference signal set; wherein the first resource indicator and the second resource indicator are sounding reference signal resource indicators.

[0142] In some examples, the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

[0143] In some examples, to support receiving control signaling, the control signal receiving component 825 may be configured to or otherwise support components for receiving a control resource set associated with the control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to the SFN transmission scheme.

[0144] In some examples, to support receiving control signaling, the control signal receiving component 825 may be configured to or otherwise support components for receiving a control resource set associated with the control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to a transmission scheme that is different from the SFN transmission scheme.

[0145] In some examples, the control signal receiving component 825 may be configured as or otherwise support components for receiving one or more messages indicating a first transmit configuration indicator code point including one or more transmit configuration indicators based on receiving control signaling that enables uplink communication with a network.

[0146] In some examples, to support receiving one or more messages, control signal receiving component 825 may be configured or otherwise support means for receiving a medium access control-control element that activates a set of multiple transmit configuration indicator code points configured at the UE. In some examples, to support receiving one or more messages, control signal receiving component 825 may be configured or otherwise support means for receiving downlink control information that includes a transmit configuration indicator indicating a first transmit configuration indicator code point from the set of multiple transmit configuration indicator code points that are activated.

[0147] In some examples, to support receiving one or more messages, the control signal receiving component 825 may be configured as or otherwise support components for receiving a medium access control-control element that activates a single transmit configuration indicator code point from a set of multiple transmit configuration indicator code points configured at the UE.

[0148] In some examples, the first transmit configuration indicator code point includes a transmit configuration indicator, and the uplink transmit component 840 may be configured as or otherwise support components for transmitting uplink communications to the network via the first transmit and receive points in accordance with an SFN configuration, wherein the SFN configuration is a non-SFN transmission scheme.

[0149] In some examples, the first transmit configuration indicator code point includes two or more transmit configuration indicators, and the uplink SFN transmit component 830 may be configured as or otherwise support components for transmitting uplink communications to a network via a first transmit and receive point and a second transmit and receive point in accordance with a SFN configuration, wherein the SFN configuration is a SFN transmission scheme.

[0150] In some examples, the first transmission configuration indicator code point includes two or more transmission configuration indicators, and the control signal receiving component 825 can be configured to or otherwise support components for receiving downlink control information, the downlink control information including a transmission and reception point switching indication indicating the use of the first transmission configuration indicator associated with the first transmission and reception point. In some examples, the first transmission configuration indicator code point includes two or more transmission configuration indicators, and the uplink transmission component 840 can be configured to or otherwise support components for transmitting uplink communications to the network via the first transmission and reception point according to the SFN configuration, wherein the SFN configuration includes a non-SFN transmission scheme.

[0151] In some examples, the first transmission configuration indicator code point includes two or more transmission configuration indicators, and the control signal receiving component 825 can be configured to or otherwise support components for receiving downlink control information, the downlink control information including a transmission and reception point switching indication indicating the use of the two or more transmission configuration indicators. In some examples, the first transmission configuration indicator code point includes two or more transmission configuration indicators, and the uplink SFN transmission component 830 can be configured to or otherwise support components for transmitting uplink communications to the network via the first transmission and reception point and the second transmission and reception point according to the SFN configuration, wherein the SFN configuration includes a SFN transmission scheme.

[0152] In some cases, the control signal receiving component 825, the uplink SFN transmitting component 830, the resource set selecting component 835, and the uplink transmitting component 840 can each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor can be coupled to a memory and execute instructions stored in the memory, which enable the processor to perform or facilitate the features of the control signal receiving component 825, the uplink SFN transmitting component 830, the resource set selecting component 835, and the uplink transmitting component 840 discussed herein.

[0153] Fig. 9 A diagram of a system 900 including a device 905 supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein or include a component of these devices. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

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

[0155] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be able to send or receive multiple wireless transmissions concurrently. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and for demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or any components thereof as described herein.

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

[0157] The processor 940 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 940 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 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) so that the device 905 performs various functions (e.g., various functions or tasks that support uplink SFN operations in a unified TCI framework). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0158] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support components for receiving control signaling that enables uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The communication manager 920 may be configured to or otherwise support components for sending uplink communications to the network via the first transmit and receive point and the second transmit and receive point according to the SFN configuration.

[0159] By including or configuring the communication manager 920 according to examples as described herein, the device 905 may support techniques for more efficiently utilizing communication resources and improving coordination between devices by configuring uplink SFN operations in a TCI framework.

[0160] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that may be executed by the processor 940 to cause the device 905 to perform various aspects of uplink SFN operations in the unified TCI framework as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0161] Fig.10 A block diagram 1000 of a device 1005 supporting uplink SFN operations in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that can be executed by the one or more processors to enable the one or more processors to perform the SFN features in the TCI framework discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

[0162] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units), which is associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). 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.

[0163] The transmitter 1015 may provide a component 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 such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units), which are associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). 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.

[0164] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0165] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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).

[0166] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

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

[0168] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The communication manager 1020 may be configured to or otherwise support components for receiving uplink communications of the network via the first transmit and receive point, the second transmit and receive point, or a combination thereof according to the SFN configuration.

[0169] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled with the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques for more efficiently utilizing communication resources by configuring uplink SFN operations in a TCI framework.

[0170] Fig.11 A block diagram 1100 of a device 1105 supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0172] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to the modem.

[0173] The device 1105 or its various components may be examples of components for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 1120 may include a control signal sending component 1125, an uplink SFN receiving component 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 1110, the transmitter 1115, or both, or otherwise cooperate with them. For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0174] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The control signal sending component 1125 may be configured to or otherwise support components for sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The uplink SFN sending component 1130 may be configured to or otherwise support components for receiving uplink communications of the network via the first transmit and receive point, the second transmit and receive point, or a combination thereof according to the SFN configuration.

[0175] In some cases, the control signal sending component 1125 and the uplink SFN receiving component 1130 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal sending component 1125 and the uplink SFN receiving component 1130 discussed herein. The transceiver processor may be co-located with and / or communicate with (e.g., direct the operation of) a transceiver of a device. The radio processor may be co-located with and / or communicate with (e.g., direct the operation of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of a device. The transmitter processor may be co-located with and / or communicate with (e.g., direct the operation of) a transmitter of a device. The receiver processor may be co-located with and / or communicate with (e.g., direct the operation of) a receiver of a device.

[0176] Fig.12 A block diagram 1200 of a communication manager 1220 supporting uplink SFN operations in a unified TCI framework according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of the communication manager 1020, the communication manager 1120, or aspects of both as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of uplink SFN operations in a unified TCI framework as described herein. For example, the communication manager 1220 may include a control signal sending component 1225, an uplink SFN receiving component 1230, 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.

[0177] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The control signal sending component 1225 may be configured to or otherwise support components for sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The uplink SFN sending component 1230 may be configured to or otherwise support components for receiving uplink communications of the network via the first transmit and receive point, the second transmit and receive point, or a combination thereof according to the SFN configuration.

[0178] In some examples, to support sending control signaling, control signal sending component 1225 can be configured or otherwise support means for sending a parameter set that enables uplink communication with the network via a physical uplink control channel or a physical uplink shared channel. In some examples, to support sending control signaling, uplink SFN receiving component 1230 can be configured or otherwise support means for receiving uplink communication via a physical uplink control channel or a physical uplink shared channel according to the parameter set.

[0179] In some examples, to support sending control signaling, control signal sending component 1225 may be configured as or otherwise support components for sending a control resource set associated with the control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to the SFN transmission scheme.

[0180] In some examples, to support sending control signaling, the control signal sending component 1225 may be configured as or otherwise support components for sending a control resource set associated with the control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to a transmission scheme that is different from the SFN transmission scheme.

[0181] In some examples, control signal sending component 1225 may be configured as or otherwise support components for sending one or more messages indicating a first transmit configuration indicator code point including one or more transmit configuration indicators based on receiving control signaling that enables uplink communication with a network.

[0182] In some cases, the control signal transmission component 1225 and the uplink SFN reception component 1230 can each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor can be coupled to a memory and execute instructions stored in the memory, which enable the processor to perform or facilitate the features of the control signal transmission component 1225 and the uplink SFN reception component 1230 discussed herein.

[0183] Fig.13 A diagram of a system 1300 including a device 1305 supporting uplink SFN operations in a unified TCI framework according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 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 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. 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 1340).

[0184] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., through one or more antennas 1315, through a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and demodulating the signal. Where applicable, transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be 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).

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

[0186] The processor 1335 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) so that the device 1305 performs various functions (e.g., various functions or tasks that support uplink SFN operations in a unified TCI framework). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 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 1330) to perform the functions of device 1305.

[0187] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 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 1305 or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system, where one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

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

[0189] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during the same set of time and frequency resources according to the SFN configuration. The communication manager 1320 may be configured to or otherwise support components for receiving uplink communications of the network via the first transmit and receive point, the second transmit and receive point, or a combination thereof according to the SFN configuration.

[0190] By including or configuring the communication manager 1320 according to examples as described herein, the device 1305 may support techniques for more efficiently utilizing communication resources and improving coordination between devices by configuring uplink SFN operations in a TCI framework.

[0191] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions that may be executed by the processor 1335 to cause the device 1305 to perform various aspects of uplink SFN operations in the unified TCI framework as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0192] Fig.14 A flowchart of a method 1400 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. 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 herein. Figures 1 to 9 The UE 115 may be used to perform the functions. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions.

[0193] At 1405, the method may include receiving control signaling that enables uplink communication with the network using a first set of antenna elements of the UE via a first transmission and reception point and using a second set of antenna elements of the UE via a second transmission and reception point during the same set of time and frequency resources according to the SFN configuration. 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 Figure 8 The control signal receiving component 825 is used to execute.

[0194] At 1410, the method may include: sending an uplink communication to a network via a first transmission and reception point and a second transmission and reception point according to the SFN configuration. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The uplink SFN sending component 830 is used for execution.

[0195] Fig.15 A flowchart of a method 1500 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. 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 herein. Figures 1 to 9 The UE 115 may be used to perform the functions. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions.

[0196] At 1505, the method may include receiving control signaling that enables uplink communication with the network using a first set of antenna elements of the UE via a first transmission and reception point and using a second set of antenna elements of the UE via a second transmission and reception point during the same set of time and frequency resources according to the SFN configuration. 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 8 The control signal receiving component 825 is used to execute.

[0197] At 1510, the method may include receiving a control resource set associated with control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to the SFN transmission scheme. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The control signal receiving component 825 is used to execute.

[0198] At 1515, the method may include: sending an uplink communication to the network via the first transmission and reception point and the second transmission and reception point according to the SFN configuration. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The uplink SFN sending component 830 is used for execution.

[0199] Fig.16 A flowchart of a method 1600 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. 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 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control a functional element of the network entity to perform the functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the functions.

[0200] At 1605, the method may include: sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmission and reception point and using a second set of antenna elements of the UE via a second transmission and reception point during the same set of time and frequency resources according to the SFN configuration. 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 Fig.12 The control signal sending component 1225 is executed.

[0201] At 1610, the method may include receiving uplink communications of the network via the first transmission and reception point, the second transmission and reception point, or a combination thereof according to the SFN configuration. 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.12 The uplink SFN receiving component 1230 is used for execution.

[0202] Fig.17 A flowchart of a method 1700 for supporting uplink SFN operation in a unified TCI framework according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13In some examples, the network entity may execute an instruction set to control a functional element of the network entity to perform the functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the functions.

[0203] At 1705, the method may include: sending control signaling that enables the UE to perform uplink communications with the network using a first set of antenna elements of the UE via a first transmission and reception point and using a second set of antenna elements of the UE via a second transmission and reception point during the same set of time and frequency resources according to the SFN configuration. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference Fig.12 The control signal sending component 1225 is executed.

[0204] At 1710, the method may include: sending a control resource set associated with the control signaling, the control resource set including an indication for the UE to send uplink communications to the network according to the SFN transmission scheme. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The control signal sending component 1225 is executed.

[0205] At 1715, the method may include receiving uplink communications of the network via the first transmission and reception point, the second transmission and reception point, or a combination thereof according to the SFN configuration. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.12 The uplink SFN receiving component 1230 is used for execution.

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

[0207] Aspect 1: A method for wireless communication at a UE, comprising: receiving control signaling, the control signaling enabling uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during the same set of time and frequency resources according to an SFN configuration; and sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration.

[0208] Aspect 2: The method according to Aspect 1, wherein receiving the control signaling further comprises: receiving a parameter set that enables the uplink communication with the network via PUCCH or PUSCH; and sending the uplink communication to the network via the PUCCH or the PUSCH according to the parameter set.

[0209] Aspect 3: The method according to any one of aspects 1 to 2 also includes: selecting one or more SRS sets based at least in part on receiving the control signaling that enables the uplink communication with the network according to the SFN configuration.

[0210] Aspect 4: A method according to Aspect 3, wherein selecting the one or more SRS sets includes: selecting a first SRS set and a second SRS set configured at the UE; and receiving a DCI or a configured grant, wherein the configured grant includes a first resource indicator associated with the first SRS set and a second resource indicator associated with the second SRS set; wherein the first resource indicator and the second resource indicator are SRI, TPMI, or a combination thereof.

[0211] Aspect 5: The method according to aspect 4, wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same demodulation reference signal port set.

[0212] Aspect 6: A method according to any one of Aspects 3 to 5, wherein selecting the one or more SRS sets further includes: receiving a first reference signal indicating a first SRS set and a second reference signal indicating a second SRS set; and receiving a DCI or a configured grant, wherein the configured grant includes a first resource indicator associated with the first SRS set and a second resource indicator associated with the second SRS set; wherein the first resource indicator and the second resource indicator are SRIs.

[0213] Aspect 7: The method according to aspect 6, wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same demodulation reference signal port set.

[0214] Aspect 8: According to the method according to any one of aspects 1 to 7, receiving the control signaling further includes: receiving a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to a SFN transmission scheme.

[0215] Aspect 9: According to the method according to any one of Aspects 1 to 8, receiving the control signaling also includes: receiving a CORESET associated with the control signaling, the CORESET including an indication for the UE to send the uplink communication to the network according to a transmission scheme different from the SFN transmission scheme.

[0216] Aspect 10: The method according to any one of Aspects 1 to 9 also includes: receiving one or more messages indicating a first TCI code point including one or more TCIs based at least in part on receiving the control signaling that enables the uplink communication with the network.

[0217] Aspect 11: A method according to Aspect 10, wherein receiving the one or more messages further comprises: receiving a MAC-CE that activates multiple TCI code points configured at the UE; and receiving a DCI including a TCI, wherein the TCI indicates the first TCI code point from the activated multiple TCI code points.

[0218] Aspect 12: The method according to any one of aspects 10 to 11, wherein receiving the one or more messages further comprises: receiving a MAC-CE activating a single TCI code point among a plurality of TCI code points configured at the UE.

[0219] Aspect 13: A method according to any one of Aspects 10 to 12, wherein the first TCI code point includes a TCI, and the method further includes: sending the uplink communication to the network via the first TRP according to the SFN configuration, wherein the SFN configuration is a non-SFN transmission scheme.

[0220] Aspect 14: A method according to any one of Aspects 10 to 13, wherein the first TCI code point includes two or more TCIs, and the method further includes: sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration, wherein the SFN configuration is a SFN sending scheme.

[0221] Aspect 15: A method according to any one of Aspects 10 to 14, wherein the first TCI coding point includes two or more TCIs, and the method further includes: receiving a DCI including a TRP switching indication indicating the use of a first TCI associated with the first TRP; and sending the uplink communication to the network via the first TRP according to the SFN configuration, wherein the SFN configuration includes a non-SFN transmission scheme.

[0222] Aspect 16: A method according to any one of Aspects 10 to 15, wherein the first TCI coding point includes two or more TCIs, and the method further includes: receiving a DCI including a TRP switching indication indicating the use of the two or more TCIs; and sending the uplink communication to the network via the first TRP and the second TRP according to the SFN configuration, wherein the SFN configuration includes a SFN sending scheme.

[0223] Aspect 17: A method for performing wireless communications at a network entity, comprising: sending signaling, the control signaling enabling a UE to perform uplink communication with a network using a first set of antenna elements of the UE via a first TRP and using a second set of antenna elements of the UE via a second TRP during the same set of time and frequency resources according to an SFN configuration; and receiving the uplink communication of the network via the first TRP, the second TRP, or a combination thereof according to the SFN configuration.

[0224] Aspect 18: The method according to Aspect 17, wherein sending the control signaling further comprises: sending a parameter set that enables the uplink communication with the network via PUCCH or PUSCH; and receiving the uplink communication via the PUCCH or the PUSCH according to the parameter set.

[0225] Aspect 19: The method according to any one of aspects 17 to 18, wherein sending the control signaling further comprises: sending a CORESET associated with the control signaling, the CORESET comprising an indication for the UE to send the uplink communication to the network according to a SFN transmission scheme.

[0226] Aspect 20: A method according to any one of Aspects 17 to 19, wherein sending the control signaling further comprises: sending a CORESET associated with the control signaling, the CORESET comprising an indication for the UE to send the uplink communication to the network according to a transmission scheme different from an SFN transmission scheme.

[0227] Aspect 21: The method according to any one of Aspects 17 to 20 also includes: sending one or more messages indicating a first TCI code point including one or more TCIs based at least in part on receiving the control signaling that enables the uplink communication with the network.

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

[0229] Aspect 23: An apparatus for wireless communication at a UE, comprising: at least one component for performing a method according to any one of aspects 1 to 16.

[0230] Aspect 24: 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 16.

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

[0232] Aspect 26: An apparatus for wireless communication at a network entity, comprising: at least one component for performing the method according to any one of aspects 17 to 21.

[0233] Aspect 27: A non-transitory computer-readable medium storing a 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 17 to 21.

[0234] 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 that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

[0238] 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 via 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 implementing the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0239] Computer-readable media include both non-transient computer storage media and communication media, including any medium that promotes the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, disk storage or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor.In addition, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable media. 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.

[0240] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on 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."

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

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

[0243] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these 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 described examples.

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during a same set of time and frequency resources in accordance with a single frequency network configuration; as well as The uplink communication is transmitted to the network via the first transmission and reception point and the second transmission and reception point in accordance with the single frequency network configuration.

2. The apparatus of claim 1 , wherein the instructions for receiving the control signaling are further executable by the processor to cause the apparatus to: receiving a set of parameters enabling the uplink communication with the network via a physical uplink control channel or a physical uplink shared channel; and The uplink communication is sent to the network via the physical uplink control channel or the physical uplink shared channel according to the set of parameters.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: One or more sounding reference signal sets are selected based at least in part on receiving the control signaling that enables the uplink communication with the network according to the single frequency network configuration.

4. The apparatus of claim 3, wherein the instructions for selecting the one or more sounding reference signal sets are executable by the processor to cause the apparatus to: selecting a first sounding reference signal set and a second sounding reference signal set configured at the UE; as well as receiving downlink control information or a configured grant, the configured grant comprising a first resource indicator associated with the first sounding reference signal set and a second resource indicator associated with the second sounding reference signal set; The first resource indicator and the second resource indicator are a sounding reference signal resource indicator, a transmission precoding matrix index or a combination thereof. 5 . The apparatus of claim 4 , wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

6. The apparatus of claim 3, wherein the instructions for selecting the one or more sounding reference signal sets are further executable by the processor to cause the apparatus to: receiving a first reference signal indicative of a first sounding reference signal set and a second reference signal indicative of a second sounding reference signal set; as well as receiving downlink control information or a configured grant, the configured grant comprising a first resource indicator associated with the first sounding reference signal set and a second resource indicator associated with the second sounding reference signal set; The first resource indicator and the second resource indicator are sounding reference signal resource indicators. 7 . The apparatus of claim 6 , wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

8. The apparatus of claim 1, wherein the instructions for receiving the control signaling are further executable by the processor to cause the apparatus to: A control resource set associated with the control signaling is received, the control resource set including an indication for the UE to transmit the uplink communication to the network according to a single frequency network transmission scheme.

9. The apparatus of claim 1, wherein the instructions for receiving the control signaling are further executable by the processor to cause the apparatus to: A control resource set associated with the control signaling is received, the control resource set including an indication for the UE to transmit the uplink communication to the network according to a transmission scheme different from a single frequency network transmission scheme.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: One or more messages indicating a first transmit configuration indicator code point including one or more transmit configuration indicators are received based at least in part on receiving the control signaling enabling the uplink communication with the network.

11. The apparatus of claim 10, wherein the instructions for receiving the one or more messages are further executable by the processor to cause the apparatus to: receiving a medium access control-control element activating a plurality of transmit configuration indicator code points configured at the UE; and Downlink control information including a transmit configuration indicator is received, the transmit configuration indicator indicating the first transmit configuration indicator code point from the activated plurality of transmit configuration indicator code points.

12. The apparatus of claim 10, wherein the instructions for receiving the one or more messages are further executable by the processor to cause the apparatus to: A medium access control-control element is received that activates a single transmission configuration indicator code point among a plurality of transmission configuration indicator code points configured at the UE.

13. The apparatus of claim 10, wherein the first transmit configuration indicator code point comprises a transmit configuration indicator, and the instructions are further executable by the processor to cause the apparatus to: The uplink communication is transmitted to the network via the first transmission and reception point according to the single frequency network configuration, wherein the single frequency network configuration is a non-single frequency network transmission scheme.

14. The apparatus of claim 10, wherein the first transmit configuration indicator code point comprises two or more transmit configuration indicators, and the instructions are further executable by the processor to cause the apparatus to: The uplink communication is transmitted to the network via the first transmission and reception point and the second transmission and reception point according to the single frequency network configuration, wherein the single frequency network configuration is a single frequency network transmission scheme.

15. The apparatus of claim 10, wherein the first transmit configuration indicator code point comprises two or more transmit configuration indicators, and the instructions are further executable by the processor to cause the apparatus to: receiving downlink control information including a transmission and reception point switching indication, the transmission and reception point switching indication indicating use of a first transmission configuration indicator associated with the first transmission and reception point; and The uplink communication is transmitted to the network via the first transmission and reception point in accordance with the single frequency network configuration, wherein the single frequency network configuration includes a non-single frequency network transmission scheme.

16. The apparatus of claim 10, wherein the first transmit configuration indicator code point comprises two or more transmit configuration indicators, and the instructions are further executable by the processor to cause the apparatus to: receiving downlink control information including a transmission and reception point switching indication indicating use of the two or more transmission configuration indicators; and The uplink communication is transmitted to the network via the first transmission and reception point and the second transmission and reception point according to the single frequency network configuration, wherein the single frequency network configuration includes a single frequency network transmission scheme.

17. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting control signaling that enables a user equipment (UE) to perform uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during a same set of time and frequency resources in accordance with a single frequency network configuration; as well as The uplink communications of the network are received via the first transmit and receive points, the second transmit and receive points, or a combination thereof, according to the single frequency network configuration.

18. The apparatus of claim 17, wherein the instructions for sending the control signaling are further executable by the processor to cause the apparatus to: sending a set of parameters enabling the uplink communication with the network via a physical uplink control channel or a physical uplink shared channel; and The uplink communication is received via the physical uplink control channel or the physical uplink shared channel according to the parameter set.

19. The apparatus of claim 17, wherein the instructions for sending the control signaling are further executable by the processor to cause the apparatus to: A control resource set associated with control signaling is transmitted, the control resource set including an indication for the UE to transmit the uplink communication to the network according to a single frequency network transmission scheme.

20. The apparatus of claim 17, wherein the instructions for sending the control signaling are further executable by the processor to cause the apparatus to: A control resource set associated with the control signaling is transmitted, the control resource set including an indication for the UE to transmit the uplink communication to the network according to a transmission scheme different from a single frequency network transmission scheme.

21. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: One or more messages indicating a first transmit configuration indicator code point including one or more transmit configuration indicators are transmitted based at least in part on receiving the control signaling enabling the uplink communication with the network.

22. A method for wireless communication at a user equipment (UE), comprising: receiving control signaling that enables uplink communication with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during a same set of time and frequency resources in accordance with a single frequency network configuration; as well as The uplink communication is transmitted to the network via the first transmission and reception point and the second transmission and reception point in accordance with the single frequency network configuration.

23. The method of claim 22, wherein receiving the control signaling further comprises: receiving a set of parameters enabling the uplink communication with the network via a physical uplink control channel or a physical uplink shared channel; as well as The uplink communication is sent to the network via the physical uplink control channel or the physical uplink shared channel according to the set of parameters.

24. The method of claim 22, further comprising: One or more sounding reference signal sets are selected based at least in part on receiving the control signaling that enables the uplink communication with the network according to the single frequency network configuration.

25. The method of claim 24, wherein selecting the one or more sounding reference signal sets comprises: selecting a first sounding reference signal set and a second sounding reference signal set configured at the UE; as well as receiving downlink control information or a configured grant, the configured grant comprising a first resource indicator associated with the first sounding reference signal set and a second resource indicator associated with the second sounding reference signal set; The first resource indicator and the second resource indicator are a sounding reference signal resource indicator, a transmission precoding matrix index or a combination thereof.

26. The method of claim 25, wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

27. The method of claim 24, wherein selecting the one or more sounding reference signal sets further comprises: receiving a first reference signal indicative of a first sounding reference signal set and a second reference signal indicative of a second sounding reference signal set; as well as receiving downlink control information or a configured grant, the configured grant comprising a first resource indicator associated with the first sounding reference signal set and a second resource indicator associated with the second sounding reference signal set; The first resource indicator and the second resource indicator are sounding reference signal resource indicators.

28. The method of claim 27, wherein the first resource indicator and the second resource indicator have the same indicator rank and share the same set of demodulation reference signal ports.

29. A method for wireless communication at a network entity, comprising: transmitting control signaling that enables a user equipment (UE) to perform uplink communications with a network using a first set of antenna elements of the UE via a first transmit and receive point and using a second set of antenna elements of the UE via a second transmit and receive point during a same set of time and frequency resources in accordance with a single frequency network configuration; as well as The uplink communications of the network are received via the first transmit and receive points, the second transmit and receive points, or a combination thereof, according to the single frequency network configuration.

30. The method of claim 29, wherein sending the control signaling further comprises: sending a set of parameters enabling the uplink communication with the network via a physical uplink control channel or a physical uplink shared channel; as well as The uplink communication is received via the physical uplink control channel or the physical uplink shared channel according to the parameter set.

Images