Per-transmit and receive point power control for uplink single frequency network operation

Abstract

Methods, systems, and devices for wireless communication are described. The described techniques provide per-transmit and receive point (TRP) power control for uplink transmissions using single frequency network (SFN) configurations. A UE establishing communication with a network via two or more TRPs using an SFN configuration for uplink transmissions may determine a respective uplink transmission power level for uplink transmissions to each TRP. The UE may transmit an uplink transmission to the two or more TRPs according to the determined respective uplink transmission power levels. In some cases, the UE may receive a downlink control information message including a transmit power command field for each respective TRP based on a transmit configuration indicator state associated with each TRP. In some cases, the UE may determine a set of power control parameters associated with each TRP. In some cases, the UE may send a power headroom report for each TRP.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, including per-transmit and receive point power control for uplink single frequency network operations. Background Art

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

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting per-transmit and receive point (TRP) power control for uplink single frequency network (SFN) operation. For example, the described technology provides per-TRP power control for uplink transmissions using SFN configuration. A UE that establishes a communication link with a network via two or more TRPs (e.g., in a multi-TRP (mTRP) system) using an SFN configuration for uplink transmissions may determine a corresponding uplink transmit power level for uplink transmissions to each TRP. A UE operating according to the SFN configuration may send uplink transmissions to two or more TRPs according to the determined corresponding uplink transmit power levels. In some cases, the UE may receive a downlink control information (DCI) message including a transmit power command field for each corresponding TRP. In some cases, the UE may determine a set of power control parameters associated with each TRP based on a transmit configuration indicator (TCI) state associated with each TRP. In some cases, the UE may send a power headroom report for each TRP (e.g., based on a measurement reference signal received from the TRP). The UE may receive an indication of an uplink power level associated with the TRP from the network based on the reported power headroom report.

[0004] A method for wireless communication at a UE is described. The method may include: establishing a communication link with a network via a first TRP and a second TRP according to a single frequency network configuration; determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP; and sending a first uplink transmission to the first TRP according to the first uplink power level and sending a second uplink transmission to the second TRP according to the second uplink power level.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: establish a communication link with a network via a first TRP and a second TRP according to a single frequency network configuration; determine a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP; and send a first uplink transmission to the first TRP according to the first uplink power level and send a second uplink transmission to the second TRP according to the second uplink power level.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: components for establishing a communication link with a network via a first TRP and a second TRP according to a single frequency network configuration; components for determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP; and components for sending a first uplink transmission to the first TRP according to the first uplink power level and sending a second uplink transmission to the second TRP according to the second uplink power level.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: establish a communication link with a network via a first TRP and a second TRP according to a single frequency network configuration; determine a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP; and send a first uplink transmission to the first TRP according to the first uplink power level and send a second uplink transmission to the second TRP according to the second uplink power level.

[0008] 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 DCI message indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP, wherein determining the first uplink power level and the second uplink power level may be based on the first transmit power command and the second transmit power command.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining, based on an order of a first field indicating a first transmit power command and a second field indicating a second transmit power command within a DCI message, that a first field may be associated with a first TCI state of a TCI code point and a second field may be associated with a second TCI state of the TCI code point.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining, based on an order of a first field indicating a first transmit power command and a second field indicating a second transmit power command within a DCI message, that a first field may be associated with a first TCI state of a first closed-loop index in a TCI code point and a second field may be associated with a second TCI state of a second closed-loop index in a TCI code point.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a first set of power control parameters associated with a first TRP and a second set of power control parameters associated with a second TRP based on a first TCI state associated with the first TRP and a second TCI state associated with the second TRP, wherein determining a first uplink power level for a first uplink transmission and a second uplink power level for a second uplink transmission may be based on the first set of power control parameters and the second set of power control parameters.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating that a first set of power control parameters may be associated with a first TCI state and a second set of power control parameters may be associated with a second TCI state based on a TCI code point including a first TCI state and a second TCI state.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating two sets of power control parameters for each uplink bandwidth portion in a set of multiple uplink bandwidth portions, wherein the identification may be based on an uplink bandwidth portion in the set of multiple uplink bandwidth portions associated with the first uplink transmission and the second uplink transmission.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first set of power control parameters includes a default first set of power control parameters, and the second set of power control parameters includes a default second set of power control parameters.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message including a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling instructing the UE to report a first power headroom report and a second power headroom report.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling for scheduling uplink transmissions using a single frequency network configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmissions.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling for scheduling uplink transmissions using a transmission configuration different than a single frequency network configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission and the second power headroom report includes a virtual power headroom report.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, establishing a communication link with a network based on a single frequency network configuration may include operations, features, components, or instructions for receiving a first set of parameter values ​​for uplink transmissions to a first TRP for a first set of antenna elements for the UE and a second set of parameter values ​​for uplink transmissions to a second TRP for a second set of antenna elements for the UE during the same set of time and frequency resources.

[0020] A method for wireless communication at a network entity is described. The method may include: establishing a communication link with a UE via a first TRP and a second TRP according to a single frequency network configuration; sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP; and receiving a first uplink transmission from the UE via the first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via the second TRP according to the second uplink power level at least in part in response to the sent power management signaling.

[0021] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: establish a communication link with a UE via a first TRP and a second TRP according to a single frequency network configuration; send power management signaling to the UE configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP; and receive a first uplink transmission from the UE via the first TRP according to the first uplink power level and receive a second uplink transmission from the UE via the second TRP according to the second uplink power level, at least in part in response to the sent power management signaling.

[0022] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for establishing a communication link with a UE via a first TRP and a second TRP according to a single frequency network configuration; a component for sending to the UE power management signaling configured to support the UE to determine a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP; and a component for receiving a first uplink transmission from the UE via the first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via the second TRP according to the second uplink power level at least in part in response to the sent power management signaling.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: establish a communication link with a UE via a first TRP and a second TRP according to a single frequency network configuration; send power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP; and receive a first uplink transmission from the UE via the first TRP according to the first uplink power level and receive a second uplink transmission from the UE via the second TRP according to the second uplink power level at least in part in response to the sent power management signaling.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting power management signaling may include operations, features, components, or instructions for sending a DCI message indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a DCI message may include operations, features, components, or instructions for sending a DCI message including a first field indicating that a first transmit power command may be associated with a first TCI state of a TCI code point and a second field indicating that a second transmit power command may be associated with a second TCI state of the TCI code point, wherein based on an order of the first field and the second field within the DCI message, a first TRP may be associated with a first TCI state and a second TRP may be associated with a second TCI state.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a DCI message may include operations, features, components, or instructions for sending a DCI message including a first field indicating that a first transmit power command may be associated with a first TCI state with a first closed-loop index in a TCI code point and a second field indicating that a second transmit power command may be associated with a second TCI state with a second closed-loop index in a TCI code point, wherein based on an order of the first field and the second field within the DCI message, a first TRP may be associated with a first TCI state and a second TRP may be associated with a second TCI state.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending power management signaling may include operations, features, components, or instructions for sending control signaling indicating that a first set of power control parameters may be associated with a first TCI state and a second set of power control parameters may be associated with a second TCI state based on a TCI code point including a first TCI state and a second TCI state, wherein the first TCI state may be associated with a first TRP and the second TCI state may be associated with a second TRP.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending power management signaling may include operations, features, components, or instructions for sending control signaling indicating two sets of power control parameters for each uplink bandwidth portion in a set of multiple uplink bandwidth portions, wherein the uplink bandwidth portions in the set of multiple uplink bandwidth portions may be associated with a first uplink transmission and a second uplink transmission.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message from a UE including a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending power management signaling may include operations, features, components, or instructions for sending control signaling indicating a first uplink power level and a second uplink power level.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to a UE instructing the UE to report a first power headroom report and a second power headroom report.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to a UE to schedule uplink transmissions using a single frequency network configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmissions.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to a UE to schedule uplink transmissions using a transmission configuration different from a single frequency network configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission and the second power headroom report includes a virtual power headroom report. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 An example of a wireless communication system supporting per-transmit and receive point (TRP) power control for uplink single frequency network (SFN) operation in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 2 An example of a network architecture supporting per-transmission and reception point power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated.

[0036] Figure 3 An example of a wireless communication system supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is illustrated.

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

[0038] Figure 5 An example of a process flow supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 6 An example of a process flow supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 7 An example of a process flow supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 8 and Fig. 9 A block diagram of a device supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown.

[0042] Fig.10 A block diagram of a communication manager supporting per-TRP power control for uplink SFN operations in accordance with one or more aspects of the present disclosure is shown.

[0043] Fig.11 A diagram of a system including a device supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown.

[0044] Fig.12 and Fig.13A block diagram of a device supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown.

[0045] Fig.14 A block diagram of a communication manager supporting per-TRP power control for uplink SFN operations in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig.15 A diagram of a system including a device supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown.

