Unified transmit configuration indication determination for single frequency networks

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may communicate with a network via two or more transmit receive points (TRPs). The described techniques involve determining which unified transmit configuration indication (TCI) state is applied to communications on a channel configured for single frequency network (SFN) operation based on one or more conditions. For example, a UE may receive control signaling identifying a configuration for the UE to communicate with a first TRP and a second TRP using an SFN operation for at least one channel. The UE may receive control signaling indicating a unified TCI state for the at least one channel. The UE may determine whether to apply the indicated unified TCI state to communications (e.g., transmission or reception of signals) on the channel according to the SFN operation configuration based on one or more conditions.

Description

Technical Field

[0001] The following relates to wireless communications, including unified transmit configuration indication determination for single frequency networks. Background Art

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

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting unified transmit configuration indication (TCI) determination for single frequency networks (SFNs). A user equipment (UE) may communicate with a network via two or more transmit receive points (TRPs). The UE may be configured to communicate via an SFN configuration. Some wireless communication systems may apply a unified TCI state. The described technology relates to determining which unified TCI state to apply to communications on a channel configured for SFN operation based on one or more conditions. For example, a UE may receive control signaling that identifies a configuration that the UE uses SFN operation for at least one channel to communicate with a first TRP and a second TRP. The UE may receive control signaling indicating a unified TCI state that identifies, at the UE, beams applicable to more than one channel including at least one channel configured according to SFN operation. The UE may determine whether to apply the indicated unified TCI state (e.g., or a default beam, e.g., as opposed to a unified TCI state) to communications (e.g., transmission of a signal or reception of a signal) on a channel configured according to SFN operation based on one or more conditions.

[0004] A method for wireless communication at a UE is described. The method may include: receiving first control signaling that identifies a configuration of the UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP; receiving second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicating on the at least one channel according to at least one beam based on determining whether to apply the unified TCI state to the at least one channel according to one or more conditions.

[0005] An apparatus for wireless communication is described. The apparatus may include: a memory; a transceiver; and at least one processor of a UE, the at least one processor being coupled to the memory and the transceiver. The at least one processor may be configured to: receive a first control signaling identifying a configuration of the UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP; receive a second control signaling indicating that the UE will use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicate on the at least one channel according to at least one beam based on determining whether to apply the unified TCI state to the at least one channel according to one or more conditions.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving a first control signaling that identifies a configuration of the UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP; a component for receiving a second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and a component for communicating on the at least one channel according to at least one beam based on determining whether to apply the unified TCI state to the at least one channel according to one or more conditions.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: receive a first control signaling that identifies a configuration of the UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP; receive a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicate on the at least one channel according to at least one beam based on determining whether to apply the unified TCI state to the at least one channel according to one or more conditions.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include a time threshold, and communicating on the at least one channel may include operations, features, components, or instructions for communicating on the at least one channel according to the unified TCI state based on the time for communicating on the at least one channel satisfying the time threshold.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include a time threshold, and communicating on the at least one channel may include operations, features, components, or instructions for communicating on the at least one channel according to a default beam based at least in part on the time for communicating on the at least one channel satisfying the time threshold.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein, wherein the one or more conditions include whether SFN operation is configured at the UE for a downlink control channel, may also include operations, features, components, or instructions for determining whether to apply the unified TCI state to the at least one channel based on configuring the SFN operation for the downlink control channel.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein (wherein the one or more conditions include whether SFN operation is configured at the UE for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel) may also include operations, features, components, or instructions for determining whether to apply the unified TCI state to the at least one channel based on configuring the SFN operation for the at least one of the downlink shared channel, the uplink control channel, or the uplink shared channel.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein, wherein the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE, may also include operations, features, components, or instructions for determining whether to apply the unified TCI state to the at least one channel based on the one of the intra-cell beam management or the inter-cell beam management that can be configured at the UE.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein, wherein the one or more conditions include that a single unified TCI state or one of the two unified TCI states has been indicated to the UE, may also include operations, features, components, or instructions for: receiving a control message indicating the single unified TCI state or the one of the two unified TCI states; and determining whether to apply the unified TCI state to the at least one channel based on indicating the single unified TCI state or the one of the two unified TCI states to the UE.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein, wherein the one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams, may also include operations, features, components, or instructions for determining whether to apply the unified TCI state to the at least one channel based on whether the UE supports the single default beam or the UE supports the set of multiple default beams.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a third control signaling indicating that the UE is enabled to use a set of multiple default beams; and determining to apply the set of multiple default beams to the at least one channel based on the UE having received the third control signaling indicating that the UE is enabled to use the set of multiple default beams.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control signaling includes a downlink control information message.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the at least one channel includes a physical downlink control channel, a physical downlink shared channel, a physical uplink control channel, a physical uplink shared channel, or any combination thereof.

[0018] A method for wireless communication at a network entity is described. The method may include: outputting a first control signaling that identifies a configuration for a UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP associated with the network entity; outputting a second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicating on the at least one channel according to at least one beam based on determining whether the UE applies the unified TCI state to the at least one channel according to one or more conditions.

[0019] An apparatus for wireless communication is described. The apparatus may include: a memory; and at least one processor of a network entity, the at least one processor being coupled to the memory. The at least one processor may be configured to: output a first control signaling identifying a configuration for a UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP associated with the network entity; output a second control signaling indicating that the UE will use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicate on the at least one channel according to at least one beam based on determining whether the UE applies the unified TCI state to the at least one channel according to one or more conditions.

[0020] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for outputting a first control signaling that identifies a configuration for a UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP associated with the network entity; a component for outputting a second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and a component for communicating on the at least one channel according to at least one beam based on determining whether the UE applies the unified TCI state to the at least one channel according to one or more conditions.

[0021] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions that can be executed by a processor to: output a first control signaling that identifies a configuration for a UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP associated with the network entity; output a second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including the at least one channel; and communicate on the at least one channel according to at least one beam based on determining whether the UE applies the unified TCI state to the at least one channel according to one or more conditions.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include a time threshold, and communicating on the at least one channel may include operations, features, components, or instructions for communicating on the at least one channel according to the unified TCI state based on the time for communicating on the at least one channel satisfying the time threshold.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include a time threshold, and communicating on the at least one channel may include operations, features, components, or instructions for communicating on the at least one channel according to a default beam based at least in part on the time for communicating on the at least one channel satisfying the time threshold.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include whether SFN operation can be configured at the UE for a downlink control channel.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include whether SFN operation is configurable at the UE for at least one of the downlink shared channels.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein, wherein the one or more conditions include that a single unified TCI state or one of the two unified TCI states has been indicated to the UE, may also include operations, features, components, or instructions for outputting a control message indicating the single unified TCI state or one of the two unified TCI states.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more conditions include whether the UE can support a single default beam or whether the UE can support a set of multiple default beams.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a third control signaling to enable the UE to use a set of multiple default beams, wherein the UE determines to apply the set of multiple default beams to the at least one channel based on the UE having received the third control signaling that enables the UE to use the set of multiple default beams. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 An example of a wireless communication system supporting unified transmission configuration indication (TCI) determination for a single frequency network (SFN) in accordance with one or more aspects of the present disclosure is illustrated.

[0031] Figure 2 An example of a network architecture supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is illustrated.

[0032] Figure 3 An example of a wireless communication system supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 4 An example of a timing diagram supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 5 An example of a timing diagram supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 6 An example of a process flow supporting unified TCI determination for SFN in accordance with one or more aspects of the present disclosure is illustrated.

[0036] Figure 7 and Figure 8 A block diagram of an apparatus supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown.

[0037] Fig. 9 A block diagram of a communications manager supporting unified TCI determination for SFNs according to one or more aspects of the present disclosure is shown.

[0038] Fig.10 A diagram of a system including a device supporting unified TCI determination for SFNs according to one or more aspects of the present disclosure is shown.

[0039] Fig.11 and Fig.12 A block diagram of an apparatus supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown.

[0040] Fig.13 A block diagram of a communications manager supporting unified TCI determination for SFNs according to one or more aspects of the present disclosure is shown.

[0041] Fig.14 A diagram of a system including a device supporting unified TCI determination for SFNs according to one or more aspects of the present disclosure is shown.

[0042] Figure 15 to Figure 16 A flow chart illustrating a method for supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0043] In some wireless communication systems, a user equipment (UE) may communicate with a network via two or more transmit receive points (TRPs). In some cases, the UE may be configured to communicate via a single frequency network (SFN) configuration. In an SFN configuration, the UE may be configured to use the same frequency and / or time resources to receive the same downlink transmission (e.g., a physical downlink control channel (PDCCH) transmission, a physical downlink shared channel (PDSCH) transmission, or a non-periodic channel state information (CSI) reference signal (CSI-RS)) or to send the same uplink transmission (e.g., a physical uplink control channel (PUCCH) transmission or a physical uplink shared channel (PUSCH) transmission). In a downlink SFN configuration, the UE may receive the same signal from multiple TRPs using different beams. In an uplink SFN configuration, the UE may send the same signal to multiple TRPs (e.g., mTRPs) using different beams for each of the multiple TRPs. Each TRP may be associated with a corresponding transmit configuration indication (TCI) state. Some wireless communication systems may apply a unified TCI state. A unified TCI state refers to a TCI state indicating a common beam for more than one downlink or uplink channel or reference signal. Currently, there may be no defined conditions for determining when a unified TCI state is applied to SFN operation.

