Downlink power control recommendations for reducing cross-link interference in full duplex networks

Abstract

Methods, systems, and devices for wireless communication are described. The technology described herein relates to a user equipment (UE) that monitors performance of downlink transmissions from a network entity to the UE and provides dynamic downlink transmission power recommendations. The UE may receive control signaling indicating configuration information for dynamically reporting recommended downlink transmission power levels for the network entity to apply to subsequent downlink transmissions. The UE may receive a downlink transmission from the network entity according to the configuration information. The UE may send a dynamic message to the network entity based on receiving the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmission power level for use by the network entity.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 970,551, entitled “DOWNLINKPOWER CONTROL RECOMMENDATION FOR CROSS LINK INTERFERENCE REDUCTION IN FULLDUPLEX NETWORKS,” filed by Abotabl et al. on October 20, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, including downlink power control recommendations for reducing cross-link interference in full-duplex networks. Background Art

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

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting downlink power control recommendations for reducing cross-link interference (CLI) in a full-duplex network. In some full-duplex communications, a user equipment (UE) may experience CLI, which may degrade the signal quality of downlink messages received at the UE. Reducing the power of downlink transmissions may reduce the CLI caused by downlink transmissions to other UEs, but may also reduce the performance of the downlink transmissions (e.g., the likelihood of being received by the target UE). The described technology provides dynamic downlink transmission power recommendations to a network entity based on monitored downlink transmissions. The network entity may dynamically adjust the downlink transmission power to manage the tradeoff between the CLI at other UEs and the accuracy of the downlink transmission at the receiving UE. In some examples, the network entity may configure the UE to periodically report downlink transmission power recommendations, such as reporting in a reporting resource associated with a CLI reporting resource. In some examples, the network entity may dynamically request downlink transmission power recommendations (e.g., via downlink control information). The UE may determine the recommended downlink transmit power level based on, for example, a relationship between channel state information (CSI) and the received downlink transmission, a relationship between CLI and the received downlink transmission, the UE's decoding performance of the received downlink transmission, a number of iterations used to decode the downlink transmission, or a measurement of the downlink transmission performance.

[0006] A method for wireless communication at a UE is described. The method may include: receiving control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receiving a downlink transmission from the network entity according to the configuration information; and sending a dynamic message to the network entity based on receiving the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive control signaling indicating configuration information from a network entity, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receive a downlink transmission from the network entity according to the configuration information; and send a dynamic message to the network entity based on receiving the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; means for receiving a downlink transmission from the network entity in accordance with the configuration information; and means for sending a dynamic message to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receive a downlink transmission from the network entity according to the configuration information; and send a dynamic message to the network entity based on receiving the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for the following actions: receiving an indication of a set of periodic reporting resources for the dynamic report along with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving second control signaling from the network entity, the second control signaling requesting the UE to report the recommended downlink transmit power level based on the configuration information, wherein sending the dynamic message may be in response to the second control signaling.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for receiving a power offset set and a reference power set along with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the recommended downlink transmit power level also includes an indication of a reference power in the set of reference powers.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for receiving an indication of a resource set associated with the reference power set along with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via resources in the resource set.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference power set may be a CSI reference signal transmit power.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for the following actions: receiving a set of absolute power levels along with the configuration information, wherein sending the dynamic message includes sending an indication of a selected absolute power level from the set of absolute power levels.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating measurement information based on the downlink transmission, wherein the recommended downlink transmission power level may be based on the measurement information.

[0018] In some examples of the methods, apparatus, and non-transitory computer readable media described herein, generating the measurement information may include operations, features, components, or instructions for generating one of a log likelihood ratio or a block error rate based on the downlink transmission.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, generating the measurement information may include operations, features, components, or instructions for measuring decoding performance of downlink transmissions.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a change in a CLI measurement at the UE or a CSI measurement at the UE based on the downlink transmission, wherein the recommended downlink transmission power level may be based on the change.

[0021] A method of wireless communication at a network entity is described. The method may include: sending control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; sending a downlink transmission to the UE in accordance with the configuration information; and receiving a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0022] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send control signaling indicating configuration information to a UE, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; send a downlink transmission to the UE in accordance with the configuration information; and receive a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0023] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; means for sending a downlink transmission to the UE in accordance with the configuration information; and means for receiving a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0024] 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: send control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; send a downlink transmission to the UE in accordance with the configuration information; and receive a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second downlink transmission to the UE based on the recommended downlink transmit power level and one or more second recommended downlink transmit powers received from one or more other UEs.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for the following actions: sending an indication of a set of periodic reporting resources for the dynamic report along with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: sending a second control signaling to the UE, the second control signaling requesting the UE to report the recommended downlink transmit power level based on the configuration information, wherein receiving the dynamic message may be based on the second control signaling.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for the following actions: sending a power offset set and a reference power set along with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the recommended downlink transmit power level also includes an indication of a reference power in the set of reference powers.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for the following actions: sending an indication of a resource set associated with the reference power set along with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via a resource in the resource set.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the reference power set may be a CSI reference signal transmit power.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for the following actions: sending a set of absolute power levels along with the configuration information, wherein receiving the dynamic message includes receiving an indication of a selected absolute power level from the set of absolute power levels. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 An example of a wireless communication system supporting downlink power control recommendations for reducing cross-link interference (CLI) in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0034] Figure 2 An example of a resource map supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0035] Figure 3 An example of a wireless communication system supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0036] Figure 4 An example of a time slot format supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0037] Figure 5 Another example of a wireless communication system supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 6 An example of a process flow supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 7 and Figure 8 A block diagram of an apparatus supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0040] Fig. 9 A block diagram of a communications manager supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0041] Fig.10 A diagram of a system including a device supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0042] Fig.11 and Fig.12 A block diagram of an apparatus supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0043] Fig.13 A block diagram of a communications manager supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0044] Fig.14 A diagram of a system including a device supporting downlink power control recommendations for reducing CLI in a full-duplex network is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig.15 and Fig.16 A flow chart illustrating a method of supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0046] Some wireless communication systems may support full-duplex communication, in which downlink messages and uplink messages are communicated simultaneously. In some cases, full-duplex communication may cause cross-link interference (CLI) to be experienced at the user equipment (UE). CLI may reduce the signal quality of the downlink message received at the UE. Specifically, a downlink transmission from a first network entity to a first UE may cause CLI to a second UE (e.g., interference with a downlink transmission from a second network entity or a sidelink transmission from a third UE). In order to reduce the CLI caused by the downlink transmission, the power of the downlink transmission may be reduced, but this may also reduce the performance of the downlink transmission (e.g., the possibility of being received by the target UE). The UE may report channel state information (CSI) or CLI information to the network to indicate channel performance or interference, but such information may not provide the network with a complete picture of the decoding performance at the UE. Therefore, the network entity may not know whether the network entity can reduce the downlink transmission power level in order to reduce CLI without affecting the downlink accuracy (e.g., decoding performance).