[0047] Figures 16 to 21 A flow chart illustrating a method of supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0048] In some wireless communication systems, a user equipment (UE) may communicate with a network via two or more transmit and receive points (TRPs). In some cases, the UE may be configured to send uplink communications via a single frequency network (SFN) configuration. In an SFN configuration, the UE may be configured to send the same uplink transmission (e.g., a physical uplink control channel (PUCCH) transmission or a physical uplink shared channel (PUSCH) transmission) using the same frequency and / or time resources. 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 indicator (TCI) state. Currently, there is no configuration to implement per-TRP power control for uplink transmissions using an SFN configuration.

[0049] Various aspects of the present disclosure relate to per-TRP power control for uplink transmissions using SFN. A UE establishing communication with a network via two or more TRPs using an SFN configuration for uplink transmissions may determine a corresponding uplink transmit power level for uplink transmissions to each TRP. A UE operating in accordance with the SFN configuration may transmit uplink transmissions to two or more TRPs in accordance with the determined corresponding uplink transmit power levels.

[0050] In some cases, the UE may receive a downlink control information (DCI) message including a transmit power command field for each corresponding TRP. In some cases, the UE may determine which transmit power command field is associated with which TRP based on the TCI state associated with the TRP and the order of the transmit power command field within the DCI message. In some cases, the UE may determine a set of power control parameters associated with each TRP based on the TCI state associated with each TRP. For example, the control signaling received at the UE may indicate a set of corresponding power control parameters associated with each TCI state based on the TCI code point, and the UE may determine the uplink transmit power level for the corresponding TRP based on the set of power control parameters associated with the corresponding TCI state. In some cases, the UE may send a power headroom report for each TRP (e.g., based on a measurement reference signal received from the TRP). The power headroom value may indicate how much transmit power is available to the UE for an upcoming transmission, calculated as the difference between the maximum available transmit power and the required transmit power for the upcoming transmission based on the set of power control parameters. The UE may receive an indication of the uplink power level to be used for the TRP from the network based on the reported power headroom report.

[0051] 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 process flows, apparatus diagrams, system diagrams, and flow charts involving per-TRP power control for uplink SFN operation, and are described with reference to these figures.

[0052] Figure 1 An example of a wireless communication system 100 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

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

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

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

[0061] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104 and one or more UEs 115. The IAB host 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 host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

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

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

[0064] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support per-TRP power control for uplink SFN operation 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).