[0044] Various aspects of the present disclosure relate to determining which unified TCI state is applied to communications on a channel configured for SFN operation based on one or more conditions. For example, a UE may receive control signaling that identifies the configuration of the UE to use SFN operation for at least one channel (e.g., PDCCH, PDSCH, PUCCH, or PUSCH) to communicate with a first TRP and a second TRP. The UE may receive control signaling indicating a unified TCI state that identifies at the UE a beam applicable to more than one channel including at least one channel configured according to SFN operation. The UE may determine whether to apply the indicated unified TCI state (e.g., or a default beam) to communications (e.g., transmission or reception of signals) on a channel configured according to SFN operation based on one or more conditions. For example, one or more conditions may include whether a time threshold between an indication of a unified TCI state and a communication satisfies a threshold (e.g., so as to switch a beam to a beam indicated by a unified TCI state). Another example condition may include whether the SFN operation is configured for PDCCH, PDSCH, PUCCH, or PUSCH. Another example condition may include the number of unified TCI states indicated to the UE (e.g., one or two). Another example condition may include the number of default beams supported by the UE (e.g., one or two).

[0045] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to unified TCI determination for SFN.

[0046] Figure 1 An example of a wireless communication system 100 supporting unified TCI determination for SFN 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.

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

[0048] 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 both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0049] 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 yet 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 a network node. 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 the second node.

[0050] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the 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 .

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

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

[0053] 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 DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) 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 an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

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

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

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

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

[0058] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support unified TCI determination for SFN, 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).

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

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

[0061] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any 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).

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

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

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

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

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

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

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

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

[0070] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. Physical control channels and physical data channels may be multiplexed, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) 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 multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

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

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

[0074] 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 respective coverage areas 110 using the same or different radio access technologies.

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

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

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

[0078] 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, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

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

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

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

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

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

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

[0085] 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) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0086] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), 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.

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

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

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

[0090] 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 reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (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., multi-panel codebook, linear combination codebook, 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).

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

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

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

[0094] 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. A first type of TCI state (e.g., type 1) may include a joint TCI state for indicating 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 PDCCH, a UE-specific PDSCH, a UE-specific PUCCH, and a UE-specific PUSCH). A second type of TCI state (e.g., type 2) may include a downlink TCI state for indicating 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). A third type of TCI state (e.g., type 3) may include an uplink TCI state for indicating 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 to UE 115 multiple downlink or uplink states for multiple TRPs.

[0095] In some cases, UE 115 may be configured to send uplink communications via a SFN configuration. In some cases, the UE may be configured to communicate via a SFN configuration. In a SFN configuration, the UE may be configured to receive the same downlink transmission (e.g., PDCCH transmission, PDSCH transmission, or non-periodic CSI-RS) or send the same uplink transmission (e.g., PUCCH transmission or PUSCH transmission) using the same frequency and / or time resources. In a SFN configuration, the UE may receive the same signal from multiple TRPs using different beams via different antenna panels at UE 115 and using the same set of time and frequency resources. In an uplink SFN configuration, the UE 115 may send the same uplink signal to two or more TRPs using different beams via different antenna panels at UE 115 and using the same set of time and frequency resources. Example applications for uplink SFN configurations may include customer premises equipment, fixed wireless broadband, or industrial equipment. In some cases, to facilitate simultaneous multi-panel uplink transmissions to achieve higher uplink throughput and reliability (e.g., focusing on FR2 and multiple TRPs), uplink precoding indications for PUSCH may be specified, where no new codebook is introduced for simultaneous multi-panel transmissions. In some cases, considering multi-TRP operation based on single downlink control information (DCI) and multiple DCIs, 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, to facilitate simultaneous multi-panel uplink transmissions to achieve higher uplink throughput and reliability (e.g., focusing on FR2 and multiple TRPs), uplink beam indications for PUCCH or PUSCH may be specified, where considering multi-TRP operation based on single DCI and multiple DCIs, a unified TCI framework may be assumed. For the case of multi-TRP operation based on multiple DCIs, in some examples, only PUSCH+PUSCH or PUCCH+PUCCH may be transmitted in the same component carrier across two panels. In some cases, timing advance for uplink multiple DCI for multi-TRP operation may be specified. In some cases, power control for uplink single DCI for multi-TRP operation may be applied.

[0096] The UE 115 may determine which unified TCI state to apply to communications on a channel configured for SFN operation based on one or more conditions. For example, the UE may receive control signaling that identifies the configuration of the UE to use SFN operation for at least one channel (e.g., PDCCH, PDSCH, PUCCH, or PUSCH) to communicate with a first TRP and a second TRP. The UE may receive control signaling indicating a unified TCI state that identifies, at the UE, beams applicable to more than one channel including at least one channel configured according to SFN operation. The UE may determine whether to apply the indicated unified TCI state (e.g., or a default beam) to communications (e.g., transmission or reception of signals) on a channel configured according to SFN operation based on one or more conditions. For example, one or more conditions may include whether a time threshold between an indication of a unified TCI state and communication satisfies a threshold (e.g., so as to switch the beam to a beam indicated by the unified TCI state). Another example condition may include whether the SFN operation is configured for PDCCH, PDSCH, PUCCH, or PUSCH. Another example condition may include the number of unified TCI states indicated to the UE (e.g., one or two). Another example condition may include the number of default beams supported by the UE (e.g., one or two).

[0097] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting unified TCI determination for SFN 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 the core network 130-a via a backhaul communication link 120-a, or indirectly 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 RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0098] Each network entity 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, the network entity 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.

[0099] 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 with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process 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.

[0100] 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 divisions, 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 with an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0101] 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 this 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 the corresponding DU 165-a. In some examples, this configuration may enable DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0102] 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) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). 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 with components configured according to a 4G RAN (e.g., via an O1 interface). 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.

[0103] The non-RT RIC 175-a may be configured to include logic functions that implement 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 implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0104] 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. 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 (such as an A1 policy).

[0105] Figure 3 An example of a timing diagram 300 supporting unified TCI determination for SFN in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 300 may be implemented by or may implement aspects of the wireless communication system 100.

[0106] UE 115 may be configured with multiple CORESETs. For example, UE 115 may be configured with CORESET A 310-a, CORESET B 310-b, CORESET C 310-c, and CORESET D 310-d. CORESET B 310-b and CORESET C 310-c may be configured for SFN operation. For example, each of CORESET B 310-b and CORESET C 310-c may be configured with two TCI states to support SFN operation.

[0107] At time t0, UE 115 may receive a PDCCH transmission via one of CORESETs 310 that schedules another transmission. For example, the PDCCH may schedule PDSCH or aperiodic CSI 320 or PDSCH, PUCCH, or PUSCH 330. Time offset 325 may be a threshold time for UE 115 to decode the scheduling DCI in the PDCCH. The scheduling DCI may indicate a unified TCI state to apply to PDSCH or aperiodic CSI 320 or PDSCH, PUCCH, or PUSCH 330. Time offset 325. PDSCH or aperiodic CSI 320 may be within time offset 325, and PDSCH, PUCCH, or PUSCH 330 may be outside time offset 325. Therefore, UE 115 may receive PDSCH or aperiodic CSI 320 using a default beam. The UE 115 may use a beam indicated by a unified TCI state indicated in a scheduling DCI for PDSCH, PUCCH, or PUSCH 330.

[0108] Figure 4 An example of a timing diagram 400 supporting unified TCI determination for SFN in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 300 may be implemented by or may implement aspects of the wireless communication system 100.

[0109] UE 115 may be configured with multiple CORESETs. For example, UE 115 may be configured with CORESET A 410-a, CORESET B 410-b, CORESET C 410-c, and CORESET D 410-d. CORESET A 410-a and CORESET B 410-b may be configured for SFN operation. For example, each of CORESET A 410-a and CORESET B 410-b may be configured with two TCI states to support SFN operation.

[0110] The first control signaling 405 (e.g., an RRC message or a MAC control element (MAC-CE)) may activate a default TCI state (e.g., a default beam). The beam indication DCI 415 may indicate a unified TCI state for one or more CORESETs in the CORESET 410. The UE 115 may send an acknowledgment (ACK) 420 for the beam indication DCI 415. Some CORESETs (e.g., CORESET D 410-d) may not follow the unified TCI state. For example, the DCI may schedule a PDSCH 425-a in CORESET D 410-d, and the UE 115 may apply a default beam (e.g., indicated in the control signaling 405) for the PDSCH 425-a in CORESET D 410-d. The DCI may schedule PDSCH 425 - b in CORESET C 410 - c , and UE 115 - may apply the beam associated with the unified TCI state indicated in the beam indication DCI 415 for PDSCH 425 - b .

[0111] Figure 5 An example of a wireless communication system 500 that supports unified TCI determination for SFN according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 500 can implement aspects of the wireless communication system 100. The wireless communication system 500 can include a UE 115-b, which can be an example of a UE 115 as described herein. The wireless communication system 500 can include a network entity 105-a, which can be an example of a network entity 105 as described herein.

[0112] UE 115-a may operate in a multi-TRP mode with a first TRP 505-a and a second TRP 505-b. In some cases, the first TRP 505-a and the second TRP 505-b may be located at the same network entity 105-a. In some cases, the first TRP 505-a and the second TRP 505-b may be located at different network entities.

