Inter-UE cross-link interference aware beam fault detection and radio link management

Abstract

Methods, systems, and devices for wireless communication are described. A first user equipment (UE) may receive a control message indicating a set of interference measurement resources (IMRs) for reference signal transmission associated with radio link monitoring or beam failure monitoring. The first UE may receive a reference signal associated with radio link monitoring or beam failure monitoring from a second UE via the set of IMRs based on the control message. In response to receiving the reference signals, the first UE may transmit a beam fault report associated with the radio link monitoring or the beam fault monitoring based on one or more measurements of the one or more reference signals. In some examples, the beam failure report may indicate that a beam failure is associated with cross-link interference (CLI) from the second UE.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 890,936, entitled “INTER-UE CROSS-LINK INTERFERENCE AWARE BEAM FAILURE DETECTION AND RADIO LINK MANAGEMENT,” filed by Zhang et al. on August 18, 2022, which is assigned to the assignee of this patent application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including cross-link interference awareness, beam failure detection and radio link management between user equipments (UEs). Background Art

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

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support cross-link interference (CLI)-aware beam failure detection and radio link management between UEs. For example, the described technology provides one or more interference measurement resources (IMRs) associated with radio link monitoring or beam failure monitoring or both for beam failure detection procedures. For example, a network entity may configure one or more UEs for radio link monitoring or beam failure monitoring using one or more IMRs. A first UE may monitor the IMRs to determine whether CLI is causing a beam failure or a radio link failure. For example, a second UE may send signaling to a network entity, which may affect downlink reception at the first UE. The second UE may send reference signals on the IMRs, which may be received at the first UE. If the first UE detects a beam failure, the first UE may determine whether CLI from the second UE is causing or contributing to a beam failure based on measurements of the reference signals sent on the IMRs. Based on the beam failure, the first UE may send a beam failure report to the network entity. In some examples, the beam failure report may indicate that the beam failure is based on CLI or channel quality degradation or both. For example, the beam failure report may indicate the cause of the beam failure.

[0006] If the CLI causes a beam failure, the devices may implement techniques for performing beam recovery. For example, a network entity, a first UE, or a second UE, or any combination thereof may implement techniques for performing beam recovery based on a beam failure affected by the CLI. For example, the network entity may configure different scheduling configurations for the first UE, the second UE, or both, such that the first UE is not scheduled to receive downlink signaling, while the second UE is scheduled to send uplink signaling. Additionally or alternatively, the network entity may configure a different downlink beam for the first UE or a different uplink beam for the second UE. In some examples, the network entity may adjust the transmit power of the second UE or adjust the transmit power of the network entity for downlink signaling to the first UE to reduce the impact of the CLI.

[0007] A method for wireless communication at a first UE is described. The method may include: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message; and sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0008] A device for wireless communication at a first UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: receive a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; receive one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message; and send a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0009] Another apparatus for wireless communication at a first UE is described. The apparatus may include: a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; a component for receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message; and a component for sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions that can be executed by a processor to perform the following operations: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message; and sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the beam failure report may include operations, features, components, or instructions for sending the beam failure report indicating cross-link interference from the second UE based on measuring the one or more reference signals.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the beam failure report may include operations, features, components, or instructions for the following operations: sending the beam failure report indicating beam failure detection based on measuring the one or more reference signals.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the beam failure report may include operations, features, components, or instructions for the following operations: sending the beam failure report indicating a radio link failure based on measuring the one or more reference signals.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the beam failure report may include operations, features, components, or instructions for sending the beam failure report, which indicates a beam failure occurring based on cross-link interference or channel quality degradation or both from the second UE.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control message in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals from the second UE may be one or more sounding reference signals.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating the following: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating a service cell identifier or a physical cell identifier of a service cell of the second UE, wherein the service cell of the second UE may be different from a network entity serving the first UE.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating a channel measurement resource set for sending a second reference signal associated with the radio link monitoring or the beam failure monitoring; receiving one or more second reference signals via the channel measurement resource set based on the control message; and sending a measurement report based on measuring the one or more second reference signals.

[0020] A method for wireless communication at a network entity is described. The method may include: sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE; receiving a beam failure report from the first UE based on the IMR set; and sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0021] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE; receive a beam failure report from the first UE based on the IMR set; and send a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0022] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE; means for receiving a beam failure report from the first UE based on the IMR set; and means for sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0023] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE; receive a beam failure report from the first UE based on the IMR set; and send a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the beam failure report may include operations, features, components, or instructions for: receiving the beam failure report indicating a CLI from the second UE.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the beam failure report may include operations, features, components, or instructions for receiving the beam failure report indicating beam failure detection based on the IMR set.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the beam failure report may include operations, features, components, or instructions for receiving the beam failure report indicating a radio link failure based on the IMR set.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the beam failure report may include operations, features, components, or instructions for receiving the beam failure report, which indicates a beam failure occurring based on a CLI from the second UE or a degradation in channel quality, or both.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control message may include operations, features, components, or instructions for the following operations: sending the second control message to the first UE or the second UE or both, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for the following operations: sending the first control message indicating a sounding reference signal resource identifier, wherein the reference signal sending may be a sounding reference signal sending.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for the following operations: sending the first control message indicating the following items: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for sending the first control message indicating a service cell identifier or a physical cell identifier of a service cell of the second UE, wherein the service cell of the second UE may be different from the network entity.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first control message may include operations, features, components, or instructions for the following operations: sending the first control message, the first control message indicating a set of channel measurement resources for sending a second reference signal associated with the radio link monitoring or the beam failure monitoring; sending one or more reference signals to the first UE via the channel measurement resource set based on the first control message; and receiving a second measurement report from the first UE indicating measurements of the one or more reference signals.

[0033] A method for wireless communication at a second UE is described. The method may include: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; and transmitting one or more reference signals via the IMR set in response to the control message.

[0034] An apparatus for wireless communication at a second UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; and transmit one or more reference signals via the IMR set in response to the control message.

[0035] Another apparatus for wireless communication at a second UE is described. The apparatus may include: a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; and a component for transmitting one or more reference signals via the IMR set in response to the control message.

[0036] A non-transitory computer-readable medium storing code for wireless communication at a second UE is described. The code may include instructions executable by a processor to: receive a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring; and transmit one or more reference signals via the IMR set in response to the control message.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals may be one or more sounding reference signals.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for the following operations: receiving the control message indicating the following: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system supporting inter-UE cross-link interference (CLI)-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a wireless communication system supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a process flow supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 4 and Figure 5 A block diagram of an apparatus supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0044] Figure 6 A block diagram of a communication manager supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0045] Figure 7 A diagram of a system including a device supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0046] Figure 8 and Fig. 9 A block diagram of an apparatus supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0047] Fig.10 A block diagram of a communication manager supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0048] Fig.11 A diagram of a system including a device supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown.