[0065] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] 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 physical downlink control channel (PDCCH), a UE-specific physical downlink shared channel (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.

[0101] In some cases, UE 115 may be configured to send uplink communications via a SFN configuration. In a SFN configuration, the UE 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, in order to facilitate simultaneous multi-panel uplink transmissions to achieve higher uplink throughput and reliability (e.g., focusing on FR2 and multiple TRPs), an uplink precoding indication for PUSCH may be specified, where no new codebook is introduced for simultaneous transmission of multiple panels. In some cases, considering multi-TRP operation based on single DCI and multiple DCI, the total number of layers across all panels may be up to four and the total number of codewords across all panels may be up to two. In some cases, in order to facilitate simultaneous multi-panel uplink transmissions to achieve higher uplink throughput and reliability (e.g., focusing on FR2 and multi-TRP), uplink beam indications for PUCCH or PUSCH may be specified, where multi-TRP operations based on single DCI and multi-DCI are considered, and a unified TCI framework may be assumed. For the case of multi-TRP operation based on multi-DCI, 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 of uplink multi-DCI for multi-TRP operation may be specified. In some cases, power control for uplink single DCI for multi-TRP operation may be applied.

[0102] Some network entities 105 may configure (e.g., RRC configure) power control parameters for each serving cell of UE 115. In some cases, multiple power control parameter sets (e.g., Uplink-powerControl) may be configured for each serving cell of UE 115. For example, each TCI state may include a set of power control parameters. In some examples, the power control parameters may be configured in a serving cell configuration (e.g., ServingCellConfig). For example, a serving cell configuration may include a list of uplink or downlink power control parameters for a corresponding serving cell, where the power control parameters may be configured for sending, for example, a PUSCH, a PUCCH, or a sounding reference signal (SRS). In some cases, if each TCI state does not include a set of uplink power control parameters, the uplink BWP may include one or more sets of uplink power control parameters.

[0103] A UE 115 establishing communication with a network via two or more TRPs using an SFN configuration for uplink transmissions may determine a corresponding uplink transmission power level for uplink transmissions to each TRP. A UE 115 operating in accordance with the SFN configuration may transmit uplink transmissions to two or more TRPs in accordance with the determined corresponding uplink transmission power levels.

[0104] In some cases, UE 115 may receive a DCI message including a transmit power command field for each respective TRP, wherein multiple transmit power command fields in the DCI message may be configured by higher layer signaling. In some cases, UE 115 may determine which transmit power command field is associated with which TRP based on the TCI state associated with the TRP and the order of the transmit power command fields within the DCI message.

[0105] In some cases, UE 115 may determine a set of power control parameters associated with each TRP based on the TCI state associated with each TRP. For example, control signaling received at UE 115 may indicate a corresponding set of power control parameters associated with each TCI state based on the TCI code point, and UE 115 may determine an uplink transmit power level for a corresponding TRP based on the set of power control parameters associated with the corresponding TCI state. Each set of power control parameters may include a path loss reference signal (PLRS) parameter, a nominal power parameter, an alpha value parameter, a closed loop index parameter, a power management maximum power reduction (P-MPR) parameter, or a combination thereof. The control signaling may be higher layer signaling, such as RRC configuration signaling.

[0106] In some cases, UE 115 may send a power headroom report for each TRP (e.g., based on a measurement reference signal received from the TRP). The power headroom value may indicate how much transmit power is available to UE 115 for an upcoming transmission, calculated as the difference between the maximum available transmit power and the required transmit power for the upcoming transmission based on a set of power control parameters. A real power headroom report may be based on an actual PUSCH to be transmitted (which may also be referred to as an actual uplink transmission, a scheduled uplink transmission, a scheduled PUSCH, a real uplink transmission, or a real PUSCH). A virtual power headroom report may be based on a reference PUSCH transmission (which may also be referred to as a reference uplink transmission, a virtual uplink transmission, a virtual PUSCH, a non-scheduled uplink transmission, or a non-scheduled PUSCH) instead of a real PUSCH transmission, so that the virtual power headroom report is based on some assumption of parameters related to PUSCH transmission rather than the actual indicated parameters for the actual PUSCH transmission. A real power headroom report may also be referred to as a scheduled power headroom report or an actual headroom report. A virtual headroom report may also be referred to as a non-scheduled headroom report.

[0107] UE 115 may receive an indication of an uplink power level for a TRP from the network based on the reported power headroom report. In some cases, at least a second set of power control parameters may be associated with a virtual power headroom report. UE 115 may send a message including a first power headroom report generated by UE 115 for a first uplink transmission (e.g., a scheduled or non-scheduled PUSCH transmission) using a first set of power control parameters. In addition, the message may include a second power headroom report generated by the UE for an uplink transmission (e.g., a scheduled or non-scheduled PUSCH transmission) using a second set of power control parameters. Thus, UE 115 may send two power headroom reports to the network based on UE 115 communicating with two TRPs having separate sets of uplink power control parameters.

[0108] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting per-transmit and receive point power control for uplink SFN operation 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 RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

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

[0110] 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 handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

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

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

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

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

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

[0116] Figure 3 An example of a wireless communication system 300 that supports per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. The wireless communication system 300 can include a UE 115-b, which can be an example of a UE 115 as described herein. The wireless communication system 300 can include a network entity 105-a, which can be an example of a network entity 105 as described herein.

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

[0118] UE 115-b may be able to perform simultaneous communications with a first TRP 305-a and a second TRP 305-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 use communication link 125-b to communicate with the first base station TRP 305-a. UE 115-b may use communication link 125-c to communicate with the second base station TRP 305-b. Communication link 125-b and communication link 125-c may include bidirectional links that implement both uplink communication and downlink communication. For example, UE 115-b may use communication link 125-b to send an uplink signal such as an uplink control signal or an uplink data signal to the first TRP 305-a, and the first TRP 305-a may use communication link 125-b to send a downlink signal such as a downlink control signal or a downlink data signal to UE 115-b. UE 115-b may use communication link 125-c to send an uplink signal such as an uplink control signal or an uplink data signal to the second TRP 305-b, and the second TRP 305-b may use communication link 125-c to send a downlink signal 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 305-a and a second TRP 305-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.

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

[0120] UE 115-b may establish a communication link with network entity 105-b via a first TRP 305-a and a second TRP 305-b according to the SFN configuration. UE 115-b may determine a first uplink power level for a first uplink transmission 310-a to the first TRP 305-a and a second uplink power level for a second uplink transmission 310-b to the second TRP 305-b. In some cases, network entity 105-a may instruct UE 115-b by transmitting power management signaling (e.g., a DCI message 315 or control signaling 320) to support UE 115-b in determining the first uplink power level and the second uplink power level. UE 115-b may send a first uplink transmission 310-a to the first TRP 305-a according to the first uplink power level and send a second uplink transmission 310-b to the second TRP 305-b according to the second uplink power level.

[0121] In some cases, when UE 115-b is capable of SFN operation for one uplink channel (e.g., PUSCH or PUCCH), UE 115-b may be configured with two transmit power command fields in the corresponding DCI message 315 to indicate transmit power commands for SFN uplink transmissions (e.g., first uplink transmission 310-a and second uplink transmission 310-b). For example, the SFN uplink transmissions (e.g., first uplink transmission 310-a and second uplink transmission 310-b) may be PUSCH or PUCCH transmissions, and the DCI message 315 may schedule uplink transmissions (e.g., first uplink transmission 310-a and second uplink transmission 310-b). For example, DCI 0_0 or DCI 0_2 having two transmit power command fields may schedule PUSCH transmissions, or DCI 1_1 or 1_2 having two transmit power command fields may schedule PUCCH.

[0122] In some cases, the mapping between the two transmit power command fields in the TCI code point and the two uplink applicable TCI states may be determined by the order of the transmit power command fields and the two TCI states associated with the first 305-a and the second TRP 305-b. For example, the first transmit power command field may indicate the transmit power command for the first TCI state in the TCI code point, and the second transmit power command field may indicate the transmit power command for the second TCI state in the TCI code point. Therefore, the UE 115-b may map the two transmit power commands in the two transmit power command fields to the first TRP 305-a and the second TRP 305-b. In some cases, the mapping between the two transmit power command fields in the TCI code point and the two uplink applicable TCI states may be determined by the order of the transmit power command fields and the two closed-loop indexes of the two TCI states associated with the first 305-a and the second TRP 305-b. For example, for each transmit power command field, for each closed-loop index value, the first transmit power command field may indicate the transmit power command of the TCI state of the first closed-loop index in the TCI code point, and the second transmit power command field may indicate the transmit power command of the TCI state of the second closed-loop index in the TCI code point. In some cases, when two TCI states are indicated in the TCI code point and the two closed-loop indexes associated with the two TCI states are different, the second transmit power command field may be valid. In some cases where one TCI state is indicated in the TCI code point or where the two closed-loop indexes associated with the two TCI states are not different, the first transmit power command field may be valid and the second transmit power command field may be invalid, and the first transmit power command field may be applicable to one or both TCI states.

[0123] In some cases, when UE 115-b is capable of SFN operation for an uplink channel (e.g., PUSCH or PUCCH, both, or additional uplink channels), UE 115-b may be indicated using two sets of power control parameters for SFN uplink transmissions (e.g., first uplink transmission 310-a and second uplink transmission 310-b). For example, UE 115-b may identify a first set of power control parameters associated with a first TRP 305-a and a second set of power control parameters associated with a second TRP 305-b for SFN uplink transmissions (e.g., first uplink transmission 310-a and second uplink transmission 310-b) based on a first TCI state associated with a first TRP 305-a and a second TCI state associated with a second TRP 305-b. In some cases, the two sets of power control parameters may be included in two uplink applicable TCI states in a TCI code point. For example, based on a TCI code point including a first TCI state and a second TCI state, control signaling 320 (such as RRC signaling or MAC-CE signaling) may indicate that a first set of power control parameters is associated with the first TCI state and a second set of power control parameters is associated with the second TCI state.

[0124] In some cases, the control signaling 320 may indicate two sets of power control parameters for each uplink BWP in a set of multiple uplink BWPs. The UE 115-b may identify a first set of power control parameters associated with the first TRP 305-a and a second set of power control parameters associated with the second TRP 305-b based on the uplink BWPs associated with the first uplink transmission 310-a and the second identified uplink transmission 310-b in the set of multiple uplink BWPs. For example, based on the BWP, the first set of power control parameters may be applicable to a first TCI state in a TCI code point, and the second set of power control parameters may be applicable to a second TCI state in a TCI code point.

[0125] In some cases, the first set of power control parameters may be a default first set of power control parameters, and the second set of power control parameters may be a second set of default power control parameters. For example, UE 115-b may determine to apply the default first set of power control parameters and the default second set of power control parameters based on the power control parameters not being included in the TCI state. In some cases, the first set of default power control parameters may be applied to a first TCI state in a TCI code point, and the second set of default power control parameters may be applied to a second TCI state in the TCI code point. For example, the configuration parameter Uplink-powerControl of the lowest identifier in the component carrier may be applied to the first TCI state in the TCI code point, and the configuration parameter Uplink-powerControl of the second lowest identifier in the component carrier may be applied to the second TCI state in the TCI code point. For example, the configuration parameter Uplink-powerControl of the closed-loop index "0" with the lowest identifier in the component carrier can be applied to the TCI state of the closed-loop index "0" in the TCI code point, and the configuration parameter Uplink-powerControl of the closed-loop index "1" with the lowest identifier in the component carrier can be applied to the TCI state of the closed-loop index "1" in the TCI code point.

[0126] In some cases, when UE 115-b is capable of SFN operation for PUSCH, UE 115-b may be configured to report two power headroom reports for SFN-based PUSCH transmissions in a serving cell. For example, UE 115-b may send a message 325 to the network including two power headroom reports associated with a first TRP 305-a and a second TRP 305-b. In some cases, the network may send control signaling 330 to UE 115-b indicating that UE 115-b reports a first power headroom report associated with the first TRP 305-a and a second power headroom report associated with the second TRP 305-b. In some cases, UE 115-b may receive control signaling 320 indicating a first uplink power level for a first uplink transmission 310-a and a second uplink power level for a second uplink transmission 310-b in response to sending the message including the two power headroom reports.

[0127] In some cases, UE 115-b may receive control signaling 335 that schedules uplink transmissions (e.g., PUSCH transmissions) associated with two power headroom reports. If the control signaling 335 schedules non-SFN PUSCH transmissions, UE 115-b may report a real power headroom report and a virtual power headroom report. If the control signaling 335 schedules SFN PUSCH transmissions, UE 115-b may report two real power headroom reports. If UE 115-b is configured to report two power headroom reports without scheduling PUSCH transmissions, UE 115-b may report two virtual power headroom reports. When calculating the virtual power headroom reports, UE 115-b may assume that power control parameters (which may include PLRS, P-MPR, nominal transmit power, α or closed loop index) are associated with a unified TCI state related to the virtual power headroom reports.

[0128] In some cases, UE 115-b may be indicated using two sets of beam failure detection resources for beam failure recovery. For each BWP of a serving cell, UE 115-b UE may be provided by RRC configuration with a set q0 of periodic CSI-RS configuration indices, i.e., failureDetectionResourcesToAddModList, and provided with a set q1 of periodic CSI-RS configuration indices through radio link quality measurement on the BWP for the serving cell and / or a search space or physical broadcast channel (PBCH) block index provided by candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList. Instead of sets q0 and q1, for each BWP of the serving cell, the UE 115-b may be provided with corresponding two sets q0,0 and q0,1 of periodic CSI-RS resource configuration indices through failureDetectionSet1-r17 and failureDetectionSet2-r17 that may be activated by a MAC control element (CE) by RRC configuration and may be provided with corresponding two sets q1,0 and q1,1 of periodic CSI-RS resource configuration indices and / or search spaces or PBCH block indices through candidateBeamRSList1 and candidateBeamRSList2, respectively, for radio link quality measurement on the BWP of the serving cell. If the number of resources configured in each set q0,0 and q0,1 is equal to or less than the number of beam failure detection resources supported for measurement as indicated by the UE capability (e.g., the value "NBFD"), the UE 115-b may be deemed to measure the resources in each set q0,0 and q0,1. The set q0,0 may be associated with the set q1,0 and the set q0,1 may be associated with the set q1,1. The UE 115-b does not expect one of the sets q0,0 and q0,1 to be configured with more than the number of beam failure detection resources supported for measurement and the other set to be configured with less than or equal to the number of beam failure detection resources supported for measurement. In some aspects, this may apply to a UE 115-b configured with any downlink multi-TRP operation (single DCI-based or multi-DCI-based multi-TRP operation), and the uplink transmission may be configured with SFN transmission. In some other aspects, this may apply to a UE 115-b configured with any downlink multi-TRP operation (single DCI-based or multi-DCI-based multi-mTRP operation), and the uplink transmission may not be configured with SFN transmission.

[0129] Figure 4An example of a process flow 400 for supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated. The process flow 400 may include a UE 115-c, which may be an example of a UE 115 as described herein. The process flow 400 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 400, 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 different times. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0130] At 405, UE 115-c may establish a communication link with network entity 105-b via a first TRP and a second TRP in accordance with the SFN configuration. Establishing the communication link with network entity 105-b in accordance with the SFN configuration may include receiving a second set of parameter values ​​for uplink transmissions to the first TRP for a first set of antenna elements of UE 115-c and a second set of parameter values ​​for uplink transmissions to the second TRP for a second set of antenna elements of UE 115-c during the same set of time and frequency resources.

[0131] At 410, UE 115-c may determine a first uplink power level for a first uplink transmission to network entity 105-b via a first TRP and a second uplink power level for a second uplink transmission to network entity 105-b via a second TRP.