[0113] UE 115-b may be able to perform simultaneous communications with a first TRP 505-a and a second TRP 505-b (e.g., using the same set of time resources or the same set of frequency resources or both, but different spatial resources). UE 115-b may communicate with the first TRP 505-a using communication link 125-b. UE 115-b may communicate with the second TRP 505-b using communication link 125-c. Communication link 125-b and communication link 125-c may include bidirectional links that implement both uplink and downlink communications. For example, UE 115-b may send an uplink transmission (such as an uplink control signal or an uplink data signal) to the first TRP 505-a using communication link 125-b, and the first TRP 505-a may send a downlink transmission (such as a downlink control signal or a downlink data signal) to UE 115-b using communication link 125-b. UE 115-b may use communication link 125-c to send an uplink transmission (such as an uplink control signal or an uplink data signal) to the second TRP 505-b, and the second TRP 505-b may use communication link 125-c to send a downlink transmission (such as a downlink control signal or a downlink data signal) to UE 115-b. In some examples, different TRPs (e.g., a first TRP 505-a and a second TRP 505-b) may have different TRP identifiers (IDs). In some examples, different TRPs may be identified by association with other IDs such as a CORESET pool index, a closed loop index, a TCI ID, a TCI group ID, or a sounding reference signal resource set ID.

[0114] In single DCI multi-TRP operation or multi-DCI multi-TRP operation, UE 115-b may communicate with the first TRP 505-a and the second TRP 505-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 the CORESETs associated with the first TRP 505-a and the second TRP 505-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 505-a and the second TRP 505-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 505-a and the second TRP 505-b on different beams using different antenna panels at UE 115-b.

[0115] UE 115-b may receive first control signaling 510, which identifies a configuration for UE 115-b to use SFN communication for at least one channel to communicate with a first TRP 505-a and a second TRP 505-b. UE 115-b may receive second control signaling 515, which indicates that UE 115-b is to use a unified TCI state, which identifies that a single beam at UE 115-b is applicable to a set of multiple channels including at least one channel (e.g., PDCCH, PDSCH, PUCCH, or PUSCH). The UE may communicate 520 on at least one channel according to at least one beam based on determining whether to apply the unified TCI state to at least one channel according to one or more conditions.

[0116] Therefore, for multi-TRP communication, UE 115-b may determine one or more conditions, such as whether the SFN is configured for PDCCH, whether the SFN is configured for PDSCH, whether the SFN is configured between cells or within cells, whether a single TCI or multiple TCIs are configured for CORESET, whether the UE supports a single or two default beams, or whether the RRC parameter "enableTwoDefaultTCI" is configured.