[0049] Figures 12 to 15 A flow chart illustrating a method for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0050] Some systems support full-duplex communication, in which devices can transmit and receive simultaneously. For example, a network entity may communicate according to sub-band full-duplex operation, thereby enabling simultaneous transmission and reception during the same time slot. In some cases, full-duplex operation may increase the possibility of cross-link interference (CLI). For example, a network entity may send downlink signaling to a first UE while receiving uplink signaling from a second UE. In some cases, the transmission from the second UE may interfere with the reception of downlink signaling at the first UE. CLI may cause a sudden change in radio conditions at the first UE, which may cause a beam failure or a radio link failure. Some systems may support radio link monitoring and beam failure detection to resolve beam failures or radio link failures. However, some radio link monitoring and beam failure detection techniques may rely on the UE to perform a random access procedure to reestablish a link, which may significantly delay communication.

[0051] The techniques described herein support configuring interference measurement resources (IMR) for radio link monitoring or beam failure monitoring. A first UE (e.g., a downlink receiving UE) may monitor the IMR to determine whether the CLI is causing a beam failure. For example, a second UE (e.g., an uplink transmitting UE) may send signaling to a network entity, which may affect downlink reception at the first UE. The second UE may send reference signals on the IMR, which may be received at the first UE. If the first UE detects a beam failure, the first UE may determine whether the CLI from the second UE is causing or contributing to the beam failure based on the reference signals on the IMR. Based on the beam failure, the first UE may send a beam failure report to the network entity. In some examples, the beam failure report may indicate that the beam failure is based on the CLI or channel quality degradation or both. For example, the beam failure report may indicate the cause of the beam failure.

[0052] If CLI causes a beam failure, the devices may implement techniques for performing beam recovery. For example, a network entity, a first UE, or a second UE, or any combination thereof may implement techniques for performing beam recovery without requiring the first UE to perform a random access procedure. For example, the network entity may configure a different scheduling configuration for the first UE, the second UE, or both, such that the first UE is not scheduled to receive downlink signaling, while the second UE is scheduled to send uplink signaling. Additionally or alternatively, the network entity may configure a different downlink beam for the first UE or a different uplink beam for the second UE. In some examples, the network entity may adjust the transmit power of the second UE or adjust the transmit power of the network entity for downlink signaling to the first UE to reduce the impact of CLI.

[0053] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams involving inter-UE CLI-aware beam failure detection and radio link management.

[0054] Figure 1 An example of a wireless communication system 100 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0055] 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 signal communications according to one or more radio access technologies (RATs).

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

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

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

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

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

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

[0062] 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 other network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a collection of independent antennas for relaying communications with the UE 115, or may share the same antenna 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 a communication link with another entity (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.

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

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

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

[0066] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support inter-UE CLI-aware beam failure detection and radio link management 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).

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

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

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

[0070] 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 based on 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 the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

[0072] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 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.

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

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

[0075] 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., ranging from 0 to 1023).

[0076] 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 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0078] 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 UE115 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 .

[0079] 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) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, etc.

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

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

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

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

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

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

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

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

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

[0089] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz (also known as a centimeter band), or an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed 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.

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

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

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

[0093] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a 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).

[0094] 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., base station 140, 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.

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

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

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

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

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

[0100] The wireless communication system 100 may support techniques for beam failure monitoring and radio link monitoring. If radio conditions change suddenly, the UE 115 may experience a beam failure. For example, if a terminal user walks around a corner or a vehicle causes an obstruction between a network entity and the UE 115, the existing beam may become unreliable before the UE 115 can switch to a different beam. Measurements for radio link monitoring (e.g., downlink measurements for radio link monitoring) may be performed via the physical layer via a radio link monitoring reference signal. The measurement results may be delivered to both the MAC layer and the RRC layer at the UE 115. The RRC may detect a radio link failure, and the MAC may detect a beam failure.