[0047] A network entity may send control signaling including configuration information for dynamically reporting by a UE a recommended downlink transmit power for application by the network entity. Based on the configuration information, a UE receiving a downlink transmission may monitor the performance of the downlink transmission and provide a dynamic downlink transmit power recommendation to the network entity based on the monitored downlink transmission. The configuration information may indicate a dynamic resource via which the UE may send a dynamic message (e.g., uplink control information (UCI) or a medium access control (MAC) control element (CE)), the dynamic message including an indication of a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. Since the downlink transmit power recommendation is sent in a dynamic message, the network entity may dynamically adjust the downlink transmit power to manage a tradeoff between CLI at other UEs and downlink transmission accuracy at a receiving UE. In some examples, the configuration information may instruct the UE to periodically report the downlink transmit power recommendation, for example, in a reporting resource associated with a CLI reporting resource. In some examples, based on the configuration information, the network entity may dynamically request a downlink transmit power recommendation (e.g., via downlink control information (DCI) or MAC-CE). The UE may determine the recommended downlink transmit power level, for example, based on a relationship between the CSI and the received downlink transmission, a relationship between the CLI and the received downlink transmission, a decoding performance of the UE for the received downlink transmission, a number of iterations for decoding the downlink transmission (e.g., a number of iterations), or a measurement of downlink transmission performance (such as a log likelihood ratio (LLR) or a block error rate (BLER)).

[0048] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to downlink power control recommendations for reducing CLI in a full-duplex network.

[0049] Figure 1 An example of a wireless communication system 100 supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with 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.

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

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

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

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

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

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

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

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

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

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

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

[0061] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support downlink power control recommendations for reducing CLI in a full-duplex network 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 disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

[0064] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured 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 these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

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

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

[0067] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier 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 communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

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

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

[0070] The time interval for the network entity 105 or the UE 115 may be expressed in multiples 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 supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

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

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

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

[0074] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within 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, etc.