[0117] Table 1 shows the scheduling offset (e.g., as referenced Figure 32 and 3. Example scenarios in which the time offset between the DCI and the scheduled PDSCH or CSI-RS described above is less than a threshold, where the UE 115-b may determine one or more default beams for receiving the scheduled PDSCH or CSI-RS. Table 2 shows the scheduling offset (e.g., as shown in reference Figure 3 An example scenario in which a UE 115-b may determine one or more beams for receiving scheduled PDSCH, PUSCH, and / or PUCCH when a SFN is configured by RRC parameters for a PDCCH / CORESET and two unified TCI states are indicated, the associated PDCCH / CORESET operates in SFN operation, otherwise the PDCCH / CORESET does not operate in SFN operation (e.g., when SFN is configured for a PDCCH / CORESET and only one unified TCI is indicated for the PDCCH / CORESET, the associated PDCCH / CORESET does not operate according to SFN operation).

[0118] Table 1

[0119]

[0120] Table 2

[0121]

[0122] In Scenario 1, a first example case (eg, Case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving synchronization signal block (SSB) as a root quasi-co-located (QCL) resource signal).

[0123] A first example sub-case (e.g., case 1.1) of the first example case of scenario 1 may involve indicating a single unified TCI state, where the unified TCI state may be indicated by a TCI indication DCI and / or a TCI activation MAC-CE. In case 1.1, if UE 115-b supports a single default beam (e.g., case 1.1.1), then in the first example (option 1), UE 115-b may use the indicated unified TCI state as the default beam for PDSCH or non-periodic CSI-RS. In case 1.1.1, in the second example (option 2), UE 115-b may use one TCI state for one CORESET. For example, UE 115-b may use a first TCI state (e.g., option 2.0) of one CORESET (e.g., a CORESET with a lowest CORESET identifier (ID)). In another example, UE 115-b may use one of the TCI states of one of the SFN CORESETs (e.g., in an SFN CORESET that does not follow the indicated unified TCI state) (e.g., option 2.1). In another example scenario, the UE may use a TCI state of a non-SFN CORESET (e.g., option 2.2). In scenario 1.1.1, in a third example (option 3), UE 115-b may use the first TCI state of the lowest CORESET ID monitored in the latest timeslot as the default beam.

[0124] In case 1.1, if UE 115-b supports two default beams (e.g., case 1.1.2), in a first example (e.g., option 1), UE 115-b may use one TCI code point with two TCI states (e.g., the lowest TCI code point). In case 1.1.2, in a second example (e.g., option 2), UE 115-b may use two TCI states of one SFN CORESET in the SFN CORESET (e.g., in those SFN CORESETs that do not follow the indicated unified TCI state). In case 1.1.2, in a third example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may use one TCI code point with two TCI states (case 1.1.2 option 1), or may use two TCI states of one SFNCORESET in the SFN CORESET (case 1.1.2 option 2). If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 1.1.1.

[0125] A second example sub-case (e.g., case 1.2) of the first example case of scenario 1 may involve indicating two unified TCI states, where the two unified TCI states may be indicated by a TCI indication DCI and / or a TCI activation MAC-CE. In case 1.2, if UE 115-b supports a single default beam (e.g., case 1.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state as the default beam for PDSCH or non-periodic CSI-RS. In case 1.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI state for one CORESET (e.g., as in case 1.1.1 option 2).

[0126] In case 1.2, if UE 115-b supports two default beams (e.g., case 1.2.2), then in a first example (e.g., option 1), UE 115-b may use two indicated TCI states. In case 1.2.2, in some examples (options 1-3), UE 115-b may use the same options as in options 1-3 of case 1.2.1.

[0127] In Scenario 1, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the TCIs used has a non-serving cell SSB as a root QCL resource signal).

[0128] The first example sub-case (e.g., case 2.1) of the second example case of scenario 1 may involve indicating a single unified TCI state. In case 2.1, if UE 115-b supports a single default beam (e.g., case 2.1.1), then in the first example (option 1), UE 115-b may use the same option as option 3 of case 1.1.1. In case 2.1.1, in the second example (e.g., option 2), UE 115-b may use one TCI for one CORESET (e.g., the same as option 2 of case 1.1.1).

[0129] In case 2.1, if UE 115-b supports two default beams (e.g., case 2.1.2), in a first example (e.g., option 1), UE 115-b may use one TCI code point with 2 TCI states, and at least one TCI state has the serving cell SSB as the root QCL resource signal (e.g., the lowest TCI code point). In case 2.1.2, in a second example (e.g., option 2), UE 115-b may use two TCI states of one SFN CORESET in the SFN CORESET (e.g., in those SFN CORESETs that do not follow the indicated unified TCI state and at least one TCI state has the serving cell SSB as the root QCL source signal). In case 2.1.2, in a third example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may use option 1 or option 2 of case 2.1.2. If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 2.1.1.

[0130] A second example sub-case (e.g., case 2.2) of the second example case of scenario 1 may involve indicating two unified TCI states. In case 2.2, if UE 115-b supports a single default beam (e.g., case 2.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state associated with a serving cell SSB as a default beam for PDSCH or aperiodic CSI-RS. For example, UE 115-b may select a first TCI state among the TCI states associated with a serving cell SSB. In case 2.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI associated with a serving cell SSB of one CORESET. For example, UE 115-b may use a first TCI state associated with a serving cell SSB of one CORESET (e.g., a CORESET with a lowest CORESET identifier (ID)) (e.g., option 2.0). In another example, UE 115-b may use a TCI state associated with a serving cell SSB in one of the SFN CORESETs (e.g., in a CORESET that does not follow the indicated unified TCI state) (e.g., option 2.1). In another example case, the UE may use a TCI state associated with a serving cell SSB on a non-SFN CORESET (e.g., option 2.2).

[0131] In case 2.1, if UE 115-b supports two default beams (e.g., case 2.2.2), then in one example (option 0), if at least one indicated TCI state is associated with a serving cell SSB, UE 115-b may use two indicated TCI states. In case 2.2.2, in another example (e.g., option 1), UE 115-b may use one TCI code point with two TCI states, wherein at least one of the TCI states is associated with a serving cell SSB (e.g., the lowest TCI code point). In case 2.2.2, in another example (e.g., option 2), UE 115-b may use two TCI states of one SFN CORESET in a SFNCORESET, wherein at least one of the TCI states is associated with a serving cell SSB (e.g., in those CORESETs that do not follow the indicated unified TCI state). In case 2.2.2, in another example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may select option 0, option 1, or option 2 of case 2.2.2. If enableTwoDefaultTCI is not configured, UE 115-b may use the option in case 2.2.1.

[0132] In Scenario 2, a first example case (eg, Case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving cell SSB as the root QCL resource signal).

[0133] The first example sub-case (e.g., case 1.1) of the first example case of scenario 2 may involve indicating a single unified TCI state. In case 1.1, if UE 115-b supports a single default beam (e.g., case 1.1.1), then in the first example (option 1), UE 115-b may use the indicated unified TCI state as the default beam for PDSCH or non-periodic CSI-RS. In case 1.1.1, in a second example (option 2), UE 115-b may use one TCI state of one CORESET. For example, UE 115-b may use a first TCI state of one CORESET (e.g., a CORESET with the lowest CORESET identifier (ID)) (e.g., option 2.0). In another example, UE 115-b may use one TCI state of a TCI state of a SFNCORESET in a SFN CORESET (e.g., in a CORESET that does not follow the indicated unified TCI state) (e.g., option 2.1). In another example case, the UE may use TCI state in one non-SFN CORESET (e.g., option 2.2). In case 1.1.1, in a third example (option 3), UE 115-b may use the first TCI state of the lowest CORESET ID monitored in the latest timeslot as the default beam.

[0134] A second example subcase (e.g., case 1.2) of the first example case of scenario 2 may involve indicating two unified TCI states. In case 1.2, if UE 115-b supports a single default beam (e.g., case 1.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state as the default beam for PDSCH or aperiodic CSI-RS. In case 1.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI state for one CORESET (e.g., as in case 1.1.1 option 2).

[0135] In Scenario 2, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the TCIs used has a non-serving cell SSB as a root QCL resource signal).

[0136] The first example subcase (e.g., case 2.1) of the second example case of scenario 2 may involve indicating a single unified TCI state. In case 2.1, if UE 115-b supports a single default beam (e.g., case 2.1.1), then in the first example (option 1), UE 115-b may use the same option as option 3 of case 1.1.1. In case 2.1.1, in the second example (e.g., option 2), UE 115-b may use one TCI for one CORESET (e.g., the same as option 2 of case 1.1.1).

[0137] A second example sub-case (e.g., case 2.2) of the second example case of scenario 2 may involve indicating two unified TCI states. In case 2.2, if UE 115-b supports a single default beam (e.g., case 2.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state associated with a serving cell SSB as a default beam for PDSCH or aperiodic CSI-RS. For example, UE 115-b may select a first TCI state among the TCI states associated with a serving cell SSB. In case 2.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI associated with a serving cell SSB of one CORESET. For example, UE 115-b may use a first TCI state associated with a serving cell SSB of one CORESET (e.g., a CORESET with a lowest CORESET identifier (ID)) (e.g., option 2.0). In another example, UE 115-b may use a TCI state associated with a serving cell SSB in one of the SFN CORESETs (e.g., in a CORESET that does not follow the indicated unified TCI state) (e.g., option 2.1). In another example case, the UE may use a TCI state associated with a serving cell SSB on a non-SFN CORESET (e.g., option 2.2).

[0138] In scenario 3, a first example case (eg, case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving cell SSB as the root quasi-co-located QCL resource signal).

[0139] The first example sub-case of the first example case of scenario 3 (e.g., case 1.1) may involve indicating a single unified TCI state. In case 1.1, if UE 115-b supports a single default beam (e.g., case 1.1.1), then in the first example (option 1), UE 115-b may use the indicated unified TCI state as the default beam for PDSCH or non-periodic CSI-RS. In case 1.1.1, in the second example (option 2), UE 115-b may use one TCI state of one CORESET. For example, UE 115-b may use the first TCI state of one CORESET (e.g., the CORESET with the lowest CORESET identifier (ID)) (e.g., option 2.0). In case 1.1.1, in the third example (option 3), UE 115-b may use the first TCI state of the lowest CORESET ID in the latest time slot as the default beam.

[0140] In case 1.1, if UE 115-b supports two default beams (e.g., case 1.1.2), in a first example (e.g., option 1), UE 115-b may use one TCI code point (e.g., the lowest TCI code point) with two TCI states. In case 1.1.2, in another example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may use one TCI code point with two TCI states (case 1.1.2 option 1). If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 1.1.1.

[0141] A second example subcase (e.g., case 1.2) of the first example case of scenario 3 may involve indicating two unified TCI states. In case 1.2, if UE 115-b supports a single default beam (e.g., case 1.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state as the default beam for PDSCH or aperiodic CSI-RS. In case 1.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI state for one CORESET (e.g., as in case 1.1.1 option 2).

[0142] In case 1.2, if UE 115-b supports two default beams (e.g., case 1.2.2), then in a first example (e.g., option 1), UE 115-b may use two indicated TCI states. In case 1.2.2, in some examples (options 1-3), UE 115-b may use the same options as in options 1-3 of case 1.2.1.

[0143] In Scenario 3, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the used TCIs has a non-serving cell SSB as a root QCL resource signal).

[0144] The first example sub-case (e.g., case 2.1) of the second example case of scenario 3 may involve indicating a single unified TCI state. In case 2.1, if UE 115-b supports a single default beam (e.g., case 2.1.1), then in the first example (option 1), UE 115-b may use the same option as option 3 of case 1.1.1. In case 2.1.1, in the second example (e.g., option 2), UE 115-b may use one TCI for one CORESET (e.g., the same as option 2 of case 1.1.1).

[0145] In case 2.1, if UE 115-b supports two default beams (e.g., case 2.1.2), in a first example (e.g., option 1), UE 115-b may use one TCI code point with 2 TCI states, and at least one TCI state has a serving cell SSB as a root QCL resource signal (e.g., the lowest TCI code point). In case 2.1.2, in another example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may use option 1 of case 2.1.2. If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 2.1.1.

[0146] A second example sub-case (e.g., case 2.2) of the second example case of scenario 3 may involve indicating two unified TCI states. In case 2.2, if UE 115-b supports a single default beam (e.g., case 2.2.1), then in the first example (e.g., option 1), UE 115-b may use one indicated TCI state associated with a serving cell SSB as a default beam for PDSCH or aperiodic CSI-RS. For example, UE 115-b may select a first TCI state among the TCI states associated with a serving cell SSB. In case 2.2.1, in the second example (e.g., option 2), UE 115-b may use one TCI associated with a serving cell SSB of one CORESET. For example, UE 115-b may use a first TCI state associated with a serving cell SSB of one CORESET (e.g., a CORESET with a lowest CORESET identifier (ID)) (e.g., option 2.0). In another example case, UE 115-b may use the TCI state associated with the serving cell SSB on a non-SFN CORESET (e.g., option 2.2). In case 2.2.1, in a third example (e.g., option 3), UE 115-b may use a default beam (e.g., the first TCI state of the lowest CORESET ID in the latest timeslot).

[0147] In case 2.1, if UE 115-b supports two default beams (e.g., case 2.2.2), in one example (option 0), if at least one indicated TCI state is associated with a serving cell SSB, UE 115-b may use two indicated TCI states. In case 2.2.2, in another example (e.g., option 1), UE 115-b may use one TCI code point with two TCI states, wherein at least one of the TCI states is associated with a serving cell SSB (e.g., the lowest TCI code point). In case 2.2.2, in another example (e.g., option 3), the default beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may be option 0 or option 1 of case 2.2.2. If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 2.2.1.

[0148] In Scenario 4, a first example case (eg, Case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving cell SSB as the root QCL resource signal).

[0149] The first example sub-case (e.g., case 1.1) of the first example case of scenario 4 may involve indicating a single unified TCI state through DCI or in a single TCI code point activated by MAC-CE. In case 1.1, if UE 115-b supports a single beam (e.g., case 1.1.1), then in the first example (option 1), UE 115-b may use the indicated unified TCI state. In case 1.1.1, in the third example (option 3), if the indicated TCI state is not followed, UE 115-b may use the TCI state of the scheduling CORESET.

[0150] In case 1.1, if UE 115-b supports two beams (e.g., case 1.1.2), then in the example (e.g., option 2), if the indicated TCI state is not followed and has two TCI states, UE 115-b can use two TCI states of one CORESET in the scheduling CORESET.

[0151] A second example sub-case (e.g., case 1.2) of the first example case of scenario 4 may involve indicating two unified TCI states through DCI or in a single TCI code point activated by MAC-CE. In case 1.2, if UE 115-b supports a single beam (e.g., case 1.2.1), then in a first example (e.g., option 0), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 1.2.1, in another example (e.g., option 3), if the indicated TCI state is not followed, UE 115-b may use the first TCI state of the scheduling CORESET.

[0152] In case 1.2, if UE 115-b supports two beams (e.g., case 1.2.2), in one example (e.g., option 0), UE 115-b may use two indicated unified TCI states. In case 1.2.2, in another example (e.g., option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 1.2.2, in another example (e.g., option 1), if the indicated TCI is not followed and has two TCI states, UE 115-b may use two TCI states of the scheduling CORESET.

[0153] In Scenario 4, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the used TCIs has a non-serving cell SSB as a root QCL resource signal).

[0154] A first example subcase (e.g., case 2.1) of the second example case of scenario 4 may involve indicating a single unified TCI state (e.g., via DCI or in a single TCI code point activated by a MAC-CE). In case 2.1, if UE 115-b supports a single beam (e.g., case 2.1.1), then in an example (e.g., option 0), the UE may indicate a single beam from the scheduling DCI. In case 2.1.1, in another example (option 1), UE 115-b may use the same option as option 3 of case 1.1.1.

[0155] In case 2.1, if UE 115-b supports two beams (e.g., case 2.1.2), in an example (e.g., option 0), UE 115-b may use two indicated TCIs from the CORESET that schedules the DCI. In case 2.1.2, in a second example (e.g., option 2), if the indicated TCI state is not followed and there are two TCI states, UE 115-b may use the two TCI states of the scheduling CORESET.

[0156] A second example subcase (e.g., case 2.2) of the second example case of scenario 4 may involve indicating (e.g., via DCI or in a single TCI code point activated by a MAC-CE) two unified TCI states. In case 2.2, if UE 115-b supports a single beam (e.g., case 2.2.1), then in one example (e.g., option 0), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 2.2.1, in another example (e.g., option 3), if the indicated TCI state is not followed, UE 115-b may use the first TCI state of the scheduling CORESET.

[0157] In case 2.1, if UE 115-b supports two beams (e.g., case 2.2.2), in one example (option 0), UE 115-b may use two indicated TCI states. In case 2.2.2, in another example (e.g., option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 2.2.2, in another example (e.g., option 2), if the indicated TCI states are not followed and there are only two TCI states, UE 115-b may use two TCI states of the scheduling CORESET.

[0158] In scenario 5, a first example case (eg, case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving cell SSB as the root QCL resource signal).

[0159] The first example sub-case (e.g., case 1.1) of the first example case of scenario 5 may involve indicating a single unified TCI state through DCI or in a single TCI code point activated by MAC-CE. In case 1.1, if UE 115-b supports a single beam (e.g., case 1.1.1), in the first example (option 1), UE 115-b may use the indicated unified TCI state. In case 1.1.1, in another example (e.g., option 0A), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 1.1.1, in a third example (option 3), if the indicated TCI state is not followed, UE 115-b may use the TCI state of the scheduling CORESET.

[0160] A second example sub-case (e.g., case 1.2) of the first example case of scenario 5 may involve indicating two unified TCI states through DCI or in a single TCI code point activated by MAC-CE. In case 1.2, if UE 115-b supports a single beam (e.g., case 1.2.1), in the first example, UE 115-b may use one indicated TCI state (e.g., the first TCI state). In case 1.2.1, in another example (e.g., option 0A), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 1.2.1, in another example (e.g., option 3), if the indicated TCI state is not followed, UE 115-b may use the first TCI state of the scheduling CORESET.

[0161] In case 1.2, if UE 115-b supports two beams (e.g., case 1.2.2), in one example (e.g., option 0), UE 115-b may use two indicated unified TCI states. In case 1.2.2, in another example (e.g., option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 1.2.2, in another example (e.g., option 1), if the indicated TCI is not followed and has two TCI states, UE 115-b may use two TCI states of the scheduling CORESET.

[0162] In Scenario 5, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the TCIs used has a non-serving cell SSB as a root QCL resource signal).

[0163] A first example subcase (e.g., case 2.1) of the second example case of scenario 5 may involve indicating (e.g., via DCI or in a single TCI code point activated by MAC-CE) a unified TCI state. In case 2.1, if UE 115-b supports a single beam (e.g., case 2.1.1), then in an example (e.g., option 0), the UE may indicate a single beam from the scheduling DCI. In case 2.1.1, in another example (option 1), UE 115-b may use the same option as option 3 of case 1.1.1.

[0164] A second example sub-case (e.g., case 2.2) of the second example case of scenario 5 may involve indicating (e.g., via DCI or in a single TCI code point activated by a MAC-CE) two unified TCI states. In case 2.2, if UE 115-b supports a single beam (e.g., case 2.2.1), in one example, UE 115-b may use one indicated TCI state. In case 2.2.1, in another example (e.g., option 0A), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 2.2.1, in another example (e.g., option 3), if the indicated TCI state is not followed, UE 115-b may use the first TCI state of the scheduling CORESET.

[0165] In scenario 6, a first example case (eg, case 1) may involve intra-cell beam management (eg, all used TCI states have the same serving cell SSB as the root QCL resource signal).

[0166] The first example sub-case (e.g., case 1.1) of the first example case of scenario 6 may involve indicating a single unified TCI state through DCI or in a single TCI code point activated by MAC-CE. In case 1.1, if UE 115-b supports a single beam (e.g., case 1.1.1), then in the first example (option 1), UE 115-b may use the indicated unified TCI state. In case 1.1.1, in another example (e.g., option 0A), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 1.1.1, in a third example (option 3), if the indicated TCI state is not followed, UE 115-b may use the TCI state of the scheduling CORESET.

[0167] In case 1.1, if UE 115-b supports two beams (e.g., case 1.1.2), in a first example (e.g., option 1), UE 115-b may use one TCI code point (e.g., the lowest code point) with 2 TCI states. In case 1.1.2, in one example (e.g., option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 1.1.2, in another example (e.g., option 3), the beam may depend on the RRC parameter "enableTwoDefaultTCI". For example, if enableTwoDefaultTCI is configured, UE 115-b may use one TCI code point with two TCI states (case 1.1.2 option 1). If enableTwoDefaultTCI is not configured, UE 115-b may use the options in case 1.1.1.

[0168] A second example sub-case (e.g., case 1.2) of the first example case of scenario 6 may involve indicating two unified TCI states through DCI or in a single TCI code point activated by MAC-CE. In case 1.2, if UE 115-b supports a single beam (e.g., case 1.2.1), in the first example (e.g., option 1), UE 115-b may use one indicated unified TCI state (e.g., first TCI state). In case 1.2.1, in another example (e.g., option 0A), UE 115-b may use a single indicated TCI state from the scheduling DCI. In case 1.2.1, in the second example (e.g., option 2), UE 115-b uses the same option as option 3 from case 1.1.1.

[0169] In case 1.2, if UE 115-b supports two beams (e.g., case 1.2.2), in one example (e.g., option 0), UE 115-b may use two indicated unified TCI states. In case 1.2.2, in another example (e.g., option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 1.2.2, in other examples, the UE may use the same options 1, 2, or 3 from case 1.1.2.

[0170] In Scenario 6, a second example case (eg, Case 2) may involve multiple TRPs between a single DCI cell (eg, at least one of the used TCIs has a non-serving cell SSB as a root QCL resource signal).

[0171] A first example subcase (e.g., case 2.1) of the second example case of scenario 6 may involve indicating a single unified TCI state (e.g., via DCI or in a single TCI code point activated by a MAC-CE). In case 2.1, if UE 115-b supports a single beam (e.g., case 2.1.1), then in an example (e.g., option 0A), UE 115-b may use the indicated TCI state from the scheduling DCI. In case 2.1.1, in another example (e.g., option 1), the UE may use option 3 from case 1.1.1.

[0172] In case 2.1, if UE 115-b supports two beams (e.g., case 2.1.2), then in an example (e.g., option 0A), UE 115-b may use two indicated TCIs from the scheduling DCI. In case 2.1.2, in a second example (e.g., option 1), UE 115-b may use one TCI code point with 2 TCI states, where at least one TCI state has a serving cell SSB as a root QCL resource signal (e.g., the lowest code point).

[0173] A second example sub-case (e.g., case 2.2) of the second example case of scenario 6 may involve indicating two unified TCI states (e.g., via DCI or in a single TCI code point activated by a MAC-CE). In case 2.2, if UE 115-b supports a single beam (e.g., case 2.2.1), in one example (e.g., option 0A), UE 115-b may use the indicated TCI state from the scheduling DCI. In case 2.2.1, in another example (e.g., option 1), UE 115-b may use option 3 from case 1.1.1. In case 2.2.1, in another example (e.g., option 3), if the indicated TCI state is not followed, UE 115-b may use the TCI state of the scheduling CORESET.

[0174] In case 2.1, if UE 115-b supports two beams (e.g., case 2.2.2), then in one example (option 0A), UE 115-b may use two indicated TCI states from the scheduling DCI. In case 2.2.2, in another example (e.g., option 1), UE 115-b may use one TCI code point with two TCIs, where at least one TCI has a serving cell SSB as a root QCL resource signal (e.g., the lowest code point).

[0175] Figure 6An example of a process flow 600 for supporting unified TCI determination for SFN in accordance with one or more aspects of the present disclosure is illustrated. The process flow 600 may include a UE 115-c, which may be an example of a UE 115 as described herein. The process flow 600 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 600, operations between the network entity 105-b and the UE 115-c may be sent in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-c may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0176] At 605, the UE 115-c may receive first control signaling from the network entity 105-b, which identifies a configuration for the UE 115-c to use SFN operation for at least one channel to communicate with the first TRP and the second TRP.

[0177] At 610, UE 115-c may receive second control signaling from network entity 105-b indicating that UE 115-c is to use a unified TCI state identifying that a single beam at UE 115-c is applicable to a set of multiple channels including at least one channel.

[0178] At 615, the UE 115-c and the network entity 105-b may communicate on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to the at least one channel according to one or more conditions.

[0179] In some examples, the one or more conditions include a time threshold, and communicating on the at least one channel includes communicating on the at least one channel according to the unified TCI state based on a time for communicating on the at least one channel satisfying the time threshold.

[0180] In some examples, the one or more conditions include a time threshold, and communicating on the at least one channel includes communicating on the at least one channel according to a default beam based on a time for communicating on the at least one channel satisfying the time threshold.

[0181] In some examples, the one or more conditions include whether SFN operation is configured for the downlink control channel at UE 115-c. UE 115-c may determine whether to apply a unified TCI state to at least one channel based on configuring SFN operation for the downlink control channel.

[0182] In some examples, the one or more conditions include whether SFN operation is configured at UE 115-c for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel. UE 115-c may determine whether to apply a unified TCI state to at least one channel based on configuring SFN operation for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel.

[0183] In some examples, the one or more conditions include one of intra-cell beam management or inter-cell beam management configured at UE 115-c. UE 115-c may determine whether to apply a unified TCI state to at least one channel based on one of the intra-cell beam management or inter-cell beam management configured at UE 115-c.

[0184] In some examples, the one or more conditions include that a single unified TCI state or one of two unified TCI states has been indicated to UE 115-c. UE 115-c may receive a control message indicating a single unified TCI state or one of two unified TCI states. UE 115-c may determine whether to apply a unified TCI state to at least one channel based on indicating a single unified TCI state or one of two unified TCI states to UE 115-c.

[0185] In some examples, one or more conditions include whether UE 115-c supports a single default beam or whether UE 115-c supports a set of multiple default beams. UE 115-c may determine whether to apply a unified TCI state to at least one channel based on whether UE 115-c supports a single default beam or whether UE 115-c supports a set of multiple default beams.

[0186] In some examples, UE 115-c may receive third control signaling indicating that UE 115-c is enabled to use a set of multiple default beams. UE 115-c may determine to apply the set of multiple default beams to at least one channel based on UE 115-c having received the third control signaling indicating that UE 115-c is enabled to use the set of multiple default beams.

[0187] In some examples, the second control signaling includes a DCI message.

[0188] In some examples, the at least one channel includes PDCCH, PDSCH, PUCCH, PUSCH, or any combination thereof.

[0189] Figure 7A block diagram 700 of a device 705 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the 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).

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

[0191] 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 (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to unified TCI determination for SFN). 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.

[0192] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of unified TCI determination for SFN as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0194] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, 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 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0195] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0196] According to the examples disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a first control signaling that identifies a configuration of the UE to use SFN operation for at least one channel to communicate with a first TRP and a second TRP. The communication manager 720 may be configured to or otherwise support a component for receiving a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The communication manager 720 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to at least one channel according to one or more conditions.

[0197] By including or configuring a communication manager 720 according to examples as described herein, a device 705 (e.g., a processor controlling or otherwise coupled to a receiver 710, a transmitter 715, a communication manager 720, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0198] Figure 8A block diagram 800 of a device 805 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0201] The device 805 or its various components may be examples of components for performing various aspects of unified TCI determination for SFN as described herein. For example, the communication manager 820 may include a multi-TRP manager 825, a unified TCI state manager 830, a channel beam manager 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0202] According to the examples disclosed herein, the communication manager 820 may support wireless communications at the UE. The multi-TRP manager 825 may be configured to or otherwise support components for receiving a first control signaling that identifies a configuration of the UE to use SFN operation for at least one channel to communicate with a first TRP and a second TRP. The unified TCI state manager 830 may be configured to or otherwise support components for receiving a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The channel beam manager 835 may be configured to or otherwise support components for communicating on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to at least one channel according to one or more conditions.