[0132] At 415, UE 115-c may send a first uplink transmission to a first TRP according to a first uplink power level and send a second uplink transmission to a second TRP according to a second uplink power level.

[0133] Figure 5An example of a process flow 500 for supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated. The process flow 500 may include a UE 115-d, which may be an example of a UE 115 as described herein. The process flow 500 may include a network entity 105-c, which may be an example of a network entity 105 as described herein. In the following description of the process flow 500, operations between the network entity 105-c and the UE 115-d may be sent in an order different from the example order shown, or operations performed by the network entity 105-c and the UE 115-d may be performed in a different order or at different times. Some operations may also be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0134] At 505, UE 115-d may establish a communication link with network entity 105-c via a first TRP and a second TRP according to the SFN configuration. Establishing a communication link with network entity 105-c according to the SFN configuration may include receiving a first set of parameter values ​​for uplink transmissions to the first TRP for a first set of antenna elements of UE 115-d and a second set of parameter values ​​for uplink transmissions to a second TRP for a second set of antenna elements of UE 115-d.

[0135] At 510, UE 115-d may receive a DCI message from network entity 105-c indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP.

[0136] At 515, UE 115-d may determine a first uplink power level for a first uplink transmission to network entity 105-c via a first TRP and a second uplink power level for a second uplink transmission to network entity 105-c via a second TRP based on the first transmit power command and the second transmit power command.

[0137] In some cases, UE 115-d may determine that a first field within a DCI message is associated with a first TCI state of a TCI code point and a second field is associated with a second TCI state of the TCI code point based at least in part on an order of a first field of the DCI message indicating a first transmit power command and a second field of the DCI message indicating a second transmit power command.

[0138] In some cases, UE 115-d may determine, at least in part based on an order of a first field of the DCI message indicating a first transmit power command and a second field of the DCI message indicating a second transmit power command, that a first field within the DCI message is associated with a first TCI state for a first closed-loop index in the TCI code point and a second field is associated with a second TCI state for a second closed-loop index in the TCI code point.

[0139] At 520, UE 115-d may send a first uplink transmission to the first TRP according to the first uplink power level and send a second uplink transmission to the second TRP according to the second uplink power level.

[0140] Figure 6 An example of a process flow 600 for supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated. The process flow 600 may include a UE 115-e, which may be an example of a UE 115 as described herein. The process flow 600 may include a network entity 105-d, 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-d and the UE 115-e may be sent in an order different from the example order shown, or operations performed by the network entity 105-d and the UE 115-e may be performed in a different order or at different times. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0141] At 605, UE 115-e may establish a communication link with network entity 105-d via a first TRP and a second TRP according to the SFN configuration. Establishing a communication link with network entity 105-d according to the SFN configuration may include receiving a first set of parameter values ​​for uplink transmissions to the first TRP for a first set of antenna elements of UE 115-d and a second set of parameter values ​​for uplink transmissions to the second TRP for a second set of antenna elements of UE 115-e.

[0142] At 615, UE 115-e may identify a first set of power control parameters associated with the first TRP and a second set of power control parameters associated with the second TRP based on a first TCI state associated with the first TRP and a second TCI state associated with the second TRP.

[0143] In some cases, at 610, UE 115-e may receive control signaling from network entity 105-d indicating a first set of power control parameters and a second set of power control parameters. In some examples, based on a TCI code point including a first TCI state and a second TCI state, the control signaling may indicate that the first set of power control parameters is associated with the first TCI state and the second set of power control parameters is associated with the second TCI state.

[0144] In some cases, the control signaling may indicate two sets of power control parameters for each uplink BWP in a set of multiple uplink BWPs. The UE 115-e may identify a first set of power control parameters associated with a first TRP and a second set of power control parameters associated with a second TRP based on the uplink BWPs in the set of multiple uplink BWPs associated with the first uplink transmission and the second uplink transmission.

[0145] In some cases, the first set of power control parameters may be a default first set of power control parameters and the second set of power control parameters may be a default second set of power control parameters. For example, the UE 115-e may determine to apply the default first set of power control parameters and the default second set of power control parameters based on not receiving control signaling indicating the first set of power control parameters and the second set of power control parameters.

[0146] At 620, UE 115-e may determine a first uplink power level for a first uplink transmission to network entity 105-d via a first TRP and a second uplink power level for a second uplink transmission to network entity 105-d via a second TRP based on the first set of power control parameters identified at 515 and the second set of power control parameters.

[0147] At 625, UE 115-e may send a first uplink transmission to a first TRP based on a first uplink power level and send a second uplink transmission to a second TRP based on a second uplink power level.

[0148] Figure 7An example of a process flow 700 for supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is illustrated. The process flow 700 may include a UE 115-f, which may be an example of a UE 115 as described herein. The process flow 700 may include a network entity 105-e, which may be an example of a network entity 105 as described herein. In the following description of the process flow 700, operations between the network entity 105-e and the UE 115-f may be sent in an order different from the example order shown, or operations performed by the network entity 105-e and the UE 115-f may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 700, and other operations may be added to the process flow 700.

[0149] At 705, UE 115-f may establish a communication link with network entity 105-d via a first TRP and a second TRP according to the SFN configuration. Establishing a communication link with network entity 105-e according to the SFN configuration may include receiving a first set of parameter values ​​for uplink transmissions to the first TRP for a first set of antenna elements of UE 115-f and a second set of parameter values ​​for uplink transmissions to a second TRP for a second set of antenna elements of UE 115-f.

[0150] In some cases, at 710, UE 115-f may receive control signaling from network entity 105-e instructing UE 115-f to report a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP.

[0151] At 715, UE 115-f may send a message to network entity 105-e including a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP. In some cases, UE 115-f may receive control signaling that schedules uplink transmissions using a SFN configuration, and the first power headroom report and the second power headroom report may be real power headroom reports associated with the uplink transmissions. In some cases, UE 115-f may receive control signaling that schedules uplink transmissions using a transmission configuration that is different from the SFN configuration, and the first power headroom report may be a real power headroom report associated with the uplink transmission, and the second power headroom report may be a virtual power headroom report. In some cases, UE 115-f may not receive scheduling information for uplink transmissions associated with the first TRP or the second TRP, and the first power headroom report and the second power headroom report may be virtual power headroom reports.

[0152] In some cases, at 720, UE 115-f may receive control signaling from network entity 105-e indicating a first uplink power level for first uplink transmissions to network entity 105-e via a first TRP and a second uplink power level for second uplink transmissions to network entity 105-e via the first TRP. In some cases, the first uplink power level and the second uplink power level may be based on the first power headroom report and the second power headroom report.

[0153] At 725, UE 115-f may send a first uplink transmission to a first TRP based on a first uplink power level and send a second uplink transmission to a second TRP based on a second uplink power level.

[0154] Figure 8 A block diagram 800 of a device 805 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 805 can be an example of aspects of the 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 one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which instructions are executable by the one or more processors to enable the one or more processors to perform the [Broad Title Features] features discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

[0155] The receiver 810 may provide means for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to per-TRP power control for uplink SFN operation), such as packets, user data, control information, or a combination thereof. 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.

[0156] 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 associated with various information channels (e.g., control channels, data channels, information channels related to per-TRP power control for uplink SFN operation), such as packets, user data, control information, or any combination thereof. 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.

[0157] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0161] According to the examples disclosed herein, the communication manager 820 may support wireless communications at the UE. For example, the communication manager 820 may be configured to or otherwise support components for establishing a communication link with the network via a first TRP and a second TRP according to an SFN configuration. The communication manager 820 may be configured to or otherwise support components for determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP. The communication manager 820 may be configured to or otherwise support components for sending a first uplink transmission to the first TRP according to the first uplink power level and sending a second uplink transmission to the second TRP according to the second uplink power level.

[0162] By including or configuring a communication manager 820 according to the examples described herein, the device 805 (e.g., a processor controlling the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof or otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources by configuring per-TRP power control for SFN uplink transmissions, etc.

[0163] Fig. 9 A block diagram 900 of a device 905 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] The receiver 910 may provide means for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to per-TRP power control for uplink SFN operation), such as packets, user data, control information, or a combination thereof. The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

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

[0166] The device 905 or its various components may be examples of components for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, the communication manager 920 may include a multi-TRP communication link manager 925, an uplink power level manager 930, an uplink transmission manager 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0167] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The multi-TRP communication link manager 925 may be configured to or otherwise support components for establishing a communication link with the network via a first TRP and a second TRP according to the SFN configuration. The uplink power level manager 930 may be configured to or otherwise support components for determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP. The uplink transmission manager 935 may be configured to or otherwise support components for transmitting a first uplink transmission to the first TRP according to the first uplink power level and transmitting a second uplink transmission to the second TRP according to the second uplink power level.