[0075] A macro cell typically 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. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells 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 small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 may support one or more cells, and may also support communication via one or more cells using one or more component carriers.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] Some signals, such as data signals associated with a particular receiving device, may be sent by a sending device (e.g., sending network entity 105, sending 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, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

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

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

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

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

[0094] In some examples, the wireless communication system 100 may support full-duplex communication, in which downlink messages and uplink messages are communicated simultaneously. In some cases, full-duplex communication may cause CLI to be experienced at UE 115, which may reduce the signal quality of downlink messages or sidelink messages received at UE 115. Specifically, a downlink transmission from a first network entity 105 to a first UE 115 may cause CLI to a second UE 115 (e.g., interfering with a downlink transmission from another network entity 105 or a sidelink transmission from a third UE 115). Reducing the power of the downlink transmission will reduce the CLI caused by the downlink transmission to other UEs 115, but may also reduce the performance of the downlink transmission (e.g., the possibility of being received by the target UE 115). UE 115 may be configured to report CSI and CLI information to the network, but such information may not provide the network with a complete picture of the decoding performance at UE 115. For example, while CSI feedback and CLI may provide an indication of channel quality and interference, CSI feedback and CLI do not provide a complete picture of decoding performance at UE 115. For example, in a low interference situation, UE 115 may be scheduled using a high modulation and coding scheme (MCS) and still be able to decode within a small number of iterations. For example, in a retransmission situation, UE 115 may know the correctly decoded codebook while the network entity may incorrectly believe that the entire transport block was received in error. Therefore, network entity 105 may not know whether network entity 105 can reduce the downlink transmit power level in order to reduce CLI without affecting downlink accuracy.

[0095] The network entity 105 may send control signaling including configuration information for dynamically reporting by the UE a UE-recommended downlink transmit power for application by the network entity. Based on the configuration information, the UE 115 receiving the downlink transmission may monitor the performance of the downlink transmission. Based on the monitored downlink transmission, the UE 115 may send a dynamic message to the network entity 105, the dynamic message including an indication of the recommended downlink transmit power. Since the downlink transmit power recommendation is sent in a dynamic message (e.g., UCI or MAC-CE), the network entity 105 may dynamically adjust the downlink transmit power to manage the tradeoff between the CLI at other UEs 115 and the downlink transmission accuracy at the receiving UE 115. In some examples, the configuration information may instruct the UE 115 to periodically report the downlink transmit power recommendation, for example, in a reporting resource associated with the CLI reporting resource. In some examples, based on the configuration information, the network entity 105 may dynamically request a downlink transmit power recommendation (e.g., via DCI or MAC-CE). In some examples, the configuration information may indicate the format of the downlink transmit power recommendation (e.g., as an offset relative to a reference power level or relative to an absolute power level in a configured (e.g., RRC configured) power level set). UE 115 may determine the recommended downlink transmit power level based on, for example, a relationship between the CSI and the received downlink transmission, a relationship between the CLI and the received downlink transmission, a decoding performance of the UE 115 for the received downlink transmission, a number of iterations used to decode the downlink transmission (e.g., a number of iterations), or a measurement of downlink transmission performance (such as LLR or BLER).

[0096] Figure 2 An example of a resource map 200 that supports multicast scheduling in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated. The resource map 200 can implement aspects of the wireless communication system 100.

[0097] As described herein, some wireless communication systems may implement full-duplex communication. Full-duplex communication may be in-band full-duplex (IBFD) communication or sub-band FDD communication (eg, flexible duplex).

[0098] The first example 205-a illustrates an IBFD example. In IBFD, a wireless device (e.g., a network entity 105 or a UE 115) may transmit and receive on the same frequency resources at the same time. For example, downlink resources 210-a and uplink resources 215-a may fully or partially overlap (e.g., downlink resources 210-a and uplink resources 215-a may share the same IBFD time or frequency resources).

[0099] The second example 205-b illustrates a sub-band FDD example. In sub-band FDD, a wireless device (e.g., network entity 105 or UE 115) may transmit and receive at the same time but on different frequency resources. For example, downlink resources 210-b may be separated from uplink resources 215-b in the frequency domain (e.g., via guard band 220).

[0100] Figure 3 Examples of wireless communication systems 300-a, 300-b, and 300-c that support multicast scheduling in a full-duplex network according to one or more aspects of the present disclosure are illustrated. The wireless communication systems 300-a, 300-b, and 300-c may implement aspects of the wireless communication system 100. For example, the wireless communication system 300-a may include a first UE 115-a and a second UE 115-b, the wireless communication system 300-b may include a first UE 115-c and a second UE 115-d, and the wireless communication system 300-c may include a first UE 115-e and a second UE 115-f, which may be examples of UE 115 as described herein. The wireless communication system 300-a may include network entity 105-a and network entity 105-b, the wireless communication system 300-b may include network entity 105-c and network entity 105-d, and the wireless communication system 300-c may include network entity 105-e, which may be examples of network entity 105 as described herein.

[0101] The wireless communication system 300-a illustrates an example in which the network entity 105-a operates in full duplex and each of the first UE 115-a and the second UE 115-b operates in half duplex. For example, the network entity 105-a may use downlink resources (e.g., downlink resources 335-a or downlink resources 335-b) to send a downlink signal 320-a to the second UE 115-b, and the first UE 115-a may use uplink resources 340-a to send an uplink signal 325-a to the network entity 105-a. The uplink resources 340-a may be non-overlapping with the downlink resources 335-a and the downlink resources 335-b. The uplink signal 325-a sent by the first UE 115-a may cause a CLI 315-b at the second UE 115-b. The transmission by the network entity 105-b may cause a CLI 315-a at the network entity 105-a. The transmission of the downlink signal 320 - a by the network entity 105 - a may cause self-interference 330 - a at the network entity 105 - a related to the reception of the uplink signal 325 - a .

[0102] The wireless communication system 300-b illustrates an example in which the network entity 105-c operates in full-duplex and the first UE 115-c operates in full-duplex. For example, the network entity 105-c may use downlink resources 335-c to send a downlink signal 320-b to the first UE 115-c, and the first UE 115-c may use uplink resources 340-b to send an uplink signal 325-b to the network entity 105-c. The network entity 105-c may also send a downlink signal 320-c to the second UE 115-d. The uplink resources 340-b may overlap (e.g., partially or completely overlap) with the downlink resources 335-c. The uplink signal 325-b sent by the first UE 115-c may cause a CLI 315-d at the second UE 115-d. The transmission by the network entity 105-d may cause a CLI 315-c at the network entity 105-c. The transmission of the downlink signal 320-b or the downlink signal 320-c by the network entity 105-c may cause self-interference 330-b at the network entity 105-a related to the reception of the uplink signal 325-b. The transmission of the uplink signal 325-b by the first UE 115-c may cause self-interference 330-c at the first UE 115-c related to the reception of the downlink signal 320-b.

[0103] The wireless communication system 300-c illustrates an example in which a network entity includes multiple TRPs (e.g., a first TRP 310-a and a second TRP 310-b) and operates in full-duplex and a first UE 115-e operates in full-duplex. For example, the first UE 115-e may support sub-band full-duplex (SBFD) operation. For example, the second TRP 310-b may use downlink resources 335-d to send a downlink signal 320-d to the first UE 115-e, and the second TRP 310-b may use downlink resources 335-d to send a downlink signal 320-e to the second UE 115-f. The first UE 115-e may use uplink resources 340-c to send an uplink signal 325-c to the first TRP 310-a. The uplink resources 340-c may overlap (e.g., partially or completely overlap) with the downlink resources 335-d. The transmission of the downlink signal 320-d and the downlink signal 320-e by the second TRP 310-b may cause a CLI 315-e at the first TRP 310-a. The uplink signal 325-c transmitted by the first UE 115-e may cause a CLI 315-f at the second UE 115-f. The transmission of the uplink signal 325-c by the first UE 115-e may cause self-interference 330-d at the first UE 115-e related to the reception of the downlink signal 320-d.

[0104] Some wireless communication systems may include only TDD frequency bands. Some wireless communication systems (e.g., wireless communication system 300-a) may include full-duplex operation at the network and half-duplex operation at the UE. Some wireless communication systems may support SBFD (e.g., no overlap between downlink and uplink frequency resources).

[0105] In some cases, if the UE 115 operates in half-duplex mode and the network entity 105 operates in SBFD / IBFD mode, the UE 115 may experience interference from multiple interference sources. For example, the UE 115 may experience inter-cell interference from other network entities 105 (e.g., in the wireless communication system 300-b, the second UE 115-d may experience CLI 315 caused by downlink transmissions performed by the network entity 105-d). For another example, the UE 115 may experience intra-cell interference from UEs 115 in the same cell (e.g., CLI 315-b, CLI 315-d, or CLI 315-f as shown in the wireless communication system 300-a, the wireless communication system 300-b, and the wireless communication system 300-c, respectively). As another example, a UE 115 may experience inter-cell CLI 315 from a UE 115 in a neighboring cell (e.g., in the wireless communication system 300-b, a second UE 115-d may experience CLI 315 caused by a UE 115 in a neighboring cell). Additionally, a full-duplex UE 115 may experience self-interference (e.g., self-interference 330-c at a first UE 115-c in the wireless communication system 300-b).

[0106] Figure 4 An example of a slot format 400 supporting multicast scheduling in a full-duplex network according to one or more aspects of the present disclosure is illustrated. The slot format 400 may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c.

[0107] The time slot format 400 illustrates an example half-duplex downlink time slot 405, a SBFD time slot 410, and a half-duplex uplink time slot 415 of a carrier bandwidth 430. The half-duplex downlink time slot 405 includes a downlink control region (e.g., resources for downlink control (e.g., resources for a physical downlink control channel (PDCCH) that can convey DCI)) and a downlink data region (e.g., resources for a physical downlink shared channel (PDSCH)). The half-duplex uplink time slot 415 includes an uplink data region (e.g., resources for a physical uplink shared channel (PUSCH)) and an uplink control region (e.g., resources for uplink control (e.g., resources for a physical uplink control channel (PUCCH) that can convey UCI).

[0108] The SBFD timeslot 410 includes a downlink BWP that includes a first downlink subband 420-a and a second downlink subband 420-b. In a "D+U" timeslot, such as the SBFD timeslot 410, the carrier bandwidth 430 may be used for both uplink transmissions and downlink transmissions. Figure 4 As illustrated, the SBFD time slot 410 includes an uplink BWP that includes an uplink subband 425. A guard band may separate a first downlink subband 420-a and a second downlink subband 420-b from the uplink subband 425. The first downlink subband 420-a includes a downlink control region and a downlink data region. The second downlink subband 420-b includes a downlink control region and a downlink data region. The uplink subband 425 includes a PUSCH region and an uplink control region. In some examples, in a "D+U" time slot, downlink transmissions and uplink transmissions may occur in overlapping frequency bands (e.g., IBFD operation). In some examples, in a "D+U" time slot, as shown in the SBFD time slot 410, downlink transmissions and uplink transmissions may occur in adjacent non-overlapping frequency bands. If the "D+U" time slot is used for scheduling, the half-duplex UE 115 may transmit in the uplink frequency band (e.g., uplink subband 425) or receive in the downlink frequency band (e.g., the first downlink subband 420-a and the second downlink subband 420-b). If the "D+U" time slot is used for scheduling, the full-duplex UE 115 (e.g., a UE 115 supporting simultaneous transmission and reception) may transmit in the uplink frequency band (e.g., uplink subband 425) or receive in the downlink frequency band (e.g., the first downlink subband 420-a and the second downlink subband 420-b). The "D+U" time slot may include a downlink symbol, an uplink symbol, or a full-duplex symbol.

[0109] In SBFD, the network entity 105 may configure downlink transmissions to the UE 115 in frequency domain resources that are adjacent to frequency domain resources configured for uplink transmissions of another UE 115. For example, in the SBFD time slot 410, the first UE 115 may transmit an uplink transmission in the uplink subband 425, and the second UE 115 may simultaneously receive downlink transmissions in the first downlink subband 420-a and / or the second downlink subband 420-b. The uplink transmission of the first UE 115 may cause CLI to the downlink reception at the second UE 115. The CLI may be caused by energy leakage caused by timing and frequency misalignment between the two UEs 115, or may be caused by an automatic gain control (AGC) of the second UE 115 when the AGC is driven by the downlink service signal of the second UE 115 but the CLI is strong enough to saturate the AGC of the second UE 115.

[0110] Figure 5 An example of a wireless communication system 500 that supports downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 500 may implement aspects of the wireless communication system 100. For example, the wireless communication system 500 may include a UE 115-g and a UE 115-h, which may be examples of a UE 115 as described herein. The wireless communication system 500 may include a network entity 105-f, which may be an example of a network entity 105 as described herein.

[0111] The wireless communication system 500 illustrates an example in which one or more of the network entity 105-f, the UE 115-g, and the UE 115-h can operate in full duplex. For example, the UE 115-g and / or the UE 115-h can communicate with the network entity 105-f simultaneously on the same frequency band as the network entity 105-f using uplink signals 505-a and 505-b, respectively. The network entity 105-f can communicate with the UE 115-g and the UE 115-h simultaneously on the same frequency band using downlink signals 510-a and 510-b, respectively.

[0112] Uplink signals 505 and downlink signals 510 may be communicated via communication link 125. UE 115-g may communicate with network entity 105-f using communication link 125-a, and UE 115-h may communicate with network entity 105-f using communication link 125-b. Communication link 125-a may be an example of an NR or LTE link between UE 115-g and network entity 105-f. Communication link 125-b may be an example of an NR or LTE link between UE 115-h and network entity 105-f. Communication link 125-a and communication link 125-b may include bidirectional links that enable both uplink and downlink communications. For example, UE 115-g may use communication link 125-a to send an uplink signal 505-a such as an uplink control signal or an uplink data signal to network entity 105-f (e.g., uplink transmission), and network entity 105-f may use communication link 125-a to send a downlink signal 510-a such as a downlink control signal or a downlink data signal to UE 115-g (e.g., downlink transmission). UE 115-h may use communication link 125-b to send an uplink signal 505-b such as an uplink control signal or an uplink data signal to network entity 105-f (e.g., uplink transmission), and network entity 105-f may use communication link 125-b to send a downlink signal 510-b such as a downlink control signal or a downlink data signal to UE 115-h (e.g., downlink transmission).

[0113] In some cases, the uplink signal 505-b sent by the UE 115-h may cause a CLI 540 at the UE 115-g. The wireless communication system 500 may implement a layer 1 CLI framework to provide flexibility to adapt to dynamic CLI. However, the layer 1 CLI framework may increase the layer 1 signaling overhead. The layer 1 CLI measurement may be triggered by a dedicated DCI or a group common DCI sent by the network entity 105-f. The aggressor UE 115 (e.g., UE 115-h) may be configured with a non-periodic, semi-persistent, or periodic non-zero power (NZP) sounding reference signal (SRS) resource. The victim UE 115 (e.g., UE 115-g) may be configured with a non-periodic, semi-persistent, or periodic CLI measurement resource corresponding to the NZP SRS resource. The UE 115-h may send SRS 545 in the configured resource, and the UE 115-g may measure the SRS using the configured CLI resource. The UE 115-g may send a CLI report 550 (e.g., a layer 1 CLI measurement report) to the network entity 105-f. The network entity 105-f may consider the CLI report 550 when scheduling uplink signals 505 and downlink signals 510. The layer 1 reporting framework may support aperiodic, semi-persistent, or periodic CLI reporting based on the timing behavior of the CLI resources. The layer 1 reporting framework may support subband-based CLI measurement and reporting and / or beam-based CLI measurement and reporting (e.g., quasi-co-located (QCL) type D for CLI measurement resources).

[0114] In some cases, the CLI report 550 may be based on the CSI reporting framework. The CLI report 550 may be a special type of CSI report, for example based on the RRC parameter reportQuantity. The CLI report 550 may be an extension of the CSI framework. The CLI measurement resources configured for the UE 115-g may be bound to the interference measurement resources (IMR), or may be new CLI measurement resources (CLI-MR) (e.g., configured by RRC). For example, the CLI measurement resources may be configured as IMRs with zero power (ZP) SRS or CSI interference measurement (IM). For example, the network entity 105-f may configure pseudo channel measurement resources (CMRs) (e.g., the CLI may be based on IMRs with ZP-SRS or CSI-IM).

[0115] In some cases, the wireless communication system 500 may implement a dedicated CLI reporting framework, which may involve a simplified reporting configuration. For example, CLI measurement resources (e.g., ZP-SRS or CSI-IM) may be bound to CLI-MR. Such an approach may minimize the impact of the CSI process. CLI report 550 may be a new UCI type.

[0116] The wireless communication system 500 may implement an inter-UE CLI identification / mitigation process. The network entity 105-f may group UEs (e.g., including UE 115-g, UE 115-h, and other UEs) into a co-scheduled UE set (e.g., UEs 115 to be co-scheduled in different directions in an SBFD time slot). Based on CLI reports from victim UEs 115 (e.g., such as UE 115-g), the network entity 105-f may construct an interference graph for determining the primary aggressor UE 115 for each victim UE 115. In the first stage of CLI mitigation for the UEs 115 in each group, the network entity 105-g may implement a scheduling-based solution (e.g., determining time / frequency resources or power control parameters) to minimize the impact of CLI, and / or may refine the inter-UE interference graph based on the optimized scheduling. In the second stage of CLI mitigation, the network entity 105-f may optimize MCS, rank, and precoding to reduce CLI. The second stage CLI mitigation may involve enhanced CSI feedback based on interference assumptions (e.g., expected CLI interference). The second stage CLI mitigation may involve advanced techniques (e.g., precoding options) for reducing CLI at the aggressor UE 115. The second stage CLI mitigation may involve advanced techniques (e.g., combining options) for reducing CLI at the victim UE 115.

[0117] In some cases, to provide accurate power reduction for downlink transmissions, the UE 115 - g may monitor downlink transmissions to provide dynamic downlink transmission power recommendations to the network entity 105 - f based on the monitored downlink transmissions.

[0118] Specifically, UE-115-g may receive control signaling 515 from network entity 105-f indicating configuration information for dynamically reporting a recommended downlink transmit power level for network entity 105-f to apply to subsequent downlink transmissions. UE 115-g may receive downlink transmission 520-a based on control signaling 515 from network entity 105-f to UE 115-g. UE 115-g may provide a dynamic downlink transmit power recommendation in a dynamic message 525-a from UE 115-g to network entity 105-f based on the monitored downlink transmission 520-a. Since the downlink transmit power recommendation is sent in a dynamic message 525-a (which may be in the form of a UCI or MAC-CE), network entity 105-f may dynamically adjust the downlink transmit power to manage the tradeoff between CLI at other UEs 115 (e.g., UE 115-h) and downlink transmission accuracy at the receiving UE 115-g.

[0119] UE-115-h may receive control signaling 515 from network entity 105-f indicating configuration information for dynamically reporting a recommended downlink transmit power level for network entity 105-f to apply to subsequent downlink transmissions. UE115-h may receive downlink transmission 520-b based on control signaling 515 from network entity 105-f to UE 115-h. UE115-g may provide a dynamic downlink transmit power recommendation in a dynamic message 525-b from UE 115-h to network entity 105-f based on the monitored downlink transmission 520-b. The description discussed herein with respect to UE 115-g or UE 115-g may be applicable to either or both of UE 115-g and UE 115-g. That is, the description discussed with respect to UE 115-g may be applicable to UE 115-h, and the description discussed with respect to UE 115-h may be applicable to UE 115-g.

[0120] In some examples, the network entity 105-f may dynamically request a downlink transmit power recommendation via a second control signaling 530 (such as via a DCI or MAC-CE request). In some examples, the downlink transmit power recommendation is transmitted based on a periodic report (e.g., a semi-persistent report) or based on a network request (such as the second control signaling 530). In periodic reporting, the reporting resources may be independently configured, the reporting resources may be associated to the CLI measurement resources, or the reporting resources may be associated to the CLI periodic reporting resources. Thus, for example, the network entity 105-f may configure the UE 115-g to periodically report the downlink transmit power recommendation in a dynamic message 525-a in a reporting resource associated to the CLI reporting resource.

[0121] For downlink transmit power recommendations transmitted based on a network request (e.g., requested by the network via second control signaling 530), the network request may be a dynamic indication, such as a message in a PDSCH DCI format (DCI 1_0 or DCI 0_0) with an invalid indication or a new DCI indication. In some examples, the network request may be based on MAC-CE.

[0122] In some examples, the configuration information in the control signaling 515 may indicate the format of the recommended downlink transmit power level in the dynamic message 525-a. For example, the network may indicate a configured power offset set via RRC, and may indicate the recommended downlink transmit power level in the dynamic message 525-a by indicating one of the power offsets in the configured power offset set (which is an offset relative to a given reference power level). For example, the reference power level may be the power level of the CSI-RS 535. In some examples, the CSI-RS 535 used as a reference may be indicated by the UE 115-g in the dynamic message 525-a (e.g., indicated from a set of multiple CSI-RS). In some examples, the configuration information may indicate multiple reporting resources that can be used to send the dynamic message 525-a to indicate the recommended downlink transmit power level. Each of the multiple reporting resources may be associated with a given CSI-RS via the configuration information. UE 115-g may send dynamic message 525-a using resources associated with CSI-RS 535 (which UE 115-g uses as a reference for power offset). In some examples, configuration information (or other control signaling such as RRC) may indicate that a fixed CSI-RS 335 is used as a reference power level, and in such examples, dynamic message 525-a may not explicitly indicate CSI-RS 335 used as a reference power.

[0123] In some examples, UE 115-g may receive a set of absolute downlink transmit power levels along with configuration information in control signaling 515 or via other control signaling (e.g., RRC signaling). In such examples, the recommended downlink transmit power level is indicated by a dynamic message 525-a having a selected absolute power level from the set of absolute power levels. As an example, network entity 105-f may indicate four different downlink transmit power levels via RRC, and UE 115-g may select one of the downlink transmit power values ​​based on monitoring downlink transmissions from network entity 105-f. UE 115-g may indicate the selected downlink transmit power level in the dynamic message 525-a. As another example, the RRC configuration may provide a set of downlink transmit power values ​​and a corresponding bit sequence for each value, and the dynamic message 525-a may include a bit sequence in the bit sequence for indicating the selected downlink transmit power value from the set of downlink transmit power values.

[0124] In some examples, UE 115-g may provide a recommended downlink transmit power in a dynamic message 525-a based on one or more parameters, such as a parameter indicating an RRC configured relationship between CSI, CLI, decoding performance, number of iterations used in message decoding, average LLR, or BLER based on downlink transmission 520-a. That is, UE 115-g may generate measurement information based on downlink transmission 520, wherein the recommended downlink transmit power level is based at least in part on the measurement information. The measurement information may correspond to a parameter indicating an RRC configured relationship. LLR and BLER may be based on the downlink transmission, and the measurement information may include decoding performance of the downlink transmission, as previously mentioned. In addition, determining a change in a CLI measurement at UE 115-g or a change in a CSI measurement at UE 115-g is based on the downlink transmission, wherein the recommended downlink transmit power level is based at least in part on the change.

[0125] In some examples, network entity 105-f may receive multiple (e.g., different) downlink power recommendations from multiple UEs 115 (e.g., via dynamic message 525-a from UE 115-g, via dynamic message 525-b from UE 115-h, and / or via dynamic messages from other UEs 115). Network entity 105-f may adapt downlink transmit power based on the recommendations from the multiple UEs 115, priority differences between the multiple UEs 115, and respective signal priorities of the different UEs 115. In some examples, network entity 105-f may adapt downlink transmit power to maximize cell throughput.

[0126] Figure 6 An example of a process flow 600 for supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is illustrated. The process flow 600 may include a UE 115-i, which may be an example of a UE 115 as described herein. The process flow 600 may include a network entity 105-g, 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-g and the UE 115-i may be sent in an order different from the example order shown, or operations performed by the network entity 105-g and the UE 115-i may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0127] At 605, UE 115-i may receive control signaling from network entity 105-g that includes an indication of configuration information for UE 115-i. The configuration information may facilitate UE 115-i to dynamically report UE recommended downlink transmit power for downlink communications from network entity 105-g to UE 115-i.

[0128] At 610, the UE 115-i may configure or communicate based at least in part on the configuration information in the control signaling. Thus, at 615, the UE 115-i may receive a downlink transmission according to the configuration information. For example, the configuration information may indicate a set of periodic reporting resources for dynamic reporting, wherein dynamic messages from the UE 115-i are provided to the network entity 105-g via periodic reporting resources in the set of periodic reporting resources.

[0129] In some examples, the network entity 105-g may send second control signaling (e.g., DCI or MAC-CE) requesting the UE 115-i to report a recommended downlink transmit power level based on the configuration information so that the dynamic message can be sent in response to the control signaling.

[0130] In some examples, the configuration information may include or be received together with a power offset set and a reference power set, wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set. The indication of the recommended downlink transmit power level may also include an indication of a reference power in the reference power set.

[0131] In some examples, the configuration information may include or be received with an indication of a resource set associated with a reference power set, wherein the dynamic message may be sent via resources in the resource set. In some examples, the reference power set may be a CSI-RS signal transmit power. Additionally, in some examples, the configuration information may include or be received with an absolute power level set, and the dynamic message may include an indication of a selected absolute power level in the absolute power level set.

[0132] In some examples, UE 115-i may generate measurement information based on the downlink transmission, wherein the recommended downlink transmit power level is based at least in part on the measurement information. The measurement information may include generating one of an LLR or a BLER based on the downlink transmission. In some examples, UE 115-i may generate the measurement information by decoding the performance of the downlink transmission. In some cases, UE 115-i may determine a change in a CLI measurement at the UE or a change in a CSI measurement at the UE 115-i based on the downlink transmission, wherein the recommended downlink transmit power level is based at least in part on the change.

[0133] At 620 , the network entity 105 - g may receive a dynamic message from the UE 115 - i , wherein the dynamic message includes an indication of a recommended downlink transmit power level based on downlink transmissions (eg, measurements and / or reference signals).

[0134] In some examples, network entity 105 - g may send a second downlink transmission to UE 115 - i based on the recommended downlink transmit power level and one or more second recommended downlink transmit powers received from one or more other UEs 115 .

[0135] Figure 7 A block diagram 700 of a device 705 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 705 can be an example of aspects of a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which are executable by the one or more processors to enable the one or more processors to perform the downlink power control recommendations for reducing CLI in a full-duplex network discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

[0136] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to downlink power control recommendations for reducing CLI in a full-duplex network), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0137] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to downlink power control recommendations for reducing CLI in full-duplex networks), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0138] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0140] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0142] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving control signaling indicating configuration information from a network entity, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The communication manager 720 may be configured to or otherwise support a component for receiving a downlink transmission from the network entity in accordance with the configuration information. The communication manager 720 may be configured to or otherwise support a component for sending a dynamic message to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0143] By including or configuring the communication manager 720 according to the examples as described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof) can support techniques for reducing CLI while providing accurate downlink transmission within the wireless communication system 100, such that the downlink transmission occurs as expected within a threshold. For example, these techniques facilitate the network entity 105 to dynamically adjust the downlink transmission power to manage the tradeoff between the CLI at other UEs 115 and the downlink transmission accuracy at the receiving UE.