[0203] Fig. 9 A block diagram 900 of a communication manager 920 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of unified TCI determination for SFN as described herein. For example, the communication manager 920 may include a multi-TRP manager 925, a unified TCI state manager 930, a channel beam manager 935, a communication timing manager 940, a default beam manager 945, a SFN manager 950, an intra-cell / inter-cell beam manager 955, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0204] According to the examples disclosed herein, the communication manager 920 may support wireless communications at the UE. The multi-TRP manager 925 may be configured to or otherwise support components for receiving a first control signaling that identifies a configuration of the UE to use SFN operation for at least one channel to communicate with a first TRP and a second TRP. The unified TCI state manager 930 may be configured to or otherwise support components for receiving a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The channel beam manager 935 may be configured to or otherwise support components for communicating on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to at least one channel according to one or more conditions.

[0205] In some examples, one or more conditions include a time threshold, and to support communication on at least one channel, the communication timing manager 940 may be configured as or otherwise support components for communicating on at least one channel according to a unified TCI state based on the time for communicating on at least one channel satisfying the time threshold.

[0206] In some examples, one or more conditions include a time threshold, and to support communication on at least one channel, the default beam manager 945 may be configured as or otherwise support components for communicating on at least one channel according to a default beam based on the time for communicating on at least one channel satisfying the time threshold.