[0101] The physical layer may use a quality threshold to trigger a failure indication to the MAC layer. For example, if the monitored radio link monitoring reference signal meets a threshold, the MAC layer may trigger, detect, or generate a beam failure instance. The MAC layer may use these indications (e.g., in conjunction with a counter of beam failure instances and a beam failure detection timer) to perform beam failure detection. Once a beam failure is detected, the UE 115 may attempt to recover the beam by initiating a random access channel procedure. For example, the UE 115 may utilize a configured beam failure recovery information element to perform a contention-free random access procedure. Before sending a random access channel preamble, the UE 115 may identify a new target beam by measuring candidate beams (e.g., by measuring the reference signal received power (RSRP) of the candidate beams. The UE 115 may select a beam for the random access channel procedure for beam failure recovery based on these measurements.

[0102] The wireless communication system 100 may support full-duplex operation, where devices may transmit and receive simultaneously. For example, the network entity 105 may communicate according to full-duplex operation, such as sub-band full-duplex (SBFD) operation. In the case of SBFD operation, the network entity 105 may simultaneously send downlink signaling and receive uplink signaling on a sub-band basis. For example, the network entity 105 may simultaneously send downlink messages on a downlink sub-band and receive uplink messages on an uplink sub-band. In some examples, SBFD operation may support an increased uplink duty cycle, thereby providing latency reduction and uplink coverage enhancement. For example, an increased uplink duty cycle may enable the UE 115 to receive downlink signals in an uplink-only time slot, thereby improving latency reduction. SBFD may also enable flexible and dynamic uplink and downlink resource adaptation according to uplink traffic patterns and downlink traffic patterns.

[0103] In some examples, devices in the wireless communication system 100 may experience CLI, where reception at a first device is interfered with by transmissions from a second device. Systems implementing full-duplex operation may be particularly susceptible to CLI because downlink reception at a first UE may be affected by uplink transmissions from a second UE (e.g., where the first UE and the second UE are communicating with the same network entity 105). However, CLI may also occur from intra-cell scheduling (e.g., where the first UE and the second UE are communicating with separate network entities 105 or separate serving cells).

[0104] In some examples, CLI may cause a beam failure or a radio link failure. For example, CLI may cause a sudden change in channel conditions at the first UE 115 because interference from the second UE 115 may cause the first UE 115 to be unable to receive downlink signaling. The wireless communication system 100 and the wireless communication systems described herein may support techniques for CLI detection and mitigation. In some examples, these techniques may support beam failure recovery or radio link recovery without causing the UE 115 experiencing CLI to perform a random access channel procedure.

[0105] For example, the network entity 105 may configure the UE 115 with the IMR for radio link monitoring or beam failure monitoring. The first UE 115 (e.g., a downlink receiving UE 115) may monitor the IMR to determine whether the CLI is causing a beam failure. For example, the second UE 115 (e.g., an uplink transmitting UE 115) may send signaling to the network entity 105, which may affect the downlink reception at the first UE 115. The second UE 115 may send reference signals on the IMR, which may be received at the first UE 115. If the first UE 115 detects a beam failure, the first UE 115 may determine whether the CLI from the second UE 115 is causing or contributing to the beam failure based on the reference signals on the IMR. Based on the beam failure, the first UE 115 may send a beam failure report to the network entity 105. In some examples, the beam failure report may indicate that the beam failure is based on the CLI or channel quality degradation or both. For example, the beam failure report may indicate the cause of the beam failure.

[0106] If CLI causes a beam failure, the devices may implement techniques for performing beam recovery. For example, the network entity 105, the first UE 115, or the second UE 115, or any combination thereof may implement techniques for performing beam recovery without requiring the first UE 115 to perform a random access procedure. For example, the network entity 105 may configure different scheduling configurations for the first UE 115, the second UE 115, or both, such that the first UE 115 is not scheduled to receive downlink signaling, while the second UE 115 is scheduled to send uplink signaling. Additionally or alternatively, the network entity may configure a different downlink beam for the first UE 115 or a different uplink beam for the second UE 115. In some examples, the network entity may adjust the transmit power of the second UE 115 or adjust the transmit power of the network entity for downlink signaling to the first UE 115 to reduce the impact of CLI.

[0107] Figure 2An example of a wireless communication system 200 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include a plurality of UEs 115, the plurality of UEs including UE 115-a and UE 115-b, each of which may be as described in reference Figure 1 The wireless communication system 200 may include a network entity 105-a, which may be as described in reference Figure 1 An example of a network entity 105 is described.

[0108] The wireless communication system 200 may support full-duplex operation. For example, the network entity 105-a may communicate with the UE 115-a and the UE 115-b according to full-duplex operation (such as SBFD). The network entity 105-a may send a downlink message 205 to the UE 115-a while receiving an uplink message 210 from the UE 115-b. In some examples, the transmission of the uplink message 210 from the UE 115-b may affect the reception of the downlink message 205 at the UE 115-a. This may result in CLI, where the signal propagation from the transmission of the uplink message 210 interferes with the reception of the downlink message 205 at the UE 115-a. Although the wireless communication system 200 shows an example of CLI occurring in an inter-cell configuration, CLI may similarly occur in an intra-cell configuration. For example, UE 115-b may be communicating with a different network entity or a second network entity 105, and transmissions from UE 115-b to the second network entity 105 may result in a CLI at UE 115-a.

[0109] The wireless communication system 200 may support techniques for mitigating or detecting CLI, such as in situations where CLI causes a beam failure or a radio link failure at the UE 115. For example, the network entity 105-a may configure the UE 115-a or the UE 115-b, or both, with an IMR associated with radio link monitoring or beam failure monitoring. The network entity 105-a may send control signaling that configures the transmission of a radio link monitoring reference signal 215 (e.g., an uplink radio link monitoring reference signal) as an IMR for beam failure detection or radio link monitoring or both. In some examples, a sounding reference signal (SRS) may be an example of a radio link monitoring reference signal 215.

[0110] For example, the control signaling may indicate parameters of the IMR at UE 115-a and UE 115-b. The control signaling may associate the transmission of a reference signal, such as radio link monitoring reference signal 215, with interference measurements (e.g., CLI measurements) for radio link monitoring or beam failure detection, or both. In some examples, the control signaling may indicate parameters of the IMR to configure resources for interference detection for radio link monitoring or beam failure detection, or both.

[0111] In some examples, the network entity 105-a may utilize the radio link monitoring configuration to indicate the parameters of the radio link monitoring IMR. For example, the network entity 105-a may send an RRC message indicating the parameters of the radio link monitoring configuration, such as via a radio link monitoring configuration information element. The radio link monitoring configuration may indicate the parameters of the radio link monitoring channel measurement resource (CMR) or the radio link monitoring IMR or both. For example, the parameters of the radio link monitoring IMR may include the associated SRS resource identifier, the SRS subcarrier spacing, the starting physical resource block (PRB) of the IMR, the number of PRBs of the IMR, the starting position of the IMR (e.g., in the radio frequency spectrum band), the number of symbols of the IMR, the SRS periodicity and offset, quasi-co-location information, a transmission configuration indicator (TCI) state identifier, or any combination thereof. In some examples, such as in the case where the interfering UE comes from a different serving cell, the parameters of the IMR may include a serving cell identifier or a physical cell identifier of the cell serving the interfering UE or the network entity 105-a or both.

[0112] UE 115-a may measure a radio link monitoring reference signal 215 from UE 115-b on the IMR. For example, UE 115-a may measure an SRS sent by UE 115-b on the IMR to determine whether UE 115-b is causing CLI at UE 115-a. For example, if the measurement of the radio link monitoring reference signal 215 satisfies a threshold, UE 115-a may determine that UE 115-b is causing CLI at UE 115-a.

[0113] In some cases, the CLI from UE 115-b may cause a beam failure at UE 115-a. For example, interference from the transmission of uplink message 210 may cause a sudden change in radio conditions at UE 115-a, thereby causing a beam failure. UE 115-a may send a beam failure report 220 to network entity 105-a.

[0114] In some examples, beam failure report 220 may indicate a cause of the beam failure. For example, beam failure report 220 may indicate whether the beam failure occurred due to detected CLI or due to reduced channel quality. For example, beam failure report 220 may include a field for indicating the cause of the beam failure. In some examples, a '1' in this field may indicate a beam failure due to CLI, and a '0' may indicate a beam failure due to reduced channel quality or channel quality degradation.

[0115] The network entity 105-a may receive the beam failure report 220 and identify a cause of the beam failure based on the beam failure report 220. The wireless communication system 200 may support techniques for beam recovery based on a beam failure due to the CLI. For example, the techniques for beam recovery in response to a beam failure due to the CLI may be different from the techniques for beam recovery in response to a degradation in channel quality.

[0116] For example, the network entity 105-a may send control signaling to configure different transmission parameters at UE 115-a or UE 115-b or both. In some examples, the network entity 105-a may configure different downlink UEs or uplink UEs or both. For example, the network entity 105-a may change the scheduling information or resource assignments for UE 115-a or UE 115-b or both so that the transmission from UE 115-b does not overlap with the reception at UE 115-a (e.g., in time), thereby avoiding future CLI. Additionally or alternatively, the network entity 105-a may send control signaling to switch beams at UE 115-a or UE 115-b or both. For example, the network entity 105-a may configure different downlink beams for UE 115-a, or different uplink beams for UE 115-b, or both. In some examples, network entity 105-a may adjust the uplink transmit power of UE 115-b, which may reduce the impact of CLI on UE 115-a. For example, when sending uplink data messages to network entity 105-a (e.g., during a time slot that may overlap with downlink reception at UE 115-a), network entity 105-a may reduce the transmit power of UE 115-b. In some examples, network entity 105-a may adjust the downlink transmit power of network entity 105-a. For example, network entity 105-a may transmit to UE 115-a using increased transmit power, thereby reducing the likelihood that uplink transmissions from UE 115-b cause CLI at UE 115-a.

[0117] The techniques may be implemented to identify and report whether CLI caused beam failure or radio link failure at UE 115. Additionally, the techniques may support beam recovery (such as beam recovery techniques) when beam failure is caused by CLI without performing a random access procedure.

[0118] Figure 3 An example of a process flow 300 for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is illustrated. The process flow 300 may be implemented by a UE 115-c, a UE 115-d, or a network entity 105-b, or any combination thereof. The UE 115-c and the UE 115-d may each be a network entity as described in reference Figure 1 The example of UE 115 described above and the network entity 105-b may be as shown in FIG. Figure 1 300. In some examples, some signaling or procedures of process flow 300 may occur in a different order than shown. Additionally or alternatively, some signaling or procedures not shown may occur, or some signaling or procedures not shown may not occur, or both.

[0119] The network entity 105-b may communicate with the UE 115-c and the UE 115-d in full-duplex operation. For example, the network entity 105-b may send a downlink message to the UE 115-c and simultaneously receive an uplink message from the UE 115-d. In some examples, the sending of the uplink message may cause a CLI at the UE 115-c. In some other examples, the UE 115-c may experience an intra-cell CLI, such as from a UE 115 communicating with a different network entity 105.

[0120] At 305, the network entity 105-b may send control signaling to configure one or more IMRs at the UE 115-a or the UE 115-b or both. For example, the UE 115-a may receive a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring or both. In one example, the control message may indicate parameters of the IMRs, such as a subcarrier spacing of the IMR set, a number of physical resource blocks, a starting physical resource block, a starting position, a number of symbols, a transmission configuration indicator state, or any combination thereof.

[0121] UE 115-c may monitor an IMR set for radio link monitoring reference signals based on the control message. At 310, UE 115-c may receive one or more reference signals associated with radio link monitoring or beam failure monitoring from UE 115-d via the IMR set based on the control message. For example, UE 115-d may send a radio link monitoring reference signal on the IMR set, and UE 115-c may measure the radio link monitoring reference signal. If the measurement for the one or more reference signals meets a threshold (e.g., has an RSRP measurement above a threshold), UE 115-c may detect CLI.

[0122] In some examples, the CLI from UE 115-d may affect channel conditions or link conditions at UE 115-c. For example, at 315, UE 115-c may detect a beam failure or a radio link failure or both. In some cases, interference transmitted from UE 115-d may cause a beam failure or a radio link failure at UE 115-c due to a sudden change in channel conditions.

[0123] At 320, UE 115-c may send a beam failure report to network entity 105-b. For example, UE 115-c may send a beam failure report associated with radio link monitoring or beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals. In some examples, the beam failure report may indicate a cause of the beam failure or radio link failure. In some examples, the beam failure report may indicate a CLI from UE 115-d based on the one or more measurements of the one or more reference signals. The beam failure report may indicate that the beam failure or radio link failure occurred based on the CLI from UE 115-d or a degradation in channel quality, or both.

[0124] At 325, the network entity 105-b may send updated transmit parameters to the UE 115-c or the UE 115-d or both. For example, CLI-based beam restoration may include different procedures than beam restoration based on channel quality degradation. In one example, the UE 115-c may receive a second control message in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof. In some examples, the network entity 105-b may configure a different downlink UE 115 or a different uplink UE 115. For example, the network entity 105-b may change the scheduling for the UE 115-c or the UE 115-d or both so that the UE 115-c does not receive at the same time as the UE 115-d transmits. In some examples, the network entity 105-b may configure a different downlink receive beam for the UE 115-c, or a different uplink transmit beam for the UE 115-d, or both. In some examples, network entity 105 - b may configure a different uplink transmit power for UE 115 - d , or adjust the downlink transmit power of network entity 105 - b , or both.

[0125] Figure 4 A block diagram 400 of a device 405 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 405 may be an example of aspects of the UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0126] The receiver 410 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to inter-UE CLI-aware beam failure detection and radio link management). The information may be delivered to other components of the device 405. The receiver 410 may utilize a single antenna or a collection of multiple antennas.