[0168] In some cases, the multi-TRP communication link manager 925, the uplink power level manager 930, and the uplink transmission manager 935 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the multi-TRP communication link manager 925, the uplink power level manager 930, and the uplink transmission manager 935 discussed herein. The transceiver processor may be co-located with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be co-located with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, an LTE radio, a Wi-Fi radio). The transmitter processor may be co-located with and / or communicate with (e.g., direct the operation of) the transmitter of the device. The receiver processor may be co-located with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0169] Fig.10 A block diagram 1000 of a communication manager 1020 supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, the communication manager 1020 may include a multi-TRP communication link manager 1025, an uplink power level manager 1030, an uplink transmit manager 1035, a transmit power command manager 1040, an uplink power control parameter manager 1045, a power headroom report manager 1050, an SFN manager 1055, an uplink transmit schedule manager 1060, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0170] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The multi-TRP communication link manager 1025 may be configured to or otherwise support components for establishing a communication link with the network via a first TRP and a second TRP according to the SFN configuration. The uplink power level manager 1030 may be configured to or otherwise support components for determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP. The uplink transmission manager 1035 may be configured to or otherwise support components for transmitting a first uplink transmission to the first TRP according to the first uplink power level and transmitting a second uplink transmission to the second TRP according to the second uplink power level.

[0171] In some examples, the transmit power command manager 1040 may be configured to or otherwise support components for receiving a DCI message indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP, wherein determining the first uplink power level and the second uplink power level is based on the first transmit power command and the second transmit power command.

[0172] In some examples, the transmit power command manager 1040 may be configured to or otherwise support components for determining that a first field is associated with a first TCI state of a TCI code point and a second field is associated with a second TCI state of the TCI code point based on an order of a first field indicating a first transmit power command and a second field indicating a second transmit power command within a DCI message.

[0173] In some examples, the transmit power command manager 1040 may be configured to or otherwise support components for determining, based on an order of a first field indicating a first transmit power command and a second field indicating a second transmit power command within a DCI message, that a first field is associated with a first TCI state for a first closed-loop index in a TCI code point and that a second field is associated with a second TCI state for a second closed-loop index in a TCI code point.

[0174] In some examples, the uplink power control parameter manager 1045 may be configured to or otherwise support components for identifying a first set of power control parameters associated with a first TRP and a second set of power control parameters associated with a second TRP based on a first TCI state associated with the first TRP and a second TCI state associated with the second TRP, wherein determining a first uplink power level for a first uplink transmission and a second uplink power level for a second uplink transmission is based on the first set of power control parameters and the second set of power control parameters.

[0175] In some examples, the uplink power control parameter manager 1045 may be configured to or otherwise support components for receiving control signaling indicating that a first set of power control parameters is associated with the first TCI state and a second set of power control parameters is associated with the second TCI state based on a TCI code point including a first TCI state and a second TCI state.

[0176] In some examples, the uplink power control parameter manager 1045 may be configured to or otherwise support components for receiving control signaling indicating two sets of power control parameters for each uplink BWP in a set of multiple uplink BWPs, where the identification is based on an uplink BWP in the set of multiple uplink BWPs associated with a first uplink transmission and a second uplink transmission.

[0177] In some examples, the first set of power control parameters includes a default first set of power control parameters, and the second set of power control parameters includes a default second set of power control parameters.

[0178] In some examples, the power headroom report manager 1050 may be configured or otherwise support components for sending a message including a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP.

[0179] In some examples, the power headroom report manager 1050 may be configured or otherwise support components for receiving control signaling instructing the UE to report a first power headroom report and a second power headroom report.

[0180] In some examples, the uplink transmission scheduling manager 1060 may be configured as or otherwise support components for receiving control signaling for scheduling uplink transmissions using an SFN configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmissions.

[0181] In some examples, the uplink transmission scheduling manager 1060 may be configured to or otherwise support components for receiving control signaling for scheduling uplink transmissions using a transmission configuration different from a SFN configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission and the second power headroom report includes a virtual power headroom report.

[0182] In some examples, to support establishing a communication link with a network based on an SFN configuration, the SFN manager 1055 may be configured as or otherwise support components for receiving a first set of parameter values ​​for uplink transmissions to a first TRP for a first set of antenna elements for the UE and a second set of parameter values ​​for uplink transmissions to a second TRP for a second set of antenna elements for the UE during the same set of time and frequency resources.

[0183] In some cases, the multi-TRP communication link manager 1025, the uplink power level manager 1030, the uplink transmission manager 1035, the transmission power command manager 1040, the uplink power control parameter manager 1045, the power headroom report manager 1050, the SFN manager 1055, and the uplink transmission scheduling manager 1060 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory, which enable the processor to perform or facilitate the features of the multi-TRP communication link manager 1025, the uplink power level manager 1030, the uplink transmission manager 1035, the transmission power command manager 1040, the uplink power control parameter manager 1045, the power headroom report manager 1050, the SFN manager 1055, and the uplink transmission scheduling manager 1060 discussed herein.

[0184] Fig.11 A diagram of a system 1100 including a device 1105 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include components thereof. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

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

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

[0187] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 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 1135 may not be directly executable by the processor 1140, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, the memory 1130 may also contain, 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.

[0188] The processor 1140 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 1140 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 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to enable the device 1105 to perform various functions (e.g., functions or tasks that support per-TRP power control for uplink SFN operation). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or coupled to the processor 1140, and the processor 1140 and the memory 1130 are configured to perform the various functions described herein.

[0189] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. For example, the communication manager 1120 may be configured to or otherwise support components for establishing a communication link with the network via a first TRP and a second TRP according to the SFN configuration. The communication manager 1120 may be configured to or otherwise support components for determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP. The communication manager 1120 may be configured to or otherwise support components for sending a first uplink transmission to the first TRP according to the first uplink power level and sending a second uplink transmission to the second TRP according to the second uplink power level.

[0190] By including or configuring a communication manager 1120 according to examples as described herein, the device 1105 may support techniques for more efficiently utilizing communication resources and improving coordination between devices by configuring per-TRP power control for SFN uplink transmissions.

[0191] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions that are executable by the processor 1140 to cause the device 1105 to perform various aspects of per-TRP power control for uplink SFN operation as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0192] Fig.12 A block diagram 1200 of a device 1205 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the 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 one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which instructions may be executed by the one or more processors to enable the one or more processors to perform the [Broad Title Features] features discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).

[0193] The 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 passed to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the 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.

[0194] 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 the modem.

[0195] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0199] According to the examples disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support components for establishing a communication link with a UE via a first TRP and a second TRP according to an SFN configuration. The communication manager 1220 may be configured to or otherwise support components for sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP. The communication manager 1220 may be configured to or otherwise support components for receiving a first uplink transmission from the UE via a first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to the second uplink power level, at least in part in response to the sent power management signaling.

[0200] By including or configuring a communication manager 1220 according to the examples described herein, the device 1205 (e.g., a processor controlling the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof or otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources by configuring per-TRP power control for SFN uplink transmissions, etc.

[0201] Fig.13 A block diagram 1300 of a device 1305 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0204] Device 1305 or its various components may be examples of components for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, communication manager 1320 may include a multi-TRP communication link manager 1325, an uplink power management signaling manager 1330, an uplink transmission manager 1335, or any combination thereof. Communication manager 1320 may be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated in combination with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0205] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a network entity. The multi-TRP communication link manager 1325 may be configured to or otherwise support components for establishing a communication link with a UE via a first TRP and a second TRP according to an SFN configuration. The uplink power management signaling manager 1330 may be configured to or otherwise support components for sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP. The uplink transmission manager 1335 may be configured to or otherwise support components for receiving a first uplink transmission from the UE via a first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to the second uplink power level, at least in part in response to the sent power management signaling.

[0206] In some cases, the multi-TRP communication link manager 1325, the uplink power management signaling manager 1330, and the uplink transmission manager 1335 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory, which enable the processor to perform or facilitate the features of the multi-TRP communication link manager 1325, the uplink power management signaling manager 1330, and the uplink transmission manager 1335 discussed herein. The transceiver processor may be co-located with and / or communicate with the transceiver of the device (e.g., direct its operation). The radio processor may be co-located with and / or communicate with the radio of the device (e.g., NR radio, LTE radio, Wi-Fi radio) (e.g., direct the operation of the radio). The transmitter processor may be co-located with and / or communicate with the transmitter of the device (e.g., direct its operation). The receiver processor may be co-located with and / or communicate with the receiver of the device (e.g., direct its operation).

[0207] Fig.14A block diagram 1400 of a communication manager 1420 supporting per-TRP power control for uplink SFN operation in accordance with one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of means for performing various aspects of per-TRP power control for uplink SFN operation as described herein. For example, the communication manager 1420 may include a multi-TRP communication link manager 1425, an uplink power management signaling manager 1430, an uplink transmit manager 1435, a transmit power command manager 1440, an uplink power control parameter manager 1445, a power headroom report manager 1450, an uplink transmit scheduling manager 1455, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0208] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a network entity. The multi-TRP communication link manager 1425 may be configured to or otherwise support components for establishing a communication link with a UE via a first TRP and a second TRP according to an SFN configuration. The uplink power management signaling manager 1430 may be configured to or otherwise support components for sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP. The uplink transmission manager 1435 may be configured to or otherwise support components for receiving a first uplink transmission from the UE via a first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to the second uplink power level, at least in part in response to the sent power management signaling.