[0207] In some examples, one or more conditions include whether SFN operation is configured for a downlink control channel at the UE, and the SFN manager 950 may be configured to or otherwise support components for determining whether to apply a unified TCI state to at least one channel based on configuring SFN operation for the downlink control channel.

[0208] In some examples, one or more conditions include whether SFN operation is configured at the UE for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel, and the SFN manager 950 may be configured to or otherwise support components for determining whether to apply a unified TCI state to at least one channel based on configuring SFN operation for at least one of the downlink shared channel, the uplink control channel, or the uplink shared channel.

[0209] In some examples, one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE, and the intra-cell / inter-cell beam manager 955 may be configured as or otherwise support components for determining whether to apply a unified TCI state to at least one channel based on one of the intra-cell beam management or inter-cell beam management configured at the UE.

[0210] In some examples, one or more conditions include indicating a single unified TCI state or one of two unified TCI states to the UE, and the unified TCI state manager 930 may be configured to or otherwise support components for: receiving a control message indicating a single unified TCI state or one of two unified TCI states; and determining whether to apply the unified TCI state to at least one channel based on indicating a single unified TCI state or one of two unified TCI states to the UE.

[0211] In some examples, one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams, and the default beam manager 945 may be configured to or otherwise support components for determining whether to apply a unified TCI state to at least one channel based on whether the UE supports a single default beam or the UE supports multiple default beams.

[0212] In some examples, the default beam manager 945 may be configured or otherwise support means for receiving a third control signaling indicating that the UE is enabled to use a set of multiple default beams. In some examples, the default beam manager 945 may be configured or otherwise support means for determining to apply the set of multiple default beams to at least one channel based on the UE having received a third control signaling enabling the UE to use a set of multiple default beams.

[0213] In some examples, the second control signaling includes a DCI message.

[0214] In some examples, the at least one channel includes a physical downlink control channel, a physical downlink shared channel, a physical uplink control channel, a physical uplink shared channel, or any combination thereof.

[0215] Fig.10 A diagram of a system 1000 including a device 1005 that supports unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. 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 1045).

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

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

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

[0219] The processor 1040 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 1040 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 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks that support unified TCI determination for SFN). For example, the device 1005 or a component of the device 1005 may include a processor 1040 and a memory 1030 coupled to or coupled to the processor 1040, and the processor 1040 and the memory 1030 are configured to perform the various functions described herein.

[0220] According to the examples disclosed herein, the communication manager 1020 may support wireless communications at a UE. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving a first control signaling that identifies a configuration of the UE to use SFN operation for at least one channel to communicate with a first TRP and a second TRP. The communication manager 1020 may be configured to or otherwise support a component for receiving a second control signaling that indicates that the UE is to use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The communication manager 1020 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to at least one channel according to one or more conditions.

[0221] By including or configuring a communications manager 1020 according to examples as described herein, the device 1005 can support techniques for more efficiently utilizing communications resources and improving utilization of processing power.

[0222] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. For example, the communication manager 1020 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1015. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that may be executed by the processor 1040 to cause the device 1005 to perform various aspects of the unified TCI determination for SFN as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0223] Fig.11 A block diagram 1100 of a device 1105 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the 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).

[0224] 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) interfaces, wireless interfaces, or any combination thereof.

[0225] 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 a modem.

[0226] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of unified TCI determination for SFN as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

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

[0228] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, 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 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0230] According to the examples disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for outputting a first control signaling that identifies a configuration for the UE to use SFN communications for at least one channel to communicate with a first TRP and a second TRP associated with the network entity. The communication manager 1120 may be configured to or otherwise support a component for outputting a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The communication manager 1120 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether the UE applies a unified TCI state to at least one channel according to one or more conditions.

[0231] By including or configuring a communications manager 1120 according to examples as described herein, a device 1105 (e.g., a processor controlling or otherwise coupled to a receiver 1110, a transmitter 1115, a communications manager 1120, or a combination thereof) may support techniques for more efficiently utilizing communications resources.

[0232] Fig.12 A block diagram 1200 of a device 1205 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0233] Receiver 1210 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 1205. In some examples, receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0234] The transmitter 1215 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 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 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 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 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0235] The device 1205 or its various components may be examples of components for performing various aspects of unified TCI determination for SFN as described herein. For example, the communication manager 1220 may include a multi-TRP manager 1225, a unified TCI state manager 1230, a channel beam manager 1235, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to use or otherwise cooperate with the receiver 1210, the transmitter 1215, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0236] According to the examples disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The multi-TRP manager 1225 may be configured to or otherwise support a component for outputting a first control signaling that identifies a configuration for the UE to use SFN communications for at least one channel to communicate with a first TRP and a second TRP associated with the same network entity. The unified TCI state manager 1230 may be configured to or otherwise support a component for outputting a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The channel beam manager 1235 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether the UE applies the unified TCI state to at least one channel according to one or more conditions.

[0237] Fig.13 A block diagram 1300 of a communication manager 1320 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing aspects of unified TCI determination for SFN as described herein. For example, the communication manager 1320 may include a multi-TRP manager 1325, a unified TCI state manager 1330, a channel beam manager 1335, a communication timing manager 1340, a default beam manager 1345, 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 the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0238] According to the examples disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The multi-TRP manager 1325 may be configured to or otherwise support a component for outputting a first control signaling that identifies a configuration for the UE to use SFN communications for at least one channel to communicate with a first TRP and a second TRP associated with the same network entity. The unified TCI state manager 1330 may be configured to or otherwise support a component for outputting a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The channel beam manager 1335 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether the UE applies a unified TCI state to at least one channel according to one or more conditions.