[0127] The transmitter 415 may provide means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to inter-UE CLI-aware beam failure detection and radio link management). In some examples, the transmitter 415 may be co-located with the receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0128] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0129] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). 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 as or otherwise supports means 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).

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

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

[0132] According to the examples disclosed herein, the communication manager 420 may support wireless communication at the first UE. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The communication manager 420 may be configured to or otherwise support a component for receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The communication manager 420 may be configured to or otherwise support a component for sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0133] Additionally or alternatively, according to examples as disclosed herein, the communication manager 420 may support wireless communication at the second UE. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The communication manager 420 may be configured to or otherwise support a component for transmitting one or more reference signals via the IMR set in response to the control message.

[0134] By including or configuring the communication manager 420 according to the examples as described herein, the device 405 (e.g., a processor controlling or otherwise coupled with the receiver 410, the transmitter 415, the communication manager 420, or a combination thereof) can support techniques for reducing power consumption and accelerating beam recovery. For example, by indicating that CLI is affecting beam failure or radio link failure, the device 405 can be configured with updated parameters to prevent CLI and recover from beam failure or radio link failure without performing random access channel procedures.

[0135] Figure 5 A block diagram 500 of a device 505 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0136] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to inter-UE CLI-aware beam failure detection and radio link management). The information may be delivered to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0137] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to inter-UE CLI-aware beam failure detection and radio link management). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0138] The device 505 or its various components may be examples of components for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 520 may include an IMR configuration component 525, an IMR monitoring component 530, a beam failure reporting component 535, an IMR sending component 540, or any combination thereof. The communication manager 520 may be an example of various aspects of the communication manager 420 as described herein. In some examples, the communication manager 520 or its various components may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0139] According to examples as disclosed herein, the communication manager 520 may support wireless communication at the first UE. The IMR configuration component 525 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The IMR monitoring component 530 may be configured to or otherwise support a component for receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The beam failure reporting component 535 may be configured to or otherwise support a component for sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0140] Additionally or alternatively, according to examples as disclosed herein, the communication manager 520 may support wireless communication at the second UE. The IMR configuration component 525 may be configured to or otherwise support a means for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The IMR transmission component 540 may be configured to or otherwise support a means for transmitting one or more reference signals via the IMR set in response to the control message.