[0209] In some examples, to support transmit power management signaling, transmit power command manager 1440 may be configured as or otherwise support components for sending a DCI message indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP.

[0210] In some examples, to support sending a DCI message, the transmit power command manager 1440 may be configured to or otherwise support components for sending a DCI message including a first field indicating that a first transmit power command is associated with a first TCI state of a TCI code point and a second field indicating that a second transmit power command is associated with a second TCI state of the TCI code point, wherein based on an order of the first field and the second field within the DCI message, the first TRP is associated with the first TCI state and the second TRP is associated with the second TCI state.

[0211] In some examples, to support sending a DCI message, the transmit power command manager 1440 may be configured to or otherwise support components for sending a DCI message including a first field indicating that a first transmit power command is associated with a first TCI state with a first closed-loop index in a TCI code point and a second field indicating that a second transmit power command is associated with a second TCI state with a second closed-loop index in the TCI code point, wherein based on an order of the first field and the second field within the DCI message, the first TRP is associated with the first TCI state and the second TRP is associated with the second TCI state.

[0212] In some examples, to support sending power management signaling, the uplink power control parameter manager 1445 may be configured as or otherwise support components for sending control signaling indicating that a first set of power control parameters is associated with a first TCI state and a second set of power control parameters is associated with a second TCI state based on a TCI code point including a first TCI state and a second TCI state, wherein the first TCI state is associated with a first TRP and the second TCI state is associated with a second TRP.

[0213] In some examples, to support sending power management signaling, the uplink power control parameter manager 1445 may be configured as or otherwise support components for sending control signaling indicating two sets of power control parameters for each uplink BWP in a set of multiple uplink BWPs, where the uplink BWPs in the set of multiple uplink BWPs are associated with a first uplink transmission and a second uplink transmission.

[0214] In some examples, the power headroom report manager 1450 may be configured as or otherwise support components for receiving a message from a UE including a first power headroom report associated with a first TRP and a second power headroom report associated with a second TRP.

[0215] In some examples, to support transmission power management signaling, uplink transmission manager 1435 may be configured or otherwise support components for transmitting control signaling indicating a first uplink power level and a second uplink power level.

[0216] In some examples, the power headroom report manager 1450 may be configured or otherwise support components for sending control signaling to the UE instructing the UE to report a first power headroom report and a second power headroom report.

[0217] In some examples, the uplink transmission scheduling manager 1455 may be configured as or otherwise support components for sending control signaling to the UE to schedule uplink transmissions using a SFN configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmissions.

[0218] In some examples, the uplink transmission scheduling manager 1455 may be configured as or otherwise support components for sending control signaling to a UE to schedule uplink transmissions using a transmission configuration different from a SFN configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission and the second power headroom report includes a virtual power headroom report.

[0219] In some cases, the multi-TRP communication link manager 1425, the uplink power management signaling manager 1430, the uplink transmission manager 1435, the transmission power command manager 1440, the uplink power control parameter manager 1445, the power headroom report manager 1450, and the uplink transmission scheduling manager 1455 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory, which enable the processor to perform or facilitate the features of the multi-TRP communication link manager 1425, the uplink power management signaling manager 1430, the uplink transmission manager 1435, the transmission power command manager 1440, the uplink power control parameter manager 1445, the power headroom report manager 1450, and the uplink transmission scheduling manager 1455 discussed herein.

[0220] Fig.15A diagram of a system 1500 including a device 1505 supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The device 1505 can be an example of a device 1205, a device 1305, or a network entity 105 as described herein, or include components thereof. The device 1505 can 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 1505 may include components that support output and acquisition of communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, a code 1530, and a processor 1535. 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 1540).

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

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

[0223] Processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1535. Processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to enable device 1505 to perform various functions (e.g., functions or tasks that support per-TRP power control for uplink SFN operation). For example, device 1505 or a component of device 1505 may include processor 1535 and memory 1525 coupled to processor 1535, and processor 1535 and memory 1525 are configured to perform various functions described herein. Processor 1535 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality (e.g., by executing code 1530) to perform the functions of device 1505.

[0224] In some examples, bus 1540 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1505 or communications performed between different components of device 1505 that may be co-located or located in different locations (e.g., where device 1505 may refer to a system, where one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of the different components or divided between the different components).

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

[0226] According to the examples disclosed herein, the communication manager 1520 may support wireless communications at a network entity. For example, the communication manager 1520 may be configured to or otherwise support components for establishing a communication link with a UE via a first TRP and a second TRP according to an SFN configuration. The communication manager 1520 may be configured to or otherwise support components for sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP. The communication manager 1520 may be configured to or otherwise support components for receiving a first uplink transmission from the UE via a first TRP according to the first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to the second uplink power level, at least in part in response to the sent power management signaling.

[0227] By including or configuring a communication manager 1520 according to examples as described herein, device 1505 may support techniques for more efficiently utilizing communication resources and improving coordination between devices by configuring per-TRP power control for SFN uplink transmissions.

[0228] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the processor 1535, the memory 1525, the code 1530, the transceiver 1510, or any combination thereof. For example, the code 1530 may include instructions that are executable by the processor 1535 to cause the device 1505 to perform various aspects of per-TRP power control for uplink SFN operation as described herein, or the processor 1535 and the memory 1525 may be otherwise configured to perform or support such operations.

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

[0230] At 1605, the method may include establishing a communication link with the network via the first TRP and the second TRP according to the SFN configuration. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.10 The multi-TRP communication link manager 1025 is used to execute.

[0231] At 1610, the method may include determining a first uplink power level for a first uplink transmission to a network via a first TRP and a second uplink power level for a second uplink transmission to a network via a second TRP. 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.10 The uplink power level manager 1030 is executed.

[0232] At 1615, the method may include sending a first uplink transmission to a first TRP according to a first uplink power level, and sending a second uplink transmission to a second TRP according to a second uplink power level. 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.10 The uplink transmission manager 1035 is used to execute.

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

[0234] At 1705, the method may include establishing a communication link with the network via the first TRP and the second TRP according to the SFN configuration. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.10 The multi-TRP communication link manager 1025 is used to execute.

[0235] At 1710, the method may include receiving a DCI message indicating a first transmit power command associated with a first TRP and a second transmit power command associated with a second TRP. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.10 The transmit power command manager 1040 is used to execute.

[0236] At 1715, the method may include determining a first uplink power level for a first uplink transmission to a network via a first TRP and a second uplink power level for a second uplink transmission to a network via a second TRP, wherein determining the first uplink power level and the second uplink power level is based on a first transmit power command and a second transmit power command. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.10 The uplink power level manager 1030 is executed.

[0237] At 1720, the method may include sending a first uplink transmission to a first TRP according to a first uplink power level, and sending a second uplink transmission to a second TRP according to a second uplink power level. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig.10 The uplink transmission manager 1035 is used to execute.

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

[0239] At 1805, the method may include establishing a communication link with the network via the first TRP and the second TRP according to the SFN configuration. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.10 The multi-TRP communication link manager 1025 is used to execute.

[0240] At 1810, the method may include identifying a first set of power control parameters associated with the first TRP and a second set of power control parameters associated with the second TRP based on a first TCI state associated with the first TRP and a second TCI state associated with the second TRP. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.10 The uplink power control parameter manager 1045 is used to perform the above operation.

[0241] At 1815, the method may include determining a first uplink power level for a first uplink transmission to a network via a first TRP and a second uplink power level for a second uplink transmission to a network via a second TRP, wherein determining the first uplink power level for the first uplink transmission and the second uplink power level for the second uplink transmission is based on a first set of power control parameters and a first set of power control parameters. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.10 The uplink power level manager 1030 is executed.

[0242] At 1820, the method may include sending a first uplink transmission to a first TRP according to a first uplink power level, and sending a second uplink transmission to a second TRP according to a second uplink power level. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.10 The uplink transmission manager 1035 is used to execute.

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

[0244] At 1905, the method may include establishing a communication link with the network via the first TRP and the second TRP according to the SFN configuration. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.10 The multi-TRP communication link manager 1025 is used to execute.

[0245] At 1910, the method may include determining a first uplink power level for a first uplink transmission to a network via a first TRP and a second uplink power level for a second uplink transmission to a network via a second TRP. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.10 The uplink power level manager 1030 is executed.

[0246] At 1915, the method may include sending a message including a first power headroom report associated with the first TRP and a second power headroom report associated with the second TRP. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.10 The power headroom reporting manager 1050 is used to perform the above operations.

[0247] At 1920, the method may include sending a first uplink transmission to a first TRP according to a first uplink power level, and sending a second uplink transmission to a second TRP according to a second uplink power level. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.10 The uplink transmission manager 1035 is used to execute.

[0248] Fig. 20 A flow chart illustrating a method 2000 for supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 7 as well as Figures 12 to 15 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.