[0239] In some examples, one or more conditions include a time threshold, and to support communication on at least one channel, the communication timing manager 1340 may be configured as or otherwise support components for communicating on at least one channel according to a unified TCI state based on the time for communicating on at least one channel satisfying the time threshold.

[0240] In some examples, one or more conditions include a time threshold, and to support communication on at least one channel, the communication timing manager 1340 may be configured as or otherwise support components for communicating on at least one channel according to a default beam based on the time for communicating on at least one channel satisfying the time threshold.

[0241] In some examples, the one or more conditions include whether SFN operation is configured at the UE for the downlink control channel.

[0242] In some examples, the one or more conditions include whether SFN operation is configured at the UE for at least one of the downlink shared channels.

[0243] In some examples, one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE.

[0244] In some examples, one or more conditions include a single unified transmit configuration indication state or one of two unified transmit configuration indication states indicated to the UE, and the unified TCI state manager 1330 may be configured as or otherwise support components for outputting a control message indicating a single unified TCI state or one of two unified TCI states.

[0245] In some examples, one or more conditions include whether the UE supports a single default beam or whether the UE supports a set of multiple default beams.

[0246] In some examples, the default beam manager 1345 may be configured as or otherwise support components for outputting third control signaling to enable the UE to use a set of multiple default beams, wherein the UE determines to apply the set of multiple default beams to at least one channel based on the UE having received third control signaling that enables the UE to use the set of multiple default beams.

[0247] Fig.14 A diagram of a system 1400 including a device 1405 supporting unified TCI determination for SFN according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 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 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. 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 1440).

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

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

[0250] The processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1435 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 1435. The processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable the device 1405 to perform various functions (e.g., functions or tasks that support unified TCI determination for SFN). For example, the device 1405 or a component of the device 1405 may include a processor 1435 and a memory 1425 coupled to the processor 1435, the processor 1435 and the memory 1425 being configured to perform various functions described herein. The processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing the functions of the device 1405 (e.g., by executing code 1430). Processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as in memory 1425). In some specific implementations, processor 1435 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be delivered to other systems or components of device 1405, for example). For example, a processing system of device 1405 may refer to a system including various other components or subcomponents of device 1405, such as processor 1435, or transceiver 1410, or communication manager 1420, or other components or combinations of components of device 1405. A processing system of device 1405 may interface with other components of device 1405 and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1405 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1405 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0251] In some examples, bus 1440 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 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 1405, or communications performed between different components of device 1405 that may be co-located or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or divided between the different components).

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

[0253] According to the examples disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support a component for outputting a first control signaling that identifies a configuration for the UE to use SFN communications for at least one channel to communicate with a first TRP and a second TRP associated with the same network entity. The communication manager 1420 may be configured to or otherwise support a component for outputting a second control signaling that indicates that the UE will use a unified TCI state that identifies that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The communication manager 1420 may be configured to or otherwise support a component for communicating on at least one channel according to at least one beam based on determining whether the UE applies a unified TCI state to at least one channel according to one or more conditions.

[0254] By including or configuring a communication manager 1420 according to examples as described herein, the device 1405 can support techniques for more efficiently utilizing communication resources and improving utilization of processing power.

[0255] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. For example, the communication manager 1420 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1410. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions that may be executed by the processor 1435 to cause the device 1405 to perform various aspects of the unified TCI determination for SFN as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0256] Fig.15 1 is a flowchart illustrating a method 1500 for supporting unified TCI determination for SFN according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0257] At 1505, the method may include receiving first control signaling that identifies a configuration of the UE to communicate with a first TRP and a second TRP using SFN communication for at least one channel. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The multi-TRP manager 925 described is executed. Additionally or alternatively, the components for executing 1505 may, but need not necessarily include, for example, an antenna 1025, a transceiver 1015, a communication manager 1020, a memory 1030 (including code 1035), a processor 1040, and / or a bus 1045.

[0258] At 1510, the method may include receiving second control signaling indicating that the UE is to use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to a set of multiple channels including at least one channel. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described unified TCI state manager 930 is executed. Additionally or alternatively, the components for executing 1510 may, but need not necessarily include, for example, an antenna 1025, a transceiver 1015, a communication manager 1020, a memory 1030 (including code 1035), a processor 1040, and / or a bus 1045.

[0259] At 1515, the method may include communicating on at least one channel according to at least one beam based on determining whether to apply a unified TCI state to the at least one channel according to one or more conditions. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 1035 , the communication manager 1020 , the memory 1030 (including the code 1035 ), the processor 1040 , and / or the bus 1045 .

[0260] Fig.16 1 is a flowchart illustrating a method 1600 for supporting unified TCI determination for SFN according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0261] At 1605, the method may include outputting first control signaling that identifies a configuration for the UE to communicate with a first TRP and a second TRP associated with a network entity using SFN communication for at least one channel. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.13The multi-TRP manager 1325 described is executed. Additionally or alternatively, the components for executing 1605 may, but need not necessarily, include, for example, an antenna 1415, a transceiver 1410, a communication manager 1420, a memory 1425 (including code 1430), a processor 1435, and / or a bus 1440.

[0262] At 1610, the method may include outputting second control signaling indicating that the UE is to use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to a set of multiple channels including at least one channel. 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.13 The described unified TCI state manager 1330 is executed.

[0263] At 1615, the method may include communicating on at least one channel according to at least one beam based on determining whether the UE applies a unified TCI state to the at least one channel according to one or more conditions. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.13 The described channel beam manager 1335 is performed.

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

[0265] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving a first control signaling, the first control signaling identifying a configuration of the UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP; receiving a second control signaling indicating that the UE will use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to multiple channels including the at least one channel; and communicating on the at least one channel according to at least one beam based at least in part on determining whether to apply the unified TCI state to the at least one channel according to one or more conditions.

[0266] Aspect 2: A method according to Aspect 1, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: communicating on the at least one channel according to the unified TCI state based at least in part on the time used to communicate on the at least one channel satisfying the time threshold.

[0267] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: communicating on the at least one channel according to a default beam based at least in part on the time for communicating on the at least one channel satisfying the time threshold.

[0268] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the one or more conditions include whether SFN operation is configured for a downlink control channel at the UE, and the method includes determining whether to apply the unified TCI state to the at least one channel based at least in part on configuring the SFN operation for the downlink control channel.

[0269] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the one or more conditions include whether SFN operation is configured at the UE for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel, and the method includes determining whether to apply the unified TCI state to the at least one channel based at least in part on configuring the SFN operation for the at least one of the downlink shared channel, the uplink control channel, or the uplink shared channel.

[0270] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE, and the method includes determining whether to apply the unified TCI state to the at least one channel based at least in part on the one of the intra-cell beam management or the inter-cell beam management configured at the UE.

[0271] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the one or more conditions include that a single unified TCI state or one of two unified TCI states has been indicated to the UE, and the method includes receiving a control message indicating the single unified TCI state or one of the two unified TCI states; and determining whether to apply the unified TCI state to the at least one channel based at least in part on indicating the single unified TCI state or one of the two unified TCI states to the UE.

[0272] Aspect 8: A method according to any one of Aspects 1 to 7, wherein the one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams, and the method includes determining whether to apply the unified TCI state to the at least one channel based at least in part on whether the UE supports the single default beam or the UE supports the multiple default beams.

[0273] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving a third control signaling indicating that the UE is enabled to use multiple default beams; and determining to apply the multiple default beams to the at least one channel based at least in part on the UE having received the third control signaling indicating that the UE is enabled to use the multiple default beams.

[0274] Aspect 10: The method according to any one of aspects 1 to 9, wherein the second control signaling includes a DCI message.

[0275] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the at least one channel comprises a physical downlink control channel, a physical downlink shared channel, a physical uplink control channel, a physical uplink shared channel, or any combination thereof.

[0276] Aspect 12: A method for performing wireless communications at a network entity, the method comprising: outputting a first control signaling, the first control signaling identifying a configuration for a UE to use SFN communication for at least one channel to communicate with a first TRP and a second TRP associated with the network entity; outputting a second control signaling, the second control signaling indicating that the UE will use a unified TCI state, the unified TCI state identifying that a single beam at the UE is applicable to multiple channels including the at least one channel; and communicating on the at least one channel according to at least one beam based at least in part on determining whether the UE applies the unified TCI state to the at least one channel according to one or more conditions.

[0277] Aspect 13: A method according to Aspect 12, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: communicating on the at least one channel according to the unified TCI state based at least in part on the time used to communicate on the at least one channel satisfying the time threshold.

[0278] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: communicating on the at least one channel according to a default beam based at least in part on the time for communicating on the at least one channel satisfying the time threshold.

[0279] Aspect 15: The method according to any one of aspects 12 to 14, wherein the one or more conditions include whether SFN operation is configured for a downlink control channel at the UE.

[0280] Aspect 16: The method according to any one of aspects 12 to 15, wherein the one or more conditions include whether SFN operation is configured at the UE for at least one of the downlink shared channels.

[0281] Aspect 17: The method according to any one of aspects 12 to 16, wherein the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE.

[0282] Aspect 18: A method according to any one of Aspects 12 to 17, wherein the one or more conditions include indicating a single unified TCI state or one of two unified TCI states to the UE, and the method includes outputting a control message indicating the single unified TCI state or one of the two unified TCI states.