[0144] Figure 8 A block diagram 800 of a device 805 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 805 can be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which are executable by the one or more processors to enable the one or more processors to perform the downlink power control recommendations for reducing CLI in a full-duplex network discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

[0145] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to downlink power control recommendations for reducing CLI in a full-duplex network), user data, control information, or any combination thereof. The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0146] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to downlink power control recommendations for reducing CLI in a full-duplex network), 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 set of multiple antennas.

[0147] The device 805 or its various components may be examples of components for performing various aspects of the downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 820 may include a control signal reception manager 825, a downlink reception manager 830, a dynamic message transmission manager 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0148] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. The control signal reception manager 825 may be configured to or otherwise support components for receiving control signaling indicating configuration information from a network entity, the configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The downlink reception manager 830 may be configured to or otherwise support components for receiving a downlink transmission from the network entity in accordance with the configuration information. The dynamic message transmission manager 835 may be configured to or otherwise support components for sending a dynamic message to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0149] In some cases, the control signal reception manager 825, the downlink reception manager 830, and the dynamic messaging manager 835 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal reception manager 825, the downlink reception manager 830, and the dynamic messaging manager 835 discussed herein. The transceiver processor may be co-located with or in communication with (e.g., directing the operation of) a transceiver of a device. The radio processor may be co-located with or in communication with (e.g., directing the operation of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of a device. The transmitter processor may be co-located with or in communication with (e.g., directing the operation of) a transmitter of a device. The receiver processor may be co-located with or in communication with (e.g., directing the operation of) a receiver of a device.

[0150] Fig. 9 A block diagram 900 of a communication manager 920 supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of the downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 920 may include a control signal reception manager 925, a downlink reception manager 930, a dynamic messaging manager 935, a periodic report reception manager 940, a power offset / reference reception manager 945, an absolute power reception manager 950, a downlink measurement manager 955, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0151] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. The control signal reception manager 925 may be configured to or otherwise support components for receiving control signaling indicating configuration information from a network entity, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The downlink reception manager 930 may be configured to or otherwise support components for receiving a downlink transmission from the network entity in accordance with the configuration information. The dynamic message transmission manager 935 may be configured to or otherwise support components for sending a dynamic message to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0152] In some examples, to support receiving the control signaling, the periodic report reception manager 940 may be configured as or otherwise support components for receiving an indication of a set of periodic reporting resources for the dynamic report along with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