[0141] Figure 6 A block diagram 600 of a communication manager 620 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The communication manager 620 can be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components can be examples of means for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 620 can include an IMR configuration component 625, an IMR monitoring component 630, a beam failure reporting component 635, an IMR sending component 640, a CLI indication component 645, a beam recovery component 650, a CMR configuration component 655, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0142] According to examples as disclosed herein, the communication manager 620 may support wireless communication at the first UE. The IMR configuration component 625 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The IMR monitoring component 630 may be configured to or otherwise support a component for receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The beam failure reporting component 635 may be configured to or otherwise support a component for sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0143] In some examples, to support sending the beam failure report, the CLI indication component 645 may be configured as or otherwise support a component for sending the beam failure report indicating the CLI from the second UE based on measuring the one or more reference signals.

[0144] In some examples, to support sending the beam failure report, the beam failure reporting component 635 may be configured to or otherwise support means for sending the beam failure report indicating beam failure detection based on measuring the one or more reference signals.

[0145] In some examples, to support sending the beam failure report, the beam failure reporting component 635 may be configured to or otherwise support means for sending the beam failure report indicating a radio link failure based on measuring the one or more reference signals.

[0146] In some examples, to support sending the beam failure report, the CLI indication component 645 may be configured as or otherwise support a component for sending the beam failure report, which beam failure report indicates a beam failure that occurs based on the CLI from the second UE or channel quality degradation, or both.

[0147] In some examples, the beam restoration component 650 may be configured to or otherwise support means for receiving a second control message in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0148] In some examples, to support receiving the control message, the IMR monitoring component 630 may be configured to or otherwise support means for receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals from the second UE are one or more sounding reference signals.

[0149] In some examples, to support receiving the control message, the IMR configuration component 625 may be configured as or otherwise support a component for receiving the control message indicating: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmit configuration indicator state, or any combination thereof.

[0150] In some examples, to support receiving the control message, the IMR configuration component 625 may be configured to or otherwise support a component for receiving the control message indicating a serving cell identifier or a physical cell identifier of a serving cell of the second UE, wherein the serving cell of the second UE is different from a network entity serving the first UE.

[0151] In some examples, to support receiving the control message, the CMR configuration component 655 may be configured to or otherwise support a means for receiving the control message, the control message indicating a channel measurement resource set for second reference signal transmission associated with radio link monitoring or beam failure monitoring. In some examples, to support receiving the control message, the CMR configuration component 655 may be configured to or otherwise support a means for receiving one or more second reference signals via the channel measurement resource set based on the control message. In some examples, to support receiving the control message, the CMR configuration component 655 may be configured to or otherwise support a means for sending a measurement report based on measuring the one or more second reference signals.

[0152] Additionally or alternatively, according to examples as disclosed herein, the communication manager 620 may support wireless communication at the second UE. In some examples, the IMR configuration component 625 may be configured to or otherwise support a means for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The IMR transmission component 640 may be configured to or otherwise support a means for transmitting one or more reference signals via the IMR set in response to the control message.

[0153] In some examples, beam restoration component 650 may be configured or otherwise support means for receiving a second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0154] In some examples, to support receiving the control message, IMR configuration component 625 may be configured or otherwise support means for receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals are one or more sounding reference signals.

[0155] In some examples, to support receiving the control message, the IMR configuration component 625 may be configured as or otherwise support a component for receiving the control message indicating: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmit configuration indicator state, or any combination thereof.

[0156] Figure 7 A diagram of a system 700 including a device 705 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein or include a component of these devices or UEs. The device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).

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

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

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

[0160] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 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 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to enable the device 705 to perform various functions (e.g., functions or tasks supporting inter-UE CLI-aware beam failure detection and radio link management). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.

[0161] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the first UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The communication manager 720 may be configured to or otherwise support a component for receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The communication manager 720 may be configured to or otherwise support a component for sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0162] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communication at the second UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The communication manager 720 may be configured to or otherwise support a component for transmitting one or more reference signals via the IMR set in response to the control message.

[0163] By including or configuring the communication manager 720 according to the examples as described herein, the device 705 can support techniques for reducing power consumption and accelerating beam recovery. For example, by indicating that CLI is affecting beam failure or radio link failure, the device 705 can be configured with updated parameters to prevent CLI and recover from beam failure or radio link failure without performing random access channel procedures.

[0164] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the processor 740 to cause the device 705 to perform various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.

[0165] Figure 8A block diagram 800 of a device 805 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0168] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0169] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). 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 means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

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

[0172] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE. The communication manager 820 may be configured to or otherwise support a component for receiving a beam failure report from the first UE based on the IMR set. The communication manager 820 may be configured to or otherwise support a component for sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0173] By including or configuring the communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) may support techniques for reducing power consumption and accelerating beam recovery for a UE 115 that is experiencing beam failure or radio link failure. For example, by determining that CLI is affecting or causing beam failure or radio link failure, the device 805 may configure the interfering UE 115 with updated parameters. The updated parameters may prevent CLI, and the UE 115 that is experiencing beam failure or radio link failure may recover the beam or radio link without performing a random access channel procedure.

[0174] Fig. 9 A block diagram 900 of a device 905 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0177] The device 905 or its various components may be examples of components for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 920 may include an IMR configuration component 925, a beam failure reporting component 930, a beam recovery component 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0178] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. The IMR configuration component 925 may be configured to or otherwise support a means for sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE. The beam failure reporting component 930 may be configured to or otherwise support a means for receiving a beam failure report from the first UE based on the IMR set. The beam recovery component 935 may be configured to or otherwise support a means for sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0179] Fig.10A block diagram 1000 of a communication manager 1020 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The communication manager 1020 can be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components can be examples of means for performing various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein. For example, the communication manager 1020 can include an IMR configuration component 1025, a beam failure reporting component 1030, a beam recovery component 1035, a CLI indication component 1040, a CMR configuration component 1045, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0180] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The IMR configuration component 1025 may be configured to or otherwise support a means for sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE. The beam failure reporting component 1030 may be configured to or otherwise support a means for receiving a beam failure report from the first UE based on the IMR set. The beam recovery component 1035 may be configured to or otherwise support a means for sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0181] In some examples, to support receiving the beam failure report, the CLI indication component 1040 may be configured as or otherwise support a component for receiving the beam failure report indicating the CLI from the second UE.