[0249] At 2005, the method may include establishing a communication link with the UE via the first TRP and the second TRP according to the SFN configuration. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.14 The multi-TRP communication link manager 1425 is used to execute.

[0250] At 2010, the method may include sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to a first TRP and a second uplink power level for a second uplink transmission to a second TRP. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.14 The uplink power management signaling manager 1430 is used for execution.

[0251] At 2015, the method may include receiving a first uplink transmission from the UE via a first TRP according to a first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to a second uplink power level at least in part in response to the transmitted power management signaling. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.14 The uplink transmission manager 1435 is used to execute.

[0252] Fig.21A flow chart illustrating a method 2100 for supporting per-TRP power control for uplink SFN operation according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 7 as well as Figures 12 to 15 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.

[0253] At 2105, the method may include establishing a communication link with the UE via the first TRP and the second TRP according to the SFN configuration. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.14 The multi-TRP communication link manager 1425 is used to execute.

[0254] At 2110, the method may include sending power management signaling to the UE, the power management signaling configured to support the UE in determining a first uplink power level for a first uplink transmission to a first TRP and a second uplink power level for a second uplink transmission to a second TRP. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.14 The uplink power management signaling manager 1430 is used for execution.

[0255] At 2115, the method may include receiving a message from the UE including a first power headroom report associated with the first TRP and a second power headroom report associated with the second TRP. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.14 The power headroom reporting manager 1450 is used to perform the above.

[0256] At 2120, the method may include receiving a first uplink transmission from the UE via a first TRP according to a first uplink power level and receiving a second uplink transmission from the UE via a second TRP according to a second uplink power level at least in part in response to the transmitted power management signaling. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.14 The uplink transmission manager 1435 is used to execute.

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

[0258] Aspect 1: A method for performing wireless communications at a UE, comprising: establishing a communication link with a network via a first TRP and a second TRP according to an SFN configuration; determining a first uplink power level for a first uplink transmission to the network via the first TRP and a second uplink power level for a second uplink transmission to the network via the second TRP; and sending a first uplink transmission to the first TRP according to the first uplink power level, and sending the second uplink transmission to the second TRP according to the second uplink power level.

[0259] Aspect 2: The method according to Aspect 1 also includes: receiving a DCI message indicating a first transmit power command associated with the first TRP and a second transmit power command associated with the second TRP, wherein determining the first uplink power level and the second uplink power level is at least partially based on the first transmit power command and the second transmit power command.

[0260] Aspect 3: The method according to Aspect 2 also includes: determining that the first field is associated with the first TCI state of the TCI code point and the second field is associated with the second TCI state of the TCI code point based at least in part on the order of the first field indicating the first transmit power command and the second field indicating the second transmit power command within the DCI message.

[0261] Aspect 4: The method according to any one of Aspects 2 to 3 also includes: determining that the first field indicating the first transmit power command and the second field indicating the second transmit power command within the DCI message are associated with a first TCI state of a first closed-loop index in a TCI code point and that the second field is associated with a second TCI state of a second closed-loop index in the TCI code point, at least in part based on the order of the first field indicating the first transmit power command and the second field indicating the second transmit power command within the TCI message.

[0262] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: identifying a first set of power control parameters associated with the first TRP and a second set of power control parameters associated with the second TRP based at least in part on a first TCI state associated with the first TRP and a second TCI state associated with the second TRP, wherein determining the first uplink power level for the first uplink transmission and the second uplink power level for the second uplink transmission is at least in part based on the first set of power control parameters and the second set of power control parameters.

[0263] Aspect 6: The method according to Aspect 5 also includes: receiving control signaling indicating that the first set of power control parameters is associated with the first TCI state and the second set of power control parameters is associated with the second TCI state, at least in part based on a TCI code point including the first TCI state and the second TCI state.

[0264] Aspect 7: The method according to any one of Aspects 5 to 6 further includes: receiving control signaling indicating two sets of power control parameters for each of a plurality of uplink bandwidth parts, wherein the identification is at least partially based on an uplink bandwidth part of the plurality of uplink bandwidth parts associated with the first uplink transmission and the second uplink transmission.

[0265] Aspect 8: The method according to any one of aspects 5 to 7, wherein the first set of power control parameters comprises a default first set of power control parameters, and the second set of power control parameters comprises a second set of default power control parameters.

[0266] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: sending a message including a first power headroom report associated with the first TRP and a second power headroom report associated with the second TRP.

[0267] Aspect 10: The method according to aspect 9 further includes: receiving control signaling instructing the UE to report the first power headroom report and the second power headroom report.

[0268] Aspect 11: The method according to any one of Aspects 9 to 10 further includes: receiving control signaling for scheduling uplink transmission using the SFN configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmission.

[0269] Aspect 12: The method according to any one of Aspects 9 to 11 further includes: receiving control signaling for scheduling uplink transmission using a transmission configuration different from the SFN configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission, and the second power headroom report includes a virtual power headroom report.

[0270] Aspect 13: A method according to any one of Aspects 1 to 12, wherein establishing the communication link with the network according to the SFN configuration includes: receiving a first set of parameter values ​​for uplink transmission to the first TRP for a first set of antenna elements for the UE and a second set of parameter values ​​for uplink transmission to the second TRP for a second set of antenna elements for the UE during the same set of time and frequency resources.

[0271] Aspect 14: A method for performing wireless communications at a network entity, comprising: establishing a communication link with a UE via a first TRP and a second TRP according to an SFN configuration; sending power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first TRP and a second uplink power level for a second uplink transmission to the second TRP; and receiving the first uplink transmission from the UE via the first TRP according to the first uplink power level and receiving the second uplink transmission from the UE via the second TRP according to the second uplink power level at least partially in response to the sent power management signaling.

[0272] Aspect 15: The method according to Aspect 14, wherein sending the power management signaling includes: sending a DCI message indicating a first transmit power command associated with the first TRP and a second transmit power command associated with the second TRP.

[0273] Aspect 16: A method according to Aspect 15, wherein sending the DCI message includes: sending the DCI message including a first field indicating that the first transmit power command is associated with a first TCI state of a TCI code point and a second field indicating that the second transmit power command is associated with a second TCI state of the TCI code point, wherein the first TRP is associated with the first TCI state and the second TRP is associated with the second TCI state based at least in part on an order of the first field and the second field within the DCI message.

[0274] Aspect 17: A method according to any one of Aspects 15 to 16, wherein sending the DCI message includes: sending the DCI message including a first field indicating that the first transmit power command is associated with a first TCI state of a first closed-loop index in a TCI code point and a second field indicating that the second transmit power command is associated with a second TCI state of a second closed-loop index in the TCI code point, wherein the first TRP is associated with the first TCI state and the second TRP is associated with the second TCI state based at least in part on an order of the first field and the second field within the DCI message.

[0275] Aspect 18: A method according to any one of Aspects 14 to 17, wherein sending the power management signaling includes: sending control signaling indicating that a first set of power control parameters is associated with the first TCI state and a second set of power control parameters is associated with the second TCI state based at least in part on a TCI code point including a first TCI state and a second TCI state, wherein the first TCI state is associated with the first TRP and the second TCI state is associated with the second TRP.

[0276] Aspect 19: A method according to any one of Aspects 14 to 18, wherein sending the power management signaling includes: sending control signaling indicating two sets of power control parameters for each uplink bandwidth part in a plurality of uplink bandwidth parts, wherein the uplink bandwidth parts in the plurality of uplink bandwidth parts are associated with the first uplink transmission and the second uplink transmission.

[0277] Aspect 20: The method according to any one of Aspects 14 to 19 also includes: receiving a message from the UE including a first power headroom report associated with the first TRP and a second power headroom report associated with the second TRP.

[0278] Aspect 21: The method according to aspect 20, wherein sending the power management signaling includes: sending control signaling indicating the first uplink power level and the second uplink power level.

[0279] Aspect 22: The method according to any one of Aspects 20 to 21 further includes: sending control signaling to the UE instructing the UE to report the first power headroom report and the second power headroom report.

[0280] Aspect 23: The method according to any one of Aspects 20 to 22 further includes: sending control signaling to the UE using the SFN configuration to schedule uplink transmission, wherein the first power headroom report and the second power headroom report include a true power headroom report associated with the uplink transmission.

[0281] Aspect 24: The method according to any one of Aspects 20 to 23 further includes: sending control signaling to the UE for scheduling uplink transmission using a transmission configuration different from the SFN configuration, wherein the first power headroom report includes a real power headroom report associated with the uplink transmission, and the second power headroom report includes a virtual power headroom report.

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

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

[0284] Aspect 27: 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 13.

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

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

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

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

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

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

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

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