[0153] In some examples, the control signal reception manager 925 may be configured to or otherwise support components for receiving a second control signaling from the network entity, the second control signaling requesting the UE to report the recommended downlink transmit power level based on the configuration information, wherein the dynamic message is sent in response to the second control signaling.

[0154] In some examples, to support receiving the control signaling, the power offset / reference reception manager 945 may be configured as or otherwise support components for receiving a power offset set and a reference power set along with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0155] In some examples, the indication of the recommended downlink transmit power level also includes an indication of a reference power in the reference power set.

[0156] In some examples, to support receiving the control signaling, the power offset / reference reception manager 945 may be configured as or otherwise support components for receiving an indication of a resource set associated with the reference power set along with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via resources in the resource set.

[0157] In some examples, the reference power set is the CSI-RS transmit power.

[0158] In some examples, to support receiving the control signaling, the absolute power reception manager 950 may be configured as or otherwise support components for receiving a set of absolute power levels along with the configuration information, wherein sending the dynamic message includes sending an indication of a selected absolute power level in the set of absolute power levels.

[0159] In some examples, downlink measurement manager 955 may be configured or otherwise support components for generating measurement information based on the downlink transmission, wherein the recommended downlink transmission power level is based on the measurement information.

[0160] In some examples, to support generating this measurement information, downlink measurement manager 955 may be configured or otherwise support components for generating one of an LLR or a BLER based on the downlink transmission.