[0182] In some examples, to support receiving the beam failure report, beam failure reporting component 1030 can be configured to or otherwise support means for receiving the beam failure report indicating beam failure detection based on the IMR set.

[0183] In some examples, to support receiving the beam failure report, beam failure reporting component 1030 may be configured to or otherwise support means for receiving the beam failure report indicating a radio link failure based on the IMR set.

[0184] In some examples, to support receiving the beam failure report, the CLI indication component 1040 may be configured as or otherwise support a component for receiving the beam failure report, which beam failure report indicates a beam failure that occurred based on the CLI from the second UE or channel quality degradation, or both.

[0185] In some examples, to support sending the second control message, the beam recovery component 1035 may be configured as or otherwise support components for sending the second control message to the first UE or the second UE or both, wherein the second control message indicates a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0186] In some examples, to support sending the first control message, the IMR configuration component 1025 may be configured to or otherwise support means for sending the first control message indicating a sounding reference signal resource identifier, wherein the reference signal transmission is a sounding reference signal transmission.

[0187] In some examples, to support sending the first control message, the IMR configuration component 1025 may be configured as or otherwise support components for sending the first control message indicating: the subcarrier spacing of the IMR set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof.

[0188] In some examples, to support sending the first control message, the IMR configuration component 1025 may be configured to or otherwise support a component for sending the first control message indicating a serving cell identifier or a physical cell identifier of a serving cell of the second UE, where the serving cell of the second UE is different from the network entity.

[0189] In some examples, to support sending the first control message, the CMR configuration component 1045 may be configured to or otherwise support a component for sending the first control message, the first control message indicating a channel measurement resource set for second reference signal transmission associated with radio link monitoring or beam failure monitoring. In some examples, to support sending the first control message, the CMR configuration component 1045 may be configured to or otherwise support a component for sending one or more reference signals to the first UE via the channel measurement resource set based on the first control message. In some examples, to support sending the first control message, the CMR configuration component 1045 may be configured to or otherwise support a component for receiving a second measurement report indicating measurements of the one or more reference signals from the first UE.

[0190] Fig.11A diagram of a system 1100 including a device 1105 supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein or include a component of these devices or network entities. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. 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 1140).

[0191] The transceiver 1110 may support bidirectional communication via a wired link, a radio link, or both, as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 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 1110, or the transceiver 1110 and one or more antennas 1115, or the transceiver 1110 and one or more antennas 1115 and one or more processors or memory components (e.g., processor 1135 or memory 1125 or both) may be included in a chip or chip assembly installed in the device 1105. 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).

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

[0193] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 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 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1125) to enable the device 1105 to perform various functions (e.g., functions or tasks supporting inter-UE CLI-aware beam failure detection and radio link management). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. The processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that can host functions (e.g., by executing code 1130) to perform functions of the device 1105. The processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as in the memory 1125). In some specific implementations, the processor 1135 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components of the device 1105, for example). For example, the processing system of the device 1105 may refer to a system including various other components or subcomponents of the device 1105 (such as the processor 1135, or the transceiver 1110, or the communication manager 1120, or other components or combinations of components of the device 1105). The processing system of device 1105 may interface with other components of device 1105 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 1105 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 1105 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 1105 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.

[0194] In some examples, bus 1140 may support communications within a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of the different components or divided between the different components).

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

[0196] 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 a component for sending a first control message to a first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE. The communication manager 1120 may be configured to or otherwise support a component for receiving a beam failure report from the first UE based on the IMR set. The communication manager 1120 may be configured to or otherwise support a component for sending a second control message indicating a parameter set for beam failure recovery in response to the beam failure report.

[0197] By including or configuring the communication manager 1120 according to the examples as described herein, the device 1105 may support techniques for reducing power consumption and accelerating beam recovery for a UE 115 that is experiencing beam failure or radio link failure. For example, by determining that CLI is affecting or causing beam failure or radio link failure, the device 1105 may configure the interfering UE 115 with updated parameters. The updated parameters may prevent CLI, and the UE 115 that is experiencing beam failure or radio link failure may recover the beam or radio link without performing a random access channel procedure.

[0198] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, the processor 1135, the memory 1125, the code 1130, or any combination thereof. For example, the code 1130 may include instructions executable by the processor 1135 to cause the device 1105 to perform various aspects of inter-UE CLI-aware beam failure detection and radio link management as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.

[0199] Fig.12 A flow chart illustrating a method 1200 for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 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.

[0200] At 1205, the method may include: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by Figure 6 The described IMR configuration component 625 is performed.

[0201] At 1210, the method may include: receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by Figure 6 The described IMR monitoring component 630 is performed.

[0202] At 1215, the method may include: sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by Figure 6 The beam failure reporting component 635 described above is executed.

[0203] Fig.13 1 is a flowchart illustrating a method 1300 for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE 115 as described in reference to Figures 1 to 7 In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0204] At 1305, the method may include: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by Figure 6 The described IMR configuration component 625 is performed.

[0205] At 1310, the method may include: receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the IMR set based on the control message. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by Figure 6 The described IMR monitoring component 630 is performed.

[0206] At 1315, the method may include: sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by Figure 6 The beam failure reporting component 635 described above is executed.

[0207] At 1320, the method may include: receiving a second control message in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 6 The beam recovery component 650 described above is performed.

[0208] Fig.14 A flowchart illustrating a method 1400 for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 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.

[0209] At 1405, the method may include: sending a first control message to the first UE, the first control message indicating an IMR set associated with radio link monitoring or beam failure monitoring for reference signal transmission from the second UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by Fig.10 The described IMR configuration component 1025 is performed.

[0210] At 1410, the method may include: receiving a beam failure report from the first UE based on the IMR set. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.10 The beam failure reporting component 1030 described above is executed.

[0211] At 1415, the method may include: sending a second control message indicating a set of parameters for beam failure recovery in response to the beam failure report. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.10 The described beam recovery component 1035 is performed.

[0212] Fig.15 1 is a flowchart illustrating a method 1500 for supporting inter-UE CLI-aware beam failure detection and radio link management according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE 115 as described in reference to Figures 1 to 7 In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0213] At 1505, the method may include: receiving a control message indicating an IMR set for reference signal transmission associated with radio link monitoring or beam failure monitoring. 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 by Figure 6 The described IMR configuration component 625 is performed.