[0293] Computer-readable media include both non-transient computer storage media and communication media, including any medium that promotes the transfer of computer programs from one place to another.Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, disk storage or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor.In addition, any connection is appropriately referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable media. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0295] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as via searching in a table, database, or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establishing a communication link with the network via the first sending and receiving point and the second sending and receiving point according to the SFN configuration; determining a first uplink power level for a first uplink transmission to the network via the first transmission and reception point and a second uplink power level for a second uplink transmission to the network via the second transmission and reception point; as well as The first uplink transmission is transmitted to the first transmission and reception point according to the first uplink power level, and the second uplink transmission is transmitted to the second transmission and reception point according to the second uplink power level.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Receive a DCI message indicating a first transmit power command associated with the first transmit and receive point and a second transmit power command associated with the second transmit and receive point, wherein determining the first uplink power level and the second uplink power level is at least partially based on the first transmit power command and the second transmit power command.

3. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: At least in part based on an order of a first field indicating the first transmit power command and a second field indicating the second transmit power command within the DCI message, determining that the first field is associated with a first transmit configuration indicator state of a transmit configuration indicator code point and the second field is associated with a second transmit configuration indicator state of the transmit configuration indicator code point.

4. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: At least in part based on an order of a first field indicating the first transmit power command and a second field indicating the second transmit power command within the DCI message, determining that the first field is associated with a first transmit configuration indicator state of a first closed-loop index in a transmit configuration indicator code point and the second field is associated with a second transmit configuration indicator state of a second closed-loop index in the transmit configuration indicator code point.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A first set of power control parameters associated with the first transmit and receive point and a second set of power control parameters associated with the second transmit and receive point are identified at least in part based on a first transmit configuration indicator state associated with the first transmit and receive point and a second transmit configuration indicator state associated with the second transmit and receive point, wherein the first uplink power level for the first uplink transmission and the second uplink power level for the second uplink transmission are determined at least in part based on the first set of power control parameters and the second set of power control parameters.

6. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is received that indicates, based at least in part on a transmit configuration indicator code point including the first transmit configuration indicator state and the second transmit configuration indicator state, that a first set of power control parameters is associated with the first transmit configuration indicator state and a second set of power control parameters is associated with the second transmit configuration indicator state.

7. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is received indicating two sets of power control parameters for each of a plurality of uplink bandwidth parts, wherein the identification is based at least in part on an uplink bandwidth part of the plurality of uplink bandwidth parts associated with the first uplink transmission and the second uplink transmission.

8. The apparatus of claim 5, wherein the first set of power control parameters comprises a default first set of power control parameters, and the second set of power control parameters comprises a default second set of power control parameters.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A message is transmitted including a first power headroom report associated with the first transmit and receive point and a second power headroom report associated with the second transmit and receive point.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is received to instruct the UE to report the first power headroom report and the second power headroom report.

11. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is received to schedule an uplink transmission using the SFN configuration, wherein the first power headroom report and the second power headroom report comprise true power headroom reports associated with the uplink transmission.

12. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is received to schedule an uplink transmission using a transmission configuration different from the SFN configuration, wherein the first power headroom report comprises a real power headroom report associated with the uplink transmission and the second power headroom report comprises a virtual power headroom report.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to establish the communication link with the network according to the SFN configuration by being executable by the processor to: A first set of parameter values ​​for uplink transmission to the first transmit and receive point for a first set of antenna elements for the UE and a second set of parameter values ​​for uplink transmission to the second transmit and receive point for a second set of antenna elements for the UE are received during the same set of time and frequency resources.

14. An apparatus for wireless communication at a network entity, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establishing a communication link with a user equipment (UE) via a first transmission and reception point and a second transmission and reception point according to the SFN configuration; transmitting power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first transmission and reception point and a second uplink power level for a second uplink transmission to the second transmission and reception point; and The first uplink transmission is received from the UE via the first transmit and receive point according to the first uplink power level and the second uplink transmission is received from the UE via the second transmit and receive point according to the second uplink power level at least in part in response to the transmitted power management signaling.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to send the power management signaling by being executable by the processor to: A DCI message is transmitted indicating a first transmit power command associated with the first transmit and receive point and a second transmit power command associated with the second transmit and receive point.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to send the DCI message by being executable by the processor to: The DCI message is sent, the DCI message comprising a first field indicating that the first transmit power command is associated with a first transmit configuration indicator state of a transmit configuration indicator code point and a second field indicating that the second transmit power command is associated with a second transmit configuration indicator state of the transmit configuration indicator code point, wherein the first transmit and receive point is associated with the first transmit configuration indicator state and the second transmit and receive point is associated with the second transmit configuration indicator state based at least in part on an order of the first field and the second field within the DCI message.

17. The apparatus of claim 15, wherein the instructions are further executable by the processor to send the DCI message by being executable by the processor to: The DCI message is sent, the DCI message including a first field indicating that the first transmit power command is associated with a first transmit configuration indicator state of a first closed loop index in a transmit configuration indicator code point and a second field indicating that the second transmit power command is associated with a second transmit configuration indicator state of a second closed loop index in the transmit configuration indicator code point, wherein the first transmit and receive point is associated with the first transmit configuration indicator state and the second transmit and receive point is associated with the second transmit configuration indicator state based at least in part on an order of the first field and the second field within the DCI message.

18. The apparatus of claim 14, wherein the instructions are further executable by the processor to send the power management signaling by being executable by the processor to: Control signaling is sent at least in part based on a transmit configuration indicator code point including a first transmit configuration indicator state and a second transmit configuration indicator state to indicate that a first set of power control parameters is associated with the first transmit configuration indicator state and a second set of power control parameters is associated with the second transmit configuration indicator state, wherein the first transmit configuration indicator state is associated with the first transmit and receive point and the second transmit configuration indicator state is associated with the second transmit and receive point.

19. The apparatus of claim 14, wherein the instructions are further executable by the processor to send the power management signaling by being executable to: Control signaling is transmitted indicating two sets of power control parameters for each of a plurality of uplink bandwidth portions associated with the first uplink transmission and the second uplink transmission.

20. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: A message is received from the UE including a first power headroom report associated with the first transmit and receive point and a second power headroom report associated with the second transmit and receive point.

21. The apparatus of claim 20, wherein the instructions are further executable by the processor to send the power management signaling by being executable to: Control signaling is sent indicating the first uplink power level and the second uplink power level.

22. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: A control signaling is sent to the UE to instruct the UE to report the first power headroom report and the second power headroom report.

23. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is sent to the UE to schedule uplink transmissions using the SFN configuration, wherein the first power headroom report and the second power headroom report include true power headroom reports associated with the uplink transmissions.

24. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling is sent to the UE to schedule an uplink transmission using a transmission configuration different from the SFN configuration, wherein the first power headroom report comprises a real power headroom report associated with the uplink transmission and the second power headroom report comprises a virtual power headroom report.

25. A method for wireless communication at a user equipment (UE), comprising: establishing a communication link with the network via the first sending and receiving point and the second sending and receiving point according to the SFN configuration; determining a first uplink power level for a first uplink transmission to the network via the first transmission and reception point and a second uplink power level for a second uplink transmission to the network via the second transmission and reception point; as well as The first uplink transmission is transmitted to the first transmission and reception point according to the first uplink power level, and the second uplink transmission is transmitted to the second transmission and reception point according to the second uplink power level.

26. The method according to claim 25, further comprising: Receive a DCI message indicating a first transmit power command associated with the first transmit and receive point and a second transmit power command associated with the second transmit and receive point, wherein determining the first uplink power level and the second uplink power level is at least partially based on the first transmit power command and the second transmit power command.

27. The method according to claim 26, further comprising: At least in part based on an order of a first field indicating the first transmit power command and a second field indicating the second transmit power command within the DCI message, determining that the first field is associated with a first transmit configuration indicator state of a transmit configuration indicator code point and the second field is associated with a second transmit configuration indicator state of the transmit configuration indicator code point.

28. The method of claim 26, further comprising: At least in part based on an order of a first field indicating the first transmit power command and a second field indicating the second transmit power command within the DCI message, determining that the first field is associated with a first transmit configuration indicator state of a first closed-loop index in a transmit configuration indicator code point and the second field is associated with a second transmit configuration indicator state of a second closed-loop index in the transmit configuration indicator code point.

29. The method of claim 25, further comprising: A first set of power control parameters associated with the first transmit and receive point and a second set of power control parameters associated with the second transmit and receive point are identified at least in part based on a first transmit configuration indicator state associated with the first transmit and receive point and a second transmit configuration indicator state associated with the second transmit and receive point, wherein the first uplink power level for the first uplink transmission and the second uplink power level for the second uplink transmission are determined at least in part based on the first set of power control parameters and the second set of power control parameters.

30. A method for wireless communication at a network entity, comprising: establishing a communication link with a user equipment (UE) via a first transmission and reception point and a second transmission and reception point according to the SFN configuration; transmitting power management signaling to the UE, the power management signaling being configured to support the UE in determining a first uplink power level for a first uplink transmission to the first transmission and reception point and a second uplink power level for a second uplink transmission to the second transmission and reception point; and The first uplink transmission is received from the UE via the first transmit and receive point according to the first uplink power level and the second uplink transmission is received from the UE via the second transmit and receive point according to the second uplink power level at least in part in response to the transmitted power management signaling.

Images