[0283] Aspect 19: A method according to any one of aspects 12 to 18, wherein the one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams.

[0284] Aspect 20: According to the method described in any one of Aspects 12 to 19, the method further includes: outputting a third control signaling to enable the UE to use multiple default beams, wherein the UE determines to apply the multiple default beams to the at least one channel at least in part based on the UE having received the third control signaling that enables the UE to use the multiple default beams.

[0285] Aspect 21: A device comprising: a memory; a transceiver; and at least one processor, the at least one processor being coupled to the memory and the transceiver, the at least one processor being configured to execute the method according to any one of Aspects 1 to 11.

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

[0287] Aspect 23: 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 11.

[0288] Aspect 24: An apparatus, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory, the at least one processor being configured to execute the method according to any one of aspects 12 to 20.

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first control signaling, the first control signaling identifying a configuration of the UE to communicate with a first transmission and reception point and a second transmission and reception point using single frequency network communication for at least one channel; receiving second control signaling indicating that the UE is to use a unified transmission configuration indication state, the unified transmission configuration indication state identifying that a single beam at the UE is applicable to multiple channels including the at least one channel; as well as Communicating on the at least one channel according to at least one beam is performed based at least in part on determining whether to apply the unified transmit configuration indication state to the at least one channel according to one or more conditions.

2. The method of claim 1 , wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: Communicating on the at least one channel in accordance with the unified transmission configuration indicates a state based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

3. The method of claim 1 , wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: Communicating on the at least one channel according to a default beam is performed based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

4. The method of claim 1 , wherein the one or more conditions include whether single frequency network operation is configured for a downlink control channel at the UE, the method comprising determining whether to apply the unified transmit configuration indication state to the at least one channel based at least in part on configuring the single frequency network operation for the downlink control channel.

5. The method of claim 1 , wherein the one or more conditions include whether single frequency network operation is configured at the UE for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel, the method comprising determining whether to apply the unified transmission configuration indication state to the at least one channel based at least in part on configuring the single frequency network operation for the at least one of the downlink shared channel, the uplink control channel, or the uplink shared channel.

6. A method according to claim 1, wherein the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE, and the method includes determining whether to apply the unified transmission configuration indication state to the at least one channel based at least in part on the one of the intra-cell beam management or the inter-cell beam management configured at the UE.

7. The method of claim 1, wherein the one or more conditions include indicating to the UE that a single unified transmission configuration indication state or two unified transmission configuration indication states have been indicated, the method comprising: receiving a control message indicating the single unified transmission configuration indication state or the one of the two unified transmission configuration indication states; as well as Determining whether to apply the unified transmit configuration indication state to the at least one channel is based at least in part on indicating the single unified transmit configuration indication state or the one of the two unified transmit configuration indication states to the UE.

8. A method according to claim 1, wherein the one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams, and the method includes determining whether to apply the unified transmit configuration indication state to the at least one channel based at least in part on whether the UE supports the single default beam or the UE supports the multiple default beams.

9. The method according to claim 1, further comprising: receiving third control signaling indicating that the UE can use multiple default beams; as well as Determining to apply the multiple default beams to the at least one channel is based at least in part on the UE having received the third control signaling enabling the UE to use the multiple default beams.

10. The method of claim 1, wherein the second control signaling comprises a downlink control information message.

11. The method of claim 1, wherein the at least one channel comprises a physical downlink control channel, a physical downlink shared channel, a physical uplink control channel, a physical uplink shared channel, or any combination thereof.

12. A method for wireless communication at a network entity, the method comprising: outputting first control signaling, the first control signaling identifying a configuration for a user equipment (UE) to communicate with a first transmission and reception point and a second transmission and reception point associated with the network entity using single frequency network communication for at least one channel; Outputting second control signaling, wherein the second control signaling indicates that the UE will use a unified transmission configuration indication state, wherein the unified transmission configuration indication state identifies that a single beam at the UE is applicable to multiple channels including the at least one channel; as well as Communicate on the at least one channel according to at least one beam based at least in part on determining whether the UE applies the unified transmit configuration indication state to the at least one channel according to one or more conditions.

13. The method of claim 12, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: Communicating on the at least one channel in accordance with the unified transmission configuration indicates a state based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

14. The method of claim 12, wherein the one or more conditions include a time threshold, and communicating on the at least one channel includes: Communicating on the at least one channel according to a default beam is performed based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

15. The method of claim 12, wherein the one or more conditions include whether single frequency network operation is configured at the UE for a downlink control channel.

16. The method of claim 12, wherein the one or more conditions include whether single frequency network operation is configured at the UE for at least one of the downlink shared channels.

17. The method of claim 12, wherein the one or more conditions include configuring one of intra-cell beam management or inter-cell beam management at the UE.

18. A method according to claim 12, wherein the one or more conditions include indicating to the UE a single unified transmission configuration indication state or one of two unified transmission configuration indication states, and the method includes outputting a control message indicating the single unified transmission configuration indication state or one of the two unified transmission configuration indication states.

19. The method of claim 12, wherein the one or more conditions include whether the UE supports a single default beam or whether the UE supports multiple default beams.

20. The method according to claim 12, further comprising: Outputting third control signaling to enable the UE to use multiple default beams, wherein the UE determines to apply the multiple default beams to the at least one channel based at least in part on the UE having received the third control signaling that enables the UE to use the multiple default beams.

21. An apparatus for wireless communication, the apparatus comprising: Memory; Transceiver; and At least one processor of a user equipment (UE), the at least one processor coupled to the memory and the transceiver, and the at least one processor configured to: receiving, via the transceiver, first control signaling, the first control signaling identifying a configuration of the UE to communicate with a first transmission and reception point and a second transmission and reception point using single frequency network communication for at least one channel; receiving, via the transceiver, second control signaling indicating that the UE is to use a unified transmit configuration indication state, the unified transmit configuration indication state identifying that a single beam at the UE is applicable to a plurality of channels including the at least one channel; as well as Communicating on the at least one channel according to at least one beam via the transceiver based at least in part on determining whether to apply the unified transmit configuration indication state to the at least one channel according to one or more conditions.

22. The apparatus of claim 21, wherein the one or more conditions include a time threshold, and wherein to communicate on the at least one channel, the at least one processor is further configured to: Communicating on the at least one channel in accordance with the unified transmission configuration indicates a state based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

23. The apparatus of claim 21 , wherein the one or more conditions comprise a time threshold, and wherein to communicate on the at least one channel, the at least one processor is further configured to: Communicating on the at least one channel according to a default beam is performed based at least in part on a time for communicating on the at least one channel satisfying the time threshold.

24. The apparatus of claim 21, wherein the one or more conditions include whether single frequency network operation is configured at the UE for a downlink control channel, wherein the at least one processor is further configured to: Determining whether to apply the unified transmit configuration indication state to the at least one channel is based at least in part on configuring the single frequency network operation for the downlink control channel.

25. The apparatus of claim 21, wherein the one or more conditions comprise whether single frequency network operation is configured at the UE for at least one of a downlink shared channel, an uplink control channel, or an uplink shared channel, wherein the at least one processor is further configured to: Determining whether to apply the unified transmit configuration indication state to the at least one channel is based at least in part on configuring the single frequency network operation for the at least one of the downlink shared channel, the uplink control channel, or the uplink shared channel.

26. The apparatus of claim 21, wherein the one or more conditions comprise configuring one of intra-cell beam management or inter-cell beam management at the UE, wherein the at least one processor is further configured to: Determining whether to apply the unified transmission configuration indication state to the at least one channel is determined based at least in part on the one of the intra-cell beam management or the inter-cell beam management configured at the UE.

27. The apparatus of claim 21, wherein the one or more conditions include indicating to the UE that a single unified transmission configuration indication state or two unified transmission configuration indication states have been indicated, wherein the at least one processor is further configured to: receiving a control message indicating the single unified transmission configuration indication state or the one of the two unified transmission configuration indication states; and Determining whether to apply the unified transmit configuration indication state to the at least one channel is based at least in part on indicating the single unified transmit configuration indication state or the one of the two unified transmit configuration indication states to the UE.

28. The apparatus of claim 21, wherein the one or more conditions include whether the UE supports a single default beam or the UE supports multiple default beams, wherein the at least one processor is further configured to: Determining whether to apply the unified transmit configuration indication state to the at least one channel is based at least in part on whether the UE supports the single default beam or the UE supports the multiple default beams.

29. The apparatus of claim 21, wherein the at least one processor is further configured to: receiving third control signaling indicating that the UE can use multiple default beams; and Determining to apply the multiple default beams to the at least one channel is based at least in part on the UE having received the third control signaling enabling the UE to use the multiple default beams.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor of a network entity, the at least one processor being coupled to the memory, and the at least one processor being configured to: outputting first control signaling, the first control signaling identifying a configuration for a user equipment (UE) to communicate with a first transmission and reception point and a second transmission and reception point associated with the network entity using single frequency network communication for at least one channel; Outputting second control signaling, wherein the second control signaling indicates that the UE will use a unified transmission configuration indication state, wherein the unified transmission configuration indication state identifies that a single beam at the UE is applicable to multiple channels including the at least one channel; as well as Communicate on the at least one channel according to at least one beam based at least in part on determining whether the UE applies the unified transmit configuration indication state to the at least one channel according to one or more conditions.

Images