[0161] In some examples, to support generating this measurement information, downlink measurement manager 955 may be configured or otherwise support components for measuring decoding performance of downlink transmissions.

[0162] In some examples, the downlink measurement manager 955 may be configured to or otherwise support components for determining a change in a CLI measurement at the UE or a CSI measurement at the UE based on the downlink transmission, wherein the recommended downlink transmit power level is based on the change.

[0163] In some cases, the control signal reception manager 925, the downlink reception manager 930, the dynamic messaging manager 935, the periodic report reception manager 940, the power offset / reference reception manager 945, the absolute power reception manager 950, and the downlink measurement manager 955 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal reception manager 925, the downlink reception manager 930, the dynamic messaging manager 935, the periodic report reception manager 940, the power offset / reference reception manager 945, the absolute power reception manager 950, and the downlink measurement manager 955 discussed herein.

[0164] Fig.10A diagram of a system 1000 including a device 1005 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

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

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

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

[0168] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., supporting various functions or tasks recommended for downlink power control for reducing CLI in a full-duplex network). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0169] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving control signaling indicating configuration information from a network entity, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The communication manager 1020 may be configured to or otherwise support a component for receiving a downlink transmission from the network entity in accordance with the configuration information. The communication manager 1020 may be configured to or otherwise support a component for sending a dynamic message to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0170] By including or configuring the communication manager 1020 according to the examples as described herein, the device 1005 can support techniques for reducing CLI while providing accurate downlink transmission within the wireless communication system 100, such that the downlink transmission occurs as expected within a threshold. For example, these techniques help the network entity 105 dynamically adjust the downlink transmission power to manage the tradeoff between CLI at other UEs 115 and downlink transmission accuracy at the recipient UE 115.

[0171] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of the downlink power control recommendation for reducing CLI in a full-duplex network as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0172] Fig.11A block diagram 1100 of a device 1105 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 1105 can be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which instructions can be executed by the one or more processors to enable the one or more processors to perform the downlink power control recommendations for reducing CLI in a full-duplex network discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

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

[0174] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0175] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0177] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0179] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support components for sending control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The communication manager 1120 may be configured to or otherwise support components for sending a downlink transmission to the UE in accordance with the configuration information. The communication manager 1120 may be configured to or otherwise support components for receiving a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0180] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor that controls or otherwise couples with the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof) can support techniques for reducing CLI while providing accurate downlink transmission within the wireless communication system 100, such that the downlink transmission occurs as expected within a threshold. For example, these techniques help the network entity 105 dynamically adjust the downlink transmission power to manage the tradeoff between the CLI at other UEs 115 and the downlink transmission accuracy at the receiving UE 115.

[0181] Fig.12 A block diagram 1200 of a device 1205 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 1205 can be an example of aspects of the device 1105 or 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 are executable by the one or more processors to enable the one or more processors to perform the downlink power control recommendations for reducing CLI in a full-duplex network discussed herein. Each of these components can communicate with each other (e.g., via one or more buses).

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

[0183] The transmitter 1215 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0184] The device 1205 or its various components may be examples of components for performing various aspects of downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 1220 may include a control signal transmission manager 1225, a downlink transmission manager 1230, a dynamic message reception manager 1235, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to use or otherwise cooperate with the receiver 1210, the transmitter 1215, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0185] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The control signal transmission manager 1225 may be configured to or otherwise support components for transmitting control signaling to the UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The downlink transmission manager 1230 may be configured to or otherwise support components for transmitting a downlink transmission to the UE in accordance with the configuration information. The dynamic message reception manager 1235 may be configured to or otherwise support components for receiving a dynamic message from the UE based on transmitting the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0186] In some cases, the control signal transmission manager 1225, the downlink transmission manager 1230, and the dynamic message reception manager 1235 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal transmission manager 1225, the downlink transmission manager 1230, and the dynamic message reception manager 1235 discussed herein. The transceiver processor may be co-located with or in communication with (e.g., directing the operation of) a transceiver of a device. The radio processor may be co-located with or in communication with (e.g., directing the operation of) a radio (e.g., an NR radio, an LTE radio, a Wi-Fi radio) of a device. The transmitter processor may be co-located with or in communication with (e.g., directing the operation of) a transmitter of a device. The receiver processor may be co-located with or in communication with (e.g., directing the operation of) a receiver of a device.