[0214] At 1510, the method may include: sending one or more reference signals via the IMR set in response to the control message. 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 by reference to Figure 6 The described IMR sending component 640 is performed.

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

[0216] Aspect 1: A method for performing wireless communications at a first UE, the method comprising: receiving a control message indicating an interference measurement resource set for reference signal sending associated with radio link monitoring or beam failure monitoring; receiving one or more reference signals associated with radio link monitoring or beam failure monitoring from a second UE via the interference measurement resource set based at least in part on the control message; and sending a beam failure report associated with the radio link monitoring or the beam failure monitoring based at least in part on one or more measurements of the one or more reference signals in response to receiving the one or more reference signals.

[0217] Aspect 2: The method according to aspect 1, wherein sending the beam failure report includes: sending the beam failure report indicating cross-link interference from the second UE based at least in part on measuring the one or more reference signals.

[0218] Aspect 3: The method according to any one of aspects 1 to 2, wherein sending the beam failure report comprises: sending the beam failure report indicating beam failure detection based at least in part on measuring the one or more reference signals.

[0219] Aspect 4: The method of any one of Aspects 1 to 3, wherein sending the beam failure report comprises: sending the beam failure report indicating a radio link failure based at least in part on measuring the one or more reference signals.

[0220] Aspect 5: A method according to any one of Aspects 1 to 4, wherein sending the beam failure report includes: sending the beam failure report, wherein the beam failure report indicates a beam failure occurring at least in part based on cross-link interference or channel quality degradation or both from the second UE.

[0221] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: receiving a second control message in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0222] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the control message comprises: receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals from the second UE are one or more sounding reference signals.

[0223] Aspect 8: A method according to any one of Aspects 1 to 7, wherein receiving the control message includes: receiving the control message indicating the following items: the subcarrier spacing of the interference measurement resource set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator status, or any combination thereof.

[0224] Aspect 9: A method according to any one of Aspects 1 to 8, wherein receiving the control message includes: receiving the control message indicating a service cell identifier or a physical cell identifier of a service cell of the second UE, wherein the service cell of the second UE is different from a network entity serving the first UE.

[0225] Aspect 10: A method according to any one of Aspects 1 to 9, wherein receiving the control message includes: receiving the control message, the control message indicating a channel measurement resource set for sending a second reference signal associated with the radio link monitoring or the beam failure monitoring; receiving one or more second reference signals via the channel measurement resource set based at least in part on the control message; and sending a measurement report based at least in part on measuring the one or more second reference signals.

[0226] Aspect 11: A method for performing wireless communications at a network entity, the method comprising: sending a first control message to a first UE, the first control message indicating a set of interference measurement resources associated with radio link monitoring or beam failure monitoring for sending a reference signal from a second UE; receiving a beam failure report from the first UE based at least in part on the interference measurement resource set; and sending a second control message indicating a set of parameters for beam failure recovery in response to the beam failure report.

[0227] Aspect 12: The method according to aspect 11, wherein receiving the beam failure report includes: receiving the beam failure report indicating cross-link interference from the second UE.

[0228] Aspect 13: The method according to any one of Aspects 11 to 12, wherein receiving the beam failure report comprises: receiving the beam failure report indicating beam failure detection based at least in part on the set of interference measurement resources.

[0229] Aspect 14: The method according to any one of aspects 11 to 13, wherein receiving the beam failure report comprises: receiving the beam failure report indicating a radio link failure based at least in part on the set of interference measurement resources.

[0230] Aspect 15: A method according to any one of Aspects 11 to 14, wherein receiving the beam failure report includes: receiving the beam failure report, the beam failure report indicating a beam failure occurring at least in part based on cross-link interference or channel quality degradation or both from the second UE.

[0231] Aspect 16: A method according to any one of Aspects 11 to 15, wherein sending the second control message includes: sending the second control message to the first UE or the second UE or both, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0232] Aspect 17: The method according to any one of aspects 11 to 16, wherein sending the first control message comprises: sending the first control message indicating a sounding reference signal resource identifier, wherein the reference signal sending is a sounding reference signal sending.

[0233] Aspect 18: A method according to any one of Aspects 11 to 17, wherein sending the first control message includes: sending the first control message indicating the following items: the subcarrier spacing of the interference measurement resource set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator status, or any combination thereof.

[0234] Aspect 19: A method according to any one of Aspects 11 to 18, wherein sending the first control message comprises: sending the first control message indicating a service cell identifier or a physical cell identifier of a service cell of the second UE, wherein the service cell of the second UE is different from the network entity.

[0235] Aspect 20: A method according to any one of Aspects 11 to 19, wherein sending the first control message includes: sending the first control message, the first control message indicating a channel measurement resource set for sending a second reference signal associated with the radio link monitoring or the beam failure monitoring; sending one or more reference signals to the first UE via the channel measurement resource set based at least in part on the first control message; and receiving a second measurement report from the first UE indicating measurements for the one or more reference signals.

[0236] Aspect 21: A method for performing wireless communications at a second UE, the method comprising: receiving a control message indicating an interference measurement resource set for reference signal transmission associated with radio link monitoring or beam failure monitoring; and sending one or more reference signals via the interference measurement resource set in response to the control message.

[0237] Aspect 22: The method according to Aspect 21 further comprises: receiving a second control message, wherein the second control message indicates a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

[0238] Aspect 23: The method according to any one of Aspects 21 to 22, wherein receiving the control message comprises: receiving the control message indicating a sounding reference signal resource identifier, wherein the one or more reference signals are one or more sounding reference signals.

[0239] Aspect 24: A method according to any one of Aspects 21 to 23, wherein receiving the control message includes: receiving the control message indicating the following items: the subcarrier spacing of the interference measurement resource set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator status, or any combination thereof.

[0240] Aspect 25: An apparatus for performing wireless communications at a first 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 10.

[0241] Aspect 26: An apparatus for wireless communication at a first UE, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 10.

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

[0243] Aspect 28: 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 11 to 20.

[0244] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 11 to 20.

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

[0246] Aspect 31: An apparatus for performing wireless communications at a second 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 21 to 24.

[0247] Aspect 32: An apparatus for wireless communication at a second UE, the apparatus comprising at least one means for performing a method according to any one of aspects 21 to 24.

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

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

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

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

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

[0253] 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 the functions are implemented at different physical locations.

[0254] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes computer program to be transferred from one location to another location.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. 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.

[0255] 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."

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

[0257] 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 or other subsequent reference labels.

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

[0259] 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 first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a control message indicating a set of interference measurement resources for reference signal transmission associated with radio link monitoring or beam failure monitoring; receiving, from a second UE via the set of interference measurement resources, one or more reference signals associated with the radio link monitoring or the beam failure monitoring based at least in part on the control message; as well as A beam failure report associated with the radio link monitoring or the beam failure monitoring is sent in response to receiving the one or more reference signals based at least in part on one or more measurements of the one or more reference signals.