[0187] Fig.13A block diagram 1300 of a communication manager 1320 supporting downlink power control recommendations for reducing CLI in a full-duplex network in accordance with one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of the downlink power control recommendations for reducing CLI in a full-duplex network as described herein. For example, the communication manager 1320 may include a control signal transmission manager 1325, a downlink transmission manager 1330, a dynamic message reception manager 1335, a periodic report reception manager 1340, a power offset / reference transmission manager 1345, an absolute power transmission manager 1350, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0188] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The control signal transmission manager 1325 may be configured to or otherwise support components for transmitting control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The downlink transmission manager 1330 may be configured to or otherwise support components for transmitting a downlink transmission to the UE in accordance with the configuration information. The dynamic message reception manager 1335 may be configured to or otherwise support components for receiving a dynamic message from the UE based on transmitting the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0189] In some examples, downlink transmit manager 1330 may be configured to or otherwise support components for sending a second downlink transmit to the UE based on the recommended downlink transmit power level and one or more second recommended downlink transmit powers received from one or more other UEs.

[0190] In some examples, to support sending the control signaling, the periodic report reception manager 1340 may be configured as or otherwise support components for sending an indication of a set of periodic reporting resources for the dynamic report along with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

[0191] In some examples, the control signal sending manager 1325 may be configured to or otherwise support components for sending a second control signaling to the UE, the second control signaling requesting the UE to report the recommended downlink transmit power level based on the configuration information, wherein receiving the dynamic message is based on the second control signaling.

[0192] In some examples, to support sending the control signaling, the power offset / reference transmission manager 1345 may be configured as or otherwise support components for sending a power offset set and a reference power set along with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0193] In some examples, the indication of the recommended downlink transmit power level also includes an indication of a reference power in the reference power set.

[0194] In some examples, to support sending the control signaling, the control signal sending manager 1325 may be configured as or otherwise support components for sending an indication of a resource set associated with a reference power set along with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via resources in the resource set.

[0195] In some examples, the reference power set is the CSI-RS transmit power.

[0196] In some examples, to support sending the control signaling, the absolute power transmission manager 1350 may be configured as or otherwise support components for sending a set of absolute power levels along with the configuration information, wherein receiving the dynamic message includes receiving an indication of a selected absolute power level in the set of absolute power levels.

[0197] In some cases, the control signal transmission manager 1325, the downlink transmission manager 1330, the dynamic message reception manager 1335, the periodic report reception manager 1340, the power offset / reference transmission manager 1345, and the absolute power transmission manager 1350 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the control signal transmission manager 1325, the downlink transmission manager 1330, the dynamic message reception manager 1335, the periodic report reception manager 1340, the power offset / reference transmission manager 1345, and the absolute power transmission manager 1350 discussed herein.

[0198] Fig.14 A diagram of a system 1400 including a device 1405 supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The device 1405 can be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 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 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

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

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

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

[0202] In some examples, bus 1440 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or communications performed between different components of device 1405 that may be co-located or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one component or divided between different components).

[0203] In some examples, communication manager 1420 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1420 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1420 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 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0204] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support components for sending control signaling to a UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The communication manager 1420 may be configured to or otherwise support components for sending a downlink transmission to the UE in accordance with the configuration information. The communication manager 1420 may be configured to or otherwise support components for receiving a dynamic message from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0205] By including or configuring a communication manager 1420 according to examples as described herein, the device 1405 can support techniques for more efficiently utilizing communication resources, such as by reducing CLI while providing accurate downlink transmissions (e.g., downlink transmissions occur as expected within a threshold) within the wireless communication system 100. For example, these techniques facilitate the network entity 105 to dynamically adjust downlink transmission power to manage the tradeoff between CLI at other UEs 115 and downlink transmission accuracy at a recipient UE 115.

[0206] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of the downlink power control recommendation for reducing CLI in a full-duplex network as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0207] Fig.15 A flowchart illustrating a method 1500 for supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0208] At 1505, the method may include receiving control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described control signal receiving manager 925 is executed.

[0209] At 1510, the method may include receiving a downlink transmission from the network entity according to the configuration information. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described downlink reception manager 930 is performed.

[0210] At 1515, the method may include sending a dynamic message to the network entity based on receiving the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmission power level for the network entity to apply to subsequent downlink transmissions. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The described dynamic messaging manager 935 is executed.

[0211] Fig.16 A flow chart illustrating a method 1600 for supporting downlink power control recommendations for reducing CLI in a full-duplex network according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 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.

[0212] At 1605, the method may include sending control signaling to the UE indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions. 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.13 The described control signals are sent to manager 1325 for execution.

[0213] At 1610, the method may include sending a downlink transmission to the UE according to the configuration information. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.13 The described downlink transmission manager 1330 is performed.

[0214] At 1615, the method may include receiving a dynamic message from the UE based on sending the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmission power level for the network entity to apply to subsequent downlink transmissions. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.13 The described dynamic message receiving manager 1335 is executed.

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

[0216] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving control signaling indicating configuration information from a network entity, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receiving a downlink transmission from the network entity based on the configuration information; and sending a dynamic message to the network entity based on receiving the downlink transmission based on the configuration information, the dynamic message comprising an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0217] Aspect 2: A method according to Aspect 1, wherein receiving the control signaling includes: receiving an indication of a periodic reporting resource set used for the dynamic report together with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via a periodic reporting resource in the periodic reporting resource set.

[0218] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: receiving a second control signaling from the network entity, the second control signaling requesting the UE to report the recommended downlink transmit power level according to the configuration information, wherein the dynamic message is sent in response to the second control signaling.

[0219] Aspect 4: A method according to any one of Aspects 1 to 3, wherein receiving the control signaling includes: receiving a power offset set and a reference power set together with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0220] Aspect 5: The method according to aspect 4, wherein the indication of the recommended downlink transmit power level also includes an indication of a reference power in the reference power set.

[0221] Aspect 6: A method according to Aspect 4, wherein receiving the control signaling includes: receiving an indication of a resource set associated with the reference power set together with the configuration information, and wherein sending the dynamic message includes sending the dynamic message via resources in the resource set.

[0222] Aspect 7: The method according to any one of Aspects 4 to 6, wherein the reference power set is a CSI reference signal transmission power.

[0223] Aspect 8: A method according to any one of Aspects 1 to 3, wherein receiving the control signaling includes: receiving a set of absolute power levels together with the configuration information, wherein sending the dynamic message includes sending an indication of a selected absolute power level in the set of absolute power levels.

[0224] Aspect 9: According to any one of aspects 1 to 8, the method further comprises: generating measurement information based on the downlink transmission, wherein the recommended downlink transmission power level is at least partially based on the measurement information.

[0225] Aspect 10: The method according to aspect 9, wherein generating the measurement information includes: generating one of a log likelihood ratio (LLR) or a block error rate (BLER) based on the downlink transmission.

[0226] Aspect 11: The method according to any one of aspects 9 to 10, wherein generating the measurement information comprises: measuring decoding performance of downlink transmission.

[0227] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method also includes: determining a change in CLI measurement at the UE or a change in CSI measurement at the UE based on the downlink transmission, wherein the recommended downlink transmission power level is at least partially based on the change.

[0228] Aspect 13: A method for performing wireless communications at a network entity, the method comprising: sending control signaling indicating configuration information to a UE, the configuration information being used to dynamically report a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; sending a downlink transmission to the UE according to the configuration information; and receiving a dynamic message from the UE based on sending the downlink transmission according to the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