2. The apparatus of claim 1 , wherein the instructions for sending the beam failure report are executable by the processor to cause the apparatus to: The beam failure report indicating cross-link interference from the second UE is sent based at least in part on measuring the one or more reference signals.

3. The apparatus of claim 1 , wherein the instructions for sending the beam failure report are executable by the processor to cause the apparatus to: The beam failure report indicating beam failure detection is sent based at least in part on measuring the one or more reference signals.

4. The apparatus of claim 1 , wherein the instructions for sending the beam failure report are executable by the processor to cause the apparatus to: The beam failure report indicating a radio link failure is sent based at least in part on measuring the one or more reference signals.

5. The apparatus of claim 1 , wherein the instructions for sending the beam failure report are executable by the processor to cause the apparatus to: The beam failure report is sent, the beam failure report indicating a beam failure occurring based at least in part on cross-link interference or channel quality degradation, or both, from the second UE.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A second control message is received in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

7. The apparatus of claim 1 , wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: The control message indicating a sounding reference signal resource identifier is received, wherein the one or more reference signals from the second UE are one or more sounding reference signals.

8. The apparatus of claim 1, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: The control message is received indicating the subcarrier spacing of the interference measurement resource set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof.

9. The apparatus of claim 1, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: The control message is received indicating a serving cell identifier or a physical cell identifier of a serving cell of the second UE, wherein the serving cell of the second UE is different from a network entity serving the first UE.

10. The apparatus of claim 1, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: receiving the control message, wherein the control message indicates a channel measurement resource set for second reference signal transmission associated with the radio link monitoring or the beam failure monitoring; receiving one or more second reference signals via the set of channel measurement resources based at least in part on the control message; as well as A measurement report is sent based at least in part on measuring the one or more second reference signals.

11. 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 a first control message to a first user equipment (UE), the first control message indicating a set of interference measurement resources associated with radio link monitoring or beam failure monitoring for reference signal transmission from a second UE; receiving a beam failure report from the first UE based at least in part on the set of interference measurement resources; as well as A second control message indicating a set of parameters for beam failure recovery is sent in response to the beam failure report.

12. The apparatus of claim 11, wherein the instructions for receiving the beam failure report are executable by the processor to cause the apparatus to: The beam failure report is received indicating cross-link interference from the second UE.

13. The apparatus of claim 11, wherein the instructions for receiving the beam failure report are executable by the processor to cause the apparatus to: The beam failure report indicating beam failure detection is received based at least in part on the set of interference measurement resources.

14. The apparatus of claim 11, wherein the instructions for receiving the beam failure report are executable by the processor to cause the apparatus to: The beam failure report indicating a radio link failure is received based at least in part on the set of interference measurement resources.

15. The apparatus of claim 11, wherein the instructions for receiving the beam failure report are executable by the processor to cause the apparatus to: The beam failure report is received, the beam failure report indicating a beam failure occurring based at least in part on cross-link interference or channel quality degradation, or both, from the second UE.

16. The apparatus of claim 11, wherein the instructions for sending the second control message are executable by the processor to cause the apparatus to: The second control message is sent to the first UE or the second UE or both, and the second control message indicates a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

17. The apparatus of claim 11, wherein the instructions for sending the first control message are executable by the processor to cause the apparatus to: The first control message indicating a sounding reference signal resource identifier is sent, wherein the reference signal transmission is a sounding reference signal transmission.

18. The apparatus of claim 11, wherein the instructions for sending the first control message are executable by the processor to cause the apparatus to: The first control message is sent indicating: a subcarrier spacing of the interference measurement resource set, a number of physical resource blocks, a starting physical resource block, a starting position, a number of symbols, a transmission configuration indicator state, or any combination thereof.

19. The apparatus of claim 11, wherein the instructions for sending the first control message are executable by the processor to cause the apparatus to: The first control message is sent indicating a serving cell identifier or a physical cell identifier of a serving cell of the second UE, wherein the serving cell of the second UE is different from the network entity.

20. The apparatus of claim 11, wherein the instructions for sending the first control message are executable by the processor to cause the apparatus to: Sending the first control message, wherein the first control message indicates a channel measurement resource set for sending a second reference signal associated with the radio link monitoring or the beam failure monitoring; sending one or more reference signals to the first UE via the set of channel measurement resources based at least in part on the first control message; as well as A second measurement report indicating measurements for the one or more reference signals is received from the first UE.

21. An apparatus for wireless communication at a second user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a control message indicating a set of interference measurement resources for reference signal transmission associated with radio link monitoring or beam failure monitoring; and One or more reference signals are sent via the set of interference measurement resources in response to the control message.

22. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: A second control message is received, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

23. The apparatus of claim 21, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: The control message indicating a sounding reference signal resource identifier is received, wherein the one or more reference signals are one or more sounding reference signals.

24. The apparatus of claim 21, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: The control message is received indicating the subcarrier spacing of the interference measurement resource set, the number of physical resource blocks, the starting physical resource block, the starting position, the number of symbols, the transmission configuration indicator state, or any combination thereof.

25. A method for wireless communication at a first user equipment (UE), the method comprising: receiving a control message indicating a set of interference measurement resources for reference signal transmission associated with radio link monitoring or beam failure monitoring; receiving, from a second UE via the set of interference measurement resources, one or more reference signals associated with the radio link monitoring or the beam failure monitoring based at least in part on the control message; as well as In response to receiving the one or more reference signals, a beam failure report associated with the radio link monitoring or the beam failure monitoring is sent based at least in part on one or more measurements of the one or more reference signals.

26. The method of claim 25, wherein sending the beam failure report comprises: The beam failure report indicating cross-link interference from the second UE is sent based at least in part on measuring the one or more reference signals.

27. The method of claim 25, wherein sending the beam failure report comprises: The beam failure report indicating beam failure detection is sent based at least in part on measuring the one or more reference signals.

28. The method of claim 25, wherein sending the beam failure report comprises: The beam failure report indicating a radio link failure is sent based at least in part on measuring the one or more reference signals.

29. The method of claim 25, wherein sending the beam failure report comprises: The beam failure report is sent, the beam failure report indicating a beam failure occurring based at least in part on cross-link interference or channel quality degradation, or both, from the second UE.

30. The method of claim 25, further comprising: A second control message is received in response to the beam failure report, the second control message indicating a transmit power parameter, a transmit beam parameter, a resource assignment, or any combination thereof.

Images