[0229] Aspect 14: According to the method according to Aspect 13, the method also includes: sending a second downlink transmission to the UE based at least in part on the recommended downlink transmission power level and one or more second recommended downlink transmission powers received from one or more other UEs.

[0230] Aspect 15: A method according to any one of Aspects 13 to 14, wherein sending the control signaling includes: sending an indication of a periodic reporting resource set used for the dynamic report together with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via a periodic reporting resource in the periodic reporting resource set.

[0231] Aspect 16: According to the method described in any one of Aspects 13 to 15, the method further includes: sending a second control signaling to the UE, the second control signaling requesting the UE to report the recommended downlink transmit power level according to the configuration information, wherein receiving the dynamic message is at least partially based on the second control signaling.

[0232] Aspect 17: A method according to any one of Aspects 13 to 16, wherein sending the control signaling includes: sending a power offset set and a reference power set together with the configuration information, and wherein the indication of the recommended downlink transmit power level includes an indication of a selected power offset in the power offset set.

[0233] Aspect 18: The method according to aspect 17, wherein the indication of the recommended downlink transmit power level also includes an indication of a reference power in the reference power set.

[0234] Aspect 19: A method according to Aspect 17, wherein sending the control signaling includes: sending an indication of a resource set associated with the reference power set together with the configuration information, and wherein receiving the dynamic message includes receiving the dynamic message via resources in the resource set.

[0235] Aspect 20: The method according to any one of aspects 17 to 19, wherein the reference power set is a CSI reference signal transmission power.

[0236] Aspect 21: A method according to any one of Aspects 13 to 15, wherein sending the control signaling includes: sending a set of absolute power levels together with the configuration information, and wherein receiving the dynamic message includes receiving an indication of a selected absolute power level in the set of absolute power levels.

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

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

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

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

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

[0242] Aspect 27: 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 13 to 21.

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

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

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

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

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

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

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receiving a downlink transmission from the network entity according to the configuration information; as well as A dynamic message is sent to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: An indication of a set of periodic reporting resources for the dynamic report is received along with the configuration information, and wherein sending the dynamic message comprises sending the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is received from the network entity, the second control signaling requesting the UE to report the recommended downlink transmit power level according to the configuration information, wherein sending the dynamic message is in response to the second control signaling.

4. The apparatus of claim 1 , wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: A set of power offsets and a set of reference powers are received with the configuration information, and wherein the indication of the recommended downlink transmit power level comprises an indication of a selected power offset from the set of power offsets.

5. The apparatus of claim 4, wherein the indication of the recommended downlink transmit power level further comprises an indication of a reference power in the reference power set.

6. The apparatus of claim 4, wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: An indication of a set of resources associated with the reference power set is received along with the configuration information, and wherein sending the dynamic message comprises sending the dynamic message via resources in the set of resources. The apparatus according to claim 4 , wherein the reference power set is a channel state information reference signal transmit power.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: A set of absolute power levels is received along with the configuration information, wherein sending the dynamic message includes sending an indication of a selected absolute power level from the set of absolute power levels.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Measurement information is generated based on the downlink transmission, wherein the recommended downlink transmit power level is based at least in part on the measurement information.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to generate the measurement information by being executable by the processor to: One of a log likelihood ratio or a block error rate is generated based on the downlink transmission.

11. The apparatus of claim 9, wherein the instructions are further executable by the processor to generate the measurement information by being executable by the processor to: Measures the decoding performance of downlink transmissions.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A change in a cross-link interference measurement at the UE or a change in a channel state information measurement at the UE is determined based on the downlink transmission, wherein the recommended downlink transmit power level is based at least in part on the change.

13. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending control signaling to a user equipment (UE) indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply for subsequent downlink transmissions; Send a downlink transmission to the UE according to the configuration information; as well as A dynamic message is received from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message comprising an indication of the recommended downlink transmit power level for the network entity to apply for subsequent downlink transmissions.

14. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: A second downlink transmission is sent to the UE based at least in part on the recommended downlink transmit power level and one or more second recommended downlink transmit powers received from one or more other UEs.

15. The apparatus of claim 13, wherein the instructions are further executable by the processor to send the control signaling by being executable by the processor to: An indication of a set of periodic reporting resources for the dynamic report is sent along with the configuration information, and wherein receiving the dynamic message comprises receiving the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

16. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is sent to the UE, the second control signaling requesting the UE to report the recommended downlink transmit power level according to the configuration information, wherein receiving the dynamic message is based at least in part on the second control signaling.

17. The apparatus of claim 13, wherein the instructions are further executable by the processor to send the control signaling by being executable by the processor to: A set of power offsets and a set of reference powers are sent with the configuration information, and wherein the indication of the recommended downlink transmit power level comprises an indication of a selected power offset from the set of power offsets.

18. The apparatus of claim 17, wherein the indication of the recommended downlink transmit power level further comprises an indication of a reference power in the set of reference powers.

19. The apparatus of claim 17, wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: An indication of a set of resources associated with the reference power set is sent along with the configuration information, and wherein receiving the dynamic message comprises receiving the dynamic message via resources in the set of resources.

20. The apparatus according to claim 17, wherein the reference power set is a channel state information reference signal transmit power.

21. The apparatus of claim 13, wherein the instructions are further executable by the processor to receive the control signaling by being executable by the processor to: A set of absolute power levels is sent along with the configuration information, wherein receiving the dynamic message includes receiving an indication of a selected absolute power level from the set of absolute power levels.

22. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling from a network entity indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions; receiving a downlink transmission from the network entity according to the configuration information; as well as A dynamic message is sent to the network entity based on receiving the downlink transmission in accordance with the configuration information, the dynamic message including an indication of the recommended downlink transmit power level for the network entity to apply to subsequent downlink transmissions.

23. The method of claim 22, wherein receiving the control signaling comprises: An indication of a set of periodic reporting resources for the dynamic report is received along with the configuration information, and wherein sending the dynamic message comprises sending the dynamic message via a periodic reporting resource in the set of periodic reporting resources.

24. The method according to claim 22, further comprising: Second control signaling is received from the network entity, the second control signaling requesting the UE to report the recommended downlink transmit power level according to the configuration information, wherein sending the dynamic message is in response to the second control signaling.

25. The method of claim 22, wherein receiving the control signaling comprises: A set of power offsets and a set of reference powers are received with the configuration information, and wherein the indication of the recommended downlink transmit power level comprises an indication of a selected power offset from the set of power offsets.

26. The method of claim 25, wherein the indication of the recommended downlink transmit power level further comprises an indication of a reference power in the set of reference powers.

27. The method of claim 25, wherein receiving the control signaling comprises: An indication of a set of resources associated with the reference power set is received along with the configuration information, and wherein sending the dynamic message comprises sending the dynamic message via resources in the set of resources.

28. The method according to claim 25, wherein the reference power set is a channel state information reference signal transmit power.

29. The method of claim 22, wherein receiving the control signaling comprises: A set of absolute power levels is received along with the configuration information, wherein sending the dynamic message includes sending an indication of a selected absolute power level from the set of absolute power levels.

30. A method for wireless communication at a network entity, the method comprising: sending control signaling to a user equipment (UE) indicating configuration information for dynamically reporting a recommended downlink transmit power level for the network entity to apply for subsequent downlink transmissions; Send a downlink transmission to the UE according to the configuration information; as well as A dynamic message is received from the UE based on sending the downlink transmission in accordance with the configuration information, the dynamic message comprising an indication of the recommended downlink transmit power level for the network entity to apply for subsequent downlink transmissions.

Images